From owner-freebsd-current Sun Mar 26 0:51:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 85E9A37B9BC; Sun, 26 Mar 2000 00:51:08 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2Q9F7n17917; Sun, 26 Mar 2000 01:15:07 -0800 (PST) Date: Sun, 26 Mar 2000 01:15:07 -0800 From: Alfred Perlstein To: current@freebsd.org Cc: phk@freebsd.org, grog@freebsd.org Subject: vinum possible casulty of B_* patches? Message-ID: <20000326011506.R21029@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm about to wander down vinum's source again. With a kernel and vinum module dated approx Tue Feb 29 06:53:56 PST 2000 everything works fine. I recently (tonight) I cvsup'd to 5.0 to play with Matt's SMP stuff and came across a problem where it seems that 5.0 doesn't get any IO down to my vinum striped disks. I'll get panics, but then rebooting both my old and new kernels+modules the vinum volume is "clean" which leads me to belive that somewhere writes just aren't making it through to my disks. If I do a reboot I'll loose something like thousands of buffers but yet my vinum drive is "marked clean" on boot without the need for fsck. Anyhow, I just wanted to let you guys know what's going on hopefully you'll have a solution faster than I will. thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@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 Mar 26 0:54:30 2000 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 5CC6337B507; Sun, 26 Mar 2000 00:54:26 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id KAA03360; Sun, 26 Mar 2000 10:54:16 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Alfred Perlstein Cc: current@FreeBSD.ORG, grog@FreeBSD.ORG Subject: Re: vinum possible casulty of B_* patches? In-reply-to: Your message of "Sun, 26 Mar 2000 01:15:07 -0800." <20000326011506.R21029@fw.wintelcom.net> Date: Sun, 26 Mar 2000 10:54:15 +0200 Message-ID: <3358.954060855@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000326011506.R21029@fw.wintelcom.net>, Alfred Perlstein writes: >I'm about to wander down vinum's source again. > >With a kernel and vinum module dated approx Tue Feb 29 06:53:56 >PST 2000 everything works fine. > >I recently (tonight) I cvsup'd to 5.0 to play with Matt's SMP stuff >and came across a problem where it seems that 5.0 doesn't get any >IO down to my vinum striped disks. > >I'll get panics, You should know better than expect help providing only this little information... -- 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 Mar 26 1:26:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 0A41A37B891; Sun, 26 Mar 2000 01:26:37 -0800 (PST) (envelope-from ticso@cicely9.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id LAA26230; Sun, 26 Mar 2000 11:25:15 +0200 (MET DST) Received: from cicely9.cicely.de (cicely9.cicely.de [10.1.7.11]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id LAA39290; Sun, 26 Mar 2000 11:26:13 +0200 (CEST) Received: (from ticso@localhost) by cicely9.cicely.de (8.10.0.Beta12/8.10.0.Beta12) id e2Q9QDl01534; Sun, 26 Mar 2000 11:26:13 +0200 (CEST) Date: Sun, 26 Mar 2000 11:26:12 +0200 From: Bernd Walter To: Alfred Perlstein Cc: current@FreeBSD.ORG, phk@FreeBSD.ORG, grog@FreeBSD.ORG Subject: Re: vinum possible casulty of B_* patches? Message-ID: <20000326112612.A1462@cicely9.cicely.de> References: <20000326011506.R21029@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="FL5UXtIhxfXey3p5" X-Mailer: Mutt 1.0i In-Reply-To: <20000326011506.R21029@fw.wintelcom.net>; from bright@wintelcom.net on Sun, Mar 26, 2000 at 01:15:07AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=us-ascii On Sun, Mar 26, 2000 at 01:15:07AM -0800, Alfred Perlstein wrote: > I'm about to wander down vinum's source again. > > With a kernel and vinum module dated approx Tue Feb 29 06:53:56 > PST 2000 everything works fine. > > I recently (tonight) I cvsup'd to 5.0 to play with Matt's SMP stuff > and came across a problem where it seems that 5.0 doesn't get any > IO down to my vinum striped disks. > > I'll get panics, but then rebooting both my old and new kernels+modules > the vinum volume is "clean" which leads me to belive that somewhere > writes just aren't making it through to my disks. > > If I do a reboot I'll loose something like thousands of buffers > but yet my vinum drive is "marked clean" on boot without the need > for fsck. > > Anyhow, I just wanted to let you guys know what's going on hopefully > you'll have a solution faster than I will. I already fixed that and send it to Greg -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=diff Index: vinuminterrupt.c =================================================================== RCS file: /vol/cvs/src/sys/dev/vinum/vinuminterrupt.c,v retrieving revision 1.27 diff -u -u -r1.27 vinuminterrupt.c --- vinuminterrupt.c 2000/03/20 11:28:32 1.27 +++ vinuminterrupt.c 2000/03/25 19:14:25 @@ -342,7 +342,8 @@ if ((rqe->b.b_iocmd == BIO_READ) /* this was a read */ &&((rqe->flags & XFR_BAD_SUBDISK) == 0)) { /* and we can write this block */ - rqe->b.b_flags &= ~B_DONE; /* we're writing now */ + rqe->b.b_flags &= ~B_DONE; /* we're not done */ + rqe->b.b_iocmd = BIO_WRITE; /* we're writing now */ rqe->b.b_iodone = complete_rqe; /* call us here when done */ rqe->flags &= ~XFR_PARITYOP; /* reset flags that brought us here */ rqe->b.b_data = &bp->b_data[rqe->useroffset << DEV_BSHIFT]; /* point to the user data */ @@ -381,7 +382,8 @@ } /* Finally, write the parity block */ rqe = &rqg->rqe[0]; - rqe->b.b_flags &= ~B_DONE; /* we're writing now */ + rqe->b.b_flags &= ~B_DONE; /* we're not done */ + rqe->b.b_iocmd = BIO_WRITE; /* writing now */ rqe->b.b_iodone = complete_rqe; /* call us here when done */ rqg->flags &= ~XFR_PARITYOP; /* reset flags that brought us here */ rqe->b.b_bcount = rqe->buflen << DEV_BSHIFT; /* length to write */ Index: vinumraid5.c =================================================================== RCS file: /vol/cvs/src/sys/dev/vinum/vinumraid5.c,v retrieving revision 1.7 diff -u -u -r1.7 vinumraid5.c --- vinumraid5.c 2000/03/20 10:44:13 1.7 +++ vinumraid5.c 2000/03/25 20:40:59 @@ -493,7 +493,7 @@ rqe->driveno = sd->driveno; if (build_rq_buffer(rqe, plex)) /* build the buffer */ return REQUEST_ENOMEM; /* can't do it */ - rqe->b.b_iocmd == BIO_READ; /* we must read first */ + rqe->b.b_iocmd = BIO_READ; /* we must read first */ m.sdcount++; /* adjust the subdisk count */ rqno++; /* and point to the next request */ } Index: vinumrequest.c =================================================================== RCS file: /vol/cvs/src/sys/dev/vinum/vinumrequest.c,v retrieving revision 1.46 diff -u -u -r1.46 vinumrequest.c --- vinumrequest.c 2000/03/20 11:28:34 1.46 +++ vinumrequest.c 2000/03/25 23:54:29 @@ -792,11 +792,11 @@ /* Initialize the buf struct */ /* copy these flags from user bp */ bp->b_flags = ubp->b_flags & (B_ORDERED | B_NOCACHE | B_ASYNC); - bp->b_iocmd = BIO_READ; /* inform us when it's done */ + bp->b_iocmd = ubp->b_iocmd; BUF_LOCKINIT(bp); /* get a lock for the buffer */ BUF_LOCK(bp, LK_EXCLUSIVE); /* and lock it */ - bp->b_iodone = complete_rqe; /* by calling us here */ + bp->b_iodone = complete_rqe; /* calling us here when done */ /* * You'd think that we wouldn't need to even * build the request buffer for a dead subdisk, @@ -921,6 +921,7 @@ } bzero(sbp, sizeof(struct sdbuf)); /* start with nothing */ sbp->b.b_flags = bp->b_flags; + sbp->b.b_iocmd = bp->b_iocmd; sbp->b.b_bufsize = bp->b_bufsize; /* buffer size */ sbp->b.b_bcount = bp->b_bcount; /* number of bytes to transfer */ sbp->b.b_resid = bp->b_resid; /* and amount waiting */ Index: vinumrevive.c =================================================================== RCS file: /vol/cvs/src/sys/dev/vinum/vinumrevive.c,v retrieving revision 1.23 diff -u -u -r1.23 vinumrevive.c --- vinumrevive.c 2000/03/20 10:44:14 1.23 +++ vinumrevive.c 2000/03/25 17:33:57 @@ -213,7 +213,7 @@ "Relaunch revive conflict sd %d: %p\n%s dev %d.%d, offset 0x%x, length %ld\n", rq->sdno, rq, - rq->bp->b_flags == BIO_READ ? "Read" : "Write", + rq->bp->b_iocmd == BIO_READ ? "Read" : "Write", major(rq->bp->b_dev), minor(rq->bp->b_dev), rq->bp->b_blkno, --FL5UXtIhxfXey3p5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 1:41: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E524D37B9AE for ; Sun, 26 Mar 2000 01:41:06 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id BAA83490 for ; Sun, 26 Mar 2000 01:41:07 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 26 Mar 2000 01:41:07 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: fsck_msdos 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 Does anyone object to adding NetBSD's fsck_msdos to /sbin? ISTR this has come up several times in the past with positive feelings, but no-one actually did the work (it compiles trivially). I could just as easily make it a port, depending on the consensus opinion. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 2:42:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 5189D37B7EB; Sun, 26 Mar 2000 02:42:51 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.224.48]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA1F77; Sun, 26 Mar 2000 12:42:49 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id MAA05560; Sun, 26 Mar 2000 12:42:43 +0200 (CEST) (envelope-from asmodai) Date: Sun, 26 Mar 2000 12:42:43 +0200 From: Jeroen Ruigrok/Asmodai To: Kris Kennaway Cc: current@freebsd.org Subject: Re: fsck_msdos Message-ID: <20000326124242.B5522@daemon.ninth-circle.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.org on Sun, Mar 26, 2000 at 01:41:07AM -0800 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000326 12:10], Kris Kennaway (kris@FreeBSD.org) wrote: >Does anyone object to adding NetBSD's fsck_msdos to /sbin? ISTR this has >come up several times in the past with positive feelings, but no-one >actually did the work (it compiles trivially). > >I could just as easily make it a port, depending on the consensus opinion. I am not sure. I mean, I agree it is useful, however I never had the need to use something like fsck_msdos in my past 1.5-2 years, so IMHO it would be best as port. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project The descent to hell is easy... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 3:55:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 2782A37B900; Sun, 26 Mar 2000 03:55:29 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id GAA17488; Sun, 26 Mar 2000 06:55:27 -0500 (EST) Date: Sun, 26 Mar 2000 06:55:27 -0500 (EST) From: "Matthew N. Dodd" To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: fsck_msdos 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 Sun, 26 Mar 2000, Kris Kennaway wrote: > Does anyone object to adding NetBSD's fsck_msdos to /sbin? ISTR this > has come up several times in the past with positive feelings, but > no-one actually did the work (it compiles trivially). Commit it. While you're there see if any of their ext2fs /sbin tools are usable. :) > I could just as easily make it a port, depending on the consensus opinion. That would be kinda lame. If we can mount it, we should be able to fsck it and newfs it. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 4: 9:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id CF3C337B52B; Sun, 26 Mar 2000 04:09:27 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id WAA11778; Sun, 26 Mar 2000 22:17:04 +1000 Date: Sun, 26 Mar 2000 22:09:07 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: fsck_msdos 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 Sun, 26 Mar 2000, Kris Kennaway wrote: > Does anyone object to adding NetBSD's fsck_msdos to /sbin? ISTR this has > come up several times in the past with positive feelings, but no-one > actually did the work (it compiles trivially). I think Robert Nordier has a better one. > I could just as easily make it a port, depending on the consensus opinion. I think it should be a port. Similarly for fsck_ext2. The Linux (source) version is much larger and presumably more comprehensive than the NetBSD one, but it requires block devices so it doesn't work under FreeBSD-4.0. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 4:24:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 9A60A37B6DC for ; Sun, 26 Mar 2000 04:24:21 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 12ZC5b-000NSJ-0A; Sun, 26 Mar 2000 12:24:20 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id NAA98827; Sun, 26 Mar 2000 13:27:21 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 26 Mar 2000 13:31:14 +0100 (BST) From: Doug Rabson To: Andrzej Bialecki Cc: freebsd-current@freebsd.org Subject: Re: Dynamic sysctls - patches for review 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, 24 Mar 2000, Andrzej Bialecki wrote: > Hi, > > Inspired by PR kern/16928 I implemented completely dynamic > creation/deletion of sysctl trees at runtime. The patches (relative to > -current) can be found at: > > http://www.freebsd.org/~abial/dyn_sysctl.tgz > > Included is an example of KLD that creates some subtrees when loaded, and > deletes them before unloading. > > I'd appreciate some feedback. Thanks! This stuff looks very useful. I have done this kind of thing 'by hand' in the past but this should make life quite a bit easier. I think the only thing in the patch which I would want to change is to rename sysctl_deltree() to sysctl_delete_tree() to be more consistent with the naming of other functions. How much has this been tested? I wonder if the code in sysctl_deltree() which iterates over the children is correct. Surely the SLIST_REMOVE called by the child will screw up the SLIST_FOREACH iterator of the parent. In this kind of situation, I often write things differently: while ((p = SLIST_FIRST(SYSCTL_CHILDREN(oidp)) != NULL) { sysctl_deltree(p); } This will make sure that the parent does not access memory after it has been freed. -- 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 Mar 26 4:31: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (Postfix) with ESMTP id 3073C37B7E7 for ; Sun, 26 Mar 2000 04:30:58 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 12ZCC0-00050r-0C; Sun, 26 Mar 2000 12:30:56 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id NAA98838; Sun, 26 Mar 2000 13:33:57 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 26 Mar 2000 13:37:50 +0100 (BST) From: Doug Rabson To: Matthew Dillon Cc: Alfred Perlstein , freebsd-current@freebsd.org Subject: Re: SMP/BGL patch 04 In-Reply-To: <200003250216.SAA18264@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 Fri, 24 Mar 2000, Matthew Dillon wrote: > Patch 04 is ready. > > http://www.backplane.com/FreeBSD4/ > http://www.backplane.com/FreeBSD4/smp-patch-04.diff > > Contains lots of cleanup of stale SMP code. There are still a few places > where get_mplock is being called with interrupts disabled which I haven't > found, so I put the sti test back in. > > I also removed the FAST_SIMPLELOCK optimization, which had been turned > on - mainly because it's not useful if we are moving to an interrupt > thread scheme (as in it's still a global interrupt lock, whereas the > thread scheme will allow concurrent interrupt execution), but also > because it makes too many assumptions about what can run outside the > MP lock. > > I'm going to let people bang on this for a few days, and then I think > it should be committed into -CURRENT (5.x) in order to allow people > to start banging on optimizing the BGL/syscall paths. All comments > welcome (but not necessary acted upon) :-). I haven't looked at the patch so I can't comment on it (but it sounds very promising). I have been writing some of the infrastructure for SMP on alpha and as an experiment I've been using the mutex_t primitive from BSD/OS as an experiment. This is a nice simple api for a counting mutex which BSD/OS 4.1 uses for its BGL. I have not yet seen the new BSD/OS smp code but it seemed that using mutex_t might make it marginally easier to work with that. -- 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 Mar 26 5:19:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id DFCC937B6F3 for ; Sun, 26 Mar 2000 05:19:46 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 2E8082DC07; Sun, 26 Mar 2000 15:23:54 +0200 (CEST) Received: by mx.webgiro.com (Postfix, from userid 1001) id 188347811; Sun, 26 Mar 2000 15:15:14 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 12BDF10E17; Sun, 26 Mar 2000 15:15:14 +0200 (CEST) Date: Sun, 26 Mar 2000 15:15:12 +0200 (CEST) From: Andrzej Bialecki To: Doug Rabson Cc: freebsd-current@freebsd.org Subject: Re: Dynamic sysctls - patches for review 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 Sun, 26 Mar 2000, Doug Rabson wrote: > On Fri, 24 Mar 2000, Andrzej Bialecki wrote: > > > Hi, > > > > Inspired by PR kern/16928 I implemented completely dynamic > > creation/deletion of sysctl trees at runtime. The patches (relative to > > -current) can be found at: > > > > http://www.freebsd.org/~abial/dyn_sysctl.tgz > > > > Included is an example of KLD that creates some subtrees when loaded, and > > deletes them before unloading. > > > > I'd appreciate some feedback. Thanks! > > This stuff looks very useful. I have done this kind of thing 'by hand' in > the past but this should make life quite a bit easier. I think the only > thing in the patch which I would want to change is to rename > sysctl_deltree() to sysctl_delete_tree() to be more consistent with the > naming of other functions. No problem with me. > How much has this been tested? I wonder if the code in > sysctl_deltree() which iterates over the children is correct. Surely the > SLIST_REMOVE called by the child will screw up the SLIST_FOREACH iterator Hmmm. Strange - it should be, since it dereferences just freed pointer... but it worked for me. (8-* > of the parent. In this kind of situation, I often write things > differently: > > while ((p = SLIST_FIRST(SYSCTL_CHILDREN(oidp)) != NULL) { > sysctl_deltree(p); > } > > This will make sure that the parent does not access memory after it has > been freed. Yes, it looks much better to do that. Well, I tested the code creating a couple of subtrees, either from root or from one of existing categories. The code "worked for me", but it's not a proof that it does the correct thing, obviously... Also, Jonathan Lemon suggested that the dynamic oids should have a reference number, so that multiple modules could create partially overlapping trees, like: kern.one.two.module1 kern.one.two.module2 kern.one.three.module3 The problem with that approach, however, is that you no longer can delete a tree - you would need to have a way to delete a path in the tree. When I started adding the reference count, I faced a problem when module1 deleted not only kern.one.two.module1, but kern.one.two.module2 as well, because it kept a reference to the root of custom tree (one....), and then called sysctl_deltree, which of course decremented refcnt in one.two, but deleted both module1 and module2, as they both had a refcnt=1 :-( This left a dangling kern.one.two node without any children, and with refcnt=1 (that of module2). Another problem is when a module3 just checks for existence of kern.one, and if it exists, it will not try to create it (thus incrementing refcnt), but proceed to creating *.three.module3. The refcnt in kern.one will not be incremented, and when the other two modules will start deleting the tree, the kern.one will be removed, although the module3 still uses it. Well, somehow the idea of overlapping subtrees sounds nice and useful IMHO. Any suggestions how to solve these issues? One possible way to do it would be to keep some ID of the oid's creator. Then, for nodes they would be deleted when the refcnt goes to 0 (no matter who created them), but for terminals the deletion would succeed only for the owners. Also, if you create a subtree not from the root of dynamic tree, the refcnt++ would propagate up the tree as well, and similarly refcnt-- would propagate on deletion. Any comments on that? 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 Sun Mar 26 5:35:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id D3B1137B762 for ; Sun, 26 Mar 2000 05:35:52 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 12ZDCp-0007ao-0X; Sun, 26 Mar 2000 14:35:51 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id OAA99296; Sun, 26 Mar 2000 14:38:47 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 26 Mar 2000 14:42:39 +0100 (BST) From: Doug Rabson To: Andrzej Bialecki Cc: freebsd-current@freebsd.org Subject: Re: Dynamic sysctls - patches for review 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 Sun, 26 Mar 2000, Andrzej Bialecki wrote: > On Sun, 26 Mar 2000, Doug Rabson wrote: > > > On Fri, 24 Mar 2000, Andrzej Bialecki wrote: > > > > > Hi, > > > > > > Inspired by PR kern/16928 I implemented completely dynamic > > > creation/deletion of sysctl trees at runtime. The patches (relative to > > > -current) can be found at: > > > > > > http://www.freebsd.org/~abial/dyn_sysctl.tgz > > > > > > Included is an example of KLD that creates some subtrees when loaded, and > > > deletes them before unloading. > > > > > > I'd appreciate some feedback. Thanks! > > > > This stuff looks very useful. I have done this kind of thing 'by hand' in > > the past but this should make life quite a bit easier. I think the only > > thing in the patch which I would want to change is to rename > > sysctl_deltree() to sysctl_delete_tree() to be more consistent with the > > naming of other functions. > > No problem with me. > > > How much has this been tested? I wonder if the code in > > sysctl_deltree() which iterates over the children is correct. Surely the > > SLIST_REMOVE called by the child will screw up the SLIST_FOREACH iterator > > Hmmm. Strange - it should be, since it dereferences just freed > pointer... but it worked for me. (8-* > > > of the parent. In this kind of situation, I often write things > > differently: > > > > while ((p = SLIST_FIRST(SYSCTL_CHILDREN(oidp)) != NULL) { > > sysctl_deltree(p); > > } > > > > This will make sure that the parent does not access memory after it has > > been freed. > > Yes, it looks much better to do that. Well, I tested the code creating a > couple of subtrees, either from root or from one of existing > categories. The code "worked for me", but it's not a proof that it does > the correct thing, obviously... This is because the kernel malloc doesn't destroy the contents of the freed memory block (it does change the first few bytes though). I guess the oid_link field survived but this should not be relied on. > > Also, Jonathan Lemon suggested that the dynamic oids should have a > reference number, so that multiple modules could create partially > overlapping trees, like: > > kern.one.two.module1 > kern.one.two.module2 > kern.one.three.module3 > > The problem with that approach, however, is that you no longer can delete > a tree - you would need to have a way to delete a path in the tree. When I > started adding the reference count, I faced a problem when module1 deleted > not only kern.one.two.module1, but kern.one.two.module2 as well, because > it kept a reference to the root of custom tree (one....), and then called > sysctl_deltree, which of course decremented refcnt in one.two, but deleted > both module1 and module2, as they both had a refcnt=1 :-( This left a > dangling kern.one.two node without any children, and with refcnt=1 (that > of module2). > > Another problem is when a module3 just checks for existence of kern.one, > and if it exists, it will not try to create it (thus incrementing refcnt), > but proceed to creating *.three.module3. The refcnt in kern.one will not > be incremented, and when the other two modules will start deleting the > tree, the kern.one will be removed, although the module3 still uses it. > > Well, somehow the idea of overlapping subtrees sounds nice and useful > IMHO. Any suggestions how to solve these issues? > > One possible way to do it would be to keep some ID of the oid's > creator. Then, for nodes they would be deleted when the refcnt goes to 0 > (no matter who created them), but for terminals the deletion would succeed > only for the owners. Also, if you create a subtree not from the root of > dynamic tree, the refcnt++ would propagate up the tree as well, and > similarly refcnt-- would propagate on deletion. This is a reasonable solution. Another would be for dynamic sysctl users to use a 'context' object to record all their edits to the tree which would allow the edits to be backed out without relying on a tree-delete operation. -- 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 Mar 26 5:44:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id E684C37B724 for ; Sun, 26 Mar 2000 05:44:16 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id IAA80797; Sun, 26 Mar 2000 08:44:09 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200003261344.IAA80797@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Doug Rabson Cc: Andrzej Bialecki , freebsd-current@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: Dynamic sysctls - patches for review References: In-reply-to: Your message of "Sun, 26 Mar 2000 14:42:39 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Mar 2000 08:44:09 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think that if the sysctl data was reorganized, so that the per module or instance data was at the leaves of the tree, you could avoid the problem entirely. This is the general approach used on MIB definitions used for SNMP; each variable is an instance (usually the 0th) at the leaf. You don't get the opportunity to clean them all up at once by deleting a whole subtree, but you don't get the hair, either. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 6: 1:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 4073B37B76B for ; Sun, 26 Mar 2000 06:01:17 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id AAA16073; Mon, 27 Mar 2000 00:08:26 +1000 Date: Mon, 27 Mar 2000 00:00:33 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Yoshinobu Inoue Cc: bmah@CA.Sandia.GOV, nnd@mail.nsk.ru, current@FreeBSD.ORG Subject: Re: 'machine/param.h' required for 'sys/socket.h' In-Reply-To: <20000326004417L.shin@nd.net.fujitsu.co.jp> 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, 26 Mar 2000, Yoshinobu Inoue wrote: > > > OK, then how about creating machine/align.h? > > > > That approach in general would give too many headers. > Then, how about defining a macro which specifies name space > polluted part, for short term solution. > > machine/param.h: > #ifdef _NO_NAME_SPACE_POLLUTION > #define _ALIGN(x) ...... > .... > #else > .... > #endif NAME_SPACE should be spelled NAMESPACE. _ALIGN() can be defined unconditionally, since it is in the implementation namespace. This gives slightly simpler ifdefs and requires less duplication (define ALIGN(...) as _ALIGN(...)). > sys/socket.h: > #ifdef _NO_NAME_SPACE_POLLUTION > #include > #else > #define _NO_NAME_SPACE_POLLUTION > #include > #undef _NO_NAME_SPACE_POLLUTION > #endif I like this for a quick fix. Only define _ALIGN() like the current ALIGN(). Don't define all the variants given in your previous mail. > The macro might be also handy for fixing each of apps which > depends on current machine/param.h and machine/types.h one by > one. It can be specified for each apps, each dir, or in > make.conf. > > When all apps are fixed, then the macro and name space > polluted part in machine/param.h and machine/types.h can be > removed. > > Or am I still too optimistic? Supporting _NO_NAME_SPACE_POLLUTION being defined when is included is too ambitious. doesn't actually support it. All headers would need to have ifdefs like the above ones for machine/param.h to support it in general. It would be simpler to make only certain leaf headers support it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 6:16:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id BD11C37B52C; Sun, 26 Mar 2000 06:16:31 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.224.48]) by smtp05.wxs.nl (Netscape Messaging Server 4.05) with ESMTP id FS18ZH02.K4V; Sun, 26 Mar 2000 16:16:29 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id QAA05908; Sun, 26 Mar 2000 16:16:16 +0200 (CEST) (envelope-from asmodai) Date: Sun, 26 Mar 2000 16:16:15 +0200 From: Jeroen Ruigrok/Asmodai To: current@freebsd.org Cc: green@freebsd.org Subject: DDB and dumping disk Message-ID: <20000326161615.A5886@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, so thanks to Brian I can at least get a good value for my swap slice by using show disk/ad0s1b. It returns that the dev_t is 0xc0b65800 Ok, so I then proceed to look at dumpdev A p dumpdev shows me that it is set to a weird value not matching my dev_t above. A p *dumpdev returns ffffffff When I want to set dumpdev to the dev_t by using w ffffffff dumpdev=c0b65800 or w dumpdev=c0b65800 or whatever combination will either result in `nothing written' or `symbol not found'. I am obviously doing something wrong. Help appreciated. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project The descent to hell is easy... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 6:50:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id 389DE37B5F3 for ; Sun, 26 Mar 2000 06:50:37 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 1887227 invoked from network); 26 Mar 2000 14:50:32 -0000 Received: from d016.paris-30.cybercable.fr (HELO cybercable.fr) ([212.198.30.16]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 26 Mar 2000 14:50:32 -0000 Message-ID: <38DE22CF.1E49FEB5@cybercable.fr> Date: Sun, 26 Mar 2000 16:46:39 +0200 From: "Thierry.herbelot" X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: gcc-bugs@gcc.gnu.org, current@freebsd.org Subject: gcc 2.95.2 19991024 (release) bug on FreeBSD4.0 (making world) Content-Type: multipart/mixed; boundary="------------D990F9AF1E36B3CA3529986C" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------D990F9AF1E36B3CA3529986C Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Note : the compile is fine without -funroll-loops multi% gcc -v --save-temps -O -pipe -march=pentiumpro -Wall -funroll-loops -fschedule-insns2 -DLIBC_RCS -DSYSLIBC_RCS -I/files3/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/files3/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/files3/src/i386/usr/include -c uname.c -o uname.o gcc: Warning: -pipe ignored since -save-temps specified Using builtin specs. gcc version 2.95.2 19991024 (release) /usr/libexec/cpp -lang-c -v -I/files3/src/lib/libc/include -I/files3/src/lib/libc/../libc/locale -I/usr/obj/files3/src/i386/usr/include -D__GNUC__=2 -D__GNUC_MINOR__=95 -Di386 -Dunix -D__FreeBSD__=4 -D__FreeBSD_cc_version=400004 -D__i386__ -D__unix__ -D__FreeBSD__=4 -D__FreeBSD_cc_version=400004 -D__i386 -D__unix -Acpu(i386) -Amachine(i386) -Asystem(unix) -Asystem(FreeBSD) -D__OPTIMIZE__ -Wall -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -D__ELF__ -DLIBC_RCS -DSYSLIBC_RCS -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -DBROKEN_DES -DYP uname.c uname.i GNU CPP version 2.95.2 19991024 (release) (i386 FreeBSD/ELF) #include "..." search starts here: #include <...> search starts here: /files3/src/lib/libc/include /files3/src/lib/libc/../libc/locale /usr/obj/files3/src/i386/usr/include /usr/include /usr/include End of search list. The following default directories have been omitted from the search path: /usr/include/g++ End of omitted list. /usr/libexec/cc1 uname.i -quiet -dumpbase uname.c -march=pentiumpro -O -Wall -version -funroll-loops -fschedule-insns2 -o uname.s GNU C version 2.95.2 19991024 (release) (i386-unknown-freebsd) compiled by GNU C version 2.95.2 19991024 (release). uname.c: In function `uname': uname.c:125: Internal compiler error in `loop_iterations', at unroll.c:3689 Please submit a full bug report. See for instructions. multi% ll total 19 -rw-r--r-- 1 thierry.herbelot users 0 Mar 18 11:24 test -rw-r--r-- 1 thierry.herbelot users 3838 Mar 26 16:33 uname.c -rw-r--r-- 1 thierry.herbelot users 13371 Mar 26 16:36 uname.i -rw-r--r-- 1 thierry.herbelot users 51 Mar 26 16:36 uname.s multi% -- Thierry Herbelot ASCII RIBBON CAMPAIGN /"\ mailto:herbelot@cybercable.fr AGAINST HTML MAIL & NEWS \ / http://perso.cybercable.fr/herbelot PAS DE HTML DANS X Hiroshima 45, Tchernobyl 86, Windows 95... LES COURRIELS / \ --------------D990F9AF1E36B3CA3529986C Content-Type: application/x-gzip; name="uname.c.gz" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="uname.c.gz" H4sICMof3jgCA3VuYW1lLmMAvVd/U9tGFPzb/hSvSSfYxNhA0ibgJlNZPrCmtuTq5BCGZKiQ zuEmsuSRZCht8t277yyPgTht0mmaGeD07m7f7r77lc72Tp22yc7mN7l+d1lSI2rS3sHBU0Rr waUiX71TaVlQNqUSn5NUX6m80OUNR+ww0dMsT3XYJrKShAxGQbkqVH6l4jZQGN5XsS7KXF8s Sp2lFKYxLQpFOqUiW+SRMpELnYb5DQFvVrToWpeXlOXmb7YoGWWWxXqqo5AxWhTmiuYqn+my VDHN8+xKx2iUl2FpmE6zJMmudfqOoiyNNU8qGIXnzVR5yO299j1qRmfFKcpijFwUJeSUIbgy aniRXXFXZReD4F+alTpSLYzQBSXAY5h1WiPvLickjZJQz1TOHtH+p0SQ8JYjKyLQGS9A7ttw oaXKCinOosUMxQ9XReugHhn6c5qFpcp1mBRr403BGPi2DCPuSdusjTDGyil1wSnX8zkBBnJw qsJygaXDZeflYZYcRBTZtLxG2SpaxgkkmSfhzT0lYfQ+za4TFb9TjHu4XMTasIRtJfRFySJW a0yK1ZVKsjkEXNx8usIZYL3IW9RT+XuVqBvjosZKh7FLsVleGLFP2+QqbUxitDScqQ17J83W 3WbN3cdaaYXEC8VuoGgZqTRGn2KDoGiWlWqlrICQHPAxTdGx0bdqJ1ExVxHvI0zVvMFy3kHp ci8VRVU0nhMMHEnSOwpOLF8Q2mPfe+X0RZ96p+gU5Itj4QaSLLdPtucGvtObBJ4v6bffLIkJ W1vcxVCWe0ri9dgXUpLnkzMaDx3gANi33MARskWOaw8nfcc9hsuTgFwvoKEzcgIMC7wW52Og T2eSd0Qj4dsDfFo9Z+gEp4bQkRO4nO4I+SwaW37g2JOh5dN44o89adBYV9+R9tByRqKPM8xx kZjEK8giObCGwzs6gXRHZk+AotUbGiyTBzL7ji/sgPWsWzZcA7thi+RY2A43xGsBKZZ/2qpg pfh1gkHoZLS+NbKOIa7xD7agJPbEFyMmDCPkpCcDJ5gEgo49ry8ZCvBS+K8cW8guDT1pHJtI 0UKSwDLpgQK70I12byIdY5zjBsL3J+PA8dwmAw28EzgDshZm943Jnms0wyTPP2Vc9sPUoEUn A4G4z54a1yz2QsI9O2C0WyORFX4Gt8SSK46HDly3Bfd6DHTiSNFEyRzJA5xl5hPr1GicGPlc LHBbNm8t3pYpKTlHZPVfOUy+GoyFIJ1q0XhHjCQn9qByn/dBp15/qKfYXFOdqrgxdHr2ubRt 2aRHj+i7VTjRadmsd7YLPisjii7DnIooKnR89pZe0IMj7MlD+rnxsLngHd+Oas/be9RYnSa4 cTtPOwdPH3SRb4WBs7pcIuUroDrRg++PcqV6sn9IRR51En3BP1EHl3Snwm5d4V57xpf4QWf3 eWf/Ge0/Ofzh4HD3R+xxHLskfp/T9w+69Yc4TqCtw7WoZJlzDTcIsaJK/fLIpJ+Km6IzD/Nw 1r58eS+Mn6hMPo0vysJwutOh8jzNOFRHjroh3eBfzXoNFwef0tU02ubf3fqf9RqzmemLs/23 LcqvwqSLsfoPdQ6iKsWH8Wl73l2OzEyKbr1e47EowC63ef4ul8MOhue/CN/tLmN7HOPvc08G p2OBMEAR4wzZ1HDbeQk5hiR6l/AYUKWpwcTG0oIGAFu036JHd2bhG5AtcidDbP3dJr14QTt7 TYIyTG5UeC9IuN5IjGBErbbKsdKCSFIo7qk07ewh+LFeu5PobCNn2iEjcuvN7taXOTGAFa41 +owXKV5G/8KM1bRv78Yq09lm2l/vhyd9MRSW/IwhOXZxWHytH9Wsb29HlehsI+f7ZuA44He/ eang2ccvkMsQ78xUXeNQUOZhqku8Lxe5eSzOEMDTpJiHkSrafGZ8gZ+4RiSulc1uVqm/0s1q 1t+7Sf+FnVWms42k79pZw8ORGnN83xnV5WNrZ6dLjx/P19S258xr6026RR8+0Oqr3FqOMEPY rZe0Z1jXeARtEadZM66iy+zM+eP9BT44uV2Owcn5yLIHuPI3F2MWRpco+1cWo5r1PxSjynS2 kfS9YuD/cbxoGwwEQR/rfwGBajGk/g4AAA== --------------D990F9AF1E36B3CA3529986C Content-Type: application/x-gzip; name="uname.i.gz" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="uname.i.gz" H4sICFQg3jgCA3VuYW1lLmkAvVrbcts4En2GvqIrqVpLij2SaFm2S5V52pf9Bo+LRVGQzDUv Ci9ae2b879O4kc2bLELZuOKYQDca6APgdAPkV1jAlyL2Iv6b/2UEo/N+vopWsyJLZ8nmv7Nd EPLsdpal/iy4fVjJ+iD2w2LLZ9l7Njt4qRf99vIFFmd3cFmH+fuBZxYdDuvF3/JdZu0WfDqU +cpiMCcsw1lDwI7v76w6xpaPjt2QuweyvLOZc0d6NmwqgzjvWjPnG4k8/yWI+cyLs2DYkoBP 6qBfuSyJsSOYDN0A1/XyPA02Rc5ddzx23SjZiifX/fd/XHcymTCGOqi5Wrr5umxa4MD3Md/C eTZctyhNkMEYa9oW+C9eiv2B6vGhs0Ojo0zWdLKXJM2ZEqJsseo0oLW0gboSVlTtb50+j8vW SqXZXLY+5Gl/c9Vaq4iF82i5+hyCogGNNXEp0WAth0tHWcvhctZZNXWVTIPPinZnBlZWdHRn UGNFR4dmkbCiq0uDGGujS/BkDWSXD5asMHw328QR7QFkeVr4uJUOL++Zt03hr5HcnunT4nk9 +oCprl+3WoTehodubhocvfBpJZtowZqskNoiPEZusttlPO+edCFuy5sWDkG85W+nNLLgT96e SLkEUr4PspynFSsgbsY9slSEY2nkZa9SsVRhxyTYMil98eItagKMRR1MXT9JXgM+AVg3tZOa uqSvLT8GPneDrdSXi+bRNpT0EFbhij+9bFS48m8PioVArEMWJvEeheJPv2VlGFmpx7YwLaSj BvJyczdpGOjubnEsnbOixaBA97fb3uBlHT79KLwtCsmgjYxpUSlQZZiyH952m9YsCshRwHwt Ieb8JM5yFXBQw3c7VI5J6OU49Ubr2KVULtFtW1ZCgE8nxbvg7ZD3CfeBRKJTFsRJQyaXBHvl 711t5LTJ2NwnjMMgfq2PpGQEYEgHjZZi+7BDa4RqThhLwyByzfJqY5bxffan6q1D+L9N+NoD drHLSkS74C4H1MO2RBf3PtEFy/zeRAAebwMvtszooFlf3+gveRKHSFm1WslYjS0vFDOqKKvr mtJinCcvZ1kUij0WgaD1sLSF66w8F6fDuft5vCycBeaHif9qAlBtWUuJXEmjUU8MBVZGt2br rEuiusyDqLuNEKSNFHk06h08221dERXXDSWdGKAUg7fIC7Qe/s3cTZBnT+PxGM+LzhJgAt8A CzAWw012Y606gSk8oBD/3cBiMoEZnFKagMw4VI/r5hyKPyLUwA4HFvtezlXgvQZJKDrojmSB QZhx/lpTuBZQGy0V3xlEkXcow/01KLSlJv2v1oEcAxmCigGK3GuqYNbb3crm2sKhkzfsYIm/ SJk4RZddf5Ats7J3oed8OdAjXK9eaOPOsH7cQ5IFb6qfT69LKGndz216qa/ursuIlRVITs0i XHxLZHIvuU9cTMb3IvcNBc2oPWY2B/4UcZDEuJP2eIYQtAHyRMFUhUpBVRI91VV4ysJtj801 42A1P/LYnEWYLLtxkge7dxliSa1wOVGVtX6VFJ8KLkL/x7rzlCSaB/EuqXqiBnUNT1NTo3Ex Eh9zoJoqpjBrpgdD6B0lhZRUmlnu5UWmqgwYrkhFOn0xjgiRpGys2uAEVCbRFdx13HWf7p9l 7Qdo32pHt5rnmtZrebyrmH2pmFgp6eMS/oofi3TGZvPSVE+DuHe9PIkCX4c2i4N16h0GUwic lkFbDboi15ArhDZudD8bUGpLLCFTpeaYiSqMTTl/q3aS74pg5fmvauWUrQAlMgeo1qjv8uyg V7Op2BzWZSHISIEHtLALSSGrnrfk2SfPGXnm24A2poXNG1WjBZ8WPFLYE8s78ixWAm7qqlGq KUiCrAGs43cSqhqqVd819Gj/faic8r4XewtcOv3vnEw6T42JPTRmEAg5oruHFM9lT87Dcw0V SVNPi/vntSHl6gXAwjrWlbGjpHQ9l9VUen4uOPUvQ674IJlXcNp4iu08V8e0CQlpLZ3S0sQk l61gMr3GZvL+V/6o3FJZ+1BqyoJbEGQ8dxd6ex0RqrXmVWvtY91HRpSD2pFajKkRrTsHTQdK ju001suQrU/arR6r6O2FudwOAmN5bTXNMrckE5VjM1GFTwSCjECAsUdYoKeYYYlcobfuuXw/ PJoM7aEVgiPCLmTvRB10EhEqiwiVRIRKIkIlEaWSiFJJRKkkolQSUSqJKJVElEoiSiVRg0oi SiURpZKIUEkkqcTb17ygsSZSjFL528ElVcajyAQMnObG/nZpuVycrskqWpMl5stsVFb4YqOo YzSrRiLqTUn40zY3RQ1xW7YWQrnimTQm5195Slx9kJ4WDU+dQa8sO7KKiiWP3BceNlL8aXY0 5Lgut+uxGQaPdP+u6/RU9XCCGTQL0NXfIL1GagWj1kClc4blmtLyqukrPM4vOJMPJwu7jxHg kxqwag7k96Q2orS0RWk4RJY3FjBEU8Vl4t/lNzNnDq3s+LM37+0LATjpaM/3FfRuYjmvPrYZ 9kpSXyb5ucXVy7BefhS84Jd/w3DRFzEGOfjcs9W9hW+fb+izYB1G9z+xcxgwBxh/7x6thkks 3K8ustA3yM6XAstB+QLpDJsu7Zve2TddLS9BR9xH3FoZ+Ap3ju3ECLCsuMfp+UBJZ1SoJQiu yiuwwhU1Zb4iKkRWt25kJx0sKz4pW9mMsmtt4X4d9LqJGIPzOeF27lzWBwzJMrC/1fKn+4Rr Y3FrCftpdJaDbueJXVzq8zvbIYF8VaSq9DcieMqW74zNYdu8caqO36ZGpqpV+827XN7Nt01n WTHXj4tLsoAiz2Tb4W9g9A7VBsodikZF+enWgWe5SWVtnGx5R3XKQ+5lzdojT7MgiRu1Op8s az/IV0HyUxWNZGNc09Z76KVjC5h8ZWD17k0OEaZ4AEMbSapfTTaGVmWUDD4L19D3VcDJW6Tz cgMRNOsQidGPZMVY/DcpT7wlypKTR/orsyjYPDnP15AePXGzqFdxyOP1SH91o68PIFFvYdBr oQvfYS6eRfv5M5YW4nJNlBZlCa3go37VLHq9+V0vuQlKlT1UGE9BYz2eTES7YIdLQ+65MRq8 Buca/lVrjmW0fQ1zwN8JfP8ON4uJvE4MduO6OSFcODARc9WUlC4xxsOMCxXt2s1C3BSOWK3X p05PxGt14fHVH/OrU4DMexAx280WEtP+F2NSskS3M2ei4vSAosnGFhPd/BdDYhiy05MmINCL ybIHE021tpjo5qcwgf8DKCZAdLpSB4XtkG3HByzXtNaCjW5u1vDt26Ea6fQgRnf1R3wFf/8N ppRfKQ2pIjD8HRZy+ExowBWIbqoR61rVuxjzB12qq7MYTcc622nRzX/1tJgI3elKY1pSnhdp DGNhCN38GP0DHsVOATs0AAA= --------------D990F9AF1E36B3CA3529986C-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 7:14:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 78AAA37B9BB for ; Sun, 26 Mar 2000 07:14:43 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id F2D762DC09; Sun, 26 Mar 2000 17:18:53 +0200 (CEST) Received: by mx.webgiro.com (Postfix, from userid 1001) id 4DA757811; Sun, 26 Mar 2000 17:12:47 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 4850A10E17; Sun, 26 Mar 2000 17:12:47 +0200 (CEST) Date: Sun, 26 Mar 2000 17:12:47 +0200 (CEST) From: Andrzej Bialecki To: Doug Rabson Cc: freebsd-current@freebsd.org Subject: Re: Dynamic sysctls - patches for review 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 Sun, 26 Mar 2000, Doug Rabson wrote: > On Sun, 26 Mar 2000, Andrzej Bialecki wrote: > > Well, somehow the idea of overlapping subtrees sounds nice and useful > > IMHO. Any suggestions how to solve these issues? > > > > One possible way to do it would be to keep some ID of the oid's > > creator. Then, for nodes they would be deleted when the refcnt goes to 0 > > (no matter who created them), but for terminals the deletion would succeed > > only for the owners. Also, if you create a subtree not from the root of > > dynamic tree, the refcnt++ would propagate up the tree as well, and > > similarly refcnt-- would propagate on deletion. > > This is a reasonable solution. Another would be for dynamic sysctl users > to use a 'context' object to record all their edits to the tree which > would allow the edits to be backed out without relying on a tree-delete > operation. Could you explain it further? Do you mean something like a transaction log? But this wouldn't work - the operations on the tree can be interdependent between users. 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 Sun Mar 26 8: 9: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id 87E0837B79A for ; Sun, 26 Mar 2000 08:09:07 -0800 (PST) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id JAA23387 for ; Sun, 26 Mar 2000 09:09:06 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id JAA08267; Sun, 26 Mar 2000 09:09:06 -0700 (MST) (envelope-from jjreynold@home.com) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14558.13857.889817.169398@whale.home-net> Date: Sun, 26 Mar 2000 09:09:05 -0700 (MST) To: freebsd-current@freebsd.org Subject: anything more current info on UDF support/activities? X-Mailer: VM 6.73 under Emacs 20.6.1 Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I was fishing through the archives this morning (sorting by date) looking for information about support for UDF filesystems. I saw that there was a lot of explaination as to what UDF was and a lot of comments stating "no, we don't support this, yet." But, the most recent thing the search engine found was from 1998. Is there any "newer" information regarding UDF support (or lack thereof)? Is anybody currently working on at least read-only support? Does anybody know if Apple is planning on contributing efforts in this arena (I saw several postings from people working on Mac OS X regarding UDF and one of them being an advertisement for a job for somebody to develop UDF support ...)? Just curious. Thanks for any info, -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ 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 Mar 26 8:39: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 98A6D37B77A for ; Sun, 26 Mar 2000 08:39:05 -0800 (PST) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id IAA65864; Sun, 26 Mar 2000 08:39:19 -0800 (PST) Date: Sun, 26 Mar 2000 08:39:18 -0800 (PST) From: Julian Elischer To: John Reynolds Cc: freebsd-current@freebsd.org Subject: Re: anything more current info on UDF support/activities? In-Reply-To: <14558.13857.889817.169398@whale.home-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'm in the process of investigating UDF with the aim of producing a UDF filesystem (possibly only read-only) and a UDF enabled version of mkisofs (porst/sysutils) I have all the appropriate specs and standards here and have been reading them. I also have the linux UDF code as of a month or two back. I'd love to see the MACOS-X UDF code but it doesn''t seem to be released in those parts they have made public. The UDF filesystem is not rocket science but the documents describing it are in "ISO-Standardese" which means that they are almost IMPOSSIBLE to read. EVERYTHING is defined in the least useful manner possible, and no overall architecture is given. they just specify every single field, and you have to piece the big picture together from about 200 pages of minute fragments. I'm about ready to start some coding, but I still have a few details to figure out from the docs. (In the mean while all CDs and DVDs should also have a ISO9660 filesystem in parallel, pointing at the same data) (for a couple of years anyhow) (that is what the standard for DVDs say) Julian On Sun, 26 Mar 2000, John Reynolds wrote: > > Hello all, > > I was fishing through the archives this morning (sorting by date) > looking for information about support for UDF filesystems. I saw that > there was a lot of explaination as to what UDF was and a lot of > comments stating "no, we don't 1998. > > Is there any "newer" information regarding UDF support (or lack > thereof)? Is anybody currently working on at least read-only support? > Does anybody know if Apple is planning on contributing efforts in this > arena (I saw several postings from people working on Mac OS X > regarding UDF and one of them being an advertisement for a job for > somebody to develop UDF support ...)? > > Just curious. > > Thanks for any info, > > -Jr > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation > jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running > jjreynold@home.com FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve. > http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 9: 2:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id 3639D37B9EF for ; Sun, 26 Mar 2000 09:02:41 -0800 (PST) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id KAA23511; Sun, 26 Mar 2000 10:02:38 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id KAA55757; Sun, 26 Mar 2000 10:02:38 -0700 (MST) (envelope-from jjreynold@home.com) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14558.17069.754126.394415@whale.home-net> Date: Sun, 26 Mar 2000 10:02:37 -0700 (MST) To: Julian Elischer , current@freebsd.org Subject: Re: anything more current info on UDF support/activities? In-Reply-To: References: <14558.13857.889817.169398@whale.home-net> X-Mailer: VM 6.73 under Emacs 20.6.1 Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Sunday, March 26, Julian Elischer wrote: ] > I'm in the process of investigating UDF with the aim of > producing a UDF filesystem (possibly only read-only) > and a UDF enabled version of mkisofs (porst/sysutils) > cool! > I have all the appropriate specs and standards here and have been reading > them. I also have the linux UDF code as of a month or two back. I'd love > to see the MACOS-X UDF code but it doesn''t seem to be released in those > parts they have made public. :( > The UDF filesystem is not rocket science but the documents describing it > are in "ISO-Standardese" which means that they are almost IMPOSSIBLE to > read. EVERYTHING is defined in the least useful manner possible, and no > overall architecture is given. they just specify every single field, and > you have to piece the big picture together from about 200 pages of minute > fragments. if it was easy to read, it couldn't be called a "standard" though ;-) > (In the mean while all CDs and DVDs should also have a ISO9660 > filesystem in parallel, pointing at the same data) (for a couple of years > anyhow) (that is what the standard for DVDs say) Right ... I was originally searching for info on this topic because my wife got a CD-R from her relatives that was supposed to have billions of scanned family pictures on it. Unfortunately the person writing the CD-R used "DirectCD" from adaptec which uses UDF and packet writing, rather than burning an ISO9660 filesystem the "traditional" way. Thus, I was not able to "see" the contents under FreeBSD. It just got me curious. Your code will not go un-appreciated! Thanks for the more-up-to-date info, -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ 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 Mar 26 9:53:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id BDB2C37BA96 for ; Sun, 26 Mar 2000 09:53:27 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA32428; Sun, 26 Mar 2000 09:53:21 -0800 (PST) (envelope-from dillon) Date: Sun, 26 Mar 2000 09:53:21 -0800 (PST) From: Matthew Dillon Message-Id: <200003261753.JAA32428@apollo.backplane.com> To: Doug Rabson Cc: Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: SMP/BGL patch 04 References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I haven't looked at the patch so I can't comment on it (but it sounds very :promising). : :I have been writing some of the infrastructure for SMP on alpha and as an :experiment I've been using the mutex_t primitive from BSD/OS as an :experiment. This is a nice simple api for a counting mutex which BSD/OS :4.1 uses for its BGL. I have not yet seen the new BSD/OS smp code but it :seemed that using mutex_t might make it marginally easier to work with :that. : :-- :Doug Rabson Mail: dfr@nlsystems.com :Nonlinear Systems Ltd. Phone: +44 181 442 9037 Our BGL is essentially the same thing - a counting mutex with no special attributes (for example, it doesn't get fancy with cli/sti). I did a commit in Nov 99 which optimized the recursion case. It may not have been apparent from reading the code due to all the nasty CPU locking stuff that was in there (and now removed in my patchset). In FreeBSD we have two other sorts of SMP related locks: s_lock, and ss_lock. s_lock is a simple spinlock, ss_lock is a spinlock which disables interrupts. ss_lock is really crufty. The word 'bad' doesn't even begin to describe it. It is not recursive or nestable. It also will not apply at all when we move to interrupt threads. I've been removing ss_lock use in my SMP patch right and left and I'll probably remove the ss_lock code itself in patch-08. -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 Mar 26 10:37: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from Draculina.otdel-1.org (Draculina.Otdel-1.ORG [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id E230037B9EF for ; Sun, 26 Mar 2000 10:36:55 -0800 (PST) (envelope-from nms@otdel-1.org) Received: by Draculina.otdel-1.org (Postfix, from userid 1002) id 358C7F9; Sun, 26 Mar 2000 22:36:51 +0400 (MSD) Date: Sun, 26 Mar 2000 22:36:50 +0400 From: Nikolai Saoukh To: freebsd-current@freebsd.org Subject: Is there spinlocks/semaphores available for drivers? Message-ID: <20000326223650.A17200@Draculina.otdel-1.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Subject says almost all. In anticipation of SMP I would like to avoid splxxx() at all in my driver. How can I do that? Let say for FreeBSD >= 4.0. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 10:58:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust32.tnt3.waldorf.md.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 51F5637B865; Sun, 26 Mar 2000 10:58:21 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Sun, 26 Mar 2000 13:58:18 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Jeroen Ruigrok/Asmodai Cc: current@freebsd.org Subject: Re: DDB and dumping disk In-Reply-To: <20000326161615.A5886@daemon.ninth-circle.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, 26 Mar 2000, Jeroen Ruigrok/Asmodai wrote: > Ok, > > so thanks to Brian I can at least get a good value for my swap slice by > using show disk/ad0s1b. > > It returns that the dev_t is 0xc0b65800 > > Ok, so I then proceed to look at dumpdev > > A p dumpdev shows me that it is set to a weird value not matching my > dev_t above. Right, that's the address of "dev_t dumpdev". > A p *dumpdev returns ffffffff That's the value of dumpdev itself. The -1 is the value for NODEV, which is right as you haven't set it :) > When I want to set dumpdev to the dev_t by using w ffffffff > dumpdev=c0b65800 or w dumpdev=c0b65800 or whatever combination will > either result in `nothing written' or `symbol not found'. > > I am obviously doing something wrong. Help appreciated. Just do a "w dumpdev 0xc0b65800". You do need the 0x prefix, something I tried to hint at with the printout of show disk ;) > -- > Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] > Documentation nutter/C-rated Coder BSD: Technical excellence at its best > The BSD Programmer's Documentation Project > The descent to hell is easy... > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 Mar 26 11:21:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4539437BA4A for ; Sun, 26 Mar 2000 11:20:58 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA32887; Sun, 26 Mar 2000 11:20:53 -0800 (PST) (envelope-from dillon) Date: Sun, 26 Mar 2000 11:20:53 -0800 (PST) From: Matthew Dillon Message-Id: <200003261920.LAA32887@apollo.backplane.com> To: Nikolai Saoukh Cc: freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? References: <20000326223650.A17200@Draculina.otdel-1.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Subject says almost all. In anticipation of SMP I would like :to avoid splxxx() at all in my driver. How can I do that? Let say :for FreeBSD >= 4.0. : :Thanks It will probably be a months before you will be able to do that. The mechanisms haven't even been built yet. We will continue to use the spl*() calls for some time. -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 Mar 26 11:25: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E8A4D37BA88 for ; Sun, 26 Mar 2000 11:25:04 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2QJn5b02096; Sun, 26 Mar 2000 11:49:05 -0800 (PST) Date: Sun, 26 Mar 2000 11:49:05 -0800 From: Alfred Perlstein To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: vinum possible casulty of B_* patches? Message-ID: <20000326114905.U21029@fw.wintelcom.net> References: <20000326011506.R21029@fw.wintelcom.net> <3358.954060855@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3358.954060855@critter.freebsd.dk>; from phk@critter.freebsd.dk on Sun, Mar 26, 2000 at 10:54:15AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Poul-Henning Kamp [000326 01:18] wrote: > In message <20000326011506.R21029@fw.wintelcom.net>, Alfred Perlstein writes: > >I'm about to wander down vinum's source again. > > > >With a kernel and vinum module dated approx Tue Feb 29 06:53:56 > >PST 2000 everything works fine. > > > >I recently (tonight) I cvsup'd to 5.0 to play with Matt's SMP stuff > >and came across a problem where it seems that 5.0 doesn't get any > >IO down to my vinum striped disks. > > > >I'll get panics, > > You should know better than expect help providing only this little > information... It's pretty obvious that your b_iocmd patches botched vinum up, you introduced a compiler warning about dead code in the raid5 stuff as well as missing several &= ~B_READ -> biocmd = BIO_WRITE. * Poul-Henning Kamp chopped out: > >I'll get panics, but then rebooting both my old and new kernels+modules > >the vinum volume is "clean" which leads me to belive that somewhere > >writes just aren't making it through to my disks. > > > >If I do a reboot I'll loose something like thousands of buffers > >but yet my vinum drive is "marked clean" on boot without the need > >for fsck. > > > >Anyhow, I just wanted to let you guys know what's going on hopefully > >you'll have a solution faster than I will. Poul, is your mailer broken in such a way that you can't quote the entire message? I'd appreciate you looking into it because it makes communicating with you a bit difficult without feeling like you're intentionally trying to be nasty. This was intended as heads-up to people using vinum that I found some nasty breakage as well as a note to the maintainer and you (the last person to touch vinum) that something went phooey. I'm sorry, beat me, whip me, eviscerate me, whatever, my /var/crash is on my vinum volume and obviously without write ability to it, I'm going to have some issues tracking it down. Although I agree with the biocmd stuff you did, I was also disapointed to see that the only official feedback you got (from dillon) asking for you to hold off until he and Kirk completed some other work, was completely ignored. In fact the commit coincided within a few hours of his kindly worded objection. Frankly you should know better than to commit when: 1) no one is able to review, 2) there are objections, and 3) entire subsystems are kicked in the pants because you're unable to hold off a couple of days for $MAINTAINER to give it a look-see. And if you _must_ commit something under such circumstances then being nice to the people that you break would er... be the nice thing to do. I also don't see how a kinder and gentler phk couldn't have just reread his own deltas and noticed the glaring ommisions and then proceed to discuss or fix it rather than jumping down my throat. thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@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 Mar 26 11:35:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from got.wedgie.org (got.wedgie.org [216.181.169.146]) by hub.freebsd.org (Postfix) with ESMTP id E51C337B53A for ; Sun, 26 Mar 2000 11:35:18 -0800 (PST) (envelope-from jgarman@got.wedgie.org) Received: by got.wedgie.org (Postfix, from userid 1000) id CCB7CD906; Sun, 26 Mar 2000 14:35:12 -0500 (EST) Date: Sun, 26 Mar 2000 14:35:12 -0500 From: Jason Garman To: current@freebsd.org Subject: amd breakage in -current Message-ID: <20000326143512.A641@got.wedgie.org> Reply-To: jgarman@wedgie.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i X-Phase-Of-Moon: The Moon is Waning Gibbous (62% of Full) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This has been broken for at least a few weeks. I've reported it before, but I haven't had any responses so far. 5.0-current, as of last night. Related to newbus changes? cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../pci/amd.c ../../pci/amd.c:168: variable `amd_device' has initializer but incomplete type ../../pci/amd.c:170: warning: excess elements in struct initializer ../../pci/amd.c:170: warning: (near initialization for `amd_device') ../../pci/amd.c:171: warning: excess elements in struct initializer ../../pci/amd.c:171: warning: (near initialization for `amd_device') ../../pci/amd.c:172: warning: excess elements in struct initializer ../../pci/amd.c:172: warning: (near initialization for `amd_device') ../../pci/amd.c:173: warning: excess elements in struct initializer ../../pci/amd.c:173: warning: (near initialization for `amd_device') ../../pci/amd.c:175: warning: excess elements in struct initializer ../../pci/amd.c:175: warning: (near initialization for `amd_device') ../../pci/amd.c:899: warning: `amd_timeout' defined but not used ../../pci/amd.c:857: warning: `amd_reset' defined but not used -- Jason Garman http://web.wedgie.org/ Student, University of Maryland jgarman@wedgie.org From fortune(1): Whois: JAG145 "... Had this been an actual emergency, we would have fled in terror, and you would not have been informed." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 12:21:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from minubian.houabg.com (minubian.houabg.com [206.109.247.11]) by hub.freebsd.org (Postfix) with ESMTP id 6494B37B913 for ; Sun, 26 Mar 2000 12:21:49 -0800 (PST) (envelope-from dchapman@houabg.com) Received: from houcbs2.houabg.com (mailhost.houabg.com [206.109.247.20]) by minubian.houabg.com (8.8.8/8.8.8) with ESMTP id PAA21385 for ; Sun, 26 Mar 2000 15:10:50 -0600 (CST) (envelope-from dchapman@houabg.com) Received: from 216-118-21-147.pdq.net by houcbs2.houabg.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id GP4JPDDV; Sun, 26 Mar 2000 14:29:41 -0600 Message-ID: <009601bf9760$abd6d120$931576d8@inethouston.net> From: "David W. Chapman Jr." To: Subject: SPWD.DB Date: Sun, 26 Mar 2000 14:20:03 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0093_01BF972E.608B60A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0093_01BF972E.608B60A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I accidently deleted my spwd.db on 4.0-stable, how do I recreate it, any = hints would be appreciated. ------=_NextPart_000_0093_01BF972E.608B60A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I accidently deleted my spwd.db on = 4.0-stable, how=20 do I recreate it, any hints would be = appreciated.
------=_NextPart_000_0093_01BF972E.608B60A0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 12:25:21 2000 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 891A737B580 for ; Sun, 26 Mar 2000 12:25:18 -0800 (PST) (envelope-from obrien@NUXI.ucdavis.edu) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id MAA81290; Sun, 26 Mar 2000 12:25:17 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id MAA86776; Sun, 26 Mar 2000 12:25:13 -0800 (PST) (envelope-from obrien) Date: Sun, 26 Mar 2000 12:25:13 -0800 From: "David O'Brien" To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: vinum possible casulty of B_* patches? Message-ID: <20000326122513.A86753@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000326011506.R21029@fw.wintelcom.net> <3358.954060855@critter.freebsd.dk> <20000326114905.U21029@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000326114905.U21029@fw.wintelcom.net>; from bright@wintelcom.net on Sun, Mar 26, 2000 at 11:49:05AM -0800 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 Sun, Mar 26, 2000 at 11:49:05AM -0800, Alfred Perlstein wrote: > Poul, is your mailer broken in such a way that you can't quote the > entire message? I doubt it. One should NOT quote entire messages, only the applicable parts. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 12:30: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 963F737B9B9 for ; Sun, 26 Mar 2000 12:30:00 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA33447; Sun, 26 Mar 2000 12:29:55 -0800 (PST) (envelope-from dillon) Date: Sun, 26 Mar 2000 12:29:55 -0800 (PST) From: Matthew Dillon Message-Id: <200003262029.MAA33447@apollo.backplane.com> To: "David W. Chapman Jr." Cc: Subject: Re: SPWD.DB References: <009601bf9760$abd6d120$931576d8@inethouston.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :I accidently deleted my spwd.db on 4.0-stable, how do I recreate it, any = :hints would be appreciated. as root type: vipw Then write it out and quit without making any changes. spwd.db should be regenerated. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 12:32: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from Draculina.otdel-1.org (Draculina.Otdel-1.ORG [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id 4969F37B9B9 for ; Sun, 26 Mar 2000 12:32:00 -0800 (PST) (envelope-from nms@otdel-1.org) Received: by Draculina.otdel-1.org (Postfix, from userid 1002) id F1323106; Mon, 27 Mar 2000 00:31:57 +0400 (MSD) Date: Mon, 27 Mar 2000 00:31:57 +0400 From: Nikolai Saoukh To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? Message-ID: <20000327003157.A17420@Draculina.otdel-1.org> References: <20000326223650.A17200@Draculina.otdel-1.org> <200003261920.LAA32887@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003261920.LAA32887@apollo.backplane.com>; from dillon@apollo.backplane.com on Sun, Mar 26, 2000 at 11:20:53AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 26, 2000 at 11:20:53AM -0800, Matthew Dillon wrote: > It will probably be a months before you will be able to do that. The > mechanisms haven't even been built yet. We will continue to use the > spl*() calls for some time. I do not expect implementation right now. I can put some stubs in pertinent places. What I am looking for is some kind of guidelines/hints/... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 12:42:51 2000 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 BF77937B987 for ; Sun, 26 Mar 2000 12:42:45 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id WAA05411; Sun, 26 Mar 2000 22:42:28 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: vinum possible casulty of B_* patches? In-reply-to: Your message of "Sun, 26 Mar 2000 11:49:05 -0800." <20000326114905.U21029@fw.wintelcom.net> Date: Sun, 26 Mar 2000 22:42:28 +0200 Message-ID: <5409.954103348@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000326114905.U21029@fw.wintelcom.net>, Alfred Perlstein writes: >> >I'll get panics, >> >> You should know better than expect help providing only this little >> information... > >Poul, is your mailer broken in such a way that you can't quote the >entire message? If you had at least told me what panic you were getting I might have looked :-) Alfred, belive me, I'm doing my best here, but simply saying "I'll get panics" is so far from a respectable bug report that I will ignore it nomatter who sends it. -- 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 Mar 26 12:48:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D63CB37B7B4 for ; Sun, 26 Mar 2000 12:48:46 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA33563; Sun, 26 Mar 2000 12:48:42 -0800 (PST) (envelope-from dillon) Date: Sun, 26 Mar 2000 12:48:42 -0800 (PST) From: Matthew Dillon Message-Id: <200003262048.MAA33563@apollo.backplane.com> To: Nikolai Saoukh Cc: freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? References: <20000326223650.A17200@Draculina.otdel-1.org> <200003261920.LAA32887@apollo.backplane.com> <20000327003157.A17420@Draculina.otdel-1.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I do not expect implementation right now. :I can put some stubs in pertinent places. :What I am looking for is some kind of :guidelines/hints/... The answer is.... nobody knows yet :-). Interrupts will probably wind up running each in its own thread, and we will probably adopt the BSDI hybridized model (which runs an interrupt synchronously if possible and spools it to a thread otherwise) to increase efficiency. I outlined a way to keep the current spl/cpl mechanisms intact while at the same time moving interrupts to a threading model in my SMP document: http://www.backplane.com/FreeBSD4/ http://www.backplane.com/FreeBSD4/smp-api.html The mechanism I outline will allow interrupt execution concurrent with supervisor execution, and allow interrupt execution concurrent with other interrupts. For example, two different ethernet interrupts could be taken concurrently with only minor spinlock controls on the IF queue, and both could run concurrent with the TCP stack (outside of the spl*() protected areas of the TCP stack). The cool thing is that we can make the above work without gutting the current spl*() mechanisms. Frankly, the moment we can take an ethernet interrupt concurrent with the network stack, we win. The moment we can take multiple concurrent ethernet interrupts, we win even more. -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 Mar 26 13: 9:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id CD23C37B77E for ; Sun, 26 Mar 2000 13:09:17 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id QAA12802; Sun, 26 Mar 2000 16:08:58 -0500 (EST) Date: Sun, 26 Mar 2000 16:08:58 -0500 (EST) From: Daniel Eischen Message-Id: <200003262108.QAA12802@pcnet1.pcnet.com> To: dillon@apollo.backplane.com, nms@otdel-1.org Subject: Re: Is there spinlocks/semaphores available for drivers? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > The answer is.... nobody knows yet :-). > > Interrupts will probably wind up running each in its own thread, and > we will probably adopt the BSDI hybridized model (which runs an interrupt > synchronously if possible and spools it to a thread otherwise) to > increase efficiency. > > I outlined a way to keep the current spl/cpl mechanisms intact while > at the same time moving interrupts to a threading model in my SMP > document: > > http://www.backplane.com/FreeBSD4/ > http://www.backplane.com/FreeBSD4/smp-api.html > > The mechanism I outline will allow interrupt execution concurrent > with supervisor execution, and allow interrupt execution concurrent > with other interrupts. For example, two different ethernet interrupts > could be taken concurrently with only minor spinlock controls > on the IF queue, and both could run concurrent with the TCP stack > (outside of the spl*() protected areas of the TCP stack). I had a look at (VI) Interrupt-Disabling Spin locks. Wouldn't it be better to use priority inheritent mutexes of some sort. If an interrupt thread tries to take a mutex that is held by another lower priority thread, then the interrupt thread would lend its priority to mutex/lock holder. Interrupts would only be disabled while taking the lock and setting the owner field, then could be reenabled immediately afterwards. This would let drivers protect potentially time-consuming sections of code without blocking interrupts. I really dislike spinlocks and am afraid of priority inversion problems. Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 14: 4:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 2E1D737B900 for ; Sun, 26 Mar 2000 14:04:13 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id OAA14671; Sun, 26 Mar 2000 14:04:10 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38DE895A.E698E5DC@gorean.org> Date: Sun, 26 Mar 2000 14:04:10 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0322 i386) X-Accept-Language: en MIME-Version: 1.0 To: "David W. Chapman Jr." Cc: current@freebsd.org Subject: Re: SPWD.DB References: <009601bf9760$abd6d120$931576d8@inethouston.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "David W. Chapman Jr." wrote: > > I accidently deleted my spwd.db on 4.0-stable, how do I recreate it, > any hints would be appreciated. Assuming that your master.passwd is up to date, the easiest way is to do, 'pwd_mkdb -p /etc/master.passwd'. That will synch everything up for you. The man page has all the info you need. Good luck, Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 14: 6:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id CA89137BAC0 for ; Sun, 26 Mar 2000 14:06:24 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id OAA29618 for freebsd-current@FreeBSD.org; Sun, 26 Mar 2000 14:06:23 -0800 (PST) Date: Sun, 26 Mar 2000 14:06:23 -0800 From: Brooks Davis To: freebsd-current@FreeBSD.org Subject: New-bus patch for tx (kern/17601) Message-ID: <20000326140623.A27878@orion.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've written a new-bus probe/attach patch for the tx driver and submitted it as PR kern/17601. It works for me, but it could definatly use wider testing as it's my first venture into driver hacking. If you've got one of these cards please give it a spin. Thanks, Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 15:16:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from starburst.demon.co.uk (starburst.demon.co.uk [194.222.114.233]) by hub.freebsd.org (Postfix) with ESMTP id 1B33537BAA4; Sun, 26 Mar 2000 15:16:02 -0800 (PST) (envelope-from richard@starburst.demon.co.uk) Received: (from richard@localhost) by starburst.demon.co.uk (8.8.7/8.8.7) id WAA01211; Sun, 26 Mar 2000 22:25:22 +0100 From: Richard Wendland Message-Id: <200003262125.WAA01211@starburst.demon.co.uk> Subject: Re: FreeBSD random I/O performance issues To: julian@elischer.org (Julian Elischer) Date: Sun, 26 Mar 2000 22:25:21 +0100 (BST) Cc: dillon@apollo.backplane.com (Matthew Dillon), current@freebsd.org, fs@freebsd.org Reply-To: richard@netcraft.com In-Reply-To: <38D9B306.2781E494@elischer.org> from "Julian Elischer" at Mar 22, 2000 11:34:11 PM Reply-To: richard@wendland.org.uk X-Mailer: ELM [version 2.5 PL2] 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 > This is one of the things that made us do so badly > in the benchmarks against NT/Linux last year. If the benchmarks included random I/O I would think so. By creating a small synthetic program exhibiting the problem, I may have obscured the scale of the real-world consequences of this problem. Here are some test results from a slightly simplified program and data that Netcraft regularly runs. This is a simple perl DB_File program that reads 10 million input records, creating and updating a Berkeley DB file from that input. At finish the DBM is 78MB logical size, 67MB physical size (it's sparse), with 2176918 keys. These benchmark results aren't perfect, since some of the machines weren't completely idle, but they aren't far off. Elapse time OS Disc 4 hrs, 2 mins 2.2.8-STABLE Atlas II, 7200RPM, 512KB buff 3 hr, 17 mins 3.3-RELEASE ATA IBM Deskstar 34GXP, 7200RPM, 2MB 3 hr, 2 mins 3.3-STABLE IBM Ultrastar 18ES, 7200RPM, 2MB buff 1 hr, 43 mins 2.2.7-RELEASE Cheetah 9, 10000RPM, 1MB buff 51 mins 2.2.7-RELEASE Cheetah 9, 10000RPM, 1MB buff, 5 way ccd striped, interleave=64 31 mins Linux 2.2.13 IBM Ultrastar 18ES, 7200RPM, 2MB buff The run on Linux seemed CPU bound at times, with 87% CPU utilisation overall. The Linux system and the 3.3-STABLE/Ultrastar 18ES machine are both similar Dell 1300s. Netcraft runs quite a few DBM programs. You can probably see why I've gone to a fair amount of effort benchmarking to pin this performance problem down, and hopefully encourage the development of a fix. Netcraft uses heavily striped fast discs, in part to make these DBM programs run at a reasonable speed, as it turns out to overcome a software deficiency. Actually DBM performance on FreeBSD can be significantly improved by: $DB_HASH->{cachesize} = 64 * 1024 * 1024; which I commented out for this test; I doubt most DBM users set this. So our programs don't now run quite as slow as the results above suggest, by in effect creating a very large in-process write buffer. On FreeBSD this test program does about 28+2191019io according to csh 'time', I assume that's in 8KB blocks, in which case it's 16.7GB of I/O. In 51 mins that's 5.6MB/sec, on top of the seeks. Richard -- Richard Wendland richard@netcraft.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 15:22: 2 2000 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 AF86B37BA16 for ; Sun, 26 Mar 2000 15:21:59 -0800 (PST) (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 QAA51224; Sun, 26 Mar 2000 16:21:57 -0700 (MST) (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 QAA87311; Sun, 26 Mar 2000 16:21:43 -0700 (MST) Message-Id: <200003262321.QAA87311@harmony.village.org> To: jgarman@wedgie.org Subject: Re: amd breakage in -current Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 26 Mar 2000 14:35:12 EST." <20000326143512.A641@got.wedgie.org> References: <20000326143512.A641@got.wedgie.org> Date: Sun, 26 Mar 2000 16:21:43 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000326143512.A641@got.wedgie.org> Jason Garman writes: : This has been broken for at least a few weeks. I've reported it before, : but I haven't had any responses so far. 5.0-current, as of last night. : Related to newbus changes? See UPDATING: 20000319: The ISA and PCI compatability shims have been connected to the options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old style PCI or ISA drivers (i.e. tx, voxware, etc.) you must include the appropriate option in your kernel config. Drivers using the shims should be updated or they won't ship with 5.0-RELEASE, targeted for 2001. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 16:16:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 7AD2937BAD2; Sun, 26 Mar 2000 16:16:46 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id TAA00166; Sun, 26 Mar 2000 19:16:44 -0500 (EST) Message-ID: <20000326191644.A29835@netmonger.net> Date: Sun, 26 Mar 2000 19:16:44 -0500 From: Christopher Masto To: usb-bsd@egroups.com, FreeBSD CURRENT Mailing List , n_hibma@FreeBSD.ORG Subject: USB Zip 250 working (was Re: umass driver) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Nick Hibma on Sun, Mar 19, 2000 at 03:24:36PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 19, 2000 at 03:24:36PM +0000, Nick Hibma wrote: > > If anyone is using the umass driver, please send me the output of (*) > > dmesg | grep '^\(.hci\|usb\|umass\|da\|(da\)' \ > mail -s 'Drive info' n_hibma@freebsd.org Just wanted to point out that the USB Zip 250 is working after your recent commit to umass.c. uhci0: port 0xb400-0xb41f irq 9 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 umass0: Iomega USB Zip 250, rev 1.10/1.00, addr 3 da0 at umass0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 650KB/s transfers da0: 239MB (489532 512 byte sectors: 64H 32S/T 239C) da0s1: type 0xa5, start 32, end = 489471, size 489440 : OK Having heard some vaguely encouraging things from the Linux world, though, I'm considering swapping it for an Orb 2.2GB drive. Any idea whether they're mass storage class or something proprietary? -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- 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 Mar 26 20:11:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 5C16B37BB32; Sun, 26 Mar 2000 20:11:51 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.229.150]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA4789; Mon, 27 Mar 2000 06:11:49 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id GAA03029; Mon, 27 Mar 2000 06:11:47 +0200 (CEST) (envelope-from asmodai) Date: Mon, 27 Mar 2000 06:11:47 +0200 From: Jeroen Ruigrok/Asmodai To: Brian Fundakowski Feldman Cc: current@freebsd.org Subject: Re: DDB and dumping disk Message-ID: <20000327061146.A3025@daemon.ninth-circle.org> References: <20000326161615.A5886@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from green@FreeBSD.org on Sun, Mar 26, 2000 at 01:58:18PM -0500 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000327 00:00], Brian Fundakowski Feldman (green@FreeBSD.org) wrote: >On Sun, 26 Mar 2000, Jeroen Ruigrok/Asmodai wrote: > >> dumpdev=c0b65800 or w dumpdev=c0b65800 or whatever combination will >> either result in `nothing written' or `symbol not found'. > >Just do a "w dumpdev 0xc0b65800". You do need the 0x prefix, something >I tried to hint at with the printout of show disk ;) Yeah, but I went wrong into using dumpdev= instead of just using dumpdev. Thanks, it works now. ;) -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Veni, Vidi, Vici... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 20:33:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4DBE637BA66; Sun, 26 Mar 2000 20:33:31 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2R4vbe14400; Sun, 26 Mar 2000 20:57:37 -0800 (PST) Date: Sun, 26 Mar 2000 20:57:37 -0800 From: Alfred Perlstein To: Bernd Walter Cc: current@FreeBSD.ORG, grog@FreeBSD.ORG Subject: Re: vinum possible casulty of B_* patches? Message-ID: <20000326205736.Y21029@fw.wintelcom.net> References: <20000326011506.R21029@fw.wintelcom.net> <20000326112612.A1462@cicely9.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000326112612.A1462@cicely9.cicely.de>; from ticso@cicely.de on Sun, Mar 26, 2000 at 11:26:12AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Bernd Walter [000326 01:51] wrote: > On Sun, Mar 26, 2000 at 01:15:07AM -0800, Alfred Perlstein wrote: > > > > I recently (tonight) I cvsup'd to 5.0 to play with Matt's SMP stuff > > and came across a problem where it seems that 5.0 doesn't get any > > IO down to my vinum striped disks. > > > > I already fixed that and send it to Greg Thank you, it's been applied, things seem ok for me now. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 21:37:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from ws-ilmar.ints.ru (ws-ilmar.ints.ru [194.67.173.16]) by hub.freebsd.org (Postfix) with ESMTP id B42E737B955 for ; Sun, 26 Mar 2000 21:37:28 -0800 (PST) (envelope-from ilmar@ints.ru) Received: from localhost (localhost [127.0.0.1]) by ws-ilmar.ints.ru (8.9.3/8.9.3) with ESMTP id JAA00469 for ; Mon, 27 Mar 2000 09:37:14 +0400 (MSD) Date: Mon, 27 Mar 2000 09:37:14 +0400 (MSD) From: "Ilmar S. Habibulin" To: freebsd-current@freebsd.org Subject: cdrom mount 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 Has the subject been fixed or not? And what seems to be the problem, why it became broken? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 21:42:16 2000 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 BB38B37BB35 for ; Sun, 26 Mar 2000 21:42:13 -0800 (PST) (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 WAA52292; Sun, 26 Mar 2000 22:42:11 -0700 (MST) (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 WAA90244; Sun, 26 Mar 2000 22:41:57 -0700 (MST) Message-Id: <200003270541.WAA90244@harmony.village.org> To: "Ilmar S. Habibulin" Subject: Re: cdrom mount panics Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 27 Mar 2000 09:37:14 +0400." References: Date: Sun, 26 Mar 2000 22:41:57 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Ilmar S. Habibulin" writes: : Has the subject been fixed or not? And what seems to be the problem, why : it became broken? Soren broken non-cdrom changers for a couple of days. He's fixed this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 22: 8: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4199037BE31 for ; Sun, 26 Mar 2000 22:07:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA36169; Sun, 26 Mar 2000 22:07:57 -0800 (PST) (envelope-from dillon) Date: Sun, 26 Mar 2000 22:07:57 -0800 (PST) From: Matthew Dillon Message-Id: <200003270607.WAA36169@apollo.backplane.com> To: Daniel Eischen Cc: nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? References: <200003262108.QAA12802@pcnet1.pcnet.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> with supervisor execution, and allow interrupt execution concurrent :> with other interrupts. For example, two different ethernet interrupts :> could be taken concurrently with only minor spinlock controls :> on the IF queue, and both could run concurrent with the TCP stack :> (outside of the spl*() protected areas of the TCP stack). : :I had a look at (VI) Interrupt-Disabling Spin locks. : :Wouldn't it be better to use priority inheritent mutexes of some sort. :If an interrupt thread tries to take a mutex that is held by another :lower priority thread, then the interrupt thread would lend its priority :to mutex/lock holder. Interrupts would only be disabled while taking :the lock and setting the owner field, then could be reenabled immediately :afterwards. This would let drivers protect potentially time-consuming :sections of code without blocking interrupts. : :I really dislike spinlocks and am afraid of priority inversion problems. : :Dan Eischen I don't think it would matter. A process sitting in the kernel is *not* preempted except when being interrupted, so there are no 'priorities', per say. Or, rather, the relative priority is strictly that the interrupt takes priority over supervisor code except when disabled by said supervisor code. In general the best solution is to avoid using locks entirely whenever possible, and masking the interrupt for things that wind up being too complex. For example, using fixed-length FIFOs rather then linked lists. The writer manipulates the write index variable, the reader manipulates the read index variable. No locking is required between reader and writer. -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 Mar 26 22:12:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D026437B589 for ; Sun, 26 Mar 2000 22:12:08 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id WAA00845; Sun, 26 Mar 2000 22:11:32 -0800 Date: Sun, 26 Mar 2000 22:11:32 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Matthew Dillon Cc: Daniel Eischen , nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? In-Reply-To: <200003270607.WAA36169@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 > The writer manipulates the write index variable, the reader manipulates > the read index variable. No locking is required between reader and > writer. "Applause". I'm all for such solutions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 22:25:24 2000 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 1AF1437BB53 for ; Sun, 26 Mar 2000 22:25:18 -0800 (PST) (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 XAA52405; Sun, 26 Mar 2000 23:25:05 -0700 (MST) (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 XAA90617; Sun, 26 Mar 2000 23:24:50 -0700 (MST) Message-Id: <200003270624.XAA90617@harmony.village.org> To: Matthew Dillon Subject: Re: Is there spinlocks/semaphores available for drivers? Cc: Daniel Eischen , nms@otdel-1.org, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 26 Mar 2000 22:07:57 PST." <200003270607.WAA36169@apollo.backplane.com> References: <200003270607.WAA36169@apollo.backplane.com> <200003262108.QAA12802@pcnet1.pcnet.com> Date: Sun, 26 Mar 2000 23:24:50 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003270607.WAA36169@apollo.backplane.com> Matthew Dillon writes: : complex. For example, using fixed-length FIFOs rather then linked lists. : The writer manipulates the write index variable, the reader manipulates : the read index variable. No locking is required between reader and : writer. What about wrap around? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 22:30:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with SMTP id 65A6737BAC7 for ; Sun, 26 Mar 2000 22:30:52 -0800 (PST) (envelope-from me@camtech.net.au) Received: from dialup-ad-15-106.camtech.net.au ([203.55.243.106]) by camtech.net.au ; Mon, 27 Mar 2000 16:00:47 +0930 Date: Mon, 27 Mar 2000 16:00:17 +0930 (CST) From: Matthew Sean Thyer X-Sender: me@dx4.my-unregistered-domain.com Reply-To: thyerm@camtech.net.au To: Kelvin Farmer Cc: freebsd-current@freebsd.org Subject: Re: 4.0(current) on a 486SLC2 ? In-Reply-To: <38AE0CDE.2339FD8A@sympatico.ca> 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 You'll need to make custom install disks with the floating point emulator in the kernel since you dont have a FPU with that processor. On Fri, 18 Feb 2000, Kelvin Farmer wrote: > Hi, > I was wondering if its possible to run FreeBSD-4.0 on a 486 SLC2 66mhz. > (win95 runs on this computer ok) > I downloaded the floppies from Feb.14th, and disabled the hardware I > don't have > but the boot panics at: > > ... > npx0: on motherboard > npx0:Using IRQ 13 interface > > Fatal trap 12: page fault while in kernel mode > ... > (if useful I can copy down the rest of this panic) > > It doesn't have a pci bus, so my guess is that it dies probing the isa > bus ??? > > Thanks, > Kelvin > kfarmer@sympatico.ca > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 26 22:38:58 2000 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 E108837BBAD; Sun, 26 Mar 2000 22:38:54 -0800 (PST) (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 XAA52440; Sun, 26 Mar 2000 23:38:47 -0700 (MST) (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 XAA90828; Sun, 26 Mar 2000 23:38:33 -0700 (MST) Message-Id: <200003270638.XAA90828@harmony.village.org> To: Mike Smith Subject: Re: Is there spinlocks/semaphores available for drivers? Cc: Matthew Dillon , Daniel Eischen , nms@otdel-1.org, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 26 Mar 2000 22:39:38 PST." <200003270639.WAA05313@mass.cdrom.com> References: <200003270639.WAA05313@mass.cdrom.com> Date: Sun, 26 Mar 2000 23:38:33 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003270639.WAA05313@mass.cdrom.com> Mike Smith writes: : What about it in particular? Or are you referring to overflow handling? Yes. Well, I guess I assumed it was a circular thing, and you'd need to have some comparison against read index, which would be racible. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 0:37: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by hub.freebsd.org (Postfix) with ESMTP id 91DCF37BC60 for ; Mon, 27 Mar 2000 00:36:56 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-32.mail.demon.net with esmtp (Exim 2.12 #1) id 12ZV14-000Ho5-0W; Mon, 27 Mar 2000 09:36:55 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA06463; Mon, 27 Mar 2000 09:39:59 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 27 Mar 2000 09:43:38 +0100 (BST) From: Doug Rabson To: Andrzej Bialecki Cc: freebsd-current@freebsd.org Subject: Re: Dynamic sysctls - patches for review 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 Sun, 26 Mar 2000, Andrzej Bialecki wrote: > On Sun, 26 Mar 2000, Doug Rabson wrote: > > > On Sun, 26 Mar 2000, Andrzej Bialecki wrote: > > > > Well, somehow the idea of overlapping subtrees sounds nice and useful > > > IMHO. Any suggestions how to solve these issues? > > > > > > One possible way to do it would be to keep some ID of the oid's > > > creator. Then, for nodes they would be deleted when the refcnt goes to 0 > > > (no matter who created them), but for terminals the deletion would succeed > > > only for the owners. Also, if you create a subtree not from the root of > > > dynamic tree, the refcnt++ would propagate up the tree as well, and > > > similarly refcnt-- would propagate on deletion. > > > > This is a reasonable solution. Another would be for dynamic sysctl users > > to use a 'context' object to record all their edits to the tree which > > would allow the edits to be backed out without relying on a tree-delete > > operation. > > Could you explain it further? Do you mean something like a transaction > log? But this wouldn't work - the operations on the tree can be > interdependent between users. I just mean creating an object to hold pointers to all the sysctl nodes and leaves which were created (or which had their refcounts incremented). To back out the module's edits, it would just run through the list and destroy each node/leaf. The destroy procedure would decrement the refcount and use that to decide when to free the memory. -- 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 Mon Mar 27 0:48:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 61E3437BAFA; Mon, 27 Mar 2000 00:48:14 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA37083; Mon, 27 Mar 2000 00:48:12 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Mar 2000 00:48:12 -0800 (PST) From: Matthew Dillon Message-Id: <200003270848.AAA37083@apollo.backplane.com> To: Mike Smith Cc: Warner Losh , Mike Smith , Daniel Eischen , nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? References: <200003270720.XAA05430@mass.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> In message <200003270639.WAA05313@mass.cdrom.com> Mike Smith writes: :> : What about it in particular? Or are you referring to overflow handling? :> :> Yes. Well, I guess I assumed it was a circular thing, and you'd need :> to have some comparison against read index, which would be racible. : :Not if you think about it; all you need are atomic read/write operations :for the indexes. Circular FIFOs are kinda neat like that. 8) : :-- :\\ Give a man a fish, and you feed him for a day. \\ Mike Smith Well, monotonically increasing (except when it wraps), and atomic writes. Atomic read-modify-writes are not required which means that no locking is needed at all, not even a 'lock' prefix (though on some architectures you have to worry about delayed commits between cpu's). -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 Mar 27 0:56:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7C36937BC43; Mon, 27 Mar 2000 00:56:21 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA37203; Mon, 27 Mar 2000 00:56:20 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Mar 2000 00:56:20 -0800 (PST) From: Matthew Dillon Message-Id: <200003270856.AAA37203@apollo.backplane.com> To: Mike Smith , Warner Losh , Mike Smith , Daniel Eischen , nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? References: <200003270720.XAA05430@mass.cdrom.com> <200003270848.AAA37083@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG SMP FIFO (one writer, one reader): #define SIZE 256 #define MASK (SIZE-1) int ri; int wi; int fifo[SIZE]; int fifo_read(void) { int r = -1; if (ri != wi) { int nri; r = fifo[ri]; nri = (ri + 1) & MASK; ri = nri; } return(r); } int fifo_write(int v) { int nwi = (wi + 1) & MASK; if (nwi != ri) { fifo[wi] = v; wi = nwi; return(0); } else { return(-1); } } int fifo_ready() { return((wi - ri) & MASK) } int fifo_space() { return(SIZE - nready() - 1); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 1:15:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 59FDF37BC32 for ; Mon, 27 Mar 2000 01:15:15 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.calcaphon.com (henny.calcaphon.com [10.0.0.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id KAA67591; Mon, 27 Mar 2000 10:19:33 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Mon, 27 Mar 2000 10:12:35 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Christopher Masto Cc: usb-bsd@egroups.com, FreeBSD CURRENT Mailing List Subject: Re: USB Zip 250 working (was Re: umass driver) In-Reply-To: <20000326191644.A29835@netmonger.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 > Having heard some vaguely encouraging things from the Linux world, > though, I'm considering swapping it for an Orb 2.2GB drive. Any > idea whether they're mass storage class or something proprietary? In 2.3.99-pre2 [mumbles something about bloody lack of source control on those source] there is no mention of the Orb drive, apart from the message in linux-usb stating that it works 'with a patch'. But then again, Linux being one big patch, I might be wrong. So I assume, 'the patch' is the addition of the Orb Vendor and Product Id to the list of devices that are ATAPI. I'll ask them however. In their driver they have already implemented the ATAPI to SCSI converter. I haven't. Will do so as soon as I get my hands on a USB ATAPI device. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 2:24:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 1CF7037B6D4 for ; Mon, 27 Mar 2000 02:24:39 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id CAA19806; Mon, 27 Mar 2000 02:24:25 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38DF36D8.EE1E8706@gorean.org> Date: Mon, 27 Mar 2000 02:24:24 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0325 i386) X-Accept-Language: en MIME-Version: 1.0 To: Adrian Chadd Cc: FreeBSD-current@freebsd.org Subject: Re: conf/17595: Preventing cp /etc/defaults/rc.conf /etc/rc.conf from looping References: <20000325103755.10128.qmail@ewok.creative.net.au> <38DCA346.58CFC148@gorean.org> <20000327083736.A4402@ewok.creative.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I took another look at this problem, and before I go forward with more testing I wanted to solicit some comments. The problem is that users who don't read blindly copy /etc/defaults/rc.conf into /etc. Because of the recursive call at the end of /etc/defaults/rc.conf when you copy the file into /etc it gets sourced once by /etc/defaults/rc.conf, then keeps sourcing itself in /etc/rc.conf forever (actually, till the system runs out of fd's). One solution that was experimented with a while back, and referenced again in PR 17595 was to put a checkpoint variable in /etc/defaults/rc.conf which would prevent it from being recursively sourced. There are two problems with this strategy. The first is that users who define both an /etc/rc.conf and an /etc/rc.conf.local will not have the second file sourced on rc's first run through the rc.conf's. More serious is the fact that there are other scripts in /etc/rc* (like rc.firewall, rc.network, etc.) that source the rc.conf's themselves. Using this checkpoint variable method those scripts first source /etc/defaults/rc.conf, then don't go on to source the files in /etc. This prevents them from reading in user defined overrides to the defaults. This is disastrous in cases like rc.firewall, where for example the firewall type would never get defined as "open", so the machine is cut off from the network on reboot if ipfw is compiled into the kernel. The method I've finally arrived at is to replace the simple recursive source at the end of /etc/defaults/rc.conf with a combination of the checkpoint variable and the definition of a function which handles the recursive sort. This function uses a local variable to keep track of which files it has sourced already. This eliminates the possibility of infinite recursive source's, while also allowing other files to source the rc.conf's both within rc, and independently. The only thing that has to change is that the files which need to source the rc.conf's will need to add a call to this new function. Here is the function: if [ -z "${sourcercs_defined}" ]; then sourcercs_defined=yes sourcercs ( ) { local sourced_files for i in ${rc_conf_files}; do case "${sourced_files}" in *:$i:*) ;; *) sourced_files="${sourced_files}:$i:" if [ -f $i ]; then . $i fi ;; esac done } fi In (for example) rc, this: if [ -r /etc/defaults/rc.conf ]; then . /etc/defaults/rc.conf elif [ -r /etc/rc.conf ]; then . /etc/rc.conf fi would change to this: if [ -r /etc/defaults/rc.conf ]; then . /etc/defaults/rc.conf sourcercs elif [ -r /etc/rc.conf ]; then . /etc/rc.conf fi I realize that this solution may seem overly complex, but it allows the greatest amount of flexibility while at the same time unloading a gun that lots of users have shot themselves in the foot with. It works with the little test suite of conf files and scripts that I created to simulate the rc* files. I plan to do more thorough testing tomorrow with actually patching my rc* files and rebooting. Comments welcome, Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 3:34:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 4672437BB62 for ; Mon, 27 Mar 2000 03:34:43 -0800 (PST) (envelope-from adrian@creative.net.au) Received: (qmail 8901 invoked by uid 1001); 27 Mar 2000 11:34:38 -0000 Date: Mon, 27 Mar 2000 19:34:38 +0800 From: Adrian Chadd To: Doug Barton Cc: Adrian Chadd , FreeBSD-current@freebsd.org Subject: Re: conf/17595: Preventing cp /etc/defaults/rc.conf /etc/rc.conf from looping Message-ID: <20000327193437.A8861@ewok.creative.net.au> References: <20000325103755.10128.qmail@ewok.creative.net.au> <38DCA346.58CFC148@gorean.org> <20000327083736.A4402@ewok.creative.net.au> <38DF36D8.EE1E8706@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <38DF36D8.EE1E8706@gorean.org>; from Doug Barton on Mon, Mar 27, 2000 at 02:24:24AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 27, 2000, Doug Barton wrote: > One solution that was experimented with a while back, and referenced > again in PR 17595 was to put a checkpoint variable in > /etc/defaults/rc.conf which would prevent it from being recursively > sourced. There are two problems with this strategy. The first is that > users who define both an /etc/rc.conf and an /etc/rc.conf.local will not > have the second file sourced on rc's first run through the rc.conf's. > More serious is the fact that there are other scripts in /etc/rc* (like > rc.firewall, rc.network, etc.) that source the rc.conf's themselves. > Using this checkpoint variable method those scripts first source > /etc/defaults/rc.conf, then don't go on to source the files in /etc. > This prevents them from reading in user defined overrides to the > defaults. This is disastrous in cases like rc.firewall, where for > example the firewall type would never get defined as "open", so the > machine is cut off from the network on reboot if ipfw is compiled into > the kernel. Ok, I tried something a little different. I wrote a script called 'getconfig', whose sole existence is to read /etc/defaults/rc.conf, /etc/rc.conf, and then any other scripts that are in rc_conf_files (well, it didn't have to read /etc/rc.conf, but I forced it anyway ..) Then each startup script which loaded /etc/defaults/rc.conf and tried to load /etc/rc.conf was modified to load /etc/getconfig instead. Since no code exists in the conf files, if the user copies them around willy nilly, they don't cause a loop. It also means that you could possibly put sanity checking code in getconfig to make sure the user hasn't done anything blatantly stupid (I can't think of anything, but then, I don't cp /etc/defaults/rc.conf /etc/rc.conf that frequently either .. ) So, the question is: What have I missed this time ? Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 4: 2:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 47B1937BCE9 for ; Mon, 27 Mar 2000 04:02:09 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12ZYDR-000ECd-00; Mon, 27 Mar 2000 14:01:53 +0200 From: Sheldon Hearn To: Warner Losh Cc: current@FreeBSD.ORG Subject: questions asked in CURRENT, answered in UPDATING In-reply-to: Your message of "Sun, 26 Mar 2000 16:21:43 MST." <200003262321.QAA87311@harmony.village.org> Date: Mon, 27 Mar 2000 14:01:53 +0200 Message-ID: <54598.954158513@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Warner, I notice you often copy back to the list your "see UPDATING" replies to "current breakage" questions. I'd like to propose that everyone confine such answers to private mail. There are two advantages to doing it that way: 1) Folks who _do_ read UPDATING aren't further inconvenienced by multiple "see UPDATING" replies. 2) Instead, the folks who didn't read UPDATING suffer this inconvenience. It's an excellent learning opportunity for these people, since multiple "see UPDATING" replies are likely to help them remember for next time. This is akin to jmb's preference for allowing misdirected subscribe and unsubscribe requests onto the list. ;-) You like? Yes? No? 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 Mar 27 4: 6:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id C04E037BBEA; Mon, 27 Mar 2000 04:06:47 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id OAA86624; Mon, 27 Mar 2000 14:06:46 +0200 (CEST) (envelope-from asmodai) Date: Mon, 27 Mar 2000 14:06:46 +0200 From: Jeroen Ruigrok van der Werven To: Brian Fundakowski Feldman Cc: current@FreeBSD.ORG Subject: Re: DDB and dumping disk Message-ID: <20000327140646.F77375@lucifer.bart.nl> References: <20000326161615.A5886@daemon.ninth-circle.org> <20000327061146.A3025@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000327061146.A3025@daemon.ninth-circle.org>; from asmodai@wxs.nl on Mon, Mar 27, 2000 at 06:11:47AM +0200 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000327 06:15], Jeroen Ruigrok/Asmodai (asmodai@wxs.nl) wrote: >-On [20000327 00:00], Brian Fundakowski Feldman (green@FreeBSD.org) wrote: >>On Sun, 26 Mar 2000, Jeroen Ruigrok/Asmodai wrote: >> >>Just do a "w dumpdev 0xc0b65800". You do need the 0x prefix, something >>I tried to hint at with the printout of show disk ;) > >Yeah, but I went wrong into using dumpdev= instead of just using >dumpdev. > >Thanks, it works now. ;) OK, the DDB trick works. And it dumps at PIO mode 4, woot! But when I reboot the system it says it cannot find a dump on the swap device. I looked at the /dev entries, and they're all character. Ideas? -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl A liar needs a good memory... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 4: 7:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 180FD37BC81 for ; Mon, 27 Mar 2000 04:07:43 -0800 (PST) (envelope-from mzaki@e-mail.ne.jp) Received: from work.mzaki.nom (192.pool5.tokyo.att.ne.jp [165.76.22.207]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/24/99)) id VAA27757; Mon, 27 Mar 2000 21:07:38 +0900 (JST) Received: from work.mzaki.nom (mzaki@localhost [127.0.0.1]) by work.mzaki.nom (8.9.3/8.9.3) with ESMTP id VAA08501 for ; Mon, 27 Mar 2000 21:07:34 +0900 (JST) (envelope-from mzaki@e-mail.ne.jp) Date: Mon, 27 Mar 2000 21:07:33 +0900 Message-ID: <86n1nkvcoq.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: FreeBSD-current@FreeBSD.ORG Subject: Please test for 8G-OVER-Booting with /boot/loader X-Mailer: Wanderlust/2.2.12 (Joyride) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: multipart/mixed; boundary="Multipart_Mon_Mar_27_21:07:33_2000-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Multipart_Mon_Mar_27_21:07:33_2000-1 Content-Type: text/plain; charset=US-ASCII Hi. I made a patch for /sys/boot/i386/libi386/biosdisk.c (attached). This aimed to enable /boot/loader to manage 8G-OVER-Disks. 0. you need 8G-OVER-ENABLED BIOS for your motherboard (check whether your BIOS has Int 13 Extended Interface) 1. teach boot0 using extended BIOS (See boot0cfg(8)) # boot0cfg -o packet YOUR-BOOT-DEVICE 2. install boot2 which have extended BIOS support # cd /sys/boot/i386/boot2; make B1FLAGS=0x80 clean install 3. patch to libi386 and install new /boot/loader # cd /sys/boot/i386/libi386/; patch Dept. of Biological Science, Faculty of Sciences, Univ. of Tokyo, Japan --Multipart_Mon_Mar_27_21:07:33_2000-1 Content-Type: application/octet-stream; type=patch Content-Disposition: attachment; filename="biosdisk.c.diff" Content-Transfer-Encoding: 7bit --- biosdisk.c Thu Mar 16 01:36:55 2000 +++ biosdisk.c.new Mon Mar 27 20:50:38 2000 @@ -74,7 +74,7 @@ int od_flags; #define BD_MODEMASK 0x3 #define BD_MODEINT13 0x0 -#define BD_MODEEDD1 0x1 +#define BD_MODEPACKET 0x1 #define BD_MODEEDD3 0x2 #define BD_FLOPPY (1<<2) struct disklabel od_disklabel; @@ -166,13 +166,13 @@ bdinfo[nbdinfo].bd_unit = unit; bdinfo[nbdinfo].bd_flags = (unit < 0x80) ? BD_FLOPPY : 0; - /* XXX add EDD probes */ if (!bd_int13probe(&bdinfo[nbdinfo])) break; /* XXX we need "disk aliases" to make this simpler */ - printf("BIOS drive %c: is disk%d\n", - (unit < 0x80) ? ('A' + unit) : ('C' + unit - 0x80), nbdinfo); + printf("BIOS drive %c: is disk%d%s\n", + (unit < 0x80) ? ('A' + unit) : ('C' + unit - 0x80), nbdinfo, + (bdinfo[nbdinfo].bd_flags & BD_MODEPACKET) ? " (LBA)" : ""); nbdinfo++; } } @@ -180,7 +180,7 @@ } /* - * Try to detect a device supported by the legacy int13 BIOS + * Try to detect a device supported by the int13 BIOS */ static int @@ -197,6 +197,26 @@ ((v86.edx & 0xff) > (bd->bd_unit & 0x7f))) { /* unit # OK */ bd->bd_flags |= BD_MODEINT13; bd->bd_type = v86.ebx & 0xff; + + /* LBA support by Motomichi Matsuzaki */ + + v86.ctl = V86_FLAGS; + v86.addr = 0x13; + v86.eax = 0x4100; + v86.ebx = 0x55AA; + v86.edx = bd->bd_unit; + v86int(); + + if (!(v86.efl & 0x1) && /* carry clear */ + (v86.ebx & 0xffff) == 0xAA55) { /* magic OK */ + if ((v86.eax & 0xf000) >= 0x3000) { + bd->bd_flags |= BD_MODEEDD3; /* meanless? */ + } + if (v86.ecx & 0x1) { + bd->bd_flags |= BD_MODEPACKET; /* packet access */ + } + } + return(1); } return(0); @@ -624,6 +644,15 @@ /* Max number of sectors to bounce-buffer if the request crosses a 64k boundary */ #define FLOPPY_BOUNCEBUF 18 +struct lba_packet { + u_int8_t len; + u_int8_t rsrv; + u_int16_t blks; + u_int16_t offs; + u_int16_t seg; + u_int64_t blkno; +}; + static int bd_read(struct open_disk *od, daddr_t dblk, int blks, caddr_t dest) { @@ -685,25 +714,44 @@ v86.edx = od->od_unit; v86int(); } - - /* build request XXX support EDD requests too */ - v86.ctl = V86_FLAGS; - v86.addr = 0x13; - v86.eax = 0x200 | x; - v86.ecx = ((cyl & 0xff) << 8) | ((cyl & 0x300) >> 2) | sec; - v86.edx = (hd << 8) | od->od_unit; - v86.es = VTOPSEG(xp); - v86.ebx = VTOPOFF(xp); - v86int(); + + /* build request */ + if (od->od_flags & BD_MODEPACKET) { + struct lba_packet pkt + = {sizeof(pkt), 0, x, VTOPOFF(xp), VTOPSEG(xp), dblk}; + v86.ctl = V86_FLAGS; + v86.addr = 0x13; + v86.eax = 0x4200; + v86.edx = od->od_unit; + v86.ds = VTOPSEG(&pkt); + v86.esi = VTOPOFF(&pkt); + v86int(); + } else { + v86.ctl = V86_FLAGS; + v86.addr = 0x13; + v86.eax = 0x200 | x; + v86.ecx = ((cyl & 0xff) << 8) | ((cyl & 0x300) >> 2) | sec; + v86.edx = (hd << 8) | od->od_unit; + v86.es = VTOPSEG(xp); + v86.ebx = VTOPOFF(xp); + v86int(); + } result = (v86.efl & 0x1); if (result == 0) break; } - DEBUG("%d sectors from %d/%d/%d to %p (0x%x) %s", x, cyl, hd, sec - 1, p, VTOP(p), result ? "failed" : "ok"); - /* BUG here, cannot use v86 in printf because putchar uses it too */ - DEBUG("ax = 0x%04x cx = 0x%04x dx = 0x%04x status 0x%x", - 0x200 | x, ((cyl & 0xff) << 8) | ((cyl & 0x300) >> 2) | sec, (hd << 8) | od->od_unit, (v86.eax >> 8) & 0xff); + if (od->od_flags & BD_MODEPACKET) { + DEBUG("%d sectors from %d to %p (0x%x) %s", + x, dblk, p, VTOP(p), result ? "failed" : "ok"); + } else { + DEBUG("%d sectors from %d/%d/%d to %p (0x%x) %s", + x, cyl, hd, sec - 1, p, VTOP(p), result ? "failed" : "ok"); + /* BUG here, cannot use v86 in printf because putchar uses it too */ + DEBUG("ax = 0x%04x cx = 0x%04x dx = 0x%04x status 0x%x", + 0x200 | x, ((cyl & 0xff) << 8) | ((cyl & 0x300) >> 2) | sec, + (hd << 8) | od->od_unit, (v86.eax >> 8) & 0xff); + } if (result) { if (bbuf != NULL) free(bbuf); --Multipart_Mon_Mar_27_21:07:33_2000-1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 4:36:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 5EBCB37BB2A; Mon, 27 Mar 2000 04:36:31 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA53149; Mon, 27 Mar 2000 14:36:14 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200003271236.OAA53149@freebsd.dk> Subject: Re: DDB and dumping disk In-Reply-To: <20000327140646.F77375@lucifer.bart.nl> from Jeroen Ruigrok van der Werven at "Mar 27, 2000 02:06:46 pm" To: asmodai@bart.nl (Jeroen Ruigrok van der Werven) Date: Mon, 27 Mar 2000 14:36:14 +0200 (CEST) Cc: green@FreeBSD.ORG (Brian Fundakowski Feldman), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Jeroen Ruigrok van der Werven wrote: > > the DDB trick works. And it dumps at PIO mode 4, woot! > You have to, there is no garantie that DMA and even less interrupts is working proberly on a potentially hosed machine.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 4:40:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 6634C37BA9F for ; Mon, 27 Mar 2000 04:40:28 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id HAA18515; Mon, 27 Mar 2000 07:40:12 -0500 (EST) Date: Mon, 27 Mar 2000 07:40:11 -0500 (EST) From: Daniel Eischen To: Matthew Dillon Cc: nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? In-Reply-To: <200003270607.WAA36169@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 Sun, 26 Mar 2000, Matthew Dillon wrote: > :> with supervisor execution, and allow interrupt execution concurrent > :> with other interrupts. For example, two different ethernet interrupts > :> could be taken concurrently with only minor spinlock controls > :> on the IF queue, and both could run concurrent with the TCP stack > :> (outside of the spl*() protected areas of the TCP stack). > : > :I had a look at (VI) Interrupt-Disabling Spin locks. > : > :Wouldn't it be better to use priority inheritent mutexes of some sort. > :If an interrupt thread tries to take a mutex that is held by another > :lower priority thread, then the interrupt thread would lend its priority > :to mutex/lock holder. Interrupts would only be disabled while taking > :the lock and setting the owner field, then could be reenabled immediately > :afterwards. This would let drivers protect potentially time-consuming > :sections of code without blocking interrupts. > : > :I really dislike spinlocks and am afraid of priority inversion problems. > : > :Dan Eischen > > I don't think it would matter. A process sitting in the kernel is > *not* preempted except when being interrupted, so there are no > 'priorities', per say. Or, rather, the relative priority is strictly > that the interrupt takes priority over supervisor code except when > disabled by said supervisor code. But locks with owners wouldn't have to disable interrupts (given that we have interrupt threads). What about shared interrupts? You could still field and process the interrupt as long as it was for a different device. > In general the best solution is to avoid using locks entirely whenever > possible, and masking the interrupt for things that wind up being too > complex. For example, using fixed-length FIFOs rather then linked lists. > The writer manipulates the write index variable, the reader manipulates > the read index variable. No locking is required between reader and > writer. No argument here. Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 4:50:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id A73D037BAEF; Mon, 27 Mar 2000 04:50:25 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id OAA86970; Mon, 27 Mar 2000 14:50:12 +0200 (CEST) (envelope-from asmodai) Date: Mon, 27 Mar 2000 14:50:12 +0200 From: Jeroen Ruigrok van der Werven To: Soren Schmidt Cc: Brian Fundakowski Feldman , current@FreeBSD.ORG Subject: Re: DDB and dumping disk Message-ID: <20000327145012.H77375@lucifer.bart.nl> References: <20000327140646.F77375@lucifer.bart.nl> <200003271236.OAA53149@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003271236.OAA53149@freebsd.dk>; from sos@freebsd.dk on Mon, Mar 27, 2000 at 02:36:14PM +0200 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000327 14:40], Soren Schmidt (sos@freebsd.dk) wrote: >It seems Jeroen Ruigrok van der Werven wrote: >> >> the DDB trick works. And it dumps at PIO mode 4, woot! >> >You have to, there is no garantie that DMA and even less interrupts >is working proberly on a potentially hosed machine.. I wasn't complaining, on the contrary! I was happily surprised it was way faster than the SCSI dump. =) -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl Necessity is the mother of invention... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 4:59:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id C2A6B37BAEF for ; Mon, 27 Mar 2000 04:59:29 -0800 (PST) (envelope-from sam@inf.enst.fr) Received: from antinea.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id 5F6CB19076; Mon, 27 Mar 2000 14:58:34 +0200 (CEST) Received: by antinea.enst.fr (Postfix, from userid 1000) id BA8AF271; Mon, 27 Mar 2000 14:58:33 +0200 (CEST) Date: Mon, 27 Mar 2000 14:58:32 +0200 To: freebsd-current@freebsd.org Subject: make buildworld fails due to a missing share/man/man4/wst.4 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-03-27-14-58-33+trackit+sam@inf.enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With the current sources. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 5: 4:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id 4148537BAEF for ; Mon, 27 Mar 2000 05:04:38 -0800 (PST) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.5.62]) by matrix.eurocontrol.fr (Postfix) with ESMTP id 54A0231F4 for ; Mon, 27 Mar 2000 14:04:34 +0100 (CET) (envelope-from roberto@caerdonn.eurocontrol.fr) Received: by caerdonn.eurocontrol.fr (Postfix, from userid 1193) id 4205C4E2D; Mon, 27 Mar 2000 15:04:34 +0200 (CEST) Date: Mon, 27 Mar 2000 15:04:34 +0200 From: Ollivier Robert To: FreeBSD Current Users' list Subject: World broken in modules/linprocfs Message-ID: <20000327150434.D85207@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.9i X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> sys/modules/linprocfs @ -> /src/src/sys machine -> /src/src/sys/i386/include rm -f .depend mkdep -f .depend -a -nostdinc -DLINPROCFS -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/src/src/i386/usr/include /src/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_misc.c /src/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_subr.c /src/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_vfsops.c /src/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_vnops.c In file included from /src/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_misc.c:48: @/sys/vnode.h:514: vnode_if.h: No such file or directory [1] + done makeworld -B In file included from /src/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_subr.c:45: @/sys/vnode.h:514: vnode_if.h: No such file or directory In file included from /src/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_vfsops.c:52: @/sys/vnode.h:514: vnode_if.h: No such file or directory In file included from /src/src/sys/modules/linprocfs/../../miscfs/linprocfs/linprocfs_vnops.c:54: @/sys/vnode.h:514: vnode_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /src/src/sys/modules/linprocfs. *** Error code 1 Stop in /src/src/sys/modules. *** Error code 1 Stop in /src/src/sys. *** Error code 1 Stop in /src/src. *** Error code 1 Stop in /src/src. *** Error code 1 Stop in /src/src. 2128.48 real 1406.59 user 358.53 sys Mon Mar 27 14:24:59 CEST 2000 -- Ollivier ROBERT -=- Eurocontrol EEC/TEC -=- Ollivier.Robert@eurocontrol.fr The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 5:30:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from imsp211.netvigator.com (imsp211.netvigator.com [205.252.144.55]) by hub.freebsd.org (Postfix) with ESMTP id 96CDE37BBC7 for ; Mon, 27 Mar 2000 05:30:01 -0800 (PST) (envelope-from leohon11@netvigator.com) Received: from netvigator.com (bbig002244.netvigator.com [208.151.89.244]) by imsp211.netvigator.com (8.9.3/8.9.1) with ESMTP id VAA13324; Mon, 27 Mar 2000 21:29:55 +0800 (HKT) Message-ID: <38DF625F.CFC1BD28@netvigator.com> Date: Mon, 27 Mar 2000 21:30:07 +0800 From: leohon11 X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pdf MIME-Version: 1.0 To: freebsd-current@FreeBSD.org, leohon11@netvigator.com Subject: Problems on installation Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Sir/Madam, I have download 4.0 but cannot install : Error "can not parse sbase ...... then reboot. Is there a problem on the iso format file in your ftp site ? Please give me information. Thanks, Regards, Leo Hon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 5:40:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from sr14.nsw-remote.bigpond.net.au (sr14.nsw-remote.bigpond.net.au [24.192.3.29]) by hub.freebsd.org (Postfix) with ESMTP id F031237BB38 for ; Mon, 27 Mar 2000 05:40:15 -0800 (PST) (envelope-from areilly@nsw.bigpond.net.au) Received: from areilly.bpc-users.org (CPE-144-132-171-71.nsw.bigpond.net.au [144.132.171.71]) by sr14.nsw-remote.bigpond.net.au (Pro-8.9.3/8.9.3) with SMTP id QAA04901 for ; Mon, 27 Mar 2000 16:35:52 +1000 (EST) Received: (qmail 74234 invoked by uid 1000); 27 Mar 2000 06:35:51 -0000 From: "Andrew Reilly" Date: Mon, 27 Mar 2000 16:35:51 +1000 To: Warner Losh Cc: Matthew Dillon , Daniel Eischen , nms@otdel-1.org, freebsd-current@freebsd.org Subject: Re: Is there spinlocks/semaphores available for drivers? Message-ID: <20000327163551.A73982@gurney.reilly.home> References: <200003270607.WAA36169@apollo.backplane.com> <200003262108.QAA12802@pcnet1.pcnet.com> <200003270607.WAA36169@apollo.backplane.com> <200003270624.XAA90617@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200003270624.XAA90617@harmony.village.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 26, 2000 at 11:24:50PM -0700, Warner Losh wrote: > In message <200003270607.WAA36169@apollo.backplane.com> Matthew Dillon writes: > : complex. For example, using fixed-length FIFOs rather then linked lists. > : The writer manipulates the write index variable, the reader manipulates > : the read index variable. No locking is required between reader and > : writer. > > What about wrap around? You mean queue empty or queue full? That's when you have to punt to a rate-limit mechanism. Dunno what that would be in interrupt context. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 6: 3:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 50DCD37BB87 for ; Mon, 27 Mar 2000 06:03:08 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id JAA85743; Mon, 27 Mar 2000 09:03:03 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200003271403.JAA85743@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <86n1nkvcoq.wl@tkc.att.ne.jp> Date: Mon, 27 Mar 2000 09:03:03 -0500 (EST) From: John Baldwin To: Motomichi Matsuzaki Subject: RE: Please test for 8G-OVER-Booting with /boot/loader Cc: FreeBSD-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Mar-00 Motomichi Matsuzaki wrote: > > Hi. > > I made a patch for /sys/boot/i386/libi386/biosdisk.c (attached). > This aimed to enable /boot/loader to manage 8G-OVER-Disks. > > 0. you need 8G-OVER-ENABLED BIOS for your motherboard > (check whether your BIOS has Int 13 Extended Interface) > > 1. teach boot0 using extended BIOS (See boot0cfg(8)) > > # boot0cfg -o packet YOUR-BOOT-DEVICE > > 2. install boot2 which have extended BIOS support > > # cd /sys/boot/i386/boot2; make B1FLAGS=0x80 clean install > > 3. patch to libi386 and install new /boot/loader > > # cd /sys/boot/i386/libi386/; patch # cd /sys/boot/i386/loader; make install Looks good to me, but I need to test it to make sure. I will also look at seeing if I can squeeze the int 13 extension installation check into boot1 and boot0 so that they will use packet mode automatically as well. I'll try and test this out in a day or two. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/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 Mon Mar 27 7: 2:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 4B44337BBA3 for ; Mon, 27 Mar 2000 07:02:38 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.calcaphon.com (henny.calcaphon.com [10.0.0.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id QAA75503; Mon, 27 Mar 2000 16:07:04 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Mon, 27 Mar 2000 16:00:02 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Samuel Tardieu Cc: freebsd-current@freebsd.org Subject: Re: make buildworld fails due to a missing share/man/man4/wst.4 In-Reply-To: <2000-03-27-14-58-33+trackit+sam@inf.enst.fr> 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 Resup. My fault, was corrected within 10 minutes. You must have been unlucky. Nick On Mon, 27 Mar 2000, Samuel Tardieu wrote: > With the current sources. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 7:10: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from veldy.net (veldy-host201.dsl.visi.com [208.42.48.201]) by hub.freebsd.org (Postfix) with ESMTP id 33E8237BC59 for ; Mon, 27 Mar 2000 07:10:05 -0800 (PST) (envelope-from veldy@veldy.net) Received: from 95CTJ (unknown [208.238.139.52]) by veldy.net (Postfix) with SMTP id D5C641918 for ; Mon, 27 Mar 2000 09:13:17 -0600 (CST) Message-ID: <007501bf97fe$5a8f6ea0$dd29680a@tgt.com> From: "Thomas T. Veldhouse" To: Subject: current.freebsd.org again? Date: Mon, 27 Mar 2000 09:08:48 -0600 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.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is going on with that server? It seems to be denying requests more than accepting them these days. [9:08am] 5 [~/FreeBSD]:cascade% ncftp3 current.freebsd.org NcFTP 3.0.0 (March 20, 2000) by Mike Gleason (ncftp@ncftp.com). Copyright (c) 1992-1999 by Mike Gleason. All rights reserved. Connecting to 209.180.6.226... usw2.freebsd.org FTP server (Version wu-2.6.0(1) Tue Jan 25 00:05:38 CST 2000) ready. Login incorrect. Redialing (try 1)... Tom Veldhouse veldy@veldy.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 8:41:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id BA8E237C013 for ; Mon, 27 Mar 2000 08:41:39 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 88FB8180ED; Mon, 27 Mar 2000 18:40:40 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <38DD8526.572973B6@gorean.org> References: <200003260018.KAA07524@shad.internal.en-bio> <38DD8526.572973B6@gorean.org> Date: Mon, 27 Mar 2000 18:13:30 +0200 To: Doug Barton From: Brad Knowles Subject: Re: Accessing FreeBSD 3.4-STABLE filesystems from4.0-STABLE... Cc: Tony Maher , FreeBSD-CURRENT Mailing List Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 7:33 PM -0800 2000/3/25, Doug Barton wrote: > 'fsck -y /dev/da0s1a' I had tried that already, but I'll do it again and let you see what happens: $ fsck -y /dev/da0s1a Can't open /dev/da0s1a: Invalid argument -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 9:13:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id E739237B630 for ; Mon, 27 Mar 2000 09:13:51 -0800 (PST) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id JAA41530; Mon, 27 Mar 2000 09:13:31 -0800 (PST) Date: Mon, 27 Mar 2000 09:13:30 -0800 (PST) From: Julian Elischer To: Brad Knowles Cc: Doug Barton , Tony Maher , FreeBSD-CURRENT Mailing List Subject: Re: Accessing FreeBSD 3.4-STABLE filesystems from4.0-STABLE... 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 in a 4.0 kernel, teh block device doesn't exist, you always use the character device, so it was renamed so that /dev/da0s1a is teh name for the char device but if you are using a device on a 3.4 disk it refers toi the block device (which isn't in a 4.0 kernel) On Mon, 27 Mar 2000, Brad Knowles wrote: > At 7:33 PM -0800 2000/3/25, Doug Barton wrote: > > > 'fsck -y /dev/da0s1a' > > I had tried that already, but I'll do it again and let you see > what happens: > > $ fsck -y /dev/da0s1a > Can't open /dev/da0s1a: Invalid argument > > -- > These are my opinions -- not to be taken as official Skynet policy > ====================================================================== > Brad Knowles, || Belgacom Skynet SA/NV > Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 > Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels > http://www.skynet.be || Belgium > > > 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 Mar 27 9:30:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 60E4B37B569 for ; Mon, 27 Mar 2000 09:30:47 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 9A55018383; Mon, 27 Mar 2000 19:30:22 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Mon, 27 Mar 2000 19:30:08 +0200 To: Julian Elischer From: Brad Knowles Subject: Re: Accessing FreeBSD 3.4-STABLE filesystems from4.0-STABLE... Cc: Doug Barton , Tony Maher , FreeBSD-CURRENT Mailing List Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:13 AM -0800 2000/3/27, Julian Elischer wrote: > in a 4.0 kernel, teh block device doesn't exist, you always use the > character device, > so it was renamed so that /dev/da0s1a is teh name for the char device > but if you are using a device on a 3.4 disk it refers toi the block device > (which isn't in a 4.0 kernel) This is a 4.0-STABLE system: $ cd /dev && ls -la da[01]s1? crw-r----- 1 root operator 13, 0x00020000 Mar 20 09:38 da0s1a crw-r----- 1 root operator 13, 0x00020001 Mar 20 09:38 da0s1b crw-r----- 1 root operator 13, 0x00020002 Mar 20 09:38 da0s1c crw-r----- 1 root operator 13, 0x00020003 Mar 20 09:38 da0s1d crw-r----- 1 root operator 13, 0x00020004 Mar 20 09:38 da0s1e crw-r----- 1 root operator 13, 0x00020005 Mar 20 09:38 da0s1f crw-r----- 1 root operator 13, 0x00020006 Mar 20 09:38 da0s1g crw-r----- 1 root operator 13, 0x00020007 Mar 20 09:38 da0s1h crw-r----- 1 root operator 13, 0x00020008 Mar 18 21:45 da1s1a crw-r----- 1 root operator 13, 0x00020009 Mar 18 21:45 da1s1b crw-r----- 1 root operator 13, 0x0002000a Mar 18 21:45 da1s1c crw-r----- 1 root operator 13, 0x0002000b Mar 18 21:45 da1s1d crw-r----- 1 root operator 13, 0x0002000c Mar 18 21:45 da1s1e crw-r----- 1 root operator 13, 0x0002000d Mar 18 21:45 da1s1f crw-r----- 1 root operator 13, 0x0002000e Mar 23 12:34 da1s1g crw-r----- 1 root operator 13, 0x0002000f Mar 18 21:45 da1s1h This is a different 3.2-RELEASE system: $ cd /dev && ls -la da[01]s1? brw-r----- 1 root operator 4, 0x00020009 Jul 7 1999 da1s1b brw-r----- 1 root operator 4, 0x0002000c Jul 28 1999 da1s1e brw-r----- 1 root operator 4, 0x0002000d Jul 29 1999 da1s1f It seems to me like I've got the correct character devices created under 4.0-STABLE, and yet there still isn't a valid filesystem that fsck can find on /dev/da0s1a, which I know to be false because I can reboot the machine and bring it up in 3.4-STABLE on that disk. So, I'll repeat the question -- what do I have to do in order to get 3.4-STABLE disks readable under 4.0-STABLE, and/or 4.0-STABLE disks readable under 3.4-STABLE? -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 9:32: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 6DE0C37BB18 for ; Mon, 27 Mar 2000 09:31:58 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA41585; Mon, 27 Mar 2000 09:31:54 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Mar 2000 09:31:54 -0800 (PST) From: Matthew Dillon Message-Id: <200003271731.JAA41585@apollo.backplane.com> To: Daniel Eischen Cc: nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> *not* preempted except when being interrupted, so there are no :> 'priorities', per say. Or, rather, the relative priority is strictly :> that the interrupt takes priority over supervisor code except when :> disabled by said supervisor code. : :But locks with owners wouldn't have to disable interrupts (given that :we have interrupt threads). What about shared interrupts? You could :still field and process the interrupt as long as it was for a different :device. :Dan Eischen The word 'too bad' comes to mind re: shared interrupts. That is, while it would be nice to support concurrent operation in that case, the current model can't, and the customer can simply rearrange his PCI cards if two high-volume devices wind up on the same interrupt to get around the limitation. So making this work would be a very low priority relative to other bullets. -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 Mar 27 9:47: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id 334DF37B625 for ; Mon, 27 Mar 2000 09:46:58 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id KAA06008; Mon, 27 Mar 2000 10:46:08 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id KAA26582; Mon, 27 Mar 2000 10:46:08 -0700 (MST) (envelope-from nate) Date: Mon, 27 Mar 2000 10:46:08 -0700 (MST) Message-Id: <200003271746.KAA26582@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Matthew Dillon Cc: Daniel Eischen , nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? In-Reply-To: <200003271731.JAA41585@apollo.backplane.com> References: <200003271731.JAA41585@apollo.backplane.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :> *not* preempted except when being interrupted, so there are no > :> 'priorities', per say. Or, rather, the relative priority is strictly > :> that the interrupt takes priority over supervisor code except when > :> disabled by said supervisor code. > : > :But locks with owners wouldn't have to disable interrupts (given that > :we have interrupt threads). What about shared interrupts? You could > :still field and process the interrupt as long as it was for a different > :device. > :Dan Eischen > > The word 'too bad' comes to mind re: shared interrupts. Too bad is not acceptable. If we want to support multi-function PCMCIA/CardBus cards, we *must* do shared interrupts, and multi-function cards are becoming the standard, rather than the exception. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 9:53:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3169437B676 for ; Mon, 27 Mar 2000 09:53:22 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA41782; Mon, 27 Mar 2000 09:53:18 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Mar 2000 09:53:18 -0800 (PST) From: Matthew Dillon Message-Id: <200003271753.JAA41782@apollo.backplane.com> To: Nate Williams Cc: Daniel Eischen , nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? References: <200003271731.JAA41585@apollo.backplane.com> <200003271746.KAA26582@nomad.yogotech.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> :> *not* preempted except when being interrupted, so there are no :> :> 'priorities', per say. Or, rather, the relative priority is strictly :> :> that the interrupt takes priority over supervisor code except when :> :> disabled by said supervisor code. :> : :> :But locks with owners wouldn't have to disable interrupts (given that :> :we have interrupt threads). What about shared interrupts? You could :> :still field and process the interrupt as long as it was for a different :> :device. :> :Dan Eischen :> :> The word 'too bad' comes to mind re: shared interrupts. : :Too bad is not acceptable. If we want to support multi-function :PCMCIA/CardBus cards, we *must* do shared interrupts, and multi-function :cards are becoming the standard, rather than the exception. : :Nate First, each PCI slot has *two* assignable interrupts. Second, CardBus cards are so slow that you would see absolutely no gain in performance whatsoever by being able to run concurrent interrupt threads for a single shared interrupt. So, frankly, it is perfectly acceptable. I can't think of a single real-life setup that would sufffer. -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 Mar 27 9:56:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id 5BD2037B80A for ; Mon, 27 Mar 2000 09:56:12 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id KAA06106; Mon, 27 Mar 2000 10:55:57 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id KAA26648; Mon, 27 Mar 2000 10:55:57 -0700 (MST) (envelope-from nate) Date: Mon, 27 Mar 2000 10:55:57 -0700 (MST) Message-Id: <200003271755.KAA26648@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Matthew Dillon Cc: Nate Williams , Daniel Eischen , nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? In-Reply-To: <200003271753.JAA41782@apollo.backplane.com> References: <200003271731.JAA41585@apollo.backplane.com> <200003271746.KAA26582@nomad.yogotech.com> <200003271753.JAA41782@apollo.backplane.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :> :> *not* preempted except when being interrupted, so there are no > :> :> 'priorities', per say. Or, rather, the relative priority is strictly > :> :> that the interrupt takes priority over supervisor code except when > :> :> disabled by said supervisor code. > :> : > :> :But locks with owners wouldn't have to disable interrupts (given that > :> :we have interrupt threads). What about shared interrupts? You could > :> :still field and process the interrupt as long as it was for a different > :> :device. > :> :Dan Eischen > :> > :> The word 'too bad' comes to mind re: shared interrupts. > : > :Too bad is not acceptable. If we want to support multi-function > :PCMCIA/CardBus cards, we *must* do shared interrupts, and multi-function > :cards are becoming the standard, rather than the exception. > : > :Nate > > First, each PCI slot has *two* assignable interrupts. > > Second, CardBus cards are so slow that you would see absolutely no > gain in performance whatsoever by being able to run concurrent interrupt > threads for a single shared interrupt. Huh? CardBus cards are *not* slow. PCMCIA cards are, but CardBus is pretty dang fast. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 10:23: 7 2000 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 6C80537BD2C for ; Mon, 27 Mar 2000 10:23:02 -0800 (PST) (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 LAA54902; Mon, 27 Mar 2000 11:22:58 -0700 (MST) (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 LAA94849; Mon, 27 Mar 2000 11:22:42 -0700 (MST) Message-Id: <200003271822.LAA94849@harmony.village.org> To: Sheldon Hearn Subject: Re: questions asked in CURRENT, answered in UPDATING Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 27 Mar 2000 14:01:53 +0200." <54598.954158513@axl.ops.uunet.co.za> References: <54598.954158513@axl.ops.uunet.co.za> Date: Mon, 27 Mar 2000 11:22:42 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <54598.954158513@axl.ops.uunet.co.za> Sheldon Hearn writes: : I'd like to propose that everyone confine such answers to private mail. No. I'm going to continue to do it publicly. : 1) Folks who _do_ read UPDATING aren't further inconvenienced by : multiple "see UPDATING" replies. 'd' works well :-). I keep the messages short, and to the point. : 2) Instead, the folks who didn't read UPDATING suffer this : inconvenience. It's an excellent learning opportunity for these : people, since multiple "see UPDATING" replies are likely to help them : remember for next time. This would be true a higher percentage of people were actually reading UPDATING before posting. Seeing a simple "See UPDATING: XXXX" keeps the file in the public eye and thus encourages people to look there and let me know when things are wrong. It also tends to self regulate the UPDATING usage. As usage falls, more messages are likely to appear on the list, to which the see updating replies happen, which causes usage to rise again. : This is akin to jmb's preference for allowing misdirected subscribe : and unsubscribe requests onto the list. ;-) : : You like? Yes? No? I don't like. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 10:23:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id A8BF437B52B for ; Mon, 27 Mar 2000 10:23:28 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id NAA07181; Mon, 27 Mar 2000 13:23:15 -0500 (EST) Date: Mon, 27 Mar 2000 13:23:15 -0500 (EST) From: Daniel Eischen To: Matthew Dillon Cc: Nate Williams , nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? In-Reply-To: <200003271753.JAA41782@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, 27 Mar 2000, Matthew Dillon wrote: > > : > :> :> *not* preempted except when being interrupted, so there are no > :> :> 'priorities', per say. Or, rather, the relative priority is strictly > :> :> that the interrupt takes priority over supervisor code except when > :> :> disabled by said supervisor code. > :> : > :> :But locks with owners wouldn't have to disable interrupts (given that > :> :we have interrupt threads). What about shared interrupts? You could > :> :still field and process the interrupt as long as it was for a different > :> :device. > :> :Dan Eischen > :> > :> The word 'too bad' comes to mind re: shared interrupts. > : > :Too bad is not acceptable. If we want to support multi-function > :PCMCIA/CardBus cards, we *must* do shared interrupts, and multi-function > :cards are becoming the standard, rather than the exception. > : > :Nate > > First, each PCI slot has *two* assignable interrupts. > > Second, CardBus cards are so slow that you would see absolutely no > gain in performance whatsoever by being able to run concurrent interrupt > threads for a single shared interrupt. > > So, frankly, it is perfectly acceptable. I can't think of a single > real-life setup that would sufffer. And would there still be areas of the kernel that disable multiple interrupts, perhaps CAM or the network stack for instance? What do all the splbio and splnet calls translate into in this new scheme? -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 10:24:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 251C437BFE7 for ; Mon, 27 Mar 2000 10:24:55 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id D02DF181EA; Mon, 27 Mar 2000 20:24:51 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200003271753.JAA41782@apollo.backplane.com> References: <200003271731.JAA41585@apollo.backplane.com> <200003271746.KAA26582@nomad.yogotech.com> <200003271753.JAA41782@apollo.backplane.com> Date: Mon, 27 Mar 2000 20:24:20 +0200 To: Matthew Dillon , Nate Williams From: Brad Knowles Subject: Re: Is there spinlocks/semaphores available for drivers? Cc: Daniel Eischen , nms@otdel-1.org, freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:53 AM -0800 2000/3/27, Matthew Dillon wrote: > So, frankly, it is perfectly acceptable. I can't think of a single > real-life setup that would sufffer. What about things like Adaptec 3940U2W controllers that have two SCSI interfaces, and by default I believe will want shared interrupts? Or controllers that have more then two interfaces? Or have I missed something fundamental here and this is not what you're talking about? -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 10:26:10 2000 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 EA27437B60F for ; Mon, 27 Mar 2000 10:26:04 -0800 (PST) (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 LAA54914; Mon, 27 Mar 2000 11:26:03 -0700 (MST) (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 LAA94872; Mon, 27 Mar 2000 11:25:46 -0700 (MST) Message-Id: <200003271825.LAA94872@harmony.village.org> To: nate@yogotech.com (Nate Williams) Subject: Re: Is there spinlocks/semaphores available for drivers? Cc: Matthew Dillon , Daniel Eischen , nms@otdel-1.org, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 27 Mar 2000 10:46:08 MST." <200003271746.KAA26582@nomad.yogotech.com> References: <200003271746.KAA26582@nomad.yogotech.com> <200003271731.JAA41585@apollo.backplane.com> Date: Mon, 27 Mar 2000 11:25:46 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003271746.KAA26582@nomad.yogotech.com> Nate Williams writes: : Too bad is not acceptable. If we want to support multi-function : PCMCIA/CardBus cards, we *must* do shared interrupts, and multi-function : cards are becoming the standard, rather than the exception. Too bad is acceptible in this context. Meaning that we can still support sharing the interrupt, but it might lock more of the kernel out than if you didn't share. That's not a big deal in the near term. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 10:27:16 2000 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 B71D437C0D8 for ; Mon, 27 Mar 2000 10:27:13 -0800 (PST) (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 LAA54920; Mon, 27 Mar 2000 11:27:09 -0700 (MST) (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 LAA94885; Mon, 27 Mar 2000 11:26:52 -0700 (MST) Message-Id: <200003271826.LAA94885@harmony.village.org> To: nate@yogotech.com (Nate Williams) Subject: Re: Is there spinlocks/semaphores available for drivers? Cc: Matthew Dillon , Daniel Eischen , nms@otdel-1.org, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 27 Mar 2000 10:55:57 MST." <200003271755.KAA26648@nomad.yogotech.com> References: <200003271755.KAA26648@nomad.yogotech.com> <200003271731.JAA41585@apollo.backplane.com> <200003271746.KAA26582@nomad.yogotech.com> <200003271753.JAA41782@apollo.backplane.com> Date: Mon, 27 Mar 2000 11:26:52 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003271755.KAA26648@nomad.yogotech.com> Nate Williams writes: : Huh? CardBus cards are *not* slow. PCMCIA cards are, but CardBus is : pretty dang fast. The consequence of Matt's position is that cardbus cards won't be able to be in their interrupt handlers at the same time. This will have a small impact on performance, but the cards will still work. Unless I'm misunderstanding Matt's position. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 11: 2: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4CDEB37BCF5 for ; Mon, 27 Mar 2000 11:01:57 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA42391; Mon, 27 Mar 2000 11:01:54 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Mar 2000 11:01:54 -0800 (PST) From: Matthew Dillon Message-Id: <200003271901.LAA42391@apollo.backplane.com> To: Daniel Eischen Cc: Nate Williams , nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :And would there still be areas of the kernel that disable multiple :interrupts, perhaps CAM or the network stack for instance? What do :all the splbio and splnet calls translate into in this new scheme? : :-- :Dan Eischen The entire design of the kernel is currently predicated on the spl*() mechanism. We obviously can't rip it out in a day. I'm guessing it will probably take two years ... or never if we can eek out sufficient performance with it still in place. I think there is a good chance we can reap the performance benefits without ripping the spl*() API to shreads, even if we have to rewrite the cpl mechanism that runs the show under the hood. The system most likely to be rewritten to avoid spl*() (under normal operation) is the network subsystem. That alone will give us a big boost. Network subsystem easy Disk subsystem hard VM subsystem really hard I outline how the current cpl mechanism can be used almost verbatim in an interrupt-thread environment in my SMP document, under 'interrupt sequencing'. http://www.backplane.com/FreeBSD4/smp-api.html -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 Mar 27 11: 4:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id CA0A137C0A9 for ; Mon, 27 Mar 2000 11:04:41 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id MAA06754; Mon, 27 Mar 2000 12:04:24 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id MAA27402; Mon, 27 Mar 2000 12:04:15 -0700 (MST) (envelope-from nate) Date: Mon, 27 Mar 2000 12:04:15 -0700 (MST) Message-Id: <200003271904.MAA27402@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Matthew Dillon Cc: Daniel Eischen , Nate Williams , nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? In-Reply-To: <200003271901.LAA42391@apollo.backplane.com> References: <200003271901.LAA42391@apollo.backplane.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :And would there still be areas of the kernel that disable multiple > :interrupts, perhaps CAM or the network stack for instance? What do > :all the splbio and splnet calls translate into in this new scheme? > : > > The entire design of the kernel is currently predicated on the spl*() > mechanism. We obviously can't rip it out in a day. I'm guessing it > will probably take two years ... or never if we can eek out sufficient > performance with it still in place. It is my (probably naive) understanding that BSDi has done a bunch of work in this area, and that we should be able to leverage alot of their work. Having never seen it, I (bogusly?) assume they aren't using spl*() anymore, given that they now have kernel threads. Does anyone know more? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 11:31:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 9B10E37BAC1 for ; Mon, 27 Mar 2000 11:31:33 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id OAA17664; Mon, 27 Mar 2000 14:31:18 -0500 (EST) Date: Mon, 27 Mar 2000 14:31:18 -0500 (EST) From: Daniel Eischen To: Matthew Dillon Cc: Nate Williams , nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? In-Reply-To: <200003271901.LAA42391@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, 27 Mar 2000, Matthew Dillon wrote: > :And would there still be areas of the kernel that disable multiple > :interrupts, perhaps CAM or the network stack for instance? What do > :all the splbio and splnet calls translate into in this new scheme? > : > :-- > :Dan Eischen > > The entire design of the kernel is currently predicated on the spl*() > mechanism. We obviously can't rip it out in a day. I'm guessing it > will probably take two years ... or never if we can eek out sufficient > performance with it still in place. There's a paper that describes how Solaris transitioned from spl()s to mutexes. ISTR they created one mutex for each splxxx. I'll have to find this and re-read it. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 11:32: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id 441AE37BAC1; Mon, 27 Mar 2000 11:31:57 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca6-109.ix.netcom.com [205.186.213.109]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id OAA05819; Mon, 27 Mar 2000 14:31:53 -0500 (EST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id LAA41525; Mon, 27 Mar 2000 11:31:51 -0800 (PST) To: "R. Imura" Cc: nsayer@freebsd.org, will@freebsd.org, freebsd-ports@freebsd.org, freebsd-current@freebsd.org Subject: Re: KDE kdm problem with packaged version (make release issue?) References: <20000323213103K.imura@cs.titech.ac.jp> <20000325170406U.imura@cs.titech.ac.jp> <20000325170618R.imura@cs.titech.ac.jp> From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Date: 27 Mar 2000 11:31:46 -0800 In-Reply-To: "R. Imura"'s message of "Sat, 25 Mar 2000 17:06:18 +0900" Message-ID: Lines: 10 X-Mailer: Gnus v5.7/Emacs 20.6 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "R. Imura" * > kdm determines X path as 'test -f $PATH/bin/X', so touching X is enough. * ^^^^^^^^^^^ $PATH/X Well, I don't want to add a dysfunctional file in the tarball (what if some port does a "test -x X"?) so I just added X and the default destination of the link (XF86_SVGA). Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 12: 1: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (Postfix) with ESMTP id DC0D737BAC1 for ; Mon, 27 Mar 2000 12:00:56 -0800 (PST) (envelope-from kent@lab1.tfd.com) Received: from lab1.tfd.com (lab1.tfd.com [10.9.200.31]) by rtp.tfd.com (8.9.3/8.9.3) with SMTP id PAA29252 for ; Mon, 27 Mar 2000 15:01:29 -0500 (EST) Received: by lab1.tfd.com id AA00215 (5.67b/IDA-1.5 for freebsd-current@freebsd.org); Mon, 27 Mar 2000 14:58:59 -0500 Date: Mon, 27 Mar 2000 14:58:59 -0500 From: Kent Hauser Message-Id: <200003271958.AA00215@lab1.tfd.com> To: freebsd-current@freebsd.org Subject: 3C589C interrupt problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just moved my laptop (Thinkpad 600E) from 3.2->5.0-CURRENT. Everything is great *except* the ethernet link is not working correctly. If I set the interrupt to `?' (as in pccard.conf.sample) or 10 (as worked under 3.2) the probe fails "no int?!". If I set it to 11, then the probe works, "netstat -r" works (implying DNS works, albeit slowly), but "telnet ipaddr" doesn't. Pings take "60000" msec. Any comments/suggestions? Thanks. Kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 12: 2:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (peter1.yahoo.com [208.48.107.4]) by hub.freebsd.org (Postfix) with ESMTP id BC2F637BA42 for ; Mon, 27 Mar 2000 12:02:18 -0800 (PST) (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 8B8C21CD9; Mon, 27 Mar 2000 12:02:07 -0800 (PST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: Greg Lehey , Brad Knowles , FreeBSD-CURRENT Mailing List Subject: Re: INVARIANTS doesn't work? In-Reply-To: Message from Matthew Dillon of "Fri, 24 Mar 2000 10:02:46 PST." <200003241802.KAA14776@apollo.backplane.com> Date: Mon, 27 Mar 2000 12:02:07 -0800 From: Peter Wemm Message-Id: <20000327200207.8B8C21CD9@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :Is there any good reason why we have two different options if they can > :only be used together? > : > :Greg > > I think it's so you can compile a kernel with INVARIANT_SUPPORT in > in order to support dynamic load modules which may have been compiled > with INVARIANTS. Or so that you can compile individual files with INVARIANTS by whatever means suits your needs. I'm aware of quite a few machines that run with #define INVARIANTS 1 near the top of kern_malloc.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 Mon Mar 27 12: 8:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2D78237B768 for ; Mon, 27 Mar 2000 12:08:37 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA42799; Mon, 27 Mar 2000 12:08:33 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Mar 2000 12:08:33 -0800 (PST) From: Matthew Dillon Message-Id: <200003272008.MAA42799@apollo.backplane.com> To: Daniel Eischen Cc: Nate Williams , nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :There's a paper that describes how Solaris transitioned from spl()s :to mutexes. ISTR they created one mutex for each splxxx. I'll have :to find this and re-read it. : :-- :Dan Eischen I think we're using a slightly different mechanism... our spl*()'s are actually interrupt bit masks. That is, any single spl*() call may mask several interrupt sources. Turning a mask with five or six bits set in it into a set of mutexes is a very expensive proposition. -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 Mar 27 13: 4:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id E500637BE6A for ; Mon, 27 Mar 2000 13:04:41 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12Zgga-000FR3-00; Mon, 27 Mar 2000 23:04:32 +0200 From: Sheldon Hearn To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: questions asked in CURRENT, answered in UPDATING In-reply-to: Your message of "Mon, 27 Mar 2000 11:22:42 MST." <200003271822.LAA94849@harmony.village.org> Date: Mon, 27 Mar 2000 23:04:32 +0200 Message-ID: <59335.954191072@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Mar 2000 11:22:42 MST, Warner Losh wrote: > It also tends to self regulate the UPDATING usage. As usage falls, > more messages are likely to appear on the list, to which the see > updating replies happen, which causes usage to rise again. Two good arguments. Idea sumamrily dismissed. :-) 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 Mar 27 13:30:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 11EC737BCE5 for ; Mon, 27 Mar 2000 13:30:24 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2RLsFT08784; Mon, 27 Mar 2000 13:54:15 -0800 (PST) Date: Mon, 27 Mar 2000 13:54:15 -0800 From: Alfred Perlstein To: Matthew Dillon Cc: Daniel Eischen , Nate Williams , nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? Message-ID: <20000327135414.M21029@fw.wintelcom.net> References: <200003272008.MAA42799@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003272008.MAA42799@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Mar 27, 2000 at 12:08:33PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Dillon [000327 12:36] wrote: > > : > :There's a paper that describes how Solaris transitioned from spl()s > :to mutexes. ISTR they created one mutex for each splxxx. I'll have > :to find this and re-read it. > : > :-- > :Dan Eischen > > I think we're using a slightly different mechanism... our spl*()'s > are actually interrupt bit masks. That is, any single spl*() call > may mask several interrupt sources. Turning a mask with five or six > bits set in it into a set of mutexes is a very expensive proposition. I think you're thinking this: /-----int 1 spl -<---> int 2 \-----int 3 spl messing with several mutexes, instead consider: int 1 >---\ int 2 >---->-- splmutex int 3 >---/ Where a single mutex is shared by several interrupts. There's also this to consider: proc0: splaaa(); splbbb(); proc1: splbbb(); splaaa(); deadlock. Which needs to be worked out somehow. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@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 Mar 27 13:32:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.wrs.com (unknown-1-11.wrs.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id BB1F837BDBA for ; Mon, 27 Mar 2000 13:32:16 -0800 (PST) (envelope-from davidhol@windriver.com) Received: from papermill.wrs.com (papermill [147.11.48.34]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id NAA10820; Mon, 27 Mar 2000 13:32:05 -0800 (PST) Received: from papermill (localhost [127.0.0.1]) by papermill.wrs.com (8.9.1/8.9.0) with ESMTP id NAA09524; Mon, 27 Mar 2000 13:32:14 -0800 (PST) Message-Id: <200003272132.NAA09524@papermill.wrs.com> To: Brad Knowles Cc: Daniel Eischen , nms@otdel-1.org, freebsd-current@FreeBSD.ORG From: David Holloway Subject: Re: Is there spinlocks/semaphores available for drivers? In-reply-to: Your message of "Mon, 27 Mar 2000 20:24:20 +0200." Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Mon, 27 Mar 2000 13:32:14 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The 3940U2W has two pci devices. One for each scsi interface. Each interface uses a separate pci interrupt. One uses INTA the other probably uses INTB and which irq they uses depends on your motherboard. In message , Brad Knowles writes: >At 9:53 AM -0800 2000/3/27, Matthew Dillon wrote: > >> So, frankly, it is perfectly acceptable. I can't think of a single >> real-life setup that would sufffer. > > What about things like Adaptec 3940U2W controllers that have two >SCSI interfaces, and by default I believe will want shared >interrupts? Or controllers that have more then two interfaces? > > Or have I missed something fundamental here and this is not what >you're talking about? > >-- > These are my opinions -- not to be taken as official Skynet policy >====================================================================== >Brad Knowles, || Belgacom Skynet SA/NV >Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 >Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels >http://www.skynet.be || Belgium > > >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 Mar 27 13:44:48 2000 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 A8A8A37B6F7 for ; Mon, 27 Mar 2000 13:44:45 -0800 (PST) (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 OAA55753; Mon, 27 Mar 2000 14:44:44 -0700 (MST) (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 OAA00265; Mon, 27 Mar 2000 14:44:27 -0700 (MST) Message-Id: <200003272144.OAA00265@harmony.village.org> To: Kent Hauser Subject: Re: 3C589C interrupt problem Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 27 Mar 2000 14:58:59 EST." <200003271958.AA00215@lab1.tfd.com> References: <200003271958.AA00215@lab1.tfd.com> Date: Mon, 27 Mar 2000 14:44:27 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003271958.AA00215@lab1.tfd.com> Kent Hauser writes: : I just moved my laptop (Thinkpad 600E) from 3.2->5.0-CURRENT. : Everything is great *except* the ethernet link is not working : correctly. If I set the interrupt to `?' (as in pccard.conf.sample) : or 10 (as worked under 3.2) the probe fails "no int?!". If I : set it to 11, then the probe works, "netstat -r" works (implying : DNS works, albeit slowly), but "telnet ipaddr" doesn't. : Pings take "60000" msec. dmesg output? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 13:47:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 5554537BBEA for ; Mon, 27 Mar 2000 13:47:10 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA43734; Mon, 27 Mar 2000 13:47:09 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Mar 2000 13:47:09 -0800 (PST) From: Matthew Dillon Message-Id: <200003272147.NAA43734@apollo.backplane.com> To: Alfred Perlstein Cc: Daniel Eischen , Nate Williams , nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? References: <200003272008.MAA42799@apollo.backplane.com> <20000327135414.M21029@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I think you're thinking this: : : /-----int 1 :spl -<---> int 2 : \-----int 3 : :spl messing with several mutexes, instead consider: : :int 1 >---\ :int 2 >---->-- splmutex :int 3 >---/ Problem #1: Different spl levels use different combinations of interrupts. Some interrupts belong to several spl sets. Problem #2: Mutexes that you compete for on a regular basis cost cpu cycles to own. Combining spl bits into a smaller set of mutexes will exasperate this problem -- it will almost be as if we had a BGL. :Where a single mutex is shared by several interrupts. : :There's also this to consider: : :proc0: splaaa(); splbbb(); :proc1: splbbb(); splaaa(); : :deadlock. Which needs to be worked out somehow. : :-- :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Yes, which is one of the many reasons why all current spl() manipualtion must be done while holding the BGL. I think the best way to approach solving the spl problem is to not attempt to migrate the spl interface. Instead we slowly replace it in a piecemeal fashion. It would work like this: Any existing code using the spl API *MUST* hold the BGL. In order to remove the BGL requirement the code, amoung other things, must migrate to the 'new' mutex interface (or whatever API we come up with). Both the old and the new interfaces would be able to work in tandem. This way we split the problem into multiple pieces rather then attempt to shoehorn the existing SPL mechanism into the ultimate SMP solution (instead it becomes only an interim solution, but one that can be 'mixed' with whatever the real solution winds up being). This allows us to solve the problem in a piecemeal fashion and reduces the chance of breaking the code base in a nasty fashion. -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 Mar 27 13:57:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (pyramid.cdrom.com [204.216.28.136]) by hub.freebsd.org (Postfix) with ESMTP id AD5F537BAE9 for ; Mon, 27 Mar 2000 13:57:53 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA00995; Mon, 27 Mar 2000 14:00:20 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003272200.OAA00995@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nate@yogotech.com (Nate Williams) Cc: Matthew Dillon , Daniel Eischen , nms@otdel-1.org, freebsd-current@FreeBSD.ORG Subject: Re: Is there spinlocks/semaphores available for drivers? In-reply-to: Your message of "Mon, 27 Mar 2000 10:55:57 MST." <200003271755.KAA26648@nomad.yogotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Mar 2000 14:00:20 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > :> The word 'too bad' comes to mind re: shared interrupts. > > : > > :Too bad is not acceptable. If we want to support multi-function > > :PCMCIA/CardBus cards, we *must* do shared interrupts, and multi-function > > :cards are becoming the standard, rather than the exception. > > > > First, each PCI slot has *two* assignable interrupts. Four, actually, although the typical routing setup reduces their effectiveness. > > Second, CardBus cards are so slow that you would see absolutely no > > gain in performance whatsoever by being able to run concurrent interrupt > > threads for a single shared interrupt. > > Huh? CardBus cards are *not* slow. PCMCIA cards are, but CardBus is > pretty dang fast. I think you're at cross purposes here. Matt's point is that you wouldn't be able to run interrupt handler threads for more than one device on a shared interrupt at a time, not that you would never be able to support shared interrupts. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Mon Mar 27 14:28:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from bartman.ic.sunysb.edu (bartman.ic.sunysb.edu [129.49.1.4]) by hub.freebsd.org (Postfix) with ESMTP id 96E5437B9CE for ; Mon, 27 Mar 2000 14:28:28 -0800 (PST) (envelope-from thsiang@ic.sunysb.edu) Received: from sparky.ic.sunysb.edu (thsiang@sparky.ic.sunysb.edu [129.49.1.3]) by bartman.ic.sunysb.edu (8.9.3/8.9.3) with ESMTP id RAA26174 for ; Mon, 27 Mar 2000 17:28:25 -0500 (EST) Received: from localhost (thsiang@localhost) by sparky.ic.sunysb.edu (8.9.3/8.9.1) with ESMTP id RAA04312 for ; Mon, 27 Mar 2000 17:28:23 -0500 (EST) X-Authentication-Warning: sparky.ic.sunysb.edu: thsiang owned process doing -bs Date: Mon, 27 Mar 2000 17:28:23 -0500 (EST) From: "T. Hsiang" To: current@freebsd.org Subject: buildworld failure 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 Any idea? ----------------- INET6 -I/usr/obj/usr/src/i386/usr/include -c policy_token.c -o policy_token.So cc -fpic -DPIC -O -pipe -I/usr/obj/usr/src/lib/libipsec -DIPSEC_DEBUG -DIPSEC -D INET6 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libipsec/ipsec_dump_po licy.c -o ipsec_dump_policy.So cc -fpic -DPIC -O -pipe -I/usr/obj/usr/src/lib/libipsec -DIPSEC_DEBUG -DIPSEC -D INET6 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libipsec/ipsec_get_pol icylen.c -o ipsec_get_policylen.So cc -fpic -DPIC -O -pipe -I/usr/obj/usr/src/lib/libipsec -DIPSEC_DEBUG -DIPSEC -D INET6 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libipsec/../../sys/net key/key_debug.c -o key_debug.So make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libl.a. Stop *** Error code 2 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 16:52:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id DC88137B596 for ; Mon, 27 Mar 2000 16:52:35 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id JAA29009; Tue, 28 Mar 2000 09:52:30 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id JAA26146; Tue, 28 Mar 2000 09:52:29 +0900 (JST) Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id JAA21175; Tue, 28 Mar 2000 09:52:29 +0900 (JST) To: thsiang@ic.sunysb.edu Cc: current@FreeBSD.ORG Subject: Re: buildworld failure In-Reply-To: References: X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000328095329W.shin@nd.net.fujitsu.co.jp> Date: Tue, 28 Mar 2000 09:53:29 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 31 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Any idea? > > ----------------- > INET6 -I/usr/obj/usr/src/i386/usr/include -c policy_token.c -o > policy_token.So > cc -fpic -DPIC -O -pipe -I/usr/obj/usr/src/lib/libipsec -DIPSEC_DEBUG > -DIPSEC -D > INET6 -I/usr/obj/usr/src/i386/usr/include -c > /usr/src/lib/libipsec/ipsec_dump_po > licy.c -o ipsec_dump_policy.So > cc -fpic -DPIC -O -pipe -I/usr/obj/usr/src/lib/libipsec -DIPSEC_DEBUG > -DIPSEC -D > INET6 -I/usr/obj/usr/src/i386/usr/include -c > /usr/src/lib/libipsec/ipsec_get_pol > icylen.c -o ipsec_get_policylen.So > cc -fpic -DPIC -O -pipe -I/usr/obj/usr/src/lib/libipsec -DIPSEC_DEBUG > -DIPSEC -D > INET6 -I/usr/obj/usr/src/i386/usr/include -c > /usr/src/lib/libipsec/../../sys/net > key/key_debug.c -o key_debug.So > make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libl.a. Stop > *** Error code 2 What is your src/lib/libipsec/Makefile version? It might have been fixed by recent commit from bde which adds define of DPADD. (Sorry I can't check it by myself now, because I can't update my local source from repository from yesterday, due to several issues.) Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 21: 4:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 05CAA37B5A9 for ; Mon, 27 Mar 2000 21:04:43 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA46615; Mon, 27 Mar 2000 21:04:42 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Mar 2000 21:04:42 -0800 (PST) From: Matthew Dillon Message-Id: <200003280504.VAA46615@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: SMP patch going into -current tonight Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The SMP patch (#7) will be going into -current tonight with Jordan's approval. After I make minor corrections to the patch (which is actually based off of 4.x). I'm pretty comfortable with it in -current and think in a week or two we can MFC it into 4.x, which will allow more of the continuing BGL work to (eventually) go into both trees. Specifically, it sure would be nice if some of the syscall work that occurs in the future can be MFC'd. The patch at least doesn't make things any slower - Bob Bishop did a buildworld test and came up with a 7% improvement. I'm a bit skeptical, I only thought it would be 1 or 2%, but perhaps the removal of the 'cpl' locks (which make spl*() calls very expensive) made up for it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 21:21:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from nakaji.tutrp.tut.ac.jp (nakaji.tutrp.tut.ac.jp [133.15.188.118]) by hub.freebsd.org (Postfix) with ESMTP id 4198137BD56 for ; Mon, 27 Mar 2000 21:21:44 -0800 (PST) (envelope-from nakaji@tutrp.tut.ac.jp) Received: from nakaji.tutrp.tut.ac.jp (localhost.tutrp.tut.ac.jp [127.0.0.1]) by nakaji.tutrp.tut.ac.jp (8.9.3/3.7W) with ESMTP id OAA53583 for ; Tue, 28 Mar 2000 14:21:37 +0900 (JST) To: current@FreeBSD.ORG Subject: Re: Please test for 8G-OVER-Booting with /boot/loader MIME-Version: 1.0 (generated by REMI 1.14.1 - =?ISO-8859-4?Q?=22Mushigawa=F2?= =?ISO-8859-4?Q?sugi=22?=) Content-Type: text/plain; charset=US-ASCII From: NAKAJI Hiroyuki Date: 28 Mar 2000 14:21:36 +0900 Message-ID: <87n1njbrfj.fsf@nakaji.tutrp.tut.ac.jp> Lines: 11 User-Agent: T-gnus/6.14.1 (based on Gnus v5.8.3) (revision 16) REMI/1.14.1 (=?ISO-8859-4?Q?Mushigawa=F2sugi?=) FLIM/1.13.2 (Kasanui) APEL/10.2 Emacs/20.6 (i386--freebsd) MULE/4.0 (HANANOEN) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How can I test this with FreeBSD which is installed over-8GB area and can't boot? I have a PC on which Solaris7 is installed within 8GB from the start of disk and FreeBSD 3.3-RELEASE is installed after(?) it. The installation was successfull. But I can't boot it. How can I install this patched /boot/loader in this dead system? -- NAKAJI Hiroyuki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 23:25:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 3AB7D37BA1D for ; Mon, 27 Mar 2000 23:25:31 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 30148 invoked from network); 28 Mar 2000 07:25:26 -0000 Received: from acs-63-85-133-249.cvzoom.net (63.85.133.249) by ns.cvzoom.net with SMTP; 28 Mar 2000 07:25:26 -0000 Date: Tue, 28 Mar 2000 02:25:09 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: getopt and GNU software 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 was wondering if it would be possible to provide a library someplace for the GNU version of getopt()? I've seen a lot of source code in the tree, and whenever a program in /usr/src/{gnu,contrib} needs to link to the GNU version of getopt() and getopt_long(), there were source files provided in that directory for these functions, e.g. getopt1.c and getopt.h. I think it would be easier to build and install a lib in /usr/lib for some of the frequently used GNU functions. We could call it /usr/lib/libcontrib.a or libgnucompat.a, or something like that. The reason I'm asking is that I'm seeing a lot of GNU software that needs to use GNU's getopt() and getopt_long(). I think it's a lot cleaner than just putting getopt*.[ch] in every contrib or gnu directory that needs it. The app that needs these functions can then link to libgnucompat.a. We could also provide a header file someplace that provides these functions, e.g. or . Well, it's not that big of a deal, but there is a certain percentage of GNU software that requires some GNU library functions. Comments? - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 23:34:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from cip12.melaten.rwth-aachen.de (cip12.melaten.RWTH-Aachen.DE [134.130.92.12]) by hub.freebsd.org (Postfix) with ESMTP id 9378437BBBB for ; Mon, 27 Mar 2000 23:34:08 -0800 (PST) (envelope-from tg@melaten.rwth-aachen.de) Received: (from tg@localhost) by cip12.melaten.rwth-aachen.de (8.9.3/8.9.3) id JAA01956; Tue, 28 Mar 2000 09:38:04 +0200 (CEST) (envelope-from tg@melaten.rwth-aachen.de) X-Authentication-Warning: cip12.melaten.rwth-aachen.de: tg set sender to tg@melaten.rwth-aachen.de using -f To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: getopt and GNU software References: From: Thomas Gellekum In-Reply-To: Donn Miller's message of "Tue, 28 Mar 2000 02:25:09 -0500 (EST)" Date: 28 Mar 2000 09:38:04 +0200 Message-ID: Lines: 8 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donn Miller writes: > I was wondering if it would be possible to provide a library someplace for > the GNU version of getopt()? /usr/ports/devel/libgnugetopt. tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 27 23:41:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 1271437BD06 for ; Mon, 27 Mar 2000 23:41:32 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 1323 invoked from network); 28 Mar 2000 07:41:28 -0000 Received: from acs-63-85-133-249.cvzoom.net (HELO cvzoom.net) (63.85.133.249) by ns.cvzoom.net with SMTP; 28 Mar 2000 07:41:28 -0000 Message-ID: <38E06216.9FCF1F0B@cvzoom.net> Date: Tue, 28 Mar 2000 02:41:10 -0500 From: Donn Miller X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Thomas Gellekum Cc: current@FreeBSD.ORG Subject: Re: getopt and GNU software References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Gellekum wrote: > Donn Miller writes: > > > I was wondering if it would be possible to provide a library someplace for > > the GNU version of getopt()? > > /usr/ports/devel/libgnugetopt. Thanks Thomas. I wasn't aware that the port existed. Yes, I had problems compiling gefax, because of these functions. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 0:38:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from crcst346.netaddress.usa.net (crcst154.netaddress.usa.net [204.68.24.154]) by hub.freebsd.org (Postfix) with SMTP id F2C6937BB28 for ; Tue, 28 Mar 2000 00:38:33 -0800 (PST) (envelope-from mitko@usa.net) Received: (qmail 9783 invoked from network); 28 Mar 2000 08:38:33 -0000 Received: from nw176.netaddress.usa.net (204.68.24.76) by outbound.netaddress.usa.net with SMTP; 28 Mar 2000 08:38:33 -0000 Received: (qmail 7231 invoked by uid 60001); 28 Mar 2000 08:38:32 -0000 Message-ID: <20000328083832.7230.qmail@nw176.netaddress.usa.net> Received: from 204.68.24.76 by nw176 for [194.12.241.161] via web-mailer(M3.4.0.33) on Tue Mar 28 08:38:32 GMT 2000 Date: 28 Mar 00 11:38:32 EET DST From: Dimitar Peikov To: freebsd-current@freebsd.org Subject: libl.a in libipsec X-Mailer: USANET web-mailer (M3.4.0.33) 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 These days I've cvsup-ed to current and start to 'make world' fro= m my 3.4 RELEASE. Everything was ok, till making /usr/src/lib/libipsec where s= ome dependencies of /usr/src/lib/libl.a was not found? Any ideas? I'm not subscribed to freebsd-current, thats please reply and to me! thanks Dimitar Peikov ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=3D= 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 0:40:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 4625437BD65; Tue, 28 Mar 2000 00:40:42 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p14-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.15]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id RAA19442; Tue, 28 Mar 2000 17:40:40 +0900 (JST) Message-ID: <38E067A8.10298DC@newsguy.com> Date: Tue, 28 Mar 2000 17:04:56 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: John Baldwin Cc: Motomichi Matsuzaki , FreeBSD-current@FreeBSD.ORG Subject: Re: Please test for 8G-OVER-Booting with /boot/loader References: <200003271403.JAA85743@server.baldwin.cx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > > Looks good to me, but I need to test it to make sure. I will also look > at seeing if I can squeeze the int 13 extension installation check into > boot1 and boot0 so that they will use packet mode automatically as well. I recall comments (by rnordier/msmith) to the effect that packet mode support might break things. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@zurichgnomes.bsdconspiracy.net The size of the pizza is inversely proportional to the intensity of the hunger. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 1:13:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 6DBD237BD82 for ; Tue, 28 Mar 2000 01:13:11 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m2.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id SAA17442; Tue, 28 Mar 2000 18:13:09 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id SAA17318; Tue, 28 Mar 2000 18:13:08 +0900 (JST) Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id SAA06150; Tue, 28 Mar 2000 18:13:07 +0900 (JST) To: mitko@usa.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: libl.a in libipsec In-Reply-To: <20000328083832.7230.qmail@nw176.netaddress.usa.net> References: <20000328083832.7230.qmail@nw176.netaddress.usa.net> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000328181407Z.shin@nd.net.fujitsu.co.jp> Date: Tue, 28 Mar 2000 18:14:07 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 9 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > These days I've cvsup-ed to current and start to 'make world' from my > 3.4 RELEASE. Everything was ok, till making /usr/src/lib/libipsec where some > dependencies of /usr/src/lib/libl.a was not found? Any ideas? I am checking it now, but not yet clear why it happens. In old environments, libl.a seemed to be already installed at that time, but now it doesn't exist at libipsec build time. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 1:20:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 60D5F37BC8B for ; Tue, 28 Mar 2000 01:20:06 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id QAA00407; Tue, 28 Mar 2000 16:20:01 +0700 (NOVST) (envelope-from nnd) Date: Tue, 28 Mar 2000 16:20:01 +0700 (NOVST) Message-Id: <200003280920.QAA00407@wint.itfs.nsk.su> From: Nickolay Dudorov To: current@freebsd.org Subject: Re: libl.a in libipsec X-Newsgroups: itfs.freebsd.current In-Reply-To: <20000328181407Z.shin@nd.net.fujitsu.co.jp> User-Agent: tin/1.4.2-20000123 ("Polish") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20000328181407Z.shin@nd.net.fujitsu.co.jp> Yoshinobu Inoue wrote: >> These days I've cvsup-ed to current and start to 'make world' from my >> 3.4 RELEASE. Everything was ok, till making /usr/src/lib/libipsec where some >> dependencies of /usr/src/lib/libl.a was not found? Any ideas? > > I am checking it now, but not yet clear why it happens. In > old environments, libl.a seemed to be already installed at > that time, but now it doesn't exist at libipsec build time. libl.a isn't necessary for libipsec building at all. The error now is the result of adding ${LIBL} to DPADD by bde in the ver 1.3 of the Makefile in the src/lib/libipsec. N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 1:47: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from oldserver.demon.nl (oldserver.demon.nl [212.238.105.241]) by hub.freebsd.org (Postfix) with ESMTP id 5485B37BEE9 for ; Tue, 28 Mar 2000 01:46:36 -0800 (PST) (envelope-from marc@oldserver.demon.nl) Received: from localhost (localhost [127.0.0.1]) by oldserver.demon.nl (8.9.3/8.9.3) with ESMTP id LAA18631; Tue, 28 Mar 2000 11:46:28 +0200 (CEST) (envelope-from marc@oldserver.demon.nl) Date: Tue, 28 Mar 2000 11:46:28 +0200 (CEST) From: Marc Schneiders X-Sender: marc@propro.freebeastie.org To: Yoshinobu Inoue Cc: thsiang@ic.sunysb.edu, current@freebsd.org Subject: Re: buildworld failure In-Reply-To: <20000328095329W.shin@nd.net.fujitsu.co.jp> 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, 28 Mar 2000, Yoshinobu Inoue wrote: > > Any idea? > > > > [...] > > /usr/src/lib/libipsec/ipsec_get_pol > > icylen.c -o ipsec_get_policylen.So > > cc -fpic -DPIC -O -pipe -I/usr/obj/usr/src/lib/libipsec -DIPSEC_DEBUG > > -DIPSEC -D > > INET6 -I/usr/obj/usr/src/i386/usr/include -c > > /usr/src/lib/libipsec/../../sys/net > > key/key_debug.c -o key_debug.So > > make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libl.a. Stop > > *** Error code 2 > > What is your src/lib/libipsec/Makefile version? > It might have been fixed by recent commit from bde which adds > define of DPADD. > [...] Mine is: # $FreeBSD: src/lib/libipsec/Makefile,v 1.3 2000/03/27 15:16:06 bde Exp $ which seems to be the one with the 'fix' you mention... I had the same build failure. There is a suggestion to fix the build failure in cvs messages. Is that the way to solve it? -- Marc Schneiders --- marc@venster.nl --- marc@dotje.com FreeBSD propro.freebeastie.org 5.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 1:52:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 9823A37B519 for ; Tue, 28 Mar 2000 01:52:28 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id SAA25930; Tue, 28 Mar 2000 18:52:23 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id SAA01079; Tue, 28 Mar 2000 18:52:22 +0900 (JST) Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id SAA06945; Tue, 28 Mar 2000 18:52:17 +0900 (JST) To: marc@oldserver.demon.nl Cc: thsiang@ic.sunysb.edu, current@freebsd.org Subject: Re: buildworld failure In-Reply-To: References: <20000328095329W.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000328185317W.shin@nd.net.fujitsu.co.jp> Date: Tue, 28 Mar 2000 18:53:17 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 8 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I had the same build failure. There is a suggestion to fix the build > failure in cvs messages. Is that the way to solve it? I am trying buildworld again with no libl in libipsec Makefile, as previous Dimitar's message. If it is OK(and will be OK), I'll commit the fix. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 2:44:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id E508D37B5C6 for ; Tue, 28 Mar 2000 02:44:37 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id CAA33527; Tue, 28 Mar 2000 02:44:34 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38E08D12.DC350F14@gorean.org> Date: Tue, 28 Mar 2000 02:44:34 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0325 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org, Peter Wemm Subject: cvs repository nits and gnats Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I'm working on a new project and had the need for a clean set of sources on a new machine. In the course of setting it all up I neglected to copy over my .cvsrc file which has (amongst other things) 'co -P'. In checking out the sources for RELENG_4 I ended up with a large number of empty directories. Some of them were obviously relics of the past, like src/TODO-2.1, src/usr.sbin/xntpd, etc. There were a large number in contrib, probably detritus from imports, etc. I'm not sure if this is significant, it obviously doesn't do any harm. I just thought I'd mention it. Slightly more serious was the presence of various lock files/directories. Specifically, one in src/games/primes killed my co as an unpriviliged user because it was set 700 and owned by root. The co failed because it couldn't create a lock file. I did a 'find . -name \*\#\* in my CVSROOT and found several other files like this. Deleting them did no harm, and they didn't return when I ran cvsup again. Finally, a question. I'm doing my cvs co/update on this machine remotely via rsh (within our secure network of course). When I start the update it creates an entire src directory tree in /tmp. This takes a great deal of time, so I'm wondering if this can be avoided somehow? I'm doing the cvs rsh as root on the client machine, and as an unpriviliged user on the cvs server machine. Hope this is helpful, Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 2:53:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 237EA37B832; Tue, 28 Mar 2000 02:53:38 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12ZtcZ-0009DC-00; Tue, 28 Mar 2000 12:53:15 +0200 From: Sheldon Hearn To: Jeroen Ruigrok van der Werven Cc: Soren Schmidt , Brian Fundakowski Feldman , current@FreeBSD.ORG Subject: Re: DDB and dumping disk In-reply-to: Your message of "Mon, 27 Mar 2000 14:50:12 +0200." <20000327145012.H77375@lucifer.bart.nl> Date: Tue, 28 Mar 2000 12:53:15 +0200 Message-ID: <35413.954240795@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Mar 2000 14:50:12 +0200, Jeroen Ruigrok van der Werven wrote: > I wasn't complaining, on the contrary! > > I was happily surprised it was way faster than the SCSI dump. =) So now the only question is whether our existing bootstrapping infrastructure already has some way to use your ddb magic to set dumpdev. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 3: 2:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 2957737BE0E; Tue, 28 Mar 2000 03:02:19 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id NAA96623; Tue, 28 Mar 2000 13:02:06 +0200 (CEST) (envelope-from asmodai) Date: Tue, 28 Mar 2000 13:02:06 +0200 From: Jeroen Ruigrok van der Werven To: Sheldon Hearn Cc: Soren Schmidt , Brian Fundakowski Feldman , current@FreeBSD.ORG Subject: Re: DDB and dumping disk Message-ID: <20000328130206.D94986@lucifer.bart.nl> References: <20000327145012.H77375@lucifer.bart.nl> <35413.954240795@axl.ops.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <35413.954240795@axl.ops.uunet.co.za>; from sheldonh@uunet.co.za on Tue, Mar 28, 2000 at 12:53:15PM +0200 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000328 12:55], Sheldon Hearn (sheldonh@uunet.co.za) wrote: >On Mon, 27 Mar 2000 14:50:12 +0200, Jeroen Ruigrok van der Werven wrote: > >> I wasn't complaining, on the contrary! >> >> I was happily surprised it was way faster than the SCSI dump. =) > >So now the only question is whether our existing bootstrapping >infrastructure already has some way to use your ddb magic to set >dumpdev. :-) Well, I can set dumpdev in ddb, but the problem is that when I reboot that savecore doesn't detect a dump. If I boot the system completely and manually panic and let it dump savecore will detect the dump and put it in /var/crash. So I wonder what I forgot in DDB. I do: db> show disk/ad0s1b 0xc0NNNNNN I then use this value to: db> write dumpdev 0xc0NNNNNN dumpdev = ffffffff -> 0x0cNNNNNN I can then dump when typing: db> panic But after the reboot savecore doesn't recognise the dump. savecore: no coredump Hope this makes it a bit more clear. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl To desire immortality is to desire the eternal perpetuation of a great mistake... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 3:10:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 5B7A337B9C4; Tue, 28 Mar 2000 03:10:39 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12Ztt8-0009Ky-00; Tue, 28 Mar 2000 13:10:22 +0200 From: Sheldon Hearn To: Jeroen Ruigrok van der Werven Cc: Soren Schmidt , Brian Fundakowski Feldman , current@FreeBSD.ORG Subject: Re: DDB and dumping disk In-reply-to: Your message of "Tue, 28 Mar 2000 13:02:06 +0200." <20000328130206.D94986@lucifer.bart.nl> Date: Tue, 28 Mar 2000 13:10:22 +0200 Message-ID: <35895.954241822@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Mar 2000 13:02:06 +0200, Jeroen Ruigrok van der Werven wrote: > I can then dump when typing: > > db> panic Damnit. So I've just committed bogus advice in dumpon(8). :-( Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 3:26:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 9195D37B956; Tue, 28 Mar 2000 03:26:36 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id NAA96876; Tue, 28 Mar 2000 13:26:26 +0200 (CEST) (envelope-from asmodai) Date: Tue, 28 Mar 2000 13:26:26 +0200 From: Jeroen Ruigrok van der Werven To: Sheldon Hearn Cc: Soren Schmidt , Brian Fundakowski Feldman , current@FreeBSD.ORG Subject: Re: DDB and dumping disk Message-ID: <20000328132626.F94986@lucifer.bart.nl> References: <20000328130206.D94986@lucifer.bart.nl> <35895.954241822@axl.ops.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <35895.954241822@axl.ops.uunet.co.za>; from sheldonh@uunet.co.za on Tue, Mar 28, 2000 at 01:10:22PM +0200 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000328 13:15], Sheldon Hearn (sheldonh@uunet.co.za) wrote: > > >On Tue, 28 Mar 2000 13:02:06 +0200, Jeroen Ruigrok van der Werven wrote: > >> I can then dump when typing: >> >> db> panic > >Damnit. So I've just committed bogus advice in dumpon(8). :-( No not really. Your patch is a step in the right direction. I am currently only trying to figure out why the DDB way doesn't trigger savecore to recognise the dump. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl How are the mighty fallen... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 3:36:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id E7D2C37BB5D for ; Tue, 28 Mar 2000 03:36:16 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m2.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id UAA27791; Tue, 28 Mar 2000 20:36:15 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id UAA14381; Tue, 28 Mar 2000 20:36:11 +0900 (JST) Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id UAA08970; Tue, 28 Mar 2000 20:36:10 +0900 (JST) To: nnd@mail.nsk.ru Cc: current@FreeBSD.ORG Subject: Re: libl.a in libipsec In-Reply-To: <200003280920.QAA00407@wint.itfs.nsk.su> References: <20000328181407Z.shin@nd.net.fujitsu.co.jp> <200003280920.QAA00407@wint.itfs.nsk.su> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000328203709M.shin@nd.net.fujitsu.co.jp> Date: Tue, 28 Mar 2000 20:37:09 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 17 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am checking it now, but not yet clear why it happens. In > > old environments, libl.a seemed to be already installed at > > that time, but now it doesn't exist at libipsec build time. > > libl.a isn't necessary for libipsec building at all. > The error now is the result of adding ${LIBL} to DPADD by bde > in the ver 1.3 of the Makefile in the src/lib/libipsec. > > N.Dudorov Thanks, after removing libl related dependency from libipsec Makefile, buildworld just passed libipsec part. libl.a was not used on the first place. :-< I'll commit the fix. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 3:46:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id DE3CB37BCF7 for ; Tue, 28 Mar 2000 03:46:33 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id GAA87302; Tue, 28 Mar 2000 06:46:27 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200003281146.GAA87302@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <38E067A8.10298DC@newsguy.com> Date: Tue, 28 Mar 2000 06:46:27 -0500 (EST) From: John Baldwin To: "Daniel C. Sobral" Subject: Re: Please test for 8G-OVER-Booting with /boot/loader Cc: FreeBSD-current@FreeBSD.org, Motomichi Matsuzaki Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Mar-00 Daniel C. Sobral wrote: > John Baldwin wrote: >> >> Looks good to me, but I need to test it to make sure. I will also look >> at seeing if I can squeeze the int 13 extension installation check into >> boot1 and boot0 so that they will use packet mode automatically as well. > > I recall comments (by rnordier/msmith) to the effect that packet mode > support might break things. Oh, I remember. This just checks if the controller supports LBA. You also need to check if the drive supports LBA. The problem is with older drives. Hmm, I'll look around to see if you can ask the BIOS for drive capabilities. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/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 Mar 28 3:53: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 7FB1837BE1D; Tue, 28 Mar 2000 03:52:57 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id NAA49210; Tue, 28 Mar 2000 13:50:56 +0200 (CEST) Message-Id: <200003281150.NAA49210@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: Jeroen Ruigrok van der Werven Cc: Sheldon Hearn , Soren Schmidt , Brian Fundakowski Feldman , current@FreeBSD.ORG Subject: Re: DDB and dumping disk Reply-To: Gary Jennejohn In-reply-to: Your message of "Tue, 28 Mar 2000 13:26:26 +0200." <20000328132626.F94986@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Mar 2000 13:50:56 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok van der Werven writes: >I am currently only trying to figure out why the DDB way doesn't trigger >savecore to recognise the dump. > Maybe because kern.dumpdev has a different value and savecore can't find a dump on it ? Have you tried setting kern.dumpdev by hand and then manually invoking savecore ? --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@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 Mar 28 4: 2: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id AF29337B903 for ; Tue, 28 Mar 2000 04:02:00 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id TAA10549; Tue, 28 Mar 2000 19:01:41 +0700 (NOVST) (envelope-from nnd) Date: Tue, 28 Mar 2000 19:01:41 +0700 (NOVST) Message-Id: <200003281201.TAA10549@wint.itfs.nsk.su> From: Nickolay Dudorov To: Yoshinobu Inoue Cc: current@freebsd.org Subject: Re: libl.a in libipsec In-Reply-To: <20000328203709M.shin@nd.net.fujitsu.co.jp> User-Agent: tin/1.4.2-20000123 ("Polish") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20000328203709M.shin@nd.net.fujitsu.co.jp> Yoshinobu Inoue wrote: >> > I am checking it now, but not yet clear why it happens. In >> > old environments, libl.a seemed to be already installed at >> > that time, but now it doesn't exist at libipsec build time. >> >> libl.a isn't necessary for libipsec building at all. >> The error now is the result of adding ${LIBL} to DPADD by bde >> in the ver 1.3 of the Makefile in the src/lib/libipsec. >> >> N.Dudorov > > Thanks, after removing libl related dependency from libipsec > Makefile, buildworld just passed libipsec part. > libl.a was not used on the first place. :-< > > I'll commit the fix. It seems to me (and my buildworld agree with this) that 'liby' is also not necessary for building of 'libipsec'. N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 4:24:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id EC74F37BD2A for ; Tue, 28 Mar 2000 04:24:08 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m4.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id VAA04581; Tue, 28 Mar 2000 21:24:08 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id VAA06291; Tue, 28 Mar 2000 21:24:03 +0900 (JST) Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id VAA10046; Tue, 28 Mar 2000 21:24:02 +0900 (JST) To: nnd@mail.nsk.ru Cc: current@FreeBSD.ORG Subject: Re: libl.a in libipsec In-Reply-To: <200003281201.TAA10549@wint.itfs.nsk.su> References: <20000328203709M.shin@nd.net.fujitsu.co.jp> <200003281201.TAA10549@wint.itfs.nsk.su> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000328212501R.shin@nd.net.fujitsu.co.jp> Date: Tue, 28 Mar 2000 21:25:01 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 15 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Thanks, after removing libl related dependency from libipsec > > Makefile, buildworld just passed libipsec part. > > libl.a was not used on the first place. :-< > > > > I'll commit the fix. > > It seems to me (and my buildworld agree with this) > that 'liby' is also not necessary for building of 'libipsec'. > > N.Dudorov I'll also commit that change after one more check. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 4:52:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 2B0F337BE53 for ; Tue, 28 Mar 2000 04:52:16 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 8425 invoked from network); 28 Mar 2000 12:52:11 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 28 Mar 2000 12:52:11 -0000 Date: Tue, 28 Mar 2000 22:51:54 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Gary Jennejohn Cc: Jeroen Ruigrok van der Werven , Sheldon Hearn , Soren Schmidt , Brian Fundakowski Feldman , current@FreeBSD.ORG Subject: Re: DDB and dumping disk In-Reply-To: <200003281150.NAA49210@peedub.muc.de> 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, 28 Mar 2000, Gary Jennejohn wrote: > Jeroen Ruigrok van der Werven writes: > >I am currently only trying to figure out why the DDB way doesn't trigger > >savecore to recognise the dump. > > > > Maybe because kern.dumpdev has a different value and savecore can't > find a dump on it ? Have you tried setting kern.dumpdev by hand and > then manually invoking savecore ? Also, dumplo must have a consistent value. dumpdev should be set using ddb before the SYSINIT for the dump device is called, or better, never set dumpdev with ddb, but call setdumpdev(desired_dumpdev) directly at a suitable time. When setdumpdev() is not called, some sanity checks are bypassed, and dumplo is only statically initialized (to 0). This means that dumps go to the start of the dumpdev device instead of to the end. I think savecore will find the dump provided dumplo is consistently initialized, so the only problem with starting dumps at the start of the device is that this will clobber the label if the device contains the label. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 4:58:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 656A737B6BA; Tue, 28 Mar 2000 04:58:33 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12ZvZ2-0009kV-00; Tue, 28 Mar 2000 14:57:44 +0200 From: Sheldon Hearn To: Bruce Evans Cc: Gary Jennejohn , Jeroen Ruigrok van der Werven , Soren Schmidt , Brian Fundakowski Feldman , current@FreeBSD.ORG Subject: Re: DDB and dumping disk In-reply-to: Your message of "Tue, 28 Mar 2000 22:51:54 +1000." Date: Tue, 28 Mar 2000 14:57:44 +0200 Message-ID: <37478.954248264@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Mar 2000 22:51:54 +1000, Bruce Evans wrote: > I think savecore will find the dump provided dumplo is consistently > initialized, so the only problem with starting dumps at the start of > the device is that this will clobber the label if the device contains > the label. Given that the moment at which dumpdev is set seems important, I think it's probably better for me to back these isntructions out of the dumpon(8) manual page and wait for something less tricky. Do you agree? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 5:27:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 3B6CA37BE6D for ; Tue, 28 Mar 2000 05:27:29 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id XAA26273; Tue, 28 Mar 2000 23:33:22 +1000 Date: Tue, 28 Mar 2000 23:26:38 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Nickolay Dudorov Cc: Yoshinobu Inoue , current@FreeBSD.ORG Subject: Re: libl.a in libipsec In-Reply-To: <200003281201.TAA10549@wint.itfs.nsk.su> 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 I broke the world. > >> > old environments, libl.a seemed to be already installed at > >> > that time, but now it doesn't exist at libipsec build time. It was never installed in the temporary build tree, except possibly in old, broken versions of /usr/src/Makefile* which built and installed it as part of making lex as a build-tool (non-broken versions had complications to avoid making lex/lib in the build-tool case, since making it caused other problems). When the dependency was missing, -ll caused the linker to find libl.a in the wrong place. I don't see how liby can get built before libipsec either. > >> libl.a isn't necessary for libipsec building at all. > >> The error now is the result of adding ${LIBL} to DPADD by bde > >> in the ver 1.3 of the Makefile in the src/lib/libipsec. > >> > >> N.Dudorov > > > > Thanks, after removing libl related dependency from libipsec > > Makefile, buildworld just passed libipsec part. > > libl.a was not used on the first place. :-< > > > > I'll commit the fix. > > It seems to me (and my buildworld agree with this) > that 'liby' is also not necessary for building of 'libipsec'. liby is used. Linking to the static version of it isn't good. I think it results in functions from liby.a being included in libipsec.so. Since liby.a isn't compiled with -fpic, it's not clear how this can work. I think the linker prints RRS warnings when it doesn't work. I haven't seen those, so maybe it does work. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 5:45:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mccons.maxbaud.net (adsl-208-191-215-92.dsl.kscymo.swbell.net [208.191.215.92]) by hub.freebsd.org (Postfix) with ESMTP id 76C3437BEFD for ; Tue, 28 Mar 2000 05:45:45 -0800 (PST) (envelope-from root@mccons.maxbaud.net) Received: from localhost (root@localhost) by mccons.maxbaud.net (8.9.3/8.9.3) with SMTP id HAA72161 for ; Tue, 28 Mar 2000 07:45:43 -0600 (CST) (envelope-from root@mccons.maxbaud.net) Date: Tue, 28 Mar 2000 07:45:42 -0600 (CST) From: Wm Brian McCane X-Sender: root@localhost To: FreeBSD-current@FreeBSD.ORG Subject: kernel trap 9 In-Reply-To: <200003281146.GAA87302@server.baldwin.cx> 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 having a serious problem trying to build a new kernel for my machine. I was running 'current' and have now 'downgraded' to 4.0-RELEASE to try and fix the problem. When I try to boot my machine, it goes into the bootstrap loader okay, and waits 10 seconds, then the screen flashes and the following message pops up on the screen: kernel trap 9 with interrupts disabled Fatal trap 9: general protection fault in kernel mode processor eflags = resume, IOPL = 0 current process = Idle interrupt mask = net tty bio cam trap number = 9 panic: general protection fault Uptime: 0s My machine is a PIII-500 on an Asus P2B-S motherboard. I have 128MB of RAM and 2 Video Cards installed. I am using using a 'dc0' type NIC. I suspect the problem is in the build process (or some residual flag), because I can boot kernel.GENERIC from the 4.0-RELEASE without a hitch. If someone would be interested in giving me a hand with this, I would be happy to send them my config files, &etc. brian +-----------------------------------+------------------------------------------+ He rides a cycle of mighty days, and \ Wm Brian and Lori McCane represents the last great schizm among\ McCane Consulting the gods. Evil though he obviously is, \ root@bmccane.maxbaud.net he is a mighty figure, this father of \ http://bmccane.maxbaud.net/ my spirit, and I respect him as the sons \ http://www.sellit-here.com/ of old did the fathers of their bodies. \ http://kidsearch.maxbaud.net/ Roger Zelazny - "Lord of Light" \ http://www.maxbaud.net/ +-------------------------------------------+----------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 6:44:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.targetnet.com (mail.targetnet.com [207.245.246.3]) by hub.freebsd.org (Postfix) with ESMTP id 4641937BEE3 for ; Tue, 28 Mar 2000 06:44:07 -0800 (PST) (envelope-from james@targetnet.com) Received: from james by mail.targetnet.com with local (Exim 3.02 #1) id 12ZxDn-000Ftf-00 for current@freebsd.org; Tue, 28 Mar 2000 09:43:55 -0500 Date: Tue, 28 Mar 2000 09:43:55 -0500 From: James FitzGibbon To: current@freebsd.org Subject: current.freebsd.org ftp misconfig ? Message-ID: <20000328094355.D1248@targetnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i Organization: Targetnet.com Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is this a transient situation, or is current down for maintainance ? [central-01:james] ~ (2) > ftp -a current.freebsd.org Connected to usw2.freebsd.org. 220 usw2.freebsd.org FTP server (Version wu-2.6.0(1) Tue Jan 25 00:05:38 CST 2000) ready. 331 Guest login ok, send your complete e-mail address as password. 530 Can't set guest privileges. ftp: Login failed. ftp> quit 221 Goodbye. [central-01:james] ~ (3) > -- j. James FitzGibbon james@targetnet.com Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 7:18:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 0522437BF60 for ; Tue, 28 Mar 2000 07:18:13 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id AAA08403; Wed, 29 Mar 2000 00:17:18 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id AAA02195; Wed, 29 Mar 2000 00:17:17 +0900 (JST) Received: from localhost ([192.168.245.131]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id AAA05923; Wed, 29 Mar 2000 00:17:16 +0900 (JST) To: bde@zeta.org.au Cc: nnd@mail.nsk.ru, current@FreeBSD.ORG Subject: Re: libl.a in libipsec In-Reply-To: References: <200003281201.TAA10549@wint.itfs.nsk.su> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000329001815N.shin@nd.net.fujitsu.co.jp> Date: Wed, 29 Mar 2000 00:18:15 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 18 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It seems to me (and my buildworld agree with this) > > that 'liby' is also not necessary for building of 'libipsec'. > > liby is used. Linking to the static version of it isn't good. > I think it results in functions from liby.a being included in > libipsec.so. Since liby.a isn't compiled with -fpic, it's not > clear how this can work. I think the linker prints RRS warnings > when it doesn't work. I haven't seen those, so maybe it does > work. > > Bruce In the build after the trial change of removing liby dependency from libipsec Makefile, misteriously libipsec is not built as if it is just neglected, and buildworld continues. :-\ Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 7:30:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 2A16437BF8A for ; Tue, 28 Mar 2000 07:30:42 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id AAA09136; Wed, 29 Mar 2000 00:29:56 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id AAA11383; Wed, 29 Mar 2000 00:29:55 +0900 (JST) Received: from localhost ([192.168.245.131]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id AAA06381; Wed, 29 Mar 2000 00:29:51 +0900 (JST) To: bde@zeta.org.au Cc: bmah@CA.Sandia.GOV, nnd@mail.nsk.ru, current@FreeBSD.ORG Subject: Re: 'machine/param.h' required for 'sys/socket.h' In-Reply-To: References: <20000326004417L.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Wed_Mar_29_00:30:47_2000_809)--" Content-Transfer-Encoding: 7bit Message-Id: <20000329003050L.shin@nd.net.fujitsu.co.jp> Date: Wed, 29 Mar 2000 00:30:50 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 221 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Wed_Mar_29_00:30:47_2000_809)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > sys/socket.h: > > #ifdef _NO_NAME_SPACE_POLLUTION > > #include > > #else > > #define _NO_NAME_SPACE_POLLUTION > > #include > > #undef _NO_NAME_SPACE_POLLUTION > > #endif > > I like this for a quick fix. Only define _ALIGN() like the current > ALIGN(). Don't define all the variants given in your previous mail. I created the patches. It become a little bit more complicated than I expected, to avoid duplicated inclusion independently in each of namespace polluted part and non polluted part. Please give me comments if any. Thanks, Yoshinobu Inoue ----Next_Part(Wed_Mar_29_00:30:47_2000_809)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="namespace.diff" Index: sys/socket.h =================================================================== RCS file: /home/ncvs/src/sys/sys/socket.h,v retrieving revision 1.39 diff -u -r1.39 socket.h --- sys/socket.h 2000/03/11 19:51:04 1.39 +++ sys/socket.h 2000/03/28 12:02:12 @@ -37,6 +37,14 @@ #ifndef _SYS_SOCKET_H_ #define _SYS_SOCKET_H_ +#ifdef _NO_NAMESPACE_POLLUTION +#include +#else +#define _NO_NAMESPACE_POLLUTION +#include +#undef _NO_NAMESPACE_POLLUTION +#endif + /* * Definitions related to sockets: types, address families, options. */ Index: i386/include/param.h =================================================================== RCS file: /home/ncvs/src/sys/i386/include/param.h,v retrieving revision 1.54 diff -u -r1.54 param.h --- i386/include/param.h 1999/12/11 10:54:06 1.54 +++ i386/include/param.h 2000/03/28 12:02:13 @@ -37,8 +37,16 @@ * $FreeBSD: src/sys/i386/include/param.h,v 1.54 1999/12/11 10:54:06 peter Exp $ */ -#ifndef _MACHINE_PARAM_H_ -#define _MACHINE_PARAM_H_ +#ifndef _MACHINE_PARAM_H_NO_NAMESPACE_POLLUTION +#define _MACHINE_PARAM_H_NO_NAMESPACE_POLLUTION + +/* + * Round p (pointer or byte index) up to a correctly-aligned value + * for all data types (int, long, ...). The result is unsigned int + * and must be cast to any desired pointer type. + */ +#define _ALIGNBYTES (sizeof(int) - 1) +#define _ALIGN(p) (((unsigned)(p) + _ALIGNBYTES) & ~_ALIGNBYTES) /* * Machine dependent constants for Intel 386. @@ -46,12 +54,23 @@ #ifndef _MACHINE #define _MACHINE i386 #endif -#ifndef MACHINE -#define MACHINE "i386" -#endif #ifndef _MACHINE_ARCH #define _MACHINE_ARCH i386 #endif + +#endif /* !_MACHINE_PARAM_H_NO_NAMESPACE_POLLUTION */ + +#ifndef _NO_NAMESPACE_POLLUTION + +#ifndef _MACHINE_PARAM_H_ +#define _MACHINE_PARAM_H_ + +/* + * Machine dependent constants for Intel 386. + */ +#ifndef MACHINE +#define MACHINE "i386" +#endif #ifndef MACHINE_ARCH #define MACHINE_ARCH "i386" #endif @@ -70,13 +89,8 @@ #define NCPUS 1 #endif -/* - * Round p (pointer or byte index) up to a correctly-aligned value - * for all data types (int, long, ...). The result is unsigned int - * and must be cast to any desired pointer type. - */ -#define ALIGNBYTES (sizeof(int) - 1) -#define ALIGN(p) (((unsigned)(p) + ALIGNBYTES) & ~ALIGNBYTES) +#define ALIGNBYTES _ALIGNBYTES +#define ALIGN(p) _ALIGN(p) #define PAGE_SHIFT 12 /* LOG2(PAGE_SIZE) */ #define PAGE_SIZE (1<; Tue, 28 Mar 2000 07:38:43 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 14501 invoked from network); 28 Mar 2000 15:38:36 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 28 Mar 2000 15:38:36 -0000 Date: Wed, 29 Mar 2000 01:38:19 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Sheldon Hearn Cc: Gary Jennejohn , Jeroen Ruigrok van der Werven , Soren Schmidt , Brian Fundakowski Feldman , current@FreeBSD.ORG Subject: Re: DDB and dumping disk In-Reply-To: <37478.954248264@axl.ops.uunet.co.za> 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, 28 Mar 2000, Sheldon Hearn wrote: > Given that the moment at which dumpdev is set seems important, I think > it's probably better for me to back these isntructions out of the > dumpon(8) manual page and wait for something less tricky. > > Do you agree? Yes. The man page is also misleading about single user mode. dumpon(8) works fine in single user mode. The problem case is when the system crashes before reaching user mode. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 7:50:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id ED18837BFD0; Tue, 28 Mar 2000 07:50:44 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id RAA00592; Tue, 28 Mar 2000 17:50:28 +0200 (CEST) (envelope-from asmodai) Date: Tue, 28 Mar 2000 17:50:28 +0200 From: Jeroen Ruigrok van der Werven To: Bruce Evans Cc: Sheldon Hearn , Gary Jennejohn , Soren Schmidt , Brian Fundakowski Feldman , current@FreeBSD.ORG Subject: Re: DDB and dumping disk Message-ID: <20000328175028.A475@lucifer.bart.nl> References: <37478.954248264@axl.ops.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from bde@zeta.org.au on Wed, Mar 29, 2000 at 01:38:19AM +1000 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000328 17:40], Bruce Evans (bde@zeta.org.au) wrote: >On Tue, 28 Mar 2000, Sheldon Hearn wrote: > >> Given that the moment at which dumpdev is set seems important, I think >> it's probably better for me to back these isntructions out of the >> dumpon(8) manual page and wait for something less tricky. >> >> Do you agree? > >Yes. > >The man page is also misleading about single user mode. dumpon(8) works >fine in single user mode. The problem case is when the system crashes >before reaching user mode. Exactly. And that is what I am now slowly trying to work on. Brian's addition of show disk in ddb was one step ahead. Now to get the functionality in one way or the other in either the loader or ddb or another thing. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl That's your Destiny, the only chance, take it, take it in your hands... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 7:51:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (Postfix) with ESMTP id 6808F37C07A for ; Tue, 28 Mar 2000 07:51:45 -0800 (PST) (envelope-from Alain.Thivillon@hsc.fr) Received: from yoko.hsc.fr (yoko.hsc.fr [192.70.106.76]) by itesec.hsc.fr (Postfix) with ESMTP id 1D01110F25 for ; Tue, 28 Mar 2000 17:51:43 +0200 (CEST) Received: by yoko.hsc.fr (Postfix release-19990601, from userid 1001) id 6DB1B9B335; Tue, 28 Mar 2000 17:51:27 +0200 (CEST) Date: Tue, 28 Mar 2000 17:51:26 +0200 From: Alain Thivillon To: freebsd-current@freebsd.org Subject: SMP patch breaks non SMP kernel build Message-ID: <20000328175126.E5025@yoko.hsc.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.5i X-Organization: Herve Schauer Consultants X-Operating-System: FreeBSD 4.0-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG . astpending is now undefined (/usr/src/sys/kern/kern_sig.c:1168) . some calls to get_mplock and rel_mplock are made without #define SMP conditionnal compile in following modules: kern_exec kern_exit kern_sig kern_sync mfs_vfsops mem trap To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 9:14:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3EA1337BE09 for ; Tue, 28 Mar 2000 09:14:16 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA52635; Tue, 28 Mar 2000 09:14:01 -0800 (PST) (envelope-from dillon) Date: Tue, 28 Mar 2000 09:14:01 -0800 (PST) From: Matthew Dillon Message-Id: <200003281714.JAA52635@apollo.backplane.com> To: Alain Thivillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP patch breaks non SMP kernel build References: <20000328175126.E5025@yoko.hsc.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :. astpending is now undefined (/usr/src/sys/kern/kern_sig.c:1168) : :. some calls to get_mplock and rel_mplock are made without #define SMP : conditionnal compile in following modules: : : kern_exec : kern_exit : kern_sig : kern_sync : mfs_vfsops : mem : trap Hoya!... ok, I'll compile up a UP kernel and fix those problems -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 Mar 28 9:36: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 001DE37B6BE for ; Tue, 28 Mar 2000 09:35:55 -0800 (PST) (envelope-from rb@gid.co.uk) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id SAA23906 for current@freebsd.org; Tue, 28 Mar 2000 18:35:54 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id SAA16215 for ; Tue, 28 Mar 2000 18:14:02 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 28 Mar 2000 18:14:02 +0100 To: current@freebsd.org From: Bob Bishop Subject: SMP kernel broken at cvsup Tue Mar 28 11:56:07 BST 2000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Appears to boot OK, but then won't answer to network or console, not even CtlAltEsc to DDB. Screen saver kicks in OK though. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 9:52:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 53D3837B811 for ; Tue, 28 Mar 2000 09:52:21 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA52954; Tue, 28 Mar 2000 09:52:12 -0800 (PST) (envelope-from dillon) Date: Tue, 28 Mar 2000 09:52:12 -0800 (PST) From: Matthew Dillon Message-Id: <200003281752.JAA52954@apollo.backplane.com> To: Bob Bishop Cc: current@FreeBSD.ORG Subject: Re: SMP kernel broken at cvsup Tue Mar 28 11:56:07 BST 2000 References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, : :Appears to boot OK, but then won't answer to network or console, not even :CtlAltEsc to DDB. Screen saver kicks in OK though. : :-- :Bob Bishop (0118) 977 4017 international code +44 118 :rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK Make sure you haven't confused it between the patch set and the commit I made last night. Do a cvs update and then a cvs diff to make sure things haven't gotten confused. -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 Mar 28 10: 3: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id AA5DD37B7A1; Tue, 28 Mar 2000 10:03:01 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup8-24.iptelecom.net.ua [212.9.227.216]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id VAA17958; Tue, 28 Mar 2000 21:08:38 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id VAA03218; Tue, 28 Mar 2000 21:02:18 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <38E0F3A6.87231410@altavista.net> Date: Tue, 28 Mar 2000 21:02:15 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org, brian@freebsd.org Subject: Strange new ppp warnings Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, After upgrading my box to the 4.0-STABLE, I've discovered that ppp started produce regular warnings I've never seen before: Warning: nat_LayerPull: Dropped a packet.... What does it mean and what implications may it have? -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 10: 7:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D1E7837C058 for ; Tue, 28 Mar 2000 10:07:18 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA53164; Tue, 28 Mar 2000 10:07:15 -0800 (PST) (envelope-from dillon) Date: Tue, 28 Mar 2000 10:07:15 -0800 (PST) From: Matthew Dillon Message-Id: <200003281807.KAA53164@apollo.backplane.com> To: Alain Thivillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP patch breaks non SMP kernel build References: <20000328175126.E5025@yoko.hsc.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :. astpending is now undefined (/usr/src/sys/kern/kern_sig.c:1168) : :. some calls to get_mplock and rel_mplock are made without #define SMP : conditionnal compile in following modules: : : kern_exec : kern_exit : kern_sig : kern_sync : mfs_vfsops : mem : trap Ok, should be fixed soon as the cvsup mirrors update. I didn't see anything in mfs_vfsops and I have no idea what 'mem' or 'trap' is, but I can compile up a UP kernel now. If you come across more compilation/options combinations that don't work send me email. Since we are probably going to be using get_mplock()/rel_mplock() and other mutex/locking functions more and more in the mainline kernel code, I've decided to turn them into __inline dummies for the UP kernel rather then attempt to #ifdef them out. -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 Mar 28 10:43:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 3C6A437B5D6 for ; Tue, 28 Mar 2000 10:43:34 -0800 (PST) (envelope-from dgilbert@office.tor.velocet.net) Received: from office.tor.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id B7E0013801B; Tue, 28 Mar 2000 13:42:47 -0500 (EST) Received: (from dgilbert@localhost) by office.tor.velocet.net (8.9.3/8.9.3) id NAA20901; Tue, 28 Mar 2000 13:42:46 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14560.64806.608659.960815@trooper.velocet.net> Date: Tue, 28 Mar 2000 13:42:46 -0500 (EST) To: freebsd-current@freebsd.org, Archie Cobbs Subject: Kernel trace question (kernel doesn't compile _without_ -O) X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm puzzled over the following kernel trace. 'm' in frame 6 is clearly not null... but in frame 5, it is. I have compiled the ng_l2tp module without -O... just in case that was the problem, but line 391 (the for loop) explicitly tests m for NULLness anyways. Also... I have noticed that several modules don't want to compile in the kernel without -O, including kern_synch.c (undefined reference to __cursig) and atomic.c (inconsistent operand constraints in an `asm'). (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:304 #1 0xc0155ed5 in panic (fmt=0xc026010f "page fault") at ../../kern/kern_shutdown.c:554 #2 0xc022557a in trap_fatal (frame=0xc0269d58, eva=16) at ../../i386/i386/trap.c:924 #3 0xc022522d in trap_pfault (frame=0xc0269d58, usermode=0, eva=16) at ../../i386/i386/trap.c:817 #4 0xc0224db3 in trap (frame={tf_fs = -1071251440, tf_es = 9502736, tf_ds = 16, tf_edi = 96, tf_esi = 1, tf_ebp = -1071211080, tf_isp = -1071211132, tf_ebx = 0, tf_edx = 0, tf_ecx = 0, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1072237390, tf_cs = 8, tf_eflags = 66054, tf_esp = -1038559808, tf_ss = -1072044908}) at ../../i386/i386/trap.c:423 #5 0xc016f4b2 in m_dup (m=0x0, how=1) at ../../kern/uipc_mbuf.c:763 #6 0xc019e4f3 in ngl2tp_ctrlq_timeout (arg=0xc218d5c0) at ../../netgraph/ng_l2tp.c:393 #7 0xc015b245 in softclock () at ../../kern/kern_timeout.c:131 (kgdb) frame 6 #6 0xc019e4f3 in ngl2tp_ctrlq_timeout (arg=0xc218d5c0) at ../../netgraph/ng_l2tp.c:393 393 n = m_dup(m, M_NOWAIT); (kgdb) l 388 int i, error = 0; 389 u_char *d; 390 391 for(m=p->ctrlq, i=0; m && i < p->Swin; m = m->m_nextpkt, i++) 392 { 393 n = m_dup(m, M_NOWAIT); 394 if(n) 395 { 396 d = mtod(n, u_char *); 397 *((u_int16_t *)(d+10)) = htons(p->Nr); /* update window recd */ (kgdb) p m $1 = (struct mbuf *) 0xc0752280 -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 10:55: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 9819937B7A1; Tue, 28 Mar 2000 10:55:02 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id KAA47144; Tue, 28 Mar 2000 10:55:02 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 28 Mar 2000 10:55:01 -0800 (PST) From: Kris Kennaway To: Doug Barton Cc: freebsd-current@freebsd.org, Peter Wemm Subject: Re: cvs repository nits and gnats In-Reply-To: <38E08D12.DC350F14@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 Tue, 28 Mar 2000, Doug Barton wrote: > src/TODO-2.1, src/usr.sbin/xntpd, etc. There were a large number in > contrib, probably detritus from imports, etc. I'm not sure if this is > significant, it obviously doesn't do any harm. I just thought I'd > mention it. CVS has no concept of removing a directory (possibly excepting repository surgery), so unless you pass the -P option (prune empty directories) you get stuck with all of the old ones. > Slightly more serious was the presence of various lock > files/directories. Specifically, one in src/games/primes killed my co as > an unpriviliged user because it was set 700 and owned by root. The co > failed because it couldn't create a lock file. I did a 'find . -name > \*\#\* in my CVSROOT and found several other files like this. Deleting > them did no harm, and they didn't return when I ran cvsup again. I havent seen this. > Finally, a question. I'm doing my cvs co/update on this machine > remotely via rsh (within our secure network of course). When I start the > update it creates an entire src directory tree in /tmp. This takes a > great deal of time, so I'm wondering if this can be avoided somehow? I'm > doing the cvs rsh as root on the client machine, and as an unpriviliged > user on the cvs server machine. I ran into this the other day and was advised to mount the CVS repository via NFS instead of accessing it via rsh. This indeed solves the problem. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 11:36:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 4CB2C37B9E5 for ; Tue, 28 Mar 2000 11:36:37 -0800 (PST) (envelope-from rb@gid.co.uk) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id UAA25598; Tue, 28 Mar 2000 20:36:02 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id UAA16671; Tue, 28 Mar 2000 20:09:29 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <200003281752.JAA52954@apollo.backplane.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 28 Mar 2000 20:09:29 +0100 To: Matthew Dillon From: Bob Bishop Subject: Re: SMP kernel broken at cvsup Tue Mar 28 11:56:07 BST 2000 Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:52 -0800 28/3/00, Matthew Dillon wrote: > Make sure you haven't confused it between the patch set and the > commit I made last night. Do a cvs update and then a cvs diff to > make sure things haven't gotten confused. Just blew /sys away and checked it out afresh. Same result I'm afraid, although I did get into DDB this time. Nothing obviously wrong, but the backtrace didn't go back past the keyboard interrupt. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 11:41:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from dead-end.net (dead-end.net [216.15.131.2]) by hub.freebsd.org (Postfix) with ESMTP id BD2A937C021 for ; Tue, 28 Mar 2000 11:41:00 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.131.2]) by dead-end.net (8.9.3/DEAD-END/2000013000-Deliver) with ESMTP id VAA65885 for ; Tue, 28 Mar 2000 21:40:59 +0200 (CEST) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9E0EA8.dip.t-dialin.net [62.158.14.168]) by mailto.dead-end.net (8.9.3/DEAD-END/2000013000-Customer) with ESMTP id VAA65880 for ; Tue, 28 Mar 2000 21:40:55 +0200 (CEST) (envelope-from rock@dead-end.net) Received: from dead-end.net (server [172.23.7.1]) by server.rock.net (8.9.3+Sun/8.9.3) with ESMTP id VAA29533 for ; Tue, 28 Mar 2000 21:38:52 +0200 (MEST) Message-ID: <38E10A4B.129A7C27@dead-end.net> Date: Tue, 28 Mar 2000 21:38:51 +0200 From: "D. Rock" X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.8 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: current@freebsd.org Subject: Resource allocation error in new pnp code Content-Type: multipart/mixed; boundary="------------53A353B57F098AF27051730B" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------53A353B57F098AF27051730B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I already mentioned this bug a few months ago but didn't got a reply. Maybe I'm the only one who is affected by this bug. I have several PnP cards in my system (see attached output of pnpinfo). Especially one card requests a resource: I/O Range 0x100 .. 0x3ff, alignment 0x1, len 0x1 [16-bit addr] My ISDN controller also requests a resource from this range: I/O Range 0x100 .. 0x3f0, alignment 0x8, len 0x8 [not 16-bit addr] Now the following happens: first card gets assigned: Mar 28 21:12:00 gate /kernel: unknown10: at port 0x100 on isa0 and the ISDN card gets assigned: Mar 28 21:12:00 gate /kernel: isic0: at port 0x101-0x108 irq 11 on isa0 which is wrong since it requests an alignment of 8. The code in /sys/isa/isa_common.c, which should prevent this is useless, since most work is done in /sys/kern/subr_rman.c which automatically tries to find an alternate region, but without honouring any alignment. Also attached is my (ugly) hack for this problem, but I think the problem should be addressed elsewhere (in the resource manager), since it may affect any type of resource allocation which requires different alignment. -- Daniel --------------53A353B57F098AF27051730B Content-Type: text/plain; charset=us-ascii; name="pnpinfo" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="pnpinfo" Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID AZT3002 (0x02305407), Serial Number 0xffffffff PnP Version 1.0, Vendor Version 1 Device Description: AZT3002 PnP SOUND DEVICE Logical Device ID: AZT0500 0x00055407 #0 Device supports I/O Range Check Device Description: IDE CDROM DISABLED TAG Start DF Good Configuration I/O Range 0x0 .. 0x0, alignment 0x8, len 0x0 [16-bit addr] I/O Range 0x0 .. 0x0, alignment 0x2, len 0x0 [16-bit addr] IRQ: IRQ: High true edge sensitive TAG End DF Logical Device ID: AZT1004 0x04105407 #1 Device supports I/O Range Check Device Description: AUDIO TAG Start DF Good Configuration I/O Range 0x220 .. 0x220, alignment 0x10, len 0x10 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x8, len 0x8 [16-bit addr] I/O Range 0x534 .. 0x534, alignment 0x4, len 0x4 [16-bit addr] IRQ: 5 IRQ: High true edge sensitive DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 3 8-bit, not a bus master, count by byte, , Compatibility mode TAG Start DF I/O Range 0x220 .. 0x240, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x8, len 0x8 [16-bit addr] I/O Range 0x534 .. 0x608, alignment 0xd4, len 0x4 [16-bit addr] IRQ: 5 9 10 IRQ: High true edge sensitive DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode TAG Start DF I/O Range 0x220 .. 0x240, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x8, len 0x8 [16-bit addr] I/O Range 0xe84 .. 0xf44, alignment 0xc0, len 0x4 [16-bit addr] IRQ: 5 9 10 IRQ: High true edge sensitive DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode TAG Start DF I/O Range 0x100 .. 0x3f0, alignment 0x10, len 0x10 [16-bit addr] I/O Range 0x100 .. 0x3f8, alignment 0x8, len 0x8 [16-bit addr] I/O Range 0x100 .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] IRQ: 5 9 10 11 15 IRQ: High true edge sensitive DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode TAG Start DF I/O Range 0x100 .. 0x3f0, alignment 0x10, len 0x10 [16-bit addr] I/O Range 0x100 .. 0x3f8, alignment 0x8, len 0x8 [16-bit addr] I/O Range 0x100 .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] IRQ: 5 9 10 11 15 IRQ: High true edge sensitive DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode TAG End DF Logical Device ID: AZT2001 0x01205407 #2 Device supports I/O Range Check Device Description: MPU401 MIDI TAG Start DF Good Configuration I/O Range 0x330 .. 0x330, alignment 0x2, len 0x2 [16-bit addr] IRQ: 9 IRQ: High true edge sensitive TAG Start DF I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] IRQ: 5 9 10 11 15 IRQ: High true edge sensitive TAG Start DF I/O Range 0x100 .. 0x3fe, alignment 0x2, len 0x2 [16-bit addr] IRQ: 5 9 10 11 15 IRQ: High true edge sensitive TAG End DF Logical Device ID: AZT3001 0x01305407 #3 Device supports I/O Range Check Device Description: GAME PORT TAG Start DF Good Configuration I/O Range 0x200 .. 0x200, alignment 0x8, len 0x8 [16-bit addr] TAG Start DF I/O Range 0x208 .. 0x208, alignment 0x8, len 0x8 [16-bit addr] TAG End DF Logical Device ID: AZT4003 0x03405407 #4 Device supports I/O Range Check Device Description: MODEM TAG Start DF Good Configuration I/O Range 0x3e8 .. 0x3e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 4 5 9 10 11 15 IRQ: High true edge sensitive TAG Start DF I/O Range 0x2f8 .. 0x2f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 IRQ: High true edge sensitive TAG Start DF I/O Range 0x3f8 .. 0x3f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 4 5 9 10 11 15 IRQ: High true edge sensitive TAG Start DF I/O Range 0x2e8 .. 0x2e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 4 5 9 10 11 15 IRQ: High true edge sensitive TAG Start DF I/O Range 0x100 .. 0x3f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 4 5 9 10 11 15 IRQ: High true edge sensitive TAG End DF Logical Device ID: AZT5001 0x01505407 #5 Device supports I/O Range Check Device Description: EEPROM TAG Start DF Good Configuration I/O Range 0x100 .. 0x3ff, alignment 0x1, len 0x1 [16-bit addr] TAG End DF End Tag Successfully got 88 resources, 6 logical fdevs -- card select # 0x0001 CSN AZT3002 (0x02305407), Serial Number 0xffffffff Logical device #0 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x00 Logical device #1 IO: 0x0388 0x0388 0x0388 0x0388 0x0388 0x0388 0x0388 0x0388 IRQ 5 0 DMA 0 1 IO range check 0x00 activate 0x01 Logical device #2 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 9 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #3 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #4 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 10 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #5 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 Card assigned CSN #2 Vendor ID SAG0001 (0x0100274c), Serial Number 0x050044b0 PnP Version 1.0, Vendor Version 1 Device Description: speed win SEDLBAUER AG Logical Device ID: SAG0001 0x0100274c #0 Device supports I/O Range Check TAG Start DF I/O Range 0x100 .. 0x3f0, alignment 0x8, len 0x8 [not 16-bit addr] IRQ: 3 4 5 7 10 11 12 13 15 - only one type (true/edge) TAG Start DF I/O Range 0x100 .. 0x3f0, alignment 0x8, len 0x8 [not 16-bit addr] IRQ: 5 - only one type (true/edge) TAG Start DF I/O Range 0x100 .. 0x3f0, alignment 0x8, len 0x8 [not 16-bit addr] IRQ: 7 - only one type (true/edge) TAG End DF End Tag Successfully got 13 resources, 1 logical fdevs -- card select # 0x0002 CSN SAG0001 (0x0100274c), Serial Number 0x050044b0 Logical device #0 IO: 0x0108 0x0108 0x0108 0x0108 0x0108 0x0108 0x0108 0x0108 IRQ 11 0 DMA 4 0 IO range check 0x00 activate 0x01 --------------53A353B57F098AF27051730B Content-Type: text/plain; charset=us-ascii; name="isa_common.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="isa_common.diff" Index: isa_common.c =================================================================== RCS file: /data/cvs/src/sys/isa/isa_common.c,v retrieving revision 1.16 diff -u -r1.16 isa_common.c --- isa_common.c 2000/02/11 04:35:07 1.16 +++ isa_common.c 2000/03/28 19:26:44 @@ -207,6 +207,13 @@ SYS_RES_IOPORT, &i, 0, ~0, 1, 0 /* !RF_ACTIVE */); if (res[i]) { + /* HACK */ + if(res[i]->r_start != start) { + bus_release_resource(child, + SYS_RES_IOPORT, i, + res[i]); + continue; + } result->ic_port[i].ir_start = start; result->ic_port[i].ir_end = start + size - 1; result->ic_port[i].ir_size = size; --------------53A353B57F098AF27051730B-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 11:53:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from goku.cl.msu.edu (goku.cl.msu.edu [35.8.3.20]) by hub.freebsd.org (Postfix) with ESMTP id 5F84E37BFF3 for ; Tue, 28 Mar 2000 11:53:46 -0800 (PST) (envelope-from dervish@goku.cl.msu.edu) Received: (from dervish@localhost) by goku.cl.msu.edu (8.9.3/8.9.3) id OAA86780 for freebsd-current@freebsd.org; Tue, 28 Mar 2000 14:53:45 -0500 (EST) (envelope-from dervish) Date: Tue, 28 Mar 2000 14:53:45 -0500 From: Bush Doctor To: freebsd-current@freebsd.org Subject: Warnings when linking against libc_r Message-ID: <20000328145345.B41117@goku.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Operating-System: FreeBSD 5.0-CURRENT i386 WWW-Home-Page: http://bantu.cl.msu.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm seeing the following diagnostics with applications linked against libc_r cc -O -pipe -I/usr/local/include -D_REENTRANT -D_THREAD_SAFE -g -Wall -o .libs/structs structs.o -L/usr/local/lib ../../ggi/.libs/libggi.so -lc_r /usr/local/lib/libgg.so /usr/local/lib/libgii.so -Wl,--rpath -Wl,/usr/local/lib /usr/lib/libc.so: warning: tmpnam() possibly used unsafely; consider using mkstemp() /usr/lib/libc.so: warning: tempnam() possibly used unsafely; consider using mkstemp() /usr/lib/libc.so: warning: this program uses gets(), which is unsafe. /usr/lib/libc.so: WARNING! setkey(3) not present in the system! /usr/lib/libc.so: WARNING! des_setkey(3) not present in the system! /usr/lib/libc.so: WARNING! encrypt(3) not present in the system! /usr/lib/libc.so: WARNING! des_cipher(3) not present in the system! /usr/lib/libc.so: warning: mktemp() possibly used unsafely; consider using mkstemp() /usr/lib/libc.so: warning: this program uses f_prealloc(), which is stupid. Can these be ignored? From what I gathered from the mailing list archives this issue has reared its head before. goku.cl.msu.edu:dervish> uname -a FreeBSD goku.cl.msu.edu 5.0-CURRENT FreeBSD 5.0-CURRENT #33: Tue Mar 14 11:25:48 EST 2000 root@goku.cl.msu.edu:/usr/src/sys/compile/GOKU i386 #;^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 12: 7:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from hurricane.columbus.rr.com (m5.columbus.rr.com [204.210.252.249]) by hub.freebsd.org (Postfix) with ESMTP id B51D037BFC8 for ; Tue, 28 Mar 2000 12:07:31 -0800 (PST) (envelope-from caa@columbus.rr.com) Received: from columbus.rr.com ([204.210.243.142]) by hurricane.columbus.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com; Tue, 28 Mar 2000 15:07:35 -0500 Received: (from caa@localhost) by columbus.rr.com (8.9.3/8.9.3) id PAA28342; Tue, 28 Mar 2000 15:07:29 -0500 (EST) (envelope-from caa) Date: Tue, 28 Mar 2000 15:07:23 -0500 From: "Charles Anderson" To: NAKAJI Hiroyuki Cc: current@FreeBSD.ORG Subject: Re: Please test for 8G-OVER-Booting with /boot/loader Message-ID: <20000328150723.A28294@midgard.dhs.org> References: <87n1njbrfj.fsf@nakaji.tutrp.tut.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <87n1njbrfj.fsf@nakaji.tutrp.tut.ac.jp>; from nakaji@tutrp.tut.ac.jp on Tue, Mar 28, 2000 at 02:21:36PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a Thinkpad 600X here that I installed freebsd on the third partition, but couldn't boot because of the >1024 cylinder bit, so I booted a Fixit floppy mounted my freebsd partitions, installed this patch, patched boot1 to always try packet mode and copied it over to the ntfs boot partition and used it from the NT Loader, and it booted right up, both natively and under VMware. I had to do a lot of mucking around to get things to the point where I could mount slice 3, the FreeBSD partition, and build the new boot code. -Charlie On Tue, Mar 28, 2000 at 02:21:36PM +0900, NAKAJI Hiroyuki wrote: > How can I test this with FreeBSD which is installed over-8GB area and > can't boot? > > I have a PC on which Solaris7 is installed within 8GB from the start > of disk and FreeBSD 3.3-RELEASE is installed after(?) it. > > The installation was successfull. But I can't boot it. > > How can I install this patched /boot/loader in this dead system? > -- > NAKAJI Hiroyuki > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Charles Anderson caa@columbus.rr.com No quote, no nothin' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 12:41:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 078AD37B59F; Tue, 28 Mar 2000 12:41:38 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id MAA38160; Tue, 28 Mar 2000 12:41:37 -0800 (PST) (envelope-from Doug@gorean.org) Date: Tue, 28 Mar 2000 12:41:37 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: Kris Kennaway Cc: freebsd-current@FreeBSD.org, Peter Wemm Subject: Re: cvs repository nits and gnats 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 Thanks for the response... On Tue, 28 Mar 2000, Kris Kennaway wrote: > On Tue, 28 Mar 2000, Doug Barton wrote: > > > src/TODO-2.1, src/usr.sbin/xntpd, etc. There were a large number in > > contrib, probably detritus from imports, etc. I'm not sure if this is > > significant, it obviously doesn't do any harm. I just thought I'd > > mention it. > > CVS has no concept of removing a directory Hrrmm... cool! I've always used the -P option, so I've not seen this before. Having always been a "customer" of cvs rather than an administrator I'm learning new things at a rapid pace. > > Slightly more serious was the presence of various lock > > files/directories. Specifically, one in src/games/primes killed my co as > > an unpriviliged user because it was set 700 and owned by root. The co > > failed because it couldn't create a lock file. I did a 'find . -name > > \*\#\* in my CVSROOT and found several other files like this. Deleting > > them did no harm, and they didn't return when I ran cvsup again. > > I havent seen this. My gut feeling is that it's a timing issue. I happened to have been cvsup'ing when someone actually had a lock on something in the repository. Still I think it's odd that A) the cvsup "mirrors" of the master repository picked up these files, B) that my cvsup of the repository picked them up, and C) having picked them up, it didn't delete them when they were deleted from the real respository. FWIW, I always use cvsup7, and I found these lock files in both my home and work copies. > I ran into this the other day and was advised to mount the CVS repository > via NFS instead of accessing it via rsh. This indeed solves the problem. Yes, that's what I do everywhere _else_, but this particular machine's network position within our firewall makes that impossible at this time. We've outgrown a class C for our internal machines so we're blending a new one in and haven't gotten all the filtering in place yet. rsh was one "hole" that was available to me, and with proper wrapping it's pretty safe on our internal network. Thanks, Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 13:23:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from nscache2.x-treme.gr (mail1.x-treme.gr [212.120.196.23]) by hub.freebsd.org (Postfix) with ESMTP id 62AE937B89E for ; Tue, 28 Mar 2000 13:23:21 -0800 (PST) (envelope-from keramida@diogenis.ceid.upatras.gr) Received: from hades.hell.gr (pat12.x-treme.gr [212.120.197.204]) by nscache2.x-treme.gr (8.9.3/8.9.3/IPNG-ADV-ANTISPAM-0.1) with SMTP id AAA25998 for ; Wed, 29 Mar 2000 00:23:10 +0300 Received: (qmail 1423 invoked by uid 1001); 28 Mar 2000 16:49:23 -0000 Date: Tue, 28 Mar 2000 19:49:23 +0300 From: Giorgos Keramidas To: current@freebsd.org Subject: periodic daily output (passwd diffs) Message-ID: <20000328194923.A1376@hades.hell.gr> Reply-To: keramida@ceid.upatras.gr Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-PGP-Fingerprint: 62 45 D1 C9 26 F9 95 06 D6 21 2A C8 8C 16 C0 8E Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I changed my passwords from DES to MD5, I noticed this little thing with periodic daily output. Backup passwd and group files: passwd diffs: 1,2c1,2 < root:(password):0:0::0:0:Superuser:/root:/bin/csh < toor:(password):0:0::0:0:Bourne-again Superuser:/root:/usr/local/bin/bash --- > root:(password):0:0::0:0:Superuser:/root:/bin/csh > toor:(password):0:0::0:0:Bourne-again Superuser:/root:/usr/local/bin/bash At first glimpse, everything seems identical.. so, where is the difference? I realized that I had changed ONLY the password, and this was shown in the diffs in this strange way--since the password is clipped from the output of diff. Is this done on purpose, to show who has changed their password, or is it a side-effect of the way things are done until now, and we should attempt to change it some time? -- Giorgos Keramidas, < keramida @ ceid . upatras . gr> See the headers of this message for my public key fingeprint. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 13:39:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 061BA37BB34 for ; Tue, 28 Mar 2000 13:39:43 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id XAA05281 for ; Tue, 28 Mar 2000 23:37:55 +0200 (CEST) Message-Id: <200003282137.XAA05281@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: freebsd-current@freebsd.org Subject: UP kernel performance and Matt Dillon's patches From: Gary Jennejohn Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Mar 2000 23:37:55 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running a UP machine with Matt's latest changes. I was just compiling a new kernel and noticed the my PS/2 mouse under X was very sluggish. I never noticed this sort of behavior before the changes, even while doing ``make -j8 buildworld''. The compile was running on a UW SCSI disk on an Adaptec aic7880 Ultra SCSI adapter on my motherboard, in case it matters. Looks like something has been verschlimmbessert (a wonderful German word which means "made worse through improvement" :) -------- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@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 Mar 28 13:45: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcat.heimat.gr.jp (pcat.heimat.gr.jp [211.0.53.98]) by hub.freebsd.org (Postfix) with ESMTP id 79AF837BF0A for ; Tue, 28 Mar 2000 13:44:54 -0800 (PST) (envelope-from nakaji@tutrp.tut.ac.jp) Received: from xa12.heimat.gr.jp (xa12.heimat.gr.jp [211.0.53.97]) by pcat.heimat.gr.jp (8.9.3/3.7W) with ESMTP id GAA60719; Wed, 29 Mar 2000 06:44:38 +0900 (JST) To: "Charles Anderson" Cc: current@FreeBSD.ORG Subject: Re: Please test for 8G-OVER-Booting with /boot/loader References: <87n1njbrfj.fsf@nakaji.tutrp.tut.ac.jp> <20000328150723.A28294@midgard.dhs.org> X-Face: %kq${$)eD!'Uqm"eT(;zJP3.K&t\N%V+;k,htw)'ucAj<"yAIE7sv`8j_9k1sKoQzXiH5i( M`cHG,^.l}h/l:-eGB\f[b+*C`>{=}E?+}L6U99;'.%0jaa8as]_i02^:zexCUr+&+Gv7_%>@ XiR,wQyBL}LMF)oX+y`4w;m$;,F9QPMwqm@F@ibzi9K<0U]:QBb8|jaob7)`2ayeF&!Ci~4IQw:5^1 BS3&;K MIME-Version: 1.0 (generated by REMI 1.14.1 - =?ISO-8859-4?Q?=22Mushigawa=F2?= =?ISO-8859-4?Q?sugi=22?=) Content-Type: text/plain; charset=US-ASCII From: NAKAJI Hiroyuki Date: 29 Mar 2000 06:44:37 +0900 In-Reply-To: <20000328150723.A28294@midgard.dhs.org> (Charles Anderson's message of "Tue, 28 Mar 2000 15:07:23 -0500") Message-ID: <867lemahx6.fsf@xa12.heimat.gr.jp> Lines: 15 User-Agent: T-gnus/6.14.1 (based on Gnus v5.8.3) (revision 16) REMI/1.14.1 (=?ISO-8859-4?Q?Mushigawa=F2sugi?=) Chao/1.14.1 (=?ISO-8859-4?Q?Rokujiz?= =?ISO-8859-4?Q?=F2?=) APEL/10.2 MULE XEmacs/21.2 (beta32) (Kastor & Polydeukes) (i386--freebsd) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks, Charlie. >>>>> In <20000328150723.A28294@midgard.dhs.org> >>>>> "Charles Anderson" wrote: C> I have a Thinkpad 600X here that I installed freebsd on the third C> partition, but couldn't boot because of the >1024 cylinder bit, so C> I booted a Fixit floppy mounted my freebsd partitions, installed C> this patch, patched boot1 to always try packet mode and copied it C> over to the ntfs boot partition and used it from the NT Loader, and C> it booted right up, both natively and under VMware. I'll try. This is my first time to use Fixit floppy. :) -- NAKAJI Hiroyuki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 14:18:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from holly.calldei.com (adsl-208-191-146-189.dsl.hstntx.swbell.net [208.191.146.189]) by hub.freebsd.org (Postfix) with ESMTP id DE5EC37BEB7 for ; Tue, 28 Mar 2000 14:18:20 -0800 (PST) (envelope-from chris@holly.calldei.com) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id QAA42358; Tue, 28 Mar 2000 16:18:14 -0600 (CST) (envelope-from chris) Date: Tue, 28 Mar 2000 16:18:13 -0600 From: Chris Costello To: Bush Doctor Cc: freebsd-current@FreeBSD.ORG Subject: Re: Warnings when linking against libc_r Message-ID: <20000328161813.Q18325@holly.calldei.com> Reply-To: chris@calldei.com References: <20000328145345.B41117@goku.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i In-Reply-To: <20000328145345.B41117@goku.cl.msu.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, March 28, 2000, Bush Doctor wrote: > I'm seeing the following diagnostics with applications linked against libc_r ... Do not directly link with libc_r. Instead, use the -pthread gcc flag. It will properly compile and link your program with the correct thread bits. -- |Chris Costello |I/O, I/O, it's off to work we go... `------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 14:22:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from holly.calldei.com (adsl-208-191-146-189.dsl.hstntx.swbell.net [208.191.146.189]) by hub.freebsd.org (Postfix) with ESMTP id 25B8737BE37 for ; Tue, 28 Mar 2000 14:22:08 -0800 (PST) (envelope-from chris@holly.calldei.com) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id QAA42414; Tue, 28 Mar 2000 16:21:46 -0600 (CST) (envelope-from chris) Date: Tue, 28 Mar 2000 16:21:46 -0600 From: Chris Costello To: Wm Brian McCane Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: kernel trap 9 Message-ID: <20000328162145.R18325@holly.calldei.com> Reply-To: chris@calldei.com References: <200003281146.GAA87302@server.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, March 28, 2000, Wm Brian McCane wrote: > Fatal trap 9: general protection fault in kernel mode > Why did you remove the vital information needed to track down and fix the problem? -- |Chris Costello |A paperless office has about as much chance as a paperless bathroom. `-------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 14:22:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 1305E37BED8 for ; Tue, 28 Mar 2000 14:22:39 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2SMl1c16291; Tue, 28 Mar 2000 14:47:01 -0800 (PST) Date: Tue, 28 Mar 2000 14:47:01 -0800 From: Alfred Perlstein To: Gary Jennejohn Cc: freebsd-current@FreeBSD.ORG Subject: Re: UP kernel performance and Matt Dillon's patches Message-ID: <20000328144701.G21029@fw.wintelcom.net> References: <200003282137.XAA05281@peedub.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003282137.XAA05281@peedub.muc.de>; from garyj@muc.de on Tue, Mar 28, 2000 at 11:37:55PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Gary Jennejohn [000328 14:04] wrote: > I'm running a UP machine with Matt's latest changes. I was just > compiling a new kernel and noticed the my PS/2 mouse under X was very > sluggish. I never noticed this sort of behavior before the changes, > even while doing ``make -j8 buildworld''. > > The compile was running on a UW SCSI disk on an Adaptec aic7880 Ultra > SCSI adapter on my motherboard, in case it matters. > > Looks like something has been verschlimmbessert (a wonderful German > word which means "made worse through improvement" :) This is unlikely as a UP kernel doesn't seem to compile after Matt's changes (no offence Matt, I know you're getting to it), when was the last time you didn't see this sluggish behavior, how are you compiling your kernel? What's your Id line for sys/i386/i386/mplock.s ? Mine is: * $FreeBSD: src/sys/i386/i386/mplock.s,v 1.30 2000/03/28 07:16:15 dillon Exp $ -- -Alfred Perlstein - [bright@wintelcom.net|alfred@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 Mar 28 14:51:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 4471F37C0DD for ; Tue, 28 Mar 2000 14:51:43 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id AAA00582; Wed, 29 Mar 2000 00:49:47 +0200 (CEST) Message-Id: <200003282249.AAA00582@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: Alfred Perlstein Cc: freebsd-current@FreeBSD.ORG Subject: Re: UP kernel performance and Matt Dillon's patches Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 29 Mar 2000 00:22:38 +0200." <20000328144701.G21029@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Mar 2000 00:49:47 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: >* Gary Jennejohn [000328 14:04] wrote: >> I'm running a UP machine with Matt's latest changes. I was just >> compiling a new kernel and noticed the my PS/2 mouse under X was very >> sluggish. I never noticed this sort of behavior before the changes, >> even while doing ``make -j8 buildworld''. >> >> The compile was running on a UW SCSI disk on an Adaptec aic7880 Ultra >> SCSI adapter on my motherboard, in case it matters. >> >> Looks like something has been verschlimmbessert (a wonderful German >> word which means "made worse through improvement" :) > >This is unlikely as a UP kernel doesn't seem to compile after Matt's >changes (no offence Matt, I know you're getting to it), when was >the last time you didn't see this sluggish behavior, how are you >compiling your kernel? > >What's your Id line for sys/i386/i386/mplock.s ? > >Mine is: > * $FreeBSD: src/sys/i386/i386/mplock.s,v 1.30 2000/03/28 07:16:15 dillon Exp >$ > I have * $FreeBSD: src/sys/i386/i386/mplock.s,v 1.31 2000/03/28 18:06:37 dillon Exp $ Matt fixed the bug which was preventing compilng a UP kernel. So I guess it is likely, after all. --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@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 Mar 28 15:29:13 2000 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 ED68937C087 for ; Tue, 28 Mar 2000 15:28:56 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac4.wam.umd.edu (root@rac4.wam.umd.edu [128.8.10.144]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id SAA25979; Tue, 28 Mar 2000 18:28:31 -0500 (EST) Received: from rac4.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id SAA20437; Tue, 28 Mar 2000 18:28:34 -0500 (EST) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA20433; Tue, 28 Mar 2000 18:28:33 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Tue, 28 Mar 2000 18:28:33 -0500 (EST) From: Kenneth Wayne Culver To: Gary Jennejohn Cc: Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: UP kernel performance and Matt Dillon's patches In-Reply-To: <200003282249.AAA00582@peedub.muc.de> 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 havn't noticed this behavior... or any other performance hits and I'm running a kernel that was cvsupped about 5 10 minutes ago.. and recompiled about 5 minutes ago... ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Wed, 29 Mar 2000, Gary Jennejohn wrote: > Alfred Perlstein writes: > >* Gary Jennejohn [000328 14:04] wrote: > >> I'm running a UP machine with Matt's latest changes. I was just > >> compiling a new kernel and noticed the my PS/2 mouse under X was very > >> sluggish. I never noticed this sort of behavior before the changes, > >> even while doing ``make -j8 buildworld''. > >> > >> The compile was running on a UW SCSI disk on an Adaptec aic7880 Ultra > >> SCSI adapter on my motherboard, in case it matters. > >> > >> Looks like something has been verschlimmbessert (a wonderful German > >> word which means "made worse through improvement" :) > > > >This is unlikely as a UP kernel doesn't seem to compile after Matt's > >changes (no offence Matt, I know you're getting to it), when was > >the last time you didn't see this sluggish behavior, how are you > >compiling your kernel? > > > >What's your Id line for sys/i386/i386/mplock.s ? > > > >Mine is: > > * $FreeBSD: src/sys/i386/i386/mplock.s,v 1.30 2000/03/28 07:16:15 dillon Exp > >$ > > > > I have > * $FreeBSD: src/sys/i386/i386/mplock.s,v 1.31 2000/03/28 18:06:37 dillon Exp $ > Matt fixed the bug which was preventing compilng a UP kernel. So I guess it > is likely, after all. > > --- > Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 15:34:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.hcisp.net (Stargate.hcisp.net [208.60.89.18]) by hub.freebsd.org (Postfix) with SMTP id 46E0337C04B for ; Tue, 28 Mar 2000 15:34:31 -0800 (PST) (envelope-from tim@mysql.com) Received: (qmail 2404 invoked from network); 28 Mar 2000 23:40:37 -0000 Received: from modem10.hcisp.net (HELO threads.polyesthetic.msg) (208.60.89.76) by stargate.hcisp.net with SMTP; 28 Mar 2000 23:40:37 -0000 Received: (qmail 4161 invoked by uid 1001); 28 Mar 2000 23:33:41 -0000 From: "Thimble Smith" Date: Tue, 28 Mar 2000 18:33:41 -0500 To: Giorgos Keramidas Cc: current@FreeBSD.ORG Subject: Re: periodic daily output (passwd diffs) Message-ID: <20000328183341.E3878@threads.polyesthetic.msg> References: <20000328194923.A1376@hades.hell.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000328194923.A1376@hades.hell.gr>; from keramida@ceid.upatras.gr on Tue, Mar 28, 2000 at 07:49:23PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 28, 2000 at 07:49:23PM +0300, Giorgos Keramidas wrote: >At first glimpse, everything seems identical.. so, where is the >difference? I realized that I had changed ONLY the password, and this >was shown in the diffs in this strange way--since the password is >clipped from the output of diff. It's on purpose. The password is masked out for obvious reasons. Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 16:13:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust1.tnt3.waldorf.md.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 4867337B598; Tue, 28 Mar 2000 16:13:36 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Tue, 28 Mar 2000 19:13:34 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Jeroen Ruigrok van der Werven Cc: Sheldon Hearn , Soren Schmidt , current@FreeBSD.ORG Subject: Re: DDB and dumping disk In-Reply-To: <20000328132626.F94986@lucifer.bart.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 Tue, 28 Mar 2000, Jeroen Ruigrok van der Werven wrote: > Your patch is a step in the right direction. > > I am currently only trying to figure out why the DDB way doesn't trigger > savecore to recognise the dump. Did you try "call setdumpdev(0xf00)" with the proper show disk/ yet? It's probably worth documenting the procedure even if it will be later be replaced with a loader functionality... however, we should still support the way it is now for people who want to get a dump but don't have the ability to use loader(8) fully (Alpha?). > -- > Jeroen Ruigrok van der Werven Network- and systemadministrator > VIA NET.WORKS The Netherlands > BSD: Technical excellence at its best http://www.bart.nl > How are the mighty fallen... -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 Mar 28 16:15: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id 9BA5437B50F for ; Tue, 28 Mar 2000 16:15:04 -0800 (PST) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id TAA25263; Tue, 28 Mar 2000 19:48:02 -0500 (EST) (envelope-from dervish) Date: Tue, 28 Mar 2000 19:48:02 -0500 From: bush doctor To: Chris Costello Cc: freebsd-current@FreeBSD.ORG Subject: Re: Warnings when linking against libc_r Message-ID: <20000328194802.A91057@ikhala.tcimet.net> References: <20000328145345.B41117@goku.cl.msu.edu> <20000328161813.Q18325@holly.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000328161813.Q18325@holly.calldei.com>; from chris@calldei.com on Tue, Mar 28, 2000 at 04:18:13PM -0600 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of da blue Chris Costello aka (chris@calldei.com) said: > On Tuesday, March 28, 2000, Bush Doctor wrote: > > I'm seeing the following diagnostics with applications linked against libc_r > ... > > Do not directly link with libc_r. Instead, use the -pthread > gcc flag. It will properly compile and link your program with > the correct thread bits. Thanxs Chris. If this was discussed on -current, I apologise for missing the discussion. :( A question why can we not link directly with libc_r? If this was discussed on -current I can look it up in the archives. Looks like gnats will be seeing some send-pr's about this. Thanxs again! > > -- > |Chris Costello > |I/O, I/O, it's off to work we go... > `------------------------------------ > #;^) -- So ya want ta hear da roots? bush doctor Of course I run FreeBSD!! 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 Mar 28 16:20: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id 456A137BB6A for ; Tue, 28 Mar 2000 16:19:59 -0800 (PST) (envelope-from carl@xena.aipo.gov.au) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id KAA75313 for ; Wed, 29 Mar 2000 10:19:56 +1000 (EST) (envelope-from carl@xena.aipo.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma075274; Wed, 29 Mar 00 10:19:20 +1000 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.9.3/8.9.3) with ESMTP id KAA91725 for ; Wed, 29 Mar 2000 10:21:03 +1000 (EST) (envelope-from carl@xena.aipo.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Wed, 29 Mar 2000 10:21:03 +1000 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: current@freebsd.org Subject: Dual Pathing to SCSI/FC devices. 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 Is anyone working on/considering this? I'm about to start hooking FreeBSD boxes up to a *big* disk array which has the ability to make LUNS appear on multiple interfaces. Being able to access LUNS via multiple paths could be a reasonable performance gain, as well as enhancing reliability. Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 16:28:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id D831A37B52E; Tue, 28 Mar 2000 16:28:05 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA61245; Wed, 29 Mar 2000 01:20:46 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA03124; Wed, 29 Mar 2000 01:20:43 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200003290020.BAA03124@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Maxim Sobolev Cc: current@FreeBSD.ORG, brian@FreeBSD.ORG, brian@hak.lan.awfulhak.org Subject: Re: Strange new ppp warnings In-Reply-To: Message from Maxim Sobolev of "Tue, 28 Mar 2000 21:02:15 +0300." <38E0F3A6.87231410@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Mar 2000 01:20:42 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > After upgrading my box to the 4.0-STABLE, I've discovered that ppp started > produce regular warnings I've never seen before: > > Warning: nat_LayerPull: Dropped a packet.... > > What does it mean and what implications may it have? This is pretty strange. I've just added a diagnostic to nat_LayerPull(). Can you update your sources (or get the latest archive from my web site in about an hour) and tell me what return value it's receiving ? The error shouldn't happen.... > -Maxim Thanks. -- 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 Tue Mar 28 16:28:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A61B737BBCE for ; Tue, 28 Mar 2000 16:28:55 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA08312; Tue, 28 Mar 2000 16:28:29 -0800 Date: Tue, 28 Mar 2000 16:28:39 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Carl Makin Cc: current@FreeBSD.ORG Subject: Re: Dual Pathing to SCSI/FC devices. 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 Yes, we very much has considered this. What's your issue about this, per se? Right now there's no framework code to directly exploit or prohibit multiple paths to the same disk, whether via Fibre Channel or SCSI. On Wed, 29 Mar 2000, Carl Makin wrote: > > Is anyone working on/considering this? > > I'm about to start hooking FreeBSD boxes up to a *big* disk array which > has the ability to make LUNS appear on multiple interfaces. Being able to > access LUNS via multiple paths could be a reasonable performance gain, as > well as enhancing reliability. > > > Carl. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 16:48:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id C725C37BBD7 for ; Tue, 28 Mar 2000 16:48:08 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id TAA365402; Tue, 28 Mar 2000 19:47:40 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20000328183341.E3878@threads.polyesthetic.msg> References: <20000328194923.A1376@hades.hell.gr> <20000328183341.E3878@threads.polyesthetic.msg> Date: Tue, 28 Mar 2000 19:48:13 -0500 To: "Thimble Smith" , Giorgos Keramidas From: Garance A Drosihn Subject: Re: periodic daily output (passwd diffs) Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:33 PM -0500 3/28/00, Thimble Smith wrote: >On Tue, Mar 28, 2000 at 07:49:23PM +0300, Giorgos Keramidas wrote: > >At first glimpse, everything seems identical.. so, where is the > >difference? I realized that I had changed ONLY the password, and this > >was shown in the diffs in this strange way--since the password is > >clipped from the output of diff. > >It's on purpose. The password is masked out for obvious reasons. yes, but it would be nice if the masking out process noticed if a password changed, and did something like "(oldpw)" "(newpw)" when masking out lines with password changes. (the literal strings, "oldpw" and "newpw"...). my guess is that's easier said than done, but still it would be nice if it WERE done... :-) --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 16:56:50 2000 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 DAD5737B50E for ; Tue, 28 Mar 2000 16:56:47 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (loot.cs.rpi.edu [128.213.16.22]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id TAA86382; Tue, 28 Mar 2000 19:56:46 -0500 (EST) Message-Id: <200003290056.TAA86382@cs.rpi.edu> To: freebsd-current@freebsd.org Cc: crossd@cs.rpi.edu Subject: Major # please :) Date: Tue, 28 Mar 2000 19:45:04 -0500 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am just about finished with a device driver for PCI DIO boards based around the 8C255 (number may be wrong ;). Specifically this is for the ComputerBoards DIO-24H DIO board. I have been using the 'development' major #, and I am ready to go about getting it committed into the CVS tree for whoever else may find it of use. Currently the system is used in conjunction with a home-brew card-access system, but future could include robotics and related fields. Thank you -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD 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 Tue Mar 28 16:58: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id 5C50137B50E for ; Tue, 28 Mar 2000 16:58:00 -0800 (PST) (envelope-from carl@xena.aipo.gov.au) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id KAA77395; Wed, 29 Mar 2000 10:57:53 +1000 (EST) (envelope-from carl@xena.aipo.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma077391; Wed, 29 Mar 00 10:57:47 +1000 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.9.3/8.9.3) with ESMTP id KAA91824; Wed, 29 Mar 2000 10:59:29 +1000 (EST) (envelope-from carl@xena.aipo.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Wed, 29 Mar 2000 10:59:29 +1000 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: Matthew Jacob Cc: current@FreeBSD.ORG Subject: Re: Dual Pathing to SCSI/FC devices. 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 Hi Matthew, On Tue, 28 Mar 2000, Matthew Jacob wrote: > Yes, we very much has considered this. What's your issue about this, per se? Well, the driver for asking was my management asking if FreeBSD supported this, as we're going to do it on AIX (with the Dual Pathing Option) and with Solaris (running Veritas which I need to investigate more). We're reasonably big on redundancy here and we're running a number of critical systems on FreeBSD (DNS, WINS, DHCP, primary webserver, PDF server, etc). > Right now there's no framework code to directly exploit or prohibit multiple > paths to the same disk, whether via Fibre Channel or SCSI. Ok, but I suspect it would get a trifle upset if I started duplicating LUNS. :) I really don't know how much work this would be but would be interested in helping. I'm not a kernel hacker but I can offer testing resources (well, in about a month or so when the box arrives) for SCSI and possibly Fibre Channel if someone has code. Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 17: 0:40 2000 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 3692637BFFC for ; Tue, 28 Mar 2000 17:00:38 -0800 (PST) (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 SAA61006; Tue, 28 Mar 2000 18:00:36 -0700 (MST) (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 SAA09737; Tue, 28 Mar 2000 18:00:15 -0700 (MST) Message-Id: <200003290100.SAA09737@harmony.village.org> To: Bush Doctor Subject: Re: Warnings when linking against libc_r Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 28 Mar 2000 14:53:45 EST." <20000328145345.B41117@goku.cl.msu.edu> References: <20000328145345.B41117@goku.cl.msu.edu> Date: Tue, 28 Mar 2000 18:00:15 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000328145345.B41117@goku.cl.msu.edu> Bush Doctor writes: : I'm seeing the following diagnostics with applications linked against libc_r Don't link against -lc_r. Use -pthread. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 17:21: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B2AAC37C080 for ; Tue, 28 Mar 2000 17:20:57 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA08464; Tue, 28 Mar 2000 17:20:40 -0800 Date: Tue, 28 Mar 2000 17:20:51 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Carl Makin Cc: current@FreeBSD.ORG Subject: Re: Dual Pathing to SCSI/FC devices. 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, 28 Mar 2000, Matthew Jacob wrote: > > > Yes, we very much has considered this. What's your issue about this, per se? > > Well, the driver for asking was my management asking if FreeBSD supported > this, as we're going to do it on AIX (with the Dual Pathing Option) and > with Solaris (running Veritas which I need to investigate more). We're > reasonably big on redundancy here and we're running a number of critical > systems on FreeBSD (DNS, WINS, DHCP, primary webserver, PDF server, etc). Umm, okay. Is this with Veritas DMP or VCS? > > > Right now there's no framework code to directly exploit or prohibit multiple > > paths to the same disk, whether via Fibre Channel or SCSI. > > Ok, but I suspect it would get a trifle upset if I started duplicating > LUNS. :) I really don't know how much work this would be but would be > interested in helping. No, it wouldn't get upset, but it wouldn't know to not get upset either :-). Formally speaking, the current non-cognizant arrangement of FreeBSD would be an active-active configuration. If you use Greg Lehey's VINUM in FreeBSD, I'm not clear about what it's role in terms of recognizing redundant paths might be, but other than that there are no particular volume or spindle identification restrictions that could cause an upset. The CAM midlayer does track Vital Product Data (like drive serial numbers), but this is put together with a bus address (e.g, HBA, bus on HBA, target, lun) to track whether particular device has changed at that location or not- not whether that particular spindle is replicated elsewhere. > > I'm not a kernel hacker but I can offer testing resources (well, in about > a month or so when the box arrives) for SCSI and possibly Fibre Channel if > someone has code. Absolutely. I mean, we do have a supported Fibre Channel card (Qlogic 2100 and Qlogic 2200), but not as much testing as one would like. You should note that there isn't, for fibre channel, any particular address wiring enforced except by that which the target device does (e.g., if the target does hard loop addressing). I've been mulling over some persistent device attribute stuff for the next round of changes (e.g., binding a particular WWN to a particular 'target'), probably stored in card NVRAM, and I've had on my 'futures' list a 'WWN' extension to devfs, but this is all futures. Let me know if this is enough info to help. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 17:29:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mg134-189.ricochet.net [204.179.134.189]) by hub.freebsd.org (Postfix) with ESMTP id E13D137B61D for ; Tue, 28 Mar 2000 17:29:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA03201; Tue, 28 Mar 2000 17:33:13 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003290133.RAA03201@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "David E. Cross" Cc: freebsd-current@freebsd.org Subject: Re: Major # please :) In-reply-to: Your message of "Tue, 28 Mar 2000 19:45:04 EST." <200003290056.TAA86382@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Mar 2000 17:33:13 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Meaning no offense, but I can't think of a single good reason to write a device driver for one of these cards. (Unless you're trying to do pattern generation, and an 8255 is a terrible choice for that.) Worse than that though, there's _no_ standard for these cards' implementation, so a driver isn't going to be even vageuly portable. Use i386_set_ioperm() and just bit-bash it in userspace. > I am just about finished with a device driver for PCI DIO boards based > around the 8C255 (number may be wrong ;). Specifically this is for the > ComputerBoards DIO-24H DIO board. I have been using the 'development' major > #, and I am ready to go about getting it committed into the CVS tree for > whoever else may find it of use. > > Currently the system is used in conjunction with a home-brew card-access > system, but future could include robotics and related fields. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Tue Mar 28 17:54:48 2000 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 7860237B69A; Tue, 28 Mar 2000 17:54:45 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (loot.cs.rpi.edu [128.213.16.22]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id UAA87769; Tue, 28 Mar 2000 20:54:32 -0500 (EST) Message-Id: <200003290154.UAA87769@cs.rpi.edu> To: Mike Smith Cc: "David E. Cross" , freebsd-current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: Major # please :) In-Reply-To: Message from Mike Smith of "Tue, 28 Mar 2000 17:33:13 PST." <200003290133.RAA03201@mass.cdrom.com> Date: Tue, 28 Mar 2000 20:42:51 -0500 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Meaning no offense, but I can't think of a single good reason to write a > device driver for one of these cards. (Unless you're trying to do > pattern generation, and an 8255 is a terrible choice for that.) Worse > than that though, there's _no_ standard for these cards' implementation, > so a driver isn't going to be even vageuly portable. > > Use i386_set_ioperm() and just bit-bash it in userspace. The bit-bashing in userspace will make this even less portable. The idea is liked by those around here of being able to do a 'set register 0', or 'clear register 0' with an ioctl() and leaving the implementation to "something else", which can key on what type of board it is and DtRT. Also, how would you trap interrupts from such a card (for when using it as a digital input) from userland? Since it is already written, and in operation. Unless we are low on major numbers, or this could be better merged with another interface, it seems to be a waste to not give it a major number. Bringing it into the base CVS tree is another question entirely, but it would appear at least one has already expressed an interest. BTW: the URL for the card that was given to me for this project is at: http://www.computerboards.com/cbicatalog/cbiproduct.asp?dept%5Fid=224&pf%5Fid=668&mscssid=50A6V97GWTSH2J6N000JU4JKRUFAAEGB Product descriptions and a technical manual are linked from that page. -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD 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 Tue Mar 28 19: 6: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from veldy.net (veldy-host201.dsl.visi.com [208.42.48.201]) by hub.freebsd.org (Postfix) with ESMTP id 97A2437BB0C for ; Tue, 28 Mar 2000 19:05:59 -0800 (PST) (envelope-from veldy@fuggle.veldy.net) Received: by veldy.net (Postfix, from userid 1000) id 0F6AA193D; Tue, 28 Mar 2000 21:09:19 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by veldy.net (Postfix) with ESMTP id 0ADE11917; Tue, 28 Mar 2000 21:09:18 -0600 (CST) Date: Tue, 28 Mar 2000 21:09:18 -0600 (CST) From: "Thomas T. Veldhouse" To: James FitzGibbon Cc: current@freebsd.org Subject: Re: current.freebsd.org ftp misconfig ? In-Reply-To: <20000328094355.D1248@targetnet.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 Good luck getting an answer. Nobody seems willing to answer this question. :( Tom Veldhouse veldy@veldy.net On Tue, 28 Mar 2000, James FitzGibbon wrote: > Is this a transient situation, or is current down for maintainance ? > > [central-01:james] ~ (2) > ftp -a current.freebsd.org > Connected to usw2.freebsd.org. > 220 usw2.freebsd.org FTP server (Version wu-2.6.0(1) Tue Jan 25 00:05:38 CST 2000) ready. > 331 Guest login ok, send your complete e-mail address as password. > 530 Can't set guest privileges. > ftp: Login failed. > ftp> quit > 221 Goodbye. > [central-01:james] ~ (3) > > > -- > j. > > James FitzGibbon james@targetnet.com > Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 19: 9: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A2C3137B664 for ; Tue, 28 Mar 2000 19:09:00 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA56364; Tue, 28 Mar 2000 19:08:57 -0800 (PST) (envelope-from dillon) Date: Tue, 28 Mar 2000 19:08:57 -0800 (PST) From: Matthew Dillon Message-Id: <200003290308.TAA56364@apollo.backplane.com> To: Gary Jennejohn Cc: freebsd-current@FreeBSD.ORG Subject: Re: UP kernel performance and Matt Dillon's patches References: <200003282137.XAA05281@peedub.muc.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm running a UP machine with Matt's latest changes. I was just :compiling a new kernel and noticed the my PS/2 mouse under X was very :sluggish. I never noticed this sort of behavior before the changes, :even while doing ``make -j8 buildworld''. : :The compile was running on a UW SCSI disk on an Adaptec aic7880 Ultra :SCSI adapter on my motherboard, in case it matters. : :Looks like something has been verschlimmbessert (a wonderful German :word which means "made worse through improvement" :) : :-------- :Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org Ok, I'll take a look at it... the most likely cause is that I somehow broke need_resched. Not impossible, I'll check it out. -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 Mar 28 19: 9:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 1798937BEC0 for ; Tue, 28 Mar 2000 19:09:31 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id 0B3F41913; Tue, 28 Mar 2000 19:09:25 -0800 (PST) Date: Tue, 28 Mar 2000 19:09:24 -0800 From: Chris Piazza To: Gary Jennejohn Cc: freebsd-current@FreeBSD.ORG Subject: Re: UP kernel performance and Matt Dillon's patches Message-ID: <20000328190924.A374@norn.ca.eu.org> References: <200003282137.XAA05281@peedub.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003282137.XAA05281@peedub.muc.de>; from garyj@muc.de on Tue, Mar 28, 2000 at 11:37:55PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 28, 2000 at 11:37:55PM +0200, Gary Jennejohn wrote: > I'm running a UP machine with Matt's latest changes. I was just > compiling a new kernel and noticed the my PS/2 mouse under X was very > sluggish. I never noticed this sort of behavior before the changes, > even while doing ``make -j8 buildworld''. > > The compile was running on a UW SCSI disk on an Adaptec aic7880 Ultra > SCSI adapter on my motherboard, in case it matters. > > Looks like something has been verschlimmbessert (a wonderful German > word which means "made worse through improvement" :) I have noticed this too. Except on an SMP kernel with IDE drives. My keyboard is lagging in the same manner with high cpu loads. Abit bp6 + 2xceleron 500 IBM DJNA 13.5gig drive on the HPT366 -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 19:11:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 5A7C437BB0C for ; Tue, 28 Mar 2000 19:11:13 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA56413; Tue, 28 Mar 2000 19:11:09 -0800 (PST) (envelope-from dillon) Date: Tue, 28 Mar 2000 19:11:09 -0800 (PST) From: Matthew Dillon Message-Id: <200003290311.TAA56413@apollo.backplane.com> To: Bob Bishop Cc: current@FreeBSD.ORG Subject: Re: SMP kernel broken at cvsup Tue Mar 28 11:56:07 BST 2000 References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :At 09:52 -0800 28/3/00, Matthew Dillon wrote: :> Make sure you haven't confused it between the patch set and the :> commit I made last night. Do a cvs update and then a cvs diff to :> make sure things haven't gotten confused. : :Just blew /sys away and checked it out afresh. Same result I'm afraid, :although I did get into DDB this time. Nothing obviously wrong, but the :backtrace didn't go back past the keyboard interrupt. : :-- :Bob Bishop (0118) 977 4017 international code +44 118 :rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK Hmm. If you can get into DDB, type 'ps'. -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 Mar 28 19:26:45 2000 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 DF4F737B641 for ; Tue, 28 Mar 2000 19:26:39 -0800 (PST) (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.3) with ESMTP id TAA12083; Tue, 28 Mar 2000 19:26:39 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA04802; Tue, 28 Mar 2000 19:26:38 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 28 Mar 2000 19:26:38 -0800 (PST) Message-Id: <200003290326.TAA04802@vashon.polstra.com> To: Doug@gorean.org Subject: Re: cvs repository nits and gnats In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Doug Barton wrote: > > > Slightly more serious was the presence of various lock > > > files/directories. Specifically, one in src/games/primes killed my co as > > > an unpriviliged user because it was set 700 and owned by root. The co > > > failed because it couldn't create a lock file. I did a 'find . -name > > > \*\#\* in my CVSROOT and found several other files like this. Deleting > > > them did no harm, and they didn't return when I ran cvsup again. > > > > I havent seen this. > > My gut feeling is that it's a timing issue. I happened to have > been cvsup'ing when someone actually had a lock on something in the > repository. Still I think it's odd that A) the cvsup "mirrors" of the > master repository picked up these files, B) that my cvsup of the > repository picked them up, and C) having picked them up, it didn't delete > them when they were deleted from the real respository. FWIW, I always use > cvsup7, and I found these lock files in both my home and work copies. I think you may be misinterpreting the symptoms, because I don't know of any way for lock files to propagate off of freefall with CVSup. All lock files are specifically excluded in the server's config files -- they won't even make it to cvsup-master, let alone to the mirrors such as cvsupN.freebsd.org. What were the names of the files you thought were lock files? It sounds to me like maybe they were created by something on your local system -- not mirrored via CVSup. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 19:48: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 15EF337C015 for ; Tue, 28 Mar 2000 19:48:03 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA56657; Tue, 28 Mar 2000 19:48:00 -0800 (PST) (envelope-from dillon) Date: Tue, 28 Mar 2000 19:48:00 -0800 (PST) From: Matthew Dillon Message-Id: <200003290348.TAA56657@apollo.backplane.com> To: Matthew Dillon Cc: Gary Jennejohn , freebsd-current@FreeBSD.ORG Subject: Very weird assembly failure (was Re: UP kernel performance and Matt Dillon's patches) References: <200003282137.XAA05281@peedub.muc.de> <200003290308.TAA56364@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found a couple of minor nits, but only one real bug. In i386/swtch.s I forgot to change out a WANT_RESCHED for AST_RESCHED: sw1a: call _chooseproc /* trash ecx, edx, ret eax*/ testl %eax,%eax CROSSJUMP(je, _idle, jne) /* if no proc, idle */ movl %eax,%ecx xorl %eax,%eax andl $~WANT_RESCHED,_astpending The problem is that a kernel build is not reporting any errors! WANT_RESCHED does not exist at all, anywhere. If I change it to a garbage name the kernel still builds. I don't get it. In anycase, please try changing WANT_RESCHED to AST_RESCHED in i386/i386/swtch.s and see if that fixes the reported performance problems. If WANT_RESCHED defaults to 0 by being undefined, then the reschedule flag is never cleared when a context switch is made and this could certainly lead to problems. I also found a movb that had to be a movl, but since only the low bits were being used anyway this would not have caused any problems. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 21: 5:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 92E7837BA89 for ; Tue, 28 Mar 2000 21:05:18 -0800 (PST) (envelope-from geoff@rucus.ru.ac.za) Received: (qmail 252 invoked by uid 268); 29 Mar 2000 05:05:14 -0000 Message-ID: <20000329050514.251.qmail@rucus.ru.ac.za> Subject: Re: UP kernel performance and Matt Dillon's patches In-Reply-To: <200003290308.TAA56364@apollo.backplane.com> from Matthew Dillon at "Mar 28, 2000 07:08:57 pm" To: Matthew Dillon Date: Wed, 29 Mar 2000 07:05:14 +0200 (SAST) Cc: Gary Jennejohn , freebsd-current@FreeBSD.ORG Reply-To: "Geoff Rehmet" From: "Geoff Rehmet" X-Mailer: ELM [version 2.4ME+ PL61 (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 Matthew Dillon writes : > :I'm running a UP machine with Matt's latest changes. I was just > :compiling a new kernel and noticed the my PS/2 mouse under X was very > :sluggish. I never noticed this sort of behavior before the changes, > :even while doing ``make -j8 buildworld''. > : > :The compile was running on a UW SCSI disk on an Adaptec aic7880 Ultra > :SCSI adapter on my motherboard, in case it matters. > : > :Looks like something has been verschlimmbessert (a wonderful German > :word which means "made worse through improvement" :) > : > :-------- > :Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org > > Ok, I'll take a look at it... the most likely cause is that I somehow > broke need_resched. Not impossible, I'll check it out. I'm seeing the same symptoms while doing a make - my console performance is very jumpy and sluggish. Geoff. -- Geoff Rehmet, The Internet Solution geoffr@is.co.za; geoff@rucus.ru.ac.za; csgr@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 21:22:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id 837DE37BAC5 for ; Tue, 28 Mar 2000 21:22:35 -0800 (PST) (envelope-from carl@xena.aipo.gov.au) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id PAA91223; Wed, 29 Mar 2000 15:22:27 +1000 (EST) (envelope-from carl@xena.aipo.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma091213; Wed, 29 Mar 00 15:22:26 +1000 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.9.3/8.9.3) with ESMTP id PAA11368; Wed, 29 Mar 2000 15:24:09 +1000 (EST) (envelope-from carl@xena.aipo.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Wed, 29 Mar 2000 15:24:09 +1000 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: Matthew Jacob Cc: current@FreeBSD.ORG Subject: Re: Dual Pathing to SCSI/FC devices. 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, 28 Mar 2000, Matthew Jacob wrote: > Umm, okay. Is this with Veritas DMP or VCS? Good question. DMP I think. I'm not sure what VCS is. > an active-active configuration. If you use Greg Lehey's VINUM in FreeBSD, I'm > not clear about what it's role in terms of recognizing redundant paths might There doesn't seem much point in using VINUM with an external RAID5 box (although we use VINUM a lot on other machines). > identification restrictions that could cause an upset. The CAM midlayer does > track Vital Product Data (like drive serial numbers), but this is put together > with a bus address (e.g, HBA, bus on HBA, target, lun) to track whether > particular device has changed at that location or not- not whether that > particular spindle is replicated elsewhere. Would it be hard to add intelligence to this layer that would detect if a drive (via it's VPD info) is visible on multiple busses? If so is there a point in CAM where it could be modified to handle, at the minimum, a redundant path or better yet, use multiple paths to a device? The box to which I'm hooking this up has sufficient performance to handle 16 U2W SCSI links running hard. Being able to utilise multiple paths could be a big performance win. > Absolutely. I mean, we do have a supported Fibre Channel card (Qlogic 2100 and > Qlogic 2200), but not as much testing as one would like. I have a Qlogic 2200 on order to test this out. > You should note that there isn't, for fibre channel, any particular address > wiring enforced except by that which the target device does (e.g., if the Would this be similar to the situation that we had with FreeBSD before you could wire down devices? > Let me know if this is enough info to help. I'm getting a little beyond my depth in CAM internals here. But it is *very* interesting. :) Thanks, Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 21:27: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id D2EB737BA7B for ; Tue, 28 Mar 2000 21:27:05 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id F3B321A09; Tue, 28 Mar 2000 21:27:03 -0800 (PST) Date: Tue, 28 Mar 2000 21:27:03 -0800 From: Chris Piazza To: Matthew Dillon Cc: Gary Jennejohn , freebsd-current@FreeBSD.ORG Subject: Re: Very weird assembly failure (was Re: UP kernel performance and Matt Dillon's patches) Message-ID: <20000328212703.A365@norn.ca.eu.org> References: <200003282137.XAA05281@peedub.muc.de> <200003290308.TAA56364@apollo.backplane.com> <200003290348.TAA56657@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003290348.TAA56657@apollo.backplane.com>; from dillon@apollo.backplane.com on Tue, Mar 28, 2000 at 07:48:00PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 28, 2000 at 07:48:00PM -0800, Matthew Dillon wrote: > I found a couple of minor nits, but only one real bug. In i386/swtch.s > I forgot to change out a WANT_RESCHED for AST_RESCHED: > > The problem is that a kernel build is not reporting any errors! > WANT_RESCHED does not exist at all, anywhere. If I change it to > a garbage name the kernel still builds. I don't get it. > > In anycase, please try changing WANT_RESCHED to AST_RESCHED in > i386/i386/swtch.s and see if that fixes the reported performance > problems. If WANT_RESCHED defaults to 0 by being undefined, then > the reschedule flag is never cleared when a context switch is made > and this could certainly lead to problems. Changing it to AST_RESCHED did not fix the problem for me. -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 21:32:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9F7E537B95B for ; Tue, 28 Mar 2000 21:32:48 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA57083; Tue, 28 Mar 2000 21:32:41 -0800 (PST) (envelope-from dillon) Date: Tue, 28 Mar 2000 21:32:41 -0800 (PST) From: Matthew Dillon Message-Id: <200003290532.VAA57083@apollo.backplane.com> To: Chris Piazza Cc: Gary Jennejohn , freebsd-current@FreeBSD.ORG Subject: Re: Very weird assembly failure (was Re: UP kernel performance and Matt Dillon's patches) References: <200003282137.XAA05281@peedub.muc.de> <200003290308.TAA56364@apollo.backplane.com> <200003290348.TAA56657@apollo.backplane.com> <20000328212703.A365@norn.ca.eu.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> problems. If WANT_RESCHED defaults to 0 by being undefined, then :> the reschedule flag is never cleared when a context switch is made :> and this could certainly lead to problems. : :Changing it to AST_RESCHED did not fix the problem for me. : :-Chris Ok. I'm seeing the same behavior here too over an ssh link. I'm pretty sure I broke need_resched and the processes are incorrectly getting too much cpu in the face of a wakeup. I just have to find out where. -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 Mar 28 21:40: 3 2000 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 69CB737C15F for ; Tue, 28 Mar 2000 21:39:54 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu (root@rac5.wam.umd.edu [128.8.10.145]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id AAA26836; Wed, 29 Mar 2000 00:39:09 -0500 (EST) Received: from rac5.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id AAA27513; Wed, 29 Mar 2000 00:39:11 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id AAA27508; Wed, 29 Mar 2000 00:39:10 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Wed, 29 Mar 2000 00:39:10 -0500 (EST) From: Kenneth Wayne Culver To: Geoff Rehmet Cc: Matthew Dillon , Gary Jennejohn , freebsd-current@FreeBSD.ORG Subject: Re: UP kernel performance and Matt Dillon's patches In-Reply-To: <20000329050514.251.qmail@rucus.ru.ac.za> 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 Yeah, I was wrong before.. I just had to really hit the system hard before I noticed this behavior... it get's pretty bad... the mouse get's jumpy, and the keyboard input is really slow... ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Wed, 29 Mar 2000, Geoff Rehmet wrote: > Matthew Dillon writes : > > :I'm running a UP machine with Matt's latest changes. I was just > > :compiling a new kernel and noticed the my PS/2 mouse under X was very > > :sluggish. I never noticed this sort of behavior before the changes, > > :even while doing ``make -j8 buildworld''. > > : > > :The compile was running on a UW SCSI disk on an Adaptec aic7880 Ultra > > :SCSI adapter on my motherboard, in case it matters. > > : > > :Looks like something has been verschlimmbessert (a wonderful German > > :word which means "made worse through improvement" :) > > : > > :-------- > > :Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org > > > > Ok, I'll take a look at it... the most likely cause is that I somehow > > broke need_resched. Not impossible, I'll check it out. > I'm seeing the same symptoms while doing a make - my console performance > is very jumpy and sluggish. > > Geoff. > > -- > Geoff Rehmet, > The Internet Solution > geoffr@is.co.za; geoff@rucus.ru.ac.za; csgr@freebsd.org > tel: +27-83-292-5800 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 21:44:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 9F36A37B598 for ; Tue, 28 Mar 2000 21:44:53 -0800 (PST) (envelope-from mantar@pacbell.net) Received: from dual.pacbell.net (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id VAA00584; Tue, 28 Mar 2000 21:44:50 -0800 (PST) (envelope-from mantar@pacbell.net) Message-Id: <4.3.1.2.20000328213448.092449e8@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Tue, 28 Mar 2000 21:44:50 -0800 To: Matthew Dillon From: Manfred Antar Subject: New SMP changes Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <200003260407.UAA26945@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just noticed something with a new kernel with a Fresh world as of 1 hour ago. I'm running 2 setiathome's one for each CPU (Pentium pro) and the machine has suddenly turned into a slug !!!! It's worse than a 286 machine I used to own. It's amazing !!! It worked with this setup before the changes fine and if I kill the setiathome's everything is back to normal. Top: PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 539 nobody 66 1 15092K 14336K CPU1 1 0:45 97.87% 90.62% setiathome 536 nobody -6 1 15092K 14336K RUN 0 0:50 97.45% 90.23% setiathome I did a make world with the new changes an it worked fine. I running setiathome version 2 Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 21:51:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C80E237B660 for ; Tue, 28 Mar 2000 21:51:24 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id VAA09188; Tue, 28 Mar 2000 21:51:07 -0800 Date: Tue, 28 Mar 2000 21:51:16 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Carl Makin Cc: current@FreeBSD.ORG Subject: Re: Dual Pathing to SCSI/FC devices. 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, 28 Mar 2000, Matthew Jacob wrote: > > > Umm, okay. Is this with Veritas DMP or VCS? > > Good question. DMP I think. I'm not sure what VCS is. Veritas Cluster Server > > > an active-active configuration. If you use Greg Lehey's VINUM in FreeBSD, I'm > > not clear about what it's role in terms of recognizing redundant paths might > > There doesn't seem much point in using VINUM with an external RAID5 box > (although we use VINUM a lot on other machines). Well, you get volume (plex) identification out of it, which is of help when you don't want to try and keep track of where disks end up over time manually. > > identification restrictions that could cause an upset. The CAM midlayer does > > track Vital Product Data (like drive serial numbers), but this is put together > > with a bus address (e.g, HBA, bus on HBA, target, lun) to track whether > > particular device has changed at that location or not- not whether that > > particular spindle is replicated elsewhere. > > Would it be hard to add intelligence to this layer that would detect if a > drive (via it's VPD info) is visible on multiple busses? If so is there a > point in CAM where it could be modified to handle, at the minimum, a > redundant path or better yet, use multiple paths to a device? > > The box to which I'm hooking this up has sufficient performance to handle > 16 U2W SCSI links running hard. Being able to utilise multiple paths > could be a big performance win. You can indeed add intelligence, but it's a very wide open question how and where the intelligence should be used. And the "why" is of importance as well. You essentially need to coordiante object and path identification with volume and filesystem usage. Right now there's no problem about having multiple paths to the same disk- the only piece that's really missing is some moderately easy method to export this information out of any specific layer- but this isn't that hard to do, and could, in fact, be done via a user daemon without any kernel modifications, so I don't view this as a hard problem. What's harder is *how* to use it. There are no particular hooks in FFS to handle the multiple paths simultaneously with any coherency (for performance reasons, should you want to do so and could prove that it'd be worthwhile), nor are there any particular hooks that I'm aware of to do dynamic multipathing for failover reasons at the volume or device level- if there were in FreeBSD, I suspect VINUM in conjunction with a completed DEVVS might be the place for them, but that's just random speculation on my part. > > > Absolutely. I mean, we do have a supported Fibre Channel card (Qlogic 2100 and > > Qlogic 2200), but not as much testing as one would like. > > I have a Qlogic 2200 on order to test this out. Good! You'll find that this is better with respect to full fabric support if you happen to have, e.g., a Brocade switch on order. > > > You should note that there isn't, for fibre channel, any particular address > > wiring enforced except by that which the target device does (e.g., if the > > Would this be similar to the situation that we had with FreeBSD before you > could wire down devices? Yes, somewhat, but not quite as bad. > > > Let me know if this is enough info to help. > > I'm getting a little beyond my depth in CAM internals here. But it is > *very* interesting. :) > > Thanks, You're welcome. Lemme know how it goes. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 22:10:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8C6B237BB53 for ; Tue, 28 Mar 2000 22:10:36 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA57338; Tue, 28 Mar 2000 22:10:26 -0800 (PST) (envelope-from dillon) Date: Tue, 28 Mar 2000 22:10:26 -0800 (PST) From: Matthew Dillon Message-Id: <200003290610.WAA57338@apollo.backplane.com> To: Kenneth Wayne Culver Cc: Geoff Rehmet , Gary Jennejohn , freebsd-current@FreeBSD.ORG Subject: Re: UP kernel performance and Matt Dillon's patches References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Yeah, I was wrong before.. I just had to really hit the system hard before :I noticed this behavior... it get's pretty bad... the mouse get's jumpy, :and the keyboard input is really slow... : :================================================================= :| Kenneth Culver | FreeBSD: The best OS around. | I definitely blew the need_resched stuff. I found it. I was clearing the 'astpending' variable in doreti, which used to be just fine, but now that we have two flags in it instead of one it was clearing the need-resched flag bit as well as the astpending flag bit. If you don't want to wait, here it is (it's really the last bit that fixes the problem. The first two bits are incidental). I've committed the fix. I would appreciate others testing it as well. It seems to solve the problem I was able to reproduce on my systems. Index: isa/ipl.s =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/ipl.s,v retrieving revision 1.33 diff -u -r1.33 ipl.s --- isa/ipl.s 2000/03/28 07:16:23 1.33 +++ isa/ipl.s 2000/03/29 06:00:29 @@ -123,10 +123,10 @@ andl _ipending,%ecx /* set bit = unmasked pending INT */ jne doreti_unpend movl %eax,_cpl - MPLOCKED decb _intr_nesting_level + decb _intr_nesting_level /* Check for ASTs that can be handled now. */ - cmpb $0,_astpending + cmpl $0,_astpending je doreti_exit testb $SEL_RPL_MASK,TF_CS(%esp) jne doreti_ast @@ -271,7 +271,7 @@ ALIGN_TEXT doreti_ast: - movl $0,_astpending + andl $~AST_PENDING,_astpending sti movl $T_ASTFLT,TF_TRAPNO(%esp) call _trap To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 22:24:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 1AE5937BBAD for ; Tue, 28 Mar 2000 22:24:55 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id WAA42555; Tue, 28 Mar 2000 22:24:51 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38E1A1B2.AA5D6321@gorean.org> Date: Tue, 28 Mar 2000 22:24:50 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0325 i386) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra , current@freebsd.org Subject: Re: cvs repository nits and gnats Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: [My silly speculation about cvs lockfiles and cvsup deleted] > I think you may be misinterpreting the symptoms, That's entirely possible. > because I don't know > of any way for lock files to propagate off of freefall with CVSup. > All lock files are specifically excluded in the server's config files > -- they won't even make it to cvsup-master, let alone to the mirrors > such as cvsupN.freebsd.org. What were the names of the files you > thought were lock files? It sounds to me like maybe they were created > by something on your local system -- not mirrored via CVSup. Well, I don't make any commits to this cvs tree, only checkouts. Unfortunately I didn't save the filename of any of the really incriminating files. The one that killed my checkout was a directory in src/games/primes. I also found these files in the logs I did keep, from the /usr/src that was checked out with cvsup, not cvs: -rw-r----- 1 root wheel 7.0k Mar 22 09:55 .#Makefile.1.232 -rw-r----- 1 root wheel 23k Mar 8 22:28 .#Makefile.inc1.1.120 -rw-r----- 1 root wheel 24k Mar 24 12:21 .#UPDATING.1.58 I also found this file in my CVSROOT on one of my repositories: ./sup/src-all/#cvs.cvsup-749.0 It's actually dated March 24 1998, which predates the creation of this repository. Hrrrmm.... Aha! Part of the mystery solved at least. I started this repository from the snapshot CD dated 7/5/99. I just untarred that repository snapshot into a new directory and found the above file, and the lock directory I mentioned earlier: drwxr-x--- 2 doug wheel 512 Jul 30 1999 ./src/games/primes/#cvs.rfl.scratch1.cdrom.com.381 -rw-r----- 1 doug wheel 2.0M Mar 24 1998 ./sup/src-all/#cvs.cvsup-749.0 In any case, my purpose for posting was to notify the PTB in case there was a problem. If anyone is qualified to state categorically that there is no problem it's probably you. :) The actual lock directory above was my chief concern, and now that I know I didn't inherit it from cvsup, I'm happy. Thanks for taking the time to help me learn... Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 22:26:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from meer.meer.net (meer.meer.net [140.174.164.2]) by hub.freebsd.org (Postfix) with ESMTP id 78E6237B541 for ; Tue, 28 Mar 2000 22:26:53 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from jchurch.meer.net (unknown-35-202.wrs.com [147.11.35.202]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id WAA370362 for ; Tue, 28 Mar 2000 22:26:51 -0800 (PST) Received: from neville-neil.com (localhost [127.0.0.1]) by jchurch.meer.net (8.9.3/8.9.2) with ESMTP id WAA62636 for ; Tue, 28 Mar 2000 22:32:26 -0800 (PST) (envelope-from gnn@neville-neil.com) Message-Id: <200003290632.WAA62636@jchurch.meer.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@freebsd.org Subject: Newbie question... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Mar 2000 22:32:26 -0800 From: George Neville-Neil Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm just starting to work with FreeBSD-Current so I can add some software back into the mix. I've read the handbook, and the FAQ (and I've been a Unix, and Real Time developer for many years so I'm not new to programming) but I have a few questions that don't seem to be in the documentation: 1) How do I do development and not overwrite my work when cvsup'ing? 2) How do I know when cvsuping will NOT trash my current setup? It would be cool if a "last known good source tree" were stored somewhere. I ask this because I sup'd this morning and got toasted and had to sup/build again. 3) Is there a guide on using CVS with CVSup (the man page is not particularly helpful) so that I can have a CVS tree that is updated by cvsup? Thanks, George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 23: 4:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 3F1C637BCBB for ; Tue, 28 Mar 2000 23:04:28 -0800 (PST) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.2/8.9.3) with UUCP id JAA75195; Wed, 29 Mar 2000 09:04:16 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id JAA40176; Wed, 29 Mar 2000 09:03:49 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Wed, 29 Mar 2000 09:03:48 +0200 (CEST) From: Leif Neland Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: Reading from bad disk ? In-Reply-To: <200003220726.IAA44014@freebsd.dk> 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 > It seems Warner Losh wrote: ... > > mount it in front of the drive to get it to run at a reasonable > > temperature. W/o the fan, it was running at 58C or so. With the fan > > it runs at 39C or so. I've included the script that I use to find > > this information out. Ken Merry sent it to me. It works on some IBM > > drives. > > > > Warner > > > > #!/bin/sh > > > > TEMPC=`camcontrol cmd -v -n da -u 0 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1"` > > > > TEMPF=`echo " 2 k $TEMPC 9 * 5 / 32 + p" | dc` > > > > echo "The temperature is: $TEMPF F $TEMPC C" > Tried this: #!/bin/sh TEMPC=`camcontrol cmd -v -n da -u 2 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1"` TEMPF=`echo " 2 k $TEMPC 9 * 5 / 32 + p" | dc` echo "The temperature is: $TEMPF F $TEMPC C" I.e. replaced -u 0 with -u 2, because unit 2 is an IBM: ncr0: port 0xd100-0xd1ff mem 0x20000000-0x200000ff irq 11 at device 1.0 on pci0 ncr0: driver is using old-style compatability shims da1 at ncr0 bus 0 target 1 lun 0 da0 at ncr0 bus 0 target 0 lun 0 da2 at ncr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 8) da2: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) But I get this: camcontrol: error sending command (pass2:ncr0:0:2:0): LOG SENSE. CDB: 4d 0 76 0 0 0 0 0 20 0 (pass2:ncr0:0:2:0): ILLEGAL REQUEST asc:24,0 (pass2:ncr0:0:2:0): Invalid field in CDB dc: stack empty The temperature is: 33.80 F C Does this simply mean this drive does not support temperature measurement, or should something more be changed to use dev da2 instead of da0? I'm running a week or so old current. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 23: 5:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 3946A37B666 for ; Tue, 28 Mar 2000 23:05:23 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id CAA29853 for ; Wed, 29 Mar 2000 02:05:05 -0500 (EST) 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 CAA08560 for ; Wed, 29 Mar 2000 02:05:18 -0500 (EST) Received: from localhost (culverk@localhost) by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id CAA08556 for ; Wed, 29 Mar 2000 02:05:17 -0500 (EST) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Wed, 29 Mar 2000 02:05:17 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: sound broken on ViBRA16X? 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 with a recently compiled kernel (cvsupped about 5 minutes ago..) sounds play for less than half a second... then just completely stop... Maybe this is related to Matt Dillon's recent work? I'm not sure... ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 23:10:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 07FDD37B72D; Tue, 28 Mar 2000 23:10:15 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup7-29.iptelecom.net.ua [212.9.227.157]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id KAA02376; Wed, 29 Mar 2000 10:14:28 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id KAA05370; Wed, 29 Mar 2000 10:08:08 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <38E1ABD9.11ED74EC@altavista.net> Date: Wed, 29 Mar 2000 10:08:09 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Brian Somers Cc: current@FreeBSD.ORG, brian@FreeBSD.ORG, brian@hak.lan.awfulhak.org Subject: Re: Strange new ppp warnings References: <200003290020.BAA03124@hak.lan.Awfulhak.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers wrote: > > Hi, > > > > After upgrading my box to the 4.0-STABLE, I've discovered that ppp started > > produce regular warnings I've never seen before: > > > > Warning: nat_LayerPull: Dropped a packet.... > > > > What does it mean and what implications may it have? > > This is pretty strange. I've just added a diagnostic to > nat_LayerPull(). Can you update your sources (or get the latest > archive from my web site in about an hour) and tell me what return > value it's receiving ? Ok, here it is using latest libalias and ppp from -current just compiled with safe -O optimisation. Warning: nat_LayerPull: Dropped a packet (2).... -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 23:21:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id DD21537BDA1 for ; Tue, 28 Mar 2000 23:21:45 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac4.wam.umd.edu (root@rac4.wam.umd.edu [128.8.10.144]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id CAA02298 for ; Wed, 29 Mar 2000 02:20:46 -0500 (EST) Received: from rac4.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id CAA21957 for ; Wed, 29 Mar 2000 02:20:14 -0500 (EST) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id CAA21953 for ; Wed, 29 Mar 2000 02:20:14 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Wed, 29 Mar 2000 02:20:14 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: Vibra16x 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, I'm not sure what was wrong before, but after a recompile of the kernel, all seems well again with sound at least. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 23:26:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.hcisp.net (Stargate.hcisp.net [208.60.89.18]) by hub.freebsd.org (Postfix) with SMTP id 744EF37BFDD for ; Tue, 28 Mar 2000 23:26:51 -0800 (PST) (envelope-from tim@mysql.com) Received: (qmail 4685 invoked from network); 29 Mar 2000 07:32:57 -0000 Received: from modem5.hcisp.net (HELO threads.polyesthetic.msg) (208.60.89.71) by stargate.hcisp.net with SMTP; 29 Mar 2000 07:32:57 -0000 Received: (qmail 41984 invoked by uid 1001); 29 Mar 2000 07:26:35 -0000 From: "Thimble Smith" Date: Wed, 29 Mar 2000 02:26:35 -0500 To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: sound broken on ViBRA16X? Message-ID: <20000329022635.C39687@threads.polyesthetic.msg> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from culverk@wam.umd.edu on Wed, Mar 29, 2000 at 02:05:17AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 29, 2000 at 02:05:17AM -0500, Kenneth Wayne Culver wrote: >with a recently compiled kernel (cvsupped about 5 minutes ago..) >sounds play for less than half a second... then just completely >stop... Maybe this is related to Matt Dillon's recent work? I'm >not sure... I doubt it; I've been unable to use anything but the mixer with my ViBRA16X for several months. It works in 3.4, but not in 4.0 (and, I guess, 5.0). Here's my previous messages about this, in case you're interested: http://marc.theaimsgroup.com/?m=95048589613417 http://marc.theaimsgroup.com/?m=95078238528385 Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 23:33:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 2C5C737BCC3; Tue, 28 Mar 2000 23:33:32 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id JAA07328; Wed, 29 Mar 2000 09:33:30 +0200 (CEST) (envelope-from asmodai) Date: Wed, 29 Mar 2000 09:33:30 +0200 From: Jeroen Ruigrok van der Werven To: Brian Fundakowski Feldman Cc: Sheldon Hearn , current@FreeBSD.org Subject: Re: DDB and dumping disk Message-ID: <20000329093330.D7178@lucifer.bart.nl> References: <20000328132626.F94986@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from green@FreeBSD.org on Tue, Mar 28, 2000 at 07:13:34PM -0500 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000329 02:15], Brian Fundakowski Feldman (green@FreeBSD.org) wrote: >On Tue, 28 Mar 2000, Jeroen Ruigrok van der Werven wrote: > >> Your patch is a step in the right direction. >> >> I am currently only trying to figure out why the DDB way doesn't trigger >> savecore to recognise the dump. > >Did you try "call setdumpdev(0xf00)" with the proper show disk/ yet? No. Will try ASAP. Thanks. >It's probably worth documenting the procedure even if it will be later >be replaced with a loader functionality... however, we should still >support the way it is now for people who want to get a dump but don't >have the ability to use loader(8) fully (Alpha?). Yes it is worth documenting, and I thought that Sheldon was already on the right way with his dumpon(8) patches. I prolly only need this extra step to solve the dump `problem' which is mostly caused due to my lack of system coredump knowledge. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl That's your Destiny, the only chance, take it, take it in your hands... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 23:34:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 8B25F37BCC3 for ; Tue, 28 Mar 2000 23:34:30 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA10783; Tue, 28 Mar 2000 23:35:28 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: James FitzGibbon Cc: current@FreeBSD.ORG Subject: Re: current.freebsd.org ftp misconfig ? In-reply-to: Your message of "Tue, 28 Mar 2000 09:43:55 EST." <20000328094355.D1248@targetnet.com> Date: Tue, 28 Mar 2000 23:35:28 -0800 Message-ID: <10780.954315328@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Temporarily down; "engineers are working on the problem." :) > Is this a transient situation, or is current down for maintainance ? > > [central-01:james] ~ (2) > ftp -a current.freebsd.org > Connected to usw2.freebsd.org. > 220 usw2.freebsd.org FTP server (Version wu-2.6.0(1) Tue Jan 25 00:05:38 CST 2000) ready. > 331 Guest login ok, send your complete e-mail address as password. > 530 Can't set guest privileges. > ftp: Login failed. > ftp> quit > 221 Goodbye. > [central-01:james] ~ (3) > > > -- > j. > > James FitzGibbon james@targetnet.co m > Targetnet.com Inc. Voice/Fax +1 416 306-0466/045 2 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 28 23:53:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 2030337C0D1; Tue, 28 Mar 2000 23:53:32 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12aDI7-0004A5-00; Wed, 29 Mar 2000 09:53:27 +0200 From: Sheldon Hearn To: Jeroen Ruigrok van der Werven Cc: Brian Fundakowski Feldman , current@FreeBSD.org Subject: Re: DDB and dumping disk In-reply-to: Your message of "Wed, 29 Mar 2000 09:33:30 +0200." <20000329093330.D7178@lucifer.bart.nl> Date: Wed, 29 Mar 2000 09:53:27 +0200 Message-ID: <16000.954316407@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Mar 2000 09:33:30 +0200, Jeroen Ruigrok van der Werven wrote: > Yes it is worth documenting, and I thought that Sheldon was already on > the right way with his dumpon(8) patches. As soon as I've seen how you do it and have tried it out successfully for myself, I'll try again. :-) The current status of the dumpon(8) page is that the stale instructions about using the kernel config "dumps on" have been removed. Nothing has replaced them yet. 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 Mar 29 0:16:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 9602B37BCF9 for ; Wed, 29 Mar 2000 00:16:30 -0800 (PST) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 12aDdy-0008jo-00; Wed, 29 Mar 2000 10:16:02 +0200 Date: Wed, 29 Mar 2000 10:16:02 +0200 From: Neil Blakey-Milner To: George Neville-Neil Cc: freebsd-current@freebsd.org Subject: Re: Newbie question... Message-ID: <20000329101602.B33199@mithrandr.moria.org> References: <200003290632.WAA62636@jchurch.meer.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200003290632.WAA62636@jchurch.meer.net> Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue 2000-03-28 (22:32), George Neville-Neil wrote: > 1) How do I do development and not overwrite my work when cvsup'ing? > > 2) How do I know when cvsuping will NOT trash my current setup? It would > be cool if a "last known good source tree" were stored somewhere. I ask > this because I sup'd this morning and got toasted and had to sup/build again. If you have about 600-900Megs free, just cvsup the CVS tree. > 3) Is there a guide on using CVS with CVSup (the man page is not particularly > helpful) so that I can have a CVS tree that is updated by cvsup? Oh, and here you ask about it. Just install /usr/ports/net/cvsup-mirror, and answer the relatively easy questions. I'll get to writing something about it in the handbook. Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 0:20:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (Postfix) with ESMTP id 8A4B937B6C0 for ; Wed, 29 Mar 2000 00:20:24 -0800 (PST) (envelope-from Alain.Thivillon@hsc.fr) Received: from yoko.hsc.fr (yoko.hsc.fr [192.70.106.76]) by itesec.hsc.fr (Postfix) with ESMTP id E9E1410E04; Wed, 29 Mar 2000 10:20:22 +0200 (CEST) Received: by yoko.hsc.fr (Postfix release-19990601, from userid 1001) id 8B3A29B33F; Wed, 29 Mar 2000 10:20:00 +0200 (CEST) Date: Wed, 29 Mar 2000 10:20:00 +0200 From: Alain Thivillon To: Matthew Dillon Cc: freebsd-current@freebsd.org Subject: Re: UP kernel performance and Matt Dillon's patches Message-ID: <20000329102000.B310@yoko.hsc.fr> References: <200003290610.WAA57338@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.1.5i In-Reply-To: <200003290610.WAA57338@apollo.backplane.com>; from dillon@apollo.backplane.com on Tue, Mar 28, 2000 at 10:10:26PM -0800 X-Organization: Herve Schauer Consultants X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon écrivait (wrote) : > I've committed the fix. I would appreciate others testing it as well. With this commit, my Kernel seems looping in doreti_ast (doreti_ast+0x15) (as seen by trace after Ctrl+Alt+Esc) after displaying "mounting root device" :) My kernel config is on http://www.hsc.fr/~thivillo/YOKO50 i have rerun cvsup to be sure that all things are in sync, ipl.s shows: $FreeBSD: src/sys/i386/isa/ipl.s,v 1.34 2000/03/29 06:15:43 dillon Exp $ -- Alain Thivillon -+- Alain.Thivillon@hsc.fr -+- Hervé Schauer Consultants To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 0:21:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A3B2137B9D7 for ; Wed, 29 Mar 2000 00:21:47 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA58526; Wed, 29 Mar 2000 00:21:44 -0800 (PST) (envelope-from dillon) Date: Wed, 29 Mar 2000 00:21:44 -0800 (PST) From: Matthew Dillon Message-Id: <200003290821.AAA58526@apollo.backplane.com> To: Alain Thivillon Cc: freebsd-current@freebsd.org Subject: Re: UP kernel performance and Matt Dillon's patches References: <200003290610.WAA57338@apollo.backplane.com> <20000329102000.B310@yoko.hsc.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :With this commit, my Kernel seems looping in doreti_ast :(doreti_ast+0x15) (as seen by trace after Ctrl+Alt+Esc) after :displaying "mounting root device" :) : :My kernel config is on http://www.hsc.fr/~thivillo/YOKO50 : :i have rerun cvsup to be sure that all things are in sync, ipl.s shows: : :$FreeBSD: src/sys/i386/isa/ipl.s,v 1.34 2000/03/29 06:15:43 dillon Exp $ : :-- :Alain Thivillon -+- Alain.Thivillon@hsc.fr -+- Hervé Schauer Consultants Ah ha! I've been trying to track that down with two other people but I wasn't getting enough debugging information out of them. This is weird, it isn't happening to me at all. But I think you've given me enough info to locate the problem. -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 Wed Mar 29 0:43:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id BD14D37BC41 for ; Wed, 29 Mar 2000 00:43:24 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12aE32-0004fr-00; Wed, 29 Mar 2000 10:41:56 +0200 From: Sheldon Hearn To: Garance A Drosihn Cc: "Thimble Smith" , Giorgos Keramidas , current@FreeBSD.ORG Subject: Re: periodic daily output (passwd diffs) In-reply-to: Your message of "Tue, 28 Mar 2000 19:48:13 EST." Date: Wed, 29 Mar 2000 10:41:56 +0200 Message-ID: <17970.954319316@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Mar 2000 19:48:13 EST, Garance A Drosihn wrote: > my guess is that's easier said than done, but still it would be > nice if it WERE done... :-) I don't think it's that difficult, and I like your idea. I'll have a look at the sed/awk magic. 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 Mar 29 1: 4: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (law2-f83.hotmail.com [216.32.181.83]) by hub.freebsd.org (Postfix) with SMTP id 762E637B5E2 for ; Wed, 29 Mar 2000 01:04:02 -0800 (PST) (envelope-from changtze@hotmail.com) Received: (qmail 22266 invoked by uid 0); 29 Mar 2000 09:04:01 -0000 Message-ID: <20000329090401.22265.qmail@hotmail.com> Received: from 203.106.63.29 by www.hotmail.com with HTTP; Wed, 29 Mar 2000 01:04:01 PST X-Originating-IP: [203.106.63.29] From: "KAMIL MUHD" To: freebsd-current@freebsd.org Subject: Error code 2 Date: Wed, 29 Mar 2000 17:04:01 MYT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi everyone... I got this error evrytime I try to make world no matter how often I cvsup'ed. I don't know what it is, what is Error code 2 anyway? Is my cc version is out-of-date? I'm using the GNU gcc-2.95.1. My box is running on 4.0-CURRENT. Any idea? Is it because I've cvsuped the wrong file? I cvsuped the 4.x-secure-stable-supfile and 4.x-stable-supfile. cc -O -pipe -I/usr/src/lib/libm/common_source -Dnational -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libm/common_source/gamma.c -o gamma.o cc -O -pipe -I/usr/src/lib/libm/common_source -Dnational -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libm/common_source/lgamma.c -o lgamma.o cc -O -pipe -I/usr/src/lib/libm/common_source -Dnational -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libm/common_source/j0.c -o j0.o cc -O -pipe -I/usr/src/lib/libm/common_source -Dnational -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libm/common_source/j1.c -o j1.o /usr/src/lib/libm/common_source/lgamma.c:141: syntax error before `double' cc -O -pipe -I/usr/src/lib/libm/common_source -Dnational -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libm/common_source/jn.c -o jn.o cc -O -pipe -I/usr/src/lib/libm/common_source -Dnational -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libm/common_source/log.c -o log.o cc -O -pipe -I/usr/src/lib/libm/common_source -Dnational -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libm/common_source/log10.c -o log10.o *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error [AWAN /usr/src ]% exit exit Script done on Wed Mar 29 16:00:40 2000 ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 1:14:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 79B2637B609 for ; Wed, 29 Mar 2000 01:14:41 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id BAA59032; Wed, 29 Mar 2000 01:14:40 -0800 (PST) (envelope-from dillon) Date: Wed, 29 Mar 2000 01:14:40 -0800 (PST) From: Matthew Dillon Message-Id: <200003290914.BAA59032@apollo.backplane.com> To: current@freebsd.org Cc: Geoff Rehmet , Bob Bishop , Alain Thivillon , Kenneth Wayne Culver Subject: src/sys/i386/isa/ipl.s rev 1.35 should fix boot lockups Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rev 1.35 of src/sys/i386/isa/ipl.s, which I just committed, should fix the boot lockups. Many thanks for Alain Thivillon who was able to catch it in the act with DDB and narrow the problem down to doreti looping on astpending. To anyone I asked to try backing out the recent patch with an explicit revision checkout, please remember to blow away your src/sys/i386 subtree and check it out again so those files are not locked to a fixed revision. I am hoping that this will also fix Bob Bishop's reported boot lockup. The slow-response and jerky mouse problem should also be fixed. -Matt Matthew Dillon Index: isa/ipl.s =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/ipl.s,v retrieving revision 1.34 retrieving revision 1.35 diff -u -r1.34 -r1.35 --- isa/ipl.s 2000/03/29 06:15:43 1.34 +++ isa/ipl.s 2000/03/29 09:07:47 1.35 @@ -36,7 +36,7 @@ * * @(#)ipl.s * - * $FreeBSD: src/sys/i386/isa/ipl.s,v 1.34 2000/03/29 06:15:43 dillon Exp $ + * $FreeBSD: src/sys/i386/isa/ipl.s,v 1.35 2000/03/29 09:07:47 dillon Exp $ */ @@ -126,7 +126,7 @@ decb _intr_nesting_level /* Check for ASTs that can be handled now. */ - cmpl $0,_astpending + testl $AST_PENDING,_astpending je doreti_exit testb $SEL_RPL_MASK,TF_CS(%esp) jne doreti_ast To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 1:30: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id AA1EF37BFA2; Wed, 29 Mar 2000 01:30:01 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id KAA11422; Wed, 29 Mar 2000 10:29:55 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id JAA00796; Wed, 29 Mar 2000 09:43:39 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200003290843.JAA00796@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Maxim Sobolev Cc: Brian Somers , current@FreeBSD.ORG, brian@FreeBSD.ORG, brian@hak.lan.awfulhak.org, brian@hak.lan.awfulhak.org Subject: Re: Strange new ppp warnings In-Reply-To: Message from Maxim Sobolev of "Wed, 29 Mar 2000 10:08:09 +0300." <38E1ABD9.11ED74EC@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Mar 2000 09:43:39 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Brian Somers wrote: > > > > Hi, > > > > > > After upgrading my box to the 4.0-STABLE, I've discovered that ppp started > > > produce regular warnings I've never seen before: > > > > > > Warning: nat_LayerPull: Dropped a packet.... > > > > > > What does it mean and what implications may it have? > > > > This is pretty strange. I've just added a diagnostic to > > nat_LayerPull(). Can you update your sources (or get the latest > > archive from my web site in about an hour) and tell me what return > > value it's receiving ? > > Ok, here it is using latest libalias and ppp from -current just compiled with > safe -O optimisation. > > Warning: nat_LayerPull: Dropped a packet (2).... Ah, ok. This is incoming data that's being ignored by ppp - maybe because you've got ``nat deny_incoming yes'' configured ? I've added some more useful diagnostics, but you'll need to ``set log +tcp/ip'' to see them. > -Maxim Cheers. -- 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 Wed Mar 29 2:38:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id 4E38E37C0CC for ; Wed, 29 Mar 2000 02:38:24 -0800 (PST) (envelope-from netchild@leidinger.net) Received: from [62.104.201.2] (helo=mx1.freenet.de) by mout1.freenet.de with esmtp (Exim 3.13 #3) id 12aFrc-0005KC-00; Wed, 29 Mar 2000 12:38:16 +0200 Received: from [213.6.44.84] (helo=Magelan.Leidinger.net) by mx1.freenet.de with esmtp (Exim 3.13 #1) id 12aFrY-0006rj-00; Wed, 29 Mar 2000 12:38:13 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id LAA01447; Wed, 29 Mar 2000 11:22:19 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200003290922.LAA01447@Magelan.Leidinger.net> Date: Wed, 29 Mar 2000 11:22:18 +0200 (CEST) From: Alexander Leidinger Subject: Re: Newbie question... To: gnn@neville-neil.com Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <200003290632.WAA62636@jchurch.meer.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28 Mar, George Neville-Neil wrote: > 1) How do I do development and not overwrite my work when cvsup'ing? See 3). > 3) Is there a guide on using CVS with CVSup (the man page is not particularly > helpful) so that I can have a CVS tree that is updated by cvsup? See /usr/share/examples/cvsup/{,secure-}cvs-supfile: - "prefix" should be set to a directory with enough space to hold the repository (e.g. "/big_disk/FreeBSD-CVS"). - at the moment it needs ~800MB (src~=620MB, ports~=180MB), if you also want doc and www it needs ~900MB. - remove your /usr/src, set the CVSROOT variable ("/big_disk/FreeBSD-CVS") and check the source out ("cvs co src"). Add "CVS_UPDATE=yes" to your make.conf (and remove "SUP_UPDATE") and a "make update" in /usr/src uses your private CVS repository to update the source. Bye, Alexander. -- The dark ages were caused by the Y1K problem. http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 2:51:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 39BCE37BF8B; Wed, 29 Mar 2000 02:51:20 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup5-7.iptelecom.net.ua [212.9.227.7]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id NAA18099; Wed, 29 Mar 2000 13:55:39 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id NAA05365; Wed, 29 Mar 2000 13:48:46 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <38E1DF8C.27DD612F@altavista.net> Date: Wed, 29 Mar 2000 13:48:44 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Brian Somers Cc: current@FreeBSD.ORG, brian@FreeBSD.ORG, brian@hak.lan.awfulhak.org Subject: Re: Strange new ppp warnings References: <200003290843.JAA00796@hak.lan.Awfulhak.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers wrote: > Ah, ok. This is incoming data that's being ignored by ppp - maybe > because you've got ``nat deny_incoming yes'' configured ? Yes, I have ``nat deny_incoming yes''. Thanks for explaining. Maybe it would be worth to add more meaningful warning message like "Dropped a incoming packet from aaa.bbb.ccc.ddd:xxxx to eee.fff.ggg.hhh:yyyy" to prevent future confusion of other ppp users? -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 2:57:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id F25C037BE1C for ; Wed, 29 Mar 2000 02:57:07 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id ECA971814C; Wed, 29 Mar 2000 12:56:38 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Wed, 29 Mar 2000 11:55:21 +0200 To: mjacob@feral.com, Carl Makin From: Brad Knowles Subject: Re: Dual Pathing to SCSI/FC devices. Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:28 PM -0800 2000/3/28, Matthew Jacob wrote: > Yes, we very much has considered this. What's your issue about this, per se? > Right now there's no framework code to directly exploit or prohibit multiple > paths to the same disk, whether via Fibre Channel or SCSI. Myself, I just need to be able to tell the system that SCSI ID x LUN y is actually the same logical device as SCSI ID v LUN w, but that one is preferred and the other is backup, and have FreeBSD deal with doing the re-targeting in the CAM SCSI driver. The end result should be that nothing above the CAM SCSI driver should know that a switch has occurred -- especially not programs like vinum, which might be called upon to do software mirroring/striping/RAID on top of the hardware mirroring/striping/RAID. Same deal with fibrechannel as SCSI. Does that about sum it up? Oh, and Carl -- I don't suppose you're looking at Hitachi DF400 (sometimes rebadged as Comparex D1400) units, are you? If so, I'd like to talk to you in some depth about these things -- maybe you can come up with some solutions for some problems I've had. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 2:57:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id E088237BC2D for ; Wed, 29 Mar 2000 02:57:10 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 1943918280; Wed, 29 Mar 2000 12:56:51 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Wed, 29 Mar 2000 12:07:27 +0200 To: Carl Makin , Matthew Jacob From: Brad Knowles Subject: Re: Dual Pathing to SCSI/FC devices. Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:24 PM +1000 2000/3/29, Carl Makin wrote: > There doesn't seem much point in using VINUM with an external RAID5 box > (although we use VINUM a lot on other machines). Speaking only for myself and the Comparex D1400 (Hitachi DF400) unit that I've been playing with so far, there is *very* good reason to use vinum on top of the external drive array. In particular, the unit has five SCSI busses internally, and when you configure LUNs you typically configure one or more rows of five disks per row. However, when you configure more than one row for a LUN, it simply appends one row to the next, and doesn't stripe or RAID-5 across all disks simultaneously. This really kills your performance. If I instead create one LUN for each row of disks (RAID-5), I can then stripe across them in software using vinum, and start approaching the levels of performance that I could get if I instead were using vinum exclusively and striping across twenty high-speed disks on five separate SCSI busses that were directly connected to the host. Unfortunately, this device doesn't have any concept of creating LUNs composed of other LUNs, so that I could keep all this bizarreness strictly within the cabinet. > The box to which I'm hooking this up has sufficient performance to handle > 16 U2W SCSI links running hard. Being able to utilise multiple paths > could be a big performance win. Theoretically, the box I'm connecting to can handle that level of performance, too. However, I've had problems with it when I push it hard with just two Adaptec 2940U2W host adaptors, each connecting to one interface on separate device controllers. In theory, practice and theory are the same. In practice, they are frequently radically different. > I'm getting a little beyond my depth in CAM internals here. But it is > *very* interesting. :) I'm out of my depth in CAM SCSI internals, too but I'm also willing to provide whatever assistance I can, with regards to testing. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 2:57:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id E77D037B9F6 for ; Wed, 29 Mar 2000 02:57:37 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id BDCF118062; Wed, 29 Mar 2000 12:56:56 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Wed, 29 Mar 2000 12:10:04 +0200 To: mjacob@feral.com, Carl Makin From: Brad Knowles Subject: Re: Dual Pathing to SCSI/FC devices. Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:51 PM -0800 2000/3/28, Matthew Jacob wrote: > What's harder is *how* to use it. There are no particular hooks in FFS to > handle the multiple paths simultaneously with any coherency (for performance > reasons, should you want to do so and could prove that it'd be worthwhile), > nor are there any particular hooks that I'm aware of to do dynamic > multipathing for failover reasons at the volume or device level- if >there were > in FreeBSD, I suspect VINUM in conjunction with a completed DEVVS >might be the > place for them, but that's just random speculation on my part. My personal view is that all of this should be invisible to the higher layers, unless they know the right interfaces to use to go looking for this information. The switch should be made at the CAM SCSI layer, and applications above that don't need to know anything about it. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 3: 4:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from spiral.inspiral.net (spiral.inspiral.net [194.204.49.249]) by hub.freebsd.org (Postfix) with ESMTP id 71F3237C044; Wed, 29 Mar 2000 03:03:50 -0800 (PST) (envelope-from mauri@inspiral.net) Received: from aquarius (aquarius.inspiral.net [194.204.49.250]) by spiral.inspiral.net (8.9.3/8.9.3) with ESMTP id NAA69311; Wed, 29 Mar 2000 13:02:52 +0300 (EEST) (envelope-from mauri@inspiral.net) From: "Lauri Laupmaa" Organization: Inspiral.Net To: stable@freebsd.org, current@freebsd.org Date: Wed, 29 Mar 2000 14:03:14 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: timezones/zoneinfo Cc: support@redhat.com, support@debian.org Message-ID: <38E20D22.17581.4939BA1@localhost> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Who and when should update/fix subj. ? Our parliament decided that estonia does not change to DST anymore and forgot to mention it to MS and other OS manufacturers :) so info for Europe/Tallinn is wrong and our little state is full of computers with wrong time :( Help! _____________ Lauri Laupmaa +3725013369 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 3: 6:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 02A2237C1CE; Wed, 29 Mar 2000 03:06:18 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id MAA12840; Wed, 29 Mar 2000 12:06:12 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id MAA02283; Wed, 29 Mar 2000 12:06:06 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200003291106.MAA02283@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Maxim Sobolev Cc: Brian Somers , current@FreeBSD.ORG, brian@FreeBSD.ORG, brian@hak.lan.awfulhak.org, brian@hak.lan.awfulhak.org Subject: Re: Strange new ppp warnings In-Reply-To: Message from Maxim Sobolev of "Wed, 29 Mar 2000 13:48:44 +0300." <38E1DF8C.27DD612F@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Mar 2000 12:06:06 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Brian Somers wrote: > > > Ah, ok. This is incoming data that's being ignored by ppp - maybe > > because you've got ``nat deny_incoming yes'' configured ? > > Yes, I have ``nat deny_incoming yes''. Thanks for explaining. > > Maybe it would be worth to add more meaningful warning message like "Dropped a > incoming packet from aaa.bbb.ccc.ddd:xxxx to eee.fff.ggg.hhh:yyyy" to prevent future > confusion of other ppp users? Exactly what I've done (great minds think alike!) :-) I've logged at TCP/IP level though as I suspect the general case will be that people don't want to see these messages. > -Maxim -- 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 Wed Mar 29 3:10:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 7AFDF37C10A for ; Wed, 29 Mar 2000 03:10:21 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id VAA29925; Wed, 29 Mar 2000 21:15:56 +1000 Date: Wed, 29 Mar 2000 21:09:45 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Matthew Dillon Cc: Gary Jennejohn , freebsd-current@FreeBSD.ORG Subject: Re: Very weird assembly failure (was Re: UP kernel performance and Matt Dillon's patches) In-Reply-To: <200003290348.TAA56657@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 Tue, 28 Mar 2000, Matthew Dillon wrote: > I found a couple of minor nits, but only one real bug. In i386/swtch.s > I forgot to change out a WANT_RESCHED for AST_RESCHED: > > sw1a: > call _chooseproc /* trash ecx, edx, ret eax*/ > testl %eax,%eax > CROSSJUMP(je, _idle, jne) /* if no proc, idle */ > movl %eax,%ecx > > xorl %eax,%eax > andl $~WANT_RESCHED,_astpending > > The problem is that a kernel build is not reporting any errors! > WANT_RESCHED does not exist at all, anywhere. If I change it to > a garbage name the kernel still builds. I don't get it. It seems to be a gas bug. The error is detected if ~WANT_RESCHED is replaced by WANT_RESCHED. ~WANT_RESCHED is no a simple relocatable expression, so it isn't clear that gas or elf can handle it. They don't seem to for the following simpler case: $ echo "movl $~FOO,%eax" >z.s $ echo ".globl foo; .set FOO,0x55555555" >z1.s $ cc -c z.s z1.s $ ld -o z z.o z1.s $ objdump --disassemble z z: file format elf32-i386 Disassembly of section .text: 08048074 <.text>: 8048074: b8 ff ff ff ff movl $0xffffffff,%eax ^^^^^^^^ should be aaaaaaaa but still has best guess at time of assembly of z.s 8048079: 90 nop 804807a: 90 nop 804807b: 90 nop Everthing works right for "FOO" instead of ~FOO. The aout case gets this wrong in a more obvious way. Gas produces the same code for "movl $~FOO,%eax" as for "movl $FOO,%eax". Linking to z1.o then gives the right value for $FOO and the wrong value for $~FOO. Gas notices the problem for "movl $-FOO,%eax": z.s: Assembler messages: z.s:1: Error: Negative of non-absolute symbol FOO Similarly for the a.out case. Complementation is equivalent to negation on 2's complement machines, so gas should produce this error for $~FOO too. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 3:34:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from mercury.is.co.za (mercury.is.co.za [196.4.160.222]) by hub.freebsd.org (Postfix) with ESMTP id BFE9437BB82 for ; Wed, 29 Mar 2000 03:34:33 -0800 (PST) (envelope-from geoffr@is.co.za) Received: from isjhbwebsec01.is.co.za ([196.23.26.5]) by mercury.is.co.za (8.9.3/8.9.3) with SMTP id NAA09109 for ; Wed, 29 Mar 2000 13:34:30 +0200 Received: FROM ISJHBEX BY isjhbwebsec01.is.co.za ; Wed Mar 29 13:40:25 2000 +0200 Received: by ISJHBEX with Internet Mail Service (5.5.2650.21) id ; Wed, 29 Mar 2000 13:38:59 +0200 Message-ID: From: Geoff Rehmet To: "'Matthew Dillon'" Cc: "'current@freebsd.org'" Subject: RE: src/sys/i386/isa/ipl.s rev 1.35 should fix boot lockups Date: Wed, 29 Mar 2000 13:38:57 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seems to be 100% now - I'm busy throwing a make -j 8 buildworld and a make -j 4 on the kernel, plus taring my source tree and browsing the web a little to see tha my console response is OK. ALL LOOKS COOL!!!! Thanks Matt! > -----Original Message----- > From: Matthew Dillon [mailto:dillon@apollo.backplane.com] > Sent: 29 March 2000 11:15 > To: current@freebsd.org > Cc: Geoff Rehmet; Bob Bishop; Alain Thivillon; Kenneth Wayne Culver > Subject: src/sys/i386/isa/ipl.s rev 1.35 should fix boot lockups > > > Rev 1.35 of src/sys/i386/isa/ipl.s, which I just committed, should > fix the boot lockups. > > Many thanks for Alain Thivillon who was able to catch it > in the act > with DDB and narrow the problem down to doreti looping on > astpending. > > To anyone I asked to try backing out the recent patch > with an explicit > revision checkout, please remember to blow away your > src/sys/i386 subtree > and check it out again so those files are not locked to a > fixed revision. > > I am hoping that this will also fix Bob Bishop's reported > boot lockup. > > The slow-response and jerky mouse problem should also be fixed. > > -Matt > Matthew Dillon > > > Index: isa/ipl.s > =================================================================== > RCS file: /home/ncvs/src/sys/i386/isa/ipl.s,v > retrieving revision 1.34 > retrieving revision 1.35 > diff -u -r1.34 -r1.35 > --- isa/ipl.s 2000/03/29 06:15:43 1.34 > +++ isa/ipl.s 2000/03/29 09:07:47 1.35 > @@ -36,7 +36,7 @@ > * > * @(#)ipl.s > * > - * $FreeBSD: src/sys/i386/isa/ipl.s,v 1.34 2000/03/29 > 06:15:43 dillon Exp $ > + * $FreeBSD: src/sys/i386/isa/ipl.s,v 1.35 2000/03/29 > 09:07:47 dillon Exp $ > */ > > > @@ -126,7 +126,7 @@ > decb _intr_nesting_level > > /* Check for ASTs that can be handled now. */ > - cmpl $0,_astpending > + testl $AST_PENDING,_astpending > je doreti_exit > testb $SEL_RPL_MASK,TF_CS(%esp) > jne doreti_ast > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 4: 5:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 87CFF37BF6D for ; Wed, 29 Mar 2000 04:05:19 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 30802 invoked from network); 29 Mar 2000 12:05:15 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 29 Mar 2000 12:05:15 -0000 Date: Wed, 29 Mar 2000 22:04:58 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Yoshinobu Inoue Cc: bmah@CA.Sandia.GOV, nnd@mail.nsk.ru, current@FreeBSD.ORG Subject: Re: 'machine/param.h' required for 'sys/socket.h' In-Reply-To: <20000329003050L.shin@nd.net.fujitsu.co.jp> 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, 29 Mar 2000, Yoshinobu Inoue wrote: > > > sys/socket.h: > > > #ifdef _NO_NAME_SPACE_POLLUTION > > > #include > > > #else > > > #define _NO_NAME_SPACE_POLLUTION > > > #include > > > #undef _NO_NAME_SPACE_POLLUTION > > > #endif > > > > I like this for a quick fix. Only define _ALIGN() like the current > > ALIGN(). Don't define all the variants given in your previous mail. > > I created the patches. > It become a little bit more complicated than I expected, to > avoid duplicated inclusion independently in each of namespace > polluted part and non polluted part. Now I don't like this for a quick fix :-). It is more complicated than a correct fix. I think it would be OK without any anti-redefinition ifdefs. Redefinition is only a micro-pessimization since there are only #define's (no typedefs, etc.) and won't occur often since should only be included by , and . Reinclusion can be optimized in the including file using e.g. #ifndef _ALIGN in . Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 4: 8:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.fast.net.uk (mail.fast.net.uk [212.42.162.3]) by hub.freebsd.org (Postfix) with ESMTP id EF88837BE55 for ; Wed, 29 Mar 2000 04:08:39 -0800 (PST) (envelope-from blair@fastnet.co.uk) Received: from java.fast.net.uk (java.fast.net.uk [212.42.162.149]) by mail.fast.net.uk (8.9.3/8.9.3) with SMTP id MAA84948 for ; Wed, 29 Mar 2000 12:08:42 GMT (envelope-from blair@fastnet.co.uk) From: Blair Sutton Organization: FastNet International To: current@FreeBSD.org Subject: Re: libl.a in libipsec Date: Wed, 29 Mar 2000 13:01:05 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00032913042001.83432@java.fast.net.uk> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone commited any changes to /usr/src/Makefile to fix the following problem in make buildworld:- ===> lib/libipsec make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libl.a. Stop Is it worth manually removing this target from the Makefile? -- Blair Sutton Systems Administrator Fastnet International To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 5:55: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.targetnet.com (mail.targetnet.com [207.245.246.3]) by hub.freebsd.org (Postfix) with ESMTP id 67CD837C0A0 for ; Wed, 29 Mar 2000 05:54:55 -0800 (PST) (envelope-from james@targetnet.com) Received: from james by mail.targetnet.com with local (Exim 3.02 #1) id 12aIvr-0001yo-00 for current@freebsd.org; Wed, 29 Mar 2000 08:54:51 -0500 Date: Wed, 29 Mar 2000 08:54:51 -0500 From: James FitzGibbon To: current@freebsd.org Subject: Re: current.freebsd.org ftp misconfig ? Message-ID: <20000329085451.A6906@targetnet.com> References: <20000328094355.D1248@targetnet.com> <10780.954315328@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <10780.954315328@zippy.cdrom.com> Organization: Targetnet.com Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jordan K. Hubbard (jkh@zippy.cdrom.com) [000329 02:34]: > Temporarily down; "engineers are working on the problem." :) Does anyone have a semi-recent 3.4-STABLE snapshot available for public consumption ? The latest I have lying around is 20000303. Thanks. > > Is this a transient situation, or is current down for maintainance ? > > > > [central-01:james] ~ (2) > ftp -a current.freebsd.org > > Connected to usw2.freebsd.org. > > 220 usw2.freebsd.org FTP server (Version wu-2.6.0(1) Tue Jan 25 00:05:38 CST > 2000) ready. > > 331 Guest login ok, send your complete e-mail address as password. > > 530 Can't set guest privileges. > > ftp: Login failed. > > ftp> quit > > 221 Goodbye. > > [central-01:james] ~ (3) > -- j. James FitzGibbon james@targetnet.com Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 8: 7:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4082D37C0CC for ; Wed, 29 Mar 2000 08:07:53 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA63043; Wed, 29 Mar 2000 08:07:48 -0800 (PST) (envelope-from dillon) Date: Wed, 29 Mar 2000 08:07:48 -0800 (PST) From: Matthew Dillon Message-Id: <200003291607.IAA63043@apollo.backplane.com> To: Bruce Evans Cc: Gary Jennejohn , freebsd-current@FreeBSD.ORG Subject: Re: Very weird assembly failure (was Re: UP kernel performance and Matt Dillon's patches) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> I found a couple of minor nits, but only one real bug. In i386/swtch.s :> I forgot to change out a WANT_RESCHED for AST_RESCHED: :> :> sw1a: :> call _chooseproc /* trash ecx, edx, ret eax*/ :> testl %eax,%eax :> CROSSJUMP(je, _idle, jne) /* if no proc, idle */ :> movl %eax,%ecx :> :> xorl %eax,%eax :> andl $~WANT_RESCHED,_astpending :> :> The problem is that a kernel build is not reporting any errors! :> WANT_RESCHED does not exist at all, anywhere. If I change it to :> a garbage name the kernel still builds. I don't get it. : :It seems to be a gas bug. The error is detected if ~WANT_RESCHED is :replaced by WANT_RESCHED. ~WANT_RESCHED is no a simple relocatable :expression, so it isn't clear that gas or elf can handle it. They :don't seem to for the following simpler case: : :$ echo "movl $~FOO,%eax" >z.s :$ echo ".globl foo; .set FOO,0x55555555" >z1.s :$ cc -c z.s z1.s :$ ld -o z z.o z1.s :$ objdump --disassemble z : :z: file format elf32-i386 : :Disassembly of section .text: : :08048074 <.text>: : 8048074: b8 ff ff ff ff movl $0xffffffff,%eax : ^^^^^^^^ should be aaaaaaaa : but still has best guess : at time of assembly of z.s : 8048079: 90 nop : 804807a: 90 nop : 804807b: 90 nop : :Everthing works right for "FOO" instead of ~FOO. : :The aout case gets this wrong in a more obvious way. Gas produces the same :code for "movl $~FOO,%eax" as for "movl $FOO,%eax". Linking to z1.o then :gives the right value for $FOO and the wrong value for $~FOO. : :Gas notices the problem for "movl $-FOO,%eax": : z.s: Assembler messages: : z.s:1: Error: Negative of non-absolute symbol FOO :Similarly for the a.out case. Complementation is equivalent to negation :on 2's complement machines, so gas should produce this error for $~FOO too. : :Bruce Ok, so who do we send your excellent analysis to at GNU-C? I think this is a rather serious bug myself since a programmer can make a simple labelname mistake and get incorrect code instead of an error. Also, probably a simple mistake but complement != negation. I think ~F = -F - 1; -0x0001 == 0xFFFF ~0x0001 == 0xFFFE -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 Wed Mar 29 9:15: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 8529C37B6C4 for ; Wed, 29 Mar 2000 09:14:57 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id JAA92088; Wed, 29 Mar 2000 09:16:47 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200003291716.JAA92088@troutmask.apl.washington.edu> Subject: Re: Error code 2 In-Reply-To: <20000329090401.22265.qmail@hotmail.com> from KAMIL MUHD at "Mar 29, 2000 05:04:01 pm" To: KAMIL MUHD Date: Wed, 29 Mar 2000 09:16:47 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 KAMIL MUHD wrote: > Hi everyone... > > I got this error evrytime I try to make world no matter how often I > cvsup'ed. I don't know what it is, what is Error code 2 anyway? Is my cc > version is out-of-date? I'm using the GNU gcc-2.95.1. My box is running on > 4.0-CURRENT. Any idea? Is it because I've cvsuped the wrong file? I cvsuped > the 4.x-secure-stable-supfile and 4.x-stable-supfile. > > cc -O -pipe -I/usr/src/lib/libm/common_source -Dnational In /etc/make.conf, you should comment out WANT_CSRG_LIBM. The default math library is in src/lib/msun. Why the csrg math library is still in the src tree is somewhat of a mystery to me. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 9:53:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from bsd.kam.pl (bsd.kam.pl [195.205.77.13]) by hub.freebsd.org (Postfix) with ESMTP id 06F2137B633 for ; Wed, 29 Mar 2000 09:53:06 -0800 (PST) (envelope-from mariusz@kam.pl) Received: from localhost (mariusz@localhost) by bsd.kam.pl (8.9.3/8.9.3) with ESMTP id RAA53306 for ; Wed, 29 Mar 2000 17:56:27 GMT (envelope-from mariusz@kam.pl) Date: Wed, 29 Mar 2000 17:56:27 +0000 (GMT) From: mariusz To: current@freebsd.org Subject: panic: worklist_remove 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 New system FreeBSD 5.0, cvsup today. System reboot in message: panic: worklist_remove: not on list syncing disks... panic: softdep_lock: locking against myself watch is wrong ? Mariusz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 10:18:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mg134-053.ricochet.net [204.179.134.53]) by hub.freebsd.org (Postfix) with ESMTP id 0A3A237BCE2 for ; Wed, 29 Mar 2000 10:18:13 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA00436; Wed, 29 Mar 2000 10:21:29 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003291821.KAA00436@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "David E. Cross" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Major # please :) In-reply-to: Your message of "Tue, 28 Mar 2000 20:42:51 EST." <200003290154.UAA87769@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Mar 2000 10:21:28 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Meaning no offense, but I can't think of a single good reason to write a > > device driver for one of these cards. (Unless you're trying to do > > pattern generation, and an 8255 is a terrible choice for that.) Worse > > than that though, there's _no_ standard for these cards' implementation, > > so a driver isn't going to be even vageuly portable. > > > > Use i386_set_ioperm() and just bit-bash it in userspace. > > The bit-bashing in userspace will make this even less portable. The idea is > liked by those around here of being able to do a 'set register 0', or > 'clear register 0' with an ioctl() and leaving the implementation to > "something else", which can key on what type of board it is and DtRT. It hardly matters whether this interface is abstracted across the kernel:userland boundary, or just somewhere within your application, eg. using a shared library. > Also, how would you trap interrupts from such a card (for when using it as > a digital input) from userland? Typically these cards don't offer interrupt generation. Iff your application is for a card that generates interrupts, and you actually need them (as opposed to being able to poll the card) then writing a tiny KLD driver is probably worthwhile for your application. > Since it is already written, and in operation. Unless we are low on major > numbers, or this could be better merged with another interface, it seems to > be a waste to not give it a major number. Bringing it into the base CVS > tree is another question entirely, but it would appear at least one has > already expressed an interest. We don't, typically, hand out major numbers for drivers that aren't part of the base system. There are 56 entries in the 200-255 range that are all available for use by deployed-but-local drivers; I'd recommend using one of those. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Wed Mar 29 10:52: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 5F85C37B800 for ; Wed, 29 Mar 2000 10:50:34 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id EAA21738; Thu, 30 Mar 2000 04:56:02 +1000 Date: Thu, 30 Mar 2000 04:50:02 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Matthew Dillon Cc: Gary Jennejohn , freebsd-current@FreeBSD.ORG Subject: Re: Very weird assembly failure (was Re: UP kernel performance and Matt Dillon's patches) In-Reply-To: <200003291607.IAA63043@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 Wed, 29 Mar 2000, Matthew Dillon wrote: > :Gas notices the problem for "movl $-FOO,%eax": > : z.s: Assembler messages: > : z.s:1: Error: Negative of non-absolute symbol FOO > :Similarly for the a.out case. Complementation is equivalent to negation > :on 2's complement machines, so gas should produce this error for $~FOO too. > > Ok, so who do we send your excellent analysis to at GNU-C? I think > this is a rather serious bug myself since a programmer can make a > simple labelname mistake and get incorrect code instead of an error. Don't know. David O'Brien has been doing most of the GNU contacting. > Also, probably a simple mistake but complement != negation. > I think ~F = -F - 1; I meant that has equivalent complexity. All normal assemblers and object formats handle offsets, so if they can handle "~" then they can probably handle "-". Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 10:53:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from androcles.com (androcles.com [204.57.240.10]) by hub.freebsd.org (Postfix) with ESMTP id 3CB2937BFE1; Wed, 29 Mar 2000 10:52:19 -0800 (PST) (envelope-from alex@androcles.com) Received: (from dhh@localhost) by androcles.com (8.9.3/8.9.3) id KAA60763; Wed, 29 Mar 2000 10:51:12 -0800 (PST) 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: <38E20D22.17581.4939BA1@localhost> Date: Wed, 29 Mar 2000 10:51:11 -0800 (PST) Reply-To: dhh@androcles.com From: "Duane H. Hesser" To: Lauri Laupmaa Subject: RE: timezones/zoneinfo Cc: support@debian.org, support@redhat.com, current@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Mar-00 Lauri Laupmaa wrote: > Hi > > Who and when should update/fix subj. ? > Our parliament decided that estonia does not change to DST > anymore and forgot to mention it to MS and other OS > manufacturers :) > > so info for Europe/Tallinn is wrong and our little state is full of > computers with wrong time :( > > Help! > _____________ > Lauri Laupmaa > +3725013369 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > A quick search of Google/BSD reveals that NetBSD is current on zoneinfo data. At least 5 country files (africa, asia, australasia, europe, northamerica, southamerica) were updated in the NetBSD zoneinfo sources on March 18, 2000. It appears that FreeBSD has not picked up these changes yet (don't know about Debian or RedHat), and does not distribute the zoneinfo data sources in any case (at least, they don't seem to be on my machine). The source file for europe (containing Estonia) may be found at ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/share/zoneinfo/ Here is the excerpt from that file for Estonia: ------ cut here ------- # Estonia # From Peter Ilieve (1994-10-15): # A relative in Tallinn confirms the accuracy of the data for 1989 onwards # [through 1994] and gives the legal authority for it, # a regulation of the Government of Estonia, No. 111 of 1989.... # # From Peter Ilieve (1996-10-28): # [IATA SSIM (1992/1996) claims that the Baltic republics switch at 01:00s, # but a relative confirms that Estonia still switches at 02:00s, writing:] # ``I do not [know] exactly but there are some little different # (confusing) rules for International Air and Railway Transport Schedules # conversion in Sunday connected with end of summer time in Estonia.... # A discussion is running about the summer time efficiency and effect on # human physiology. It seems that Estonia maybe will not change to # summer time next spring.'' # From Peter Ilieve (1998-11-04), heavily edited: # # The 1998-09-22 Estonian time law # # refers to the Eighth Directive and cites the association agreement between # the EU and Estonia, ratified by the Estonian law (RT II 1995, 22--27, 120). # # I also asked [my relative] whether they use any standard abbreviation # for their standard and summer times. He says no, they use "suveaeg" # (summer time) and "talveaeg" (winter time). # From The Baltic Times (1999-09-09) # via Steffen Thorsen: # This year will mark the last time Estonia shifts to summer time, # a council of the ruling coalition announced Sept. 6.... # But what this could mean for Estonia's chances of joining the European # Union are still unclear. In 1994, the EU declared summer time compulsory # for all member states until 2001. Brussels has yet to decide what to do # after that. # From Mart Oruaas (2000-01-29): # Regulation no. 301 (1999-10-12) obsoletes previous regulation # no. 206 (1998-09-22) and thus sticks Estonia to +02:00 GMT for all # the year round. The regulation is effective 1999-11-01. # Zone NAME GMTOFF RULES FORMAT [UNTIL] Zone Europe/Tallinn 1:39:00 - LMT 1880 1:39:00 - TMT 1918 Feb # Tallinn Mean Time 1:00 C-Eur CE%sT 1919 Jul 1:39:00 - TMT 1921 May 2:00 - EET 1940 Aug 6 3:00 - MSK 1941 Sep 15 1:00 C-Eur CE%sT 1944 Sep 22 3:00 Russia MSK/MSD 1989 Mar 26 2:00s 2:00 1:00 EEST 1989 Sep 24 2:00s 2:00 C-Eur EE%sT 1998 Sep 22 2:00 EU EE%sT 1999 Nov 1 2:00 - EET -------- end cut ------- You will note the addition for Estonia's new regulation effective Nov 1 last year. Machines which use "zoneinfo" need a 'compiled' form of the file. You should be able to grab the data source file from the ftp URL above, run 'zic' on it to produce a new compiled file for Tallinn for each system type, and distribute the new files for a quick fix on machines to which you have access. 'zic' is in section 8 of the manuals. -------------- Duane H. Hesser dhh@androcles.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 11:31: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from math.uic.edu (galois.math.uic.edu [131.193.178.114]) by hub.freebsd.org (Postfix) with SMTP id BC76237B89A for ; Wed, 29 Mar 2000 11:30:54 -0800 (PST) (envelope-from vladimir-bsd-current@math.uic.edu) Received: (qmail 8645 invoked by uid 31415); 29 Mar 2000 19:30:41 -0000 Date: 29 Mar 2000 19:30:41 -0000 Message-ID: <20000329193041.8644.qmail@math.uic.edu> From: vladimir-bsd-current@math.uic.edu To: freebsd-current@freebsd.org Subject: any news on that? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone know if these changes have been made? Thank you! Vladimir >From owner-freebsd-current@FreeBSD.ORG Thu Mar 16 18:50:34 2000 >Delivered-To: vladimir-bsd-current@math.uic.edu >Delivered-To: freebsd-current@freebsd.org >To: freebsd-current@freebsd.org >Subject: rpc.lockd and XDR 64bit >Date: Thu, 16 Mar 2000 13:47:30 -0500 >From: "David E. Cross" >X-Loop: FreeBSD.ORG >X-Status: >X-Keywords: >X-UID: 25 > >Now that the code freeze is over, can the 64Bit XDR changes be made? This >is the only thing preventing the next release of the rpc.lockd code at this >point. > >-- >David Cross | email: crossd@cs.rpi.edu >Acting Lab Director | NYSLP: FREEBSD >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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 13:31: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36]) by hub.freebsd.org (Postfix) with ESMTP id D54A337C186 for ; Wed, 29 Mar 2000 13:30:55 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id XAA08908 for ; Wed, 29 Mar 2000 23:30:16 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma008906; Wed, 29 Mar 00 23:30:16 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id XAA10745 for ; Wed, 29 Mar 2000 23:30:15 +0200 (MET DST) Received: (qmail 80842 invoked by uid 666); 29 Mar 2000 21:30:15 -0000 Date: Wed, 29 Mar 2000 23:30:15 +0200 From: Jos Backus To: current@freebsd.org Subject: Transparent proxying using ``ipfw fwd'' seems broken as of today Message-ID: <20000329233015.B80583@hal.mpn.cp.philips.com> Reply-To: Jos Backus Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it just me or is anybody else seeing this as well with today's kernel/world? Thanks, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 15: 1:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id BAD7537B780 for ; Wed, 29 Mar 2000 15:01:37 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA65915; Wed, 29 Mar 2000 15:01:36 -0800 (PST) (envelope-from dillon) Date: Wed, 29 Mar 2000 15:01:36 -0800 (PST) From: Matthew Dillon Message-Id: <200003292301.PAA65915@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: SMP buildworld times / performance tests Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG time make -j 20 buildworld build FreeBSD-current using 4.0 kernel 4745.607u 1673.646s 1:29:07.45 120.0% 1323+1599k 8237+251565io 1615pf+0w time make -j 20 buildworld build FreeBSD-current using 5.0 kernel 4696.987u 1502.278s 1:10:34.17 146.4% 1359+1641k 10889+4270io 1779pf+0w Difference: 19 minutes, or a 21% improvement. Bob Bishop got 7% with an earlier patch (hopefully his system is no longer locking up and he can repeat his test with the current stuff). It would be interesting to see what other people get. I suspect my numbers may not be entirely accurate (I'll have to run the build a couple of times). Of course, this includes whatever other changes have gone into 5.x that haven't gone into 4.x, but I'm pretty sure the SMP patches are the major benefit to the timings. I also did some syscall timing tests between 4.0 and 5.0. Using getpid(), which is *NOT* MP-safe in 5.0 (getuid() is but for obviously reasons would not be a fair test). Under FreeBSD-4: test4:/test3/smp# ./smptime 1 3343 nsec/call 1666 nsec/call 1647 nsec/call 1646 nsec/call 1646 nsec/call 1647 nsec/call 1657 nsec/call 1646 nsec/call 1647 nsec/call 1646 nsec/call ^C test4:/test3/smp# ./smptime 2 6922 nsec/call 5122 nsec/call 5162 nsec/call 5101 nsec/call Under FreeBSD-5: test3:/test/smp# ./smptime 1 2727 nsec/call 1360 nsec/call 1359 nsec/call 1359 nsec/call 1359 nsec/call 1359 nsec/call ^C test3:/test/smp# ./smptime 2 3620 nsec/call 2252 nsec/call 2253 nsec/call 2251 nsec/call 2251 nsec/call ^C Now, I consider that significant. Even though getpid() is NOT MP safe under FreeBSD-5, the SMP patch has improved its syscall overhead in a competing-cpu's case (two forks running concurrently) by an immense degree over FreeBSD-4. 5.1uS in FreeBSD-4 went down to 2.2uS in FreeBSD-5. That's a big deal, folks! It's quite a bit more then I thought we would get. For the single-process (1-fork) case, syscall overhead improved moderately from 1.6 uS in 4.0 to 1.3 uS in 5.0. I think the marked improvement in the competing-cpu's case is due to the movement of the MP lock inward somewhat (even for syscalls that aren't MP safe), the removal of a considerable number of unnecessary 'lock'ed instructions, and the removal of the cpl lock (which benefits spl*() code as well as syscall/interrupt code). I got similar results for calling sigprocmask(): Under FreeBSD-4: test4:/test3/smp# ./smptime 1 5455 nsec/call 2742 nsec/call 2741 nsec/call 2741 nsec/call 2741 nsec/call 2741 nsec/call 2741 nsec/call 2741 nsec/call 2741 nsec/call 2740 nsec/call 2740 nsec/call 2741 nsec/call ^C test4:/test3/smp# ./smptime 2 10011 nsec/call 7291 nsec/call 7289 nsec/call 7289 nsec/call 7289 nsec/call 7294 nsec/call ^C Under FreeBSD-5: test3:/test/smp# ./smptime 1 4083 nsec/call 2044 nsec/call 2041 nsec/call 2041 nsec/call 2041 nsec/call 2041 nsec/call 2041 nsec/call 2041 nsec/call 2041 nsec/call 2041 nsec/call 2041 nsec/call ^C test3:/test/smp# ./smptime 2 6514 nsec/call 4459 nsec/call 4466 nsec/call 4474 nsec/call 4484 nsec/call 4476 nsec/call 4475 nsec/call ^C 2.7 uS -> 2.0 uS non-competing 7.3 uS -> 4.5 uS competing Very significant. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 15: 5: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id DB47937B506 for ; Wed, 29 Mar 2000 15:05:05 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA66008; Wed, 29 Mar 2000 15:04:58 -0800 (PST) (envelope-from dillon) Date: Wed, 29 Mar 2000 15:04:58 -0800 (PST) From: Matthew Dillon Message-Id: <200003292304.PAA66008@apollo.backplane.com> To: mariusz Cc: current@FreeBSD.ORG Subject: Re: panic: worklist_remove References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi : :New system FreeBSD 5.0, cvsup today. : :System reboot in message: : :panic: worklist_remove: not on list :syncing disks... panic: softdep_lock: locking against myself : :watch is wrong ? : :Mariusz Compile up a kernel with DDB so it drops into DDB when it has a problem, then 'trace' and 'ps' the next time you get this failure. -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 Wed Mar 29 15: 7:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 0F5B737BB65 for ; Wed, 29 Mar 2000 15:06:35 -0800 (PST) (envelope-from rb@gid.co.uk) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id AAA51709; Thu, 30 Mar 2000 00:05:58 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id XAA20898; Wed, 29 Mar 2000 23:54:07 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <200003290914.BAA59032@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 29 Mar 2000 23:54:08 +0100 To: Matthew Dillon From: Bob Bishop Subject: Re: src/sys/i386/isa/ipl.s rev 1.35 should fix boot lockups Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 01:14 -0800 29/3/00, Matthew Dillon wrote: >[...] > I am hoping that this will also fix Bob Bishop's reported boot lockup. It does! When I get a minute I'll rerun that timing test... -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 16:30:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mg135-034.ricochet.net [204.179.135.34]) by hub.freebsd.org (Postfix) with ESMTP id 62E4B37B7A7 for ; Wed, 29 Mar 2000 16:29:51 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA07919; Wed, 29 Mar 2000 16:33:37 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003300033.QAA07919@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests In-reply-to: Your message of "Wed, 29 Mar 2000 15:01:36 PST." <200003292301.PAA65915@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Mar 2000 16:33:36 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For the single-process (1-fork) case, syscall overhead improved > moderately from 1.6 uS in 4.0 to 1.3 uS in 5.0. I think the marked > improvement in the competing-cpu's case is due to the movement of the > MP lock inward somewhat (even for syscalls that aren't MP safe), > the removal of a considerable number of unnecessary 'lock'ed instructions, > and the removal of the cpl lock (which benefits spl*() code as well as > syscall/interrupt code). > > I got similar results for calling sigprocmask(): You should be able to remove the splhigh() from sigprocmask and run it MPSAFE. At least, I can't find a reason not to (and it works here, yes). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Wed Mar 29 16:33:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 471D137B8C4; Wed, 29 Mar 2000 16:33:08 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA66570; Wed, 29 Mar 2000 16:33:07 -0800 (PST) (envelope-from dillon) Date: Wed, 29 Mar 2000 16:33:07 -0800 (PST) From: Matthew Dillon Message-Id: <200003300033.QAA66570@apollo.backplane.com> To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests References: <200003300033.QAA07919@mass.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :You should be able to remove the splhigh() from sigprocmask and run it :MPSAFE. At least, I can't find a reason not to (and it works here, yes). : :\\ Give a man a fish, and you feed him for a day. \\ Mike Smith : Tentitively it looks like we will indeed be able to make sigprocmask() MP-safe. I have to check the rfork() case. I haven't researched why splhigh() was being used there in the first place and I have to do that as well. -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 Wed Mar 29 16:34:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mg135-034.ricochet.net [204.179.135.34]) by hub.freebsd.org (Postfix) with ESMTP id 93FDA37B65A; Wed, 29 Mar 2000 16:34:28 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA08006; Wed, 29 Mar 2000 16:38:18 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003300038.QAA08006@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Smith Cc: Matthew Dillon , freebsd-current@freebsd.org Subject: Re: SMP buildworld times / performance tests In-reply-to: Your message of "Wed, 29 Mar 2000 16:33:36 PST." <200003300033.QAA07919@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Mar 2000 16:38:18 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > For the single-process (1-fork) case, syscall overhead improved > > moderately from 1.6 uS in 4.0 to 1.3 uS in 5.0. I think the marked > > improvement in the competing-cpu's case is due to the movement of the > > MP lock inward somewhat (even for syscalls that aren't MP safe), > > the removal of a considerable number of unnecessary 'lock'ed instructions, > > and the removal of the cpl lock (which benefits spl*() code as well as > > syscall/interrupt code). > > > > I got similar results for calling sigprocmask(): > > You should be able to remove the splhigh() from sigprocmask and run it > MPSAFE. At least, I can't find a reason not to (and it works here, yes). Just following on from this, one thing that I can see immediately being very important to me at least is a spinlock in the timecounter structure. Calcru and various other things call microtime(), and we're going to want to lock out updates and parallel accesses to the timecounter. What should we be using for an interrupt-disabling spinlock? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Wed Mar 29 17: 5:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (Postfix) with ESMTP id DFAE437BA7E for ; Wed, 29 Mar 2000 17:05:38 -0800 (PST) (envelope-from kent@lab1.tfd.com) Received: from lab1.tfd.com (lab1.tfd.com [10.9.200.31]) by rtp.tfd.com (8.9.3/8.9.3) with SMTP id UAA02426 for ; Wed, 29 Mar 2000 20:06:08 -0500 (EST) Received: by lab1.tfd.com id AA07427 (5.67b/IDA-1.5 for freebsd-current@freebsd.org); Wed, 29 Mar 2000 20:03:37 -0500 Date: Wed, 29 Mar 2000 20:03:37 -0500 From: Kent Hauser Message-Id: <200003300103.AA07427@lab1.tfd.com> To: freebsd-current@freebsd.org, problem@lab1.tfd.com Subject: make rerelease Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Today I did a "make rerelease" in "/usr/src/release" and the kernels were rebuilt, but the binaries weren't. I think the following patch to "release/Makefile" fixes the problem. Basically, this patch does a "make world" for target "release" & for target "rerelease" if "/tmp/.world_done" doesn't exist. Otherwise for target "rerelease" it does "make all install". I believe this is what's wanted. As I'm a flunkie (not a commiter), I submit this for review by someone who knows what they're doing. Kent --- Makefile-dist Wed Mar 29 19:54:56 2000 +++ Makefile Wed Mar 29 19:56:16 2000 @@ -242,17 +242,19 @@ # Don't remove this, or the build will fall over! echo "export RELEASEDIR=${_R}" >> ${CHROOTDIR}/mk echo "export PATH=${BOOTSTRAPDIR}:$${PATH}:${LOCALDIR}" >> ${CHROOTDIR}/mk - echo "if [ ! -f /tmp/.world_done ]; then" >> ${CHROOTDIR}/mk echo " cd /usr/src" >> ${CHROOTDIR}/mk -.if make(release) +.if make(rerelease) + echo "if [ ! -f /tmp/.world_done ]; then" >> ${CHROOTDIR}/mk +.endif echo " (cd etc; make distrib-dirs distribution)" >> ${CHROOTDIR}/mk echo " make world" >> ${CHROOTDIR}/mk -.endif + echo " touch /tmp/.world_done" >> ${CHROOTDIR}/mk .if make(rerelease) + echo " else echo " make all install" >> ${CHROOTDIR}/mk -.endif - echo " touch /tmp/.world_done" >> ${CHROOTDIR}/mk echo "fi" >> ${CHROOTDIR}/mk +.endif echo "cd /usr/src/release/sysinstall" >> ${CHROOTDIR}/mk echo "make obj" >> ${CHROOTDIR}/mk echo "cd /usr/src/release" >> ${CHROOTDIR}/mk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 17:11:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 1E8FE37B5DA; Wed, 29 Mar 2000 17:11:49 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Wed, 29 Mar 2000 20:11:48 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Jos Backus Cc: current@freebsd.org Subject: Re: Transparent proxying using ``ipfw fwd'' seems broken as of today In-Reply-To: <20000329233015.B80583@hal.mpn.cp.philips.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 Wed, 29 Mar 2000, Jos Backus wrote: > Is it just me or is anybody else seeing this as well with today's > kernel/world? Phew, I thought I was going insane. Yes, ipfw fwd is definitely broken as of at least 3/28/2000. jlemon has found the problem and is working on a fix. > Thanks, > -- > Jos Backus _/ _/_/_/ "Reliability means never > _/ _/ _/ having to say you're sorry." > _/ _/_/_/ -- D. J. Bernstein > _/ _/ _/ _/ > Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 Mar 29 17:19:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtprelay3.adelphia.net (smtprelay3.adelphia.net [64.8.25.8]) by hub.freebsd.org (Postfix) with ESMTP id 854E937B8DE for ; Wed, 29 Mar 2000 17:19:23 -0800 (PST) (envelope-from pvlad@bigfoot.com) Received: from bigfoot.com ([24.48.148.58]) by smtprelay3.adelphia.net (Netscape Messaging Server 4.05) with ESMTP id FS7NLY00.G1T for ; Wed, 29 Mar 2000 20:17:58 -0500 Message-ID: <38E265D3.279D4F0A@bigfoot.com> Date: Wed, 29 Mar 2000 15:21:39 -0500 From: Vladik X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: en MIME-Version: 1.0 Cc: current@FreeBSD.ORG Subject: Re: Please test for 8G-OVER-Booting with /boot/loader References: <87n1njbrfj.fsf@nakaji.tutrp.tut.ac.jp> <20000328150723.A28294@midgard.dhs.org> 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 not sure if this exactly on topic, but this is how I boot freeBSD partition that is installed beyond cyl 1024 I use GRUB boot loader that understands LBA (www.gnu.org/grub) Once GRUB boots from a floppy, go to GRUB's command prompt and do the following: root (hd0,3,a) # or whatever your FreeBSD root slice is #after the command above, it mounted the partition kernel /kernel -remount boot When kernel boots to the point where it needs to mount a root partion it will ask you, in there you type ufs:/dev/ad0s4a ---- Vladislav Charles Anderson wrote: > > I have a Thinkpad 600X here that I installed freebsd on the third partition, > but couldn't boot because of the >1024 cylinder bit, so I booted a Fixit > floppy mounted my freebsd partitions, installed this patch, patched boot1 > to always try packet mode and copied it over to the ntfs boot partition and > used it from the NT Loader, and it booted right up, both natively and under > VMware. > > I had to do a lot of mucking around to get things to the point where I could > mount slice 3, the FreeBSD partition, and build the new boot code. > > -Charlie > On Tue, Mar 28, 2000 at 02:21:36PM +0900, NAKAJI Hiroyuki wrote: > > How can I test this with FreeBSD which is installed over-8GB area and > > can't boot? > > > > I have a PC on which Solaris7 is installed within 8GB from the start > > of disk and FreeBSD 3.3-RELEASE is installed after(?) it. > > > > The installation was successfull. But I can't boot it. > > > > How can I install this patched /boot/loader in this dead system? > > -- > > NAKAJI Hiroyuki > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- > Charles Anderson caa@columbus.rr.com > > No quote, no nothin' > > 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 Wed Mar 29 18: 1:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id DA03137B80E for ; Wed, 29 Mar 2000 18:01:28 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from backup.af.speednet.com.au (andyf@backup.af.speednet.com.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id MAA14931; Thu, 30 Mar 2000 12:01:09 +1000 (EST) (envelope-from andyf@speednet.com.au) Date: Thu, 30 Mar 2000 12:01:08 +1000 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests In-Reply-To: <200003292301.PAA65915@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 Wed, 29 Mar 2000, Matthew Dillon wrote: > time make -j 20 buildworld build FreeBSD-current using 4.0 kernel > > 4745.607u 1673.646s 1:29:07.45 120.0% 1323+1599k 8237+251565io 1615pf+0w > > time make -j 20 buildworld build FreeBSD-current using 5.0 kernel > > 4696.987u 1502.278s 1:10:34.17 146.4% 1359+1641k 10889+4270io 1779pf+0w Can I ask why is there a huge difference in the number of io (251k vs 4k)? What is so different between 4.0 and 5.0 that causes this? -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 18:21:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 6646B37BBBC for ; Wed, 29 Mar 2000 18:21:30 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id UAA34462; Wed, 29 Mar 2000 20:24:24 -0600 (CST) (envelope-from jlemon) Date: Wed, 29 Mar 2000 20:24:24 -0600 (CST) From: Jonathan Lemon Message-Id: <200003300224.UAA34462@prism.flugsvamp.com> To: Jos.Backus@nl.origin-it.com, current@freebsd.org Subject: Re: Transparent proxying using ``ipfw fwd'' seems broken as of today X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >Is it just me or is anybody else seeing this as well with today's >kernel/world? Yes, green just brought this to my attention. I've committed a fix that should solve the problem. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 18:25:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from ugly.prth.tensor.pgs.com (ugly.prth.tensor.pgs.com [157.147.225.240]) by hub.freebsd.org (Postfix) with ESMTP id 6F78B37B553 for ; Wed, 29 Mar 2000 18:25:20 -0800 (PST) (envelope-from shocking@ugly.prth.tensor.pgs.com) Received: from ugly (IDENT:shocking@localhost.prth.tensor.pgs.com [127.0.0.1]) by ugly.prth.tensor.pgs.com (8.9.3/8.9.3) with ESMTP id KAA25981 for ; Thu, 30 Mar 2000 10:23:13 +0800 Message-Id: <200003300223.KAA25981@ugly.prth.tensor.pgs.com> X-Mailer: exmh version 2.0.3 To: current@freebsd.org Subject: Latest kernel hangs on mounting /dev/ad0a Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Mar 2000 10:23:12 +0800 From: Stephen Hocking-Senior Programmer PGS SPS Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As at cvs-cur.6207 -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 18:46: 6 2000 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 D2C3C37B553 for ; Wed, 29 Mar 2000 18:45:57 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id VAA61637; Wed, 29 Mar 2000 21:45:46 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Wed, 29 Mar 2000 21:45:45 -0500 (EST) From: Chuck Robey To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests In-Reply-To: <200003292301.PAA65915@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 Wed, 29 Mar 2000, Matthew Dillon wrote: > time make -j 20 buildworld build FreeBSD-current using 4.0 kernel > > 4745.607u 1673.646s 1:29:07.45 120.0% 1323+1599k 8237+251565io 1615pf+0w > > time make -j 20 buildworld build FreeBSD-current using 5.0 kernel > > 4696.987u 1502.278s 1:10:34.17 146.4% 1359+1641k 10889+4270io 1779pf+0w > > Difference: 19 minutes, or a 21% improvement. Bob Bishop got 7% with an > earlier patch (hopefully his system is no longer locking up and he can > repeat his test with the current stuff). Goddamn. That's significant! Congratulations, Matt. Did it again! ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 19: 0:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 8D04637B6BB; Wed, 29 Mar 2000 19:00:51 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2U3PT013109; Wed, 29 Mar 2000 19:25:29 -0800 (PST) Date: Wed, 29 Mar 2000 19:25:29 -0800 From: Alfred Perlstein To: Mike Smith Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Using packed structs to gain cheap SMP primatives Message-ID: <20000329192526.U21029@fw.wintelcom.net> References: <200003300033.QAA07919@mass.cdrom.com> <200003300038.QAA08006@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003300038.QAA08006@mass.cdrom.com>; from msmith@FreeBSD.ORG on Wed, Mar 29, 2000 at 04:38:18PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Mike Smith [000329 17:03] wrote: > > > For the single-process (1-fork) case, syscall overhead improved > > > moderately from 1.6 uS in 4.0 to 1.3 uS in 5.0. I think the marked > > > improvement in the competing-cpu's case is due to the movement of the > > > MP lock inward somewhat (even for syscalls that aren't MP safe), > > > the removal of a considerable number of unnecessary 'lock'ed instructions, > > > and the removal of the cpl lock (which benefits spl*() code as well as > > > syscall/interrupt code). > > > > > > I got similar results for calling sigprocmask(): > > > > You should be able to remove the splhigh() from sigprocmask and run it > > MPSAFE. At least, I can't find a reason not to (and it works here, yes). > > Just following on from this, one thing that I can see immediately being > very important to me at least is a spinlock in the timecounter structure. > Calcru and various other things call microtime(), and we're going to want > to lock out updates and parallel accesses to the timecounter. What > should we be using for an interrupt-disabling spinlock? One thing everyone should be aware of is that most archs will support atomic read/write of a data value that's under a certail width (and aligned properly) Yesterday I was looking at how Linux handles the gettimeofday stuff without locking thier sys_tz variable, well it seems they don't care or I'm missing something important. They just don't lock it, not that settimeofday will be called all that often but it leaves me wondering what we can do about this, effectively we can pack our tz (sys_tz in Linux) into a 32bit value which should afford us read/write atomicity on every platform I'm aware of. In fact this can be quite effective for certain types of data structures, even though our 'struct timezone' is two ints we can pack it into two uint16 and pack a private structure, then copy it to a stack and expand it into the user's address space. What do you guys think about that? Am I totally missing something that makes the Linux way right/ok? (no locking on a 64bit struct) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@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 Mar 29 19:25:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id CEEF737B6C6; Wed, 29 Mar 2000 19:25:29 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p50-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.51]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id MAA15606; Thu, 30 Mar 2000 12:25:21 +0900 (JST) Message-ID: <38E2C8C0.C0714A65@newsguy.com> Date: Thu, 30 Mar 2000 12:23:44 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Brian Fundakowski Feldman Cc: Jeroen Ruigrok van der Werven , Sheldon Hearn , Soren Schmidt , current@FreeBSD.ORG Subject: Re: DDB and dumping disk 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 Fundakowski Feldman wrote: > > Did you try "call setdumpdev(0xf00)" with the proper show disk/ yet? > It's probably worth documenting the procedure even if it will be later > be replaced with a loader functionality... however, we should still > support the way it is now for people who want to get a dump but don't > have the ability to use loader(8) fully (Alpha?). All interaction with kernel is available on Alpha. It's only the "advanced" scripting ability (Forth) that isn't. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@zurichgnomes.bsdconspiracy.net The size of the pizza is inversely proportional to the intensity of the hunger. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 19:54: 4 2000 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 7AB6137BACB; Wed, 29 Mar 2000 19:53:59 -0800 (PST) (envelope-from obrien@NUXI.ucdavis.edu) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA11711; Wed, 29 Mar 2000 19:53:59 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA27062; Wed, 29 Mar 2000 19:53:58 -0800 (PST) (envelope-from obrien) Date: Wed, 29 Mar 2000 19:53:58 -0800 From: "David O'Brien" To: stable@freebsd.org, current@freebsd.org Subject: build broken for libobjc on RELENG_4 Message-ID: <20000329195358.A27052@dragon.nuxi.com> Reply-To: obrien@NUXI.ucdavis.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i 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 I know that the build is broken when installing libobjc on RELENG_4. I did a fat fingered typo and now need some bits to catch up to me via cvsup, but I have to leave for an hour or so. Very sorry for this. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 19:57:27 2000 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 3F72537BB45; Wed, 29 Mar 2000 19:57:24 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id WAA89938; Wed, 29 Mar 2000 22:57:21 -0500 (EST) (envelope-from wollman) Date: Wed, 29 Mar 2000 22:57:21 -0500 (EST) From: Garrett Wollman Message-Id: <200003300357.WAA89938@khavrinen.lcs.mit.edu> To: Alfred Perlstein Cc: Mike Smith , Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Using packed structs to gain cheap SMP primatives In-Reply-To: <20000329192526.U21029@fw.wintelcom.net> References: <200003300033.QAA07919@mass.cdrom.com> <200003300038.QAA08006@mass.cdrom.com> <20000329192526.U21029@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > What do you guys think about that? Am I totally missing something > that makes the Linux way right/ok? (no locking on a 64bit struct) Generally, it's better to design an optimistic or non-blocking algorithm rather than twisting data structures to fit some pre-conceived machine model just to allow atomic updates. Most architectures provide either an atomic compare-exchange instruction, or a ``load linked'' instruction, which is what you need in order to make this work. For example, there are good non-blocking algorithms for maintaining a queue given either LL or compare-exchange of 2*sizeof(pointer). Unfortunately, this requires strict queue semantics, which few parts of FreeBSD are designed to make use of. I've had as a background task for a while now the creation of a non-blocking equivalent to queue(3), with as much functionality as is possible to achieve while still maintaining the non-blocking behavior. (If you were ever wondering why it was that struct socket and struct inpcb had grown version numbers: it is for similar reasons. If I were only smart enough to figure out how, I would have made all socket and pcb accesses non-blocking.) -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 Wed Mar 29 20:36:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id B09F537BC67; Wed, 29 Mar 2000 20:36:12 -0800 (PST) (envelope-from pulsifer@mediaone.net) Received: from ahp3 (ahp.ne.mediaone.net [24.128.184.250]) by chmls06.mediaone.net (8.8.7/8.8.7) with SMTP id XAA03320; Wed, 29 Mar 2000 23:36:04 -0500 (EST) From: "Allen Pulsifer" To: "Alfred Perlstein" , "Mike Smith" Cc: "Matthew Dillon" , Subject: RE: Using packed structs to gain cheap SMP primatives Date: Wed, 29 Mar 2000 23:36:05 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20000329192526.U21029@fw.wintelcom.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's another alternative for reading structures like time that always change monotonically: read the values in "MSB" to "LSB" order, then go back and check in reverse order that nothing has changed. For example, to read a structure containing hours, minutes, seconds: for (;;) { h = timep->hour; m = timep->minute; s = timep->second; if (m != timep->minute) continue; if (h != timep->hour) continue; break; } The assumption is that from the instant you first read timep->hour until the instant you double check its value, it could not have wrapped all the way back around to its previous value. Or to put it another way, if it has succeeding in wrapping all the way around, having a correct snapshot of the structure is the least of your problems and the value you use is arbitary. This same method can be used to read the MSW and LSW of any counter-like structure that is updated by an interrupt. Note this method will not work for a structure that can both increment and decrement--it has to be only one or the other. Allen > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Alfred Perlstein > Sent: Wednesday, March 29, 2000 10:25 PM > To: Mike Smith > Cc: Matthew Dillon; freebsd-current@FreeBSD.ORG > Subject: Using packed structs to gain cheap SMP primatives > > > * Mike Smith [000329 17:03] wrote: > > > > For the single-process (1-fork) case, syscall overhead improved > > > > moderately from 1.6 uS in 4.0 to 1.3 uS in 5.0. I think the marked > > > > improvement in the competing-cpu's case is due to the movement of the > > > > MP lock inward somewhat (even for syscalls that aren't MP safe), > > > > the removal of a considerable number of unnecessary 'lock'ed instructions, > > > > and the removal of the cpl lock (which benefits spl*() code as well as > > > > syscall/interrupt code). > > > > > > > > I got similar results for calling sigprocmask(): > > > > > > You should be able to remove the splhigh() from sigprocmask and run it > > > MPSAFE. At least, I can't find a reason not to (and it works here, yes). > > > > Just following on from this, one thing that I can see immediately being > > very important to me at least is a spinlock in the timecounter structure. > > Calcru and various other things call microtime(), and we're going to want > > to lock out updates and parallel accesses to the timecounter. What > > should we be using for an interrupt-disabling spinlock? > > One thing everyone should be aware of is that most archs will support > atomic read/write of a data value that's under a certail width (and > aligned properly) > > Yesterday I was looking at how Linux handles the gettimeofday stuff > without locking thier sys_tz variable, well it seems they don't care > or I'm missing something important. > > They just don't lock it, not that settimeofday will be called all that > often but it leaves me wondering what we can do about this, effectively > we can pack our tz (sys_tz in Linux) into a 32bit value which should > afford us read/write atomicity on every platform I'm aware of. > > In fact this can be quite effective for certain types of data structures, > even though our 'struct timezone' is two ints we can pack it into two > uint16 and pack a private structure, then copy it to a stack and expand > it into the user's address space. > > What do you guys think about that? Am I totally missing something > that makes the Linux way right/ok? (no locking on a 64bit struct) > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > > > 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 Wed Mar 29 21: 5: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id 6D12C37B764; Wed, 29 Mar 2000 21:04:48 -0800 (PST) (envelope-from pulsifer@mediaone.net) Received: from ahp3 (ahp.ne.mediaone.net [24.128.184.250]) by chmls06.mediaone.net (8.8.7/8.8.7) with SMTP id AAA10557; Thu, 30 Mar 2000 00:03:45 -0500 (EST) From: "Allen Pulsifer" To: "Allen Pulsifer" , "Alfred Perlstein" , "Mike Smith" Cc: "Matthew Dillon" , Subject: RE: Using packed structs to gain cheap SMP primatives Date: Thu, 30 Mar 2000 00:03:45 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, I spoke too soon. That's an algorithm used to read deglitched hardware counters or ISR counters on a single processor machine. But it may not be safe in a multiprocessor environment where one CPU can read the structure while a second CPU can be updating the structure. There may be a way to update the structure in a way that is MP safe, but I'll have to think about it some more. Sorry. Allen (with foot planted firmly in mouth) > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Allen Pulsifer > Sent: Wednesday, March 29, 2000 11:36 PM > To: Alfred Perlstein; Mike Smith > Cc: Matthew Dillon; freebsd-current@FreeBSD.ORG > Subject: RE: Using packed structs to gain cheap SMP primatives > > > Here's another alternative for reading structures like time > that always change monotonically: read the values in > "MSB" to "LSB" order, then go back and check in reverse > order that nothing has changed. For example, to read a > structure containing hours, minutes, seconds: > > for (;;) > { h = timep->hour; > m = timep->minute; > s = timep->second; > if (m != timep->minute) continue; > if (h != timep->hour) continue; > break; > } > > The assumption is that from the instant you first read > timep->hour until the instant you double check its value, > it could not have wrapped all the way back around to its > previous value. Or to put it another way, if it has > succeeding in wrapping all the way around, having a > correct snapshot of the structure is the least of your > problems and the value you use is arbitary. > > This same method can be used to read the MSW and LSW of > any counter-like structure that is updated by an interrupt. > > Note this method will not work for a structure that can > both increment and decrement--it has to be only one or > the other. > > Allen > > > > -----Original Message----- > > From: owner-freebsd-current@FreeBSD.ORG > > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Alfred Perlstein > > Sent: Wednesday, March 29, 2000 10:25 PM > > To: Mike Smith > > Cc: Matthew Dillon; freebsd-current@FreeBSD.ORG > > Subject: Using packed structs to gain cheap SMP primatives > > > > > > * Mike Smith [000329 17:03] wrote: > > > > > For the single-process (1-fork) case, syscall overhead improved > > > > > moderately from 1.6 uS in 4.0 to 1.3 uS in 5.0. I think the marked > > > > > improvement in the competing-cpu's case is due to the movement of the > > > > > MP lock inward somewhat (even for syscalls that aren't MP safe), > > > > > the removal of a considerable number of unnecessary 'lock'ed instructions, > > > > > and the removal of the cpl lock (which benefits spl*() code as well as > > > > > syscall/interrupt code). > > > > > > > > > > I got similar results for calling sigprocmask(): > > > > > > > > You should be able to remove the splhigh() from sigprocmask and run it > > > > MPSAFE. At least, I can't find a reason not to (and it works here, yes). > > > > > > Just following on from this, one thing that I can see immediately being > > > very important to me at least is a spinlock in the timecounter structure. > > > Calcru and various other things call microtime(), and we're going to want > > > to lock out updates and parallel accesses to the timecounter. What > > > should we be using for an interrupt-disabling spinlock? > > > > One thing everyone should be aware of is that most archs will support > > atomic read/write of a data value that's under a certail width (and > > aligned properly) > > > > Yesterday I was looking at how Linux handles the gettimeofday stuff > > without locking thier sys_tz variable, well it seems they don't care > > or I'm missing something important. > > > > They just don't lock it, not that settimeofday will be called all that > > often but it leaves me wondering what we can do about this, effectively > > we can pack our tz (sys_tz in Linux) into a 32bit value which should > > afford us read/write atomicity on every platform I'm aware of. > > > > In fact this can be quite effective for certain types of data structures, > > even though our 'struct timezone' is two ints we can pack it into two > > uint16 and pack a private structure, then copy it to a stack and expand > > it into the user's address space. > > > > What do you guys think about that? Am I totally missing something > > that makes the Linux way right/ok? (no locking on a 64bit struct) > > > > -- > > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 21:19:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id D326F37B604; Wed, 29 Mar 2000 21:19:44 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2U5iMS18883; Wed, 29 Mar 2000 21:44:22 -0800 (PST) Date: Wed, 29 Mar 2000 21:44:22 -0800 From: Alfred Perlstein To: Allen Pulsifer Cc: Mike Smith , Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: Using packed structs to gain cheap SMP primatives Message-ID: <20000329214422.X21029@fw.wintelcom.net> References: <20000329192526.U21029@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from pulsifer@mediaone.net on Wed, Mar 29, 2000 at 11:36:05PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Allen Pulsifer [000329 21:05] wrote: > Here's another alternative for reading structures like time > that always change monotonically: read the values in > "MSB" to "LSB" order, then go back and check in reverse > order that nothing has changed. For example, to read a > structure containing hours, minutes, seconds: > > for (;;) > { h = timep->hour; > m = timep->minute; > s = timep->second; > if (m != timep->minute) continue; > if (h != timep->hour) continue; > break; > } > > The assumption is that from the instant you first read > timep->hour until the instant you double check its value, > it could not have wrapped all the way back around to its > previous value. Or to put it another way, if it has > succeeding in wrapping all the way around, having a > correct snapshot of the structure is the least of your > problems and the value you use is arbitary. > > This same method can be used to read the MSW and LSW of > any counter-like structure that is updated by an interrupt. > > Note this method will not work for a structure that can > both increment and decrement--it has to be only one or > the other. I'm aware of this, the problem is that tz may move in either direction. Hence my question about using sizes that are machine atomic for read/write. :) I've got several books on various systems here and I don't remeber any of them mentioning a problem with 32bit aligned updates being atomic. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 21:26:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 98D6337B764 for ; Wed, 29 Mar 2000 21:26:50 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id XAA40214; Wed, 29 Mar 2000 23:30:00 -0600 (CST) (envelope-from jlemon) Date: Wed, 29 Mar 2000 23:30:00 -0600 (CST) From: Jonathan Lemon Message-Id: <200003300530.XAA40214@prism.flugsvamp.com> To: bright@wintelcom.net, current@freebsd.org Subject: Re: Using packed structs to gain cheap SMP primatives X-Newsgroups: local.mail.freebsd-current In-Reply-To: References: Organization: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >* Allen Pulsifer [000329 21:05] wrote: >> Here's another alternative for reading structures like time >> that always change monotonically: read the values in >> "MSB" to "LSB" order, then go back and check in reverse >> order that nothing has changed. For example, to read a >> structure containing hours, minutes, seconds: >> >> for (;;) >> { h = timep->hour; >> m = timep->minute; >> s = timep->second; >> if (m != timep->minute) continue; >> if (h != timep->hour) continue; >> break; >> } >> >> The assumption is that from the instant you first read >> timep->hour until the instant you double check its value, >> it could not have wrapped all the way back around to its >> previous value. Or to put it another way, if it has >> succeeding in wrapping all the way around, having a >> correct snapshot of the structure is the least of your >> problems and the value you use is arbitary. >> >> This same method can be used to read the MSW and LSW of >> any counter-like structure that is updated by an interrupt. >> >> Note this method will not work for a structure that can >> both increment and decrement--it has to be only one or >> the other. > >I'm aware of this, the problem is that tz may move in either >direction. Hence my question about using sizes that are machine >atomic for read/write. :) > >I've got several books on various systems here and I don't remeber >any of them mentioning a problem with 32bit aligned updates being >atomic. Each architecture will define what is atomic or not. Most modern architectures will provide atomic access to their native word size, provided it is aligned on a natural word boundary. On the PPro and upwards, 64 bit reads/writes to quadword aligned structures are atomic. it's just too bad that there is no direct 64-bit read insn (excluding FP). -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 21:32:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mccons.maxbaud.net (adsl-208-191-215-92.dsl.kscymo.swbell.net [208.191.215.92]) by hub.freebsd.org (Postfix) with ESMTP id E221737BB6B for ; Wed, 29 Mar 2000 21:32:38 -0800 (PST) (envelope-from root@mccons.maxbaud.net) Received: from localhost (root@localhost) by mccons.maxbaud.net (8.9.3/8.9.3) with SMTP id XAA47799; Wed, 29 Mar 2000 23:32:26 -0600 (CST) (envelope-from root@mccons.maxbaud.net) Date: Wed, 29 Mar 2000 23:32:25 -0600 (CST) From: Wm Brian McCane X-Sender: root@localhost To: Chris Costello Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: kernel trap 9 In-Reply-To: <20000328162145.R18325@holly.calldei.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 Chris, Sorry, I didn't know what was needed. I have also located the problem (well, sort of). I built a GENERIC kernel, and then made incremental changes until I had my old working kernel back. The problem appears to be in the code for one of the following options: CLK_CALIBRATION_LOOP CLK_USE_I8254_CALIBRATION CLK_USE_TSC_CALIBRATION I don't need these anymore (my machine figures out the clock speed when it boots without them), so I didn't try to isolate which was at fault. If people would like, I can turn these on one at a time and see which is causing it. If I remember correctly from when I last looked at the code, CLK_CALIBRATION_LOOP turns on the feature and the other 2 select variations on how it is handled. brian +-----------------------------------+------------------------------------------+ He rides a cycle of mighty days, and \ Wm Brian and Lori McCane represents the last great schizm among\ McCane Consulting the gods. Evil though he obviously is, \ root@bmccane.maxbaud.net he is a mighty figure, this father of \ http://bmccane.maxbaud.net/ my spirit, and I respect him as the sons \ http://www.sellit-here.com/ of old did the fathers of their bodies. \ http://kidsearch.maxbaud.net/ Roger Zelazny - "Lord of Light" \ http://www.maxbaud.net/ +-------------------------------------------+----------------------------------+ On Tue, 28 Mar 2000, Chris Costello wrote: > On Tuesday, March 28, 2000, Wm Brian McCane wrote: > > Fatal trap 9: general protection fault in kernel mode > > > > Why did you remove the vital information needed to track down > and fix the problem? > > -- > |Chris Costello > |A paperless office has about as much chance as a paperless bathroom. > `-------------------------------------------------------------------- > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 29 21:46: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 90CC837B6F6; Wed, 29 Mar 2000 21:46:06 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2U6Agh20172; Wed, 29 Mar 2000 22:10:42 -0800 (PST) Date: Wed, 29 Mar 2000 22:10:42 -0800 From: Alfred Perlstein To: Jonathan Lemon Cc: current@FreeBSD.ORG, dillon@FreeBSD.ORG, alc@FreeBSD.ORG Subject: Re: Using packed structs to gain cheap SMP primatives Message-ID: <20000329221042.Y21029@fw.wintelcom.net> References: <200003300530.XAA40214@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003300530.XAA40214@prism.flugsvamp.com>; from jlemon@flugsvamp.com on Wed, Mar 29, 2000 at 11:30:00PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jonathan Lemon [000329 21:52] wrote: > In article you write: > > > >I'm aware of this, the problem is that tz may move in either > >direction. Hence my question about using sizes that are machine > >atomic for read/write. :) > > > >I've got several books on various systems here and I don't remeber > >any of them mentioning a problem with 32bit aligned updates being > >atomic. > > Each architecture will define what is atomic or not. Most modern > architectures will provide atomic access to their native word size, > provided it is aligned on a natural word boundary. > > On the PPro and upwards, 64 bit reads/writes to quadword aligned > structures are atomic. it's just too bad that there is no direct > 64-bit read insn (excluding FP). What I'm calling for is a vote if we'll rely on this type of behavior (32 bit stores being atomic with respect to readers) or not, or perhaps to rely on it but mark it somehow so people can "fix it" if the need arises later by using other locking primatives on what should be atomic updates. My vote is yes. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@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 Mar 29 22: 0:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 6F03037B522 for ; Wed, 29 Mar 2000 22:00:48 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA68006; Wed, 29 Mar 2000 22:00:41 -0800 (PST) (envelope-from dillon) Date: Wed, 29 Mar 2000 22:00:41 -0800 (PST) From: Matthew Dillon Message-Id: <200003300600.WAA68006@apollo.backplane.com> To: Andy Farkas Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> time make -j 20 buildworld build FreeBSD-current using 4.0 kernel :> :> 4745.607u 1673.646s 1:29:07.45 120.0% 1323+1599k 8237+251565io 1615pf+0w :> :> time make -j 20 buildworld build FreeBSD-current using 5.0 kernel :> :> 4696.987u 1502.278s 1:10:34.17 146.4% 1359+1641k 10889+4270io 1779pf+0w : :Can I ask why is there a huge difference in the number of io (251k vs 4k)? :What is so different between 4.0 and 5.0 that causes this? That is very odd. I'm using the same make.conf on both machines but even if they weren't the same 19 minutes should not make that sort of difference in I/O statistics. There are two possibilities: Either 5.0 is doing something very different in regards to I/O, or I have another patch in 5.0 that is causing the difference. I do have one other patch in 5.0 that could be causing the difference. I added the sequential heuristic code that read() is using to write() to determine whether to push out the cluster or not. I'm using the heuristic to 'detect' non-sequential behavior (aka the DBM random I/O test that was bantied about in an earlier thread which was tripping over cluster pushouts). I discounted it before because I figured that compiling would almost always be doing sequential writes anyway and thus result in the same behavior. Maybe I'm wrong. I am going to disable the patch in the 5.0 test to see if that accounts for the reduced I/O. If so then I guess I get to still claim credit, but it will have been due to the sequential write heuristic instead of the SMP stuff :-) -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 Wed Mar 29 22: 4:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8CCA337BC7F for ; Wed, 29 Mar 2000 22:04:22 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA68031; Wed, 29 Mar 2000 22:04:17 -0800 (PST) (envelope-from dillon) Date: Wed, 29 Mar 2000 22:04:17 -0800 (PST) From: Matthew Dillon Message-Id: <200003300604.WAA68031@apollo.backplane.com> To: Andy Farkas Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> 4696.987u 1502.278s 1:10:34.17 146.4% 1359+1641k 10889+4270io 1779pf+0w : :Can I ask why is there a huge difference in the number of io (251k vs 4k)? :What is so different between 4.0 and 5.0 that causes this? : :-- : : Andy Farkas Ha! I found it. Kirk gets the credit --- softupdates was turned on in one of the machine's /usr/obj's and off on the other machine's. So softupdates improves buildworld times by a significant margin. I've turned softupdates on on both machines and am rerunning the test. I expect I will see an improvement closer to what Bob Bishop saw when he ran the test (7% or so) rather then 20+%. -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 Wed Mar 29 22: 7:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (peter1.yahoo.com [208.48.107.4]) by hub.freebsd.org (Postfix) with ESMTP id 200D837BBBB for ; Wed, 29 Mar 2000 22:07:14 -0800 (PST) (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 B400E1CD7; Wed, 29 Mar 2000 22:07:08 -0800 (PST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests In-Reply-To: Message from Matthew Dillon of "Wed, 29 Mar 2000 22:00:41 PST." <200003300600.WAA68006@apollo.backplane.com> Date: Wed, 29 Mar 2000 22:07:08 -0800 From: Peter Wemm Message-Id: <20000330060708.B400E1CD7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > :> time make -j 20 buildworld build FreeBSD-current using 4.0 kernel > :> > :> 4745.607u 1673.646s 1:29:07.45 120.0% 1323+1599k 8237+251565io 1615p f+0w > :> > :> time make -j 20 buildworld build FreeBSD-current using 5.0 kernel > :> > :> 4696.987u 1502.278s 1:10:34.17 146.4% 1359+1641k 10889+4270io 1779pf +0w > : > :Can I ask why is there a huge difference in the number of io (251k vs 4k)? > :What is so different between 4.0 and 5.0 that causes this? > > That is very odd. I'm using the same make.conf on both machines > but even if they weren't the same 19 minutes should not make that sort > of difference in I/O statistics. One other possibility.. was the state of /usr/obj the same? make world does a lot less IO and is generally a fair bit quicker if /usr/obj is empty from the start. Just a thought... 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 Mar 29 22:28:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mg136-158.ricochet.net [204.179.136.158]) by hub.freebsd.org (Postfix) with ESMTP id 7C02337B590 for ; Wed, 29 Mar 2000 22:28:03 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA00497; Wed, 29 Mar 2000 22:31:18 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003300631.WAA00497@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alfred Perlstein Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: Using packed structs to gain cheap SMP primatives In-reply-to: Your message of "Wed, 29 Mar 2000 19:25:29 PST." <20000329192526.U21029@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Mar 2000 22:31:17 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yesterday I was looking at how Linux handles the gettimeofday stuff > without locking thier sys_tz variable, well it seems they don't care > or I'm missing something important. > > They just don't lock it, not that settimeofday will be called all that > often but it leaves me wondering what we can do about this, effectively > we can pack our tz (sys_tz in Linux) into a 32bit value which should > afford us read/write atomicity on every platform I'm aware of. > > In fact this can be quite effective for certain types of data structures, > even though our 'struct timezone' is two ints we can pack it into two > uint16 and pack a private structure, then copy it to a stack and expand > it into the user's address space. It would be cheaper just to lock the bloody thing, although you can't pack all the significance of a timeval into 16 bits anyway (in a fashion that's going to make many people happy). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Wed Mar 29 22:47: 7 2000 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 E89A837BC55; Wed, 29 Mar 2000 22:47:00 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id IAA02923; Thu, 30 Mar 2000 08:46:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: Alfred Perlstein , Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: Using packed structs to gain cheap SMP primatives In-reply-to: Your message of "Wed, 29 Mar 2000 22:31:17 -0800." <200003300631.WAA00497@mass.cdrom.com> Date: Thu, 30 Mar 2000 08:46:57 +0200 Message-ID: <2921.954398817@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003300631.WAA00497@mass.cdrom.com>, Mike Smith writes: >> Yesterday I was looking at how Linux handles the gettimeofday stuff >> without locking thier sys_tz variable, well it seems they don't care >> or I'm missing something important. >> >> They just don't lock it, not that settimeofday will be called all that >> often but it leaves me wondering what we can do about this, effectively >> we can pack our tz (sys_tz in Linux) into a 32bit value which should >> afford us read/write atomicity on every platform I'm aware of. >> >> In fact this can be quite effective for certain types of data structures, >> even though our 'struct timezone' is two ints we can pack it into two >> uint16 and pack a private structure, then copy it to a stack and expand >> it into the user's address space. > >It would be cheaper just to lock the bloody thing, although you can't >pack all the significance of a timeval into 16 bits anyway (in a fashion >that's going to make many people happy). Or do the "stable-storage" thing with it, and just grab a copy of the pointer (which will be an atomic op). See timecounters for an example. -- 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 Wed Mar 29 23:27:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 38B5037BC50; Wed, 29 Mar 2000 23:27:11 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id JAA17545; Thu, 30 Mar 2000 09:27:06 +0200 (CEST) (envelope-from asmodai) Date: Thu, 30 Mar 2000 09:27:06 +0200 From: Jeroen Ruigrok van der Werven To: Brian Fundakowski Feldman Cc: Sheldon Hearn , current@FreeBSD.org Subject: Re: DDB and dumping disk Message-ID: <20000330092706.A17338@lucifer.bart.nl> References: <20000328132626.F94986@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from green@FreeBSD.org on Tue, Mar 28, 2000 at 07:13:34PM -0500 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000329 02:15], Brian Fundakowski Feldman (green@FreeBSD.org) wrote: >On Tue, 28 Mar 2000, Jeroen Ruigrok van der Werven wrote: > >Did you try "call setdumpdev(0xf00)" with the proper show disk/ yet? I tried: db> show disk/ad0s1b 0xc0b65880 bd> write dumpdev 0xc0b65880 dumpdev: ffffffff -> 0xc0b65880 bd> call setdumpdev(0xc0b65880) Unknown symbol So again, I am probably doing something wrong. =) -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl That's your Destiny, the only chance, take it, take it in your hands... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 0:12:48 2000 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 A371937B66C; Thu, 30 Mar 2000 00:12:44 -0800 (PST) (envelope-from obrien@NUXI.ucdavis.edu) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id AAA12694; Thu, 30 Mar 2000 00:12:12 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id AAA27757; Thu, 30 Mar 2000 00:12:12 -0800 (PST) (envelope-from obrien) Date: Thu, 30 Mar 2000 00:12:12 -0800 From: "David O'Brien" To: stable@freebsd.org, current@freebsd.org Subject: BUILD FIXED (was: build broken for libobjc on RELENG_4) Message-ID: <20000330001211.A27737@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000329195358.A27052@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000329195358.A27052@dragon.nuxi.com>; from obrien@NUXI.ucdavis.edu on Wed, Mar 29, 2000 at 07:53:58PM -0800 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 build breakage due to libobjc has been fixed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 2: 0:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 6D89137BB8D for ; Thu, 30 Mar 2000 02:00:14 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id CAA02071; Thu, 30 Mar 2000 02:00:01 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id CAA06996; Thu, 30 Mar 2000 02:00:00 -0800 (PST) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id BAA01712; Thu, 30 Mar 2000 01:59:59 -0800 (PST) From: Don Lewis Message-Id: <200003300959.BAA01712@salsa.gv.tsc.tdk.com> Date: Thu, 30 Mar 2000 01:59:59 -0800 In-Reply-To: <200003201900.LAA05709@bubba.whistle.com> References: <200003201900.LAA05709@bubba.whistle.com> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Archie Cobbs , Don.Lewis@tsc.tdk.com (Don Lewis) Subject: Re: kern/8324 Cc: bright@wintelcom.net (Alfred Perlstein), freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mar 20, 11:00am, Archie Cobbs wrote: } Subject: Re: kern/8324 } Don Lewis writes: } > This patch (vs the 3.4-STABLE version of tty.c) causes SIGIO to be } > sent when a regular or pseudo tty becomes writeable. } > } > } > --- tty.c.orig Sun Aug 29 09:26:09 1999 } > +++ tty.c Sat Mar 18 03:09:32 2000 } > @@ -2133,6 +2133,8 @@ } > } > if (tp->t_wsel.si_pid != 0 && tp->t_outq.c_cc <= tp->t_olowat) } > selwakeup(&tp->t_wsel); } > + if (ISSET(tp->t_state, TS_ASYNC) && tp->t_sigio != NULL) } > + pgsigio(tp->t_sigio, SIGIO, (tp->t_session != NULL)); } > if (ISSET(tp->t_state, TS_BUSY | TS_SO_OCOMPLETE) == } > TS_SO_OCOMPLETE && tp->t_outq.c_cc == 0) { } > CLR(tp->t_state, TS_SO_OCOMPLETE); } > } > } > BTW, I had to add: } > fcntl(1, F_SETOWN, getpid()); } > to the test program since there is no longer a default target to send } > the signal to. The old scheme had the defect of sending SIGIO to the } > process group that owned the terminal, which implied that the terminal } > had to be the controlling terminal for the process group. This limited } > a process to only receiving SIGIO from one terminal device even if it } > had more than one open and it wanted to receive SIGIO from all of them. } > Also, SIGIO was sent to the entire process group, but it may be desireable } > to limit this to one process. I wonder if it might make sense to go } > back to the old default for tty devices so that processes only receive } > SIGIO when they are in the foreground ... } } Don- } } After applying your patch to kern/tty.c and adding the F_SETOWN, } the problem indeed seems to go away.. } } Is this patch ready to be committed, or do we need more reviewers? Sorry for the delay, I was out of town most of last week and sick most of this week. It's probably safe to commit to -current if someone can give it a quick test there. Unfortunately I don't have a box running -current to test it on. Now, on to some more of my 6280 unread email messages :-( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 2: 3:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id DE0D237BD83 for ; Thu, 30 Mar 2000 02:03:19 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.22.136] (dialup220.brussels.skynet.be [195.238.19.220]) by trinity.skynet.be (Postfix) with ESMTP id 12DF2181DF; Thu, 30 Mar 2000 12:03:02 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Thu, 30 Mar 2000 11:39:04 +0200 To: Chuck Robey , Matthew Dillon From: Brad Knowles Subject: Re: SMP buildworld times / performance tests Cc: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:45 PM -0500 2000/3/29, Chuck Robey wrote: >> Difference: 19 minutes, or a 21% improvement. Bob Bishop got 7% with an >> earlier patch (hopefully his system is no longer locking up and he can >> repeat his test with the current stuff). > > Goddamn. That's significant! Congratulations, Matt. Did it again! You're not kidding! This is OUTSTANDING! I can't wait for this stuff to get MFC'ed to 4.0-STABLE.... -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 2:25:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id C2E3F37B8F4 for ; Thu, 30 Mar 2000 02:25:51 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.22.136] (dialup220.brussels.skynet.be [195.238.19.220]) by morpheus.skynet.be (Postfix) with ESMTP id 5F04EDAFB; Thu, 30 Mar 2000 12:25:46 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200003300604.WAA68031@apollo.backplane.com> References: <200003300604.WAA68031@apollo.backplane.com> Date: Thu, 30 Mar 2000 12:25:06 +0200 To: Matthew Dillon , Andy Farkas From: Brad Knowles Subject: Re: SMP buildworld times / performance tests Cc: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:04 PM -0800 2000/3/29, Matthew Dillon wrote: > So softupdates improves buildworld times by a significant margin. Uh, I think we've known this for a while now. ;-) Still, I'm looking forward to finding out what the new timings are for SMP builds with the new code (both with and without softupdates), and I still can't wait to get this stuff MFC's to 4.0-STABLE. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 2:31: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 02BBF37BA7C for ; Thu, 30 Mar 2000 02:31:01 -0800 (PST) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id MAA59517; Thu, 30 Mar 2000 12:31:08 +0200 (CEST) (envelope-from assar) To: Alfred Perlstein Cc: freebsd-current@FreeBSD.ORG Subject: Re: Using packed structs to gain cheap SMP primatives References: <20000329192526.U21029@fw.wintelcom.net> <20000329214422.X21029@fw.wintelcom.net> From: Assar Westerlund Date: 30 Mar 2000 12:31:07 +0200 In-Reply-To: Alfred Perlstein's message of "Wed, 29 Mar 2000 21:44:22 -0800" Message-ID: <5l1z4sn40k.fsf@assaris.sics.se> Lines: 17 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: > I'm aware of this, the problem is that tz may move in either > direction. Why not just ignore the timezone argument? That hasn't been relevant for a long time. The timezone information is kept in user-space. From gettimeofday(2): Note: timezone is no longer used; this information is kept outside the kernel. And single unix standard says: If tzp is not a null pointer, the behaviour is unspecified. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 2:39:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 4D8AA37B57E for ; Thu, 30 Mar 2000 02:39:44 -0800 (PST) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id MAA59537; Thu, 30 Mar 2000 12:39:59 +0200 (CEST) (envelope-from assar) From: Assar Westerlund To: freebsd-current@FreeBSD.ORG Subject: kernel building problems/room-for-improvement Date: 30 Mar 2000 12:39:59 +0200 Message-ID: <5ln1nglp1c.fsf@assaris.sics.se> Lines: 20 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would appreciate some feedback (in the form of commits also works) on two small issues (I've also opened PR's on these). 1. Due to vnode_if.h not getting installed, you need to have kernel source (namely vnode_if.src and vnode_if.pl) to build any file system to be loaded as a kernel module. This is unfortunate and should be fairly easy to solve by installing vnode_if.h. See PR kern/17613. 2. It's hard to build some KLD that use macros from without optimization in some cases. The particular case that I triggered was the definition of __cursig in as `extern __inline' instead of `static __inline'. I don't think there's any particular good reason to not have everything build without -O and the fix (included in the PR) for this problem is trivial. See PR kern/17614. Comments? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 3:25: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 2416F37C0D4; Thu, 30 Mar 2000 03:24:53 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id VAA09454; Thu, 30 Mar 2000 21:30:04 +1000 Date: Thu, 30 Mar 2000 21:24:28 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Mike Smith Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests In-Reply-To: <200003300038.QAA08006@mass.cdrom.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 Wed, 29 Mar 2000, Mike Smith wrote: > Just following on from this, one thing that I can see immediately being > very important to me at least is a spinlock in the timecounter structure. > Calcru and various other things call microtime(), and we're going to want > to lock out updates and parallel accesses to the timecounter. What > should we be using for an interrupt-disabling spinlock? Nothing. Accesses to the timecounter struct are already MP safe and fast. Only the i8254 timecounter hardware currently needs interrupt-disabling, but it is hopefully never used on SMP machines. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 3:35:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 0A62037B590 for ; Thu, 30 Mar 2000 03:35:53 -0800 (PST) (envelope-from freebsd@ewok.creative.net.au) Received: (qmail 32462 invoked by uid 1008); 30 Mar 2000 11:35:46 -0000 Date: Thu, 30 Mar 2000 19:35:46 +0800 From: Adrian Chadd To: Assar Westerlund Cc: freebsd-current@FreeBSD.ORG Subject: Re: kernel building problems/room-for-improvement Message-ID: <20000330193545.D21291@ewok.creative.net.au> References: <5ln1nglp1c.fsf@assaris.sics.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <5ln1nglp1c.fsf@assaris.sics.se>; from Assar Westerlund on Thu, Mar 30, 2000 at 12:39:59PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 30, 2000, Assar Westerlund wrote: > I would appreciate some feedback (in the form of commits also works) > on two small issues (I've also opened PR's on these). > > 1. Due to vnode_if.h not getting installed, you need to have kernel > source (namely vnode_if.src and vnode_if.pl) to build any file > system to be loaded as a kernel module. This is unfortunate and > should be fairly easy to solve by installing vnode_if.h. See PR > kern/17613. > I agree that vnode_if.h needs to be in the sys/ tree for this, but I don't think it needs to be checked into CVS. It means any time someone modifies vnode_if.src a whole new vnode_if.h could possibly be generated, causing unnecessary repobloat. How about having it built as part of populating /usr/include/sys/ ? Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 3:55: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.43.150]) by hub.freebsd.org (Postfix) with ESMTP id E4FBC37B70B; Thu, 30 Mar 2000 03:55:05 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id NAA01276; Thu, 30 Mar 2000 13:37:32 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: Mike Smith , Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests In-reply-to: Your message of "Thu, 30 Mar 2000 21:24:28 +1000." Date: Thu, 30 Mar 2000 13:37:32 +0200 Message-ID: <1274.954416252@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Bruce Ev ans writes: >On Wed, 29 Mar 2000, Mike Smith wrote: > >> Just following on from this, one thing that I can see immediately being >> very important to me at least is a spinlock in the timecounter structure. >> Calcru and various other things call microtime(), and we're going to want >> to lock out updates and parallel accesses to the timecounter. What >> should we be using for an interrupt-disabling spinlock? > >Nothing. Accesses to the timecounter struct are already MP safe and fast. >Only the i8254 timecounter hardware currently needs interrupt-disabling, >but it is hopefully never used on SMP machines. Worse. It is used by default on SMP machines which don't sport the PIIX timecounter. -- 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 Thu Mar 30 3:57: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id BC5EB37B872; Thu, 30 Mar 2000 03:56:57 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup3-10.iptelecom.net.ua [212.9.226.138]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id PAA18398; Thu, 30 Mar 2000 15:02:44 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id OAA97509; Thu, 30 Mar 2000 14:56:16 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <38E340E1.43E443D3@altavista.net> Date: Thu, 30 Mar 2000 14:56:17 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org, multimedia@freebsd.org Subject: What is the status of the mmap support in the pcm driver? Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Does anybody can clarify what is current status of the mmap support in the pcm driver? I'm trying to get sound in the quakeforge working, but only managed to get famous "dsp_mmap." message in kernel logs instead of sound :(. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 4:27:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id B1F3837B7F3; Thu, 30 Mar 2000 04:27:41 -0800 (PST) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id OAA59668; Thu, 30 Mar 2000 14:27:56 +0200 (CEST) (envelope-from assar) From: Assar Westerlund To: Adrian Chadd Cc: freebsd-current@FreeBSD.ORG Subject: Re: kernel building problems/room-for-improvement References: <5ln1nglp1c.fsf@assaris.sics.se> <20000330193545.D21291@ewok.creative.net.au> Date: 30 Mar 2000 14:27:55 +0200 In-Reply-To: Adrian Chadd's message of "Thu, 30 Mar 2000 19:35:46 +0800" Message-ID: <5l4s9oiqwk.fsf@assaris.sics.se> Lines: 17 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adrian Chadd writes: > I agree that vnode_if.h needs to be in the sys/ tree for this, but I > don't think it needs to be checked into CVS. It means any time > someone modifies vnode_if.src a whole new vnode_if.h could possibly > be generated, causing unnecessary repobloat. Right, but that's the same as with syscall.h et al. > How about having it built as part of populating /usr/include/sys/ ? That would also work. The reason why I didn't do it that way was because there didn't seem to be any simple way of adding that generation of vnode_if.h into src/include/Makefile. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 4:47:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 914AD37BADF; Thu, 30 Mar 2000 04:47:20 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id OAA38551; Thu, 30 Mar 2000 14:47:28 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200003301247.OAA38551@info.iet.unipi.it> Subject: Re: What is the status of the mmap support in the pcm driver? In-Reply-To: <38E340E1.43E443D3@altavista.net> from Maxim Sobolev at "Mar 30, 2000 02:56:17 pm" To: Maxim Sobolev Date: Thu, 30 Mar 2000 14:47:27 +0200 (CEST) Cc: current@FreeBSD.ORG, multimedia@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 [Charset koi8-r unsupported, filtering to ASCII...] > Hi, > > Does anybody can clarify what is current status of the mmap support in the pcm > driver? I'm trying to get sound in the quakeforge working, but only managed to > get famous "dsp_mmap." message in kernel logs instead of sound :(. not present in 3.x, don't know about 4.x/5.x cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 5:51: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 0210437BCFE for ; Thu, 30 Mar 2000 05:50:57 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 11811 invoked from network); 30 Mar 2000 13:50:48 -0000 Received: from acs-63-85-133-249.cvzoom.net (HELO cvzoom.net) (63.85.133.249) by ns.cvzoom.net with SMTP; 30 Mar 2000 13:50:48 -0000 Message-ID: <38E35BAD.B55B0B8@cvzoom.net> Date: Thu, 30 Mar 2000 08:50:37 -0500 From: Donn Miller X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Performance drop in sound (pcm driver or scheduler?) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just rebuilt by kernel this morning at around 2:00 AM from a fresh cvsup. Now, the sound driver doesn't perform as well as it used to. For example, playing audio clips in realplayer sometimes skips or cuts out when I open up windows, etc. My Mar 28 build of the kernel doesn't have this behavior. I have the ESS 1868 ISA sound card. Maybe it was a change in the scheduler that did it? At any rate, I'm noticing a drop in performance when I play mp3's or even low-quality audio clips with RealPlayer. I'm thinking that if the sound driver isn't at fault, then it's gotta be changes in the scheduler that's causing the sound apps to not get the CPU time it used to. Again, I'm comparing kernels that were built Mar 28 and Mar 30, the Mar 30 build having the noticable drop in sound driver quality. Basically, I don't really notice any difference overall in system performance between the two, but the pcm driver doesn't seem to be performing as good as it did as of mar 28 and before. I'm guessing that it's the pcm driver's fault, but I just want to cover all bases since someone did mention the new sched. code. What pieces of both were changed between Mar 28 and Mar 30? - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 7: 2:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 2E80E37B7F3 for ; Thu, 30 Mar 2000 07:02:47 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 23557 invoked from network); 30 Mar 2000 15:02:43 -0000 Received: from acs-63-85-133-249.cvzoom.net (HELO cvzoom.net) (63.85.133.249) by ns.cvzoom.net with SMTP; 30 Mar 2000 15:02:43 -0000 Message-ID: <38E36C88.CC3979D1@cvzoom.net> Date: Thu, 30 Mar 2000 10:02:32 -0500 From: Donn Miller X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Recent changes made to pcm Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, it looks as if some changes were made to pcm. Specifically, it looks as if changes were made to address the problem of RealPlayer not stopping the clip immediately after pressing stop. Before the changes, RealPlayer (all versions) would keep playing the clip ~ 3 secs after pressing stop. Now, it stops playing the clip almost immediately after pressing stop. In the wake of these changes, now RealPlayer's sound gets interrupted very easily after opening/closing windows. Also, the previous pcm changes performed much better under high CPU loads. Now, pcm chokes under CPU loads. I may be wrong, but it looks to me like there's a tradeoff here: if you fix pcm so that RealPlayer stops playing the clip sooner after pressing stop, it performs noticeable worse under moderate to heavy cpu loads. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 7:41: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from hurricane.columbus.rr.com (m5.columbus.rr.com [204.210.252.249]) by hub.freebsd.org (Postfix) with ESMTP id D953637BCAB for ; Thu, 30 Mar 2000 07:40:54 -0800 (PST) (envelope-from caa@columbus.rr.com) Received: from columbus.rr.com ([204.210.243.142]) by hurricane.columbus.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com; Thu, 30 Mar 2000 10:40:58 -0500 Received: (from caa@localhost) by columbus.rr.com (8.9.3/8.9.3) id KAA61016; Thu, 30 Mar 2000 10:40:46 -0500 (EST) (envelope-from caa) Date: Thu, 30 Mar 2000 10:40:45 -0500 From: "Charles Anderson" To: Vladik Cc: current@FreeBSD.ORG Subject: Re: Please test for 8G-OVER-Booting with /boot/loader Message-ID: <20000330104045.A1509@midgard.dhs.org> References: <87n1njbrfj.fsf@nakaji.tutrp.tut.ac.jp> <20000328150723.A28294@midgard.dhs.org> <38E265D3.279D4F0A@bigfoot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38E265D3.279D4F0A@bigfoot.com>; from pvlad@bigfoot.com on Wed, Mar 29, 2000 at 03:21:39PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do you do this everytime or just to get things started? If it's everytime, man that's a pain, if it's just to get things started it's easier than what I did. (but now I get a list of what I want to boot from the NT bootloader, and I just hit the arrow down to FreeBSD and go.) -Charlie On Wed, Mar 29, 2000 at 03:21:39PM -0500, Vladik wrote: > Hello, > I am not sure if this exactly on topic, > but this is how I boot freeBSD partition that is installed > beyond cyl 1024 > > > I use GRUB boot loader that understands LBA (www.gnu.org/grub) > > Once GRUB boots from a floppy, go to GRUB's command prompt and > do the following: > > root (hd0,3,a) # or whatever your FreeBSD root slice is > #after the command above, it mounted the partition > > kernel /kernel -remount > boot > > When kernel boots to the point where it needs to mount a root > partion it will ask you, > in there you type > ufs:/dev/ad0s4a > > > ---- > Vladislav -- Charles Anderson caa@columbus.rr.com No quote, no nothin' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 7:42:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from alpha.nowalls.com (ns.nowalls.com [216.190.228.2]) by hub.freebsd.org (Postfix) with ESMTP id 1870537BD0D for ; Thu, 30 Mar 2000 07:42:47 -0800 (PST) (envelope-from stephen@nowalls.com) Received: from mindy (mindy.nowalls.com [216.190.229.25]) by alpha.nowalls.com (8.9.3/8.9.3) with ESMTP id IAA11061 for ; Thu, 30 Mar 2000 08:36:04 -0700 Message-Id: <4.2.2.20000330083923.00b5b800@mail.nowalls.com> X-Sender: stephen@mail.nowalls.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 30 Mar 2000 08:39:49 -0700 To: freebsd-current@FreeBSD.org From: Stephen Cheung Subject: subscribe Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 8:50: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 80BC837BCA6 for ; Thu, 30 Mar 2000 08:50:00 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA73374; Thu, 30 Mar 2000 08:49:07 -0800 (PST) (envelope-from dillon) Date: Thu, 30 Mar 2000 08:49:07 -0800 (PST) From: Matthew Dillon Message-Id: <200003301649.IAA73374@apollo.backplane.com> To: Brad Knowles Cc: Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests References: <200003300604.WAA68031@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :At 10:04 PM -0800 2000/3/29, Matthew Dillon wrote: : :> So softupdates improves buildworld times by a significant margin. : : Uh, I think we've known this for a while now. ;-) : : Still, I'm looking forward to finding out what the new timings :are for SMP builds with the new code (both with and without :softupdates), and I still can't wait to get this stuff MFC's to :4.0-STABLE. : :====================================================================== :Brad Knowles, || Belgacom Skynet SA/NV 4694.193u 1477.722s 1:10:24.37 146.1% 1364+1646k 10077+4118io 1734pf+0w 5.0 softupdates on 4696.987u 1502.278s 1:10:34.17 146.4% 1359+1641k 10889+4270io 1779pf+0w 5.0 softupdates on 4745.607u 1673.646s 1:29:07.45 120.0% 1323+1599k 8237+251565io 1615pf+0w 4.0 softupdates off 4745.062u 1668.094s 1:28:58.04 120.1% 1323+1601k 8022+251525io 1787pf+0w 4.0 softupdates off 4712.080u 1678.329s 1:16:29.38 139.2% 1330+1609k 11714+130429io 1692pf+0w 4.0 softupdates on 4708.749u 1674.349s 1:16:20.60 139.3% 1331+1608k 11512+130477io 1479pf+0w 4.0 softupdates on 6 minutes 20 seconds (about 7%). I am still getting a major difference in the I/O stats, though it is much less then before. But now I have no clue as to why that last I/O parameter is so different. -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 Mar 30 9: 1:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 5833037B98D; Thu, 30 Mar 2000 09:01:37 -0800 (PST) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb23.imasy.or.jp [202.227.24.151]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id CAA16482; Fri, 31 Mar 2000 02:01:29 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <200003301701.CAA16482@tasogare.imasy.or.jp> To: freebsd-mobile@FreeBSD.org Cc: freebsd-current@FreeBSD.org Subject: HEADS UP: new pccard.conf scheme, please test! 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 Date: Fri, 31 Mar 2000 02:01:25 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 52 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG HI, all. I've just committed new feature for pccardd, but default pccard configuration file is still /etc/pccard.conf.sample because I'd like to see how things go and test them more for about a week. Test version of /etc/defaults/pccard.conf, /etc/pccard.conf are available at http://www.freebsd.org/~iwasaki/pccard/pccard.conf.tar.gz and, patches against the files under src/etc and src/share are available at http://www.freebsd.org/~iwasaki/pccard/pccardd-etc.diff You might need to copy /etc/defaults/pccard.conf to src/etc/defauts/ for make world until src/etc/defauts/pccard.conf is created. Please test them and report your problem to iwasaki@jp.FreeBSD.org if anything wrong. Thanks! > iwasaki 2000/03/30 08:01:39 PST > > Modified files: > usr.sbin/pccard/pccardd cardd.h file.c pccard.conf.5 pccardd.8 > pccardd.c > Log: > - default config file changed from /etc/pccard.conf to > /etc/defaults/pccard.conf in pccardd. But system default pccardd > config file is still /etc/pccard.conf.sample specified in /etc/rc.conf > for the testing this changes. > - improved `include' keyword function for error handling. > - now that resource pool (io, irq, mem) can be overridden. > - pccard config entries is searched following the first match rule if > there are more than two entries which have the same card identifier. > > Note that the /etc/defaults/pccard.conf related files is not committed > at this time, will come a week later. I'll prepare the test version > of /etc/defaults/pccard.conf, /etc/pccard.conf and other files soon. > > Reviewed by: imp and nomads in Japan. > > Revision Changes Path > 1.19 +3 -1 src/usr.sbin/pccard/pccardd/cardd.h > 1.25 +116 -41 src/usr.sbin/pccard/pccardd/file.c > 1.13 +18 -4 src/usr.sbin/pccard/pccardd/pccard.conf.5 > 1.18 +10 -4 src/usr.sbin/pccard/pccardd/pccardd.8 > 1.7 +3 -2 src/usr.sbin/pccard/pccardd/pccardd.c > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 9: 7: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id 9FDFE37BCAC; Thu, 30 Mar 2000 09:07:01 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id MAA18273; Thu, 30 Mar 2000 12:06:49 -0500 (EST) (envelope-from efutch@nyct.net) Date: Thu, 30 Mar 2000 12:06:49 -0500 (EST) From: "Eric D. Futch" To: Bruce Evans Cc: Mike Smith , Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests 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 Oops.. some of us are using i8254 on SMP machines. This motherboard is a Intel PR440FX. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #5: Mon Mar 27 20:39:24 EST 2000 efutch@quake.nyct.net:/usr/src/sys/compile/QUAKE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (198.67-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 134217728 (131072K bytes) avail memory = 126488576 (123524K 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 0xc03c7000. -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Thu, 30 Mar 2000, Bruce Evans wrote: > >Nothing. Accesses to the timecounter struct are already MP safe and fast. >Only the i8254 timecounter hardware currently needs interrupt-disabling, >but it is hopefully never used on SMP machines. > >Bruce > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 9:16: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 13B8737B8F9; Thu, 30 Mar 2000 09:15:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA73702; Thu, 30 Mar 2000 09:15:54 -0800 (PST) (envelope-from dillon) Date: Thu, 30 Mar 2000 09:15:54 -0800 (PST) From: Matthew Dillon Message-Id: <200003301715.JAA73702@apollo.backplane.com> To: Poul-Henning Kamp Cc: Bruce Evans , Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests References: <1274.954416252@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In message , Bruce Ev :ans writes: :>On Wed, 29 Mar 2000, Mike Smith wrote: :> :>> Just following on from this, one thing that I can see immediately being :>> very important to me at least is a spinlock in the timecounter structure. :>> Calcru and various other things call microtime(), and we're going to want :>> to lock out updates and parallel accesses to the timecounter. What :>> should we be using for an interrupt-disabling spinlock? :> :>Nothing. Accesses to the timecounter struct are already MP safe and fast. :>Only the i8254 timecounter hardware currently needs interrupt-disabling, :>but it is hopefully never used on SMP machines. : :Worse. It is used by default on SMP machines which don't sport the :PIIX timecounter. : :-- :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! The general problem with the timecounter is that not only is the hardware indeterminant, but the timecounter structure itself is *NOT* MP safe, at least not by my read of it. It also doesn't appear to be interrupt safe. If a microtime() or getmicrotime() call is interrupted and the interrupting interrupt calls microtime(), it can corrupt the data returned by the first guy and even corrupt the structure. -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 Mar 30 9:36:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (law2-f225.hotmail.com [216.32.181.225]) by hub.freebsd.org (Postfix) with SMTP id 620A237B98D for ; Thu, 30 Mar 2000 09:36:09 -0800 (PST) (envelope-from changtze@hotmail.com) Received: (qmail 79663 invoked by uid 0); 30 Mar 2000 17:36:05 -0000 Message-ID: <20000330173605.79662.qmail@hotmail.com> Received: from 203.106.62.10 by www.hotmail.com with HTTP; Thu, 30 Mar 2000 09:36:05 PST X-Originating-IP: [203.106.62.10] From: "KAMIL MUHD" To: sgk@troutmask.apl.washington.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: Error code 2 Date: Fri, 31 Mar 2000 01:36:05 MYT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG KAMIL MUHD wrote: > Hi everyone... > > I got this error evrytime I try to make world no matter how often I > cvsup'ed. I don't know what it is, what is Error code 2 anyway? Is my cc > version is out-of-date? I'm using the GNU gcc-2.95.1. My box is running on > 4.0-CURRENT. Any idea? Is it because I've cvsuped the wrong file? I cvsuped > the 4.x-secure-stable-supfile and 4.x-stable-supfile. > > cc -O -pipe -I/usr/src/lib/libm/common_source -Dnational In /etc/make.conf, you should comment out WANT_CSRG_LIBM. The default math library is in src/lib/msun. Why the csrg math library is still in the src tree is somewhat of a mystery to me. -- Steve ----------------------------------------------------- Well, thank you Steve, thak you all. Thanks very much, your suggestion really helps me out. Know I know why... :) ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 10: 3:52 2000 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 918A937BE9C; Thu, 30 Mar 2000 10:03:37 -0800 (PST) (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 LAA69350; Thu, 30 Mar 2000 11:03:35 -0700 (MST) (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 LAA25466; Thu, 30 Mar 2000 11:03:08 -0700 (MST) Message-Id: <200003301803.LAA25466@harmony.village.org> To: Matthew Dillon Subject: Re: SMP buildworld times / performance tests Cc: Poul-Henning Kamp , Bruce Evans , Mike Smith , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 30 Mar 2000 09:15:54 PST." <200003301715.JAA73702@apollo.backplane.com> References: <200003301715.JAA73702@apollo.backplane.com> <1274.954416252@critter.freebsd.dk> Date: Thu, 30 Mar 2000 11:03:08 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003301715.JAA73702@apollo.backplane.com> Matthew Dillon writes: : The general problem with the timecounter is that not only is the hardware : indeterminant, but the timecounter structure itself is *NOT* MP safe, : at least not by my read of it. : : It also doesn't appear to be interrupt safe. If a microtime() or : getmicrotime() call is interrupted and the interrupting interrupt calls : microtime(), it can corrupt the data returned by the first guy and : even corrupt the structure. We've hacked the parallel port interrupt to be a fast one on one of our boxes. It is connected to the pps driver which calls getnanotime to timestamp the pps pulse that came in. We've seen, in carefully plotting ntp data, that there are often (1 in a thousand) large dropouts in the times reported. They are in the neighborhood of the clock tick. Since ntp discards the outliers, this was a low priority issue for us given the overall nature of that particular system. At the time I took a look at it, and couldn't see how access to the counter could be mp safe, but didn't have a lot of time to pursue it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 11:16:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mg137-078.ricochet.net [204.179.137.78]) by hub.freebsd.org (Postfix) with ESMTP id 5D1E937BF8D; Thu, 30 Mar 2000 11:15:58 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA00452; Thu, 30 Mar 2000 10:05:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003301805.KAA00452@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: Bruce Evans , Mike Smith , Matthew Dillon , freebsd-current@freebsd.org Subject: Re: SMP buildworld times / performance tests In-reply-to: Your message of "Thu, 30 Mar 2000 13:37:32 +0200." <1274.954416252@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Mar 2000 10:05:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Just following on from this, one thing that I can see immediately being > >> very important to me at least is a spinlock in the timecounter structure. > >> Calcru and various other things call microtime(), and we're going to want > >> to lock out updates and parallel accesses to the timecounter. What > >> should we be using for an interrupt-disabling spinlock? > > > >Nothing. Accesses to the timecounter struct are already MP safe and fast. > >Only the i8254 timecounter hardware currently needs interrupt-disabling, > >but it is hopefully never used on SMP machines. > > Worse. It is used by default on SMP machines which don't sport the > PIIX timecounter. ie. anything using the PIIX3 or older (think 440FX dual P6 systems, etc.) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Thu Mar 30 11:25:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 4076B37BF12; Thu, 30 Mar 2000 11:25:37 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id E4D563E24; Thu, 30 Mar 2000 21:25:35 +0200 (CEST) Date: Thu, 30 Mar 2000 21:25:35 +0200 From: Jesper Skriver To: Mike Smith Cc: freebsd-current@freebsd.org Subject: Re: SMP buildworld times / performance tests Message-ID: <20000330212535.A49637@skriver.dk> References: <1274.954416252@critter.freebsd.dk> <200003301805.KAA00452@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003301805.KAA00452@mass.cdrom.com>; from msmith@freebsd.org on Thu, Mar 30, 2000 at 10:05:26AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 30, 2000 at 10:05:26AM -0800, Mike Smith wrote: > > >> Just following on from this, one thing that I can see immediately being > > >> very important to me at least is a spinlock in the timecounter structure. > > >> Calcru and various other things call microtime(), and we're going to want > > >> to lock out updates and parallel accesses to the timecounter. What > > >> should we be using for an interrupt-disabling spinlock? > > > > > >Nothing. Accesses to the timecounter struct are already MP safe and fast. > > >Only the i8254 timecounter hardware currently needs interrupt-disabling, > > >but it is hopefully never used on SMP machines. > > > > Worse. It is used by default on SMP machines which don't sport the > > PIIX timecounter. > > ie. anything using the PIIX3 or older (think 440FX dual P6 systems, etc.) On the box below, a relative new dual PIII box, with a Intel motherboard, does it use the i8254 or the PIIX timecounter ? Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #0: Mon Mar 27 17:02:42 CEST 2000 root@:/usr/src/sys/compile/REMIE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon (496.66-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Features=0x387fbff real memory = 268369920 (262080K bytes) config> q avail memory = 257515520 (251480K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02c5000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02c509c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 [snip] isab0: at device 18.0 on pci0 isa0: on isab0 pci0: at 18.1 pci0: at 18.2 irq 10 Timecounter "PIIX" frequency 3579545 Hz /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 11:30:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mg137-078.ricochet.net [204.179.137.78]) by hub.freebsd.org (Postfix) with ESMTP id F2B6537BF1B for ; Thu, 30 Mar 2000 11:29:59 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA00453; Thu, 30 Mar 2000 11:33:47 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003301933.LAA00453@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jesper Skriver Cc: freebsd-current@freebsd.org Subject: Re: SMP buildworld times / performance tests In-reply-to: Your message of "Thu, 30 Mar 2000 21:25:35 +0200." <20000330212535.A49637@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Mar 2000 11:33:43 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > >Only the i8254 timecounter hardware currently needs interrupt-disabling, > > > >but it is hopefully never used on SMP machines. > > > > > > Worse. It is used by default on SMP machines which don't sport the > > > PIIX timecounter. > > > > ie. anything using the PIIX3 or older (think 440FX dual P6 systems, etc.) > > On the box below, a relative new dual PIII box, with a Intel > motherboard, does it use the i8254 or the PIIX timecounter ? sysctl kern.timecounter.hardware (should have been hw.timecounter.hardware, but whatever) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Thu Mar 30 12: 9:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 191BC37BD4C for ; Thu, 30 Mar 2000 12:09:27 -0800 (PST) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id MAA19689 for ; Thu, 30 Mar 2000 12:09:26 -0800 (PST) Date: Thu, 30 Mar 2000 12:09:25 -0800 (PST) From: Julian Elischer To: current@freebsd.org Subject: My KDE she's broke.. 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 Sometime recently (in the last month or so a lot of my kde stuff stopped working. they all complain about: jules# kpanel /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol "_vt$9exception" jules# Not being a library specialist.. does anyone know offhand who's got out of step with who? and what I should do to fix it? I reinstalled the kde-base, and that didn't seem to fix it. I did a make world, so THEORETICALLY all teh system libraries should be in sync .. right? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 12:15:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mg137-078.ricochet.net [204.179.137.78]) by hub.freebsd.org (Postfix) with ESMTP id 09C0937BE6F for ; Thu, 30 Mar 2000 12:15:44 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA02871; Thu, 30 Mar 2000 12:19:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003302019.MAA02871@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Julian Elischer Cc: current@freebsd.org Subject: Re: My KDE she's broke.. In-reply-to: Your message of "Thu, 30 Mar 2000 12:09:25 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Mar 2000 12:19:39 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sometime recently (in the last month or so a lot of my kde stuff stopped > working. > > they all complain about: > jules# kpanel > /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol > "_vt$9exception" > jules# You should be reading -current; this changed before the 4.0 release. You have to rebuild all your C++ binaries. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Thu Mar 30 12:28:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from yellowdog.com (yellowdog.com [161.58.237.126]) by hub.freebsd.org (Postfix) with ESMTP id E6FCB37BF12 for ; Thu, 30 Mar 2000 12:28:41 -0800 (PST) (envelope-from yellow2@yellowdog.com) Received: (yellow2@localhost) by yellowdog.com (8.8.8) id PAA06202; Thu, 30 Mar 2000 15:28:34 -0500 (EST) Date: Thu, 30 Mar 2000 15:28:34 -0500 (EST) From: yellow2@yellowdog.com (Yellow Dog Communications Inc) Message-Id: <200003302028.PAA06202@yellowdog.com> To: Some perl administrator Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Subject: Mail::Internet test subject This is a test message that was sent by the test suite of Mail::Internet. Testing. one From foo four >From bar seven To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 13:21:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from hydrant.intranova.net (hydrant.ncw.qc.ca [209.201.95.10]) by hub.freebsd.org (Postfix) with SMTP id 6FB2637B8D9 for ; Thu, 30 Mar 2000 13:21:40 -0800 (PST) (envelope-from oogali@intranova.net) Received: (qmail 50430 invoked from network); 30 Mar 2000 19:38:20 -0000 Received: from localhost.abuselabs.com (HELO localhost) (missnglnk@127.0.0.1) by localhost.abuselabs.com with SMTP; 30 Mar 2000 19:38:20 -0000 Date: Thu, 30 Mar 2000 14:38:20 -0500 (EST) From: Omachonu Ogali To: freebsd-current@freebsd.org Cc: freebsd-small@freebsd.org Subject: Traceroute 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 IPSEC is hard-defined into the Makefile...not good, especially for PicoBSD. -- snip -- --- /usr/src/usr.sbin/traceroute/Makefile.orig Thu Mar 30 14:16:52 2000 +++ /usr/src/usr.sbin/traceroute/Makefile Thu Mar 30 14:23:28 2000 @@ -5,4 +5,11 @@ BINMODE=4555 + +.ifndef (NOIPSEC) CFLAGS+=-DHAVE_SYS_SELECT_H=1 -DHAVE_SETLINEBUF=1 -DHAVE_RAW_OPTIONS=1 \ -DSTDC_HEADERS=1 -DIPSEC +.else +CFLAGS+=-DHAVE_SYS_SELECT_H=1 -DHAVE_SETLINEBUF=1 -DHAVE_RAW_OPTIONS=1 \ + -DSTDC_HEADERS=1 +.endif + # RTT Jitter on the internet these days means printing 3 decimal places on @@ -14,4 +21,7 @@ CLEANFILES+= version.c + +.ifndef (NOIPSEC) DPADD= ${LIBIPSEC} LDADD= -lipsec +.endif -- snip -- -- +-------------------------------------------------------------------------+ | Omachonu Ogali oogali@intranova.net | | Intranova Networking Group http://tribune.intranova.net | | PGP Key ID: 0xBFE60839 | | PGP Fingerprint: C8 51 14 FD 2A 87 53 D1 E3 AA 12 12 01 93 BD 34 | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 14:28:28 2000 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 7ECD737B93B for ; Thu, 30 Mar 2000 14:28:24 -0800 (PST) (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 PAA70531; Thu, 30 Mar 2000 15:28:22 -0700 (MST) (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 PAA27394; Thu, 30 Mar 2000 15:27:56 -0700 (MST) Message-Id: <200003302227.PAA27394@harmony.village.org> To: Julian Elischer Subject: Re: My KDE she's broke.. Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 30 Mar 2000 12:09:25 PST." References: Date: Thu, 30 Mar 2000 15:27:56 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Julian Elischer writes: : I did a make world, so THEORETICALLY all teh system libraries should be in : sync .. right? Did you also rebuild kde after doing the make world? If not, you missed one of the entries in UPDATING talking about needing to recompile all C++ applications. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 14:31: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (Postfix) with ESMTP id DA4C637B9CD for ; Thu, 30 Mar 2000 14:30:59 -0800 (PST) (envelope-from Tomi.Vainio@finland.sun.com) Received: from sunfin.Finland.Sun.COM ([129.159.101.10]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA20191 for ; Thu, 30 Mar 2000 14:30:57 -0800 (PST) Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87]) by sunfin.Finland.Sun.COM (8.8.8+Sun/8.8.8/ENSMAIL,v1.7) with ESMTP id BAA04533 for ; Fri, 31 Mar 2000 01:30:54 +0300 (EET DST) Received: (from tomppa@localhost) by ultrahot.Finland.Sun.COM (8.9.3/8.9.3) id BAA06902; Fri, 31 Mar 2000 01:30:52 +0300 (EET DST) From: Tomi Vainio - Sun Finland - MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14563.54684.729495.581128@ultrahot.Finland.Sun.COM> Date: Fri, 31 Mar 2000 01:30:52 +0300 (EET DST) To: freebsd-current@freebsd.org Subject: Voxware audio is too fast X-Mailer: VM 6.75 under 21.1 (patch 6) "Big Bend" XEmacs Lucid Reply-To: Tomi.Vainio@Sun.COM Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm still using old voxware driver on 5.0 current system because it is only way to get support for my Pro Audio Spectrum card. But there is one problem on playback. It's 5% too fast and it sounds annoying. If I play these same mp3 files through pcm/sbc driver everything is ok. It's also easy to measure this problem just using time command. pas0 at port 0x388 irq 10 drq 5 on isa0 snd0: pas0: driver is using old-style compatability shims mss_detect, busy still set (0xff) sbc0: at port 0x220-0x22f irq 7 drq 1 on isa0 pcm1: on sbc0 pcm: setmap 1a000, 2000; 0xc5cfa000 -> 1a000 pcm: setmap 1c000, 2000; 0xc5cfc000 -> 1c000 Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: Tomi.Vainio@Sun.COM +358 9 52556252 fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 15:10:51 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id BC05137B88B; Thu, 30 Mar 2000 15:10:48 -0800 (PST) From: "Jonathan M. Bresler" To: yellow2@yellowdog.com Cc: current@freebsd.org In-reply-to: <200003302028.PAA06202@yellowdog.com> (yellow2@yellowdog.com) Message-Id: <20000330231048.BC05137B88B@hub.freebsd.org> Date: Thu, 30 Mar 2000 15:10:48 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NEVER send test messages to any FreeBSD mailing list but freebsd-test. doing so can result in you being filtered from all the freebsd mailing lists. jmb > From: yellow2@yellowdog.com (Yellow Dog Communications Inc) > Sender: owner-freebsd-current@FreeBSD.ORG > X-Loop: FreeBSD.ORG > Precedence: bulk > > Subject: Mail::Internet test subject > > > This is a test message that was sent by the test suite of > Mail::Internet. > > Testing. > > one > > >From foo > four > > >From bar > seven > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 15:45:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 2C28437B9CB for ; Thu, 30 Mar 2000 15:45:25 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id RAA07247; Thu, 30 Mar 2000 17:44:53 -0600 (CST) Date: Thu, 30 Mar 2000 17:44:53 -0600 From: "Matthew D. Fuller" To: Matthew Dillon Cc: Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests Message-ID: <20000330174453.D10480@futuresouth.com> References: <200003300604.WAA68031@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <200003300604.WAA68031@apollo.backplane.com> X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 29, 2000 at 10:04:17PM -0800, a little birdie told me that Matthew Dillon remarked > > Ha! I found it. Kirk gets the credit --- softupdates was turned on > in one of the machine's /usr/obj's and off on the other machine's. > > So softupdates improves buildworld times by a significant margin. I've > turned softupdates on on both machines and am rerunning the test. I > expect I will see an improvement closer to what Bob Bishop saw when > he ran the test (7% or so) rather then 20+%. Does softupdates provide faster performance than async/noatime? I keep /usr/src and /usr/obj as such, would it be faster with softupdates? And if so, why? -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 16: 0:52 2000 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 B994C37B946 for ; Thu, 30 Mar 2000 16:00:48 -0800 (PST) (envelope-from obrien@NUXI.ucdavis.edu) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id QAA18124; Thu, 30 Mar 2000 16:00:47 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id QAA57666; Thu, 30 Mar 2000 16:00:43 -0800 (PST) (envelope-from obrien) Date: Thu, 30 Mar 2000 16:00:43 -0800 From: "David O'Brien" To: "Matthew D. Fuller" Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests Message-ID: <20000330160043.A57508@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200003300604.WAA68031@apollo.backplane.com> <20000330174453.D10480@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000330174453.D10480@futuresouth.com>; from fullermd@futuresouth.com on Thu, Mar 30, 2000 at 05:44:53PM -0600 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 Thu, Mar 30, 2000 at 05:44:53PM -0600, Matthew D. Fuller wrote: > Does softupdates provide faster performance than async/noatime? In general it depends. Softupdates is faster on creating a file and then deleteing it before both hit the disk. Softupdates nulifies out the creation. Async would write the file to disk just to turn around and delete it. For somethings mounting `async' is faster. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 16: 4:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id A6F1F37B92F; Thu, 30 Mar 2000 16:04:06 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id SAA09112; Thu, 30 Mar 2000 18:04:02 -0600 (CST) Date: Thu, 30 Mar 2000 18:04:02 -0600 From: "Matthew D. Fuller" To: "David O'Brien" Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests Message-ID: <20000330180402.E10480@futuresouth.com> References: <200003300604.WAA68031@apollo.backplane.com> <20000330174453.D10480@futuresouth.com> <20000330160043.A57508@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <20000330160043.A57508@dragon.nuxi.com> X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 30, 2000 at 04:00:43PM -0800, a little birdie told me that David O'Brien remarked > On Thu, Mar 30, 2000 at 05:44:53PM -0600, Matthew D. Fuller wrote: > > Does softupdates provide faster performance than async/noatime? > > In general it depends. Softupdates is faster on creating a file and then > deleteing it before both hit the disk. Softupdates nulifies out the > creation. Async would write the file to disk just to turn around and > delete it. > > For somethings mounting `async' is faster. The question at task is, is buildworld one of them? I don't think that situation comes up a lot in buildworld, but I'm not exactly an authority on it... -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 16:14: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.hellasnet.gr (mail.hellasnet.gr [212.54.192.3]) by hub.freebsd.org (Postfix) with ESMTP id 8FDF137B773 for ; Thu, 30 Mar 2000 16:13:48 -0800 (PST) (envelope-from keramida@ceid.upatras.gr) Received: from hades.hell.gr (ppp3.patr.hellasnet.gr [212.54.197.18]) by mail.hellasnet.gr (8.9.1/8.9.1) with ESMTP id CAA08446 for ; Fri, 31 Mar 2000 02:12:49 +0200 (GMT) Received: (from charon@localhost) by hades.hell.gr (8.9.3/8.9.3) id DAA05396 for current@freebsd.org; Fri, 31 Mar 2000 03:15:03 +0300 (EEST) (envelope-from charon) Date: Fri, 31 Mar 2000 03:15:03 +0300 From: Giorgos Keramidas To: current@freebsd.org Subject: pcvt console driver? Message-ID: <20000331031503.A5362@hades.hell.gr> Reply-To: keramida@ceid.upatras.gr Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-PGP-Fingerprint: 62 45 D1 C9 26 F9 95 06 D6 21 2A C8 8C 16 C0 8E Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsup'ed and compiled my kernel with the options shown below in my config file. device isa0 device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? # The pcvt console driver (vt220 compatible). device vt0 at isa? options XSERVER # support for running an X server on vt options FAT_CURSOR # start with block cursor # PCVT options documented in pcvt(4). options PCVT_CTRL_ALT_DEL options PCVT_FREEBSD=211 options PCVT_META_ESC options PCVT_NSCREENS=5 options PCVT_PRETTYSCRNS options PCVT_SCREENSAVER I wanted to give a test to pcvt driver, just for fun (and for profit, if it seemed better than syscons). Is pcvt working, at all? Or I should avoid using it? << This is with revision 1.64 of /sys/i386/isa/pcvt/pcvt_drv.c >> cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes \ -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual \ -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. \ -I../../../include -D_KERNEL -include opt_global.h -elf \ -mpreferred-stack-boundary=2 ../../i386/isa/pcvt/pcvt_drv.c ../../i386/isa/pcvt/pcvt_drv.c:108: warning: `struct isa_device' declared inside parameter list ../../i386/isa/pcvt/pcvt_drv.c:108: warning: its scope is only this definition or declaration, which is probably not what you want. ../../i386/isa/pcvt/pcvt_drv.c:109: warning: `struct isa_device' declared inside parameter list ../../i386/isa/pcvt/pcvt_drv.c:111: variable `vtdriver' has initializer but incomplete type ../../i386/isa/pcvt/pcvt_drv.c:112: warning: excess elements in struct initializer ../../i386/isa/pcvt/pcvt_drv.c:112: warning: (near initialization for `vtdriver') ../../i386/isa/pcvt/pcvt_drv.c:112: warning: excess elements in struct initializer ../../i386/isa/pcvt/pcvt_drv.c:112: warning: (near initialization for `vtdriver') ../../i386/isa/pcvt/pcvt_drv.c:112: warning: excess elements in struct initializer ../../i386/isa/pcvt/pcvt_drv.c:112: warning: (near initialization for `vtdriver') ../../i386/isa/pcvt/pcvt_drv.c:112: warning: excess elements in struct initializer ../../i386/isa/pcvt/pcvt_drv.c:112: warning: (near initialization for `vtdriver') ../../i386/isa/pcvt/pcvt_drv.c:119: warning: `struct isa_device' declared inside parameter list ../../i386/isa/pcvt/pcvt_drv.c:120: conflicting types for `pcprobe' ../../i386/isa/pcvt/pcvt_drv.c:108: previous declaration of `pcprobe' ../../i386/isa/pcvt/pcvt_drv.c: In function `pcprobe': ../../i386/isa/pcvt/pcvt_drv.c:127: dereferencing pointer to incomplete type ../../i386/isa/pcvt/pcvt_drv.c: At top level: ../../i386/isa/pcvt/pcvt_drv.c:142: warning: `struct isa_device' declared inside parameter list ../../i386/isa/pcvt/pcvt_drv.c:143: conflicting types for `pcattach' ../../i386/isa/pcvt/pcvt_drv.c:109: previous declaration of `pcattach' ../../i386/isa/pcvt/pcvt_drv.c: In function `pcattach': ../../i386/isa/pcvt/pcvt_drv.c:149: dereferencing pointer to incomplete type ../../i386/isa/pcvt/pcvt_drv.c:151: dereferencing pointer to incomplete type ../../i386/isa/pcvt/pcvt_drv.c:214: dereferencing pointer to incomplete type *** Error code 1 - Giorgos Keramidas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 16:27:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 657A337B92F; Thu, 30 Mar 2000 16:27:57 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA96976; Thu, 30 Mar 2000 16:29:09 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: fenner@freebsd.org Cc: current@freebsd.org Subject: So, AGAIN, why was tcpdump moved? Date: Thu, 30 Mar 2000 16:29:09 -0800 Message-ID: <96973.954462549@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You moved tcpdump into the crypto distribution with revision 1.25 of its Makefile. I am still scratching my head and trying to figure out why, however, since most people expect tcpdump to be in the bin distribution where it's always been. Did you have some really good reason for this which we're just missing here? Thanks! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 16:40:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id 6D50237B520 for ; Thu, 30 Mar 2000 16:40:43 -0800 (PST) (envelope-from carl@xena.aipo.gov.au) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id KAA53897; Fri, 31 Mar 2000 10:40:30 +1000 (EST) (envelope-from carl@xena.aipo.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma053886; Fri, 31 Mar 00 10:40:13 +1000 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.9.3/8.9.3) with ESMTP id KAA07995; Fri, 31 Mar 2000 10:41:47 +1000 (EST) (envelope-from carl@xena.aipo.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Fri, 31 Mar 2000 10:41:47 +1000 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: Brad Knowles Cc: mjacob@feral.com, current@FreeBSD.ORG Subject: Re: Dual Pathing to SCSI/FC devices. 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, 29 Mar 2000, Brad Knowles wrote: > At 4:28 PM -0800 2000/3/28, Matthew Jacob wrote: > > Yes, we very much has considered this. What's your issue about this, per se? > Myself, I just need to be able to tell the system that SCSI ID x > LUN y is actually the same logical device as SCSI ID v LUN w, but > that one is preferred and the other is backup, and have FreeBSD deal > with doing the re-targeting in the CAM SCSI driver. heh, the buzzword for this is "Dynamic Failover". :) In management circles where the current focus is on 24x7, this is seen as a distinct advantage. > The end result should be that nothing above the CAM SCSI driver > should know that a switch has occurred -- especially not programs > Same deal with fibrechannel as SCSI. > Does that about sum it up? Yes. That was pretty much what I was thinking. "Dual Pathing" the buzzword for using both paths to the device would also be desirable, but then you get into things like wanting to optimise data paths depending on how busy each path is. > Oh, and Carl -- I don't suppose you're looking at Hitachi DF400 > (sometimes rebadged as Comparex D1400) units, are you? If so, I'd No, sorry. I can't actually say what box we're buying yet since we haven't signed the contract. :( Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 16:59:13 2000 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 81C9437C2C6; Thu, 30 Mar 2000 16:58:55 -0800 (PST) (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 RAA71038; Thu, 30 Mar 2000 17:58:49 -0700 (MST) (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 RAA30753; Thu, 30 Mar 2000 17:58:22 -0700 (MST) Message-Id: <200003310058.RAA30753@harmony.village.org> To: "Matthew D. Fuller" Subject: Re: SMP buildworld times / performance tests Cc: "David O'Brien" , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 30 Mar 2000 18:04:02 CST." <20000330180402.E10480@futuresouth.com> References: <20000330180402.E10480@futuresouth.com> <200003300604.WAA68031@apollo.backplane.com> <20000330174453.D10480@futuresouth.com> <20000330160043.A57508@dragon.nuxi.com> Date: Thu, 30 Mar 2000 17:58:22 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000330180402.E10480@futuresouth.com> "Matthew D. Fuller" writes: : The question at task is, is buildworld one of them? I don't think that : situation comes up a lot in buildworld, but I'm not exactly an authority : on it... About 6 months ago, softupdates made things about 5% faster than async for makeworld on my PPro 200 + 196M of memory. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 16:59:53 2000 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 49D1837C2EB for ; Thu, 30 Mar 2000 16:59:48 -0800 (PST) (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 RAA71044; Thu, 30 Mar 2000 17:59:45 -0700 (MST) (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 RAA30766; Thu, 30 Mar 2000 17:59:18 -0700 (MST) Message-Id: <200003310059.RAA30766@harmony.village.org> To: keramida@ceid.upatras.gr Subject: Re: pcvt console driver? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 31 Mar 2000 03:15:03 +0300." <20000331031503.A5362@hades.hell.gr> References: <20000331031503.A5362@hades.hell.gr> Date: Thu, 30 Mar 2000 17:59:18 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG See UPDATING: 20000319: The ISA and PCI compatability shims have been connected to the options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old style PCI or ISA drivers (i.e. tx, voxware, etc.) you must include the appropriate option in your kernel config. Drivers using the shims should be updated or they won't ship with 5.0-RELEASE, targeted for 2001. Work is underway to fix pcvt. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 17:38:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id B265E37C246 for ; Thu, 30 Mar 2000 17:38:10 -0800 (PST) (envelope-from rb@gid.co.uk) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id CAA69434; Fri, 31 Mar 2000 02:37:20 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id CAA25227; Fri, 31 Mar 2000 02:14:18 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <200003301649.IAA73374@apollo.backplane.com> References: <200003300604.WAA68031@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 31 Mar 2000 02:14:17 +0100 To: Matthew Dillon From: Bob Bishop Subject: Re: SMP buildworld times / performance tests Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >:At 10:04 PM -0800 2000/3/29, Matthew Dillon wrote: >[...] > 6 minutes 20 seconds (about 7%). I'm seeing the same order of improvement still. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 17:43:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 6B13837C2D0; Thu, 30 Mar 2000 17:43:13 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA71466; Thu, 30 Mar 2000 17:43:07 -0800 (PST) (envelope-from dillon) Date: Thu, 30 Mar 2000 17:43:07 -0800 (PST) From: Matthew Dillon Message-Id: <200003310143.RAA71466@apollo.backplane.com> To: Warner Losh Cc: "David O'Brien" , freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests References: <20000330180402.E10480@futuresouth.com> <200003300604.WAA68031@apollo.backplane.com> <20000330174453.D10480@futuresouth.com> <20000330160043.A57508@dragon.nuxi.com> <200003310058.RAA30753@harmony.village.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In message <20000330180402.E10480@futuresouth.com> "Matthew D. Fuller" writes: :: The question at task is, is buildworld one of them? I don't think that :: situation comes up a lot in buildworld, but I'm not exactly an authority :: on it... : :About 6 months ago, softupdates made things about 5% faster than async :for makeworld on my PPro 200 + 196M of memory. : :Warner Softupdates is basically going to beat async on just about everything, and beat it *badly* for a bunch of things like /tmp operation. There are a few minor issues with the write-behind code (e.g. that thread on DBM ops and certain contrived random I/O tests being slow), which async is much faster on, but that's just a quirk in the clustering code. I'm working on a patch set which extends the sequential read heuristic to also handle writes. The patch is currently under review and can hopefully be committed to 4.x and 5.x soon (or something like it). Async should not be used unless you really like restoring crashed filesystems from tape :-). Oh, and perhaps when one is doing an initial OS install from CDRom :-). Async itself will not cause a crash, but if your machine crashes in the middle of a bunch of async writes you might end up with an unrecoverable filesystem. Also, async can be awefully hard on the VM system if you are doing a lot of writing - there's a reason why we have write-behind code, even if it has a few bogus cases. -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 Mar 30 17:49:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 010BF37C3F6 for ; Thu, 30 Mar 2000 17:49:39 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA71632; Thu, 30 Mar 2000 17:49:32 -0800 (PST) (envelope-from dillon) Date: Thu, 30 Mar 2000 17:49:32 -0800 (PST) From: Matthew Dillon Message-Id: <200003310149.RAA71632@apollo.backplane.com> To: Bob Bishop Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests References: <200003300604.WAA68031@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :>:At 10:04 PM -0800 2000/3/29, Matthew Dillon wrote: :>[...] :> 6 minutes 20 seconds (about 7%). : :I'm seeing the same order of improvement still. : :-- :Bob Bishop (0118) 977 4017 international code +44 118 :rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK Ok, excellent. I figured out why my I/O rate was still high -- I also hadn't turned on softupdates for /var/tmp, but it didn't make much of a difference since I use -pipe in my compiler options so I am still hanging on around 5-7% too. That's still significant, but not as fun a number as the first one :-). I am coordinating one more patch set with Mike that makes sigprocmask and the core copyout function MP safe (so both copyin and copyout are MP safe). Copyout is basically MP safe already, sigprocmask needed only minor adjustments. Then I'm going to turn the code loose in 5.0 and, in a week or two, backport it to 4.0. Then it will be up to the rest of the community to push the MP lock further, I don't have as much time on my hands as I used to :-). -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 Mar 30 19:58: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtprelay3.adelphia.net (smtprelay3.adelphia.net [64.8.25.8]) by hub.freebsd.org (Postfix) with ESMTP id 8940637C33D for ; Thu, 30 Mar 2000 19:57:56 -0800 (PST) (envelope-from pvlad@bigfoot.com) Received: from bigfoot.com ([24.48.148.111]) by smtprelay3.adelphia.net (Netscape Messaging Server 4.05) with ESMTP id FS9PNF00.2BY; Thu, 30 Mar 2000 22:57:15 -0500 Message-ID: <38E3DC98.3793ADDA@bigfoot.com> Date: Thu, 30 Mar 2000 18:00:40 -0500 From: Vladik X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: en MIME-Version: 1.0 To: Charles Anderson Cc: current@FreeBSD.ORG Subject: Re: Please test for 8G-OVER-Booting with /boot/loader References: <87n1njbrfj.fsf@nakaji.tutrp.tut.ac.jp> <20000328150723.A28294@midgard.dhs.org> <38E265D3.279D4F0A@bigfoot.com> <20000330104045.A1509@midgard.dhs.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, for now I am doing this every time (but I also do not reboot too often). GRUB has a curses-like based menu thing where you can specify what to boot and how. You have to set the config file during the compilation. And then compile, and then build the floppy with that or install on to the MBR. And I have not done that yet. -- Vladislav Charles Anderson wrote: > > Do you do this everytime or just to get things started? > > If it's everytime, man that's a pain, if it's just to get things > started it's easier than what I did. (but now I get a list of what I > want to boot from the NT bootloader, and I just hit the arrow down to > FreeBSD and go.) > > -Charlie > On Wed, Mar 29, 2000 at 03:21:39PM -0500, Vladik wrote: > > Hello, > > I am not sure if this exactly on topic, > > but this is how I boot freeBSD partition that is installed > > beyond cyl 1024 > > > > > > I use GRUB boot loader that understands LBA (www.gnu.org/grub) > > > > Once GRUB boots from a floppy, go to GRUB's command prompt and > > do the following: > > > > root (hd0,3,a) # or whatever your FreeBSD root slice is > > #after the command above, it mounted the partition > > > > kernel /kernel -remount > > boot > > > > When kernel boots to the point where it needs to mount a root > > partion it will ask you, > > in there you type > > ufs:/dev/ad0s4a > > > > > > ---- > > Vladislav > > -- > Charles Anderson caa@columbus.rr.com > > No quote, no nothin' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 20:52:38 2000 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 88FFC37B8FD; Thu, 30 Mar 2000 20:52:33 -0800 (PST) (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 VAA71799; Thu, 30 Mar 2000 21:52:22 -0700 (MST) (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 VAA31984; Thu, 30 Mar 2000 21:51:55 -0700 (MST) Message-Id: <200003310451.VAA31984@harmony.village.org> To: Matthew Dillon Subject: Re: SMP buildworld times / performance tests Cc: "David O'Brien" , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 30 Mar 2000 17:43:07 PST." <200003310143.RAA71466@apollo.backplane.com> References: <200003310143.RAA71466@apollo.backplane.com> <20000330180402.E10480@futuresouth.com> <200003300604.WAA68031@apollo.backplane.com> <20000330174453.D10480@futuresouth.com> <20000330160043.A57508@dragon.nuxi.com> <200003310058.RAA30753@harmony.village.org> Date: Thu, 30 Mar 2000 21:51:55 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003310143.RAA71466@apollo.backplane.com> Matthew Dillon writes: : Async should not be used unless you really like restoring crashed : filesystems from tape :-). Oh, and perhaps when one is doing an : initial OS install from CDRom :-). Async itself will not cause a crash, : but if your machine crashes in the middle of a bunch of async writes : you might end up with an unrecoverable filesystem. Sure makes those restores from backup tapes run fast, however :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 21:23: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from fbsd.ods.org (fbsd.ods.org [63.236.135.3]) by hub.freebsd.org (Postfix) with SMTP id 8E45337B7D4 for ; Thu, 30 Mar 2000 21:23:05 -0800 (PST) (envelope-from geniusj@ods.org) Received: (qmail 21255 invoked by uid 1000); 31 Mar 2000 05:23:04 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 31 Mar 2000 05:23:04 -0000 Date: Fri, 31 Mar 2000 00:23:04 -0500 (EST) From: Systems Administrator To: current@freebsd.org Subject: NFS/Vinum problems 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 -2, exclusive lock holder 5 unlocking Syncing disks... Timedout SCB handled by another timeout Timedout handled by another timeout That is what I get when doing a 'du -k' on an NFS mount from a remote machine.. THe machine I am speaking of is the actual nfs server, i'm using freebsd's default nfsd/mountd flags as specified by rc.conf.. However, when I do lets say, a du -k on the mounted volume, I get that panic.. If this is a known bug or if anyone knows how to fix this, get back to me asap.. Thanks in advance, Jason DiCioccio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 21:41:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 7454437C3B4 for ; Thu, 30 Mar 2000 21:41:08 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: from mojave.worldwide.lemis.com (linuxcare.canberra.net.au [203.29.91.49]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id PAA13072; Fri, 31 Mar 2000 15:09:15 +0930 (CST) (envelope-from grog@mojave.worldwide.lemis.com) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id PAA08006; Fri, 31 Mar 2000 15:39:39 +1000 (EST) (envelope-from grog) Date: Fri, 31 Mar 2000 15:39:39 +1000 From: Greg Lehey To: Systems Administrator Cc: current@FreeBSD.ORG Subject: Re: NFS/Vinum problems Message-ID: <20000331153939.O6764@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from geniusj@ods.org on Fri, Mar 31, 2000 at 12:23:04AM -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 Friday, 31 March 2000 at 0:23:04 -0500, Systems Administrator wrote: > > panic: lockmgr: pid -2, exclusive lock holder 5 unlocking > > Syncing disks... Timedout SCB handled by another timeout > Timedout handled by another timeout > > That is what I get when doing a 'du -k' on an NFS mount from a remote > machine.. THe machine I am speaking of is the actual nfs server, i'm using > freebsd's default nfsd/mountd flags as specified by rc.conf.. However, > when I do lets say, a du -k on the mounted volume, I get that panic.. If > this is a known bug or if anyone knows how to fix this, get back to me > asap.. Yes, I've seen something like this. My best guess is that there's a problem in the error recovery code in CAM, but that's just a guess. If you want to help, give us more information, at least what I'm asking for in http://www.lemis.com/vinum/how-to-debug.html. In addition, the way you're using NFS would be very helpful. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 21:53:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from barmetta.barmetta.com (cm-24-142-60-178.cableco-op.ispchannel.com [24.142.60.178]) by hub.freebsd.org (Postfix) with ESMTP id 5EC5F37B901 for ; Thu, 30 Mar 2000 21:53:51 -0800 (PST) (envelope-from bryan@barmetta.barmetta.com) Received: (from bryan@localhost) by barmetta.barmetta.com (8.9.3/8.9.3) id VAA18212; Thu, 30 Mar 2000 21:53:14 -0800 (PST) (envelope-from bryan) Date: Thu, 30 Mar 2000 21:53:14 -0800 From: "bryan d. o'connor" To: Stephen Hocking-Senior Programmer PGS SPS Perth Cc: current@FreeBSD.ORG Subject: Re: Updating examples /usr/share/examples/ld Message-ID: <20000330215314.C2250@barmetta.com> References: <200003260646.OAA15530@ariadne.prth.tensor.pgs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003260646.OAA15530@ariadne.prth.tensor.pgs.com>; from shocking@prth.pgs.com on Sun, Mar 26, 2000 at 02:46:10PM +0800 X-X: super karate monkey death car Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | Can someone please update the examples in /usr/share/examples/kld? | | It's a bit confusing when it doesn't even compile. i just submitted a patch to get the kld/cdev module to compile (and work too ;). i tested this on a -stable box.. but it should still work for -current. i used the vn device as an example since i'm still learning how KLDs work. see patch below or at: http://www.barmetta.com/freebsd/examples-kld-cdev.patch ...bryan -- bryan@barmetta.com -----8<----- diff -rc cdev-old/module/cdevmod.c cdev/module/cdevmod.c *** cdev-old/module/cdevmod.c Thu Mar 30 21:19:48 2000 --- cdev/module/cdevmod.c Thu Mar 30 21:17:15 2000 *************** *** 81,99 **** /* read */ noread, /* write */ nowrite, /* ioctl */ mydev_ioctl, - /* stop */ nostop, - /* reset */ noreset, - /* devtotty */ nodevtotty, /* poll */ nopoll, /* mmap */ nommap, /* strategy */ nostrategy, /* name */ "cdev", - /* parms */ noparms, /* maj */ CDEV_MAJOR, /* dump */ nodump, /* psize */ nopsize, /* flags */ D_TTY, - /* maxio */ 0, /* bmaj */ -1 }; --- 81,94 ---- *************** *** 109,115 **** */ static int ! cdev_load(module_t mod, int cmd, void *arg) { int err = 0; --- 104,110 ---- */ static int ! cdev_modevent(module_t mod, int cmd, void *arg) { int err = 0; *************** *** 117,122 **** --- 112,119 ---- case MOD_LOAD: /* Do any initialization that you should do with the kernel */ + cdevsw_add(&my_devsw); + make_dev(&my_devsw, 0, UID_ROOT, GID_OPERATOR, 0644, "%s", "cdev"); /* if we make it to here, print copyright on console*/ printf("\nSample Loaded kld character device driver\n"); *************** *** 126,135 **** break; /* Success*/ case MOD_UNLOAD: printf("Unloaded kld character device driver\n"); break; /* Success*/ ! default: /* we only understand load/unload*/ err = EINVAL; break; } --- 123,136 ---- break; /* Success*/ case MOD_UNLOAD: + /* fall through */ + case MOD_SHUTDOWN: + cdevsw_remove(&my_devsw); + printf("Unloaded kld character device driver\n"); break; /* Success*/ ! default: err = EINVAL; break; } *************** *** 139,142 **** /* Now declare the module to the system */ ! DEV_MODULE(cdev, CDEV_MAJOR, -1, my_devsw, cdev_load, 0); --- 140,143 ---- /* Now declare the module to the system */ ! DEV_MODULE(cdev, cdev_modevent, NULL); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 22:10:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from volatile.by-tor.tacorp.net (ci391991-a.grnvle1.sc.home.com [24.9.31.75]) by hub.freebsd.org (Postfix) with ESMTP id 3D63037B901 for ; Thu, 30 Mar 2000 22:10:46 -0800 (PST) (envelope-from by-tor@volatile.by-tor.tacorp.net) Received: (from by-tor@localhost) by volatile.by-tor.tacorp.net (8.9.3/8.9.3) id BAA00649; Fri, 31 Mar 2000 01:12:21 -0500 (EST) (envelope-from by-tor) Date: Fri, 31 Mar 2000 01:12:21 -0500 (EST) From: Wes Morgan X-Sender: by-tor@volatile.by-tor.tacorp.net To: Vladik Cc: Charles Anderson , current@FreeBSD.ORG Subject: Re: Please test for 8G-OVER-Booting with /boot/loader In-Reply-To: <38E3DC98.3793ADDA@bigfoot.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 Little tip for would-be grub users... I had to play with the compiler flags quite a bit to get a bootable image. I suggest taking the flags used to compile the FreeBSD boot loaders and using them. On Thu, 30 Mar 2000, Vladik wrote: > Hi, for now I am doing this every time (but I also do not > reboot too often). > GRUB has a curses-like based menu thing where you > can specify what to boot and how. You have to > set the config file during the compilation. And then > compile, and then build the floppy with that or install > on to the MBR. And I have not done that yet. > > -- > Vladislav > > Charles Anderson wrote: > > > > Do you do this everytime or just to get things started? > > > > If it's everytime, man that's a pain, if it's just to get things > > started it's easier than what I did. (but now I get a list of what I > > want to boot from the NT bootloader, and I just hit the arrow down to > > FreeBSD and go.) > > > > -Charlie > > On Wed, Mar 29, 2000 at 03:21:39PM -0500, Vladik wrote: > > > Hello, > > > I am not sure if this exactly on topic, > > > but this is how I boot freeBSD partition that is installed > > > beyond cyl 1024 > > > > > > > > > I use GRUB boot loader that understands LBA (www.gnu.org/grub) > > > > > > Once GRUB boots from a floppy, go to GRUB's command prompt and > > > do the following: > > > > > > root (hd0,3,a) # or whatever your FreeBSD root slice is > > > #after the command above, it mounted the partition > > > > > > kernel /kernel -remount > > > boot > > > > > > When kernel boots to the point where it needs to mount a root > > > partion it will ask you, > > > in there you type > > > ufs:/dev/ad0s4a > > > > > > > > > ---- > > > Vladislav > > > > -- > > Charles Anderson caa@columbus.rr.com > > > > No quote, no nothin' > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@engr.sc.edu _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 30 23:47: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.stc-energy.net (relay.stc-energy.net [212.90.160.3]) by hub.freebsd.org (Postfix) with ESMTP id 7E54737BA05 for ; Thu, 30 Mar 2000 23:46:47 -0800 (PST) (envelope-from maxx@ns.stc-energy.net) Received: from ns.stc-energy.net (ns.stc-energy.net [212.90.160.2]) by relay.stc-energy.net (8.9.3/8.9.3) with ESMTP id KAA59571 for ; Fri, 31 Mar 2000 10:46:43 +0300 (EEST) (envelope-from maxx@ns.stc-energy.net) Received: (from root@localhost) by ns.stc-energy.net (8.9.3/8.9.3) id KAA29509 for Some perl administrator ; Fri, 31 Mar 2000 10:46:43 +0300 (EEST) (envelope-from maxx) Date: Fri, 31 Mar 2000 10:46:43 +0300 (EEST) From: "Maxim U. Sivkov" Message-Id: <200003310746.KAA29509@ns.stc-energy.net> To: Some perl administrator Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Subject: Mail::Internet test subject This is a test message that was sent by the test suite of Mail::Internet. Testing. one From foo four >From bar seven To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 0:29:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id 6F50237B994 for ; Fri, 31 Mar 2000 00:29:33 -0800 (PST) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id A7CEE1E00A; Fri, 31 Mar 2000 03:29:13 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id DAA01584; Fri, 31 Mar 2000 03:29:12 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id AAA02707; Fri, 31 Mar 2000 00:28:22 -0800 (PST) Message-Id: <200003310828.AAA02707@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: jkh@zippy.cdrom.com Subject: Re: So, AGAIN, why was tcpdump moved? Cc: current@freebsd.org Date: Fri, 31 Mar 2000 00:28:22 -0800 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just out of curiosity, why is there an "AGAIN" in the subject line, since this is the first email I've gotten on the subject? tcpdump is capable of decrypting ESP, if you give it the key and if it's linked with libcrypto. Since IPSEC is part of FreeBSD, and libcrypto is part of FreeBSD, I figured it would be a nice thing to have. It didn't occur to me that this would change where tcpdump lived (i.e. it seemed like libcrypto was part of FreeBSD) so it wasn't an explicit choice on my part to move distributions. I agree that's a bad side effect. It's easy to disable the decrypting-ESP feature if the disadvantage of having it is greater than the advantage. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 0:33:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A866937B975 for ; Fri, 31 Mar 2000 00:33:55 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA98577; Fri, 31 Mar 2000 00:34:55 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Bill Fenner Cc: current@freebsd.org Subject: Re: So, AGAIN, why was tcpdump moved? In-reply-to: Your message of "Fri, 31 Mar 2000 00:28:22 PST." <200003310828.AAA02707@windsor.research.att.com> Date: Fri, 31 Mar 2000 00:34:54 -0800 Message-ID: <98574.954491694@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just out of curiosity, why is there an "AGAIN" in the subject line, > since this is the first email I've gotten on the subject? Sorry, the first queries about this probably didn't go directly to you since it was only yesterday that I actually bothered to go track down the specific commit which resulted in this behavior in 4.0-RELEASE. There's been general mutterings but no conclusions. > tcpdump is capable of decrypting ESP, if you give it the key and if it's > linked with libcrypto. Since IPSEC is part of FreeBSD, and libcrypto > is part of FreeBSD, I figured it would be a nice thing to have. Agreed. > It didn't occur to me that this would change where tcpdump lived > (i.e. it seemed like libcrypto was part of FreeBSD) so it wasn't an > explicit choice on my part to move distributions. I agree that's a bad > side effect. It's easy to disable the decrypting-ESP feature if the > disadvantage of having it is greater than the advantage. I think most people are pretty flabbergasted that tcpdump is gone from the bindist, so yes, we should definitely see to this side-effect. That said, isn't there some way we could build it twice, once for the crypto dist and once for the bindist? That would mean that the crypto distribution copy simply blops over the bin distribution version if selected and POLA is fully obeyed. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 0:38:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from holly.calldei.com (adsl-208-191-146-189.dsl.hstntx.swbell.net [208.191.146.189]) by hub.freebsd.org (Postfix) with ESMTP id 0D77837BE0D for ; Fri, 31 Mar 2000 00:38:14 -0800 (PST) (envelope-from chris@holly.calldei.com) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id CAA01096; Fri, 31 Mar 2000 02:38:32 -0600 (CST) (envelope-from chris) Date: Fri, 31 Mar 2000 02:38:32 -0600 From: Chris Costello To: Bill Fenner Cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: So, AGAIN, why was tcpdump moved? Message-ID: <20000331023831.A370@holly.calldei.com> Reply-To: chris@calldei.com References: <200003310828.AAA02707@windsor.research.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i In-Reply-To: <200003310828.AAA02707@windsor.research.att.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, March 31, 2000, Bill Fenner wrote: > It didn't occur to me that this would change where tcpdump lived > (i.e. it seemed like libcrypto was part of FreeBSD) so it wasn't an > explicit choice on my part to move distributions. I agree that's a bad > side effect. It's easy to disable the decrypting-ESP feature if the > disadvantage of having it is greater than the advantage. Well, I believe the disadvantage greatly outweighs the advantage in this situation. On one hand you have a tcpdump that can decrypt ESP and on the other you have systems that don't have tcpdump because they didn't install crypto. -- |Chris Costello |Managing programmers is like herding cats. `------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 0:41:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id D3A8337BA52 for ; Fri, 31 Mar 2000 00:41:08 -0800 (PST) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id 1BE1D1E00A; Fri, 31 Mar 2000 03:41:05 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id DAA02366; Fri, 31 Mar 2000 03:41:01 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id AAA02751; Fri, 31 Mar 2000 00:40:11 -0800 (PST) Message-Id: <200003310840.AAA02751@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: jkh@zippy.cdrom.com Subject: Re: So, AGAIN, why was tcpdump moved? Cc: fenner@research.att.com, current@freebsd.org Date: Fri, 31 Mar 2000 00:40:10 -0800 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >That said, isn't there some way we could build it twice, once for the >crypto dist and once for the bindist? That would mean that the crypto >distribution copy simply blops over the bin distribution version if >selected and POLA is fully obeyed. Sounds perfectly reasonable to me. I'd be happy if someone else wants to look at this, or I can look at it on the 10th when I get back from Australia. This would mean there's a src/secure/usr.sbin/tcpdump that builds with crypto and src/usr.sbin/tcpdump that builds without? Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 0:46:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2FAAC37B744 for ; Fri, 31 Mar 2000 00:46:23 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA98681; Fri, 31 Mar 2000 00:47:25 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Bill Fenner Cc: current@freebsd.org Subject: Re: So, AGAIN, why was tcpdump moved? In-reply-to: Your message of "Fri, 31 Mar 2000 00:40:10 PST." <200003310840.AAA02751@windsor.research.att.com> Date: Fri, 31 Mar 2000 00:47:20 -0800 Message-ID: <98671.954492440@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sounds perfectly reasonable to me. I'd be happy if someone else wants > to look at this, or I can look at it on the 10th when I get back from > Australia. This would mean there's a src/secure/usr.sbin/tcpdump that > builds with crypto and src/usr.sbin/tcpdump that builds without? Correct! Both would share some common set of sources with VPATH directives and install conditionally on some boolean set of variable tests where one would always succeed and one always fail unless it was the distribute target being invoked, in which case both would install with different values for DISTRIBUTION and not collide. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 0:51:51 2000 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 CCBD237B637; Fri, 31 Mar 2000 00:51:45 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id KAA01801; Fri, 31 Mar 2000 10:50:12 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Bruce Evans , Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests In-reply-to: Your message of "Thu, 30 Mar 2000 09:15:54 -0800." <200003301715.JAA73702@apollo.backplane.com> Date: Fri, 31 Mar 2000 10:50:12 +0200 Message-ID: <1799.954492612@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003301715.JAA73702@apollo.backplane.com>, Matthew Dillon writes: > The general problem with the timecounter is that not only is the hardware > indeterminant, but the timecounter structure itself is *NOT* MP safe, > at least not by my read of it. Well, read again then :-) I've had a paper in the works about timecounters for over a year now, I should really sit down and finish it. -- 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 Fri Mar 31 0:53:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id BB6F237B744 for ; Fri, 31 Mar 2000 00:53:48 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 18379 invoked from network); 31 Mar 2000 08:53:40 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 31 Mar 2000 08:53:40 -0000 Date: Fri, 31 Mar 2000 18:53:22 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: "Matthew D. Fuller" Cc: Matthew Dillon , Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests In-Reply-To: <20000330174453.D10480@futuresouth.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 Thu, 30 Mar 2000, Matthew D. Fuller wrote: > Does softupdates provide faster performance than async/noatime? I keep > /usr/src and /usr/obj as such, would it be faster with softupdates? And > if so, why? Async is theoretically faster if it is implemented properly. It is poorly implemented in FreeBSD, but is good enough for things like makeworld. From my makeworld logs: async mounts, standard kernel, standard Makefile.inc1, NOSHARED=yes -------------------------------------------------------------- >>> elf make world started on Mon Jan 17 12:11:25 EST 2000 >>> elf make world completed on Mon Jan 17 13:23:23 EST 2000 -------------------------------------------------------------- 4317.91 real 3237.34 user 636.77 sys 11864 maximum resident set size 1105 average shared memory size 1061 average unshared data size 129 average unshared stack size 9103073 page reclaims 15251 page faults 0 swaps 40230 block input operations 4313 block output operations 0 messages sent 0 messages received 7 signals received 372803 voluntary context switches 198051 involuntary context switches There were only 4313 disk writes for the whole makeworld. This shows that -async is doing a good job of stopping writes going to the disk. 4313 writes is too few too take very long. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 0:54:20 2000 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 D615637B8BF; Fri, 31 Mar 2000 00:54:15 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id KAA01896; Fri, 31 Mar 2000 10:54:13 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Jesper Skriver Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests In-reply-to: Your message of "Thu, 30 Mar 2000 21:25:35 +0200." <20000330212535.A49637@skriver.dk> Date: Fri, 31 Mar 2000 10:54:13 +0200 Message-ID: <1894.954492853@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000330212535.A49637@skriver.dk>, Jesper Skriver writes: >On the box below, a relative new dual PIII box, with a Intel >motherboard, does it use the i8254 or the PIIX timecounter ? > >[...] >Timecounter "PIIX" frequency 3579545 Hz You're using the PIIX. -- 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 Fri Mar 31 2:23:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from laurin.munich.netsurf.de (laurin.munich.netsurf.de [194.64.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3015C37B999 for ; Fri, 31 Mar 2000 02:23:21 -0800 (PST) (envelope-from Dirk.Roehrdanz@munich.netsurf.de) Received: from ns1129.munich.netsurf.de (ns1129.munich.netsurf.de [195.180.235.129]) by laurin.munich.netsurf.de (8.9.3/8.9.3) with ESMTP id MAA06666 for ; Fri, 31 Mar 2000 12:23:18 +0200 (MET DST) Received: (qmail 19156 invoked by uid 1001); 31 Mar 2000 10:24:24 -0000 Date: Fri, 31 Mar 2000 12:24:24 +0200 From: Dirk Roehrdanz To: current@FreeBSD.ORG Subject: Re: RSA library problems Message-ID: <20000331122424.A19141@diroxfbsd.dx> References: <38DA4E03.CB2E84A8@originative.co.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="rwEMma7ioTxnRzrJ" X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.ORG on Fri, Mar 24, 2000 at 12:15:16AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --rwEMma7ioTxnRzrJ Content-Type: text/plain; charset=us-ascii Hello, On 0, Kris Kennaway wrote: > On Thu, 23 Mar 2000, Paul Richards wrote: > > > I stuck a dlerror() in there and the problem is > > > > usr/lib/librsaINTL.so: Undefined symbol "BN_mod_exp_mont" > > This symbol is defined in bn_ext.c and should be compiled into libcrypto - > can you verify yours has it? > > Kris > I had the same problem. "BN_mod_exp_mont" is in libcrypto,but isn't visible from librsaINTL.so because libcrypto is loaded in conjunction with the load of /usr/local/libexec/apache/libssl.so via dlopen() . The man page to dlopen states " The symbols exported by objects added to the address space by dlopen() can be accessed only through calls to dlsym()". I have solved the problem with the attached patch. It adds libcrypto to the list of linked libs. Maybe there is a better solution,who knows ? Regards Dirk --rwEMma7ioTxnRzrJ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=diff Index: Makefile =================================================================== RCS file: /usr/current/src/secure/lib/librsaintl/Makefile,v retrieving revision 1.2 diff -u -r1.2 Makefile --- Makefile 2000/03/13 21:50:37 1.2 +++ Makefile 2000/03/31 09:37:12 @@ -9,6 +9,7 @@ SHLIB_MAJOR= 1 CFLAGS+= -I${.OBJDIR} +LDADD+= -lcrypto # rsaref SRCS+= rsa_err.c rsa_eay.c rsa_intlstubs.c --rwEMma7ioTxnRzrJ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 2:40:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 106BD37B806; Fri, 31 Mar 2000 02:40:28 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id CAA99962; Fri, 31 Mar 2000 02:40:27 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 31 Mar 2000 02:40:27 -0800 (PST) From: Kris Kennaway To: Bill Fenner Cc: jkh@zippy.cdrom.com, current@freebsd.org Subject: Re: So, AGAIN, why was tcpdump moved? In-Reply-To: <200003310828.AAA02707@windsor.research.att.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 Fri, 31 Mar 2000, Bill Fenner wrote: > Just out of curiosity, why is there an "AGAIN" in the subject line, > since this is the first email I've gotten on the subject? First I've heard about it too. > It didn't occur to me that this would change where tcpdump lived > (i.e. it seemed like libcrypto was part of FreeBSD) so it wasn't an > explicit choice on my part to move distributions. I agree that's a bad > side effect. It's easy to disable the decrypting-ESP feature if the > disadvantage of having it is greater than the advantage. AFAIK there were two versions built, one which ends up in the bin distribution and one in the crypto distribution (I believe ppp also does this to take advantage of crypto support if it's available). Both versions of tcpdump are built from the same place (usr.sbin/tcpdump where it's always been), and so theres no need to have two separate copies of the build infrastructure (e.g. the proposed extra one in secure/). There *were* several problems with the .ifdefs in the tcpdump makefile which I fixed prior to 4.0, and I thought I had fixed the problem of tcpdump in the bin distribution being linked against libcrypto (this was broken in the initial 4.0 Release but fixed when jkh rereleased it). If I screwed something up I apologise - I didn't test the outcome of a full make release. I just looked at the makefile again - am I misinterpreting the following: .if exists(../../../secure) && !defined(NOCRYPT) && !defined(NOSECURE) && \ !defined(NO_OPENSSL) && !defined(RELEASE_CRUNCH) DISTRIBUTION=crypto ... .endif which I interpret as saying "if we're building release and making the bin distribution (NOCRYPT) then don't build the crypto stuff, and leave us in the bin distribution, but if we're not building NOCRYPT then put us in the crypto distribution and build the extra bits". This is the same thing usr.sbin/ppp does as far as I can see (it was copied directly from there). What did I miss? Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 2:46:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 57E8837B919; Fri, 31 Mar 2000 02:46:16 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA99180; Fri, 31 Mar 2000 02:47:26 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: Bill Fenner , current@FreeBSD.ORG Subject: Re: So, AGAIN, why was tcpdump moved? In-reply-to: Your message of "Fri, 31 Mar 2000 02:40:27 PST." Date: Fri, 31 Mar 2000 02:47:26 -0800 Message-ID: <99177.954499646@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There *were* several problems with the .ifdefs in the tcpdump makefile > which I fixed prior to 4.0, and I thought I had fixed the problem of > tcpdump in the bin distribution being linked against libcrypto (this was > broken in the initial 4.0 Release but fixed when jkh rereleased it). If I > screwed something up I apologise - I didn't test the outcome of a full > make release. What you missed is that this pass is done once, in the release.2 target of release/Makefile. Perhaps if you'd also special-cased it in release.5, it might have worked as you expected. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 2:53: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 363C337B938 for ; Fri, 31 Mar 2000 02:53:06 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 624DCDC26; Fri, 31 Mar 2000 12:53:04 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20000330174453.D10480@futuresouth.com> References: <200003300604.WAA68031@apollo.backplane.com> <20000330174453.D10480@futuresouth.com> Date: Fri, 31 Mar 2000 12:24:27 +0200 To: "Matthew D. Fuller" , Matthew Dillon From: Brad Knowles Subject: Re: SMP buildworld times / performance tests Cc: Andy Farkas , freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 5:44 PM -0600 2000/3/30, Matthew D. Fuller wrote: > Does softupdates provide faster performance than async/noatime? I keep > /usr/src and /usr/obj as such, would it be faster with softupdates? And > if so, why? Of course, once you ask this question, the next logical one that follows is "what happens if you do all three?" -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 2:53:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id E997437BBE0 for ; Fri, 31 Mar 2000 02:53:07 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 2644EDBDF; Fri, 31 Mar 2000 12:53:06 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Fri, 31 Mar 2000 12:26:31 +0200 To: Carl Makin From: Brad Knowles Subject: Re: Dual Pathing to SCSI/FC devices. Cc: mjacob@feral.com, current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:41 AM +1000 2000/3/31, Carl Makin wrote: > heh, the buzzword for this is "Dynamic Failover". :) In management > circles where the current focus is on 24x7, this is seen as a distinct > advantage. Okay, then I'd certainly like to have that. > "Dual Pathing" the buzzword for using both paths to the device would also > be desirable, but then you get into things like wanting to optimise data > paths depending on how busy each path is. Ahh, right. Basically you're talking about active/active load balancing. Yup, I'd like to have that, too. > No, sorry. I can't actually say what box we're buying yet since we > haven't signed the contract. :( You may be fortunate -- we were stupid enough to sign a three year lease on equipment we thought would do the job, but are now having some problems with. ;-( -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 2:53:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 9AB3C37B921; Fri, 31 Mar 2000 02:53:45 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id CAA03977; Fri, 31 Mar 2000 02:53:45 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 31 Mar 2000 02:53:44 -0800 (PST) From: Kris Kennaway To: "Jordan K. Hubbard" Cc: Bill Fenner , current@FreeBSD.ORG Subject: Re: So, AGAIN, why was tcpdump moved? In-Reply-To: <99177.954499646@zippy.cdrom.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 Fri, 31 Mar 2000, Jordan K. Hubbard wrote: > What you missed is that this pass is done once, in the release.2 > target of release/Makefile. Perhaps if you'd also special-cased it in > release.5, it might have worked as you expected. Aha, so I see. I'll commit a fix tomorrow if you don't get there sooner. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 3:40:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from gwdu42.gwdg.de (gwdu42.gwdg.de [134.76.10.26]) by hub.freebsd.org (Postfix) with ESMTP id 9E78437B8C3 for ; Fri, 31 Mar 2000 03:40:20 -0800 (PST) (envelope-from rhurlin@gwdg.de) Received: from uffz02.uni-forst.gwdg.de ([134.76.195.161] helo=gwdg.de) by gwdu42.gwdg.de with esmtp (Exim 3.12 #1) id 12azml-0002rh-00; Fri, 31 Mar 2000 13:40:19 +0200 Message-ID: <38E48E8F.791B93CB@gwdg.de> Date: Fri, 31 Mar 2000 13:39:59 +0200 From: Rainer Hurling Organization: Institut fuer Forstzoologie und Waldschutz X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en, de MIME-Version: 1.0 To: Leif Neland Cc: current@FreeBSD.ORG Subject: Re: Reading from bad disk ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland wrote: > > > It seems Warner Losh wrote: > ... > > > mount it in front of the drive to get it to run at a reasonable > > > temperature. W/o the fan, it was running at 58C or so. With the fan > > > it runs at 39C or so. I've included the script that I use to find > > > this information out. Ken Merry sent it to me. It works on some IBM > > > drives. > > > > > > Warner > > > > > > #!/bin/sh > > > > > > TEMPC=`camcontrol cmd -v -n da -u 0 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1"` > > > > > > TEMPF=`echo " 2 k $TEMPC 9 * 5 / 32 + p" | dc` > > > > > > echo "The temperature is: $TEMPF F $TEMPC C" > > > Tried this: > #!/bin/sh > > TEMPC=`camcontrol cmd -v -n da -u 2 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1"` > TEMPF=`echo " 2 k $TEMPC 9 * 5 / 32 + p" | dc` > echo "The temperature is: $TEMPF F $TEMPC C" > > I.e. replaced -u 0 with -u 2, because unit 2 is an IBM: > > ncr0: port 0xd100-0xd1ff mem 0x20000000-0x200000ff irq 11 at device 1.0 on pci0 > ncr0: driver is using old-style compatability shims > da1 at ncr0 bus 0 target 1 lun 0 > da0 at ncr0 bus 0 target 0 lun 0 > da2 at ncr0 bus 0 target 2 lun 0 > da2: Fixed Direct Access SCSI-2 device > da2: 10.000MB/s transfers (10.000MHz, offset 8) > da2: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) > > But I get this: > > camcontrol: error sending command > (pass2:ncr0:0:2:0): LOG SENSE. CDB: 4d 0 76 0 0 0 0 0 20 0 > (pass2:ncr0:0:2:0): ILLEGAL REQUEST asc:24,0 > (pass2:ncr0:0:2:0): Invalid field in CDB > dc: stack empty > The temperature is: 33.80 F C > > Does this simply mean this drive does not support temperature measurement, > or should something more be changed to use dev da2 instead of da0? > > I'm running a week or so old current. > > Leif > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Have had same Problem with my DCAS-34330's. Having a look in IBM's product specification at http://www.storage.ibm.com/techsup/hddtech/prodspec/dcas_spw.pdf, chapter 7.8 and others. It seems there is no information logging in this type of harddisk drive?! Rainer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 3:59:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from hydrant.intranova.net (hydrant.ncw.qc.ca [209.201.95.10]) by hub.freebsd.org (Postfix) with SMTP id 593AD37BBD3 for ; Fri, 31 Mar 2000 03:58:52 -0800 (PST) (envelope-from oogali@intranova.net) Received: (qmail 27456 invoked from network); 31 Mar 2000 12:02:11 -0000 Received: from localhost.abuselabs.com (HELO localhost) (missnglnk@127.0.0.1) by localhost.abuselabs.com with SMTP; 31 Mar 2000 12:02:11 -0000 Date: Fri, 31 Mar 2000 07:02:11 -0500 (EST) From: Omachonu Ogali To: freebsd-small@freebsd.org Cc: freebsd-current@freebsd.org Subject: PicoBSD 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 following patch is for -CURRENT. It at least gets past that dumb floppy loop. The problem I'm having is that after the scripts, nothing else is done, it just sits there with "Welcome to PicoBSD". Any ideas? To Luigi: I made the changes you asked for, disregard that patchfile as I've incorporated those changes in here. -- snip -- --- /usr/src/release/picobsd/build/Makefile.crunch Tue Feb 8 03:27:55 2000 +++ /usr/src/release/picobsd/build/Makefile.crunch Thu Mar 30 14:28:20 2000 @@ -4,3 +4,3 @@ SRC?=/usr/src -CRUNCHFLAGS+= -DNOPAM -DRELEASE_CRUNCH -DNOSECURE -DNOCRYPT +CRUNCHFLAGS+= -DNOPAM -DRELEASE_CRUNCH -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC @@ -31,12 +31,12 @@ install: - cp crunch1 /mnt/stand/crunch - chmod 555 /mnt/stand/crunch + cp crunch1 ${MFS_MOUNTPOINT}/stand/crunch + chmod 555 ${MFS_MOUNTPOINT}/stand/crunch for i in `crunchgen -l crunch1.conf` ; \ do \ - ln /mnt/stand/crunch /mnt/stand/$${i}; \ + ln ${MFS_MOUNTPOINT}/stand/crunch ${MFS_MOUNTPOINT}/stand/$${i}; \ done - rm /mnt/stand/crunch + rm ${MFS_MOUNTPOINT}/stand/crunch # Install the MIB files - #mkdir -p /mnt/usr/local/share/snmp/mibs - #cp ../../net/crunch1/mibs/*.txt /mnt/usr/local/share/snmp/mibs/ + #mkdir -p ${MFS_MOUNTPOINT}/usr/local/share/snmp/mibs + #cp ../../net/crunch1/mibs/*.txt ${MFS_MOUNTPOINT}/usr/local/share/snmp/mibs/ --- /usr/src/release/picobsd/build/build Tue Feb 8 03:24:59 2000 +++ /usr/src/release/picobsd/build/build Thu Mar 30 14:33:40 2000 @@ -75,3 +75,3 @@ -# Main build procedure. It calls another scripts (stage1) +# Main build procedure. It calls another script (stage1) main() { @@ -103,4 +103,5 @@ echo -n "-> Cleaning temporary files... " - umount -f /mnt - vnconfig -u /dev/rvn0 + umount -f ${MFS_MOUNTPOINT} + rm -rf ${MFS_MOUNTPOINT} + vnconfig -u /dev/rvn${VNUM} ./clean ${TYPE} --- /usr/src/release/picobsd/build/crunch.inc Tue Feb 8 03:29:18 2000 +++ /usr/src/release/picobsd/build/crunch.inc Thu Mar 30 12:04:03 2000 @@ -6 +6,2 @@ NONETGRAPH=yes +NOIPSEC=yes --- /usr/src/release/picobsd/build/mfs.mtree Tue Feb 8 06:39:28 2000 +++ /usr/src/release/picobsd/build/mfs.mtree Thu Mar 30 12:04:04 2000 @@ -49,2 +49,8 @@ .. + locale + .. + syscons + .. + nls + .. .. --- /usr/src/release/picobsd/build/stage1 Tue Feb 8 03:25:00 2000 +++ /usr/src/release/picobsd/build/stage1 Thu Mar 30 14:03:27 2000 @@ -10,4 +10,8 @@ +# By default, /tmp should exist. +# MFS_NAME=fs.PICOBSD -MFS_MOUNTPOINT=/mnt +MFS_MOUNTPOINT=`mktemp -d "/tmp/picobsd.XXXXXXXXXX"` +export MFS_MOUNTPOINT + # fail errno errcode @@ -21,3 +25,3 @@ no_vnconfig) - echo "Error while doing vnconfig of ${MFS_NAME} on /dev/rvn0..." + echo "Error while doing vnconfig of ${MFS_NAME} on /dev/rvn${VNUM}..." echo " Most probably your running kernel doesn't have the vn(4) device." @@ -28,3 +32,3 @@ no_mount) - echo "Error while mounting ${MFS_NAME} (/dev/vn0c) on ${MFS_MOUNTPOINT}" + echo "Error while mounting ${MFS_NAME} (/dev/vn${VNUM}c) on ${MFS_MOUNTPOINT}" ;; @@ -40,3 +44,3 @@ vnconfig2) - echo "Error while doing vnconfig of floppy.img on /dev/rvn0..." + echo "Error while doing vnconfig of floppy.img on /dev/rvn${VNUM}..." ;; @@ -56,2 +60,4 @@ echo "-> Aborting $0" + umount ${MFS_MOUNTPOINT} 2> /dev/null || true + rm -rf ${MFS_MOUNTPOINT} 2> /dev/null || true exit 10 @@ -63,5 +69,9 @@ echo "-> Preparing MFS filesystem..." - umount /dev/vn0 2> /dev/null || true + VNUM=`mount | awk "/vn/ { num++ } END { printf \"%d\", num }"` + export VNUM + echo "-> Using vn${VNUM}..." + + umount /dev/vn${VNUM} 2> /dev/null || true umount ${MFS_MOUNTPOINT} 2> /dev/null || true - vnconfig -u /dev/rvn0 2> /dev/null || true + vnconfig -u /dev/rvn${VNUM} 2> /dev/null || true @@ -72,3 +82,3 @@ - vnconfig -s labels -c /dev/rvn0 ${MFS_NAME} 2>/dev/null || \ + vnconfig -s labels -c /dev/rvn${VNUM} ${MFS_NAME} 2>/dev/null || \ fail $? no_vnconfig @@ -80,9 +90,9 @@ if [ ${MFS_SIZE} -lt 1024 ] ; then - disklabel -rw /dev/rvn0 fd${MFS_SIZE} || fail $? disklabel + disklabel -rw /dev/rvn${VNUM} fd${MFS_SIZE} || fail $? disklabel else - disklabel -rw vn0 auto || fail $? disklabel + disklabel -rw vn${VNUM} auto || fail $? disklabel fi - newfs -i ${MFS_INODES} -m 0 -p 0 -o space /dev/rvn0c - mount /dev/vn0c ${MFS_MOUNTPOINT} || fail $? no_mount + newfs -i ${MFS_INODES} -m 0 -p 0 -o space /dev/rvn${VNUM}c + mount /dev/vn${VNUM}c ${MFS_MOUNTPOINT} || fail $? no_mount @@ -148,4 +158,4 @@ umount ${MFS_MOUNTPOINT} - fsck -p /dev/rvn0c - vnconfig -u /dev/rvn0 + fsck -p /dev/rvn${VNUM}c + vnconfig -u /dev/rvn${VNUM} } @@ -174,3 +184,3 @@ - vnconfig -c /dev/rvn0 picobsd.bin || fail $? vnconfig2 + vnconfig -c /dev/rvn${VNUM} picobsd.bin || fail $? vnconfig2 @@ -179,8 +189,8 @@ # XXX todo: use a type matching floppy size. - disklabel -Brw -b /boot/boot1 -s /boot/boot2 /dev/rvn0 fd1440 || \ + disklabel -Brw -b /boot/boot1 -s /boot/boot2 /dev/rvn${VNUM} fd1440 || \ fail $? disklabel - newfs -i ${FLOPPY_INODES} -m 0 -p 0 -o space /dev/rvn0c + newfs -i ${FLOPPY_INODES} -m 0 -p 0 -o space /dev/rvn${VNUM}c - mount /dev/vn0c ${MFS_MOUNTPOINT} + mount /dev/vn${VNUM}c ${MFS_MOUNTPOINT} @@ -217,3 +227,3 @@ files="motd" - echo "-> Copying language dependent files: ${files} -> /mnt/etc ..." + echo "-> Copying language dependent files: ${files} -> ${MFS_MOUNTPOINT}/etc ..." for i in ${files} ; do @@ -265,3 +275,3 @@ umount ${MFS_MOUNTPOINT} - vnconfig -u /dev/rvn0 + vnconfig -u /dev/rvn${VNUM} # rm kernel.gz ${MFS_NAME} --- /usr/src/release/picobsd/dial/Makefile.mfs Fri Aug 27 21:33:14 1999 +++ /usr/src/release/picobsd/dial/Makefile.mfs Thu Mar 30 12:12:19 2000 @@ -4,3 +4,5 @@ +.ifndef (DESTDIR) DESTDIR?=/mnt +.endif @@ -15,3 +17,3 @@ .if ${LANGUAGE} == pl -LOCALE= pl_PL.ISO_8859-2 +LOCALE=pl_PL.ISO_8859-2 LOCALE_LINKS=${PL_LOCALE_LINKS} @@ -20,3 +22,3 @@ .else -LOCALE= en_US.ISO_8859-1 +LOCALE=en_US.ISO_8859-1 LOCALE_LINKS=${US_LOCALE_LINKS} @@ -27,3 +29,3 @@ tree: - mtree -deU -f mfs.mtree -p ${DESTDIR} + mtree -deU -f ../build/mfs.mtree -p ${DESTDIR} @@ -44,3 +46,3 @@ ln -s /etc/termcap termcap; \ - echo emacs >/mnt/usr/share/misc/init.ee; \ + echo emacs >${DESTDIR}/usr/share/misc/init.ee; \ cd ../; \ @@ -51,2 +53,3 @@ done; \ + mkdir ${LOCALE}/; \ cp /usr/share/locale/${LOCALE}/* ${LOCALE}/; \ --- /usr/src/release/picobsd/dial/PICOBSD Wed Mar 15 21:45:38 2000 +++ /usr/src/release/picobsd/dial/PICOBSD Thu Mar 30 13:43:06 2000 @@ -31,2 +31,4 @@ options NO_SWAPPING +options COMPAT_OLDISA #Use ISA shims and glue for old drivers +options COMPAT_OLDPCI #Use PCI shims and glue for old drivers --- /usr/src/release/picobsd/dial/crunch1/crunch.conf Tue Feb 8 03:37:50 2000 +++ /usr/src/release/picobsd/dial/crunch1/crunch.conf Thu Mar 30 20:49:05 2000 @@ -4,6 +4,2 @@ # correct value set in 'build' script - you should change it there -# -# NOTE2: use of init(8) is now optional (selectable in "build" script). -# See Makefile for details on how it's added here - you shouldn't add it -# manually here... @@ -21,3 +17,3 @@ -progs ppp ftp telnet ee gzip more +progs ppp ftp telnet ee gzip more init #progs ssh --- /usr/src/release/picobsd/dial/floppy.tree/etc/mfs.rc Fri Aug 27 21:33:17 1999 +++ /usr/src/release/picobsd/dial/floppy.tree/etc/mfs.rc Fri Mar 31 06:49:59 2000 @@ -30,3 +30,8 @@ echo "" +rm -f rc +gzip -d fstab.gz +gzip -d rc.gz . rc +echo "" +date exit 0 --- /usr/src/release/picobsd/dial/floppy.tree/etc/rc Fri Aug 27 21:33:17 1999 +++ /usr/src/release/picobsd/dial/floppy.tree/etc/rc Fri Mar 31 06:54:00 2000 @@ -6,10 +6,16 @@ ############################################ +gzip -9 rc mount -a -t nonfs -if [ -f /etc/rc.conf ]; then + +if [ -f /etc/rc.conf.gz ]; then + gzip -d /etc/rc.conf.gz . /etc/rc.conf + gzip -9 /etc/rc.conf fi # start up the initial network configuration. -if [ -f /etc/rc.network ]; then - . /etc/rc.network - network_pass1 +if [ -f /etc/rc.network.gz ]; then + gzip -d /etc/rc.network.gz + . /etc/rc.network + gzip -9 /etc/rc.network + network_pass1 fi --- /usr/src/release/picobsd/dial/floppy.tree/etc/rc.conf Fri Aug 27 21:33:18 1999 +++ /usr/src/release/picobsd/dial/floppy.tree/etc/rc.conf Fri Mar 31 06:46:33 2000 @@ -29,4 +29,6 @@ ### Allow local configuration override at the very end here ## -if [ -f /etc/rc.conf.local ]; then +if [ -f /etc/rc.conf.local.gz ]; then + gzip -d /etc/rc.conf.local.gz . /etc/rc.conf.local + gzip -9 /etc/rc.conf.local fi --- /usr/src/release/picobsd/dial/floppy.tree/etc/ttys Thu Aug 27 13:38:42 1998 +++ /usr/src/release/picobsd/dial/floppy.tree/etc/ttys Fri Mar 31 06:45:18 2000 @@ -10,22 +10 @@ ttyv0 "/usr/libexec/getty Pc" cons25 on secure -# Virtual terminals -ttyv1 "/usr/libexec/getty Pc" cons25 on secure -ttyv2 "/usr/libexec/getty Pc" cons25 on secure -ttyv3 "/usr/libexec/getty Pc" cons25 on secure -ttyv4 "/usr/libexec/getty Pc" cons25 on secure -ttyv5 "/usr/libexec/getty Pc" cons25 on secure -ttyv6 "/usr/libexec/getty Pc" cons25 on secure -ttyv7 "/usr/libexec/getty Pc" cons25 on secure -ttyv8 "/usr/libexec/getty Pc" cons25 on secure -ttyv9 "/usr/libexec/getty Pc" cons25 on secure -# Pseudo terminals -ttyp0 none network secure -ttyp1 none network secure -ttyp2 none network secure -ttyp3 none network -ttyp4 none network -ttyp5 none network -ttyp6 none network -ttyp7 none network -ttyp8 none network -ttyp9 none network --- /usr/src/release/picobsd/floppy.tree/etc/fstab Tue Feb 8 09:20:49 2000 +++ /usr/src/release/picobsd/floppy.tree/etc/fstab Thu Mar 30 20:48:48 2000 @@ -1,2 +1 @@ -proc /proc procfs rw 0 0 /dev/fd0c /fd ufs rw,noauto 0 0 -- snip -- -- +-------------------------------------------------------------------------+ | Omachonu Ogali oogali@intranova.net | | Intranova Networking Group http://tribune.intranova.net | | PGP Key ID: 0xBFE60839 | | PGP Fingerprint: C8 51 14 FD 2A 87 53 D1 E3 AA 12 12 01 93 BD 34 | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 6:14:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from pr.infosec.ru (pr.infosec.ru [194.135.141.98]) by hub.freebsd.org (Postfix) with ESMTP id 02CD137B652 for ; Fri, 31 Mar 2000 06:14:05 -0800 (PST) (envelope-from blaze@infosec.ru) Received: from blaze (200.0.0.51 [200.0.0.51]) by pr.infosec.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id H9Z76TGL; Fri, 31 Mar 2000 18:14:18 +0400 Date: Fri, 31 Mar 2000 18:13:07 +0400 (MSD) From: Andrey Sverdlichenko X-Sender: blaze@blaze To: freebsd-current@freebsd.org Subject: hostcache 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 to store some info (in kernel) indexed by peer hosts ip addresses. in_hostcache.h interface looks good, but i hasn't found any use of it in -CURRENT kernel sources. It this interface obsoleted by other? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 7: 9:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from fbsd.ods.org (fbsd.ods.org [63.236.135.3]) by hub.freebsd.org (Postfix) with SMTP id A7DB137BB08 for ; Fri, 31 Mar 2000 07:09:52 -0800 (PST) (envelope-from geniusj@ods.org) Received: (qmail 28537 invoked by uid 1000); 31 Mar 2000 15:09:51 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 31 Mar 2000 15:09:51 -0000 Date: Fri, 31 Mar 2000 10:09:50 -0500 (EST) From: Systems Administrator To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: NFS/Vinum problems In-Reply-To: <20000331153939.O6764@mojave.worldwide.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 The thing is i'm not sure if it's vinum, I could also duplicate this on another machine without vinum.. except I duplicated it differently.. Consider the following perl script: #!/usr/bin/perl for ( ; ; ) { system("fetch http://www.web.site/index.html"); } Of course, replacing the site with something else, but on this one box (and the raid), it panic'd the box.. See if you can duplicate this on any 4.0/5.0 boxes you have, I have tried on both and it worked, however it does not crash 3.x boxes.. Try your luck, Jason DiCioccio On Fri, 31 Mar 2000, Greg Lehey wrote: > On Friday, 31 March 2000 at 0:23:04 -0500, Systems Administrator wrote: > > > > panic: lockmgr: pid -2, exclusive lock holder 5 unlocking > > > > Syncing disks... Timedout SCB handled by another timeout > > Timedout handled by another timeout > > > > That is what I get when doing a 'du -k' on an NFS mount from a remote > > machine.. THe machine I am speaking of is the actual nfs server, i'm using > > freebsd's default nfsd/mountd flags as specified by rc.conf.. However, > > when I do lets say, a du -k on the mounted volume, I get that panic.. If > > this is a known bug or if anyone knows how to fix this, get back to me > > asap.. > > Yes, I've seen something like this. My best guess is that there's a > problem in the error recovery code in CAM, but that's just a guess. > If you want to help, give us more information, at least what I'm > asking for in http://www.lemis.com/vinum/how-to-debug.html. In > addition, the way you're using NFS would be very helpful. > > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 7:19:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from esimbis.grp-esim.imt-mrs.fr (esimbis.grp-esim.imt-mrs.fr [147.94.36.196]) by hub.freebsd.org (Postfix) with ESMTP id 8E27C37B7BE for ; Fri, 31 Mar 2000 07:19:19 -0800 (PST) (envelope-from root@esimbis.grp-esim.imt-mrs.fr) Received: from (root@localhost) by esimbis.grp-esim.imt-mrs.fr (8.9.3/jtpda-5.3.2) id RAA63069 for Some perl administrator ; Fri, 31 Mar 2000 17:11:16 +0200 (CEST) Date: Fri, 31 Mar 2000 17:11:16 +0200 (CEST) From: root@esimbis.grp-esim.imt-mrs.fr (Charlie Root) Message-Id: <200003311511.RAA63069@esimbis.grp-esim.imt-mrs.fr> To: Some perl administrator Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Subject: Mail::Internet test subject This is a test message that was sent by the test suite of Mail::Internet. Testing. one From foo four >From bar seven To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 7:19:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from esimbis.grp-esim.imt-mrs.fr (esimbis.grp-esim.imt-mrs.fr [147.94.36.196]) by hub.freebsd.org (Postfix) with ESMTP id 3E9FE37B8A1 for ; Fri, 31 Mar 2000 07:19:22 -0800 (PST) (envelope-from root@esimbis.grp-esim.imt-mrs.fr) Received: from (root@localhost) by esimbis.grp-esim.imt-mrs.fr (8.9.3/jtpda-5.3.2) id RAA63195 for Some perl administrator ; Fri, 31 Mar 2000 17:11:34 +0200 (CEST) Date: Fri, 31 Mar 2000 17:11:34 +0200 (CEST) From: root@esimbis.grp-esim.imt-mrs.fr (Charlie Root) Message-Id: <200003311511.RAA63195@esimbis.grp-esim.imt-mrs.fr> To: Some perl administrator Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Subject: Mail::Internet test subject This is a test message that was sent by the test suite of Mail::Internet. Testing. one From foo four >From bar seven To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 7:20:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from esimbis.grp-esim.imt-mrs.fr (esimbis.grp-esim.imt-mrs.fr [147.94.36.196]) by hub.freebsd.org (Postfix) with ESMTP id 3827637BA1A for ; Fri, 31 Mar 2000 07:20:14 -0800 (PST) (envelope-from root@esimbis.grp-esim.imt-mrs.fr) Received: from (root@localhost) by esimbis.grp-esim.imt-mrs.fr (8.9.3/jtpda-5.3.2) id RAA63536 for Some perl administrator ; Fri, 31 Mar 2000 17:12:26 +0200 (CEST) Date: Fri, 31 Mar 2000 17:12:26 +0200 (CEST) From: root@esimbis.grp-esim.imt-mrs.fr (Charlie Root) Message-Id: <200003311512.RAA63536@esimbis.grp-esim.imt-mrs.fr> To: Some perl administrator Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Subject: Mail::Internet test subject This is a test message that was sent by the test suite of Mail::Internet. Testing. one From foo four >From bar seven To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 7:21:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from drama.navipath.com (drama.navipath.com [216.67.14.8]) by hub.freebsd.org (Postfix) with ESMTP id 10BC537BAEA for ; Fri, 31 Mar 2000 07:21:49 -0800 (PST) (envelope-from forrie@drama.navipath.com) Received: (from root@localhost) by drama.navipath.com with id e2VFL2K12550; Fri, 31 Mar 2000 10:21:02 -0500 (EST) Date: Fri, 31 Mar 2000 10:21:02 -0500 From: Baby Jane Hudson To: Charlie Root Cc: Some perl administrator Subject: Re: your mail Message-ID: <20000331102102.F11939@drama.navipath.com> References: <200003311511.RAA63195@esimbis.grp-esim.imt-mrs.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003311511.RAA63195@esimbis.grp-esim.imt-mrs.fr>; from root@esimbis.grp-esim.imt-mrs.fr on Fri, Mar 31, 2000 at 05:11:34PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Someone can this idiot. On Fri, Mar 31, 2000 at 05:11:34PM +0200, Charlie Root wrote: > Subject: Mail::Internet test subject > > > This is a test message that was sent by the test suite of > Mail::Internet. > > Testing. > > one > > >From foo > four > > >From bar > seven > > > 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 Mar 31 8:46:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from Draculina.otdel-1.org (Draculina.Otdel-1.ORG [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id D335437B652 for ; Fri, 31 Mar 2000 08:46:24 -0800 (PST) (envelope-from nms@otdel-1.org) Received: by Draculina.otdel-1.org (Postfix, from userid 1002) id DEF2C167; Fri, 31 Mar 2000 20:46:20 +0400 (MSD) Date: Fri, 31 Mar 2000 20:46:20 +0400 From: Nikolai Saoukh To: freebsd-current@freebsd.org Subject: kldload of driver for isa pnp card (cycle two) Message-ID: <20000331204620.A33493@Draculina.otdel-1.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hot days of 4.0 preparation are behind. May be some guru will find the solution for the subject? Two problems are here a) devices without driver attached to 'unknown' driver, thus no orphan devices -- no reason to call device_probe method from kldloaded driver. b) if disable 'unknown' driver as was recommended earlier, device still consume resources, and this resources are not presented to kldloaded driver -- resource leak. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 9: 8:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.va.home.com (ha1.rdc1.va.home.com [24.2.32.66]) by hub.freebsd.org (Postfix) with ESMTP id 98A9637B7BE; Fri, 31 Mar 2000 09:08:22 -0800 (PST) (envelope-from jgowdy@home.com) Received: from cx443070a ([24.4.93.90]) by mail.rdc1.va.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <20000331170821.ZJWY12441.mail.rdc1.va.home.com@cx443070a>; Fri, 31 Mar 2000 09:08:21 -0800 Message-ID: <004a01bf9b35$0cc56be0$0100000a@vista1.sdca.home.com> From: "Jeremiah Gowdy" To: , , "FreeBSD questions" Subject: JetDirect 500X and FreeBSD Date: Fri, 31 Mar 2000 09:17:52 -0800 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.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone have any experiance or information about using HP JetDirect 500X Printer Hubs with FreeBSD ? This is mission critical for my company, so any information greatly appriciated. Thank you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 9:47:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8F9B537B652 for ; Fri, 31 Mar 2000 09:47:14 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA29684; Fri, 31 Mar 2000 09:47:05 -0800 (PST) (envelope-from dillon) Date: Fri, 31 Mar 2000 09:47:05 -0800 (PST) From: Matthew Dillon Message-Id: <200003311747.JAA29684@apollo.backplane.com> To: Systems Administrator Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: NFS/Vinum problems References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :The thing is i'm not sure if it's vinum, I could also duplicate this on :another machine without vinum.. except I duplicated it differently.. : :Consider the following perl script: : :#!/usr/bin/perl :for ( ; ; ) { : system("fetch http://www.web.site/index.html"); :} : :Of course, replacing the site with something else, but on this one box :(and the raid), it panic'd the box.. See if you can duplicate this on any :4.0/5.0 boxes you have, I have tried on both and it worked, however it :does not crash 3.x boxes.. : :Try your luck, :Jason DiCioccio Ok, I'm a bit confused. You are running this script on the NFS client while CD'd into an NFS mount and the NFS server is crashing? Or are you running this on the NFS server while CD'd into a local disk mount and the NFS server is crashing? I presume the web site you are fetching from is not crashing. Have you tried exporting a non-raid mount from the server to the client to see if that crashes? The only thing that happens to me when I run the above script on an NFS client while CD'd into an NFS server is that the client winds up with thousands of sockets in TIME_WAIT on the client until it runs out and starts getting 'socket is not connected' errors (I was using a web server on my LAN so the fetches were completeing very quickly). But the NFS server didn't have any problems. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 9:52: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id BFAC037B52C for ; Fri, 31 Mar 2000 09:52:06 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA29716; Fri, 31 Mar 2000 09:52:06 -0800 (PST) (envelope-from dillon) Date: Fri, 31 Mar 2000 09:52:06 -0800 (PST) From: Matthew Dillon Message-Id: <200003311752.JAA29716@apollo.backplane.com> To: Matthew Dillon Cc: Systems Administrator , Greg Lehey , current@FreeBSD.ORG Subject: Re: NFS/Vinum problems References: <200003311747.JAA29684@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ::Jason DiCioccio Another possibility -- could you post your 'dmesg' output? One thing that NFS does do is severely exercise both the network and the SCSI device in a concurrent fashion. If you happen to be using an NCR SCSI chipset, that could be the cause of the problem (though I have never in my life seen the panic message you posted in relation to the NCR cards). If you can get the panic regularly then it may be worthwhile trying to get some more information out of it. If you compile up a kernel with the DDB option and your console is not running X, then the kernel will drop into DDB on the console when it panics and allow you to do a stack 'trace'. You may also be able to then dump the machine by typing 'panic' manually at the ddb prompt after copying down the trace information. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 10: 0:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 1836037BCC7 for ; Fri, 31 Mar 2000 10:00:42 -0800 (PST) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA23565 for ; Fri, 31 Mar 2000 10:00:41 -0800 (PST) Date: Fri, 31 Mar 2000 10:00:40 -0800 (PST) From: Julian Elischer To: current@freebsd.org Subject: Neat kernel development environment. 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 have just managed to get the following going: By writing a device driver that is two terminals back-to-back, and configuring vmware to map one of the virtual ttys over the 'null-modem' device, and then running a kernel configured with the console on com1 and the gdb port on com2, (in the virtual machine in vmware) I can on a single machine run a test system, allow it to run the vmware X server, and at the same time have access to the console, AND be able to single step it under xxdgb or DDB depending on the task. Thus no need to have that second machine for debugging.. :-) It's amazing to see on the same X screen, 1/ The xserver of the virtual BSD box 2/ the console in another window, (which can be sent into DDB if needed) 3/ a 3rd window running xxgdb, single stepping the kernel with source and setting breakpoints etc. 4/ some othe rwindow on the host system, completely unaffected. I'll try get a screenshot. (And yes I did buy a vmware licence) Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 10:15:12 2000 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 06CA837B69E for ; Fri, 31 Mar 2000 10:15:07 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id KAA48258; Fri, 31 Mar 2000 10:15:05 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id KAA15514; Fri, 31 Mar 2000 10:14:58 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200003311814.KAA15514@whistle.com> Subject: Re: Neat kernel development environment. In-Reply-To: from Julian Elischer at "Mar 31, 2000 10:00:40 am" To: Julian Elischer Date: Fri, 31 Mar 2000 10:14:57 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 Julian Elischer writes: | | I have just managed to get the following going: | | By writing a device driver that is two terminals back-to-back, | and configuring vmware to map one of the virtual ttys over the | 'null-modem' device, and then running a kernel configured with the console | on com1 and the gdb port on com2, (in the virtual machine in vmware) | I can on a single machine run a test system, allow it to run the vmware X | server, and at the same time have access to the console, AND be able to | single step it under xxdgb or DDB depending on the task. FYI, via the latest Etherboot port that was commited you can netboot a vmware machine. Could you post your null-modem device? ... it saves on serial ports. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 10:31:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 528B637B693 for ; Fri, 31 Mar 2000 10:31:33 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA30865; Fri, 31 Mar 2000 10:31:31 -0800 (PST) (envelope-from dillon) Date: Fri, 31 Mar 2000 10:31:31 -0800 (PST) From: Matthew Dillon Message-Id: <200003311831.KAA30865@apollo.backplane.com> To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: Neat kernel development environment. References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I have just managed to get the following going: : :By writing a device driver that is two terminals back-to-back, :and configuring vmware to map one of the virtual ttys over the :.. : :Thus no need to have that second machine for debugging.. ::-) :It's amazing to see on the same X screen, :1/ The xserver of the virtual BSD box :2/ the console in another window, (which can be sent into DDB if needed) :3/ a 3rd window running xxgdb, single stepping the kernel with source :and setting breakpoints etc. :4/ some othe rwindow on the host system, completely unaffected. : :I'll try get a screenshot. :(And yes I did buy a vmware licence) : :Julian I can just see all the coolness seeping out. Now guys, we have to have as a goal something at least as comparable as what IBM did with one of their mainframes. Oh, say, lets shoot for being able to run 4000 copies or so of linux under VMWare on FreeBSD :-) Once we fix the deadlocks, that 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 Fri Mar 31 10:34:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from fbsd.ods.org (fbsd.ods.org [63.236.135.3]) by hub.freebsd.org (Postfix) with SMTP id 4FE2737BFAA for ; Fri, 31 Mar 2000 10:34:41 -0800 (PST) (envelope-from geniusj@ods.org) Received: (qmail 31306 invoked by uid 1000); 31 Mar 2000 18:34:30 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 31 Mar 2000 18:34:30 -0000 Date: Fri, 31 Mar 2000 13:34:30 -0500 (EST) From: Systems Administrator To: Matthew Dillon Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: NFS/Vinum problems In-Reply-To: <200003311752.JAA29716@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 Here is my dmesg output, and btw, sorry.. the perl script was not running on the NFS volume, just regularly on a regular 4.0 box, and it crashed the box (yes, I had login limits set), I was just giving another example of what seems to be some instability in 4.0 under high loads.. Here my dmesg from the raid/nfs server: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Fri Mar 31 00:03:37 EST 2000 geniusj@fbsd4.ods.org:/usr/src/sys/compile/RAID Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 186006596 Hz CPU: IDT WinChip C6 (186.01-MHz 586-class CPU) Origin = "CentaurHauls" Id = 0x541 Stepping = 1 Features=0x8000b5 real memory = 50331648 (49152K bytes) config> en ed0 config> po ed0 0x240 config> ir ed0 5 config> iom ed0 0xd8000 config> f ed0 0 config> q avail memory = 45297664 (44236K bytes) Preloaded elf kernel "kernel" at 0xc036f000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc036f09c. npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 3.0 on pci0 pci1: on pcib1 isab0: at device 4.0 on pci0 eisa0: on isab0 mainboard0: on eisa0 slot 0 isa0: on isab0 ahc0: port 0xf800-0xf8ff mem 0xfedff000-0xfedffff f irq 15 at device 5.0 on pci0 ahc0: Using left over BIOS settings ahc0: aic7855 Single Channel A, SCSI Id=7, 3/255 SCBs ahc1: port 0xf400-0xf4ff mem 0xfedfe000-0xfedfeff f irq 15 at device 6.0 on pci0 ahc1: Using left over BIOS settings ahc1: aic7855 Single Channel A, SCSI Id=7, 3/255 SCBs fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3cf iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA (mono) <16 virtual consoles, flags=0x200> ed0 at port 0x240-0x25f iomem 0xd8000-0xd9fff irq 5 drq 0 on isa0 ed0: address 00:00:c0:00:dc:ba, type SMC8416T (16 bit) Waiting 15 seconds for SCSI devices to settle vinum: loaded da1 at ahc1 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: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) da5 at ahc1 bus 0 target 5 lun 0 da5: Fixed Direct Access SCSI-2 device da5: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da5: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) da6 at ahc1 bus 0 target 6 lun 0 da6: Fixed Direct Access SCSI-2 device da6: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da6: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) da4 at ahc1 bus 0 target 4 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da4: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) da3 at ahc1 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da3: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) da2 at ahc1 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da2: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) Mounting root from ufs:/dev/da0s1a cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.032MB/s transfers (4.032MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present 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), Tagged Queueing Enabled da0: 2048MB (4195116 512 byte sectors: 64H 32S/T 2048C) WARNING: / was not properly dismounted vinum: reading configuration from /dev/da6s1e vinum: updating configuration from /dev/da5s1e vinum: updating configuration from /dev/da4s1e vinum: updating configuration from /dev/da3s1e vinum: updating configuration from /dev/da2s1e vinum: updating configuration from /dev/da1s1e I hope this helps.. and i'll setup crash dumping on raid, thanks for your time On Fri, 31 Mar 2000, Matthew Dillon wrote: > ::Jason DiCioccio > > Another possibility -- could you post your 'dmesg' output? One thing > that NFS does do is severely exercise both the network and the SCSI > device in a concurrent fashion. > > If you happen to be using an NCR SCSI chipset, that could be the cause > of the problem (though I have never in my life seen the panic message > you posted in relation to the NCR cards). > > If you can get the panic regularly then it may be worthwhile trying to > get some more information out of it. If you compile up a kernel with > the DDB option and your console is not running X, then the kernel will > drop into DDB on the console when it panics and allow you to do a > stack 'trace'. You may also be able to then dump the machine by typing > 'panic' manually at the ddb prompt after copying down the trace > information. > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 10:39:17 2000 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 44CDB37BA6A for ; Fri, 31 Mar 2000 10:39:11 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA05252; Fri, 31 Mar 2000 20:39:04 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: Neat kernel development environment. In-reply-to: Your message of "Fri, 31 Mar 2000 10:31:31 -0800." <200003311831.KAA30865@apollo.backplane.com> Date: Fri, 31 Mar 2000 20:39:04 +0200 Message-ID: <5250.954527944@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003311831.KAA30865@apollo.backplane.com>, Matthew Dillon writes: >:I have just managed to get the following going: >: >:By writing a device driver that is two terminals back-to-back, >:and configuring vmware to map one of the virtual ttys over the >:.. >: >:Thus no need to have that second machine for debugging.. >::-) >:It's amazing to see on the same X screen, >:1/ The xserver of the virtual BSD box >:2/ the console in another window, (which can be sent into DDB if needed) >:3/ a 3rd window running xxgdb, single stepping the kernel with source >:and setting breakpoints etc. >:4/ some othe rwindow on the host system, completely unaffected. >: >:I'll try get a screenshot. >:(And yes I did buy a vmware licence) >: >:Julian > > I can just see all the coolness seeping out. Now guys, we have to > have as a goal something at least as comparable as what IBM did > with one of their mainframes. Oh, say, lets shoot for being able to > run 4000 copies or so of linux under VMWare on FreeBSD :-) > > Once we fix the deadlocks, that is. We don't need VMWare really, we can just run N jails... -- 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 Fri Mar 31 10:39:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from fbsd.ods.org (fbsd.ods.org [63.236.135.3]) by hub.freebsd.org (Postfix) with SMTP id 2214E37B897 for ; Fri, 31 Mar 2000 10:39:07 -0800 (PST) (envelope-from geniusj@ods.org) Received: (qmail 31362 invoked by uid 1000); 31 Mar 2000 18:39:06 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 31 Mar 2000 18:39:06 -0000 Date: Fri, 31 Mar 2000 13:39:06 -0500 (EST) From: Systems Administrator To: Matthew Dillon Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: NFS/Vinum problems In-Reply-To: <200003311752.JAA29716@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 One more thing, here's my kernel config file just in case you need it: machine i386 cpu I586_CPU ident RAID maxusers 64 makeoptions DEBUG=-g #Build kernel with gdb(1) debug options DDB_UNATTENDED options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep options NFS #Network Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options NMBCLUSTERS=10240 options VINUMDEBUG #enable Vinum debugging hooks device isa device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # SCSI Controllers device ahc # AHA2940 and onboard AIC7xxx devices # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device cd # CD device pass # Passthrough device (direct SCSI access) device mlx # Mylex DAC960 family # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # ISA Ethernet NICs. device ed0 at isa? port 0x240 irq 5 iomem 0xd8000 # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device vinum #Vinum concat/mirror/raid driver pseudo-device snp # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter On Fri, 31 Mar 2000, Matthew Dillon wrote: > ::Jason DiCioccio > > Another possibility -- could you post your 'dmesg' output? One thing > that NFS does do is severely exercise both the network and the SCSI > device in a concurrent fashion. > > If you happen to be using an NCR SCSI chipset, that could be the cause > of the problem (though I have never in my life seen the panic message > you posted in relation to the NCR cards). > > If you can get the panic regularly then it may be worthwhile trying to > get some more information out of it. If you compile up a kernel with > the DDB option and your console is not running X, then the kernel will > drop into DDB on the console when it panics and allow you to do a > stack 'trace'. You may also be able to then dump the machine by typing > 'panic' manually at the ddb prompt after copying down the trace > information. > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 11: 2: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 222CE37B897 for ; Fri, 31 Mar 2000 11:02:02 -0800 (PST) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA23780; Fri, 31 Mar 2000 11:01:59 -0800 (PST) Date: Fri, 31 Mar 2000 11:01:58 -0800 (PST) From: Julian Elischer To: Doug Ambrisko Cc: current@FreeBSD.ORG Subject: Re: Neat kernel development environment. In-Reply-To: <200003311814.KAA15514@whistle.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'll put the device driver on http://www.freebsd.org/~julian/ but it needs teh eyes of someone who's really at home in the tty system to look at it. I got kinda confused half way through hacking it (from the pty driver) and it shows. basically each pair of minor numbers is a pair and are connected to each other back-to-back. The support for 'select' etc is a bit confused at this stage. also originally I wanted it to shut down the other one (e.g. like loss of carrier) when one gets closed, and for one that is openning to stall waiting for its partner, but it turns out that makes it hard to use with vmware. So I backed that out (which gives a bit more confusion). the screenshot will be there too, (but it's big) also the little script I use to get it all sarteed (trivial). Julian On Fri, 31 Mar 2000, Doug Ambrisko wrote: > Julian Elischer writes: > | > | I have just managed to get the following going: > | > | By writing a device driver that is two terminals back-to-back, > | and configuring vmware to map one of the virtual ttys over the > | 'null-modem' device, and then running a kernel configured with the console > | on com1 and the gdb port on com2, (in the virtual machine in vmware) > | I can on a single machine run a test system, allow it to run the vmware X > | server, and at the same time have access to the console, AND be able to > | single step it under xxdgb or DDB depending on the task. > > FYI, via the latest Etherboot port that was commited you can netboot a > vmware machine. Could you post your null-modem device? ... it saves on > serial ports. > > Doug A. > > > 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 Mar 31 11: 5:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 1CD5237BE64 for ; Fri, 31 Mar 2000 11:05:19 -0800 (PST) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA23798; Fri, 31 Mar 2000 11:05:13 -0800 (PST) Date: Fri, 31 Mar 2000 11:05:13 -0800 (PST) From: Julian Elischer To: Poul-Henning Kamp Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: Neat kernel development environment. In-Reply-To: <5250.954527944@critter.freebsd.dk> 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 Oh? can you run a kernel in a jail for debugging? That's what I'm using it for.. (debugging kernel code.. I only have one machine here.) On Fri, 31 Mar 2000, Poul-Henning Kamp wrote: > > run 4000 copies or so of linux under VMWare on FreeBSD :-) Unfortunatly you can only run one vmware at a time under BSD. > > > > Once we fix the deadlocks, that is. > > We don't need VMWare really, we can just run N jails... > > -- > 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 Fri Mar 31 11:20:29 2000 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 2EBC237BDCA for ; Fri, 31 Mar 2000 11:20:25 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id VAA05393; Fri, 31 Mar 2000 21:20:17 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: Neat kernel development environment. In-reply-to: Your message of "Fri, 31 Mar 2000 11:05:13 -0800." Date: Fri, 31 Mar 2000 21:20:17 +0200 Message-ID: <5391.954530417@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Julian El ischer writes: >Oh? can you run a kernel in a jail for debugging? No, not quite yet, but what IBM bragged about the 41k linuxes for was for what jails do for you. Poul-Henning >That's what I'm using it for.. >(debugging kernel code.. I only have one machine here.) > > >On Fri, 31 Mar 2000, Poul-Henning Kamp wrote: >> > run 4000 copies or so of linux under VMWare on FreeBSD :-) > >Unfortunatly you can only run one vmware at a time under BSD. > >> > >> > Once we fix the deadlocks, that is. >> >> We don't need VMWare really, we can just run N jails... >> >> -- >> 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! >> > > -- 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 Fri Mar 31 11:25:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 1BAFF37BD6C for ; Fri, 31 Mar 2000 11:25:50 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 09A382CE64 for ; Fri, 31 Mar 2000 21:25:39 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id B7DAF1C5629; Fri, 31 Mar 2000 21:25:44 +0200 (EET) Date: Fri, 31 Mar 2000 21:25:44 +0200 From: Vallo Kallaste To: freebsd-current@freebsd.org Subject: Deadlock with vinum raid5 Message-ID: <20000331212544.A59295@myhakas.matti.ee> Reply-To: vallo@matti.ee Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Organization: =?UTF-8?Q?AS_Matti_B=C3=BCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I have four (4) ATA disks, all same new 20GB IBM 7200rpm models. Intel Seattle BX2 mobo, PIIX4 controller. I'm not expecting any performance increase or such, simply want to get my hands on. Ata driver, as the -current doesn't have wd anymore. I have raid5 volume laid over four disks, containing /usr filesystem, stripe unit size 256k. Machine deadlocks very reliably while doing ordinary buildworld, keyboard is responsive, network also but no disk I/O happens. I see syncer and bufdaemon in vrlock state; make, ln, syslogd and dhclient in flswait state. I usually don't see such states. Sources from which I built the system are todays, before I set up vinum. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 11:32:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 28B5337B652 for ; Fri, 31 Mar 2000 11:32:31 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA70873; Fri, 31 Mar 2000 21:32:23 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200003311932.VAA70873@freebsd.dk> Subject: Re: Deadlock with vinum raid5 In-Reply-To: <20000331212544.A59295@myhakas.matti.ee> from Vallo Kallaste at "Mar 31, 2000 09:25:44 pm" To: vallo@matti.ee Date: Fri, 31 Mar 2000 21:32:22 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Vallo Kallaste wrote: > Hi > > I have four (4) ATA disks, all same new 20GB IBM 7200rpm models. Intel > Seattle BX2 mobo, PIIX4 controller. I'm not expecting any performance > increase or such, simply want to get my hands on. Ata driver, as the > -current doesn't have wd anymore. > I have raid5 volume laid over four disks, containing /usr filesystem, > stripe unit size 256k. Machine deadlocks very reliably while doing > ordinary buildworld, keyboard is responsive, network also but no disk > I/O happens. I see syncer and bufdaemon in vrlock state; make, ln, > syslogd and dhclient in flswait state. I usually don't see such states. > Sources from which I built the system are todays, before I set up vinum. Yup, Greg and I know of this problem, it also happens with the wd driver and with CAM, so the problem is probably not the driver. I'm investigating this right now, and it looks like vinum is botching a struct buf in action somehow. -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 Mar 31 11:48:10 2000 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 A311937BA21 for ; Fri, 31 Mar 2000 11:48:05 -0800 (PST) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [149.173.6.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id OAA20835 for ; Fri, 31 Mar 2000 14:48:04 -0500 (EST) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA22180; Fri, 31 Mar 2000 14:47:34 -0500 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.1) id OAA22808; Fri, 31 Mar 2000 14:47:33 -0500 (EST) (envelope-from brdean) From: Brian Dean Message-Id: <200003311947.OAA22808@dean.pc.sas.com> Subject: Odd problem with ppp0 in -current To: freebsd-current@freebsd.org Date: Fri, 31 Mar 2000 14:47:33 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL61 (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, I'm trying to track down the change that broke my ppp. The symptoms are that I cannot telnet out though my ppp0 interface. Ktrace indicates that the connect() to the remote system never returns (it may eventually timeout - I didn't wait a really long time). However, I run natd and have several other boxes here that I _can_ use to establish a connection with a remote system, via my ppp0 interface (my gateway) . Very odd indeed. Does this ring a bell with anyone as far as what recent commit (last few days) might have resulted in such behaviour? My previous kernel of about a week ago is fine. Telnet works fine through my xl0 interface to my local machines. It's just my ppp0 interface that has this problem. Looking through the commit messages, I didn't see anything that jumped out as being the culprit. Any ideas? Is anyone else seeing this? For reference, this is with last night's cvs update, and kernel with IPFIREWALL, IPDIVERT, and natd. I use 'pppd' and 'ppp0'. Thanks, -Brian -- Brian Dean brdean@unx.sas.com bsd@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 Mar 31 11:49: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id 6FFF237B652 for ; Fri, 31 Mar 2000 11:48:58 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 12b7Pd-000NZj-0B; Fri, 31 Mar 2000 19:48:58 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA97055; Fri, 31 Mar 2000 20:53:09 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 31 Mar 2000 20:55:37 +0100 (BST) From: Doug Rabson To: Nikolai Saoukh Cc: freebsd-current@freebsd.org Subject: Re: kldload of driver for isa pnp card (cycle two) In-Reply-To: <20000331204620.A33493@Draculina.otdel-1.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 Fri, 31 Mar 2000, Nikolai Saoukh wrote: > Hot days of 4.0 preparation are behind. May be some > guru will find the solution for the subject? > > Two problems are here > > a) devices without driver attached to 'unknown' driver, thus > no orphan devices -- no reason to call device_probe method > from kldloaded driver. > > b) if disable 'unknown' driver as was recommended earlier, > device still consume resources, and this resources are not > presented to kldloaded driver -- resource leak. I will try to tackle these issues soon. Due to other commitments, this won't happen for a few days though. -- 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 Fri Mar 31 12: 7:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from Draculina.otdel-1.org (Draculina.Otdel-1.ORG [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id C019837BE70 for ; Fri, 31 Mar 2000 12:07:07 -0800 (PST) (envelope-from nms@otdel-1.org) Received: by Draculina.otdel-1.org (Postfix, from userid 1002) id 9DF5E167; Sat, 1 Apr 2000 00:06:54 +0400 (MSD) Date: Sat, 1 Apr 2000 00:06:54 +0400 From: Nikolai Saoukh To: Doug Rabson Cc: freebsd-current@freebsd.org Subject: Re: kldload of driver for isa pnp card (cycle two) Message-ID: <20000401000654.A34004@Draculina.otdel-1.org> References: <20000331204620.A33493@Draculina.otdel-1.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from dfr@nlsystems.com on Fri, Mar 31, 2000 at 08:55:37PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 31, 2000 at 08:55:37PM +0100, Doug Rabson wrote: > I will try to tackle these issues soon. Due to other commitments, this > won't happen for a few days though. Can I halp somehow? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 13: 0:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from Draculina.otdel-1.org (Draculina.Otdel-1.ORG [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id 5360E37BA3B; Fri, 31 Mar 2000 13:00:15 -0800 (PST) (envelope-from nms@otdel-1.org) Received: by Draculina.otdel-1.org (Postfix, from userid 1002) id 1DEC1167; Sat, 1 Apr 2000 00:59:29 +0400 (MSD) Date: Sat, 1 Apr 2000 00:59:28 +0400 From: Nikolai Saoukh To: dfr@freebsd.org Cc: freebsd-current@freebsd.org Subject: io memory requests from pnp devices lands in video bios Message-ID: <20000401005928.A34356@Draculina.otdel-1.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It has the internal identification `kern/17715'. > The individual assigned to look at your > report is: freebsd-bugs. > > >Category: kern > >Responsible: freebsd-bugs > >Synopsis: io memory requests from pnp devices lands in video bios > >Arrival-Date: Fri Mar 31 12:50:01 PST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 13:12:19 2000 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 18E3937B93A for ; Fri, 31 Mar 2000 13:12:16 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA55839; Fri, 31 Mar 2000 13:12:15 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id NAA18171; Fri, 31 Mar 2000 13:12:02 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200003312112.NAA18171@whistle.com> Subject: Re: Neat kernel development environment. In-Reply-To: <5391.954530417@critter.freebsd.dk> from Poul-Henning Kamp at "Mar 31, 2000 09:20:17 pm" To: Poul-Henning Kamp Date: Fri, 31 Mar 2000 13:12:02 -0800 (PST) Cc: Julian Elischer , Matthew Dillon , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 Poul-Henning Kamp writes: | In message , Julian El | ischer writes: | | >Oh? can you run a kernel in a jail for debugging? | | No, not quite yet, but what IBM bragged about the 41k linuxes for | was for what jails do for you. Nope not quite. Since you could actually crash the kernel in the VM/Linux session and the others are still going. Crash the kernel in a jail and all sessions are toast. Note I do like jail on FreeBSD one thing that would be nice with jail is if the IP address for the jail disappeared from the non-jail machine. For example sendmail doesn't like to send mail to the jail session if it sees the jail's IP is one of its own IPs. Sort of like, I'm already there why bother and it could cause mail looping under mis-configuration. This isn't a problem for the IBM type solution or vmware. Then with IBM the machine can disable a bad CPU and call home for a fix. None of the session are bothered (except performance) assuming you have more then one CPU working. Maybe we heard different bragging. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 13:59:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 30B0737BA58 for ; Fri, 31 Mar 2000 13:59:35 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id PAA26407; Fri, 31 Mar 2000 15:59:23 -0600 (CST) Date: Fri, 31 Mar 2000 15:59:23 -0600 From: "Matthew D. Fuller" To: Brad Knowles Cc: Matthew Dillon , Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: SMP buildworld times / performance tests Message-ID: <20000331155923.F10480@futuresouth.com> References: <200003300604.WAA68031@apollo.backplane.com> <20000330174453.D10480@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 31, 2000 at 12:24:27PM +0200, a little birdie told me that Brad Knowles remarked > At 5:44 PM -0600 2000/3/30, Matthew D. Fuller wrote: > > > Does softupdates provide faster performance than async/noatime? I keep > > /usr/src and /usr/obj as such, would it be faster with softupdates? And > > if so, why? > > Of course, once you ask this question, the next logical one that > follows is "what happens if you do all three?" TTBOMK, nothing, as softupdates will override the other two. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 15:42: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 51F4A37BA58 for ; Fri, 31 Mar 2000 15:41:59 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA51813; Sat, 1 Apr 2000 09:11:40 +0930 (CST) Date: Sat, 1 Apr 2000 09:11:40 +0930 From: Greg Lehey To: Soren Schmidt Cc: vallo@matti.ee, freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000401091140.A51727@freebie.lemis.com> References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0pre2i In-Reply-To: <200003311932.VAA70873@freebsd.dk> 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, 31 March 2000 at 21:32:22 +0200, Søren Schmidt wrote: > It seems Vallo Kallaste wrote: >> Hi >> >> I have four (4) ATA disks, all same new 20GB IBM 7200rpm models. Intel >> Seattle BX2 mobo, PIIX4 controller. I'm not expecting any performance >> increase or such, simply want to get my hands on. Ata driver, as the >> -current doesn't have wd anymore. >> I have raid5 volume laid over four disks, containing /usr filesystem, >> stripe unit size 256k. Machine deadlocks very reliably while doing >> ordinary buildworld, keyboard is responsive, network also but no disk >> I/O happens. I see syncer and bufdaemon in vrlock state; make, ln, >> syslogd and dhclient in flswait state. I usually don't see such states. >> Sources from which I built the system are todays, before I set up vinum. > > Yup, Greg and I know of this problem, it also happens with the wd > driver and with CAM, so the problem is probably not the driver. > I'm investigating this right now, and it looks like vinum is > botching a struct buf in action somehow. I'm not sure that this is the same problem. Please supply the information I ask for in http://www.lemis.com/vinum/how-to-debug.html. The problem that Søren and I are looking at is usually a panic. We don't really know where it's happening, but we're each sure it's not in *our* code :-) From a Vinum standpoint, it happens between the time that Vinum sends a request to the driver and when the I/O completes, so it's difficult to blame Vinum. On the other hand, we've seen it with SCSI as well, so it's difficult to blame the driver. I'm half guessing that it's something else altogether which is spamming freed data. Vinum mallocs the buffer headers rather than using geteblk(), which could explain why it happens only with Vinum. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 16:37:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id AC09A37B6EE for ; Fri, 31 Mar 2000 16:37:50 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA35356; Fri, 31 Mar 2000 16:37:44 -0800 (PST) (envelope-from dillon) Date: Fri, 31 Mar 2000 16:37:44 -0800 (PST) From: Matthew Dillon Message-Id: <200004010037.QAA35356@apollo.backplane.com> To: Greg Lehey Cc: Soren Schmidt , vallo@matti.ee, freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm not sure that this is the same problem. Please supply the :information I ask for in http://www.lemis.com/vinum/how-to-debug.html. : :The problem that Søren and I are looking at is usually a panic. We :don't really know where it's happening, but we're each sure it's not :in *our* code :-) From a Vinum standpoint, it happens between the time :that Vinum sends a request to the driver and when the I/O completes, :so it's difficult to blame Vinum. On the other hand, we've seen it :with SCSI as well, so it's difficult to blame the driver. I'm half :guessing that it's something else altogether which is spamming freed :data. Vinum mallocs the buffer headers rather than using geteblk(), :which could explain why it happens only with Vinum. : :Greg The business about vinum malloc()ing the buffer header has always bothered me, maybe we should introduce an 'allocpbuf' call (and 'freepbuf') to complement the getpbuf()/relpbuf() routines we already have to take this out of the hands of the device driver. -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 Mar 31 16:42:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 901E237B690 for ; Fri, 31 Mar 2000 16:42:23 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA52417; Sat, 1 Apr 2000 10:11:59 +0930 (CST) Date: Sat, 1 Apr 2000 10:11:59 +0930 From: Greg Lehey To: Matthew Dillon Cc: Soren Schmidt , vallo@matti.ee, freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000401101159.E51727@freebie.lemis.com> References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <200004010037.QAA35356@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0pre2i In-Reply-To: <200004010037.QAA35356@apollo.backplane.com> 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, 31 March 2000 at 16:37:44 -0800, Matthew Dillon wrote: > >> I'm not sure that this is the same problem. Please supply the >> information I ask for in http://www.lemis.com/vinum/how-to-debug.html. >> >> The problem that Søren and I are looking at is usually a panic. We >> don't really know where it's happening, but we're each sure it's not >> in *our* code :-) From a Vinum standpoint, it happens between the time >> that Vinum sends a request to the driver and when the I/O completes, >> so it's difficult to blame Vinum. On the other hand, we've seen it >> with SCSI as well, so it's difficult to blame the driver. I'm half >> guessing that it's something else altogether which is spamming freed >> data. Vinum mallocs the buffer headers rather than using geteblk(), >> which could explain why it happens only with Vinum. > > The business about vinum malloc()ing the buffer header has > always bothered me, maybe we should introduce an 'allocpbuf' > call (and 'freepbuf') to complement the getpbuf()/relpbuf() > routines we already have to take this out of the hands of the > device driver. Seems good to me. I thought of a few alternatives as well. But if this is a problem with some other process nuking data which has since been freed, this will just drive the problem into hiding. The most obvious alternative would be for Vinum to use geteblk() after all and use b_caller1 to point to the rest of the information; but it would still need to be malloced. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 18: 0:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by hub.freebsd.org (Postfix) with ESMTP id ED92437B690 for ; Fri, 31 Mar 2000 18:00:03 -0800 (PST) (envelope-from cattelan@thebarn.com) Received: from thebarn.com (dialin5.lcse.umn.edu [160.94.231.37]) by lips.borg.umn.edu (8.10.0/8.10.0) with ESMTP id e311xu382792; Fri, 31 Mar 2000 19:59:56 -0600 (CST) Message-ID: <38E5581B.57215AED@thebarn.com> Date: Fri, 31 Mar 2000 19:59:55 -0600 From: Russell Cattelan X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: wpaul@ctr.columbia.edu Cc: freebsd-current@freebsd.org Subject: Strange problem with Wavelan card. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just go two new wavelan cards. The drivers comes up and the interface is there but these messages keep appearing. No traffic seems to get through. FreeBSD lupo.thebarn.com 4.0-STABLE FreeBSD 4.0-STABLE #6: Thu Mar 30 23:15:22 CST 2000 cattelan@lupo.thebarn.com:/export/cyan/src/sys/compile/LUPO i386 Tried loading the driver as a module and statically compiled in the kernel... same result. Any ideas? Mar 30 23:45:22 lupo pccard:wi0: WaveLAN/IEEE inserted Mar 30 23:45:22 lupo pccardd[334]: pccardd started Mar 30 23:45:57 lupo /kernel: wi0: tx buffer allocation failed Mar 30 23:45:57 lupo /kernel: wi0: starting DAD for fe80:000c::0260:1dff:fe1d :3848 Mar 30 23:45:57 lupo /kernel: wi0: xmit failed Mar 30 23:45:57 lupo routed[85]: possible netmask problem between wi0:10.0.0. 0/8 and xl0:10.0.0.0/24 Mar 30 23:45:58 lupo /kernel: wi0: DAD complete for fe80:000c::0260:1dff:fe1d :3848 - no duplicates found Mar 30 23:46:00 lupo /kernel: wi0: tx buffer allocation failed Mar 30 23:46:00 lupo /kernel: wi0: xmit failed Mar 30 23:46:04 lupo /kernel: wi0: device timeout Mar 30 23:46:04 lupo /kernel: wi0: tx buffer allocation failed Mar 30 23:46:07 lupo /kernel: wi0: xmit failed Mar 30 23:46:12 lupo /kernel: wi0: device timeout Mar 30 23:46:12 lupo /kernel: wi0: tx buffer allocation failed Mar 30 23:53:32 lupo /kernel: wi0: tx buffer allocation failed Mar 30 23:53:32 lupo /kernel: wi0: xmit failed Mar 30 23:53:36 lupo /kernel: wi0: device timeout Mar 30 23:53:36 lupo /kernel: wi0: tx buffer allocation failed Mar 30 23:53:38 lupo /kernel: wi0: xmit failed Mar 30 23:53:43 lupo /kernel: wi0: device timeout Mar 30 23:53:43 lupo /kernel: wi0: tx buffer allocation failed Mar 30 23:53:47 lupo /kernel: wi0: xmit failed Mar 30 23:53:52 lupo /kernel: wi0: device timeout Mar 30 23:53:52 lupo /kernel: wi0: tx buffer allocation failed Mar 30 23:54:19 lupo /kernel: pid 85 (routed), uid 0: exited on signal 11 (co re dumped) Mar 30 23:54:19 lupo /kernel: wi0: xmit failed Mar 30 23:54:24 lupo /kernel: wi0: device timeout Mar 30 23:54:24 lupo /kernel: wi0: tx buffer allocation failed -- Russell Cattelan cattelan@thebarn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 18:10: 4 2000 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 DB49237B87B for ; Fri, 31 Mar 2000 18:09:58 -0800 (PST) (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.3) with ESMTP id SAA00356 for ; Fri, 31 Mar 2000 18:09:57 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id SAA11169 for current@freebsd.org; Fri, 31 Mar 2000 18:09:57 -0800 (PST) (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: Fri, 31 Mar 2000 18:09:57 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: current@freebsd.org Subject: RSAREF in make.conf Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This can be deleted from "src/etc/defaults/make.conf" now, right? I can't find any uses of it in the tree. # To tell the base system that you are using RSAREF (from ports). # (This needs revisiting) - it is very likely that this is too # heavily tied to USA_RESIDENT==YES. #RSAREF= YES John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 18:28:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id D231337BAA8 for ; Fri, 31 Mar 2000 18:28:44 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (reyim.ne.mediaone.net [24.218.251.241]) by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id VAA03764; Fri, 31 Mar 2000 21:28:35 -0500 (EST) Message-ID: <38E55ED2.6A41C3DD@acm.org> Date: Fri, 31 Mar 2000 21:28:34 -0500 From: Jim Bloom X-Mailer: Mozilla 4.72 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dirk Roehrdanz Cc: current@FreeBSD.ORG Subject: Re: RSA library problems References: <38DA4E03.CB2E84A8@originative.co.uk> <20000331122424.A19141@diroxfbsd.dx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A similar patch was added for the USA version of RSA for the same basic reason. Your patch is almost correct. It should add the line: LDADD+= -L$[.OBJDIR]/../libcrypto -lcrypto Your version would reference the system crypto library and not the one being built as part of buildworld. Jim Bloom bloom@acm.org Dirk Roehrdanz wrote: > > I had the same problem. "BN_mod_exp_mont" is in libcrypto,but isn't > visible from librsaINTL.so because libcrypto is loaded in conjunction > with the load of /usr/local/libexec/apache/libssl.so via dlopen() . > The man page to dlopen states " The symbols exported by objects added > to the address space by dlopen() can be accessed only through calls > to dlsym()". > I have solved the problem with the attached patch. It adds libcrypto > to the list of linked libs. > Maybe there is a better solution,who knows ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 18:48: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from netserver.pth.com (fx3-1-125.mgfairfax.rr.com [24.28.200.125]) by hub.freebsd.org (Postfix) with ESMTP id 4763E37B7F0; Fri, 31 Mar 2000 18:47:45 -0800 (PST) (envelope-from paul@pth.com) Received: from dell.pth.com ([192.42.172.11] helo=dell) by netserver.pth.com with smtp (Exim 3.13 #1) id 12bDwQ-0006Jc-00; Fri, 31 Mar 2000 21:47:14 -0500 Message-ID: <008501bf9b84$ad365270$0bac2ac0@pth.com> From: "Paul Haddad" To: "Christopher Masto" Cc: , References: <200003220051.IAA23805@bandicoot.prth.tensor.pgs.com> <38D837AA.A93FF73B@originative.co.uk> <20000322001604.A26234@netmonger.net> Subject: Re: Another current crash (cvs-cur.6183 Date: Fri, 31 Mar 2000 21:47:53 -0500 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.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Boy I wish I had read this message before I went out and bought a USB zip drive... I'm in the exact same situation IOPENER with 4.0 installed and screwed up to a point where I can boot but not mount the sandisk drive. I figured that I would get a zip drive and mount it instead. Anyways if you found some way around this please let me know, otherwise I've got to make another trip out and get a SuperDisk instead... BTW What state are you in? Mine will boot, but gets to the point where it tries to mount the sandisk and panics with a ffs_write panic. Booting in single user doesn't help. --- Paul Haddad (paul@pth.com) Imagine that Cray computer decides to make a personal computer. It has a 150 MHz processor, 200 megabytes of RAM, 1500 megabytes of disk storage, a screen resolution of 4096 x 4096 pixels, relies entirely on voice recognition for input, fits in your shirt pocket and costs $300. What's the first question that the computer community asks? "Is it PC compatible?" ----- Original Message ----- From: "Christopher Masto" To: "Paul Richards" ; "Stephen Hocking-Senior Programmer PGS SPS Perth" Cc: ; Sent: Wednesday, March 22, 2000 12:16 AM Subject: Re: Another current crash (cvs-cur.6183 > On Wed, Mar 22, 2000 at 03:02:02AM +0000, Paul Richards wrote: > > I've got a different but I think related panic. > > > > #9 0xc0143280 in panic (fmt=0xc0250460 "vm_page_wakeup: page not > > busy!!!") > > at ../../kern/kern_shutdown.c:552 > > #10 0xc01df583 in swp_pager_async_iodone (bp=0xc3236250) > > at ../../vm/vm_page.h:346 > > I've been playing around with one of those iopener things and got > myself into a state I thought I could get out of with the help of a > USB Zip drive. Unfortunately, upon purchasing and connecting one, > I discovered that I can't access it without a panic, which I > point out here on the chance it's also related. > > #7 0xc024ac2c in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, > tf_edi = -1018879976, tf_esi = 256, tf_ebp = -919618472, tf_isp = -919618500, > tf_ebx = -1071201278, tf_edx = 0, tf_ecx = -1070746656, tf_eax = 18, > tf_trapno = 3, tf_err = 0, tf_eip = -1071396739, tf_cs = 8, tf_eflags = 582, > tf_esp = -1071099905, tf_ss = -1071212893}) at ../../i386/i386/trap.c:549 > #8 0xc023c87d in Debugger (msg=0xc02696a3 "panic") at machine/cpufunc.h:64 > #9 0xc01549e8 in panic (fmt=0xc026c402 "allocbuf: buffer too small") > at ../../kern/kern_shutdown.c:552 > #10 0xc0178f5a in allocbuf (bp=0xc3452018, size=83886080) at ../../kern/vfs_bio.c:2346 > #11 0xc0178f01 in geteblk (size=83886080) at ../../kern/vfs_bio.c:2315 > #12 0xc025cb57 in dsinit (dev=0xc0be1e00, lp=0xc0c490f4, sspp=0xc0c490f0) > at ../../kern/subr_diskmbr.c:186 > #13 0xc015eec6 in dsopen (dev=0xc0be1e00, mode=8192, flags=0, sspp=0xc0c490f0, > lp=0xc0c490f4) at ../../kern/subr_diskslice.c:683 > #14 0xc015dfbf in diskopen (dev=0xc0be1e00, oflags=1, devtype=8192, p=0xc88be860) > at ../../kern/subr_disk.c:146 > #15 0xc018ae65 in spec_open (ap=0xc92fbe10) at ../../miscfs/specfs/spec_vnops.c:191 > #16 0xc018ad65 in spec_vnoperate (ap=0xc92fbe10) > at ../../miscfs/specfs/spec_vnops.c:117 > #17 0xc01ff2e9 in ufs_vnoperatespec (ap=0xc92fbe10) at ../../ufs/ufs/ufs_vnops.c:2301 > #18 0xc018595f in vn_open (ndp=0xc92fbedc, fmode=1, cmode=0) at vnode_if.h:189 > #19 0xc0181951 in open (p=0xc88be860, uap=0xc92fbf80) at ../../kern/vfs_syscalls.c:994 > #20 0xc024b4ce in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, > tf_edi = -1077937212, tf_esi = 134894800, tf_ebp = -1077937132, > tf_isp = -919617580, tf_ebx = 0, tf_edx = 8, tf_ecx = 134894828, tf_eax = 5, > tf_trapno = 12, tf_err = 2, tf_eip = 672026540, tf_cs = 31, tf_eflags = 642, > tf_esp = -1077937316, tf_ss = 47}) at ../../i386/i386/trap.c:1073 > #21 0xc023cf26 in Xint0x80_syscall () > > I'm not intimately familiar with the function involved, and I'm out of > time tonight, so I'm backing up a few days to see if it goes away. > -- > Christopher Masto Senior Network Monkey NetMonger Communications > chris@netmonger.net info@netmonger.net http://www.netmonger.net > > Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ > > > 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 Mar 31 19:23:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from friley-160-236.res.iastate.edu (friley-160-236.res.iastate.edu [129.186.160.236]) by hub.freebsd.org (Postfix) with ESMTP id 5998237B87B for ; Fri, 31 Mar 2000 19:23:34 -0800 (PST) (envelope-from patrick@137.org) Received: from friley-160-236.res.iastate.edu (localhost [127.0.0.1]) by friley-160-236.res.iastate.edu (Postfix) with ESMTP id A42F51D4 for ; Fri, 31 Mar 2000 21:23:24 -0600 (CST) To: freebsd-current@freebsd.org Subject: Panic in pmap_enter Date: Fri, 31 Mar 2000 21:23:24 -0600 From: Patrick Hartling Message-Id: <20000401032324.A42F51D4@friley-160-236.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I rebuilt my -current system this morning and am now getting paincs with both the SMP and non-SMP kernels. The current panic with a uniprocessor kernel is: panic: pmap_enter: invalid page directory, pdir=0, va=0xc0da0000 It occurs right after the output for pci0. I'm currently sitting at the db> prompt with this kernel. With an SMP kernel, I get the following at the same point in the boot process: panic: pmap_enter: invalid page directory, pdir=0, va=0xc0da3000 mp_lock=00000023; cpuid=0; Fatal trap 12: page fault while in kernel mode mp_lock=00000024; cpuid=0; This is with sources cvsup'd around 8:30 am CST today (3/31). I can still boot my old kernel (from 3/26), but I get a panic in ifconfig when my Ethernet card (an onboard Intel EtherExpress Pro 10/100) is configured, so it's not easy for me to get working sources or newer changes. Has anyone else seen this? I haven't seen much email today because my -current machine is where I normally get my mail. :( -Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 19:59:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9D26337B87B for ; Fri, 31 Mar 2000 19:59:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA36352; Fri, 31 Mar 2000 19:58:51 -0800 (PST) (envelope-from dillon) Date: Fri, 31 Mar 2000 19:58:51 -0800 (PST) From: Matthew Dillon Message-Id: <200004010358.TAA36352@apollo.backplane.com> To: Patrick Hartling Cc: freebsd-current@FreeBSD.ORG Subject: Re: Panic in pmap_enter References: <20000401032324.A42F51D4@friley-160-236.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I rebuilt my -current system this morning and am now getting paincs with :both the SMP and non-SMP kernels. The current panic with a uniprocessor :kernel is: : :panic: pmap_enter: invalid page directory, pdir=0, va=0xc0da0000 : :It occurs right after the output for pci0. I'm currently sitting at the db> :prompt with this kernel. : :With an SMP kernel, I get the following at the same point in the boot :process: : :panic: pmap_enter: invalid page directory, pdir=0, va=0xc0da3000 This usually happens when you set kernel resource options that are too high. If you are setting kernel resource options, try commenting them out. To get your old kernel to boot you may have to remove your ethernet card. :I can still boot my old kernel (from 3/26), but I get a panic in ifconfig :when my Ethernet card (an onboard Intel EtherExpress Pro 10/100) is :configured, so it's not easy for me to get working sources or newer changes. :Has anyone else seen this? I haven't seen much email today because my :-current machine is where I normally get my mail. :( : : -Patrick You can boot the kernel into single user mode. Interrupt the FreeBSD boot sequence by hitting space, then (typically) type 'boot /kernel -s' (specify a path to your working kernel if not /kernel). -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 Mar 31 20:19:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from friley-160-236.res.iastate.edu (friley-160-236.res.iastate.edu [129.186.160.236]) by hub.freebsd.org (Postfix) with ESMTP id 7B1B737B6D9 for ; Fri, 31 Mar 2000 20:19:36 -0800 (PST) (envelope-from patrick@137.org) Received: from friley-160-236.res.iastate.edu (localhost [127.0.0.1]) by friley-160-236.res.iastate.edu (Postfix) with ESMTP id 2978E1D4; Fri, 31 Mar 2000 22:19:34 -0600 (CST) Reply-To: Patrick Hartling To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Panic in pmap_enter In-reply-to: Message from Matthew Dillon of "Fri, 31 Mar 2000 19:58:51 PST." <200004010358.TAA36352@apollo.backplane.com> Date: Fri, 31 Mar 2000 22:19:34 -0600 From: Patrick Hartling Message-Id: <20000401041935.2978E1D4@friley-160-236.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :I rebuilt my -current system this morning and am now getting paincs with > :both the SMP and non-SMP kernels. The current panic with a uniprocessor > :kernel is: > : > :panic: pmap_enter: invalid page directory, pdir=0, va=0xc0da0000 > : > :It occurs right after the output for pci0. I'm currently sitting at the db> > :prompt with this kernel. > : > :With an SMP kernel, I get the following at the same point in the boot > :process: > : > :panic: pmap_enter: invalid page directory, pdir=0, va=0xc0da3000 > > This usually happens when you set kernel resource options that are > too high. If you are setting kernel resource options, try commenting > them out. Well, I did recently add options for shared memory settings to get XFree86 4.0 working better. It hadn't caused any problems until now though. I just tried commenting out those options and recompiling, but I still get the panic. > To get your old kernel to boot you may have to remove your ethernet card. That's not an option. ;) I am, however, using the if_fxp module instead of compiling the driver into the kernel, so I can avoid loading the module. > :I can still boot my old kernel (from 3/26), but I get a panic in ifconfig > :when my Ethernet card (an onboard Intel EtherExpress Pro 10/100) is ^^^^^^^ > :configured, so it's not easy for me to get working sources or newer changes. > :Has anyone else seen this? I haven't seen much email today because my > :-current machine is where I normally get my mail. :( > : > : -Patrick > > You can boot the kernel into single user mode. Interrupt the FreeBSD > boot sequence by hitting space, then (typically) type 'boot /kernel -s' > (specify a path to your working kernel if not /kernel). Yes, I know how to get into single-user mode and how to choose kernels at boot time. I was a bit vague in what I was trying to do with my old kernel. Sorry for any confusion. -Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 21:46:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from friley-160-236.res.iastate.edu (friley-160-236.res.iastate.edu [129.186.160.236]) by hub.freebsd.org (Postfix) with ESMTP id 8C4FC37B6EE for ; Fri, 31 Mar 2000 21:46:47 -0800 (PST) (envelope-from patrick@137.org) Received: from friley-160-236.res.iastate.edu (localhost [127.0.0.1]) by friley-160-236.res.iastate.edu (Postfix) with ESMTP id 246611DF; Fri, 31 Mar 2000 23:46:45 -0600 (CST) To: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: Panic in pmap_enter In-reply-to: Message from Patrick Hartling of "Fri, 31 Mar 2000 22:19:34 CST." <20000401041935.2978E1D4@friley-160-236.res.iastate.edu> Date: Fri, 31 Mar 2000 23:46:45 -0600 From: Patrick Hartling Message-Id: <20000401054646.246611DF@friley-160-236.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patrick Hartling wrote: > Matthew Dillon wrote: > > :I rebuilt my -current system this morning and am now getting paincs with > > :both the SMP and non-SMP kernels. The current panic with a uniprocessor > > :kernel is: > > : > > :panic: pmap_enter: invalid page directory, pdir=0, va=0xc0da0000 > > : > > :It occurs right after the output for pci0. I'm currently sitting at the d > b> > > :prompt with this kernel. > > : > > :With an SMP kernel, I get the following at the same point in the boot > > :process: > > : > > :panic: pmap_enter: invalid page directory, pdir=0, va=0xc0da3000 > > > > This usually happens when you set kernel resource options that are > > too high. If you are setting kernel resource options, try commenting > > them out. > > Well, I did recently add options for shared memory settings to get XFree86 > 4.0 working better. It hadn't caused any problems until now though. I just > tried commenting out those options and recompiling, but I still get the > panic. Revision 1.5 of sys/isa/pnpparse.c has fixed my problems, and I didn't have to give up the shared memory options. It was acquired through the magic of cvsweb and copied over via a floppy. :) What a day. -Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 31 22:21:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 895AE37BB5B for ; Fri, 31 Mar 2000 22:21:50 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA36923; Fri, 31 Mar 2000 22:21:35 -0800 (PST) (envelope-from dillon) Date: Fri, 31 Mar 2000 22:21:35 -0800 (PST) From: Matthew Dillon Message-Id: <200004010621.WAA36923@apollo.backplane.com> To: Patrick Hartling Cc: freebsd-current@FreeBSD.ORG Subject: Re: Panic in pmap_enter References: <20000401054646.246611DF@friley-160-236.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Revision 1.5 of sys/isa/pnpparse.c has fixed my problems, and I didn't have :to give up the shared memory options. It was acquired through the magic of :cvsweb and copied over via a floppy. :) What a day. : : -Patrick Ah, excellent. P.S. word to the wise even though this wasn't your problem this time: modules and -current don't mix, if you get out of sync you usually wind up crashing the system. I usually compile everything I use into -current kernels directly. -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 Mar 31 23:51:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E595D37BCFF for ; Fri, 31 Mar 2000 23:51:25 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA48796; Sat, 1 Apr 2000 09:51:02 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004010751.JAA48796@freebsd.dk> Subject: Re: Deadlock with vinum raid5 In-Reply-To: <20000401091140.A51727@freebie.lemis.com> from Greg Lehey at "Apr 1, 2000 09:11:40 am" To: grog@lemis.com (Greg Lehey) Date: Sat, 1 Apr 2000 09:51:02 +0200 (CEST) Cc: vallo@matti.ee, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Greg Lehey wrote: > > The problem that Søren and I are looking at is usually a panic. We > don't really know where it's happening, but we're each sure it's not > in *our* code :-) From a Vinum standpoint, it happens between the time > that Vinum sends a request to the driver and when the I/O completes, > so it's difficult to blame Vinum. On the other hand, we've seen it > with SCSI as well, so it's difficult to blame the driver. I'm half > guessing that it's something else altogether which is spamming freed > data. Vinum mallocs the buffer headers rather than using geteblk(), > which could explain why it happens only with Vinum. It happens also with the wd driver, so its 3 drivers against one :) What seems to be happening is that *something* is corrupting the buf structure, or the pointer to it. What I see in most cases is that the buf structure I get in adstrategy has gotten some of its fields changed when I get to work on it in ad_start. That should _not_ be happening, and doesn't when vinum is not involved. Somehow I think that vinums shuffleing around with buf's and copies of them at some point gets confused. I'm still instrumenting my kernel to locate where it happens, and I havn't got anything definite yet... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 4:12:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhost.netbenefit.co.uk (mailhost.netbenefit.co.uk [212.53.64.39]) by hub.freebsd.org (Postfix) with ESMTP id 999DB37B5D8 for ; Sat, 1 Apr 2000 04:12:22 -0800 (PST) (envelope-from pierre.dampure@k2c.co.uk) Received: from [62.188.17.29] (helo=bladerunner.k2c.co.uk) by mailhost.netbenefit.co.uk with esmtp (NetBenefit 1.5) id 12bMl6-00050I-00 for current@freebsd.org; Sat, 01 Apr 2000 13:12:08 +0100 Received: (from dampurep@localhost) by bladerunner.k2c.co.uk (8.9.3/8.9.3) id NAA00316; Sat, 1 Apr 2000 13:12:14 +0100 (BST) (envelope-from pierre.dampure@k2c.co.uk) Date: Sat, 1 Apr 2000 13:12:14 +0100 (BST) Message-Id: <200004011212.NAA00316@bladerunner.k2c.co.uk> X-Authentication-Warning: bladerunner.k2c.co.uk: dampurep set sender to dampurep@bladerunner.k2c.co.uk using -f From: "Pierre Y. Dampure" To: current@freebsd.org Subject: PNP dependant configs in /sys/isa/pnpparse.c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since revision 1.5 of the above, my kernel is giving me a "too many dependant configs (8)" when probing PNP resources. Problem is, it looks like the SoundBlaster AWE 64 Gold advertises 8 different PNP configurations (at least, that's what I got when i bumped MAXDEP to 16 and rebooted in verbose mode). Is there a set limit to the number of PNP configurations that can be advertised? if it's indeed 8, shouldn't the test read: if (ncfgs > MAXDEP) { rather than if (ncfgs >= MAXDEP) { Comments appreciated... PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 10:28:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from gatekeep.ti.com (gatekeep.ti.com [192.94.94.61]) by hub.freebsd.org (Postfix) with ESMTP id 8615937B8AF for ; Sat, 1 Apr 2000 10:28:11 -0800 (PST) (envelope-from ntakpe@ffab.tide.ti.com) Received: from dlep7.itg.ti.com ([157.170.134.103]) by gatekeep.ti.com (8.10.0/8.10.0) with ESMTP id e31ISAj05523 for ; Sat, 1 Apr 2000 12:28:10 -0600 (CST) Received: from dlep7.itg.ti.com (localhost [127.0.0.1]) by dlep7.itg.ti.com (8.9.3/8.9.3) with ESMTP id MAA01852 for ; Sat, 1 Apr 2000 12:28:05 -0600 (CST) Received: from wrks2host.ffab.tide.ti.com (wrks2host.ffab.tide.ti.com [137.167.200.37]) by dlep7.itg.ti.com (8.9.3/8.9.3) with ESMTP id MAA01848 for ; Sat, 1 Apr 2000 12:28:04 -0600 (CST) Received: from ishtar.ffab.tide.ti.com (ishtar.ffab.tide.ti.com [137.167.193.220]) by wrks2host.ffab.tide.ti.com (8.8.8+Sun/8.8.8) with ESMTP id UAA23354 for ; Sat, 1 Apr 2000 20:28:06 +0200 (MET DST) Received: (from ntakpe@localhost) by ishtar.ffab.tide.ti.com (8.9.3/8.9.3) id UAA02631 for current@FreeBSD.ORG; Sat, 1 Apr 2000 20:28:05 +0200 From: Jean Louis Ntakpe Message-Id: <200004011828.UAA02631@ishtar.ffab.tide.ti.com> Subject: No loopback configured To: current@FreeBSD.ORG Date: Sat, 1 Apr 2000 20:28:04 +0200 (CEST) X-Mailer: ELM [version 2.5 PL1] 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, I've removed all Ethernet NICs from my kernel konfiguration and used only kernel modules. No loopback device is configured. I reconfigured my kernel with at least one Ethernet NIC entry and the loopback device is back. I'm also getting kernel panic if "options BRIDGE" is configured. I'll try to submit more verbose log. regards, Jean Louis Ntakpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 11:14:16 2000 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 6D44837C35E; Sat, 1 Apr 2000 11:14:10 -0800 (PST) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [149.173.6.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id OAA17513; Sat, 1 Apr 2000 14:14:08 -0500 (EST) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA07758; Sat, 1 Apr 2000 14:13:38 -0500 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.1) id OAA29276; Sat, 1 Apr 2000 14:13:38 -0500 (EST) (envelope-from brdean) From: Brian Dean Message-Id: <200004011913.OAA29276@dean.pc.sas.com> Subject: Re: Odd problem with ppp0 in -current In-Reply-To: <200003311947.OAA22808@dean.pc.sas.com> from Brian Dean at "Mar 31, 2000 02:47:33 pm" To: freebsd-current@freebsd.org Date: Sat, 1 Apr 2000 14:13:38 -0500 (EST) Cc: jlemon@freebsd.org X-Mailer: ELM [version 2.4ME+ PL61 (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 Just to follow up - this has been tracked down and fixed. The recent delayed checksum code was not compatible with IPDIVERT. Thanks for the fix, Jonathan! -Brian Brian Dean wrote: > The symptoms are that I cannot telnet out though my ppp0 interface. > Ktrace indicates that the connect() to the remote system never returns > (it may eventually timeout - I didn't wait a really long time). > However, I run natd and have several other boxes here that I _can_ use > to establish a connection with a remote system, via my ppp0 interface > (my gateway) . Very odd indeed. Does this ring a bell with anyone as > far as what recent commit (last few days) might have resulted in such > behaviour? [...] > For reference, this is with last night's cvs update, and kernel with > IPFIREWALL, IPDIVERT, and natd. I use 'pppd' and 'ppp0'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 12:57:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (Postfix) with ESMTP id 72E4B37B655 for ; Sat, 1 Apr 2000 12:57:00 -0800 (PST) (envelope-from kent@lab1.tfd.com) Received: from lab1.tfd.com (lab1.tfd.com [10.9.200.31]) by rtp.tfd.com (8.9.3/8.9.3) with SMTP id PAA06275 for ; Sat, 1 Apr 2000 15:57:30 -0500 (EST) Received: by lab1.tfd.com id AA24992 (5.67b/IDA-1.5 for current@freebsd.org); Sat, 1 Apr 2000 15:54:57 -0500 Date: Sat, 1 Apr 2000 15:54:57 -0500 From: Kent Hauser Message-Id: <200004012054.AA24992@lab1.tfd.com> To: current@freebsd.org Subject: no audio with newpcm driver on TP600E Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm having problems with the newpcm driver. Basically, I can't get audio from the speakers. This while trying to play a cd. The output of mixer looks reasonable. Hardware is a ThinkPad 600E. "audio" portions of the config attached along with the output of dmesg. Help would be greatly appreciated. Thanks, Kent =============== # For PnP/PCI sound cards #device pcm #device sbc #device csa # For non-PnP cards: device pcm0 at isa? irq 10 drq 1 flags 0x0 device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x15 device csa device gusc0 at isa? port 0x220 irq 5 drq 1 flags 0x13 # Not controlled by `snd' device pca0 at isa? port IO_TIMER1 device matcd0 at isa? port 0x230 ============= Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-20000331-SNAP #5: Sat Apr 1 20:32:28 GMT 2000 kent@kent.tfd.com:/usr/src/sys/compile/TP Calibrating clock(s) ... TSC clock: 297777462 Hz, i8254 clock: 1193150 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Pentium II Xeon/Celeron (297.79-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 66912256 (65344K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x003ce000 - 0x03fc7fff, 62889984 bytes (15354 pages) avail memory = 61317120 (59880K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fd800 bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x0 pnpbios: Found PnP BIOS data at 0xc00fe700 pnpbios: Entry = f0000:e724 Rev = 1.0 pnpbios: Event flag at 415 Other BIOS signatures found: ACPI: 000fd6e0 Preloaded elf kernel "kernel" at 0xc03b5000. Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x000038c8 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) pcib0: on motherboard found-> vendor=0x8086, dev=0x7190, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base 40000000, size 26, enabled found-> vendor=0x8086, dev=0x7191, revid=0x02 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x104c, dev=0xac1d, revid=0x00 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=4 secondarybus=2 intpin=a, irq=11 map[10]: type 1, range 32, base 50102000, size 12, enabled found-> vendor=0x104c, dev=0xac1d, revid=0x00 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=7 secondarybus=5 intpin=b, irq=11 map[10]: type 1, range 32, base 50101000, size 12, enabled found-> vendor=0x1013, dev=0x6001, revid=0x01 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 50100000, size 12, enabled map[14]: type 1, range 32, base 50000000, size 20, enabled found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000fcf0, size 4, enabled found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=11 map[20]: type 1, range 32, base 00008400, size 5, enabled found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 1, range 32, base 0000efa0, size 4, enabled pci0: on pcib0 pcib1: at device 1.0 on pci0 found-> vendor=0x10c8, dev=0x0005, revid=0x12 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base d0000000, size 24, enabled map[14]: type 1, range 32, base 70000000, size 22, enabled map[18]: type 1, range 32, base 70400000, size 20, enabled pci1: on pcib1 pci1: (vendor=0x10c8, dev=0x0005) at 0.0 irq 11 pcic-pci0: mem 0x50102000-0x50102fff irq 11 at device 2.0 on pci0 pcic-pci0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][CSC parallel isa irq] pcic-pci0: Legacy address set to 0x3e0 PCI Config space: 00: ac1d104c 02100007 06070000 0082a808 10: 50102000 020000a0 b0040200 00000000 20: 00000000 00000000 00000000 00000000 30: 00000000 00000000 00000000 03c0010b 40: 00eb1014 000003e1 00000000 00000000 50: 00000000 00000000 00000000 00000000 60: 00000000 00000000 00000000 00000000 70: 00000000 00000000 00000000 00000000 80: 00449060 00000000 09818948 fba97543 90: 606282c0 00000000 00000000 00000000 Cardbus Socket registers: 00: 0000000f: 00000000: 30000710: 00000000: 10: 00000000: 00000000: 00000000: 00000000: ExCa registers: 00: 83 0c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10: 00 00 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 pcic-pci1: mem 0x50101000-0x50101fff irq 11 at device 2.1 on pci0 pcic-pci1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][CSC parallel isa irq] PCI Config space: 00: ac1d104c 02100007 06070000 0082a808 10: 50101000 020000a0 b0070500 00000000 20: 00000000 00000000 00000000 00000000 30: 00000000 00000000 00000000 03c0020b 40: 00eb1014 000003e1 00000000 00000000 50: 00000000 00000000 00000000 00000000 60: 00000000 00000000 00000000 00000000 70: 00000000 00000000 00000000 00000000 80: 00449060 00000000 09818948 fba97543 90: 606282c0 00000000 00000000 00000000 Cardbus Socket registers: 00: 00000000: 00000000: 30000306: 00000000: 10: 00000000: 00000000: 00000000: 00000000: ExCa registers: 00: 83 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10: 00 00 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 csa0: mem 0x50000000-0x500fffff,0x50100000-0x50100fff irq 11 at device 6.0 on pci0 pcm0: on csa0 pcm0: ac97 codec id 0x 0 pcm0: ac97 codec features 5 bit master volume, pcm0: ac97 codec reports dac not ready pcm: setmap 3e73000, 1000; 0xc08bf000 -> 3e73000 pcm: setmap 3e60000, 1000; 0xc08cc000 -> 3e60000 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfcf0-0xfcff at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xfcf8 ata1: mask=03 status0=50 status1=01 ata1: mask=03 status0=00 status1=01 ata1: devices = 0x4 ata1: at 0x170 irq 15 on atapci0 pci0: (vendor=0x8086, dev=0x7112) at 7.2 irq 11 chip1: port 0xefa0-0xefaf at device 7.3 on pci0 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 ata-: ata0 exists, using next available unit number ata-: ata1 exists, using next available unit number pcm-: pcm0 exists, using next available unit number ex_isa_identify() isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x54ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: data 08 00 00 psm: status 10 00 64 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 30 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 pccard0: on pcic0 pccard1: on pcic0 pcic1: not probed (disabled) sio0: irq maps: 0x445 0x455 0x445 0x445 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A ppc0: parallel port found at 0x3bc ppc0: cannot reserve I/O port range isa_compat: didn't get irq for lnc mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) sbc0: at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 pcm2: on sbc0 pcm: setmap 6000, 2000; 0xc577e000 -> 6000 pcm: setmap 8000, 2000; 0xc5780000 -> 8000 pca0 at port 0x40 on isa0 isa_probe_children: probing PnP devices BIOS Geometries: 0:033fef3f 0..831=832 cylinders, 0..239=240 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: sl0 attached bpf: ppp0 attached new masks: bio 4008c040, tty 40031832, net 40071832 bpf: lo0 attached bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: stf0 attached bpf: faith0 attached IPsec: Initialized Security Association Processing. ata0-master: success setting up UDMA2 mode on PIIX4 chip ad0: ATA-4 disk at ata0 as master ad0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad0 Creating DISK wd0 ata1-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata1-master: success setting up PIO4 mode on generic chip acd0: DVD-ROM drive at ata1 as master acd0: read 1031KB/s (3437KB/s), 512KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, DVD-ROM, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked Mounting root from ufs:/dev/ad0s2a pccard: card inserted, slot 0 ad0s1: type 0x6, start 63, end = 4188239, size 4188177 : OK ad0s2: type 0xa5, start 4188240, end = 12594959, size 8406720 : OK start_init: trying /sbin/init pcic: I/O win 0 flags 11 2e8-2ef pcic: I/O win 0 flags 1 2e8-2ef sio2 at port 0x2e8-0x2ef irq 3 slot 0 on pccard0 pcic: I/O win 0 flags 11 2e8-2ef sio2: type 16550A bpf: tun0 attached To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 13:11:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (Postfix) with ESMTP id 21D1A37B7E4 for ; Sat, 1 Apr 2000 13:11:41 -0800 (PST) (envelope-from kent@lab1.tfd.com) Received: from lab1.tfd.com (lab1.tfd.com [10.9.200.31]) by rtp.tfd.com (8.9.3/8.9.3) with SMTP id QAA06310 for ; Sat, 1 Apr 2000 16:12:16 -0500 (EST) Received: by lab1.tfd.com id AA25089 (5.67b/IDA-1.5 for current@freebsd.org); Sat, 1 Apr 2000 16:09:43 -0500 Date: Sat, 1 Apr 2000 16:09:43 -0500 From: Kent Hauser Message-Id: <200004012109.AA25089@lab1.tfd.com> To: current@freebsd.org Subject: IPSec & ppp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've configured my laptop to use IPSec to set up a link back to my office network. Every encapsulated packet generates an error message "cksum: out of data". The link works fine otherwise. I'm using AH+ESP over a normal PPP dialup link to my ISP. Normal internet packets do not generate this message. From my home box, I use a similar arrangement, except it's PPPoE and thus has "netgraph" config'd in the kernel. The laptop box does not. This did not happen with a kernel built a couple of weeks ago. The problem system resulted from a "make world" from a cvsup of current 3/31/00. Kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 13:16:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 764A537BA31 for ; Sat, 1 Apr 2000 13:16:28 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 16599 invoked from network); 1 Apr 2000 21:16:27 -0000 Received: from acs-63-90-88-170.zbzoom.net (HELO cvzoom.net) (63.90.88.170) by ns.cvzoom.net with SMTP; 1 Apr 2000 21:16:27 -0000 Message-ID: <38E66717.7112CFE8@cvzoom.net> Date: Sat, 01 Apr 2000 16:16:07 -0500 From: Donn Miller X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Kent Hauser Cc: current@freebsd.org Subject: Re: no audio with newpcm driver on TP600E References: <200004012054.AA24992@lab1.tfd.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Hauser wrote: > I'm having problems with the newpcm driver. Basically, I can't > get audio from the speakers. This while trying to play a cd. > The output of mixer looks reasonable. How recently has your kernel been built? I've been running -current for a long time, and my ESS 1868 ALWAYS worked until I built a kernel on Mar 30. It looks like the pcm driver was overhauled as of Mar 29 or 30. Basically, my sound still works, but sound apps are acting real flaky. The sound is really flaky, and the sound chokes bad under any CPU load. I had to revert back to a kernel I built around midnight Mar 28 before the changes to pcm were committed. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 13:16:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from hydrant.intranova.net (hydrant.ncw.qc.ca [209.201.95.10]) by hub.freebsd.org (Postfix) with SMTP id DAD8D37BA53 for ; Sat, 1 Apr 2000 13:16:29 -0800 (PST) (envelope-from oogali@intranova.net) Received: (qmail 14148 invoked from network); 1 Apr 2000 21:20:01 -0000 Received: from localhost.abuselabs.com (HELO localhost) (missnglnk@127.0.0.1) by localhost.abuselabs.com with SMTP; 1 Apr 2000 21:20:01 -0000 Date: Sat, 1 Apr 2000 16:20:01 -0500 (EST) From: Omachonu Ogali To: freebsd-small@freebsd.org, freebsd-current@freebsd.org Subject: PicoBSD 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, parts of PicoBSD are finally working again. I've managed to get dial, isp, and net working again. The only ones left to check out are bridge and install, I'm not sure about router, does that still exist or was that replaced by bridge? Bridge is too big to fit on a floppy so I'm working on slimming that down a little. -- +-------------------------------------------------------------------------+ | Omachonu Ogali oogali@intranova.net | | Intranova Networking Group http://tribune.intranova.net | | PGP Key ID: 0xBFE60839 | | PGP Fingerprint: C8 51 14 FD 2A 87 53 D1 E3 AA 12 12 01 93 BD 34 | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 13:37:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id AA26537B589 for ; Sat, 1 Apr 2000 13:37:35 -0800 (PST) (envelope-from gandalf@vilnya.demon.co.uk) Received: from vilnya.demon.co.uk ([158.152.19.238]) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 12bVaI-000A4V-0B; Sat, 1 Apr 2000 21:37:34 +0000 Received: from NENYA (nenya.rings [10.2.4.3]) by vilnya.demon.co.uk (Postfix) with SMTP id 23961D9A8; Sat, 1 Apr 2000 22:36:52 +0100 (BST) Message-ID: <001101bf9c22$a0749800$0304020a@NENYA> From: "Cameron Grant" To: "Kent Hauser" , References: <200004012054.AA24992@lab1.tfd.com> Subject: Re: no audio with newpcm driver on TP600E Date: Sat, 1 Apr 2000 22:38:32 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > # For PnP/PCI sound cards > #device pcm > #device sbc > #device csa > > # For non-PnP cards: > device pcm0 at isa? irq 10 drq 1 flags 0x0 > device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x15 > device csa > device gusc0 at isa? port 0x220 irq 5 drq 1 flags 0x13 this is wrong. try: options PNPBIOS device pcm - cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 14:49:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 1B4EA37BC43 for ; Sat, 1 Apr 2000 14:49:16 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m4.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id HAA12811; Sun, 2 Apr 2000 07:48:15 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id HAA00418; Sun, 2 Apr 2000 07:48:14 +0900 (JST) Received: from localhost ([192.168.245.183]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id HAA15291; Sun, 2 Apr 2000 07:48:11 +0900 (JST) To: bde@zeta.org.au Cc: bmah@CA.Sandia.GOV, nnd@mail.nsk.ru, current@FreeBSD.ORG Subject: Re: 'machine/param.h' required for 'sys/socket.h' In-Reply-To: References: <20000329003050L.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Sun_Apr__2_07:49:06_2000_809)--" Content-Transfer-Encoding: 7bit Message-Id: <20000402074908D.shin@nd.net.fujitsu.co.jp> Date: Sun, 02 Apr 2000 07:49:08 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 257 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Sun_Apr__2_07:49:06_2000_809)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > I created the patches. > > It become a little bit more complicated than I expected, to > > avoid duplicated inclusion independently in each of namespace > > polluted part and non polluted part. > > Now I don't like this for a quick fix :-). It is more complicated than > a correct fix. > > I think it would be OK without any anti-redefinition ifdefs. Redefinition > is only a micro-pessimization since there are only #define's (no > typedefs, etc.) and won't occur often since should only > be included by , and . Reinclusion > can be optimized in the including file using e.g. #ifndef _ALIGN in > . I once tried more simpler patches, but then I had a build problem at sbin/ipfw/ipfw.c. It includes before , so is once included via but namespace non-polluted part only. Then it is re-included via , but nothing actually included due to anti-redefiition ifdefs. And build failed because the file needs namespace polluted definitions in . This seems to be difficult issue, and some considration in seems to be inevitable. This time I created less complicated patches, which define namespace non-polluted macros outside of anti-redefiition ifdefs for the file. But each such namespace non-polluted macros have each anti-redefinition ifdef itself. Yoshinobu Inoue ----Next_Part(Sun_Apr__2_07:49:06_2000_809)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="namespace.diff" Index: sys/socket.h =================================================================== RCS file: /home/ncvs/src/sys/sys/socket.h,v retrieving revision 1.39 diff -u -r1.39 socket.h --- sys/socket.h 2000/03/11 19:51:04 1.39 +++ sys/socket.h 2000/04/01 20:40:30 @@ -37,6 +37,14 @@ #ifndef _SYS_SOCKET_H_ #define _SYS_SOCKET_H_ +#ifdef _NO_NAMESPACE_POLLUTION +#include +#else +#define _NO_NAMESPACE_POLLUTION +#include +#undef _NO_NAMESPACE_POLLUTION +#endif + /* * Definitions related to sockets: types, address families, options. */ @@ -352,20 +360,20 @@ /* given pointer to struct cmsghdr, return pointer to data */ #define CMSG_DATA(cmsg) ((u_char *)(cmsg) + \ - ALIGN(sizeof(struct cmsghdr))) + _ALIGN(sizeof(struct cmsghdr))) /* given pointer to struct cmsghdr, return pointer to next cmsghdr */ #define CMSG_NXTHDR(mhdr, cmsg) \ - (((caddr_t)(cmsg) + ALIGN((cmsg)->cmsg_len) + \ - ALIGN(sizeof(struct cmsghdr)) > \ + (((caddr_t)(cmsg) + _ALIGN((cmsg)->cmsg_len) + \ + _ALIGN(sizeof(struct cmsghdr)) > \ (caddr_t)(mhdr)->msg_control + (mhdr)->msg_controllen) ? \ (struct cmsghdr *)NULL : \ - (struct cmsghdr *)((caddr_t)(cmsg) + ALIGN((cmsg)->cmsg_len))) + (struct cmsghdr *)((caddr_t)(cmsg) + _ALIGN((cmsg)->cmsg_len))) #define CMSG_FIRSTHDR(mhdr) ((struct cmsghdr *)(mhdr)->msg_control) -#define CMSG_SPACE(l) (ALIGN(sizeof(struct cmsghdr)) + ALIGN(l)) -#define CMSG_LEN(l) (ALIGN(sizeof(struct cmsghdr)) + (l)) +#define CMSG_SPACE(l) (_ALIGN(sizeof(struct cmsghdr)) + _ALIGN(l)) +#define CMSG_LEN(l) (_ALIGN(sizeof(struct cmsghdr)) + (l)) /* "Socket"-level control message types: */ #define SCM_RIGHTS 0x01 /* access rights (array of int) */ Index: i386/include/param.h =================================================================== RCS file: /home/ncvs/src/sys/i386/include/param.h,v retrieving revision 1.55 diff -u -r1.55 param.h --- i386/include/param.h 2000/03/29 05:39:04 1.55 +++ i386/include/param.h 2000/04/01 20:40:31 @@ -37,8 +37,17 @@ * $FreeBSD: src/sys/i386/include/param.h,v 1.55 2000/03/29 05:39:04 jlemon Exp $ */ -#ifndef _MACHINE_PARAM_H_ -#define _MACHINE_PARAM_H_ +/* + * Round p (pointer or byte index) up to a correctly-aligned value + * for all data types (int, long, ...). The result is unsigned int + * and must be cast to any desired pointer type. + */ +#ifndef _ALIGNBYTES +#define _ALIGNBYTES (sizeof(int) - 1) +#endif +#ifndef _ALIGN +#define _ALIGN(p) (((unsigned)(p) + _ALIGNBYTES) & ~_ALIGNBYTES) +#endif /* * Machine dependent constants for Intel 386. @@ -46,12 +55,21 @@ #ifndef _MACHINE #define _MACHINE i386 #endif -#ifndef MACHINE -#define MACHINE "i386" -#endif #ifndef _MACHINE_ARCH #define _MACHINE_ARCH i386 #endif + +#ifndef _NO_NAMESPACE_POLLUTION + +#ifndef _MACHINE_PARAM_H_ +#define _MACHINE_PARAM_H_ + +/* + * Machine dependent constants for Intel 386. + */ +#ifndef MACHINE +#define MACHINE "i386" +#endif #ifndef MACHINE_ARCH #define MACHINE_ARCH "i386" #endif @@ -70,13 +88,8 @@ #define NCPUS 1 #endif -/* - * Round p (pointer or byte index) up to a correctly-aligned value - * for all data types (int, long, ...). The result is unsigned int - * and must be cast to any desired pointer type. - */ -#define ALIGNBYTES (sizeof(int) - 1) -#define ALIGN(p) (((unsigned)(p) + ALIGNBYTES) & ~ALIGNBYTES) +#define ALIGNBYTES _ALIGNBYTES +#define ALIGN(p) _ALIGN(p) #define PAGE_SHIFT 12 /* LOG2(PAGE_SIZE) */ #define PAGE_SIZE (1<; Sat, 1 Apr 2000 14:55:13 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id HAA07291; Sun, 2 Apr 2000 07:55:05 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id HAA23981; Sun, 2 Apr 2000 07:54:57 +0900 (JST) Received: from localhost ([192.168.245.183]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id HAA15398; Sun, 2 Apr 2000 07:54:53 +0900 (JST) To: cpiazza@jaxon.net Cc: current@FreeBSD.ORG Subject: Re: 75 second delay using telnet/ssh (ipv6 related) In-Reply-To: <20000321105026G.shin@nd.net.fujitsu.co.jp> References: <20000319150009.A404@norn.ca.eu.org> <20000321105026G.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Sun_Apr__2_07:55:48_2000_518)--" Content-Transfer-Encoding: 7bit Message-Id: <20000402075551N.shin@nd.net.fujitsu.co.jp> Date: Sun, 02 Apr 2000 07:55:51 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 647 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Sun_Apr__2_07:55:48_2000_518)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Hi, > > > This is kind of weird, so I want to see if anyone else has noticed > > this or has a solution to it. > > > > If I use telnet or ssh (there might be more programs, > > but I have only noticed these two so far), and supply a hostname to it, > > my machine is constantly requesting AAAA records, and finally after > > 75 seconds it requests and receives an A record from the nameserver. > > Currently, using -4 option is a workaround for the problem, > but I think this should be fixed by a resolver change as > discussed on this list before. > > The change is from, > all AAAA trial, then all A trial, > to > try AAAA and A for each trial. > > Sorry for the inconvenience and I'll try the fix. Sorry to be late, but I tried resolver fix and it seems to work. This should remove such 75 seconds delay in apps which use getaddrinfo(). Please review and try this patches. Thanks, Yoshinobu Inoue ----Next_Part(Sun_Apr__2_07:55:48_2000_518)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="resolv.diff" Index: getaddrinfo.c =================================================================== RCS file: /home/ncvs/src/lib/libc/net/getaddrinfo.c,v retrieving revision 1.9 diff -u -r1.9 getaddrinfo.c --- getaddrinfo.c 2000/02/19 16:10:12 1.9 +++ getaddrinfo.c 2000/04/01 20:38:03 @@ -108,7 +108,6 @@ }; struct explore { - int e_af; int e_socktype; int e_protocol; const char *e_protostr; @@ -119,15 +118,10 @@ }; static const struct explore explore[] = { -#ifdef INET6 - { PF_INET6, SOCK_DGRAM, IPPROTO_UDP, "udp", 0x07 }, - { PF_INET6, SOCK_STREAM, IPPROTO_TCP, "tcp", 0x07 }, - { PF_INET6, SOCK_RAW, ANY, NULL, 0x05 }, -#endif - { PF_INET, SOCK_DGRAM, IPPROTO_UDP, "udp", 0x07 }, - { PF_INET, SOCK_STREAM, IPPROTO_TCP, "tcp", 0x07 }, - { PF_INET, SOCK_RAW, ANY, NULL, 0x05 }, - { -1, 0, 0, NULL, 0 }, + { SOCK_DGRAM, IPPROTO_UDP, "udp", 0x07 }, + { SOCK_STREAM, IPPROTO_TCP, "tcp", 0x07 }, + { SOCK_RAW, ANY, NULL, 0x05 }, + { 0, 0, NULL, 0 }, }; #ifdef INET6 @@ -136,7 +130,8 @@ #define PTON_MAX 4 #endif - +extern struct hostent * _getipnodebyname_multi __P((const char *name, + int af, int flags, int *errp)); static int str_isnumber __P((const char *)); static int explore_fqdn __P((const struct addrinfo *, const char *, const char *, struct addrinfo **)); @@ -307,9 +302,7 @@ if (pai->ai_socktype != ANY && pai->ai_protocol != ANY) { int matched = 0; - for (ex = explore; ex->e_af >= 0; ex++) { - if (pai->ai_family != ex->e_af) - continue; + for (ex = explore; ex->e_socktype; ex++) { if (ex->e_socktype == ANY) continue; if (ex->e_protocol == ANY) @@ -353,10 +346,12 @@ } /* NULL hostname, or numeric hostname */ - for (ex = explore; ex->e_af >= 0; ex++) { + for (afd = afdl; afd->a_af; afd++) + { + for (ex = explore; ex->e_socktype; ex++) { *pai = ai0; - if (!MATCH_FAMILY(pai->ai_family, ex->e_af, WILD_AF(ex))) + if (!MATCH_FAMILY(pai->ai_family, afd->a_af, WILD_AF(ex))) continue; if (!MATCH(pai->ai_socktype, ex->e_socktype, WILD_SOCKTYPE(ex))) continue; @@ -364,7 +359,7 @@ continue; if (pai->ai_family == PF_UNSPEC) - pai->ai_family = ex->e_af; + pai->ai_family = afd->a_af; if (pai->ai_socktype == ANY && ex->e_socktype != ANY) pai->ai_socktype = ex->e_socktype; if (pai->ai_protocol == ANY && ex->e_protocol != ANY) @@ -381,6 +376,7 @@ while (cur && cur->ai_next) cur = cur->ai_next; } + } /* * XXX @@ -394,27 +390,12 @@ ERR(EAI_NONAME); if (hostname == NULL) ERR(EAI_NONAME); - - /* - * hostname as alphabetical name. - * we would like to prefer AF_INET6 than AF_INET, so we'll make a - * outer loop by AFs. - */ - for (afd = afdl; afd->a_af; afd++) { - *pai = ai0; - if (!MATCH_FAMILY(pai->ai_family, afd->a_af, 1)) - continue; - - for (ex = explore; ex->e_af >= 0; ex++) { + /* hostname as alphabetical name. */ + { + for (ex = explore; ex->e_socktype; ex++) { *pai = ai0; - if (pai->ai_family == PF_UNSPEC) - pai->ai_family = afd->a_af; - - if (!MATCH_FAMILY(pai->ai_family, ex->e_af, - WILD_AF(ex))) - continue; if (!MATCH(pai->ai_socktype, ex->e_socktype, WILD_SOCKTYPE(ex))) { continue; @@ -424,8 +405,6 @@ continue; } - if (pai->ai_family == PF_UNSPEC) - pai->ai_family = ex->e_af; if (pai->ai_socktype == ANY && ex->e_socktype != ANY) pai->ai_socktype = ex->e_socktype; if (pai->ai_protocol == ANY && ex->e_protocol != ANY) @@ -485,12 +464,8 @@ if (get_portmatch(pai, servname) != 0) return 0; - afd = find_afd(pai->ai_family); - if (afd == NULL) - return 0; - - hp = getipnodebyname(hostname, pai->ai_family, AI_ADDRCONFIG, - &h_error); + hp = _getipnodebyname_multi(hostname, pai->ai_family, AI_ADDRCONFIG, + &h_error); if (hp == NULL) { switch (h_error) { case HOST_NOT_FOUND: @@ -519,8 +494,12 @@ for (i = 0; hp->h_addr_list[i] != NULL; i++) { af = hp->h_addrtype; ap = hp->h_addr_list[i]; + + if (pai->ai_family != AF_UNSPEC && af != pai->ai_family) + continue; - if (af != pai->ai_family) + afd = find_afd(af); + if (afd == NULL) continue; GET_AI(cur->ai_next, afd, ap); Index: name6.c =================================================================== RCS file: /home/ncvs/src/lib/libc/net/name6.c,v retrieving revision 1.7 diff -u -r1.7 name6.c --- name6.c 2000/03/15 15:04:54 1.7 +++ name6.c 2000/04/01 20:38:04 @@ -42,11 +42,13 @@ #include #include #include +#include #include #include #include +#include #include #include #include @@ -255,8 +257,6 @@ if (flags & AI_ADDRCONFIG) { int s; - if ((s = socket(af, SOCK_DGRAM, 0)) < 0) - return NULL; /* * TODO: * Note that implementation dependent test for address @@ -264,7 +264,25 @@ * (or apropriate interval), * because addresses will be dynamically assigned or deleted. */ - _close(s); + if (af == AF_UNSPEC) { + if ((s = socket(AF_INET6, SOCK_DGRAM, 0)) < 0) + af = AF_INET; + else { + _close(s); +#ifdef INET6 + if ((s = socket(AF_INET, SOCK_DGRAM, 0)) < 0) + af = AF_INET6; + else + _close(s); +#endif + } + + } + if (af != AF_UNSPEC) { + if ((s = socket(af, SOCK_DGRAM, 0)) < 0) + return NULL; + _close(s); + } } for (i = 0; i < MAXHOSTCONF; i++) { @@ -277,16 +295,19 @@ return NULL; } +/* getipnodebyname() internal routine for multiple query(PF_UNSPEC) support. */ struct hostent * -getipnodebyname(const char *name, int af, int flags, int *errp) +_getipnodebyname_multi(const char *name, int af, int flags, int *errp) { struct hostent *hp; union inx_addr addrbuf; + /* XXX: PF_UNSPEC is only supposed to be passed from getaddrinfo() */ if (af != AF_INET #ifdef INET6 && af != AF_INET6 #endif + && af != PF_UNSPEC ) { *errp = NO_RECOVERY; @@ -341,6 +362,21 @@ } struct hostent * +getipnodebyname(const char *name, int af, int flags, int *errp) +{ + if (af != AF_INET +#ifdef INET6 + && af != AF_INET6 +#endif + ) + { + *errp = NO_RECOVERY; + return NULL; + } + return(_getipnodebyname_multi(name, af ,flags, errp)); +} + +struct hostent * getipnodebyaddr(const void *src, size_t len, int af, int *errp) { struct hostent *hp; @@ -746,6 +782,7 @@ char *aliases[MAXALIASES + 1], *addrs[2]; union inx_addr addrbuf; char buf[BUFSIZ]; + int af0 = af; if ((fp = _files_open(errp)) == NULL) return NULL; @@ -766,11 +803,39 @@ } if (!match) continue; - if ((af == AF_INET - ? inet_aton(addrstr, (struct in_addr *)&addrbuf) - : inet_pton(af, addrstr, &addrbuf)) != 1) { + switch (af0) { + case AF_INET: + if (inet_aton(addrstr, (struct in_addr *)&addrbuf) + != 1) { + *errp = NO_DATA; /* name found */ + continue; + } + af = af0; + break; +#ifdef INET6 + case AF_INET6: + if (inet_pton(af, addrstr, &addrbuf) != 1) { + *errp = NO_DATA; /* name found */ + continue; + } + af = af0; + break; +#endif + case AF_UNSPEC: + if (inet_aton(addrstr, (struct in_addr *)&addrbuf) + == 1) { + af = AF_INET; + break; + } +#ifdef INET6 + if (inet_pton(AF_INET6, addrstr, &addrbuf) == 1) { + af = AF_INET6; + break; + } +#endif *errp = NO_DATA; /* name found */ continue; + /* NOTREACHED */ } hp = &hpbuf; hp->h_name = cname; @@ -842,6 +907,8 @@ { struct hostent *hp = NULL; + if (af == AF_UNSPEC) + af = AF_INET; if (af == AF_INET) { hp = _gethostbynisname(name, af); if (hp != NULL) @@ -870,15 +937,22 @@ #define DNS_ASSERT(X) if (!(X)) { goto badanswer; } #endif +struct __res_type_list { + SLIST_ENTRY(__res_type_list) rtl_entry; + int rtl_type; +}; + static struct hostent * -_dns_ghbyname(const char *name, int af, int *errp) +_gethpbyanswer(answer, anslen, qtype, errp) + const u_char *answer; + int anslen; + int qtype; + int *errp; { int n; - u_char answer[BUFSIZ]; char tbuf[MAXDNAME+1]; HEADER *hp; - u_char *cp, *eom; - int qtype; + const u_char *cp, *eom; int type, class, ancount, qdcount; u_long ttl; char hostbuf[BUFSIZ]; @@ -889,30 +963,13 @@ int buflen; int na, nh; - if ((_res.options & RES_INIT) == 0) { - if (res_init() < 0) { - *errp = h_errno; - return NULL; - } - } hbuf.h_aliases = alist; - hbuf.h_addrtype = af; - hbuf.h_length = ADDRLEN(af); + hbuf.h_addrtype = AF_INET; + hbuf.h_length = ADDRLEN(AF_INET); hbuf.h_addr_list = hlist; na = nh = 0; - -#ifdef INET6 - qtype = (af == AF_INET6 ? T_AAAA : T_A); -#else - qtype = T_A; -#endif - n = res_search(name, C_IN, qtype, answer, sizeof(answer)); - if (n < 0) { - *errp = h_errno; - return NULL; - } hp = (HEADER *)answer; - eom = answer + n; + eom = answer + anslen; ancount = ntohs(hp->ancount); qdcount = ntohs(hp->qdcount); DNS_ASSERT(qdcount == 1); @@ -962,11 +1019,13 @@ bp += n; buflen -= n; break; - case T_A: #ifdef INET6 case T_AAAA: + hbuf.h_addrtype = AF_INET6; + hbuf.h_length = ADDRLEN(AF_INET6); #endif - DNS_ASSERT(type == qtype); + case T_A: + DNS_ASSERT(qtype == 0 || type == qtype); bp = (char *)ALIGN(bp); DNS_ASSERT(n == hbuf.h_length); DNS_ASSERT(n < buflen); @@ -992,6 +1051,210 @@ alist[na] = NULL; hlist[nh] = NULL; return _hpcopy(&hbuf, errp); +} + +/* res_search() variant with multiple query support. */ +static struct hostent * +_res_search_multi(name, rtl, errp) + const char *name; /* domain name */ + struct __res_type_list *rtl; /* list of query types */ + int *errp; +{ + u_char answer[BUFSIZ]; /* buffer to put answer */ + const char *cp, * const *domain; + struct hostent *hp0 = NULL, *hp; + u_int dots; + int trailing_dot, ret, saved_herrno; + int got_nodata = 0, got_servfail = 0, tried_as_is = 0; + struct __res_type_list *rtl0 = rtl; + + if ((_res.options & RES_INIT) == 0 && res_init() == -1) { + *errp = NETDB_INTERNAL; + return (NULL); + } + dots = 0; + for (cp = name; *cp; cp++) + dots += (*cp == '.'); + trailing_dot = 0; + if (cp > name && *--cp == '.') + trailing_dot++; + + /* If there aren't any dots, it could be a user-level alias */ + if (!dots && (cp = hostalias(name)) != NULL) { + for(rtl = rtl0; rtl != NULL; + rtl = SLIST_NEXT(rtl, rtl_entry)) { + ret = res_query(cp, C_IN, rtl->rtl_type, answer, + sizeof(answer)); + if (ret > 0) { + hp = _gethpbyanswer(answer, ret, rtl->rtl_type, + errp); + hp0 = _hpmerge(hp0, hp, errp); + } + } + return (hp0); + } + + /* + * If there are dots in the name already, let's just give it a try + * 'as is'. The threshold can be set with the "ndots" option. + */ + saved_herrno = -1; + if (dots >= _res.ndots) { + for(rtl = rtl0; rtl != NULL; + rtl = SLIST_NEXT(rtl, rtl_entry)) { + ret = res_querydomain(name, NULL, C_IN, rtl->rtl_type, + answer, sizeof(answer)); + if (ret > 0) { + hp = _gethpbyanswer(answer, ret, rtl->rtl_type, + errp); + hp0 = _hpmerge(hp0, hp, errp); + } + } + if (hp0 != NULL) + return (hp0); + saved_herrno = *errp; + tried_as_is++; + } + + /* + * We do at least one level of search if + * - there is no dot and RES_DEFNAME is set, or + * - there is at least one dot, there is no trailing dot, + * and RES_DNSRCH is set. + */ + if ((!dots && (_res.options & RES_DEFNAMES)) || + (dots && !trailing_dot && (_res.options & RES_DNSRCH))) { + int done = 0; + + for (domain = (const char * const *)_res.dnsrch; + *domain && !done; + domain++) { + + for(rtl = rtl0; rtl != NULL; + rtl = SLIST_NEXT(rtl, rtl_entry)) { + ret = res_querydomain(name, *domain, C_IN, + rtl->rtl_type, + answer, sizeof(answer)); + if (ret > 0) { + hp = _gethpbyanswer(answer, ret, + rtl->rtl_type, + errp); + hp0 = _hpmerge(hp0, hp, errp); + } + } + if (hp0 != NULL) + return (hp0); + + /* + * If no server present, give up. + * If name isn't found in this domain, + * keep trying higher domains in the search list + * (if that's enabled). + * On a NO_DATA error, keep trying, otherwise + * a wildcard entry of another type could keep us + * from finding this entry higher in the domain. + * If we get some other error (negative answer or + * server failure), then stop searching up, + * but try the input name below in case it's + * fully-qualified. + */ + if (errno == ECONNREFUSED) { + *errp = TRY_AGAIN; + return (NULL); + } + + switch (*errp) { + case NO_DATA: + got_nodata++; + /* FALLTHROUGH */ + case HOST_NOT_FOUND: + /* keep trying */ + break; + case TRY_AGAIN: + if (((HEADER *)answer)->rcode == SERVFAIL) { + /* try next search element, if any */ + got_servfail++; + break; + } + /* FALLTHROUGH */ + default: + /* anything else implies that we're done */ + done++; + } + + /* if we got here for some reason other than DNSRCH, + * we only wanted one iteration of the loop, so stop. + */ + if (!(_res.options & RES_DNSRCH)) + done++; + } + } + + /* + * If we have not already tried the name "as is", do that now. + * note that we do this regardless of how many dots were in the + * name or whether it ends with a dot unless NOTLDQUERY is set. + */ + if (!tried_as_is && (dots || !(_res.options & RES_NOTLDQUERY))) { + for(rtl = rtl0; rtl != NULL; + rtl = SLIST_NEXT(rtl, rtl_entry)) { + ret = res_querydomain(name, NULL, C_IN, rtl->rtl_type, + answer, sizeof(answer)); + if (ret > 0) { + hp = _gethpbyanswer(answer, ret, rtl->rtl_type, + errp); + hp0 = _hpmerge(hp0, hp, errp); + } + } + if (hp0 != NULL) + return (hp0); + } + + /* if we got here, we didn't satisfy the search. + * if we did an initial full query, return that query's h_errno + * (note that we wouldn't be here if that query had succeeded). + * else if we ever got a nodata, send that back as the reason. + * else send back meaningless h_errno, that being the one from + * the last DNSRCH we did. + */ + if (saved_herrno != -1) + *errp = saved_herrno; + else if (got_nodata) + *errp = NO_DATA; + else if (got_servfail) + *errp = TRY_AGAIN; + return (NULL); +} + +static struct hostent * +_dns_ghbyname(const char *name, int af, int *errp) +{ + struct __res_type_list *rtl, rtl4; +#ifdef INET6 + struct __res_type_list rtl6; +#endif + +#ifdef INET6 + switch (af) { + case AF_UNSPEC: + SLIST_NEXT(&rtl4, rtl_entry) = NULL; rtl4.rtl_type = T_A; + SLIST_NEXT(&rtl6, rtl_entry) = &rtl4; rtl6.rtl_type = T_AAAA; + rtl = &rtl6; + break; + case AF_INET6: + SLIST_NEXT(&rtl6, rtl_entry) = NULL; rtl6.rtl_type = T_AAAA; + rtl = &rtl6; + break; + case AF_INET: + SLIST_NEXT(&rtl4, rtl_entry) = NULL; rtl4.rtl_type = T_A; + rtl = &rtl4; + break; + } +#else + SLIST_NEXT(&rtl4, rtl_entry) = NULL; rtl4.rtl_type = T_A; + rtl = &rtl4; +#endif + return(_res_search_multi(name, rtl, errp)); } static struct hostent * ----Next_Part(Sun_Apr__2_07:55:48_2000_518)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 15: 4:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 946E637BC5C for ; Sat, 1 Apr 2000 15:04:16 -0800 (PST) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id BAB28275; Sun, 2 Apr 2000 01:02:50 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id BAA27991; Sun, 2 Apr 2000 01:03:50 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id BAA24159; Sun, 2 Apr 2000 01:04:54 +0200 (CEST) (envelope-from ticso) Date: Sun, 2 Apr 2000 01:04:53 +0200 From: Bernd Walter To: Vallo Kallaste Cc: freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402010453.A24134@cicely8.cicely.de> References: <20000331212544.A59295@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000331212544.A59295@myhakas.matti.ee>; from vallo@matti.ee on Fri, Mar 31, 2000 at 09:25:44PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 31, 2000 at 09:25:44PM +0200, Vallo Kallaste wrote: > Hi > > I have four (4) ATA disks, all same new 20GB IBM 7200rpm models. Intel > Seattle BX2 mobo, PIIX4 controller. I'm not expecting any performance > increase or such, simply want to get my hands on. Ata driver, as the > -current doesn't have wd anymore. > I have raid5 volume laid over four disks, containing /usr filesystem, > stripe unit size 256k. Machine deadlocks very reliably while doing > ordinary buildworld, keyboard is responsive, network also but no disk > I/O happens. I see syncer and bufdaemon in vrlock state; make, ln, > syslogd and dhclient in flswait state. I usually don't see such states. > Sources from which I built the system are todays, before I set up vinum. What version of sys/dev/vinum/vinumlock.c are you using? There was such a problem in the history. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 15:15:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 68B2637B795 for ; Sat, 1 Apr 2000 15:15:11 -0800 (PST) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id BAA28748; Sun, 2 Apr 2000 01:13:36 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id BAA28006; Sun, 2 Apr 2000 01:14:36 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id BAA24178; Sun, 2 Apr 2000 01:15:39 +0200 (CEST) (envelope-from ticso) Date: Sun, 2 Apr 2000 01:15:39 +0200 From: Bernd Walter To: Greg Lehey Cc: Soren Schmidt , vallo@matti.ee, freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402011538.B24134@cicely8.cicely.de> References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0.1i In-Reply-To: <20000401091140.A51727@freebie.lemis.com>; from grog@lemis.com on Sat, Apr 01, 2000 at 09:11:40AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 01, 2000 at 09:11:40AM +0930, Greg Lehey wrote: > On Friday, 31 March 2000 at 21:32:22 +0200, Søren Schmidt wrote: > > Yup, Greg and I know of this problem, it also happens with the wd > > driver and with CAM, so the problem is probably not the driver. > > I'm investigating this right now, and it looks like vinum is > > botching a struct buf in action somehow. > > I'm not sure that this is the same problem. Please supply the > information I ask for in http://www.lemis.com/vinum/how-to-debug.html. > > The problem that Søren and I are looking at is usually a panic. We > don't really know where it's happening, but we're each sure it's not > in *our* code :-) From a Vinum standpoint, it happens between the time > that Vinum sends a request to the driver and when the I/O completes, > so it's difficult to blame Vinum. On the other hand, we've seen it > with SCSI as well, so it's difficult to blame the driver. I'm half > guessing that it's something else altogether which is spamming freed > data. Vinum mallocs the buffer headers rather than using geteblk(), > which could explain why it happens only with Vinum. Greg - I'm using vinums raid5 code since months now for FreeBSDs CVS-Tree on 7x 200M disks - it does not hang for me since a long time. The latest current I tested R5 well is from 19th March on alpha. That's shortly before PHKs changes - I don't beleave that it introduced something new. The only problem with R5 I know of is parity corruption because of a bug in lockrange() for which I've already send you a fix. Even it is a general bug it seems only to cause problems together with softupdates. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 15:39:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from oscar.dorf.wh.uni-dortmund.de (oscar.dorf.wh.uni-dortmund.de [129.217.244.216]) by hub.freebsd.org (Postfix) with ESMTP id DD9E337C0F0 for ; Sat, 1 Apr 2000 15:39:18 -0800 (PST) (envelope-from patrick@oscar.dorf.wh.uni-dortmund.de) Received: from tony.dorf.wh.uni-dortmund.de (root@tony.dorf.wh.uni-dortmund.de [129.217.244.217]) by oscar.dorf.wh.uni-dortmund.de (8.9.3/8.9.3) with ESMTP id BAA53946 for ; Sun, 2 Apr 2000 01:39:17 +0200 (CEST) (envelope-from patrick@oscar.dorf.wh.uni-dortmund.de) Received: (from patrick@localhost) by tony.dorf.wh.uni-dortmund.de (8.9.3/8.9.3) id BAA27427 for freebsd-current@freebsd.org; Sun, 2 Apr 2000 01:39:15 +0200 Date: Sun, 2 Apr 2000 01:39:15 +0200 From: Patrick Mau To: FreeBSD Current Subject: 'make world' fails Message-ID: <20000402013915.A27424@tony.dorf.wh.uni-dortmund.de> Reply-To: Patrick Mau Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, the subject says it all. It fails with the follwing messages: ===> libssh cd /usr/src/gnu/lib/libgcc; make depend; make all; make install echo '#include ' > config.h echo '#include "gansidecl.h"' > tconfig.h echo '#include ' >> config.h echo '#include "i386/xm-i386.h"' >> tconfig.h echo '#include "i386/i386.h"' > tm.h echo '#include "i386/att.h"' >> tm.h echo '#include ' >> tm.h echo '#include "i386/freebsd.h"' >> tm.h echo '#include "i386/perform.h"' >> tm.h rm -f .depend mkdep -f .depend -a -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -DIN_GCC -I/usr/obj/usr/src/i386/usr/include /usr/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c mkdep -f .depend -a -nostdinc++ -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/inc /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/tinfo.cc /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/tinfo2.cc /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/new.cc /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/exception.cc /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/exception.cc:33: gansidecl.h: No such file or directory /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/exception.cc:34: eh-common.h: No such file or directory [root@oscar /usr/src] locate gansidecl.h /usr/src/contrib/gcc/gansidecl.h [root@oscar /usr/src] locate eh-common.h /usr/src/contrib/gcc/eh-common.h thanks, Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 15:50:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 6DD8137B795 for ; Sat, 1 Apr 2000 15:50:24 -0800 (PST) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id BAA00502; Sun, 2 Apr 2000 01:48:11 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id BAA28092; Sun, 2 Apr 2000 01:49:09 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id BAA24242; Sun, 2 Apr 2000 01:50:16 +0200 (CEST) (envelope-from ticso) Date: Sun, 2 Apr 2000 01:50:16 +0200 From: Bernd Walter To: Bernd Walter Cc: Greg Lehey , Soren Schmidt , vallo@matti.ee, freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402015016.C24134@cicely8.cicely.de> References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000402011538.B24134@cicely8.cicely.de>; from ticso@cicely.de on Sun, Apr 02, 2000 at 01:15:39AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 01:15:39AM +0200, Bernd Walter wrote: > > Greg - I'm using vinums raid5 code since months now for FreeBSDs CVS-Tree on > 7x 200M disks - it does not hang for me since a long time. > The latest current I tested R5 well is from 19th March on alpha. That's shortly > before PHKs changes - I don't beleave that it introduced something new. > The only problem with R5 I know of is parity corruption because of a bug in > lockrange() for which I've already send you a fix. Even it is a general bug it > seems only to cause problems together with softupdates. Ops - I oversaw that this happened with a recent current. The best I can say is that it is likely that it happened after the 19th March. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 16:46:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id A50EF37B8CD for ; Sat, 1 Apr 2000 16:46:38 -0800 (PST) (envelope-from will@blackdawn.com) Received: from argon.blackdawn.com (03-181.dial.008.popsite.net [209.69.196.181]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id QAA09550; Sat, 1 Apr 2000 16:46:23 -0800 (PST) Received: by argon.blackdawn.com (Postfix, from userid 1000) id EBB1E1945; Sat, 1 Apr 2000 19:45:59 -0500 (EST) Date: Sat, 1 Apr 2000 19:45:59 -0500 From: Will Andrews To: Patrick Mau Cc: FreeBSD Current Subject: Re: 'make world' fails Message-ID: <20000401194559.J98577@argon.blackdawn.com> References: <20000402013915.A27424@tony.dorf.wh.uni-dortmund.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000402013915.A27424@tony.dorf.wh.uni-dortmund.de>; from patrick@oscar.prima.de on Sun, Apr 02, 2000 at 01:39:15AM +0200 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 01:39:15AM +0200, Patrick Mau wrote: > Hi all, > > the subject says it all. It fails with the follwing messages: > > ===> libssh > cd /usr/src/gnu/lib/libgcc; make depend; make all; make install > echo '#include ' > config.h > echo '#include "gansidecl.h"' > tconfig.h > echo '#include ' >> config.h > echo '#include "i386/xm-i386.h"' >> tconfig.h > echo '#include "i386/i386.h"' > tm.h > echo '#include "i386/att.h"' >> tm.h > echo '#include ' >> tm.h > echo '#include "i386/freebsd.h"' >> tm.h > echo '#include "i386/perform.h"' >> tm.h > rm -f .depend > mkdep -f .depend -a > -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config > -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. > -DIN_GCC -I/usr/obj/usr/src/i386/usr/include > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c > > mkdep -f .depend -a > -nostdinc++ -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/inc > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/tinfo.cc > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/tinfo2.cc > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/new.cc > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/exception.cc > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/exception.cc:33: > gansidecl.h: No such file or directory > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/cp/exception.cc:34: > eh-common.h: No such file or directory > > [root@oscar /usr/src] locate gansidecl.h > /usr/src/contrib/gcc/gansidecl.h > > [root@oscar /usr/src] locate eh-common.h > /usr/src/contrib/gcc/eh-common.h I had a similar problem that plagued me for 2 months before I finally figured it out 2 days ago. You need to remove your CXXFLAGS definition in /etc/make.conf, it is conflicting with CXXFLAGS in /usr/share/mk/sys.mk. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 17: 3:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id EFED437B5ED; Sat, 1 Apr 2000 17:03:34 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA43602; Sat, 1 Apr 2000 17:03:24 -0800 (PST) (envelope-from dillon) Date: Sat, 1 Apr 2000 17:03:24 -0800 (PST) From: Matthew Dillon Message-Id: <200004020103.RAA43602@apollo.backplane.com> To: Richard Wendland Cc: Paul Richards , Alfred Perlstein , Poul-Henning Kamp , current@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: FreeBSD random I/O performance issues References: <200003221544.PAA08760@ns0.netcraft.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've committed an 80% fix for the random seek / write performance issue. The rest of the fix will come later when Kirk commits his shared-lock-buffer-cache idea. I've committed it into -current and will MFC it into -stable in a week if there aren't any problems. I do not intend to MFC it into 3.x. This should solve most of the random-I/O latency issues with read-after-write on buffers. Basically what had to be done was to continue to call the clustering code as before (so reallocblks still gets called), but only issue write_behind I/O if the writes are generally sequential. If the writes are random, even big writes, we do not issue write-behind I/O. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 19:15:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id EDC6A37B5ED; Sat, 1 Apr 2000 19:15:41 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id 33D7319A9; Sat, 1 Apr 2000 19:15:35 -0800 (PST) Date: Sat, 1 Apr 2000 19:15:35 -0800 From: Chris Piazza To: current@FreeBSD.org Cc: shin@FreeBSD.org Subject: kernel build broken without INET6 Message-ID: <20000401191535.A4013@norn.ca.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patch included... Index: in_pcb.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/in_pcb.c,v retrieving revision 1.61 diff -u -r1.61 in_pcb.c --- in_pcb.c 2000/04/01 22:35:43 1.61 +++ in_pcb.c 2000/04/02 03:14:15 @@ -153,10 +153,12 @@ inp->inp_gencnt = ++pcbinfo->ipi_gencnt; inp->inp_pcbinfo = pcbinfo; inp->inp_socket = so; +#ifdef INET6 if (ip6_mapped_addr_on) inp->inp_flags &= ~IN6P_BINDV6ONLY; else inp->inp_flags |= IN6P_BINDV6ONLY; +#endif LIST_INSERT_HEAD(pcbinfo->listhead, inp, inp_list); pcbinfo->ipi_count++; so->so_pcb = (caddr_t)inp; -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 19:30:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 86F7537B5CC for ; Sat, 1 Apr 2000 19:30:12 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id AD4311A21; Sat, 1 Apr 2000 19:30:05 -0800 (PST) Date: Sat, 1 Apr 2000 19:30:05 -0800 From: Chris Piazza To: Yoshinobu Inoue Cc: current@FreeBSD.ORG Subject: Re: 75 second delay using telnet/ssh (ipv6 related) Message-ID: <20000401193005.A353@norn.ca.eu.org> References: <20000319150009.A404@norn.ca.eu.org> <20000321105026G.shin@nd.net.fujitsu.co.jp> <20000402075551N.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000402075551N.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Sun, Apr 02, 2000 at 07:55:51AM +0900 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 07:55:51AM +0900, Yoshinobu Inoue wrote: > > > Sorry for the inconvenience and I'll try the fix. > > Sorry to be late, but I tried resolver fix and it seems to work. > This should remove such 75 seconds delay in apps which use > getaddrinfo(). > > Please review and try this patches. I applied it and am running with it now, but I can't say one way or another if it has fixed the problem :-). It only cropped up every couple of weeks and seemingly random at that. I'll assume it works if I don't see it happening again. Thanks, -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 19:44:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 8BC8E37B5CC for ; Sat, 1 Apr 2000 19:44:14 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m4.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id MAA14481; Sun, 2 Apr 2000 12:43:31 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id MAA20332; Sun, 2 Apr 2000 12:43:31 +0900 (JST) Received: from localhost ([192.168.245.91]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id MAA21061; Sun, 2 Apr 2000 12:43:30 +0900 (JST) To: cpiazza@jaxon.net Cc: current@FreeBSD.org Subject: Re: kernel build broken without INET6 In-Reply-To: <20000401191535.A4013@norn.ca.eu.org> References: <20000401191535.A4013@norn.ca.eu.org> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000402124426D.shin@nd.net.fujitsu.co.jp> Date: Sun, 02 Apr 2000 12:44:26 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 6 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Patch included... Sorry for it and thanks for the patch. I'll committ the fix. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 19:47: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 6519337BA20 for ; Sat, 1 Apr 2000 19:46:58 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id MAA21451; Sun, 2 Apr 2000 12:46:47 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id MAA00426; Sun, 2 Apr 2000 12:46:46 +0900 (JST) Received: from localhost ([192.168.245.91]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id MAA21124; Sun, 2 Apr 2000 12:46:45 +0900 (JST) To: cpiazza@jaxon.net Cc: current@FreeBSD.ORG Subject: Re: 75 second delay using telnet/ssh (ipv6 related) In-Reply-To: <20000401193005.A353@norn.ca.eu.org> References: <20000321105026G.shin@nd.net.fujitsu.co.jp> <20000402075551N.shin@nd.net.fujitsu.co.jp> <20000401193005.A353@norn.ca.eu.org> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000402124742P.shin@nd.net.fujitsu.co.jp> Date: Sun, 02 Apr 2000 12:47:42 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 20 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Sorry for the inconvenience and I'll try the fix. > > > > Sorry to be late, but I tried resolver fix and it seems to work. > > This should remove such 75 seconds delay in apps which use > > getaddrinfo(). > > > > Please review and try this patches. > > I applied it and am running with it now, but I can't say one way or another > if it has fixed the problem :-). It only cropped up every couple of > weeks and seemingly random at that. I'll assume it works if I don't see > it happening again. > > Thanks, OK, anyway it is rather critical fix, so I think it needs some testing period. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 21: 2:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from posgate.acis.com.au (posgate.acis.com.au [203.14.230.14]) by hub.freebsd.org (Postfix) with ESMTP id 6FF5D37BD11; Sat, 1 Apr 2000 21:02:13 -0800 (PST) (envelope-from andymac@bullseye.apana.org.au) Received: from bullseye.apana.org.au (uucp@localhost) by posgate.acis.com.au (8.9.3/8.9.3) with UUCP id PAA17375; Sun, 2 Apr 2000 15:01:58 +1000 Received: from bullseye.apana.org.au (central.apana.org.au [203.9.107.245]) by bullseye.apana.org.au (8.8.8/8.8.8) with SMTP id NAA06549; Sun, 2 Apr 2000 13:55:25 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Date: Sun, 2 Apr 2000 13:52:12 +1000 (EST) From: Andrew MacIntyre To: Jeremiah Gowdy Cc: freebsd-hackers@FreeBSD.ORG, current@FreeBSD.ORG, FreeBSD questions Subject: Re: JetDirect 500X and FreeBSD In-Reply-To: <004a01bf9b35$0cc56be0$0100000a@vista1.sdca.home.com> Message-ID: X-X-Sender: andymac@bullseye.apana.org.au 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, 31 Mar 2000, Jeremiah Gowdy wrote: > Does anyone have any experiance or information about using HP JetDirect 500X > Printer Hubs with FreeBSD ? This is mission critical for my company, so any > information greatly appriciated. These things have an LPD server built in IIRC, so your could just configure them as a remote LPD printer in /etc/printcap. However, I've not been totally satisfied with some of HP's earlier attempts at LPD support in JetDirect cards for their lasers printers, as they weren't particularly reliable, particularly when multiple jobs were queued simultaneously. I hope their more recent stuff is better behaved. You might want to check out LprNg or CUPS to see whether they support the native HP protocol (on port 9100???) if your box doesn't seem to cope, so that one box can be the "print server" and thus serialize all the jobs. We do this at work, although in that case NT is providing the "print server" function. -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andrew.macintyre@aba.gov.au (work) | Snail: PO Box 370 andymac@bullseye.apana.org.au (play) | Belconnen ACT 2616 andymac@pcug.org.au (play2) | Australia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 21:53:33 2000 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 3B59937B6B6; Sat, 1 Apr 2000 21:53:24 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA19677; Sat, 1 Apr 2000 22:52:42 -0700 (MST) (envelope-from ken) Date: Sat, 1 Apr 2000 22:52:42 -0700 From: "Kenneth D. Merry" To: Andrew MacIntyre Cc: Jeremiah Gowdy , freebsd-hackers@FreeBSD.ORG, current@FreeBSD.ORG, FreeBSD questions Subject: Re: JetDirect 500X and FreeBSD Message-ID: <20000401225242.A19443@panzer.kdm.org> References: <004a01bf9b35$0cc56be0$0100000a@vista1.sdca.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from andymac@bullseye.apana.org.au on Sun, Apr 02, 2000 at 01:52:12PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 13:52:12 +1000, Andrew MacIntyre wrote: > On Fri, 31 Mar 2000, Jeremiah Gowdy wrote: > > > Does anyone have any experiance or information about using HP JetDirect 500X > > Printer Hubs with FreeBSD ? This is mission critical for my company, so any > > information greatly appriciated. > > These things have an LPD server built in IIRC, so your could just > configure them as a remote LPD printer in /etc/printcap. > > However, I've not been totally satisfied with some of HP's earlier > attempts at LPD support in JetDirect cards for their lasers printers, as > they weren't particularly reliable, particularly when multiple jobs were > queued simultaneously. I hope their more recent stuff is better behaved. > > You might want to check out LprNg or CUPS to see whether they support the > native HP protocol (on port 9100???) if your box doesn't seem to cope, so > that one box can be the "print server" and thus serialize all the jobs. > We do this at work, although in that case NT is providing the "print > server" function. You can setup the stock FreeBSD lpd to talk the native HP printer protocol to a HP printer with a Jet Direct card. I've got the following setup on a -current box that talks to my HP LaserJet 4000 (hostname is "printer"): in /etc/printcap: lp|ps:\ :mx#0:lp=9100@printer:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:sh:\ :if=/usr/local/lib/filters/inputshell:\ :of=/usr/local/lib/filters/ofhp: /usr/local/lib/filters/inputshell is just this: #!/bin/sh /usr/local/lib/filters/ifhp -Ttbcp=on,model=5M exit 0 The ifhp/ofhp comes in the ifhp port, which is ports/print/ifhp. The above setup works well with either text files or postscript. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 1 22:20:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 04FD237B858 for ; Sat, 1 Apr 2000 22:19:56 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id PAA19667; Sun, 2 Apr 2000 15:17:37 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id PAA25710; Sun, 2 Apr 2000 15:17:37 +0900 (JST) Received: from localhost ([192.168.245.168]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id PAA24590; Sun, 2 Apr 2000 15:17:36 +0900 (JST) To: kent@lab1.tfd.com Cc: current@FreeBSD.ORG Subject: Re: IPSec & ppp In-Reply-To: <200004012109.AA25089@lab1.tfd.com> References: <200004012109.AA25089@lab1.tfd.com> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000402151832X.shin@nd.net.fujitsu.co.jp> Date: Sun, 02 Apr 2000 15:18:32 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 20 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, Hi, > I've configured my laptop to use IPSec to set up a link > back to my office network. Every encapsulated packet > generates an error message "cksum: out of data". The link > works fine otherwise. > > I'm using AH+ESP over a normal PPP dialup link to my ISP. > Normal internet packets do not generate this message. By the way, how about the communication itself? I also confirmed the same error messages in my local environment, but IPsec communication itself has no problem. I suppose there are some garbages at the end of cksum'ed area. I'll more investigate this. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message