From owner-freebsd-current@FreeBSD.ORG Sun Mar 30 01:57:16 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3231837B401; Sun, 30 Mar 2003 01:57:16 -0800 (PST) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 854B043FBF; Sun, 30 Mar 2003 01:57:15 -0800 (PST) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 8AD255309; Sun, 30 Mar 2003 11:57:14 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Peter Wemm From: des@ofug.org (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Date: Sun, 30 Mar 2003 11:57:13 +0200 In-Reply-To: <20030329190253.E3A112A8BB@canning.wemm.org> (Peter Wemm's message of "Sat, 29 Mar 2003 11:02:53 -0800") Message-ID: User-Agent: Gnus/5.090015 (Oort Gnus v0.15) Emacs/21.2 References: <20030329190253.E3A112A8BB@canning.wemm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable cc: Mike Barcroft cc: current@FreeBSD.org cc: sparc64@FreeBSD.org Subject: Re: sparc64 tinderbox failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Mar 2003 09:57:20 -0000 Peter Wemm writes: > Mike Barcroft wrote: > > >>> stage 4: building everything.. > > -------------------------------------------------------------- > > =3D=3D=3D> share/man/man9 > > make: don't know how to make bus_Activate_resource.9. Stop > > *** Error code 2 > This looks like a single bit memory error to me. Turn off bit 5 and a > lowercase a turns into an uppercase A. nice try, but check rev 1.179 of src/share/man/man9/Makefile. DES --=20 Dag-Erling Sm=F8rgrav - des@ofug.org From owner-freebsd-current@FreeBSD.ORG Sun Mar 30 01:57:45 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9909637B404; Sun, 30 Mar 2003 01:57:45 -0800 (PST) Received: from gate.consol.de (gate.consol.de [194.221.87.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id F126A43F85; Sun, 30 Mar 2003 01:57:40 -0800 (PST) (envelope-from m2n@consol.de) Received: from imap.consol.de (imap.consol.de [10.250.0.113]) by gate.consol.de (8.12.8/8.11.6) with ESMTP id h2U9vdAJ085930; Sun, 30 Mar 2003 11:57:39 +0200 (CEST) (envelope-from m2n@consol.de) Received: (from m2n@localhost) by imap.consol.de (8.12.8/8.12.2) id h2U9vcER084010 for m2n-bounce@consol.de; Sun, 30 Mar 2003 11:57:38 +0200 (CEST) (envelope-from m2n) Received: from gate.consol.de (vscanner.bb.consol.de [10.250.0.120]) by imap.consol.de (8.12.8/8.12.2) with ESMTP id h2U9vbHg084004 for ; Sun, 30 Mar 2003 11:57:37 +0200 (CEST) (envelope-from owner-freebsd-sparc64@freebsd.org) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by gate.consol.de (8.12.8/8.11.6) with ESMTP id h2U9vaAJ085927 for ; Sun, 30 Mar 2003 11:57:36 +0200 (CEST) (envelope-from owner-freebsd-sparc64@freebsd.org) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id A55C35573E; Sun, 30 Mar 2003 01:57:22 -0800 (PST) (envelope-from owner-freebsd-sparc64@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 902E737B401; Sun, 30 Mar 2003 01:57:22 -0800 (PST) Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3231837B401; Sun, 30 Mar 2003 01:57:16 -0800 (PST) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 854B043FBF; Sun, 30 Mar 2003 01:57:15 -0800 (PST) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 8AD255309; Sun, 30 Mar 2003 11:57:14 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Peter Wemm From: des@ofug.org (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Date: Sun, 30 Mar 2003 11:57:13 +0200 In-Reply-To: <20030329190253.E3A112A8BB@canning.wemm.org> (Peter Wemm's message of "Sat, 29 Mar 2003 11:02:53 -0800") Message-ID: User-Agent: Gnus/5.090015 (Oort Gnus v0.15) Emacs/21.2 References: <20030329190253.E3A112A8BB@canning.wemm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Prev-Sender: owner-freebsd-sparc64@freebsd.org Errors-To: owner-freebsd-sparc64@freebsd.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by imap.consol.de id h2U9vbHg084004 X-Filter: mailagent [version 3.0 PL73] for m2n@consol.de cc: Mike Barcroft cc: current@freebsd.org cc: sparc64@freebsd.org Subject: Re: sparc64 tinderbox failure X-BeenThere: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Mar 2003 09:57:46 -0000 Peter Wemm writes: > Mike Barcroft wrote: > > >>> stage 4: building everything.. > > -------------------------------------------------------------- > > ===> share/man/man9 > > make: don't know how to make bus_Activate_resource.9. Stop > > *** Error code 2 > This looks like a single bit memory error to me. Turn off bit 5 and a > lowercase a turns into an uppercase A. nice try, but check rev 1.179 of src/share/man/man9/Makefile. DES -- Dag-Erling Smørgrav - des@ofug.org _______________________________________________ freebsd-sparc64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64 To unsubscribe, send any mail to "freebsd-sparc64-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sun Mar 30 09:59:22 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A71E37B401 for ; Sun, 30 Mar 2003 09:59:22 -0800 (PST) Received: from HAL9000.homeunix.com (12-233-57-131.client.attbi.com [12.233.57.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7449B43F85 for ; Sun, 30 Mar 2003 09:59:18 -0800 (PST) (envelope-from das@FreeBSD.org) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id h2T0J3ah022266; Fri, 28 Mar 2003 16:19:03 -0800 (PST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id h2T0IxsH022265; Fri, 28 Mar 2003 16:18:59 -0800 (PST) (envelope-from das@FreeBSD.ORG) Date: Fri, 28 Mar 2003 16:18:59 -0800 From: David Schultz To: Kevin Oberman Message-ID: <20030329001859.GA22238@HAL9000.homeunix.com> Mail-Followup-To: Kevin Oberman , current@FreeBSD.ORG References: <20030325211426.1E1E95D08@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030325211426.1E1E95D08@ptavv.es.net> cc: current@FreeBSD.org Subject: Re: Unclean sync in current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Mar 2003 17:59:24 -0000 Thus spake Kevin Oberman : > I've been seeing this for a couple of weeks since I updated my laptop to > CURRENT. I do a normal shutdown (-p or -r) and reboot. The shutdown > looked normal, with no problems reported with the sync, but, when the > system is rebooted, the partitions are all shown as possibly > unclean. From my dmesg: > Mounting root from ufs:/dev/ad0s3a > WARNING: / was not properly dismounted > WARNING: / was not properly dismounted > WARNING: /tmp was not properly dismounted > WARNING: /usr was not properly dismounted > WARNING: /var was not properly dismounted > > All disks are mounted with soft-updates enabled. > > I don't see any other reports of this. Is this unique to my system? Unlike the SCSI driver, the ATA driver does not send a flush cache command to your disks before powering off the system. The kernel waits for five seconds in either case, but for some disks that may not be sufficient. The following patch should fix that, although it may have rotted a bit in the last two months given Soeren's sweeping ATA changes. I also edited an unrelated change out of the diff, which might confuse patch(1). If you run into problems getting it to apply, let me know and I'll fix it when I'm back from vacation. Index: sys/dev/ata/ata-all.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v retrieving revision 1.163 diff -u -r1.163 ata-all.c --- sys/dev/ata/ata-all.c 2003/01/19 20:18:07 1.163 +++ sys/dev/ata/ata-all.c 2003/01/27 09:17:02 @@ -77,6 +77,7 @@ static void ata_intr(void *); static int ata_getparam(struct ata_device *, u_int8_t); static int ata_service(struct ata_channel *); +static void ata_shutdown(void *arg, int howto); static void bswap(int8_t *, int); static void btrim(int8_t *, int); static void bpack(int8_t *, int8_t *, int); @@ -1160,7 +1161,32 @@ return error; } +/* + * This procedure is called during shutdown, + * after all dirty buffers have been flushed. + */ static void +ata_shutdown(void *arg, int howto) +{ + struct ata_channel *ch; + int ctlr; + +#ifdef DEV_ATADISK + /* Flush the caches of each open ATA disk device. */ + for (ctlr = 0; ctlr < devclass_get_maxunit(ata_devclass); ctlr++) { + if (!(ch = devclass_get_softc(ata_devclass, ctlr))) + continue; + ch->lock_func(ch, ATA_LF_LOCK); + if (ch->devices & ATA_ATA_MASTER && ch->device[MASTER].driver) + ad_sync(&ch->device[MASTER]); + if (ch->devices & ATA_ATA_SLAVE && ch->device[SLAVE].driver) + ad_sync(&ch->device[SLAVE]); + ch->lock_func(ch, ATA_LF_UNLOCK); + } +#endif /* DEV_ATADISK */ +} + +static void ata_drawer_start(struct ata_device *atadev) { ATA_INB(atadev->channel->r_io, ATA_DRIVE); @@ -1516,5 +1542,10 @@ printf("ata: config_intrhook_establish failed\n"); free(ata_delayed_attach, M_TEMP); } + + /* Register a handler to flush write caches on shutdown */ + if ((EVENTHANDLER_REGISTER(shutdown_post_sync, ata_shutdown, + NULL, SHUTDOWN_PRI_DEFAULT)) == NULL) + printf("ata: shutdown event registration failed!\n"); } SYSINIT(atadev, SI_SUB_DRIVERS, SI_ORDER_SECOND, ata_init, NULL) Index: sys/dev/ata/ata-disk.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-disk.c,v retrieving revision 1.139 diff -u -r1.139 ata-disk.c --- sys/dev/ata/ata-disk.c 2002/12/17 16:26:22 1.139 +++ sys/dev/ata/ata-disk.c 2003/01/27 09:17:04 @@ -255,10 +255,8 @@ disk_invalidate(&adp->disk); disk_destroy(adp->dev); devstat_remove_entry(&adp->stats); - if (flush) { - if (ata_command(atadev, ATA_C_FLUSHCACHE, 0, 0, 0, ATA_WAIT_READY)) - ata_prtdev(atadev, "flushing cache on detach failed\n"); - } + if (flush) + ad_sync(atadev); if (adp->flags & AD_F_RAID_SUBDISK) ata_raiddisk_detach(adp); ata_free_name(atadev); @@ -289,8 +287,7 @@ adp->device->channel->lock_func(adp->device->channel, ATA_LF_LOCK); ATA_SLEEPLOCK_CH(adp->device->channel, ATA_CONTROL); - if (ata_command(adp->device, ATA_C_FLUSHCACHE, 0, 0, 0, ATA_WAIT_READY)) - ata_prtdev(adp->device, "flushing cache on close failed\n"); + ad_sync(adp->device); ATA_UNLOCK_CH(adp->device->channel); adp->device->channel->lock_func(adp->device->channel, ATA_LF_UNLOCK); return 0; @@ -765,6 +762,20 @@ return ATA_OP_CONTINUES; } return ATA_OP_FINISHED; +} + +/* + * Flush the write cache of the given device. + */ +int +ad_sync(struct ata_device *atadev) +{ + int error; + + /* XXX The ATA standard says this command can take up to 30 seconds. */ + if ((error = ata_command(atadev,ATA_C_FLUSHCACHE,0,0,0,ATA_WAIT_READY))) + ata_prtdev(atadev, "flushing cache failed\n"); + return error; } static void Index: sys/dev/ata/ata-disk.h =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-disk.h,v retrieving revision 1.42 diff -u -r1.42 ata-disk.h --- sys/dev/ata/ata-disk.h 2002/07/22 18:35:01 1.42 +++ sys/dev/ata/ata-disk.h 2003/01/27 09:17:04 @@ -80,6 +80,7 @@ void ad_detach(struct ata_device *, int); void ad_reinit(struct ata_device *); void ad_start(struct ata_device *); +int ad_sync(struct ata_device *); int ad_transfer(struct ad_request *); int ad_interrupt(struct ad_request *); int ad_service(struct ad_softc *, int); From owner-freebsd-current@FreeBSD.ORG Sun Mar 30 09:59:28 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9386437B423 for ; Sun, 30 Mar 2003 09:59:28 -0800 (PST) Received: from HAL9000.homeunix.com (12-233-57-131.client.attbi.com [12.233.57.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F04E43F85 for ; Sun, 30 Mar 2003 09:59:22 -0800 (PST) (envelope-from das@FreeBSD.org) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id h2T055ah022203; Fri, 28 Mar 2003 16:05:05 -0800 (PST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id h2T055xO022202; Fri, 28 Mar 2003 16:05:05 -0800 (PST) (envelope-from das@FreeBSD.ORG) Date: Fri, 28 Mar 2003 16:05:05 -0800 From: David Schultz To: Alexander Langer Message-ID: <20030329000505.GB22044@HAL9000.homeunix.com> Mail-Followup-To: Alexander Langer , current@FreeBSD.ORG References: <20030324215712.GA844@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030324215712.GA844@fump.kawo2.rwth-aachen.de> cc: current@FreeBSD.org Subject: Re: several background fsck panics X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Mar 2003 17:59:30 -0000 Thus spake Alexander Langer : > I had several panics related to background fsck now. Once I disabled > background fsck, all went ok. > > It began when I pressed the reset buttons on several boots while the > system was still doing fscks. [...] > Mar 24 21:48:59 fump kernel: panic: ufs_dirbad: bad dir You would have gotten this one without bgfsck as well the next time you tried to look the offending directory. Background fsck only expedited the panic by reading all the directories on the system in order to perform its checks. Basically, the panic is the kernel's way of telling you that something is unexpectedly wrong with the filesystem (due in this case to ATA write caching), and that it is going to give up rather than risk causing further damage. UFS, as well as most other filesystems, are not designed to tolerate failures on the part of the hardware to honor its guarantees, so it's hard to do better without inventing a new filesystem. From owner-freebsd-current@FreeBSD.ORG Sun Mar 30 09:59:30 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0ED0537B40A for ; Sun, 30 Mar 2003 09:59:30 -0800 (PST) Received: from HAL9000.homeunix.com (12-233-57-131.client.attbi.com [12.233.57.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D9C343FB1 for ; Sun, 30 Mar 2003 09:59:28 -0800 (PST) (envelope-from das@FreeBSD.org) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id h2SNquah022168; Fri, 28 Mar 2003 15:52:56 -0800 (PST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id h2SNqo9X022167; Fri, 28 Mar 2003 15:52:50 -0800 (PST) (envelope-from das@FreeBSD.ORG) Date: Fri, 28 Mar 2003 15:52:50 -0800 From: David Schultz To: Terry Lambert Message-ID: <20030328235250.GA22044@HAL9000.homeunix.com> Mail-Followup-To: Terry Lambert , The Anarcat , current@freebsd.org, Alexander Langer References: <20030324215712.GA844@fump.kawo2.rwth-aachen.de> <3E7FE3CE.ECD2775F@mindspring.com> <20030325110843.GF1700@fump.kawo2.rwth-aachen.de> <3E804392.40844D63@mindspring.com> <20030325161632.GB600@lenny.anarcat.ath.cx> <3E810547.3653FFEA@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E810547.3653FFEA@mindspring.com> cc: current@FreeBSD.org cc: Alexander Langer Subject: Re: [Re: several background fsck panics X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Mar 2003 17:59:32 -0000 Thus spake Terry Lambert : > o Put a counter in the first superblock; it would be > incremented when the BG fsck is started, and reset > to zero when it completes. If the counter reaches > 3 (or some command line specified number), then the > BG flagging is ignored, and a full FG fsck is then > performed instead. I like this idea because it will > always work, and it's not actually a hack, it's a > correct solution. I'm glad you like it because AFAIK, it is already implemented. ;-) > o Implement "soft read-only". The place that most of > the complaints are coming from is desktop users, with > relatively quiescent machines. Though swap is used, > it does not occur in an FS partition. As a result, > the FS could be marked "read-only" for long period of > time. This marking would be in memory. The clean bit > would be set on the superblock. When a write occurs, > the clean bit would be reset to "dirty", and committed > to disk prior to the write operation being permitted > to proceed (a stall barrier). I like this idea because, > for the most part, it eliminates fsck, both BG and FG, > on systems that crash while it's in effect. The net > result is a system that is statistically much more > tolerant of failures, but which still requires another > safety net, such as the previous solution. I was thinking of doing something like this myself as part of an ``idle timeout'' for disks. (Marking the filesystem clean after a period of quiescence would actually interfere with ATA disks' built-in mechanism for spinning down after a timeout, which is important for laptops, so the OS would have to track the true amount of idle time.) Annoyingly, I can never get the disk containing /var to remain quiescent for long while cron is running (even without any crontabs), and I hope this can be solved without disabling cron or adding a nontrivial hack to bio. From owner-freebsd-current@FreeBSD.ORG Sun Mar 30 11:46:31 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52C9037B401; Sun, 30 Mar 2003 11:46:31 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id E90B143FB1; Sun, 30 Mar 2003 11:46:30 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id D67EC2A89E; Sun, 30 Mar 2003 11:46:30 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: sos@freebsd.org Date: Sun, 30 Mar 2003 11:46:30 -0800 From: Peter Wemm Message-Id: <20030330194630.D67EC2A89E@canning.wemm.org> cc: alpha@freebsd.org cc: current@freebsd.org Subject: ATA broken on alpha? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Mar 2003 19:46:32 -0000 beast.freebsd.org is panicing at bootup with this: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #81: Sun Mar 30 07:48:29 PST 2003 root@beast.freebsd.org:/usr/src/sys/alpha/compile/BEAST Preloaded elf kernel "/boot/kernel/kernel" at 0xfffffc0000714000. ST6600 AlphaPC 264DP 833 MHz, 833MHz 8192 byte page size, 2 processors. CPU: EV6 (21264) major=8 minor=0 extensions=0x1307 OSF PAL rev: 0x200370002013e real memory = 2144706560 (2045 MB) avail memory = 2081095680 (1984 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs Allocating major#253 to "net" Allocating major#252 to "g_ctl" Allocating major#251 to "pci" tsunami0: <21271 Core Logic chipset> pcib0: <21271 PCI host bus adapter> on tsunami0 pci0: on pcib0 isab0: at device 5.0 on pci0 isa0: on isab0 atapci0: port 0x1300-0x130f,0x3f4-0x3f7,0x1f0-0x1f7 irq 238 at device 5.1 on pci0 fatal kernel trap: trap entry = 0x2 (memory management fault) cpuid = 0 faulting va = 0x0 type = access violation cause = load instructon pc = 0xfffffc000037b0fc ra = 0xfffffc000037b0d0 sp = 0xfffffc000071ba50 usp = 0x0 curthread = 0xfffffc000063d3f8 pid = 0, comm = swapper Stopped at ata_pcisub_probe+0x11c: ldl t0,0(t0) <0x0> db> trace ata_pcisub_probe() at ata_pcisub_probe+0x11c device_probe_child() at device_probe_child+0x114 device_probe_and_attach() at device_probe_and_attach+0x58 bus_generic_attach() at bus_generic_attach+0x28 ata_pci_attach() at ata_pci_attach+0x600 device_probe_and_attach() at device_probe_and_attach+0xc4 bus_generic_attach() at bus_generic_attach+0x28 pci_attach() at pci_attach+0xe0 device_probe_and_attach() at device_probe_and_attach+0xc4 bus_generic_attach() at bus_generic_attach+0x28 device_probe_and_attach() at device_probe_and_attach+0xc4 bus_generic_attach() at bus_generic_attach+0x28 tsunami_attach() at tsunami_attach+0x98 device_probe_and_attach() at device_probe_and_attach+0xc4 root_bus_configure() at root_bus_configure+0x38 configure() at configure+0x40 mi_startup() at mi_startup+0x144 locorestart() at locorestart+0x64 --- root of call graph --- Do you need more details or is that enough of a clue? Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Sun Mar 30 11:56:51 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4FA537B401; Sun, 30 Mar 2003 11:56:51 -0800 (PST) Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 811C643F85; Sun, 30 Mar 2003 11:56:48 -0800 (PST) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.8/8.12.8) id h2UJulHN032136; Sun, 30 Mar 2003 21:56:47 +0200 (CEST) (envelope-from sos) From: Soeren Schmidt Message-Id: <200303301956.h2UJulHN032136@spider.deepcore.dk> In-Reply-To: <20030330194630.D67EC2A89E@canning.wemm.org> To: Peter Wemm Date: Sun, 30 Mar 2003 21:56:47 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL98b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 cc: alpha@FreeBSD.ORG cc: current@FreeBSD.ORG cc: sos@FreeBSD.ORG Subject: Re: ATA broken on alpha? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Mar 2003 19:56:52 -0000 It seems Peter Wemm wrote: > Do you need more details or is that enough of a clue? I can see what the problem is, I'll have to look to find the reason... -Søren From owner-freebsd-current@FreeBSD.ORG Sun Mar 30 14:07:22 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 576D837B401; Sun, 30 Mar 2003 14:07:22 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A40F043FBF; Sun, 30 Mar 2003 14:07:21 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.8/8.12.7) with ESMTP id h2UM7LAm035564; Sun, 30 Mar 2003 14:07:21 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.8/8.12.8/Submit) id h2UM7Kch035563; Sun, 30 Mar 2003 14:07:20 -0800 (PST) Date: Sun, 30 Mar 2003 14:07:20 -0800 From: "David O'Brien" To: Ruslan Ermilov Message-ID: <20030330220720.GB20921@dragon.nuxi.com> Mail-Followup-To: David O'Brien , Ruslan Ermilov , Bruce Evans , current@FreeBSD.org References: <20030313180854.GB47492@sunbay.com> <20030329231905.GA44034@dragon.nuxi.com> <20030330060918.GB43829@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030330060918.GB43829@sunbay.com> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: Bruce Evans cc: current@FreeBSD.org Subject: Re: Do we want to let cpp(1) hide warnings in system headers? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Mar 2003 22:07:23 -0000 On Sun, Mar 30, 2003 at 09:09:18AM +0300, Ruslan Ermilov wrote: > On Sat, Mar 29, 2003 at 03:19:05PM -0800, David O'Brien wrote: > > On Thu, Mar 13, 2003 at 08:08:54PM +0200, Ruslan Ermilov wrote: > > > Sigh. It's been a while since I've fixed the "feature" of gcc(1) > > > that makes it hide warnings in system headers (but visible with > > > -nostdinc -I/usr/include). > > > > What is the difference in output from "make buildworld"? > > > Lot of (non-fatal) warnings. I was hoping you'd acutally show some of the increased warning output. From owner-freebsd-current@FreeBSD.ORG Sun Mar 30 15:23:13 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44CC437B401 for ; Sun, 30 Mar 2003 15:23:13 -0800 (PST) Received: from web14501.mail.yahoo.com (web14501.mail.yahoo.com [216.136.224.64]) by mx1.FreeBSD.org (Postfix) with SMTP id DB5C643F85 for ; Sun, 30 Mar 2003 15:23:12 -0800 (PST) (envelope-from gordonzaft@yahoo.com) Message-ID: <20030330232312.11419.qmail@web14501.mail.yahoo.com> Received: from [69.9.21.224] by web14501.mail.yahoo.com via HTTP; Sun, 30 Mar 2003 15:23:11 PST Date: Sun, 30 Mar 2003 15:23:11 -0800 (PST) From: Gordon Zaft To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Newbie build problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Mar 2003 23:23:14 -0000 Hi, I've been R-ing the FWP but haven't had any luck so far: Specifically, when I try to make buildworld I get: ===> usr.bin/yacc /shared/FreeBSD-current/shared/FreeBSD-current/usr/src/usr.bin/yacc created for /shared/FreeBSD-current/usr/src/usr.bin/yacc sh /shared/FreeBSD-current/usr/src/tools/install.sh -s -o root -g wheel -m 555 yacc /shared/FreeBSD-current/usr/bin sh /shared/FreeBSD-current/usr/src/tools/install.sh -o root -g wheel -m 555 yy fix.sh /shared/FreeBSD-current/usr/bin/yyfix install: /shared/FreeBSD-current/usr/bin/yyfix: Not a directory *** Error code 71 Stop in /shared/FreeBSD-current/usr/src/usr.bin/yacc. *** Error code 1 Stop in /shared/FreeBSD-current/usr/src. *** Error code 1 Stop in /shared/FreeBSD-current/usr/src. *** Error code 1 Stop in /shared/FreeBSD-current/usr/src. This is with the tree cvsup'd into /shared/FreeBSD-current. Am I supposed to create the bin directory by hand? I thought the makefile would build directories it needs. My make.conf looks like this: # -- use.perl generated deltas -- # # Created: Thu Mar 6 04:17:57 2003 # Setting to use base perl from ports: PERL_VER=5.6.1 PERL_VERSION=5.6.1 PERL_ARCH=mach NOPERL=yo NO_PERL=yo NO_PERL_WRAPPER=yo MAKEOBJDIRPREFIX=/shared/FreeBSD-current NOGAMES=true Any pointers would be helpful. I've spent a lot of time on this webpage: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html But it seems to be out of date as some files on it don't exist in 5.0. Thanks for any help! Gordon ===== ------ Gordon Zaft zaft@zaft.org __________________________________________________ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com From owner-freebsd-current@FreeBSD.ORG Sun Mar 30 16:40:54 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91BA237B408 for ; Sun, 30 Mar 2003 16:40:54 -0800 (PST) Received: from mail1.arcor-ip.de (mail1.arcor-ip.de [145.253.2.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 766AF43F93 for ; Sun, 30 Mar 2003 16:40:53 -0800 (PST) (envelope-from Friedemann.Becker@student.uni-tuebingen.de) Received: from chasey (213.23.49.203) by mail1.arcor-ip.de (5.5.034) id 3E1E8763004F6892 for freebsd-current@freebsd.org; Mon, 31 Mar 2003 02:40:52 +0200 Date: Mon, 31 Mar 2003 02:40:29 +0200 (=?ISO-8859-1?Q?Westeurop=E4ische_Sommerzeit?=) From: Friedemann Becker To: freebsd-current@freebsd.org Message-ID: X-X-Sender: zxmxy33@mailserv02.uni-tuebingen.de MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: Problems with clock (fwd) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Friedemann.Becker@student.uni-tuebingen.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 00:41:26 -0000 ---------- Forwarded message ---------- Date: Fri, 28 Mar 2003 23:18:35 +0100 (CET) From: Friedemann Becker To: Andris Subject: Re: Problems with clock Try this one. I had the same problem, and de fix described put the clock back to normal operation. http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/32226 On Fri, 28 Mar 2003, Andris wrote: > Hi everyone! > > I have strange problems with my PC clock. Clock seems to be ~2 times faster. > > What's up? > > Andris > > Here is dmesg output: > > Copyright (c) 1992-2003 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.0-RELEASE-p6 #0: Fri Mar 28 11:45:46 EET 2003 > root@mezhs.buts.lv:/usr/obj/usr/src/sys/MEZHS > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0407000. > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04070a8. > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 333516074 Hz > CPU: AMD-K6(tm) 3D processor (333.52-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 > Features=0x8021bf > AMD Features=0xffffffff80000800 > real memory = 134152192 (127 MB) > avail memory = 125931520 (120 MB) > Initializing GEOMetry subsystem > K6-family MTRR support enabled (2 registers) > VESA: v1.2, 2048k memory, flags:0x0, mode table:0xc00c4eeb (c0004eeb) > VESA: S3 Incorporated. 86C775/86C785 > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 > ACPI-0625: *** Info: GPE Block1 defined as GPE16 to GPE31 > Using $PIR table, 6 entries at 0xc00f7c40 > acpi0: power button is handled as a fixed feature programming model. > Timecounter "ACPI-safe" frequency 3579545 Hz > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 > acpi_cpu0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > agp0: mem 0xd0000000-0xd1ffffff at device 0.0 > on pci0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci0: at device 3.0 (no driver attached) > isab0: at device 7.0 on pci0 > isa0: on isab0 > pci0: at device 8.0 (no driver attached) > rl0: port 0xdc00-0xdcff mem > 0xebfeff00-0xebfeffff irq 10 at device 9.0 on pci0 > rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect > mode > rl0: Ethernet address: 00:30:4f:16:8f:79 > miibus0: on rl0 > rlphy0: on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ed0: port 0xdf80-0xdf9f irq 9 at device > 10.0 on pci0 > ed0: address 00:48:45:00:07:9e, type NE2000 (16 bit) > atapci0: port 0xffa0-0xffaf at device > 15.0 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > acpi_button0: on acpi0 > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > fdc0: cmd 3 failed at out byte 1 of 3 > ppc0 port 0x378-0x37f irq 7 on acpi0 > ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode > lpt0: on ppbus0 > lpt0: Interrupt-driven port > sio0 port 0x3f8-0x3ff irq 4 on acpi0 > sio0: type 16550A > sio1 port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > fdc0: cmd 3 failed at out byte 1 of 3 > orm0: #include #include using namespace std; int main(void) { cout << isnan(1.0) << endl; return 0; } test.cpp: In function `int main()': test.cpp:8: `isnan' undeclared (first use this function) test.cpp:8: (Each undeclared identifier is reported only once for each function it appears in.) what's wrong with my system ? or what can I do for it ? -- int i;main(){for(;i["] Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F32C637B404 for ; Mon, 31 Mar 2003 00:14:35 -0800 (PST) Received: from mail.cordis.lu (mail.cordis.lu [212.190.217.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69A9443FAF for ; Mon, 31 Mar 2003 00:14:33 -0800 (PST) (envelope-from a.carter@cordis.lu) Received: from mailsvr.intrasoft.lu (mail.intrasoft.lu [212.190.217.251]) by mail.cordis.lu (8.12.8/8.12.8) with ESMTP id h2V8H9qE032153 for ; Mon, 31 Mar 2003 10:17:09 +0200 Received: by mail.intrasoft.lu with Internet Mail Service (5.5.2656.59) id ; Mon, 31 Mar 2003 10:12:07 +0200 Received: from intra241.intrasoft.lu (212.190.217.170 [212.190.217.170]) by mailsvr.intrasoft.lu with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59) id HXZK8N0Y; Mon, 31 Mar 2003 10:12:02 +0200 From: CARTER Anthony To: freebsd-current@freebsd.org Organization: Intrasoft Date: Mon, 31 Mar 2003 10:19:53 +0200 User-Agent: KMail/1.5 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200303311019.53522.a.carter@intrasoft.lu> X-Spam-Status: No, hits=-126.1 required=4.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT,USER_IN_WHITELIST version=2.50 X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: Re: kdm & xdm problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 08:14:38 -0000 You do not need the wrapper to login via kdm or gdm. What version are you using of gdm? Versions prior to 2 of GDM can be launched from ttys, but the latest versions require (are recommended???) the shell script that is installed to be run. Anthony On Sunday 30 March 2003 05:08, Dane Butler wrote: > Hey, my name is Dane. > > I have been a Linux user for a few years and have been trying out FreeBSD > 5.0, but there is a problem. I edited the /etc/ttys file as instructed to > make kdm (and xdm) boot, but as soon as i login, x crashes and reboots, how > do i get around this? > > _________________________________________________________________ > Hotmail now available on Australian mobile phones. Go to > http://ninemsn.com.au/mobilecentral/hotmail_mobile.asp > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 00:44:46 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D35C37B401; Mon, 31 Mar 2003 00:44:46 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-150.dsl.lsan03.pacbell.net [63.207.60.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A4A343F75; Mon, 31 Mar 2003 00:44:45 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id C5F0066CFA; Mon, 31 Mar 2003 00:44:44 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 9DCCE12A5; Mon, 31 Mar 2003 00:44:44 -0800 (PST) Date: Mon, 31 Mar 2003 00:44:44 -0800 From: Kris Kennaway To: Ying-Chieh Liao Message-ID: <20030331084444.GB44857@rot13.obsecurity.org> References: <20030331064605.GA42030@terry.dragon2.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RASg3xLB4tUQ4RcS" Content-Disposition: inline In-Reply-To: <20030331064605.GA42030@terry.dragon2.net> User-Agent: Mutt/1.4i cc: questions@FreeBSD.org cc: current@FreeBSD.org Subject: Re: isnan() with gcc 3.2.2 on FreeBSD 5.0-C X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 08:44:48 -0000 --RASg3xLB4tUQ4RcS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Mar 31, 2003 at 02:46:05PM +0800, Ying-Chieh Liao wrote: > what's wrong with my system ? or what can I do for it ? See Message-ID: <20030320202706.A35844@dilbert.robbins.dropbear.id.au> Kris --RASg3xLB4tUQ4RcS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+h//8Wry0BWjoQKURAkQMAKCk+BbuQqOHJ02JeljEyOFHgG4jQwCfQlct WBU6P5hJL/Ao1PTmcMCP3EM= =0sAP -----END PGP SIGNATURE----- --RASg3xLB4tUQ4RcS-- From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 00:49:39 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A75D37B401; Mon, 31 Mar 2003 00:49:39 -0800 (PST) Received: from fafoe.dyndns.org (chello212186121237.14.vie.surfer.at [212.186.121.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CF7B43F93; Mon, 31 Mar 2003 00:49:38 -0800 (PST) (envelope-from stefan@fafoe.dyndns.org) Received: from frog.fafoe (frog.fafoe [192.168.2.101]) by fafoe.dyndns.org (Postfix) with ESMTP id 1F1393FA9; Mon, 31 Mar 2003 10:49:36 +0200 (CEST) Received: by frog.fafoe (Postfix, from userid 1001) id 8C106521; Mon, 31 Mar 2003 10:49:35 +0200 (CEST) Date: Mon, 31 Mar 2003 10:49:35 +0200 From: Stefan Farfeleder To: Ying-Chieh Liao Mail-Followup-To: Ying-Chieh Liao , questions@FreeBSD.org, current@FreeBSD.org References: <20030331064605.GA42030@terry.dragon2.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030331064605.GA42030@terry.dragon2.net> User-Agent: Mutt/1.5.4i Message-Id: <20030331084936.1F1393FA9@fafoe.dyndns.org> cc: questions@FreeBSD.org cc: current@FreeBSD.org Subject: Re: isnan() with gcc 3.2.2 on FreeBSD 5.0-C X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 08:49:40 -0000 On Mon, Mar 31, 2003 at 02:46:05PM +0800, Ying-Chieh Liao wrote: > the following code snippet works fine with gcc 2.95.4 on RELENG_4 > but failed on my -current > > > #include > #include > > using namespace std; > > int main(void) > { > cout << isnan(1.0) << endl; > return 0; > } > > > > test.cpp: In function `int main()': > test.cpp:8: `isnan' undeclared (first use this function) > test.cpp:8: (Each undeclared identifier is reported only once for each function > it appears in.) > > > what's wrong with my system ? or what can I do for it ? The isnan() macro is a new feature of C99 and thus not (yet) part of C++. Nevertheless you can use -D_GLIBCPP_USE_C99 to include this and some other non-standard C++ features. Regards, Stefan Farfeleder From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 01:25:39 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AFD237B404 for ; Mon, 31 Mar 2003 01:25:39 -0800 (PST) Received: from smtp1.Stanford.EDU (smtp1.Stanford.EDU [171.64.14.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1838443F85 for ; Mon, 31 Mar 2003 01:25:39 -0800 (PST) (envelope-from jstockdale@stanford.edu) Received: from quenya (quenya.Stanford.EDU [128.12.44.61]) by smtp1.Stanford.EDU (8.12.9/8.12.9) with ESMTP id h2V9PaZA006050 for ; Mon, 31 Mar 2003 01:25:36 -0800 (PST) From: "John Stockdale" To: Date: Mon, 31 Mar 2003 01:25:37 -0800 Message-ID: <001001c2f767$7d770740$3d2c0c80@quenya> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: buildworld problem (source cvsup around 10:00pm march 30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 09:25:42 -0000 I'm running FreeBSD 5.0-CURRENT, and just updated my source tree from cvsup10.freebsd.org about 3 hours ago. Upon make buildworld, the make runs fine for about an hour, then spits out: ===> etc ===> etc/sendmail make: don't know how to make freebsd.mc. Stop *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Any help/suggestions would be appreciated. Thanks. -John From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 02:07:17 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B7E137B404 for ; Mon, 31 Mar 2003 02:07:17 -0800 (PST) Received: from freebsd.org.ru (sweet.etrust.ru [194.84.67.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 746BD43FB1 for ; Mon, 31 Mar 2003 02:07:16 -0800 (PST) (envelope-from osa@freebsd.org.ru) Received: by freebsd.org.ru (Postfix, from userid 1000) id 1DD6623; Mon, 31 Mar 2003 14:07:15 +0400 (MSD) Date: Mon, 31 Mar 2003 14:07:15 +0400 From: "Sergey A. Osokin" To: John Stockdale Message-ID: <20030331100715.GN37187@freebsd.org.ru> References: <001001c2f767$7d770740$3d2c0c80@quenya> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001001c2f767$7d770740$3d2c0c80@quenya> User-Agent: Mutt/1.5.4i cc: freebsd-current@FreeBSD.ORG Subject: Re: buildworld problem (source cvsup around 10:00pm march 30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: osa@FreeBSD.org.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 10:07:18 -0000 On Mon, Mar 31, 2003 at 01:25:37AM -0800, John Stockdale wrote: > I'm running FreeBSD 5.0-CURRENT, and just updated my source tree from > cvsup10.freebsd.org about 3 hours ago. Upon make buildworld, the make > runs fine for about an hour, then spits out: > > ===> etc > ===> etc/sendmail > make: don't know how to make freebsd.mc. Stop > *** Error code 2 > 1 error > > Any help/suggestions would be appreciated. Do you have SENDMAIL_MC in your /etc/make.conf ? -- Rgdz, /"\ ASCII RIBBON CAMPAIGN Sergey Osokin aka oZZ, \ / AGAINST HTML MAIL http://ozz.pp.ru/ X AND NEWS / \ From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 03:01:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1581837B404 for ; Mon, 31 Mar 2003 03:01:32 -0800 (PST) Received: from mta02.mail.mel.aone.net.au (mta02.mail.au.uu.net [203.2.192.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5298F43FE3 for ; Mon, 31 Mar 2003 03:01:27 -0800 (PST) (envelope-from rbyrnes@ozemail.com.au) Received: from pootah.ozemail.com.au ([63.60.5.101]) by mta02.mail.mel.aone.net.au with ESMTP <20030331110124.FALT3633.mta02.mail.mel.aone.net.au@pootah.ozemail.com.au>; Mon, 31 Mar 2003 21:01:24 +1000 Message-Id: <5.2.0.9.2.20030331205816.0263bec0@127.0.0.1> X-Sender: rbyrnes@pop.ozemail.com.au@127.0.0.1 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Mon, 31 Mar 2003 20:59:54 +1000 To: Glenn Johnson From: Rob B In-Reply-To: <20030331015951.GA2878@gforce.johnson.home> References: <5.2.0.9.2.20030331103734.0261e310@127.0.0.1> <20030328185710.GA805@node1.cluster.srrc.usda.gov> <5.2.0.9.2.20030331103734.0261e310@127.0.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: current@freebsd.org Subject: Re: ypserv and sshd not getting along in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 11:01:39 -0000 At 11:59 AM 31/03/03, Glenn Johnson sent this up the stick: >On Mon, Mar 31, 2003 at 10:46:07AM +1000, Rob B wrote: > > > At 02:55 PM 29/03/03, Terry Lambert sent this up the stick: > > > > > >man ypbind > > > > > >(-s is the magic incantation). > > > > > Mar 31 10:10:39 erwin ypserv[92]: access to master.passwd.byuid denied -- > > client 192.168.100.30:49255 not privileged > > > > Why would the request be coming from a high port when I have > > specifically told it to bind to a low port? > >The answer (work around) is to turn off PrivelegeSeparation in your >sshd_config file. That got it, thanks Rob -- Two prostitutes standing on a street corner. One says to the other, "Have you ever been picked up by the fuzz?" The other replies, "No, but I've been swung around by the boobs a few times!" This is random quote 1117 of 1254. Distance from the centre of the brewing universe [15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian Public Key fingerprint = 6219 33BD A37B 368D 29F5 19FB 945D C4D7 1F66 D9C5 From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 03:15:54 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 988EE37B401 for ; Mon, 31 Mar 2003 03:15:54 -0800 (PST) Received: from main.evrocom.net (main.evrocom.net [212.39.92.2]) by mx1.FreeBSD.org (Postfix) with SMTP id 8278143FD7 for ; Mon, 31 Mar 2003 03:15:52 -0800 (PST) (envelope-from veno@evrocom.net) Received: (qmail 35687 invoked from network); 31 Mar 2003 11:15:50 -0000 Received: from unknown (HELO beatle) (217.10.240.35) by main.evrocom.net with SMTP; 31 Mar 2003 11:15:50 -0000 Message-ID: <006401c2f776$d16f0230$23f00ad9@beatle> From: "Ventsislav Velkov" To: Date: Mon, 31 Mar 2003 14:15:21 +0300 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: problem updating from 4.7 Stable do 5.0 Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 11:15:56 -0000 Hello all, I have a problem updating one of our servers from 4.7Stable to = 5.0Current. It is a Compaq Proliant 7000 Server with 4 Xeons @500Mhz with 2MB L2 = cache each. I has a 4200 Compaq Smart Raid Controler with attached 3 U1 Storages.=20 I update the src rebuild the world from updated src to 5.0Current, build = a GENERIC kernel and installed it. But after I boot it brokes up during the booting process with the = following error: //strip Fatal trap 12: page fault while in kernel mode cpuid=3D0; lapic.id=3D = 01000000 fault virtual address =3D 0x54 fault code =3D supervisor read, page not present .... .... .... process eflags =3D interrupt enabled, resume, IOPL=3D0 current process =3D 4(g_down) kernel: type12trap, code=3D0 Stopped at ida_construct_qcb+0xe3: movzbl 0x54(%eax),%eax //strip It may have some punctual mistakes because it is not a copy/paste. Will appreciate any advices where could be the problem. Best regards, Veno From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 04:10:08 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FF6737B401 for ; Mon, 31 Mar 2003 04:10:08 -0800 (PST) Received: from mail.cordis.lu (mail.cordis.lu [212.190.217.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC38443F75 for ; Mon, 31 Mar 2003 04:10:06 -0800 (PST) (envelope-from a.carter@cordis.lu) Received: from mailsvr.intrasoft.lu (mail.intrasoft.lu [212.190.217.251]) by mail.cordis.lu (8.12.8/8.12.8) with ESMTP id h2VCCjqE007295 for ; Mon, 31 Mar 2003 14:12:45 +0200 Received: by mail.intrasoft.lu with Internet Mail Service (5.5.2656.59) id ; Mon, 31 Mar 2003 14:07:40 +0200 Received: from intra241.intrasoft.lu (212.190.217.170 [212.190.217.170]) by mailsvr.intrasoft.lu with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59) id HXZK830M; Mon, 31 Mar 2003 14:07:36 +0200 From: CARTER Anthony To: freebsd-current@freebsd.org Organization: Intrasoft Date: Mon, 31 Mar 2003 14:15:27 +0200 User-Agent: KMail/1.5 References: <006401c2f776$d16f0230$23f00ad9@beatle> In-Reply-To: <006401c2f776$d16f0230$23f00ad9@beatle> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200303311415.27166.a.carter@intrasoft.lu> X-Spam-Status: No, hits=-126.1 required=4.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT,USER_IN_WHITELIST version=2.50 X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: Re: problem updating from 4.7 Stable do 5.0 Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 12:10:40 -0000 Have you installed the world? I don't know if just rebuilding it is sufficient.... To install the world you have to go to single user mode and run mergemaster to update any changes in configuration files (take a backup of your current files as it overwrites them). Anthony On Monday 31 March 2003 13:15, Ventsislav Velkov wrote: > Hello all, > > I have a problem updating one of our servers from 4.7Stable to 5.0Current. > It is a Compaq Proliant 7000 Server with 4 Xeons @500Mhz with 2MB L2 cache > each. I has a 4200 Compaq Smart Raid Controler with attached 3 U1 Storages. > I update the src rebuild the world from updated src to 5.0Current, build a > GENERIC kernel and installed it. But after I boot it brokes up during the > booting process with the following error: > > //strip > > Fatal trap 12: page fault while in kernel mode cpuid=0; lapic.id= 01000000 > fault virtual address = 0x54 > fault code = supervisor read, page not present > .... > .... > .... > process eflags = interrupt enabled, resume, IOPL=0 > current process = 4(g_down) > kernel: type12trap, code=0 > Stopped at ida_construct_qcb+0xe3: movzbl 0x54(%eax),%eax > > //strip > > It may have some punctual mistakes because it is not a copy/paste. > > Will appreciate any advices where could be the problem. > > Best regards, > > Veno > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 04:46:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47E5737B401; Mon, 31 Mar 2003 04:46:04 -0800 (PST) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF10043F93; Mon, 31 Mar 2003 04:46:03 -0800 (PST) (envelope-from leimy2k@mac.com) Received: from asmtp01.mac.com (asmtp01-qfe3 [10.13.10.65]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id h2VCk3DU003899; Mon, 31 Mar 2003 04:46:03 -0800 (PST) Received: from mac.com ([66.156.161.248]) by asmtp01.mac.com (Netscape Messaging Server 4.15) with ESMTP id HCM64Q00.30P; Mon, 31 Mar 2003 04:46:02 -0800 Date: Mon, 31 Mar 2003 06:46:01 -0600 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) To: Stefan Farfeleder From: David Leimbach In-Reply-To: <20030331084936.1F1393FA9@fafoe.dyndns.org> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.551) cc: questions@freebsd.org cc: Ying-Chieh Liao cc: current@freebsd.org Subject: Re: isnan() with gcc 3.2.2 on FreeBSD 5.0-C X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 12:46:06 -0000 On Monday, March 31, 2003, at 02:49 AM, Stefan Farfeleder wrote: > > The isnan() macro is a new feature of C99 and thus not (yet) part of > C++. Nevertheless you can use -D_GLIBCPP_USE_C99 to include this and There may be no guarantee that any new parts of C99 ever make it into the C++ language. C++ has always been a superset of a subset of C :). That is to say that C is not 100% contained within C++. This has gotten to be more of a problem since the C99 standard has added things the C++ already had as well such as _Complex and the very weird tgmath.h header that seemingly cannot even be written with standard C. [I have seen the version that came with RedHat linux and it involved a bunch of gcc specific code]. Anyway... Its a real world problem now and the errors people are seeing are due to the fact that g++-3.x is more standards compliant than 2.x was. Dave From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 05:04:45 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C903137B401 for ; Mon, 31 Mar 2003 05:04:45 -0800 (PST) Received: from main.evrocom.net (main.evrocom.net [212.39.92.2]) by mx1.FreeBSD.org (Postfix) with SMTP id C544F43FBF for ; Mon, 31 Mar 2003 05:04:34 -0800 (PST) (envelope-from veno@evrocom.net) Received: (qmail 45947 invoked from network); 31 Mar 2003 13:04:27 -0000 Received: from unknown (HELO beatle) (217.10.240.35) by main.evrocom.net with SMTP; 31 Mar 2003 13:04:27 -0000 Message-ID: <00ad01c2f785$fe095250$23f00ad9@beatle> From: "Ventsislav Velkov" To: "CARTER Anthony" References: <006401c2f776$d16f0230$23f00ad9@beatle> <200303311415.27166.a.carter@intrasoft.lu> Date: Mon, 31 Mar 2003 16:03:58 +0300 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-current@FreeBSD.ORG Subject: Re: problem updating from 4.7 Stable do 5.0 Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 13:04:47 -0000 I could not boot in single user mode with the 5.0 kernel because it = brokes. Do you mean I should boot in single user with the 4.7 kernel in there = installworld and to mergemaster ? regards, Veno ----- Original Message -----=20 From: CARTER Anthony=20 To: freebsd-current@freebsd.org=20 Sent: Monday, March 31, 2003 3:15 PM Subject: Re: problem updating from 4.7 Stable do 5.0 Current Have you installed the world? I don't know if just rebuilding it is=20 sufficient.... To install the world you have to go to single user mode and run = mergemaster to=20 update any changes in configuration files (take a backup of your = current=20 files as it overwrites them). Anthony On Monday 31 March 2003 13:15, Ventsislav Velkov wrote: > Hello all, > > I have a problem updating one of our servers from 4.7Stable to = 5.0Current. > It is a Compaq Proliant 7000 Server with 4 Xeons @500Mhz with 2MB L2 = cache > each. I has a 4200 Compaq Smart Raid Controler with attached 3 U1 = Storages. > I update the src rebuild the world from updated src to 5.0Current, = build a > GENERIC kernel and installed it. But after I boot it brokes up = during the > booting process with the following error: > > //strip > > Fatal trap 12: page fault while in kernel mode cpuid=3D0; = lapic.id=3D 01000000 > fault virtual address =3D 0x54 > fault code =3D supervisor read, page not present > .... > .... > .... > process eflags =3D interrupt enabled, resume, IOPL=3D0 > current process =3D 4(g_down) > kernel: type12trap, code=3D0 > Stopped at ida_construct_qcb+0xe3: movzbl 0x54(%eax),%eax > > //strip > > It may have some punctual mistakes because it is not a copy/paste. > > Will appreciate any advices where could be the problem. > > Best regards, > > Veno > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 05:08:14 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C030337B401 for ; Mon, 31 Mar 2003 05:08:14 -0800 (PST) Received: from sbk-gw.sibnet.ru (sbk-gw.sibnet.ru [217.70.96.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DF3D43F85 for ; Mon, 31 Mar 2003 05:08:13 -0800 (PST) (envelope-from stranger@sberbank.sibnet.ru) Received: from sbk-gw.sibnet.ru (localhost.sibnet.ru [127.0.0.1]) by sbk-gw.sibnet.ru (8.12.6/8.12.6) with ESMTP id h2VD8QuI072675; Mon, 31 Mar 2003 20:08:26 +0700 (NOVST) (envelope-from stranger@sberbank.sibnet.ru) Received: from localhost (stranger@localhost)h2VD8QY1072672; Mon, 31 Mar 2003 20:08:26 +0700 (NOVST) X-Authentication-Warning: sbk-gw.sibnet.ru: stranger owned process doing -bs Date: Mon, 31 Mar 2003 20:08:26 +0700 (NOVST) From: "Maxim M. Kazachek" X-X-Sender: stranger@sbk-gw.sibnet.ru To: Ventsislav Velkov In-Reply-To: <00ad01c2f785$fe095250$23f00ad9@beatle> Message-ID: <20030331200734.O72671@sbk-gw.sibnet.ru> References: <006401c2f776$d16f0230$23f00ad9@beatle> <200303311415.27166.a.carter@intrasoft.lu> <00ad01c2f785$fe095250$23f00ad9@beatle> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: problem updating from 4.7 Stable do 5.0 Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 13:08:16 -0000 What your server do when it panics? It tries to detect disks? Sincerely, Maxim M. Kazachek mailto:stranger@sberbank.sibnet.ru mailto:stranger@fpm.ami.nstu.ru On Mon, 31 Mar 2003, Ventsislav Velkov wrote: >I could not boot in single user mode with the 5.0 kernel because it brokes. >Do you mean I should boot in single user with the 4.7 kernel in there installworld and to mergemaster ? > >regards, >Veno > ----- Original Message ----- > From: CARTER Anthony > To: freebsd-current@freebsd.org > Sent: Monday, March 31, 2003 3:15 PM > Subject: Re: problem updating from 4.7 Stable do 5.0 Current > > > Have you installed the world? I don't know if just rebuilding it is > sufficient.... > > To install the world you have to go to single user mode and run mergemaster to > update any changes in configuration files (take a backup of your current > files as it overwrites them). > > Anthony > > On Monday 31 March 2003 13:15, Ventsislav Velkov wrote: > > Hello all, > > > > I have a problem updating one of our servers from 4.7Stable to 5.0Current. > > It is a Compaq Proliant 7000 Server with 4 Xeons @500Mhz with 2MB L2 cache > > each. I has a 4200 Compaq Smart Raid Controler with attached 3 U1 Storages. > > I update the src rebuild the world from updated src to 5.0Current, build a > > GENERIC kernel and installed it. But after I boot it brokes up during the > > booting process with the following error: > > > > //strip > > > > Fatal trap 12: page fault while in kernel mode cpuid=0; lapic.id= 01000000 > > fault virtual address = 0x54 > > fault code = supervisor read, page not present > > .... > > .... > > .... > > process eflags = interrupt enabled, resume, IOPL=0 > > current process = 4(g_down) > > kernel: type12trap, code=0 > > Stopped at ida_construct_qcb+0xe3: movzbl 0x54(%eax),%eax > > > > //strip > > > > It may have some punctual mistakes because it is not a copy/paste. > > > > Will appreciate any advices where could be the problem. > > > > Best regards, > > > > Veno > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 05:27:27 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89CB537B401 for ; Mon, 31 Mar 2003 05:27:27 -0800 (PST) Received: from mail.cordis.lu (mail.cordis.lu [212.190.217.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27FD743FD7 for ; Mon, 31 Mar 2003 05:27:26 -0800 (PST) (envelope-from a.carter@cordis.lu) Received: from mailsvr.intrasoft.lu (mail.intrasoft.lu [212.190.217.251]) by mail.cordis.lu (8.12.8/8.12.8) with ESMTP id h2VDTxqE010100; Mon, 31 Mar 2003 15:29:59 +0200 Received: by mail.intrasoft.lu with Internet Mail Service (5.5.2656.59) id ; Mon, 31 Mar 2003 15:24:54 +0200 Received: from intra241.intrasoft.lu (212.190.217.170 [212.190.217.170]) by mailsvr.intrasoft.lu with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59) id HXZK8PL9; Mon, 31 Mar 2003 15:24:50 +0200 From: CARTER Anthony To: Ventsislav Velkov , CARTER Anthony Organization: Intrasoft Date: Mon, 31 Mar 2003 15:32:41 +0200 User-Agent: KMail/1.5 References: <006401c2f776$d16f0230$23f00ad9@beatle> <200303311415.27166.a.carter@intrasoft.lu> <00ad01c2f785$fe095250$23f00ad9@beatle> In-Reply-To: <00ad01c2f785$fe095250$23f00ad9@beatle> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200303311532.41300.a.carter@intrasoft.lu> X-Spam-Status: No, hits=-126.1 required=4.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT,USER_IN_WHITELIST version=2.50 X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: freebsd-current@FreeBSD.ORG Subject: Re: problem updating from 4.7 Stable do 5.0 Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 13:27:30 -0000 Process: Boot up normally with 4.7 kernel. DO THIS: rm -rf /usr/obj/* (removes compiled files) rm -rf /tmp/* Add COMPAT_FREEBSD4 to your kernel configuration file. make buildworld make buildkernel KERNCONF=YOURKERNELFILE cp /usr/src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints (MACHINE = i386, powerpc, ia64 etc depending on architecture. check out the directory first) make installkernel KERNCONF=YOURKERNELFILE #The next line installs the 5.x boot loader. cd /usr/src/sys/boot; make install reboot. Hit a key at boot (other than Enter) Type: boot -s This will boot into single user mode with your new kernel. fsck -p mount -u / mount -a mergemaster -p rm -rf /usr/include/g++ make installworld mergemaster PLEASE NOTE: Your should REALLY REALLY read the /usr/src/UPDATING file. All the information given here is taken from that file...You should read that file to find out if there are any particular entries that are relevent to your platform. The first few pages are updates to versions of FreeBSD, you can ignore these really and scroll to the bottom where the upgrade processes are described. Good Luck, Anthony Carter Yeah. When booting the computer and it tells you to press Enter to boot or any other blah blah, hit any key (not enter ;)) and type boot -s name_of_4.7_kernel this will boot into single usermode. Then, do this: fsck -p mount -u / On Monday 31 March 2003 15:03, Ventsislav Velkov wrote: > I could not boot in single user mode with the 5.0 kernel because it > brokes. > Do you mean I should boot in single user with the 4.7 kernel in there > installworld and to mergemaster ? > > regards, > Veno > > ----- Original Message ----- > From: CARTER Anthony > To: freebsd-current@freebsd.org > Sent: Monday, March 31, 2003 3:15 PM > Subject: Re: problem updating from 4.7 Stable do 5.0 Current > > Have you installed the world? I don't know if just rebuilding it is > sufficient.... > > To install the world you have to go to single user mode and run > mergemaster to > update any changes in configuration files (take a backup of your current > > files as it overwrites them). > > Anthony > > On Monday 31 March 2003 13:15, Ventsislav Velkov wrote: > > Hello all, > > > > I have a problem updating one of our servers from 4.7Stable to > > 5.0Current. > > > It is a Compaq Proliant 7000 Server with 4 Xeons @500Mhz with 2MB L2 > > cache > > > each. I has a 4200 Compaq Smart Raid Controler with attached 3 U1 > > Storages. > > > I update the src rebuild the world from updated src to 5.0Current, > > build a > > > GENERIC kernel and installed it. But after I boot it brokes up during > > the > > > booting process with the following error: > > > > //strip > > > > Fatal trap 12: page fault while in kernel mode cpuid=0; lapic.id= > > 01000000 > > > fault virtual address = 0x54 > > fault code = supervisor read, page not present > > .... > > .... > > .... > > process eflags = interrupt enabled, resume, IOPL=0 > > current process = 4(g_down) > > kernel: type12trap, code=0 > > Stopped at ida_construct_qcb+0xe3: movzbl 0x54(%eax),%eax > > > > //strip > > > > It may have some punctual mistakes because it is not a copy/paste. > > > > Will appreciate any advices where could be the problem. > > > > Best regards, > > > > Veno > > _______________________________________________ > > freebsd-current@freebsd.org > > mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > > To unsubscribe, send any mail to " > > freebsd-current-unsubscribe@freebsd.org > " > _______________________________________________ > freebsd-current@freebsd.org > mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org > " From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 06:26:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4761E37B401 for ; Mon, 31 Mar 2003 06:26:38 -0800 (PST) Received: from main.evrocom.net (main.evrocom.net [212.39.92.2]) by mx1.FreeBSD.org (Postfix) with SMTP id D4CA443F85 for ; Mon, 31 Mar 2003 06:26:13 -0800 (PST) (envelope-from veno@evrocom.net) Received: (qmail 52444 invoked from network); 31 Mar 2003 14:26:06 -0000 Received: from unknown (HELO beatle) (217.10.240.35) by main.evrocom.net with SMTP; 31 Mar 2003 14:26:06 -0000 Message-ID: <011501c2f791$6607c8e0$23f00ad9@beatle> From: "Ventsislav Velkov" To: "Maxim M. Kazachek" References: <006401c2f776$d16f0230$23f00ad9@beatle><200303311415.27166.a.carter@intrasoft.lu><00ad01c2f785$fe095250$23f00ad9@beatle> <20030331200734.O72671@sbk-gw.sibnet.ru> <00be01c2f787$93f8d8c0$23f00ad9@beatle> <20030331212152.D72882@sbk-gw.sibnet.ru> Date: Mon, 31 Mar 2003 17:25:37 +0300 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-current@FreeBSD.ORG Subject: Re: problem updating from 4.7 Stable do 5.0 Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 14:26:39 -0000 I am on the same opinion also, but only the maintainer of the driver = could confirm. From: Maxim M. Kazachek=20 To: Ventsislav Velkov=20 Sent: Monday, March 31, 2003 5:22 PM Subject: Re: problem updating from 4.7 Stable do 5.0 Current Seems that the problem is in ida driver which runs your disk array... Sincerely, Maxim M. Kazachek mailto:stranger@sberbank.sibnet.ru mailto:stranger@fpm.ami.nstu.ru From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 07:04:14 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C046F37B401 for ; Mon, 31 Mar 2003 07:04:14 -0800 (PST) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F56F43F93 for ; Mon, 31 Mar 2003 07:04:05 -0800 (PST) (envelope-from ru@whale.sunbay.crimea.ua) Received: from whale.sunbay.crimea.ua (ru@localhost [127.0.0.1]) h2VF3mAP035219 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Mar 2003 18:03:52 +0300 (EEST) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.12.8/8.12.8/Submit) id h2VF3mpD035214; Mon, 31 Mar 2003 18:03:48 +0300 (EEST) (envelope-from ru) Date: Mon, 31 Mar 2003 18:03:48 +0300 From: Ruslan Ermilov To: Makoto Matsushita Message-ID: <20030331150348.GD21700@sunbay.com> References: <20030329190908R.matusita@jp.FreeBSD.org> <3E857E9C.F7476A32@mindspring.com> <20030329203005.GB94956@sunbay.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Km1U/tdNT/EmXiR1" Content-Disposition: inline In-Reply-To: <20030329203005.GB94956@sunbay.com> User-Agent: Mutt/1.5.4i cc: current@freebsd.org Subject: Re: FreeBSD/alpha kern.flp flood X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 15:04:16 -0000 --Km1U/tdNT/EmXiR1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 29, 2003 at 10:30:05PM +0200, Ruslan Ermilov wrote: > On Sat, Mar 29, 2003 at 03:08:12AM -0800, Terry Lambert wrote: > > Makoto Matsushita wrote: > > > It seems that kern.flp for FreeBSD/alpha is flooded (tested on FreeBS= D/i386). > > > Maybe several kbytes should be removed from the kernel: > > [ ... ] > > > -r-xr-xr-x 1 root wheel 1223388 Mar 28 00:57 kernel.gz > > > -r-xr-xr-x 1 root wheel 200864 Mar 28 00:57 loader > > [ ... ] > > > Anybody have an idea to reduce the size? > >=20 > > In theory, you could boot the kernel directly, without the > > loader. For that to work, though, you would need to do some > > extra work, but that would get you 200K back. > >=20 > bde@ had patches for i386 that obviate the need of loader(8). >=20 > > You might also consider stripping the kernel, if it's not > > stripped already; that will break some things, but probably > > not things you care about when booting from a floppy. > >=20 > It's already stripped. Stripping the .comment section > saves me 400K for my i386 kernel. >=20 I was lying, only 12K or so. I didn't know that "strip -R" also does the usual stripping. Anyway, I've committed the fix to release/Makefile that strips the .comment section out from the BOOTMFS kernel. If you have time, you can exploit the effect of this by changing sweaping over src/sys/ and changing rcsid =3D "$FreeBSD$" lines to be __FBSDID() -- that would put these IDs in the .comment section, thus reducing the size of the stripped kernel by a few more kilobytes. Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --Km1U/tdNT/EmXiR1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+iFjUUkv4P6juNwoRAtrHAJ9RlKS2hykmfgOL5ZkqrF8VdNNHUwCfUtW9 zVkRUSagUDihTz2fp4DqrNE= =SGh6 -----END PGP SIGNATURE----- --Km1U/tdNT/EmXiR1-- From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 07:38:34 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12D7F37B401 for ; Mon, 31 Mar 2003 07:38:34 -0800 (PST) Received: from smtp.us.messagingengine.com (ny3.fastmail.fm [66.111.4.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4900B43FAF for ; Mon, 31 Mar 2003 07:38:32 -0800 (PST) (envelope-from thanjee@fastmail.fm) Received: from smtp.us2.messagingengine.com (server2.internal [10.202.2.133]) by fastmail.fm (Postfix) with ESMTP id BA8474AB76 for ; Mon, 31 Mar 2003 10:38:30 -0500 (EST) Received: from 127.0.0.1 ([127.0.0.1] helo=smtp.us2.messagingengine.com) by messagingengine.com with SMTP; Mon, 31 Mar 2003 10:38:30 -0500 Received: by smtp.us2.messagingengine.com (Postfix, from userid 99) id 636FE4F2EB; Mon, 31 Mar 2003 10:38:29 -0500 (EST) Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 1.2 (F2.71; T1.001; A1.51; B2.12; Q2.03) From: "Thanjee Neefam" To: freebsd-current@freebsd.org Date: Mon, 31 Mar 2003 07:38:29 -0800 X-Epoch: 1049125110 X-Sasl-enc: zAZg7OCqQIjxYFtL2D6Lig Message-Id: <20030331153829.636FE4F2EB@smtp.us2.messagingengine.com> Subject: MIDI X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 15:38:37 -0000 Hello, I am not sure if this is most appropriate here, but there is no sound-dev-current mailing list. I was very happy when compiling my 5.0 kernel. For the first time "device midi" compiled without giving any errors. This abnormal excitement only led to misery when I discovered after rebooting that there still was no MIDI. Is MIDI going to be implemented soon? Who is working on it? Can I help them? (I am not a very good programmer, but I can hack pre existing code, and I am good at testing). MIDI is the ONLY thing stopping me from running FreeBSD exclusively. Also Gentoo is extremely unstable. I updated ports about 2 days ago and installed it. I don't know if this is a 5.0 issue or a ports issue. Cheers, Tim -- http://www.fastmail.fm - Send your email first class From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 12:21:49 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A515C37B401; Mon, 31 Mar 2003 12:21:49 -0800 (PST) Received: from tomts12-srv.bellnexxia.net (tomts12.bellnexxia.net [209.226.175.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8534243F3F; Mon, 31 Mar 2003 12:21:48 -0800 (PST) (envelope-from mike@sparc64.style9.org) Received: from sparc64.style9.org ([65.93.76.196]) by tomts12-srv.bellnexxia.netESMTP <20030331202147.WJQD23066.tomts12-srv.bellnexxia.net@sparc64.style9.org>; Mon, 31 Mar 2003 15:21:47 -0500 Received: (from mike@localhost) by sparc64.style9.org (8.12.6/8.12.6/Submit) id h2VKMMQv044770; Mon, 31 Mar 2003 15:22:22 -0500 (EST) Date: Mon, 31 Mar 2003 15:22:22 -0500 (EST) From: Mike Barcroft Message-Id: <200303312022.h2VKMMQv044770@sparc64.style9.org> To: current@FreeBSD.org, sparc64@FreeBSD.org Subject: sparc64 tinderbox failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 20:21:53 -0000 Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- >>> stage 2: rebuilding the object tree -------------------------------------------------------------- >>> stage 2: build tools -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- >>> stage 4: populating /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- >>> stage 4: building everything.. -------------------------------------------------------------- ===> sbin/devd In file included from /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include/g++/bits/stl_iterator_base_funcs.h:68, from /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include/g++/bits/stl_algobase.h:74, from /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include/g++/algorithm:66, from /tinderbox/sparc64/src/sbin/devd/devd.cc:54: /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include/g++/bits/concept_check.h:64:1: multi-line comment *** Error code 1 Stop in /tinderbox/sparc64/src/sbin/devd. *** Error code 1 Stop in /tinderbox/sparc64/src/sbin. *** Error code 1 Stop in /tinderbox/sparc64/src. *** Error code 1 Stop in /tinderbox/sparc64/src. *** Error code 1 Stop in /tinderbox/sparc64/src. From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 12:54:44 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83EAC37B401 for ; Mon, 31 Mar 2003 12:54:44 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AA6943F75 for ; Mon, 31 Mar 2003 12:54:44 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) h2VKshPR078434 for ; Mon, 31 Mar 2003 12:54:43 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)h2VKshVa078433 for freebsd-current@freebsd.org; Mon, 31 Mar 2003 12:54:43 -0800 (PST) Date: Mon, 31 Mar 2003 12:54:43 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20030331205443.GA78416@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: g++ or devd breaks world X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 20:54:45 -0000 Sources retrieved by cvsup 11 am PST. The tree is clean, and obj/ is empty. ===> sbin/devd c++ -O -pipe -mcpu=pentiumpro -I. -I/usr/src/sbin/devd -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/sbin/devd/devd.cc In file included from /usr/obj/usr/src/i386/usr/include/g++/bits/stl_iterator_base_funcs.h:68, from /usr/obj/usr/src/i386/usr/include/g++/bits/stl_algobase.h:74, from /usr/obj/usr/src/i386/usr/include/g++/algorithm:66, from /usr/src/sbin/devd/devd.cc:54: /usr/obj/usr/src/i386/usr/include/g++/bits/concept_check.h:64:1: multi-line comment *** Error code 1 -- Steve From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 13:31:35 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0454037B401 for ; Mon, 31 Mar 2003 13:31:35 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4007243FAF for ; Mon, 31 Mar 2003 13:31:34 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h2VLVX344182 for ; Mon, 31 Mar 2003 16:31:33 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Mon, 31 Mar 2003 16:31:33 -0500 (EST) From: Jeff Roberson To: current@freebsd.org Message-ID: <20030331162932.R64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: New signal code going in. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 21:31:36 -0000 Over the next few hours I'll be commiting initial support for the 1:1 threading code. Mostly I'll be commiting the signal related bits. I intend to break up this patch in to several smaller commits. Each commit should leave the tree in a stable, working, compilable state. I may screw something up though. Just be aware that it will be a few hours to get this all in while I test each mini patch and so on. Cheers, Jeff From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 13:53:49 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A709F37B401 for ; Mon, 31 Mar 2003 13:53:49 -0800 (PST) Received: from mail1.arcor-ip.de (mail1.arcor-ip.de [145.253.2.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7764D43FA3 for ; Mon, 31 Mar 2003 13:53:48 -0800 (PST) (envelope-from Friedemann.Becker@student.uni-tuebingen.de) Received: from chasey (213.23.46.50) by mail1.arcor-ip.de (5.5.034) id 3E1E876300508385 for freebsd-current@freebsd.org; Mon, 31 Mar 2003 23:53:46 +0200 Date: Mon, 31 Mar 2003 23:53:26 +0200 (=?ISO-8859-1?Q?Westeurop=E4ische_Sommerzeit?=) From: Friedemann Becker To: freebsd-current@freebsd.org In-Reply-To: <20030331153829.636FE4F2EB@smtp.us2.messagingengine.com> Message-ID: References: <20030331153829.636FE4F2EB@smtp.us2.messagingengine.com> X-X-Sender: zxmxy33@mailserv02.uni-tuebingen.de MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: MIDI X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Friedemann.Becker@student.uni-tuebingen.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 21:53:50 -0000 I'm interrested in using MIDI on FreeBSD, too, but I have to tell you, that - as far as I found out - there has been midi support some time ago, but it's not included in the system/kernel anymore. There's probably some hope although, I don't find it, but I remember someone stated that you can easily apply the netbsd midi code as a patch to the current kernel. 5.0RC2 works according to this source, but had system reboots, when kldloading the midi module. If you're interrested, maybee you have more luck searching, there aren't many articles about freebsd and midi on the net (especially newer ones). I'll keep on searching.... Friedemann > Hello, > I am not sure if this is most appropriate here, but there is no > sound-dev-current mailing list. > > I was very happy when compiling my 5.0 kernel. For the first time "device > midi" compiled without giving any errors. This abnormal excitement only > led to misery when I discovered after rebooting that there still was no > MIDI. > Is MIDI going to be implemented soon? Who is working on it? Can I help > them? (I am not a very good programmer, but I can hack pre existing code, > and I am good at testing). MIDI is the ONLY thing stopping me from > running FreeBSD exclusively. From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 15:54:49 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D27F237B401 for ; Mon, 31 Mar 2003 15:54:49 -0800 (PST) Received: from HAL9000.homeunix.com (12-233-57-131.client.attbi.com [12.233.57.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D93A43FAF for ; Mon, 31 Mar 2003 15:54:49 -0800 (PST) (envelope-from das@FreeBSD.ORG) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) h2VNsiKj090968; Mon, 31 Mar 2003 15:54:44 -0800 (PST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6p2/8.12.5/Submit) id h2VNshwn090967; Mon, 31 Mar 2003 15:54:43 -0800 (PST) (envelope-from das@FreeBSD.ORG) Date: Mon, 31 Mar 2003 15:54:43 -0800 From: David Schultz To: Thanjee Neefam Message-ID: <20030331235443.GB32627@HAL9000.homeunix.com> Mail-Followup-To: Thanjee Neefam , freebsd-current@freebsd.org References: <20030331153829.636FE4F2EB@smtp.us2.messagingengine.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030331153829.636FE4F2EB@smtp.us2.messagingengine.com> cc: freebsd-current@FreeBSD.ORG Subject: Re: MIDI X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 23:54:50 -0000 Thus spake Thanjee Neefam : > I was very happy when compiling my 5.0 kernel. For the first time "device > midi" compiled without giving any errors. This abnormal excitement only > led to misery when I discovered after rebooting that there still was no > MIDI. > Is MIDI going to be implemented soon? Who is working on it? Can I help > them? (I am not a very good programmer, but I can hack pre existing code, > and I am good at testing). MIDI is the ONLY thing stopping me from > running FreeBSD exclusively. FYI, the non-free OSS driver supports MIDI: http://www.opensound.com/bsd.html From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 16:50:24 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B39D37B478 for ; Mon, 31 Mar 2003 16:50:22 -0800 (PST) Received: from monsterjam.org (rdu57-10-206.nc.rr.com [66.57.10.206]) by mx1.FreeBSD.org (Postfix) with SMTP id 81D9843F75 for ; Mon, 31 Mar 2003 16:50:21 -0800 (PST) (envelope-from jason@monsterjam.org) Received: (qmail 5936 invoked by uid 1005); 1 Apr 2003 00:50:21 -0000 Received: from jason@monsterjam.org by monsterjam.org by uid 1002 with qmail-scanner-1.14 (clamscan: 0.54. Clear:. Processed in 1.030868 secs); 01 Apr 2003 00:50:21 -0000 Received: from unknown (HELO monsterjam.org) (10.1.1.3) by 0 with SMTP; 1 Apr 2003 00:50:19 -0000 Date: Mon, 31 Mar 2003 19:50:19 -0500 (EST) From: jason To: freebsd-current@freebsd.org Message-ID: <20030331194719.M5711-100000@monsterjam.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Upgrading from 5.0-RELEASE to -CURRENT on sparc64 (me too) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 00:50:25 -0000 Im getting the same thing as http://groups.google.com/groups?q=+attempt+to+use+poisoned+%22malloc%22+cc1plus&hl=en&lr=lang_en&ie=UTF-8&oe=UTF-8&safe=off&selm=Pine.NEB.3.96L.1030212144405.82101A-100000%40fledge.watson.org.lucky.freebsd.current&rnum=3 when doing a make buildworld.. after cvsupping CURRENT .. /usr/src/contrib/gcc/config/sparc/sysv4.h:96:1: warning: this is the location of the previous definition In file included from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/tconfig.h:11, from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/hconfig.h:2, from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/config.h:1, from /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/parse.y:34, from /usr/src/contrib/gcc/cp/spew.c:34: /usr/src/contrib/gcc/config/elfos.h:594:1: warning: "STRING_ASM_OP" redefined In file included from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/tconfig.h:15, from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/hconfig.h:2, from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/config.h:1, from /usr/src/contrib/gcc/cp/spew.c:26: /usr/src/contrib/gcc/config/sparc/sysv4.h:87:1: warning: this is the location of the previous definition In file included from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/tconfig.h:12, from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/hconfig.h:2, from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/config.h:1, from /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/parse.y:34, from /usr/src/contrib/gcc/cp/spew.c:34: /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:61:25: attempt to use poisoned "malloc" /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:62:25: attempt to use poisoned "calloc" /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:63:25: attempt to use poisoned "realloc" /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:64:25: attempt to use poisoned "strdup" mkdep: compile failed *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc1plus. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. sparky# regards, Jason -- Coincidence, n.: You weren't paying attention to the other half of what was going on. From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 17:37:55 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id 1612237B401; Mon, 31 Mar 2003 17:37:55 -0800 (PST) Date: Mon, 31 Mar 2003 19:37:55 -0600 From: Juli Mallett To: freebsd-current@FreeBSD.org Message-ID: <20030331193755.A60987@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Organisation: The FreeBSD Project X-Alternate-Addresses: , , , , X-Towel: Yes X-Negacore: Yes X-Title: Code Maven X-Authentication-Warning: localhost: juli pwned teh intarweb cc: freebsd-scsi@FreeBSD.org Subject: Odd issues with USB SmartMedia Reader/Writer (PNY) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 01:37:55 -0000 I'm really dumb when it comes to CAM, SCSI, USB, and so on, so forgive if I am being naive... (Also that would probably explain why I am having a hard time deciding where this mail should end up... Forgive me on that account, plz.) I have a PNY USB SmartMedia reader which works excellently with 5.x with 8M media, but which blows up with 32M media. I'd assume this is due to improper geometry or something, but I really have no idea. Insert-reinsert produces no change in results, etc. Below are bits from dmesg, with the smaller then the larger. Any insight would be appreciated. Once this is taken care of, the weekly reboots into windows to clean off the camera can finally stop... Out last legitimate use of Windows :) %%% --> With the 8M SmartMedia umass0: Alcor Mass Storage Device, rev 1.10/1.00, addr 5 umass0: Get Max Lun not supported (STALLED) umass0:0:0:-1: Attached to scbus0 as device 0 pass0 at umass-sim0 bus 0 target 0 lun 0 pass0: Removable Direct Access SCSI-0 device pass0: 1.000MB/s transfers GEOM: new disk da0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 7MB (16000 512 byte sectors: 64H 32S/T 7C) (da0:umass-sim0:0:0:0): READ(6)/WRITE(6) not supported, increasing minimum_cmd_size to 10. [0] f:80 typ:1 s(CHS):0/1/10 e(CHS):249/3/16 s:25 l:15975 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure da0s1, start 12800 length 8179200 end 8191999 %%% %%% --> With the 32M SmartMedia umass0: Alcor Mass Storage Device, rev 1.10/1.00, addr 5 umass0: Get Max Lun not supported (STALLED) umass0:0:0:-1: Attached to scbus0 as device 0 pass0 at umass-sim0 bus 0 target 0 lun 0 pass0: Removable Direct Access SCSI-0 device pass0: 1.000MB/s transfers GEOM: new disk da0 (da0:umass-sim0:0:0:0): error 6 (da0:umass-sim0:0:0:0): Unretryable Error da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present Unretryable error (da0:umass-sim0:0:0:0): error 6 (da0:umass-sim0:0:0:0): Unretryable Error Opened disk da0 -> 6 (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present Unretryable error (da0:umass-sim0:0:0:0): error 6 (da0:umass-sim0:0:0:0): Unretryable Error Opened disk da0 -> 6 %%% Thanx! juli. -- juli mallett. email: jmallett@freebsd.org; aim: bsdflata; efnet: juli; From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 17:48:41 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16DFB37B404 for ; Mon, 31 Mar 2003 17:48:41 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A6A343F75 for ; Mon, 31 Mar 2003 17:28:26 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h311SQb76177 for ; Mon, 31 Mar 2003 20:28:26 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Mon, 31 Mar 2003 20:28:26 -0500 (EST) From: Jeff Roberson To: current@freebsd.org Message-ID: <20030331202655.B64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: New threading code. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 01:48:41 -0000 The kernel components for the 1:1 threading implementation are in the tree. This includes the thr system calls, the umtx implementation, and all of the signal changes. I will commit the library shortly. This is all 'beta' quality. It runs mozilla and openoffice without issue. There are known bugs which I will point out when libthr is in the tree. More to come. Cheers, Jeff From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 19:25:34 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FF7837B401; Mon, 31 Mar 2003 19:25:34 -0800 (PST) Received: from toq6-srv.bellnexxia.net (toq6-srv.bellnexxia.net [209.226.175.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 835C143F3F; Mon, 31 Mar 2003 19:25:33 -0800 (PST) (envelope-from mike@sparc64.style9.org) Received: from sparc64.style9.org ([65.93.76.196]) by tomts17-srv.bellnexxia.netESMTP <20030401032519.TIQW22713.tomts17-srv.bellnexxia.net@sparc64.style9.org>; Mon, 31 Mar 2003 22:25:19 -0500 Received: (from mike@localhost) by sparc64.style9.org (8.12.6/8.12.6/Submit) id h313QAJ4020914; Mon, 31 Mar 2003 22:26:10 -0500 (EST) Date: Mon, 31 Mar 2003 22:26:10 -0500 (EST) From: Mike Barcroft Message-Id: <200304010326.h313QAJ4020914@sparc64.style9.org> To: current@FreeBSD.org, sparc64@FreeBSD.org Subject: sparc64 tinderbox failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 03:25:34 -0000 Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- >>> stage 2: rebuilding the object tree -------------------------------------------------------------- >>> stage 2: build tools -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- >>> stage 4: populating /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- >>> stage 4: building everything.. -------------------------------------------------------------- ===> bin/ps /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/lib/libkvm.a(kvm_proc.o)(.text+0x794): undefined reference to `SIGANDSET' *** Error code 1 Stop in /tinderbox/sparc64/src/bin/ps. *** Error code 1 Stop in /tinderbox/sparc64/src/bin. *** Error code 1 Stop in /tinderbox/sparc64/src. *** Error code 1 Stop in /tinderbox/sparc64/src. *** Error code 1 Stop in /tinderbox/sparc64/src. From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 19:54:47 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 067EB37B401 for ; Mon, 31 Mar 2003 19:54:47 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FB7843FB1 for ; Mon, 31 Mar 2003 19:54:46 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h313sji50951 for ; Mon, 31 Mar 2003 22:54:45 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Mon, 31 Mar 2003 22:54:45 -0500 (EST) From: Jeff Roberson To: current@freebsd.org Message-ID: <20030331225124.W64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 03:54:47 -0000 I have commited libthr. To try this out you'll need to do the following 1. cvsup 2. rebuild world and kernel 3. install world and kernel 4. build libthr from src/lib/libthr 5. Either replace /usr/lib/libc_r.so.5 with /usr/lib/libthr.so.1 or relink your applications against libthr.so.1 This works with mozilla and open office. Known errata: 1. Mutex priority inheritance is not implemented. 2. If you mess with the mutex or condvar queues from a signal handler you will break. 3. If you reset the sigaction for SIGTHR you will break things. 4. The scheduling parameters lie. 5. The garbage collector deadlocks. We never free threads. You will eventually leak memory or run out of LDT entries. 6. This is x86 only for a short while. 7. Some of the code is ugly. I will be addressing all of this shortly. Feel free to try it out and report bugs that are not mentioned above. Cheers, Jeff From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 20:42:25 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D4FA37B401; Mon, 31 Mar 2003 20:42:25 -0800 (PST) Received: from meriadoc.jobeus.net (meriadoc.jobeus.net [205.206.125.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9670143F85; Mon, 31 Mar 2003 20:42:24 -0800 (PST) (envelope-from freebsd@jobeus.net) Received: from meriadoc.jobeus.net (freebsd@localhost [127.0.0.1]) by meriadoc.jobeus.net (8.12.8/8.12.3) with ESMTP id h314gK8m085910; Mon, 31 Mar 2003 21:42:21 -0700 (MST) (envelope-from freebsd@jobeus.net) Received: from localhost (freebsd@localhost)h314gIBo085907; Mon, 31 Mar 2003 21:42:20 -0700 (MST) X-Authentication-Warning: meriadoc.jobeus.net: freebsd owned process doing -bs Date: Mon, 31 Mar 2003 21:42:18 -0700 (MST) From: Scott Carmichael To: freebsd-current@freebsd.org Message-ID: <20030331214022.F85896@meriadoc.jobeus.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-questions@freebsd.org Subject: 5.0-Current build failing on libkvm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 04:42:25 -0000 I just cvsup'd today and am now getting this error and subsequent fails... :( Anyone have any ideas? (please keep me in the reply as I'm not subscribed to -current) cc -O -pipe -march=pentium4 -DLAZY_PS -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -static -o ps fmt.o keyword.o nlist.o print.o ps.o -lm -lkvm /usr/obj/usr/src/i386/usr/lib/libkvm.a(kvm_proc.o)(.text+0x948): undefined reference to `SIGANDSET' From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 20:50:14 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAD0E37B401; Mon, 31 Mar 2003 20:50:14 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA4F343FBF; Mon, 31 Mar 2003 20:50:13 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h314o1f76771; Mon, 31 Mar 2003 23:50:01 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Mon, 31 Mar 2003 23:50:01 -0500 (EST) From: Jeff Roberson To: Scott Carmichael In-Reply-To: <20030331214022.F85896@meriadoc.jobeus.net> Message-ID: <20030331234913.A64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: 5.0-Current build failing on libkvm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 04:50:15 -0000 On Mon, 31 Mar 2003, Scott Carmichael wrote: > I just cvsup'd today and am now getting this error and subsequent fails... > :( > > Anyone have any ideas? (please keep me in the reply as I'm not subscribed > to -current) > > > cc -O -pipe -march=pentium4 -DLAZY_PS -Wsystem-headers -Werror -Wall > -Wno-format-y2k -Wno-uninitialized -static -o ps fmt.o keyword.o nlist.o > print.o ps.o -lm -lkvm > /usr/obj/usr/src/i386/usr/lib/libkvm.a(kvm_proc.o)(.text+0x948): undefined > reference to `SIGANDSET' Sorry, this was my fault. I totally spaced on this bit. You can cvsup again when your mirror picks up my fix or you can change that SIGANDSET in kvm_proc.c to SIGSETOR. Cheers, Jeff From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 00:06:31 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C510637B40A; Tue, 1 Apr 2003 00:06:31 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B29743FA3; Tue, 1 Apr 2003 00:06:31 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.9/8.12.6) with ESMTP id h3186UVI074289; Tue, 1 Apr 2003 00:06:31 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9/8.12.6/Submit) id h3186STC074286; Tue, 1 Apr 2003 00:06:28 -0800 (PST) Date: Tue, 1 Apr 2003 00:06:28 -0800 (PST) From: Matthew Dillon Message-Id: <200304010806.h3186STC074286@apollo.backplane.com> To: Juli Mallett References: <20030331193755.A60987@FreeBSD.org> cc: freebsd-scsi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Odd issues with USB SmartMedia Reader/Writer (PNY) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 08:06:32 -0000 It's likely that a quirk entry is needed for that smart media device. Most smart media USB devices require quirk entries in CAM. Many such devices simply lockup permanently (until you unplug and replug them in) when sent an unsupported command so without the quirk entry anything can happen after the first reported failure. -Matt Matthew Dillon : :I'm really dumb when it comes to CAM, SCSI, USB, and so on, so forgive :if I am being naive... (Also that would probably explain why I am :having a hard time deciding where this mail should end up... Forgive :me on that account, plz.) : :I have a PNY USB SmartMedia reader which works excellently with 5.x :with 8M media, but which blows up with 32M media. I'd assume this is :due to improper geometry or something, but I really have no idea. :Insert-reinsert produces no change in results, etc. Below are bits :from dmesg, with the smaller then the larger. : :Any insight would be appreciated. Once this is taken care of, the :weekly reboots into windows to clean off the camera can finally stop... :Out last legitimate use of Windows :) : :%%% --> With the 8M SmartMedia :umass0: Alcor Mass Storage Device, rev 1.10/1.00, addr 5 :umass0: Get Max Lun not supported (STALLED) :umass0:0:0:-1: Attached to scbus0 as device 0 :pass0 at umass-sim0 bus 0 target 0 lun 0 :pass0: Removable Direct Access SCSI-0 device :pass0: 1.000MB/s transfers :GEOM: new disk da0 :da0 at umass-sim0 bus 0 target 0 lun 0 :da0: Removable Direct Access SCSI-0 device :da0: 1.000MB/s transfers :da0: 7MB (16000 512 byte sectors: 64H 32S/T 7C) :(da0:umass-sim0:0:0:0): READ(6)/WRITE(6) not supported, increasing minimum_cmd_size to 10. :[0] f:80 typ:1 s(CHS):0/1/10 e(CHS):249/3/16 s:25 l:15975 :[1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 :[2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 :[3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 :GEOM: Configure da0s1, start 12800 length 8179200 end 8191999 :%%% : :%%% --> With the 32M SmartMedia :umass0: Alcor Mass Storage Device, rev 1.10/1.00, addr 5 :umass0: Get Max Lun not supported (STALLED) :umass0:0:0:-1: Attached to scbus0 as device 0 :pass0 at umass-sim0 bus 0 target 0 lun 0 :pass0: Removable Direct Access SCSI-0 device :pass0: 1.000MB/s transfers :GEOM: new disk da0 :(da0:umass-sim0:0:0:0): error 6 :(da0:umass-sim0:0:0:0): Unretryable Error :da0 at umass-sim0 bus 0 target 0 lun 0 :da0: Removable Direct Access SCSI-0 device :da0: 1.000MB/s transfers :da0: Attempt to query device size failed: NOT READY, Medium not present :(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 :(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error :(da0:umass-sim0:0:0:0): SCSI Status: Check Condition :(da0:umass-sim0:0:0:0): NOT READY asc:3a,0 :(da0:umass-sim0:0:0:0): Medium not present :(da0:umass-sim0:0:0:0): (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 :(da0:umass-sim0:0:0:0): NOT READY asc:3a,0 :(da0:umass-sim0:0:0:0): Medium not present :Unretryable error :(da0:umass-sim0:0:0:0): error 6 :(da0:umass-sim0:0:0:0): Unretryable Error :Opened disk da0 -> 6 :(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 :(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error :(da0:umass-sim0:0:0:0): SCSI Status: Check Condition :(da0:umass-sim0:0:0:0): NOT READY asc:3a,0 :(da0:umass-sim0:0:0:0): Medium not present :(da0:umass-sim0:0:0:0): (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 :(da0:umass-sim0:0:0:0): NOT READY asc:3a,0 :(da0:umass-sim0:0:0:0): Medium not present :Unretryable error :(da0:umass-sim0:0:0:0): error 6 :(da0:umass-sim0:0:0:0): Unretryable Error :Opened disk da0 -> 6 :%%% : :Thanx! :juli. :-- :juli mallett. email: jmallett@freebsd.org; aim: bsdflata; efnet: juli; :_______________________________________________ :freebsd-current@freebsd.org mailing list :http://lists.freebsd.org/mailman/listinfo/freebsd-current :To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 00:07:59 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CAEC37B40B; Tue, 1 Apr 2003 00:07:59 -0800 (PST) Received: from meriadoc.jobeus.net (meriadoc.jobeus.net [205.206.125.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4FE643F75; Tue, 1 Apr 2003 00:07:58 -0800 (PST) (envelope-from freebsd@jobeus.net) Received: from meriadoc.jobeus.net (freebsd@localhost [127.0.0.1]) by meriadoc.jobeus.net (8.12.8/8.12.3) with ESMTP id h3187v8m063547; Tue, 1 Apr 2003 01:07:57 -0700 (MST) (envelope-from freebsd@jobeus.net) Received: from localhost (freebsd@localhost)h3187vr8063538; Tue, 1 Apr 2003 01:07:57 -0700 (MST) X-Authentication-Warning: meriadoc.jobeus.net: freebsd owned process doing -bs Date: Tue, 1 Apr 2003 01:07:57 -0700 (MST) From: Scott Carmichael To: freebsd-current@freebsd.org In-Reply-To: <20030331234913.A64602-100000@mail.chesapeake.net> Message-ID: <20030401010527.C59610@meriadoc.jobeus.net> References: <20030331234913.A64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-questions@freebsd.org Subject: Re: 5.0-Current build failing on libkvm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 08:08:00 -0000 Sigh... It seems that there's a lot of problems in -current right now. First there was a double-line comment problem with a .h file, seems fixed now, but then there's also an ununsed var in sys/kern/kern_sig.c (line 184), which I fixed and am trying to compile again... for the 3rd time. Someone wanna get that one in CVS? On Mon, 31 Mar 2003, Jeff Roberson wrote: > On Mon, 31 Mar 2003, Scott Carmichael wrote: > > > I just cvsup'd today and am now getting this error and subsequent fails... > > :( > > > > Anyone have any ideas? (please keep me in the reply as I'm not subscribed > > to -current) > > > > > > cc -O -pipe -march=pentium4 -DLAZY_PS -Wsystem-headers -Werror -Wall > > -Wno-format-y2k -Wno-uninitialized -static -o ps fmt.o keyword.o nlist.o > > print.o ps.o -lm -lkvm > > /usr/obj/usr/src/i386/usr/lib/libkvm.a(kvm_proc.o)(.text+0x948): undefined > > reference to `SIGANDSET' > > Sorry, this was my fault. I totally spaced on this bit. You can cvsup > again when your mirror picks up my fix or you can change that SIGANDSET in > kvm_proc.c to SIGSETOR. > > Cheers, > Jeff > > From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 00:22:22 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B647337B401; Tue, 1 Apr 2003 00:22:22 -0800 (PST) Received: from relay.macomnet.ru (relay.macomnet.ru [195.128.64.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1564143FAF; Tue, 1 Apr 2003 00:22:21 -0800 (PST) (envelope-from maxim@macomnet.ru) Received: from news1.macomnet.ru (news1.macomnet.ru [195.128.64.14]) by relay.macomnet.ru (8.11.6/8.11.6) with ESMTP id h318MGR2373079; Tue, 1 Apr 2003 12:22:16 +0400 (MSD) Date: Tue, 1 Apr 2003 12:22:16 +0400 (MSD) From: Maxim Konovalov To: Scott Carmichael In-Reply-To: <20030401010527.C59610@meriadoc.jobeus.net> Message-ID: <20030401122034.F42286@news1.macomnet.ru> References: <20030331234913.A64602-100000@mail.chesapeake.net> <20030401010527.C59610@meriadoc.jobeus.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: 5.0-Current build failing on libkvm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 08:22:23 -0000 On 01:07-0700, Apr 1, 2003, Scott Carmichael wrote: > Sigh... It seems that there's a lot of problems in -current right now. > First there was a double-line comment problem with a .h file, seems fixed > now, but then there's also an ununsed var in sys/kern/kern_sig.c (line > 184), which I fixed and am trying to compile again... for the 3rd time. > > Someone wanna get that one in CVS? "quick and dirty" Index: sys/kern/kern_sig.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_sig.c,v retrieving revision 1.221 diff -u -r1.221 kern_sig.c --- sys/kern/kern_sig.c 31 Mar 2003 23:30:41 -0000 1.221 +++ sys/kern/kern_sig.c 1 Apr 2003 08:15:12 -0000 @@ -181,10 +181,12 @@ int cursig(struct thread *td) { +#ifdef INVARIANTS struct proc *p = td->td_proc; PROC_LOCK_ASSERT(p, MA_OWNED); mtx_assert(&sched_lock, MA_NOTOWNED); +#endif return (SIGPENDING(td) ? issignal(td) : 0); } %%% -- Maxim Konovalov, maxim@macomnet.ru, maxim@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 02:48:54 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6DE037B401 for ; Tue, 1 Apr 2003 02:48:54 -0800 (PST) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3098843F85 for ; Tue, 1 Apr 2003 02:48:54 -0800 (PST) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.9/8.12.9) with ESMTP id h31AmrEF046873 for ; Tue, 1 Apr 2003 05:48:53 -0500 (EST) (envelope-from mdodd@FreeBSD.ORG) Date: Tue, 1 Apr 2003 05:48:53 -0500 (EST) From: "Matthew N. Dodd" X-X-Sender: winter@sasami.jurai.net To: freebsd-current@FreeBSD.ORG Message-ID: <20030401054552.N1365@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: IFF_EVIL patch available. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 10:48:55 -0000 Leveraging our new RFC3514 support I've implemented a new network interface flag 'IFF_EVIL' which causes all IP packets crossing the interface to have the IP_EVIL bit set. ftp://ftp.jurai.net/users/winter/patches/IFF_EVIL.patch Enjoy. -- | 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 | For Great Justice! | ISO8802.5 4ever | From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 03:49:13 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6847A37B401 for ; Tue, 1 Apr 2003 03:49:13 -0800 (PST) Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id C911B43F3F for ; Tue, 1 Apr 2003 03:49:12 -0800 (PST) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.nectar.cc (Postfix) with ESMTP id EE87BF; Tue, 1 Apr 2003 05:49:11 -0600 (CST) Received: by madman.celabo.org (Postfix, from userid 1001) id 3D97178C66; Tue, 1 Apr 2003 05:49:11 -0600 (CST) Date: Tue, 1 Apr 2003 05:49:11 -0600 From: "Jacques A. Vidrine" To: Jeff Roberson Message-ID: <20030401114911.GA46472@madman.celabo.org> References: <20030331225124.W64602-100000@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030331225124.W64602-100000@mail.chesapeake.net> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.3i-ja.1 cc: current@FreeBSD.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 11:49:13 -0000 On Mon, Mar 31, 2003 at 10:54:45PM -0500, Jeff Roberson wrote: > 5. Either replace /usr/lib/libc_r.so.5 with /usr/lib/libthr.so.1 or > relink your applications against libthr.so.1 Happily strlen(libc_r.so.5) == strlen(libthr.so.1), so you can also edit your binaries' SONEEDED fields in place :-) ed -s /path/to/binary <<-EOF /libc_r.so.5/ s/libc_r.so.5/libthr.so.1/ w q EOF or similar ... Cheers, -- Jacques A. Vidrine http://www.celabo.org/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos jvidrine@verio.net . nectar@FreeBSD.org . nectar@kth.se From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 03:55:08 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80AD237B401 for ; Tue, 1 Apr 2003 03:55:08 -0800 (PST) Received: from main.evrocom.net (main.evrocom.net [212.39.92.2]) by mx1.FreeBSD.org (Postfix) with SMTP id AB16243FBD for ; Tue, 1 Apr 2003 03:55:03 -0800 (PST) (envelope-from veno@evrocom.net) Received: (qmail 2232 invoked from network); 1 Apr 2003 11:55:00 -0000 Received: from unknown (HELO beatle) (217.10.240.35) by main.evrocom.net with SMTP; 1 Apr 2003 11:55:00 -0000 Message-ID: <023501c2f845$746f5380$23f00ad9@beatle> From: "Ventsislav Velkov" To: Date: Tue, 1 Apr 2003 14:54:30 +0300 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Fw: problem updating from 4.7 Stable do 5.0 Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 11:55:08 -0000 Does anybody have an idea ? ----- Original Message -----=20 From: Ventsislav Velkov=20 To: freebsd-current@FreeBSD.ORG=20 Sent: Monday, March 31, 2003 2:15 PM Subject: problem updating from 4.7 Stable do 5.0 Current Hello all, I have a problem updating one of our servers from 4.7Stable to = 5.0Current. It is a Compaq Proliant 7000 Server with 4 Xeons @500Mhz with 2MB L2 = cache each. I has a 4200 Compaq Smart Raid Controler with attached 3 U1 Storages.=20 I update the src rebuild the world from updated src to 5.0Current, build = a GENERIC kernel and installed it. But after I boot it brokes up during the booting process with the = following error: //strip Fatal trap 12: page fault while in kernel mode cpuid=3D0; lapic.id=3D = 01000000 fault virtual address =3D 0x54 fault code =3D supervisor read, page not present .... .... .... process eflags =3D interrupt enabled, resume, IOPL=3D0 current process =3D 4(g_down) kernel: type12trap, code=3D0 Stopped at ida_construct_qcb+0xe3: movzbl 0x54(%eax),%eax //strip It may have some punctual mistakes because it is not a copy/paste. Will appreciate any advices where could be the problem. Best regards, Veno _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 04:11:16 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AC5237B401; Tue, 1 Apr 2003 04:11:16 -0800 (PST) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id F302543F85; Tue, 1 Apr 2003 04:11:10 -0800 (PST) (envelope-from ru@whale.sunbay.crimea.ua) Received: from whale.sunbay.crimea.ua (ru@localhost [127.0.0.1]) h31CB6AP062669 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Apr 2003 15:11:06 +0300 (EEST) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.12.8/8.12.8/Submit) id h31CB2jl062657; Tue, 1 Apr 2003 15:11:02 +0300 (EEST) (envelope-from ru) Date: Tue, 1 Apr 2003 15:11:02 +0300 From: Ruslan Ermilov To: Mike Barcroft Message-ID: <20030401121102.GC61909@sunbay.com> References: <200303312022.h2VKMMQv044770@sparc64.style9.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wxDdMuZNg1r63Hyj" Content-Disposition: inline In-Reply-To: <200303312022.h2VKMMQv044770@sparc64.style9.org> User-Agent: Mutt/1.5.4i cc: current@freebsd.org cc: sparc64@freebsd.org Subject: Re: sparc64 tinderbox failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 12:11:16 -0000 --wxDdMuZNg1r63Hyj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 31, 2003 at 03:22:22PM -0500, Mike Barcroft wrote: > Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html >=20 > -------------------------------------------------------------- > >>> stage 4: building everything.. > -------------------------------------------------------------- > =3D=3D=3D> sbin/devd > In file included from /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc6= 4/usr/include/g++/bits/stl_iterator_base_funcs.h:68, > from /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc6= 4/usr/include/g++/bits/stl_algobase.h:74, > from /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc6= 4/usr/include/g++/algorithm:66, > from /tinderbox/sparc64/src/sbin/devd/devd.cc:54: > /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include/g++/bits= /concept_check.h:64:1: multi-line comment > *** Error code 1 >=20 > Stop in /tinderbox/sparc64/src/sbin/devd. > *** Error code 1 >=20 Fixed by lowering the WARNS level. Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --wxDdMuZNg1r63Hyj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+iYHWUkv4P6juNwoRArzdAJwL+CNKB6SbDNuobFYswIWmwwfdbgCeM/Ec 46W/mtSt2KEU8MNH9OwZr2Y= =lsVH -----END PGP SIGNATURE----- --wxDdMuZNg1r63Hyj-- From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 04:23:55 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D54E437B401; Tue, 1 Apr 2003 04:23:55 -0800 (PST) Received: from tomts26-srv.bellnexxia.net (tomts26.bellnexxia.net [209.226.175.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id C30EC43F85; Tue, 1 Apr 2003 04:23:54 -0800 (PST) (envelope-from mike@sparc64.style9.org) Received: from sparc64.style9.org ([65.93.76.196]) by tomts26-srv.bellnexxia.netESMTP <20030401122353.DTBK13343.tomts26-srv.bellnexxia.net@sparc64.style9.org>; Tue, 1 Apr 2003 07:23:53 -0500 Received: (from mike@localhost) by sparc64.style9.org (8.12.6/8.12.6/Submit) id h31COARf006279; Tue, 1 Apr 2003 07:24:10 -0500 (EST) Date: Tue, 1 Apr 2003 07:24:10 -0500 (EST) From: Mike Barcroft Message-Id: <200304011224.h31COARf006279@sparc64.style9.org> To: current@FreeBSD.org, sparc64@FreeBSD.org Subject: sparc64 tinderbox failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 12:23:56 -0000 Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- >>> stage 2: rebuilding the object tree -------------------------------------------------------------- >>> stage 2: build tools -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- >>> stage 4: populating /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- >>> stage 4: building everything.. -------------------------------------------------------------- ===> sbin/devd In file included from /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include/g++/bits/stl_iterator_base_funcs.h:68, from /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include/g++/bits/stl_algobase.h:74, from /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include/g++/algorithm:66, from /tinderbox/sparc64/src/sbin/devd/devd.cc:54: /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include/g++/bits/concept_check.h:64:1: multi-line comment *** Error code 1 Stop in /tinderbox/sparc64/src/sbin/devd. *** Error code 1 Stop in /tinderbox/sparc64/src/sbin. *** Error code 1 Stop in /tinderbox/sparc64/src. *** Error code 1 Stop in /tinderbox/sparc64/src. *** Error code 1 Stop in /tinderbox/sparc64/src. From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 06:08:01 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4B1737B404 for ; Tue, 1 Apr 2003 06:08:01 -0800 (PST) Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 312E743FB1 for ; Tue, 1 Apr 2003 06:08:00 -0800 (PST) (envelope-from miniyan@kt.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (3.7W/HMX-13) id XAA04049; Tue, 1 Apr 2003 23:07:58 +0900 (JST) Received: from [192.168.2.10] (l224047.ppp.asahi-net.or.jp [218.219.224.47]) by mail1.rim.or.jp (3.7W) id XAA15435; Tue, 1 Apr 2003 23:07:57 +0900 (JST) Date: Tue, 01 Apr 2003 23:07:58 +0900 From: miniyan To: Maksim Yevmenkin In-Reply-To: <3E775939.3070907@exodus.net> References: <20030318235120.2559.MINIYAN@kt.rim.or.jp> <3E775939.3070907@exodus.net> Message-Id: <20030401222211.257C.MINIYAN@kt.rim.or.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.05.08 cc: current@FreeBSD.ORG Subject: Re: bluetooth BW-BH02U reset failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 14:08:02 -0000 Hi Maksim, It's slow response [...] > > what you need is Linux bluez-bluefw-0.9 package. in firmware/ > directory you will find two files: BCM2033-MD.hex (mini-driver) > and BCM2033-FW.bin (firmware). the loader itself is implemented > in bcm_usb.c file. I understand it. It's my further target. [...] > > right. you *will* get these errors if you disconnect the device > while stack is running (i.e. USB transfer is pending). i'm still > looking into USB code to find why i'm getting lots of IOERRORs > before CANCELLED. I've no special error on it. [...] > >>3) is it uhci or ohci USB controller? > > [...] I have another PC, which is Crusoe LAPTOP CASIO FIVA 206. This PC has OHCI root hub AcerLab M5237 (Aladdin-V) USB controller. I tried to connect mitsumi's dongle and rc.bluetooth. So this pc shows error. If you have any well-known problem with OHCI, please let me know or point information. # usbdevs -d -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), AcerLabs(0x0000), rev 1.00 uhub0 port 1 addr 2: full speed, power 200 mA, config 1, product 0x641f(0x641f), Mitsumi(0x03ee), rev 1.14 ubt0 port 2 powered # /etc/rc.bluetooth start ubt0 BD_ADDR: 00:a0:96:1f:d6:d6 Features: 0xff 0xff 0x5 00 00 00 00 00 <3-Slot> <5-Slot> Max. ACL packet size: 128 bytes Number of ACL packets: 8 Max. SCO packet size: 64 bytes Number of SCO packets: 8 Could not execute command "initialize". Invalid argument # but console shows(sorry detailed value does not recognized. I just take picture and read text from it) .... Bad mbuf alloc flags: 1 Stack backtrace: backtrace(... mb_alloc(... m_get(1,8,... ng_btsocket_hcl_raw_send( send+0xd8 sosend( sendit( sendto( syscall( XInt0x80_syscall() at ... --- syscall (133),elp = ... > BTW you might want to check Pav Lucistnik's (pav@oook.cz) Bluetooth > on FreeBSD page. > > http://www.oook.cz/bsd/bluetooth.html > It's very good information. It's big helps for me. I trying to connect with this document. Unfortunately, I just finished hccontrol. h2ping looks strange. I just summarize it and send further mail. Thanks, Takahiko -- miniyan From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 07:31:16 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C5CD37B401; Tue, 1 Apr 2003 07:31:16 -0800 (PST) Received: from meriadoc.jobeus.net (meriadoc.jobeus.net [205.206.125.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 316E143FB1; Tue, 1 Apr 2003 07:31:15 -0800 (PST) (envelope-from freebsd@jobeus.net) Received: from meriadoc.jobeus.net (freebsd@localhost [127.0.0.1]) by meriadoc.jobeus.net (8.12.8/8.12.3) with ESMTP id h31FVA8m039198; Tue, 1 Apr 2003 08:31:10 -0700 (MST) (envelope-from freebsd@jobeus.net) Received: from localhost (freebsd@localhost)h31FV75L038855; Tue, 1 Apr 2003 08:31:07 -0700 (MST) X-Authentication-Warning: meriadoc.jobeus.net: freebsd owned process doing -bs Date: Tue, 1 Apr 2003 08:31:07 -0700 (MST) From: Scott Carmichael To: Maxim Konovalov In-Reply-To: <20030401122034.F42286@news1.macomnet.ru> Message-ID: <20030401083012.Y34413@meriadoc.jobeus.net> References: <20030331234913.A64602-100000@mail.chesapeake.net> <20030401122034.F42286@news1.macomnet.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: 5.0-Current build failing on libkvm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 15:31:16 -0000 I lied, that .h file wasn't fixed. libstdc++/include/concept_check.h There's a "// #define [stuff] \" line, and that final \ is making make world fail. :( On Tue, 1 Apr 2003, Maxim Konovalov wrote: > On 01:07-0700, Apr 1, 2003, Scott Carmichael wrote: > > > Sigh... It seems that there's a lot of problems in -current right now. > > First there was a double-line comment problem with a .h file, seems fixed > > now, but then there's also an ununsed var in sys/kern/kern_sig.c (line > > 184), which I fixed and am trying to compile again... for the 3rd time. > > > > Someone wanna get that one in CVS? > > "quick and dirty" > > Index: sys/kern/kern_sig.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/kern_sig.c,v > retrieving revision 1.221 > diff -u -r1.221 kern_sig.c > --- sys/kern/kern_sig.c 31 Mar 2003 23:30:41 -0000 1.221 > +++ sys/kern/kern_sig.c 1 Apr 2003 08:15:12 -0000 > @@ -181,10 +181,12 @@ > int > cursig(struct thread *td) > { > +#ifdef INVARIANTS > struct proc *p = td->td_proc; > > PROC_LOCK_ASSERT(p, MA_OWNED); > mtx_assert(&sched_lock, MA_NOTOWNED); > +#endif > return (SIGPENDING(td) ? issignal(td) : 0); > } > > > %%% > > -- > Maxim Konovalov, maxim@macomnet.ru, maxim@FreeBSD.org > From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 08:06:30 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4E5837B404 for ; Tue, 1 Apr 2003 08:06:30 -0800 (PST) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48E8043F3F for ; Tue, 1 Apr 2003 08:06:30 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0040.cvx21-bradley.dialup.earthlink.net ([209.179.192.40] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190OHK-0001D4-00; Tue, 01 Apr 2003 08:06:27 -0800 Message-ID: <3E89B615.48BCCBF@mindspring.com> Date: Tue, 01 Apr 2003 07:53:57 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ventsislav Velkov References: <023501c2f845$746f5380$23f00ad9@beatle> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a483b0599105cae5b099e7e93edb5ec84c350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@FreeBSD.ORG Subject: Re: Fw: problem updating from 4.7 Stable do 5.0 Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 16:06:31 -0000 Ventsislav Velkov wrote: > > Does anybody have an idea ? option DISABLE_PSE option DISABLE_PG_G -- Terry From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 09:42:48 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8009837B401 for ; Tue, 1 Apr 2003 09:42:48 -0800 (PST) Received: from hotmail.com (f136.pav1.hotmail.com [64.4.31.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 225D543FA3 for ; Tue, 1 Apr 2003 09:42:48 -0800 (PST) (envelope-from evantd@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 1 Apr 2003 09:42:28 -0800 Received: from 128.208.59.99 by pv1fd.pav1.hotmail.msn.com with HTTP; Tue, 01 Apr 2003 17:42:25 GMT X-Originating-IP: [128.208.59.99] X-Originating-Email: [evantd@hotmail.com] From: "Evan Dower" To: freebsd-current@freebsd.org Date: Tue, 01 Apr 2003 09:42:25 -0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 01 Apr 2003 17:42:28.0932 (UTC) FILETIME=[10ABD040:01C2F876] Subject: RELENG_5_0 v. HEAD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 17:42:48 -0000 I've been tracking RELENG_5_0 pretty much since it existed, but I am wondering now if it would be better to track -CURRENT via HEAD instead. After all, with the semi-frozen status of HEAD, all knew commits should be fairly conservative and the _general_ _ trend_ should at least be toward a more stable product. I wonder if HEAD is actually a more stable product than RELENG_5_0. Certainly it would be for anyone using the nvidia-driver, since it is unsupported on RELENG_5_0. What are your thoughts? Do you have any advice for me? I do not run a "production server" but I require that my computer work most of the time as a workstation. Thanks for your opinions on the matter, Evan Dower _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 09:44:46 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5736B37B404 for ; Tue, 1 Apr 2003 09:44:46 -0800 (PST) Received: from mail.gmx.net (imap.gmx.net [213.165.65.60]) by mx1.FreeBSD.org (Postfix) with SMTP id 0FCE543FCB for ; Tue, 1 Apr 2003 09:44:45 -0800 (PST) (envelope-from s.moeck@gmx.de) Received: (qmail 12581 invoked by uid 65534); 1 Apr 2003 17:44:43 -0000 Received: from dsl254-062-177.sea1.dsl.speakeasy.net (HELO xpn) (216.254.62.177) by mail.gmx.net (mp004-rz3) with SMTP; 01 Apr 2003 19:44:43 +0200 From: =?iso-8859-1?Q?Stephan_M=F6ck?= To: Date: Tue, 1 Apr 2003 10:44:31 +0200 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.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: kqueue and kevent X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 17:44:47 -0000 I want to use kqueue and kevent to watch directories and subdirectories. Does anybody have information about these to things beside the man page? Especially I want to figure out on which file or folder an event occurs. Thank you Stephan From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 10:02:56 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90D3B37B401; Tue, 1 Apr 2003 10:02:56 -0800 (PST) Received: from castle.org (castle.org [207.178.4.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id E743D43FE9; Tue, 1 Apr 2003 10:02:48 -0800 (PST) (envelope-from nomad@castle.org) Received: from castle.org (localhost.castle.org [127.0.0.1]) by castle.org (8.12.9/8.12.9) with ESMTP id h31I2lR2013383; Tue, 1 Apr 2003 10:02:48 -0800 (PST) (envelope-from nomad@castle.org) Message-Id: <200304011802.h31I2lR2013383@castle.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: mobile@FreeBSD.ORG, current@FreeBSD.ORG X-uri: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Apr 2003 10:02:47 -0800 From: Lee Damon Subject: IBM T30 USB issue: kernel: uhub2: device problem, disabling port 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 18:02:56 -0000 I've just sup'd a completely clean source tree and compiled a new kernel and world. My kernconf is the generic one with pcm and apm turned on. apci is turned off in the hints file (because it breaks the mouse). I have INVARIANTS, DDB, and WITNESS turned off right now, for speed. When I try to activate a Bluetooth USB device, I get the following error: Apr 1 09:57:26 tylendel kernel: uhub2: device problem, disabling port 1 I am reasonably convinced it isn't a problem with the bluetooth daughter card (but can be convinced otherwise, of course). I'd be happy to work with any USB/Kernel experts to try to get this working. Just let me know what you need me to do. (I am not now, and never have been, a kernel hacker.) I can recompile the kernel with INVARIANTS &co turned on if that would be helpful. thanks, nomad ----------- The cry has been that when war is declared, all opposition should therefore be hushed. A sentiment more unworthy of a free country could hardly be propagated. If the doctrine be admitted, rulers have only to declare war and they are screened at once from scrutiny ... In war, then, as in peace, assert the freedom of speech and of the press. Cling to this as the bulwark of all our rights and privileges. -- William Ellery Channing ----------- - Lee "nomad" Damon - \ play: nomad@castle.org or castle!nomad \ work: nomad@ee.washington.edu \ /\ Seneschal, Castle PAUS. / \ "Celebrate Diversity" / \ From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 10:18:12 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4372137B401 for ; Tue, 1 Apr 2003 10:18:12 -0800 (PST) Received: from h00609772adf0.ne.client2.attbi.com (h00609772adf0.ne.client2.attbi.com [24.61.43.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F81843F93 for ; Tue, 1 Apr 2003 10:18:11 -0800 (PST) (envelope-from rodrigc@attbi.com) Received: from h00609772adf0.ne.client2.attbi.com (localhost.ne.attbi.com [127.0.0.1])h31IIPri087759; Tue, 1 Apr 2003 13:18:26 -0500 (EST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)h31IIPLd087758; Tue, 1 Apr 2003 13:18:25 -0500 (EST) Date: Tue, 1 Apr 2003 13:18:25 -0500 From: Craig Rodrigues To: Stephan M?ck Message-ID: <20030401181825.GA87742@attbi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i cc: freebsd-current@freebsd.org Subject: Re: kqueue and kevent X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 18:18:12 -0000 On Tue, Apr 01, 2003 at 10:44:31AM +0200, Stephan M?ck wrote: > I want to use kqueue and kevent to watch directories and subdirectories. > Does anybody have information about these to things beside the man page? > Especially I want to figure out on which file or folder an event occurs. > Thank you Jonathan Lemon has some good kqueue papers: http://people.freebsd.org/~jlemon/ -- Craig Rodrigues http://home.attbi.com/~rodrigc rodrigc@attbi.com From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 10:27:00 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECEC137B401 for ; Tue, 1 Apr 2003 10:27:00 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-150.dsl.lsan03.pacbell.net [63.207.60.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CC3043FAF for ; Tue, 1 Apr 2003 10:27:00 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id E264366CFA; Tue, 1 Apr 2003 10:26:59 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id B17D012A9; Tue, 1 Apr 2003 10:26:59 -0800 (PST) Date: Tue, 1 Apr 2003 10:26:59 -0800 From: Kris Kennaway To: Stephan M?ck Message-ID: <20030401182659.GC4151@rot13.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qbvjkv9qwOGw/5Fx" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i cc: freebsd-current@freebsd.org Subject: Re: kqueue and kevent X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 18:27:01 -0000 --Qbvjkv9qwOGw/5Fx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Apr 01, 2003 at 10:44:31AM +0200, Stephan M?ck wrote: > I want to use kqueue and kevent to watch directories and subdirectories. > Does anybody have information about these to things beside the man page? > Especially I want to figure out on which file or folder an event occurs. > Thank you You can look at the l0pht-watch port for an implementation of this. Kris --Qbvjkv9qwOGw/5Fx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+idnzWry0BWjoQKURAr2bAKD79/M38G2wMUVYr9FocpPLMWEQugCg2VXx jOVwwukQeZ8mjPzHvxzMITo= =tTYR -----END PGP SIGNATURE----- --Qbvjkv9qwOGw/5Fx-- From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 10:29:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15BEA37B401 for ; Tue, 1 Apr 2003 10:29:07 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-150.dsl.lsan03.pacbell.net [63.207.60.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C20143F3F for ; Tue, 1 Apr 2003 10:29:06 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 3890666CFA; Tue, 1 Apr 2003 10:29:06 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 211B012AA; Tue, 1 Apr 2003 10:29:06 -0800 (PST) Date: Tue, 1 Apr 2003 10:29:06 -0800 From: Kris Kennaway To: Evan Dower Message-ID: <20030401182906.GD4151@rot13.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="P+33d92oIH25kiaB" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i cc: freebsd-current@freebsd.org Subject: Re: RELENG_5_0 v. HEAD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 18:29:07 -0000 --P+33d92oIH25kiaB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 01, 2003 at 09:42:25AM -0800, Evan Dower wrote: > I've been tracking RELENG_5_0 pretty much since it existed, but I am=20 > wondering now if it would be better to track -CURRENT via HEAD instead.= =20 > After all, with the semi-frozen status of HEAD, all knew commits should b= e=20 > fairly conservative and the _general_ _ trend_ should at least be toward = a=20 > more stable product. I wonder if HEAD is actually a more stable product= =20 > than RELENG_5_0. Sometimes is, sometimes isn't. You have to be fairly careful to upgrade at the right time based on commit activity and mailing list traffic. > Certainly it would be for anyone using the nvidia-driver,=20 > since it is unsupported on RELENG_5_0. What are your thoughts? It's just as unsupported on HEAD. Kris --P+33d92oIH25kiaB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+idpxWry0BWjoQKURAokYAKDk6ysVFAHFOTbQhiEw6aT22PdaOgCdHDTG ZOduStEsM9lokznqy2Loemk= =aPIT -----END PGP SIGNATURE----- --P+33d92oIH25kiaB-- From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 11:07:51 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0621B37B401 for ; Tue, 1 Apr 2003 11:07:51 -0800 (PST) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7522443F75 for ; Tue, 1 Apr 2003 11:07:50 -0800 (PST) (envelope-from scott_long@btc.adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h31J6Xl31043; Tue, 1 Apr 2003 11:06:33 -0800 Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [10.100.0.52]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id LAA25896; Tue, 1 Apr 2003 11:07:39 -0800 (PST) Received: from btc.adaptec.com ([10.20.80.159]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id MAA11856; Tue, 1 Apr 2003 12:07:23 -0700 (MST) Message-ID: <3E89E369.5090204@btc.adaptec.com> Date: Tue, 01 Apr 2003 12:07:21 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2.1) Gecko/20030206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jeff Roberson References: <20030331225124.W64602-100000@mail.chesapeake.net> In-Reply-To: <20030331225124.W64602-100000@mail.chesapeake.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 19:07:51 -0000 Jeff Roberson wrote: > I have commited libthr. To try this out you'll need to do the following > Excellent job Jeff and Jon, thanks a lot! Is anyone working on getting full Apache2 support for this? Also, linking the Java 1.3 and 1.4 ports to this might be interesting. Scott From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 11:24:51 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91A9737B401 for ; Tue, 1 Apr 2003 11:24:51 -0800 (PST) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE2A543F75 for ; Tue, 1 Apr 2003 11:24:50 -0800 (PST) (envelope-from scott_long@btc.adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h31JNXl20776; Tue, 1 Apr 2003 11:23:33 -0800 Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [10.100.0.52]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id LAA00817; Tue, 1 Apr 2003 11:24:33 -0800 (PST) Received: from btc.adaptec.com ([10.20.80.159]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id MAA11865; Tue, 1 Apr 2003 12:24:09 -0700 (MST) Message-ID: <3E89E753.60600@btc.adaptec.com> Date: Tue, 01 Apr 2003 12:24:03 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2.1) Gecko/20030206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jeff Roberson References: <20030331225124.W64602-100000@mail.chesapeake.net> In-Reply-To: <20030331225124.W64602-100000@mail.chesapeake.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 19:24:51 -0000 Jeff Roberson wrote: > I have commited libthr. To try this out you'll need to do the following > Excellent job Jeff and Jon, thanks a lot! Is anyone working on getting full Apache2 support for this? Also, linking the Java 1.3 and 1.4 ports to this might be interesting. Scott From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 11:47:24 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D352737B401; Tue, 1 Apr 2003 11:47:24 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 152A443FB1; Tue, 1 Apr 2003 11:47:24 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.9/8.12.7) with ESMTP id h31JlID0010174; Tue, 1 Apr 2003 11:47:22 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h31JlCeD010173; Tue, 1 Apr 2003 11:47:12 -0800 (PST) Date: Tue, 1 Apr 2003 11:47:12 -0800 From: "David O'Brien" To: Ruslan Ermilov Message-ID: <20030401194712.GA10151@dragon.nuxi.com> Mail-Followup-To: David O'Brien , Ruslan Ermilov , Makoto Matsushita , current@freebsd.org References: <20030329190908R.matusita@jp.FreeBSD.org> <3E857E9C.F7476A32@mindspring.com> <20030329203005.GB94956@sunbay.com> <20030331150348.GD21700@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030331150348.GD21700@sunbay.com> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: Makoto Matsushita cc: current@freebsd.org Subject: Re: FreeBSD/alpha kern.flp flood X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 19:47:25 -0000 On Mon, Mar 31, 2003 at 06:03:48PM +0300, Ruslan Ermilov wrote: > Anyway, I've committed the fix to release/Makefile that strips > the .comment section out from the BOOTMFS kernel. If you have > time, you can exploit the effect of this by changing sweaping > over src/sys/ and changing rcsid = "$FreeBSD$" lines to be > __FBSDID() -- that would put these IDs in the .comment section, > thus reducing the size of the stripped kernel by a few more > kilobytes. Why can't the bits be built with -Dlint to remove rcsid's. From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 11:56:52 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id 3565A37B401; Tue, 1 Apr 2003 11:56:52 -0800 (PST) Date: Tue, 1 Apr 2003 13:56:52 -0600 From: Juli Mallett To: David O'Brien , Ruslan Ermilov , Makoto Matsushita , current@freebsd.org Message-ID: <20030401135652.A53787@FreeBSD.org> References: <20030329190908R.matusita@jp.FreeBSD.org> <3E857E9C.F7476A32@mindspring.com> <20030329203005.GB94956@sunbay.com> <20030331150348.GD21700@sunbay.com> <20030401194712.GA10151@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030401194712.GA10151@dragon.nuxi.com>; from obrien@freebsd.org on Tue, Apr 01, 2003 at 11:47:12AM -0800 Organisation: The FreeBSD Project X-Alternate-Addresses: , , , , X-Towel: Yes X-Negacore: Yes X-Title: Code Maven X-Authentication-Warning: localhost: juli pwned teh intarweb Subject: Re: FreeBSD/alpha kern.flp flood X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 19:56:52 -0000 * De: David O'Brien [ Data: 2003-04-01 ] [ Subjecte: Re: FreeBSD/alpha kern.flp flood ] > On Mon, Mar 31, 2003 at 06:03:48PM +0300, Ruslan Ermilov wrote: > > Anyway, I've committed the fix to release/Makefile that strips > > the .comment section out from the BOOTMFS kernel. If you have > > time, you can exploit the effect of this by changing sweaping > > over src/sys/ and changing rcsid = "$FreeBSD$" lines to be > > __FBSDID() -- that would put these IDs in the .comment section, > > thus reducing the size of the stripped kernel by a few more > > kilobytes. > > Why can't the bits be built with -Dlint to remove rcsid's. Because that would change other things, wouldn't it. Like maybe structure sizes or macros which need to actually work? -- juli mallett. email: jmallett@freebsd.org; aim: bsdflata; efnet: juli; From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 11:58:06 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C5FB37B401 for ; Tue, 1 Apr 2003 11:58:06 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 916CA43F93 for ; Tue, 1 Apr 2003 11:58:05 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h31Jw3t23870; Tue, 1 Apr 2003 14:58:03 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Tue, 1 Apr 2003 14:58:03 -0500 (EST) From: Jeff Roberson To: Scott Long In-Reply-To: <3E89E369.5090204@btc.adaptec.com> Message-ID: <20030401145603.R64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 19:58:06 -0000 On Tue, 1 Apr 2003, Scott Long wrote: > Jeff Roberson wrote: > > I have commited libthr. To try this out you'll need to do the following > > > > Excellent job Jeff and Jon, thanks a lot! > > Is anyone working on getting full Apache2 support for this? Also, > linking the Java 1.3 and 1.4 ports to this might be interesting. > > Scott > I'd be surprised if apache2 didn't just work. I have yet to try it out though. I have enough bug fixing and little features to do that I'm not worried about more app compat for now. Hopefully I can get things to a state where there are no known bugs and then find a maintainer for this. There is plenty of exciting work to do on it after that but I'm not sure what kind of bandwidth I will have for it. Cheers, Jeff From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 12:23:12 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B27A37B401; Tue, 1 Apr 2003 12:23:12 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5066D43FCB; Tue, 1 Apr 2003 12:23:11 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.9/8.12.7) with ESMTP id h31KN4D0010606; Tue, 1 Apr 2003 12:23:04 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h31KMxKK010601; Tue, 1 Apr 2003 12:22:59 -0800 (PST) Date: Tue, 1 Apr 2003 12:22:58 -0800 From: "David O'Brien" To: Juli Mallett Message-ID: <20030401202258.GA10571@dragon.nuxi.com> Mail-Followup-To: David O'Brien , Juli Mallett , Ruslan Ermilov , Makoto Matsushita , current@freebsd.org References: <20030329190908R.matusita@jp.FreeBSD.org> <3E857E9C.F7476A32@mindspring.com> <20030329203005.GB94956@sunbay.com> <20030331150348.GD21700@sunbay.com> <20030401194712.GA10151@dragon.nuxi.com> <20030401135652.A53787@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030401135652.A53787@FreeBSD.org> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: Makoto Matsushita cc: Ruslan Ermilov cc: current@FreeBSD.org Subject: Re: FreeBSD/alpha kern.flp flood X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 20:23:12 -0000 On Tue, Apr 01, 2003 at 01:56:52PM -0600, Juli Mallett wrote: > * De: David O'Brien [ Data: 2003-04-01 ] > [ Subjecte: Re: FreeBSD/alpha kern.flp flood ] > > On Mon, Mar 31, 2003 at 06:03:48PM +0300, Ruslan Ermilov wrote: > > > Anyway, I've committed the fix to release/Makefile that strips > > > the .comment section out from the BOOTMFS kernel. If you have > > > time, you can exploit the effect of this by changing sweaping > > > over src/sys/ and changing rcsid = "$FreeBSD$" lines to be > > > __FBSDID() -- that would put these IDs in the .comment section, > > > thus reducing the size of the stripped kernel by a few more > > > kilobytes. > > > > Why can't the bits be built with -Dlint to remove rcsid's. > > Because that would change other things, wouldn't it. Like maybe > structure sizes or macros which need to actually work? I didn't see any issues like that with a very curiory look at the sources. Are you willing to take a look also? From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 13:01:33 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AFAB37B401; Tue, 1 Apr 2003 13:01:33 -0800 (PST) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DBE643F3F; Tue, 1 Apr 2003 13:01:29 -0800 (PST) (envelope-from ru@whale.sunbay.crimea.ua) Received: from whale.sunbay.crimea.ua (ru@localhost [127.0.0.1]) h31L1OAP043675 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Apr 2003 00:01:25 +0300 (EEST) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.12.8/8.12.8/Submit) id h31L1GS4043643; Wed, 2 Apr 2003 00:01:16 +0300 (EEST) (envelope-from ru) Date: Wed, 2 Apr 2003 00:01:16 +0300 From: Ruslan Ermilov To: "David O'Brien" , Juli Mallett , Makoto Matsushita , current@FreeBSD.org Message-ID: <20030401210116.GA43262@sunbay.com> References: <20030329190908R.matusita@jp.FreeBSD.org> <3E857E9C.F7476A32@mindspring.com> <20030329203005.GB94956@sunbay.com> <20030331150348.GD21700@sunbay.com> <20030401194712.GA10151@dragon.nuxi.com> <20030401135652.A53787@FreeBSD.org> <20030401202258.GA10571@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline In-Reply-To: <20030401202258.GA10571@dragon.nuxi.com> User-Agent: Mutt/1.5.4i Subject: Re: FreeBSD/alpha kern.flp flood X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 21:01:33 -0000 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 01, 2003 at 12:22:58PM -0800, David O'Brien wrote: > On Tue, Apr 01, 2003 at 01:56:52PM -0600, Juli Mallett wrote: > > * De: David O'Brien [ Data: 2003-04-01 ] > > [ Subjecte: Re: FreeBSD/alpha kern.flp flood ] > > > On Mon, Mar 31, 2003 at 06:03:48PM +0300, Ruslan Ermilov wrote: > > > > Anyway, I've committed the fix to release/Makefile that strips > > > > the .comment section out from the BOOTMFS kernel. If you have > > > > time, you can exploit the effect of this by changing sweaping > > > > over src/sys/ and changing rcsid =3D "$FreeBSD$" lines to be > > > > __FBSDID() -- that would put these IDs in the .comment section, > > > > thus reducing the size of the stripped kernel by a few more > > > > kilobytes. > > >=20 > > > Why can't the bits be built with -Dlint to remove rcsid's. > >=20 > > Because that would change other things, wouldn't it. Like maybe > > structure sizes or macros which need to actually work? >=20 > I didn't see any issues like that with a very curiory look at the > sources. Are you willing to take a look also? >=20 With my very cursory look, I think the "#ifdef lint" part of is going to be a major problem here. Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+if4cUkv4P6juNwoRAphKAJ9rkxkPJSRJj0da+W6nPHS/fYsFHwCeMh4Z +YVCdKcAkq4ZFJKhOBFbGOI= =e8ec -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62-- From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 13:54:05 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF3D137B401 for ; Tue, 1 Apr 2003 13:54:05 -0800 (PST) Received: from hotmail.com (f20.pav1.hotmail.com [64.4.31.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A73843F75 for ; Tue, 1 Apr 2003 13:54:05 -0800 (PST) (envelope-from evantd@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 1 Apr 2003 13:54:05 -0800 Received: from 128.208.59.99 by pv1fd.pav1.hotmail.msn.com with HTTP; Tue, 01 Apr 2003 21:54:04 GMT X-Originating-IP: [128.208.59.99] X-Originating-Email: [evantd@hotmail.com] From: "Evan Dower" To: kris@obsecurity.org Date: Tue, 01 Apr 2003 13:54:04 -0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 01 Apr 2003 21:54:05.0266 (UTC) FILETIME=[36C99320:01C2F899] cc: freebsd-current@freebsd.org Subject: Re: RELENG_5_0 v. HEAD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 21:54:06 -0000 Perhaps I should choose my words more wisely. The ports system will allow you to build it (nvidia-driver) on a recent HEAD, but not on RELENG_5_0. I assume that this is because some change was made that increased its stability. I had it installed anyway, for a while, but in the end chose stability over tuxracer ;-). Maybe now I can have both. I would guess that stability and performance have both increased in a number of areas since 5.0 was released. As a user of an SMP system, that may affect me more than the average user, but as the owner of a lowly workstation (as opposed to a server), maybe it wouldn't be so noticeable. Of course, it has only been about two and a half months, but I get the impression that perhaps it has come along way in that short time. I guess my question, if it can be boiled down into a single question, is "Is HEAD _usually_ faster and more stable than RELENG_5_0?" Thanks again, Evan Dower, a recently admitted CS major at the University of Washington who would love for some nice FreeBSD developer to take him under their wing and gently introduce him to the world of FreeBSD development (instead of being an idle spectator) >From: Kris Kennaway >To: Evan Dower >CC: freebsd-current@freebsd.org >Subject: Re: RELENG_5_0 v. HEAD >Date: Tue, 1 Apr 2003 10:29:06 -0800 >MIME-Version: 1.0 >Received: from obsecurity.dyndns.org ([63.207.60.150]) by >mc4-f23.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Tue, 1 Apr >2003 10:29:07 -0800 >Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5])by >obsecurity.dyndns.org (Postfix) with ESMTPid 3890666CFA; Tue, 1 Apr 2003 >10:29:06 -0800 (PST) >Received: by rot13.obsecurity.org (Postfix, from userid 1000)id 211B012AA; >Tue, 1 Apr 2003 10:29:06 -0800 (PST) >X-Message-Info: JGTYoYF78jEHjJx36Oi8+Q1OJDRSDidP >Message-ID: <20030401182906.GD4151@rot13.obsecurity.org> >References: >In-Reply-To: >User-Agent: Mutt/1.4i >Return-Path: kris@obsecurity.org >X-OriginalArrivalTime: 01 Apr 2003 18:29:07.0789 (UTC) >FILETIME=[94EB7FD0:01C2F87C] > >On Tue, Apr 01, 2003 at 09:42:25AM -0800, Evan Dower wrote: > > I've been tracking RELENG_5_0 pretty much since it existed, but I am > > wondering now if it would be better to track -CURRENT via HEAD instead. > > After all, with the semi-frozen status of HEAD, all knew commits should >be > > fairly conservative and the _general_ _ trend_ should at least be toward >a > > more stable product. I wonder if HEAD is actually a more stable product > > than RELENG_5_0. > >Sometimes is, sometimes isn't. You have to be fairly careful to >upgrade at the right time based on commit activity and mailing list >traffic. > > > Certainly it would be for anyone using the nvidia-driver, > > since it is unsupported on RELENG_5_0. What are your thoughts? > >It's just as unsupported on HEAD. > >Kris ><< attach3 >> _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 16:56:26 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A97BF37B401 for ; Tue, 1 Apr 2003 16:56:26 -0800 (PST) Received: from speicher.org (sirius.speicher.org [209.74.10.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E42943F3F for ; Tue, 1 Apr 2003 16:56:25 -0800 (PST) (envelope-from geoff@speicher.org) Received: from localhost (geoff@localhost) by speicher.org (8.11.6/8.11.6) with ESMTP id h3217u697664; Tue, 1 Apr 2003 20:07:56 -0500 (EST) (envelope-from geoff@speicher.org) Date: Tue, 1 Apr 2003 20:07:55 -0500 (EST) From: "Geoffrey C. Speicher" To: current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Jeff Roberson Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 00:56:26 -0000 Jeff Roberson wrote: > > I have commited libthr. To try this out you'll need to do the following > > 1. cvsup > 2. rebuild world and kernel > 3. install world and kernel > 4. build libthr from src/lib/libthr > 5. Either replace /usr/lib/libc_r.so.5 with /usr/lib/libthr.so.1 or > relink your applications against libthr.so.1 > > This works with mozilla and open office. FWIW, it also appears to work fine with KDE 3.1 and multithreaded qt (I opted for replacing rather than relinking). Geoff From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 21:25:10 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4722137B401; Tue, 1 Apr 2003 21:25:10 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D9F643FBD; Tue, 1 Apr 2003 21:25:08 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id PAA10551; Wed, 2 Apr 2003 15:25:00 +1000 Date: Wed, 2 Apr 2003 15:24:59 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: "David O'Brien" In-Reply-To: <20030401194712.GA10151@dragon.nuxi.com> Message-ID: <20030402151519.U25349@gamplex.bde.org> References: <20030329190908R.matusita@jp.FreeBSD.org> <3E857E9C.F7476A32@mindspring.com><20030331150348.GD21700@sunbay.com> <20030401194712.GA10151@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Makoto Matsushita cc: current@freebsd.org Subject: Re: FreeBSD/alpha kern.flp flood X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 05:25:10 -0000 On Tue, 1 Apr 2003, David O'Brien wrote: > On Mon, Mar 31, 2003 at 06:03:48PM +0300, Ruslan Ermilov wrote: > > Anyway, I've committed the fix to release/Makefile that strips > > the .comment section out from the BOOTMFS kernel. If you have > > time, you can exploit the effect of this by changing sweaping > > over src/sys/ and changing rcsid = "$FreeBSD$" lines to be > > __FBSDID() -- that would put these IDs in the .comment section, > > thus reducing the size of the stripped kernel by a few more > > kilobytes. > > Why can't the bits be built with -Dlint to remove rcsid's. This would make little difference, since using __FBSDID() or rcsid[] in kernel sources is a style bugs, and most of the sources are missing this style bug. "strings -a LINT/kernel | grep FreeBSD" gives: %%% @(#)$FreeBSD: src/sys/contrib/ipfilter/netinet/fil.c,v 1.36 2003/02/19 05:47:00 imp Exp $ @(#)$FreeBSD$ @(#)$FreeBSD: src/sys/contrib/ipfilter/netinet/ip_fil.c,v 1.38 2003/02/19 05:47:00 imp Exp $ @(#)$FreeBSD: src/sys/contrib/ipfilter/netinet/ip_frag.c,v 1.24 2003/02/15 06:23:45 darrenr Exp $ @(#)$FreeBSD: src/sys/contrib/ipfilter/netinet/ip_nat.c,v 1.33 2003/02/15 06:23:45 darrenr Exp $ @(#)$FreeBSD: src/sys/contrib/ipfilter/netinet/ip_proxy.c,v 1.22 2003/02/15 06:23:45 darrenr Exp $ @(#)$FreeBSD: src/sys/contrib/ipfilter/netinet/ip_state.c,v 1.31 2003/02/15 06:47:27 darrenr Exp $ $FreeBSD: src/sys/dev/an/if_an.c,v 1.47 2003/02/19 05:47:00 imp Exp $ $FreeBSD: src/sys/dev/an/if_an_isa.c,v 1.9 2003/02/17 19:57:32 imp Exp $ $FreeBSD: src/sys/dev/an/if_an_pccard.c,v 1.16 2003/02/17 19:57:32 imp Exp $ $FreeBSD: src/sys/dev/an/if_an_pci.c,v 1.17 2003/02/17 19:57:32 imp Exp $ $FreeBSD: src/sys/dev/bge/if_bge.c,v 1.31 2003/02/19 05:47:01 imp Exp $ $FreeBSD: src/sys/dev/lge/if_lge.c,v 1.17 2003/02/19 05:47:07 imp Exp $ $FreeBSD: src/sys/dev/mii/amphy.c,v 1.12 2003/01/19 02:59:32 obrien Exp $ $FreeBSD: src/sys/dev/mii/brgphy.c,v 1.17 2003/01/19 02:59:32 obrien Exp $ $FreeBSD: src/sys/dev/mii/dcphy.c,v 1.19 2003/01/19 02:59:32 obrien Exp $ $FreeBSD: src/sys/dev/mii/exphy.c,v 1.15 2003/01/19 02:59:32 obrien Exp $ $FreeBSD: src/sys/dev/mii/mii.c,v 1.15 2002/10/14 22:31:52 alfred Exp $ $FreeBSD: src/sys/dev/mii/mii_physubr.c,v 1.16 2002/05/04 11:08:49 phk Exp $ $FreeBSD: src/sys/dev/mii/nsphy.c,v 1.17 2003/01/19 02:59:32 obrien Exp $ $FreeBSD: src/sys/dev/mii/nsgphy.c,v 1.13 2003/01/19 02:59:32 obrien Exp $ $FreeBSD: src/sys/dev/mii/pnphy.c,v 1.13 2003/01/19 02:59:32 obrien Exp $ $FreeBSD: src/sys/dev/mii/pnaphy.c,v 1.11 2003/01/19 02:59:32 obrien Exp $ $FreeBSD: src/sys/dev/mii/rlphy.c,v 1.15 2003/01/19 02:59:32 obrien Exp $ $FreeBSD: src/sys/dev/mii/tlphy.c,v 1.13 2003/01/19 02:59:32 obrien Exp $ $FreeBSD: src/sys/dev/mii/ukphy.c,v 1.12 2002/10/14 22:31:52 alfred Exp $ $FreeBSD: src/sys/dev/mii/ukphy_subr.c,v 1.5 2002/04/29 13:35:31 phk Exp $ $FreeBSD: src/sys/dev/mii/xmphy.c,v 1.11 2003/01/19 02:59:32 obrien Exp $ $FreeBSD: src/sys/dev/mii/lxtphy.c,v 1.9 2003/01/19 02:59:32 obrien Exp $ $FreeBSD: src/sys/dev/mii/qsphy.c,v 1.10 2003/01/19 02:59:32 obrien Exp $ $FreeBSD: src/sys/dev/mii/acphy.c,v 1.12 2003/01/19 02:59:32 obrien Exp $ $FreeBSD: src/sys/dev/nge/if_nge.c,v 1.42 2003/02/19 05:47:08 imp Exp $ $FreeBSD: src/sys/dev/txp/if_txp.c,v 1.14 2003/02/19 05:47:15 imp Exp $ $FreeBSD: src/sys/dev/usb/if_aue.c,v 1.66 2003/03/05 13:25:35 shiba Exp $ $FreeBSD: src/sys/dev/usb/if_cue.c,v 1.32 2003/03/21 17:53:15 mdodd Exp $ $FreeBSD: src/sys/dev/usb/if_kue.c,v 1.44 2003/02/19 05:47:15 imp Exp $ $FreeBSD$ $FreeBSD: src/sys/dev/wi/if_wi.c,v 1.135 2003/03/22 15:39:38 imp Exp $ $FreeBSD: src/sys/dev/wi/if_wi_pccard.c,v 1.18 2003/03/18 02:47:53 imp Exp $ @(#) $FreeBSD: src/sys/netatm/spans/spans_xdr.x,v 1.4 2002/09/17 08:57:52 peter Exp $ $FreeBSD: src/sys/pci/if_dc.c,v 1.98 2003/03/31 20:22:00 jhb Exp $ $FreeBSD: src/sys/pci/if_pcn.c,v 1.37 2003/03/31 20:22:00 jhb Exp $ $FreeBSD: src/sys/pci/if_sf.c,v 1.51 2003/03/31 20:22:00 jhb Exp $ $FreeBSD: src/sys/pci/if_sis.c,v 1.68 2003/03/31 20:22:00 jhb Exp $ $FreeBSD: src/sys/pci/if_sk.c,v 1.56 2003/04/01 08:10:21 phk Exp $ $FreeBSD: src/sys/pci/if_ste.c,v 1.47 2003/03/31 20:22:00 jhb Exp $ $FreeBSD: src/sys/pci/if_ti.c,v 1.73 2003/04/01 08:57:28 phk Exp $ $FreeBSD: src/sys/pci/if_tl.c,v 1.77 2003/03/31 20:22:00 jhb Exp $ $FreeBSD: src/sys/pci/if_vr.c,v 1.65 2003/03/31 20:22:00 jhb Exp $ $FreeBSD: src/sys/pci/if_wb.c,v 1.55 2003/03/31 20:22:00 jhb Exp $ $FreeBSD: src/sys/pci/ncr.c,v 1.170 2003/02/19 05:47:41 imp Exp $ FreeBSD %s version %s (des@freebsd.org) (gcc version 3.2.1 [FreeBSD] 20021119 (release)) #4 Sun Dec 18 04:30:00 CET 1977 FreeBSD ATA driver RAID ar: FreeBSD check1 failed Qlogic ISP Driver, FreeBSD Version %d.%d, Core Version %d.%d FreeBSD Midi Driver (newmidi) %s %s FreeBSD Audio Driver (newpcm) FreeBSD WaveLAN/IEEE node <> <> <> FreeBSD/SMP: Multiprocessor System Detected: %d CPUs 20010528/FreeBSD FreeBSD PECoff FreeBSD PEcoff FreeBSD Kernel Dump FreeBSD ELF32 FreeBSD a.out Adaptec FreeBSD 4.0.0 Unix SCSI I2O HBA Driver $FreeBSD: src/sys/dev/sound/isa/ad1816.c,v 1.27 2003/02/07 14:05:33 nyan Exp $ $FreeBSD: src/sys/dev/sound/isa/es1888.c,v 1.10 2003/02/08 07:05:07 nyan Exp $ $FreeBSD: src/sys/dev/sound/isa/ess.c,v 1.25 2003/02/07 14:05:33 nyan Exp $ $FreeBSD: src/sys/dev/sound/isa/gusc.c,v 1.12 2001/08/23 11:30:50 cg Exp $ $FreeBSD: src/sys/dev/sound/isa/mss.c,v 1.84 2003/02/07 14:05:33 nyan Exp $ $FreeBSD: src/sys/dev/sound/isa/sb16.c,v 1.78 2003/02/07 14:05:33 nyan Exp $ $FreeBSD: src/sys/dev/sound/isa/sb8.c,v 1.71 2003/02/07 14:05:33 nyan Exp $ $FreeBSD: src/sys/dev/sound/isa/sbc.c,v 1.38 2003/02/07 14:05:33 nyan Exp $ $FreeBSD: src/sys/dev/sound/isa/sndbuf_dma.c,v 1.1 2003/02/07 14:05:33 nyan Exp $ $FreeBSD: src/sys/dev/sound/pci/als4000.c,v 1.10 2003/02/20 17:31:11 cognet Exp $ $FreeBSD: src/sys/dev/sound/pci/cmi.c,v 1.20 2003/02/20 17:31:11 cognet Exp $ $FreeBSD: src/sys/dev/sound/pci/cs4281.c,v 1.14 2003/02/20 17:31:11 cognet Exp $ $FreeBSD: src/sys/dev/sound/pci/csa.c,v 1.24 2002/07/24 21:27:22 ambrisko Exp $ $FreeBSD: src/sys/dev/sound/pci/csapcm.c,v 1.24 2003/02/20 17:31:11 cognet Exp $ $FreeBSD: src/sys/dev/sound/pci/ds1.c,v 1.31 2003/02/20 17:31:11 cognet Exp $ $FreeBSD: src/sys/dev/sound/pci/emu10k1.c,v 1.33 2003/02/26 16:11:18 cognet Exp $ $FreeBSD: src/sys/dev/sound/pci/es137x.c,v 1.43 2003/02/20 17:31:11 cognet Exp $ $FreeBSD: src/sys/dev/sound/pci/fm801.c,v 1.17 2003/02/20 17:31:11 cognet Exp $ $FreeBSD: src/sys/dev/sound/pci/ich.c,v 1.26 2003/02/20 17:31:11 cognet Exp $ $FreeBSD: src/sys/dev/sound/pci/maestro.c,v 1.17 2002/11/26 18:16:26 cg Exp $ $FreeBSD: src/sys/dev/sound/pci/neomagic.c,v 1.27 2002/03/04 00:36:04 orion Exp $ $FreeBSD: src/sys/dev/sound/pci/solo.c,v 1.25 2003/02/20 17:31:11 cognet Exp $ $FreeBSD: src/sys/dev/sound/pci/t4dwave.c,v 1.36 2003/02/20 17:31:11 cognet Exp $ $FreeBSD: src/sys/dev/sound/pci/via8233.c,v 1.8 2003/03/26 05:51:13 orion Exp $ $FreeBSD: src/sys/dev/sound/pci/via82c686.c,v 1.24 2003/03/28 16:33:15 orion Exp $ $FreeBSD: src/sys/dev/sound/pci/vibes.c,v 1.12 2003/02/20 17:31:11 cognet Exp $ $FreeBSD: src/sys/dev/sound/pcm/ac97.c,v 1.38 2003/03/20 18:17:39 orion Exp $ $FreeBSD: src/sys/dev/sound/pcm/ac97_patch.c,v 1.1 2003/01/25 16:54:05 orion Exp $ $FreeBSD: src/sys/dev/sound/pcm/buffer.c,v 1.18 2003/02/20 17:31:12 cognet Exp $ $FreeBSD: src/sys/dev/sound/pcm/channel.c,v 1.88 2003/02/26 14:38:19 orion Exp $ $FreeBSD: src/sys/dev/sound/pcm/dsp.c,v 1.62 2003/03/25 00:07:01 jake Exp $ $FreeBSD: src/sys/dev/sound/pcm/fake.c,v 1.12 2003/02/19 05:47:12 imp Exp $ $FreeBSD: src/sys/dev/sound/pcm/feeder.c,v 1.29 2003/03/05 14:48:28 orion Exp $ $FreeBSD: src/sys/dev/sound/pcm/feeder_fmt.c,v 1.10 2003/03/05 14:48:28 orion Exp $ $FreeBSD: src/sys/dev/sound/pcm/feeder_rate.c,v 1.9 2003/03/05 14:48:28 orion Exp $ $FreeBSD: src/sys/dev/sound/pcm/mixer.c,v 1.31 2003/03/03 12:15:46 phk Exp $ $FreeBSD: src/sys/dev/sound/pcm/sndstat.c,v 1.13 2003/03/03 12:15:46 phk Exp $ $FreeBSD: src/sys/dev/sound/pcm/sound.c,v 1.83 2003/02/19 05:47:12 imp Exp $ $FreeBSD: src/sys/dev/sound/pcm/vchan.c,v 1.12 2003/02/19 05:47:12 imp Exp $ Copyright (c) 1992-2003 The FreeBSD Project. @(#)FreeBSD 5.0-CURRENT #2031: Tue Apr 1 22:33:26 EST 2003 FreeBSD GCC: (GNU) 3.2.1 [FreeBSD] 20021119 (release) [1739 duplicates of previous line deleted] $FreeBSD: src/sys/dev/dpt/dpt.h,v 1.14 2003/03/29 08:30:45 mdodd Exp $ $FreeBSD: src/sys/dev/dpt/dpt.h,v 1.14 2003/03/29 08:30:45 mdodd Exp $ $FreeBSD: src/sys/dev/dpt/dpt_scsi.c,v 1.40 2003/03/29 14:51:50 mdodd Exp $ $FreeBSD: src/sys/dev/dpt/dpt.h,v 1.14 2003/03/29 08:30:45 mdodd Exp $ @(#) $FreeBSD: src/sys/dev/hea/eni.c,v 1.22 2002/06/14 16:59:37 arr Exp $ @(#) $FreeBSD: src/sys/dev/hea/eni_buffer.c,v 1.16 2003/02/27 08:56:41 harti Exp $ @(#) $FreeBSD: src/sys/dev/hea/eni_globals.c,v 1.9 2002/06/14 16:59:37 arr Exp $ @(#) $FreeBSD: src/sys/dev/hea/eni_if.c,v 1.11 2002/03/20 02:07:22 alfred Exp $ @(#) $FreeBSD: src/sys/dev/hea/eni_init.c,v 1.7 2002/11/06 22:58:55 jhb Exp $ @(#) $FreeBSD: src/sys/dev/hea/eni_intr.c,v 1.9 2002/03/20 02:07:22 alfred Exp $ @(#) $FreeBSD$ @(#) $FreeBSD: src/sys/dev/hea/eni_transmit.c,v 1.15 2002/11/06 22:58:55 jhb Exp $ @(#) $FreeBSD: src/sys/dev/hea/eni_vcm.c,v 1.12 2002/11/08 18:27:28 jhb Exp $ @(#) $FreeBSD: src/sys/dev/hfa/fore_buffer.c,v 1.12 2002/08/22 21:23:59 archie Exp $ @(#) $FreeBSD: src/sys/dev/hfa/fore_command.c,v 1.14 2003/03/02 16:54:33 des Exp $ @(#) $FreeBSD: src/sys/dev/hfa/fore_globals.c,v 1.10 2002/06/14 16:59:37 arr Exp $ @(#) $FreeBSD: src/sys/dev/hfa/fore_if.c,v 1.10 2002/06/24 05:03:44 arr Exp $ @(#) $FreeBSD: src/sys/dev/hfa/fore_init.c,v 1.13 2002/06/24 05:03:44 arr Exp $ @(#) $FreeBSD: src/sys/dev/hfa/fore_intr.c,v 1.9 2000/12/07 22:19:03 phk Exp $ @(#) $FreeBSD: src/sys/dev/hfa/fore_output.c,v 1.14 2002/11/06 22:58:55 jhb Exp $ @(#) $FreeBSD$ @(#) $FreeBSD: src/sys/dev/hfa/fore_stats.c,v 1.9 2002/06/24 05:03:44 arr Exp $ @(#) $FreeBSD: src/sys/dev/hfa/fore_timer.c,v 1.7 2000/10/30 20:37:00 phk Exp $ @(#) $FreeBSD: src/sys/dev/hfa/fore_transmit.c,v 1.9 2002/06/24 05:03:44 arr Exp $ @(#) $FreeBSD: src/sys/dev/hfa/fore_vcm.c,v 1.8 2000/10/30 20:37:00 phk Exp $ $FreeBSD: src/sys/dev/puc/puc.c,v 1.22 2003/03/15 16:25:40 sobomax Exp $ $FreeBSD: src/sys/dev/puc/puc_pci.c,v 1.4 2002/09/01 01:59:38 jmallett Exp $ $FreeBSD: src/sys/dev/puc/pucdata.c,v 1.17 2003/03/15 16:25:40 sobomax Exp $ $FreeBSD: src/sys/dev/sio/sio_puc.c,v 1.5 2002/11/07 22:22:10 jhb Exp $ $FreeBSD: src/sys/dev/trm/trm.c,v 1.6 2003/02/20 03:21:34 cognet Exp $ $FreeBSD: src/sys/dev/usb/ubsa.c,v 1.6 2003/02/19 05:47:15 imp Exp $ $FreeBSD: src/sys/kern/md5c.c,v 1.20 2002/10/20 22:33:42 phk Exp $ $FreeBSD: src/sys/libkern/strlcat.c,v 1.8 2002/09/06 06:04:36 peter Exp $ $FreeBSD: src/sys/libkern/strlcpy.c,v 1.6 2002/09/06 06:04:36 peter Exp $ $FreeBSD: src/sys/libkern/strsep.c,v 1.6 2002/10/10 17:02:11 rwatson Exp $ @(#) $FreeBSD: src/sys/netatm/atm_aal5.c,v 1.16 2002/05/31 11:52:31 tanimura Exp $ @(#) $FreeBSD: src/sys/netatm/atm_cm.c,v 1.25 2003/02/19 05:47:30 imp Exp $ @(#) $FreeBSD$ @(#) $FreeBSD: src/sys/netatm/atm_if.c,v 1.21 2003/02/19 05:47:30 imp Exp $ @(#) $FreeBSD: src/sys/netatm/atm_proto.c,v 1.9 2002/04/21 01:41:04 arr Exp $ @(#) $FreeBSD: src/sys/netatm/atm_signal.c,v 1.11 2002/11/08 18:27:29 jhb Exp $ @(#) $FreeBSD: src/sys/netatm/atm_socket.c,v 1.15 2003/02/19 05:47:30 imp Exp $ @(#) $FreeBSD$ @(#) $FreeBSD: src/sys/netatm/atm_usrreq.c,v 1.17 2002/12/22 05:35:02 hsu Exp $ @(#) $FreeBSD: src/sys/netatm/ipatm/ipatm_event.c,v 1.8 2000/12/07 22:19:04 phk Exp $ @(#) $FreeBSD: src/sys/netatm/ipatm/ipatm_if.c,v 1.14 2003/02/19 05:47:30 imp Exp $ @(#) $FreeBSD$ @(#) $FreeBSD: src/sys/netatm/ipatm/ipatm_load.c,v 1.15 2002/11/08 18:27:29 jhb Exp $ @(#) $FreeBSD: src/sys/netatm/ipatm/ipatm_output.c,v 1.10 2002/04/21 01:41:04 arr Exp $ @(#) $FreeBSD: src/sys/netatm/ipatm/ipatm_usrreq.c,v 1.10 2003/01/28 12:10:11 phk Exp $ @(#) $FreeBSD: src/sys/netatm/ipatm/ipatm_vcm.c,v 1.13 2003/02/19 05:47:30 imp Exp $ @(#) $FreeBSD: src/sys/netatm/sigpvc/sigpvc_if.c,v 1.14 2002/05/24 00:38:25 arr Exp $ @(#) $FreeBSD: src/sys/netatm/sigpvc/sigpvc_subr.c,v 1.12 2003/02/19 05:47:31 imp Exp $ @(#) $FreeBSD: src/sys/netatm/spans/spans_arp.c,v 1.15 2003/02/19 05:47:31 imp Exp $ @(#) $FreeBSD: src/sys/netatm/spans/spans_cls.c,v 1.15 2003/02/19 05:47:31 imp Exp $ @(#) $FreeBSD: src/sys/netatm/spans/spans_if.c,v 1.12 2002/05/24 00:39:58 arr Exp $ @(#) $FreeBSD: src/sys/netatm/spans/spans_kxdr.c,v 1.11 2002/11/08 18:27:30 jhb Exp $ @(#) $FreeBSD: src/sys/netatm/spans/spans_msg.c,v 1.14 2003/02/19 05:47:31 imp Exp $ @(#) $FreeBSD: src/sys/netatm/spans/spans_print.c,v 1.9 2002/03/20 08:00:51 alfred Exp $ @(#) $FreeBSD: src/sys/netatm/spans/spans_proto.c,v 1.11 2003/02/19 05:47:31 imp Exp $ @(#) $FreeBSD: src/sys/netatm/spans/spans_subr.c,v 1.11 2003/02/19 05:47:31 imp Exp $ @(#) $FreeBSD: src/sys/netatm/spans/spans_util.c,v 1.9 2002/12/30 21:18:09 schweikh Exp $ @(#) $FreeBSD: src/sys/netatm/uni/q2110_sigaa.c,v 1.9 2002/11/08 18:27:30 jhb Exp $ @(#) $FreeBSD: src/sys/netatm/uni/q2110_sigcpcs.c,v 1.10 2003/02/23 22:26:39 obrien Exp $ @(#) $FreeBSD: src/sys/netatm/uni/q2110_subr.c,v 1.7 2000/10/30 07:42:05 phk Exp $ @(#) $FreeBSD: src/sys/netatm/uni/qsaal1_sigaa.c,v 1.9 2002/11/08 18:27:30 jhb Exp $ @(#) $FreeBSD: src/sys/netatm/uni/qsaal1_sigcpcs.c,v 1.10 2003/02/23 22:26:39 obrien Exp $ @(#) $FreeBSD: src/sys/netatm/uni/qsaal1_subr.c,v 1.7 2000/10/30 07:42:05 phk Exp $ @(#) $FreeBSD: src/sys/netatm/uni/sscf_uni.c,v 1.16 2003/02/19 05:47:31 imp Exp $ @(#) $FreeBSD: src/sys/netatm/uni/sscf_uni_lower.c,v 1.10 2002/11/08 18:27:30 jhb Exp $ @(#) $FreeBSD: src/sys/netatm/uni/sscf_uni_upper.c,v 1.10 2002/11/08 18:27:30 jhb Exp $ @(#) $FreeBSD: src/sys/netatm/uni/sscop.c,v 1.15 2003/02/19 05:47:31 imp Exp $ @(#) $FreeBSD: src/sys/netatm/uni/sscop_lower.c,v 1.13 2002/12/30 21:18:09 schweikh Exp $ @(#) $FreeBSD: src/sys/netatm/uni/sscop_pdu.c,v 1.10 2002/11/08 18:27:30 jhb Exp $ @(#) $FreeBSD: src/sys/netatm/uni/sscop_sigaa.c,v 1.8 2002/11/08 18:27:30 jhb Exp $ @(#) $FreeBSD: src/sys/netatm/uni/sscop_sigcpcs.c,v 1.9 2003/02/23 22:26:39 obrien Exp $ @(#) $FreeBSD: src/sys/netatm/uni/sscop_subr.c,v 1.14 2003/02/23 22:26:39 obrien Exp $ @(#) $FreeBSD: src/sys/netatm/uni/sscop_timer.c,v 1.9 2002/03/20 08:00:53 alfred Exp $ @(#) $FreeBSD: src/sys/netatm/uni/sscop_upper.c,v 1.12 2002/11/08 18:27:30 jhb Exp $ @(#) $FreeBSD: src/sys/netatm/uni/uni_load.c,v 1.10 2002/03/20 08:00:53 alfred Exp $ @(#) $FreeBSD: src/sys/netatm/uni/uniarp.c,v 1.15 2003/02/19 05:47:31 imp Exp $ @(#) $FreeBSD: src/sys/netatm/uni/uniarp_cache.c,v 1.10 2003/02/19 05:47:31 imp Exp $ @(#) $FreeBSD: src/sys/netatm/uni/uniarp_input.c,v 1.11 2002/03/20 08:00:53 alfred Exp $ @(#) $FreeBSD: src/sys/netatm/uni/uniarp_output.c,v 1.8 2002/04/19 17:45:21 arr Exp $ @(#) $FreeBSD: src/sys/netatm/uni/uniarp_timer.c,v 1.9 2002/06/13 14:32:51 arr Exp $ @(#) $FreeBSD: src/sys/netatm/uni/uniarp_vcm.c,v 1.12 2003/02/19 05:47:31 imp Exp $ @(#) $FreeBSD: src/sys/netatm/uni/uniip.c,v 1.13 2003/02/19 05:47:31 imp Exp $ @(#) $FreeBSD: src/sys/netatm/uni/unisig_decode.c,v 1.14 2003/02/19 05:47:31 imp Exp $ @(#) $FreeBSD: src/sys/netatm/uni/unisig_encode.c,v 1.12 2002/11/08 18:27:30 jhb Exp $ @(#) $FreeBSD: src/sys/netatm/uni/unisig_if.c,v 1.13 2002/06/13 14:32:51 arr Exp $ @(#) $FreeBSD: src/sys/netatm/uni/unisig_mbuf.c,v 1.9 2000/12/07 22:19:06 phk Exp $ @(#) $FreeBSD: src/sys/netatm/uni/unisig_msg.c,v 1.13 2003/01/21 08:56:01 alfred Exp $ @(#) $FreeBSD: src/sys/netatm/uni/unisig_print.c,v 1.10 2003/01/01 18:48:55 schweikh Exp $ @(#) $FreeBSD: src/sys/netatm/uni/unisig_proto.c,v 1.9 2000/12/07 22:19:06 phk Exp $ @(#) $FreeBSD: src/sys/netatm/uni/unisig_sigmgr_state.c,v 1.12 2002/04/19 17:45:21 arr Exp $ @(#) $FreeBSD: src/sys/netatm/uni/unisig_subr.c,v 1.13 2003/02/19 05:47:31 imp Exp $ @(#) $FreeBSD: src/sys/netatm/uni/unisig_util.c,v 1.10 2002/06/13 14:32:51 arr Exp $ @(#) $FreeBSD: src/sys/netatm/uni/unisig_vc_state.c,v 1.14 2003/02/19 05:47:31 imp Exp $ $FreeBSD: src/sys/nfs/nfs_common.c,v 1.114 2003/02/19 05:47:38 imp Exp $ $FreeBSD: src/sys/nfsclient/bootp_subr.c,v 1.47 2003/02/19 05:47:38 imp Exp $ $FreeBSD: src/sys/nfsclient/krpc_subr.c,v 1.22 2003/02/19 05:47:38 imp Exp $ $FreeBSD: src/sys/nfsclient/nfs_bio.c,v 1.117 2003/03/04 00:04:43 jeff Exp $ $FreeBSD: src/sys/nfsclient/nfs_node.c,v 1.61 2003/02/19 05:47:38 imp Exp $ $FreeBSD: src/sys/nfsclient/nfs_socket.c,v 1.97 2003/03/31 22:49:17 jeff Exp $ $FreeBSD: src/sys/nfsclient/nfs_subs.c,v 1.117 2003/02/19 05:47:38 imp Exp $ $FreeBSD: src/sys/nfsclient/nfs_nfsiod.c,v 1.77 2003/03/02 16:54:38 des Exp $ $FreeBSD: src/sys/nfsclient/nfs_vfsops.c,v 1.132 2003/02/19 05:47:38 imp Exp $ $FreeBSD: src/sys/nfsclient/nfs_vnops.c,v 1.202 2003/03/31 23:26:10 thomas Exp $ $FreeBSD: src/sys/nfsclient/nfs_lock.c,v 1.33 2003/03/26 19:21:34 rwatson Exp $ $FreeBSD: src/sys/nfsserver/nfs_serv.c,v 1.132 2003/03/13 07:05:22 jeff Exp $ $FreeBSD: src/sys/nfsserver/nfs_srvsock.c,v 1.83 2003/03/02 16:54:39 des Exp $ $FreeBSD: src/sys/nfsserver/nfs_srvcache.c,v 1.35 2003/03/02 16:54:38 des Exp $ $FreeBSD: src/sys/nfsserver/nfs_srvsubs.c,v 1.120 2003/02/19 05:47:39 imp Exp $ $FreeBSD: src/sys/nfsserver/nfs_syscalls.c,v 1.87 2003/03/02 16:54:39 des Exp $ $FreeBSD: src/sys/pci/if_rl.c,v 1.92 2003/03/31 20:22:00 jhb Exp $ $FreeBSD: src/sys/pci/if_xl.c,v 1.136 2003/03/31 20:22:00 jhb Exp $ $FreeBSD: src/sys/ufs/ffs/ffs_softdep.c,v 1.139 2003/03/18 08:45:24 phk Exp $ %%% Most of the savings from stripping commits is from removing verbose compiler id "GCC: (GNU) 3.2.1 [FreeBSD] 20021119 (release)". Many of the sources that have this style bug also have the style bug of dupicate $FreeBSD$ (another one in the copyright comment). Bruce From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 21:30:52 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A45237B401; Tue, 1 Apr 2003 21:30:52 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F0DC43FB1; Tue, 1 Apr 2003 21:30:50 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id PAA11656; Wed, 2 Apr 2003 15:30:47 +1000 Date: Wed, 2 Apr 2003 15:30:46 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Ruslan Ermilov In-Reply-To: <20030401210116.GA43262@sunbay.com> Message-ID: <20030402152618.F25349@gamplex.bde.org> References: <20030329190908R.matusita@jp.FreeBSD.org> <3E857E9C.F7476A32@mindspring.com><20030331150348.GD21700@sunbay.com> <20030401135652.A53787@FreeBSD.org> <20030401210116.GA43262@sunbay.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Makoto Matsushita cc: current@freebsd.org Subject: Re: FreeBSD/alpha kern.flp flood X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 05:30:52 -0000 On Wed, 2 Apr 2003, Ruslan Ermilov wrote: > On Tue, Apr 01, 2003 at 12:22:58PM -0800, David O'Brien wrote: > > On Tue, Apr 01, 2003 at 01:56:52PM -0600, Juli Mallett wrote: > > > * De: David O'Brien [ Data: 2003-04-01 ] > > > [ Subjecte: Re: FreeBSD/alpha kern.flp flood ] > > > > On Mon, Mar 31, 2003 at 06:03:48PM +0300, Ruslan Ermilov wrote: > > > > > Anyway, I've committed the fix to release/Makefile that strips > > > > > the .comment section out from the BOOTMFS kernel. If you have > > > > ... > > > > Why can't the bits be built with -Dlint to remove rcsid's. > > > > > > Because that would change other things, wouldn't it. Like maybe > > > structure sizes or macros which need to actually work? > > > > I didn't see any issues like that with a very curiory look at the > > sources. Are you willing to take a look also? > > > With my very cursory look, I think the "#ifdef lint" part of > is going to be a major problem here. This ifdef is a bug and is not present in my version. It makes lint see different things than the compiler would and thus breaks checking of some areas. E.g., it hides the syntax error "__packed" and binary compatibility breakage for compilers that don't support __packed, and this breakage isn't even limited to the kernel. I still have the lint ifdef for __FBSDID(). Bruce From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 22:54:23 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C61737B401 for ; Tue, 1 Apr 2003 22:54:23 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D81743FAF for ; Tue, 1 Apr 2003 22:54:22 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h326sLd54840 for ; Wed, 2 Apr 2003 01:54:21 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Wed, 2 Apr 2003 01:54:21 -0500 (EST) From: Jeff Roberson To: current@freebsd.org Message-ID: <20030402015226.E64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: ULE nice behavior fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 06:54:23 -0000 It probably still needs some tweaking but it seems to be MUCH better now. New algorithm entirely. nice +20 processes will not run if anything else wants to. idleprio is still not working correctly. bde reports that this causes a 3% perf degradation for buildworld. I'd appreciate feedback from anyone brave enough to try it. I think my fork/exit code is still wrong and my cpu estimator is still a bit slow. I'll work on this soon. Cheers, Jeff From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 23:05:16 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3A1F37B401 for ; Tue, 1 Apr 2003 23:05:16 -0800 (PST) Received: from web41803.mail.yahoo.com (web41803.mail.yahoo.com [66.218.93.137]) by mx1.FreeBSD.org (Postfix) with SMTP id C085843F75 for ; Tue, 1 Apr 2003 23:05:15 -0800 (PST) (envelope-from csujun@yahoo.com) Message-ID: <20030402070515.40396.qmail@web41803.mail.yahoo.com> Received: from [207.46.71.13] by web41803.mail.yahoo.com via HTTP; Wed, 02 Apr 2003 15:05:15 CST Date: Wed, 2 Apr 2003 15:05:15 +0800 (CST) From: =?gb2312?q?Jun=20Su?= To: current@FreeBSD.org In-Reply-To: <20030401114911.GA46472@madman.celabo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 8bit Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: csujun@21cn.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 07:05:17 -0000 --- "Jacques A. Vidrine" µÄÕýÎÄ£º> On Mon, Mar 31, 2003 at 10:54:45PM -0500, Jeff > Roberson wrote: > > > 5. Either replace /usr/lib/libc_r.so.5 with > /usr/lib/libthr.so.1 or > > relink your applications against libthr.so.1 > > Happily strlen(libc_r.so.5) == strlen(libthr.so.1), > so you can also > edit your binaries' SONEEDED fields in place :-) > > ed -s /path/to/binary <<-EOF > /libc_r.so.5/ s/libc_r.so.5/libthr.so.1/ > w > q > EOF > > or similar ... > > Cheers, > -- > Jacques A. Vidrine > http://www.celabo.org/ > NTT/Verio SME . FreeBSD UNIX . > Heimdal Kerberos > jvidrine@verio.net . nectar@FreeBSD.org . > nectar@kth.se > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" A benchmark would be interested. Jun Su _________________________________________________________ Do You Yahoo!? žü¶àŸªÏ²£¬Í¬ÑùŸ«²Ê£¬NetVista A30 ÈÈÂô http://ad.cn.doubleclick.net/clk;5313999;7930402;p?http://www.ibm.com/cn/promotion/pc/netvista_a30/index.shtml From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 23:29:26 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC29437B401 for ; Tue, 1 Apr 2003 23:29:26 -0800 (PST) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C6EB43F3F for ; Tue, 1 Apr 2003 23:29:26 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0093.cvx40-bradley.dialup.earthlink.net ([216.244.42.93] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190cgT-0006cS-00; Tue, 01 Apr 2003 23:29:22 -0800 Message-ID: <3E8A9101.66FE4135@mindspring.com> Date: Tue, 01 Apr 2003 23:28:01 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: csujun@21cn.com References: <20030402070515.40396.qmail@web41803.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a44879d9401f18aea621888d9a2c7d0dba548b785378294e88350badd9bab72f9c350badd9bab72f9c cc: current@FreeBSD.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 07:29:27 -0000 Jun Su wrote: > [ ... 1:1 kernel threads implementation ... ] > > A benchmark would be interested. This request doesn't make sense. The primary performance reasoning behind a 1:1 kernel threading implementation, relative to the user space single kernel entry scheduler in the libc_r implementation is SMP scalability for threaded applications. Basically, the only reasonable benchmark, given this, for a comparison of the two would be a threaded CPU-bound program on a *non-SMP* system. That really makes no sense, because that wasn't the use case for the design goal of SMP scalability; it doesn't really matter *what* the relative performance is on UP systems, relative to the libc_r library, so long as it adds SMP scalability. Which it does. It's apples and oranges; there's really no reasonable way to compare the two implementations, since they solve different problem sets. Could you maybe ask a different question? -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 00:30:57 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 424E037B401 for ; Wed, 2 Apr 2003 00:30:57 -0800 (PST) Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45F8443FA3 for ; Wed, 2 Apr 2003 00:30:56 -0800 (PST) (envelope-from stijn@pcwin002.win.tue.nl) Received: from pcwin002.win.tue.nl (orb_rules@localhost [127.0.0.1]) by pcwin002.win.tue.nl (8.12.8/8.12.8) with ESMTP id h328UQSZ083901; Wed, 2 Apr 2003 10:30:26 +0200 (CEST) (envelope-from stijn@pcwin002.win.tue.nl) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.12.8/8.12.8/Submit) id h328UQtH083900; Wed, 2 Apr 2003 10:30:26 +0200 (CEST) Date: Wed, 2 Apr 2003 10:30:26 +0200 From: Stijn Hoop To: Jeff Roberson Message-ID: <20030402083026.GB83512@pcwin002.win.tue.nl> References: <20030331225124.W64602-100000@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" Content-Disposition: inline In-Reply-To: <20030331225124.W64602-100000@mail.chesapeake.net> User-Agent: Mutt/1.4i X-Bright-Idea: Let's abolish HTML mail! cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 08:30:57 -0000 --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 31, 2003 at 10:54:45PM -0500, Jeff Roberson wrote: > I have commited libthr. To try this out you'll need to do the following I know very very little about threads, but I'm interested as to what the purpose is of this library. Is there a document available somewhere that describes the relationships between this, KSE, libc_r, pthreads, the Giant-unwinding-make-SMP-work-better project and some of the other threads and SMP related libraries and terminology? --Stijn --=20 "...I like logs. They give me a warm fuzzy feeling. I've been known to keep logs for 30 months at a time (generally when I thought I was rotating them daily, but was actually rotating them once a month)." -- Michael Lucas, in Big Scary Daemons article 'Controlling Bandwidth' --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+ip+iY3r/tLQmfWcRAvpfAKCrMpMs6Tucn/QOHHn98pj8hUngZQCgiT9r TNhkleSj+kZlkAncNBtsg7k= =dRth -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s-- From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 01:13:05 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AB4237B401 for ; Wed, 2 Apr 2003 01:13:05 -0800 (PST) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 406C143FBF for ; Wed, 2 Apr 2003 01:13:04 -0800 (PST) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 4.12) id 190eIm-0000GB-00; Wed, 02 Apr 2003 11:13:00 +0200 Date: Wed, 2 Apr 2003 11:13:00 +0200 From: Sheldon Hearn To: Jeff Roberson Message-ID: <20030402091300.GG725@starjuice.net> Mail-Followup-To: Jeff Roberson , current@freebsd.org References: <20030402015226.E64602-100000@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030402015226.E64602-100000@mail.chesapeake.net> User-Agent: Mutt/1.5.4i Sender: Sheldon Hearn cc: current@freebsd.org Subject: Re: ULE nice behavior fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 09:13:05 -0000 On (2003/04/02 01:54), Jeff Roberson wrote: > It probably still needs some tweaking but it seems to be MUCH better now. > New algorithm entirely. > > nice +20 processes will not run if anything else wants to. Some of us have been waiting for that behaviour for a long time (long before you started working on ULE). Thanks very much! Ciao, Sheldon. From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 01:19:17 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA4D337B401 for ; Wed, 2 Apr 2003 01:19:16 -0800 (PST) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5019F43F3F for ; Wed, 2 Apr 2003 01:19:16 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0093.cvx40-bradley.dialup.earthlink.net ([216.244.42.93] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190eOl-0001Eq-00; Wed, 02 Apr 2003 01:19:12 -0800 Message-ID: <3E8AAAA1.CB4B51B0@mindspring.com> Date: Wed, 02 Apr 2003 01:17:21 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Stijn Hoop References: <20030331225124.W64602-100000@mail.chesapeake.net> <20030402083026.GB83512@pcwin002.win.tue.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4db8b4a983a519484b56f88a96dcfe43e350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: Jeff Roberson cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 09:19:17 -0000 Stijn Hoop wrote: > On Mon, Mar 31, 2003 at 10:54:45PM -0500, Jeff Roberson wrote: > > I have commited libthr. To try this out you'll need to do the following > > I know very very little about threads, but I'm interested as to what the > purpose is of this library. Is there a document available somewhere that > describes the relationships between this, KSE, libc_r, pthreads, the > Giant-unwinding-make-SMP-work-better project and some of the other > threads and SMP related libraries and terminology? No, not really: the new libthr was pretty much a "Skunk Works" project, and was not managed through the KSE project; it's really orthogonal, but builds on some of the KSE work already done in the kernel so far... most of KSE lives there. Here's a thumbnail sketch, though (forgive me, KSE folks, if I mung it too badly): pthreads: POSIX Threads is a threads API, which is specified by the standard ISO/IEC 9945-1:1996 (``POSIX.1''). libc_r: A user space implementation of the pthreads API; this implementation uses a "call conversion" scheduler, in user space, to convert blocking calls into non-blocking calls, plus a threads context switch via the user space scheduler. Like all interactive timesharing schedulers, it gives the illusion of concurrency. However, the kernel is not thread-reentrant in this model, so it does not scale to more than one CPU on an SMP system, since there is only a single scheduler context. KSE: "Kernel Schedulable Entitites" is the name of the modified scheduler activations framework, as well as the user space components, and kernel modifications, for an N:M model threading system. It has the advantage over the "libc_r" in that it causes the kernel to be thread reentrant, and so it provides SMP scalability. Because it's N:M, it also has the advantage over the 1:1 approach of causing full quantum utilization, and providing for CPU affinity for individual threads, and CPU negaffinity for threads within the same process, thereby providing for theoretically optimal CPU and other resource utilization. It also includes a user-space library component, which is incomplete at present. libthr: This is the recently committed 1:1 model threading library. It provides a simpler user space library component, which provides the same SMP scalability, as far as kernel thread reentrancy is concerned, but fails to provide for full quantum utilization, and, at present, does not directly address the CPU affinity issues itself (no sophisticated use of KSEGRP). It builds on the kernel modifications for KSE, and adds a couple of system call API's in order to manage creation, etc., of threads. The major intent is to provide for SMP scalability; as a side effect, it provides a proof-of-concept for the KSE code already in the kernel, and as such, has been very welcome. SMPng: "The Giant-unwinding-make-SMP-work-better project", to quote you. 8-). SMPng has it's own project page and documentation. To give another thumbnail drawing, it's about improving the granularity of locking and the logical seperation between kernel subsystems, so that stall barriers are eliminated. By doing this, inter-CPU contention is reduced, and you get better SMP scaling. Traditionally, when you added another CPU, you maybe got a 20% performance improvement for a 100% increase in cost. The idea is to get that 20% up to as close to 100% as possible (impossible, but you can approach that). SVR4, for example, scales well up to 4 processors on Intel. It scales higher than that, but the incremental improvement is about 80%, and so at about 4 processors, you hit a point where the cost of additional processors is higher than the value of the additional compute cycles. You may also find these resources useful: http://people.freebsd.org/~julian/threads/ http://www.freebsd.org/smp/index.html http://www.freebsd.org/projects/busdma/index.html http://www.freebsd.org/projects/projects.html Most of the documentation lives in mailing list archives, and is not terribly formal (Software Engineers, not English Majors, and all that...). -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 02:44:57 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38AC937B401; Wed, 2 Apr 2003 02:44:57 -0800 (PST) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id C719743FB1; Wed, 2 Apr 2003 02:44:53 -0800 (PST) (envelope-from ru@whale.sunbay.crimea.ua) Received: from whale.sunbay.crimea.ua (ru@localhost [127.0.0.1]) h32AinAP027981 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Apr 2003 13:44:50 +0300 (EEST) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.12.8/8.12.8/Submit) id h32AieO3027938; Wed, 2 Apr 2003 13:44:40 +0300 (EEST) (envelope-from ru) Date: Wed, 2 Apr 2003 13:44:39 +0300 From: Ruslan Ermilov To: Bruce Evans Message-ID: <20030402104439.GA26900@sunbay.com> References: <20030329190908R.matusita@jp.FreeBSD.org> <3E857E9C.F7476A32@mindspring.com> <20030329203005.GB94956@sunbay.com> <20030331150348.GD21700@sunbay.com> <20030401194712.GA10151@dragon.nuxi.com> <20030402151519.U25349@gamplex.bde.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LQksG6bCIzRHxTLp" Content-Disposition: inline In-Reply-To: <20030402151519.U25349@gamplex.bde.org> User-Agent: Mutt/1.5.4i cc: Makoto Matsushita cc: current@freebsd.org Subject: Re: FreeBSD/alpha kern.flp flood X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 10:44:57 -0000 --LQksG6bCIzRHxTLp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 02, 2003 at 03:24:59PM +1000, Bruce Evans wrote: > On Tue, 1 Apr 2003, David O'Brien wrote: >=20 > > On Mon, Mar 31, 2003 at 06:03:48PM +0300, Ruslan Ermilov wrote: > > > Anyway, I've committed the fix to release/Makefile that strips > > > the .comment section out from the BOOTMFS kernel. If you have > > > time, you can exploit the effect of this by changing sweaping > > > over src/sys/ and changing rcsid =3D "$FreeBSD$" lines to be > > > __FBSDID() -- that would put these IDs in the .comment section, > > > thus reducing the size of the stripped kernel by a few more > > > kilobytes. > > > > Why can't the bits be built with -Dlint to remove rcsid's. >=20 > This would make little difference, since using __FBSDID() or rcsid[] > in kernel sources is a style bugs, and most of the sources are missing > this style bug. >=20 I'd hardly call it a bug, since style(9) explicitly says C files should use __FBSDID(). > Most of the savings from stripping commits is from removing verbose compi= ler > id "GCC: (GNU) 3.2.1 [FreeBSD] 20021119 (release)". >=20 And I wondered why I get so huge savings where only few files put $FreeBSD$ into a .comment by way of __FBSDID(). Sure, ``objdump -s -j .comment kernel'' is full of these. David, can we get rid of the .comment section for the normal builds too, or at least not put these long GCC strings into? Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --LQksG6bCIzRHxTLp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+ir8XUkv4P6juNwoRAse0AJ9bl2HZZoKipE+/sLcTRCxqtKjO1gCbBo+S Oc0Y7xFC4cuXL7I5cUgavMI= =cIqt -----END PGP SIGNATURE----- --LQksG6bCIzRHxTLp-- From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 03:23:25 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C443C37B401 for ; Wed, 2 Apr 2003 03:23:25 -0800 (PST) Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02F0743FA3 for ; Wed, 2 Apr 2003 03:23:25 -0800 (PST) (envelope-from Alexander@Leidinger.net) Received: from fwd10.sul.t-online.de by mailout02.sul.t-online.com with smtp id 190gKi-00070n-05; Wed, 02 Apr 2003 13:23:08 +0200 Received: from Andro-Beta.Leidinger.net (520065502893-0001@[217.83.28.130]) by fmrl10.sul.t-online.com with esmtp id 190gKT-15h3TMC; Wed, 2 Apr 2003 13:22:53 +0200 Received: from Magelan.Leidinger.net (Magelan [192.168.1.1]) h32BMqOq096424; Wed, 2 Apr 2003 13:22:52 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from Magelan.Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.12.7/8.12.7) with SMTP id h32BMqGc002209; Wed, 2 Apr 2003 13:22:52 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Date: Wed, 2 Apr 2003 13:22:52 +0200 From: Alexander Leidinger To: Terry Lambert Message-Id: <20030402132252.23f4e6f3.Alexander@Leidinger.net> In-Reply-To: <3E8A9101.66FE4135@mindspring.com> References: <20030402070515.40396.qmail@web41803.mail.yahoo.com> <3E8A9101.66FE4135@mindspring.com> X-Mailer: Sylpheed version 0.8.9claws (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Sender: 520065502893-0001@t-dialin.net cc: Jeff Roberson cc: csujun@21cn.com cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 11:23:26 -0000 On Tue, 01 Apr 2003 23:28:01 -0800 Terry Lambert wrote: > The primary performance reasoning behind a 1:1 kernel threading > implementation, relative to the user space single kernel entry > scheduler in the libc_r implementation is SMP scalability for > threaded applications. I think Jeff (or someone else?) said, that some web browsers gain "something" too (serialization issues with libc_r)? I had the impression that this also applies to UP systems. Do I misremember this? If not, does it not apply to UP systems as well? Bye, Alexander. -- Actually, Microsoft is sort of a mixture between the Borg and the Ferengi. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 03:48:53 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC06037B401 for ; Wed, 2 Apr 2003 03:48:53 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E33543F93 for ; Wed, 2 Apr 2003 03:48:52 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id VAA29312; Wed, 2 Apr 2003 21:48:38 +1000 Date: Wed, 2 Apr 2003 21:48:37 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Sheldon Hearn In-Reply-To: <20030402091300.GG725@starjuice.net> Message-ID: <20030402212503.N26453@gamplex.bde.org> References: <20030402015226.E64602-100000@mail.chesapeake.net> <20030402091300.GG725@starjuice.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Jeff Roberson cc: current@freebsd.org Subject: Re: ULE nice behavior fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 11:48:54 -0000 On Wed, 2 Apr 2003, Sheldon Hearn wrote: > On (2003/04/02 01:54), Jeff Roberson wrote: > > > It probably still needs some tweaking but it seems to be MUCH better now. > > New algorithm entirely. > > > > nice +20 processes will not run if anything else wants to. > > Some of us have been waiting for that behaviour for a long time (long > before you started working on ULE). Er, this is the normal behaviour in FreeBSD-3.0 through FreeBSD-4.8, so you shouldn't have waited more than negative 4 years for it :-). The strict implementation of this behaviour in these releases causes priority inversion problems, but the problems apparently aren't very important. The scaling of niceness was re-broken in -current about 3 years ago to "fix" the priority inversion problems. This is with SCHED_4BSD. SCHED_ULE has larger problems. Bruce From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 03:58:34 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 63B6037B401 for ; Wed, 2 Apr 2003 03:58:34 -0800 (PST) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26A9943FBD for ; Wed, 2 Apr 2003 03:58:33 -0800 (PST) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 4.12) id 190gsj-0007oK-00; Wed, 02 Apr 2003 13:58:17 +0200 Date: Wed, 2 Apr 2003 13:58:17 +0200 From: Sheldon Hearn To: Bruce Evans Message-ID: <20030402115816.GN725@starjuice.net> Mail-Followup-To: Bruce Evans , Jeff Roberson , current@freebsd.org References: <20030402015226.E64602-100000@mail.chesapeake.net> <20030402091300.GG725@starjuice.net> <20030402212503.N26453@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030402212503.N26453@gamplex.bde.org> User-Agent: Mutt/1.5.4i Sender: Sheldon Hearn cc: Jeff Roberson cc: current@freebsd.org Subject: Re: ULE nice behavior fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 11:58:34 -0000 On (2003/04/02 21:48), Bruce Evans wrote: > > Some of us have been waiting for that behaviour for a long time (long > > before you started working on ULE). > > Er, this is the normal behaviour in FreeBSD-3.0 through FreeBSD-4.8, > so you shouldn't have waited more than negative 4 years for it :-). > The strict implementation of this behaviour in these releases causes > priority inversion problems, but the problems apparently aren't very > important. The scaling of niceness was re-broken in -current about 3 > years ago to "fix" the priority inversion problems. I should have realized that "a long time" would mean different things to different people, with respect to HEAD. I remember being involved in a flamefest on this issue a few years back. You were involved too. :-) However, are you sure the "nice 20 only gets unwanted CPU" behaviour is actually what you get in RELENG_4 (as opposed to your heavily patched version)? Ciao, Sheldon. From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 04:07:37 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAD0C37B401; Wed, 2 Apr 2003 04:07:37 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 144D143F93; Wed, 2 Apr 2003 04:07:36 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id WAA31094; Wed, 2 Apr 2003 22:07:29 +1000 Date: Wed, 2 Apr 2003 22:07:28 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Ruslan Ermilov In-Reply-To: <20030402104439.GA26900@sunbay.com> Message-ID: <20030402215049.G26531@gamplex.bde.org> References: <20030329190908R.matusita@jp.FreeBSD.org> <3E857E9C.F7476A32@mindspring.com><20030331150348.GD21700@sunbay.com> <20030402151519.U25349@gamplex.bde.org> <20030402104439.GA26900@sunbay.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Makoto Matsushita cc: current@freebsd.org Subject: Re: FreeBSD/alpha kern.flp flood X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 12:07:38 -0000 On Wed, 2 Apr 2003, Ruslan Ermilov wrote: > On Wed, Apr 02, 2003 at 03:24:59PM +1000, Bruce Evans wrote: > > On Tue, 1 Apr 2003, David O'Brien wrote: > > > > > On Mon, Mar 31, 2003 at 06:03:48PM +0300, Ruslan Ermilov wrote: > > > > Anyway, I've committed the fix to release/Makefile that strips > > > > the .comment section out from the BOOTMFS kernel. If you have > > > > ... > > > Why can't the bits be built with -Dlint to remove rcsid's. > > > > This would make little difference, since using __FBSDID() or rcsid[] > > in kernel sources is a style bugs, and most of the sources are missing > > this style bug. > > > I'd hardly call it a bug, since style(9) explicitly says C files > should use __FBSDID(). Another bug. __FBSDID() is is not normally used in the kernel. E.g., rev.1.1 of almost every file in libkern is about removing (sccs) id strings since their bloat is not wanted in the kernel. It is true that __FBSDID() and suitable stripping can handle this more configurably, but no one ever cared enough to change n,000 $FreeBSD$'s to __FBSDID()'s in the kernel (ugh) or provide infrastructure (#define lint doesn't count) for stripping the ids. > > Most of the savings from stripping commits is from removing verbose compiler > > id "GCC: (GNU) 3.2.1 [FreeBSD] 20021119 (release)". > > > And I wondered why I get so huge savings where only few files > put $FreeBSD$ into a .comment by way of __FBSDID(). Sure, > ``objdump -s -j .comment kernel'' is full of these. > > David, can we get rid of the .comment section for the normal > builds too, or at least not put these long GCC strings into? They bloat programs and libraries too. I once saved a MB or so in the root partition by just by removing a couple of useless words in these ids. I like having these ids in object files and static libraries but not duplicating them in executables and shared libraries. Bruce From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 04:25:18 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C17837B401 for ; Wed, 2 Apr 2003 04:25:18 -0800 (PST) Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0D5643FBF for ; Wed, 2 Apr 2003 04:25:16 -0800 (PST) (envelope-from miniyan@kt.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (3.7W/HMX-13) id VAA22119; Wed, 2 Apr 2003 21:25:15 +0900 (JST) Received: from [192.168.2.10] (l224047.ppp.asahi-net.or.jp [218.219.224.47]) by mail1.rim.or.jp (3.7W) id VAA03749; Wed, 2 Apr 2003 21:25:15 +0900 (JST) Date: Wed, 02 Apr 2003 21:25:15 +0900 From: miniyan To: Maksim Yevmenkin In-Reply-To: <3E89CDE1.4030404@cw.com> References: <20030401222211.257C.MINIYAN@kt.rim.or.jp> <3E89CDE1.4030404@cw.com> Message-Id: <20030402202800.2584.MINIYAN@kt.rim.or.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.05.08 cc: current@freebsd.org Subject: Re: bluetooth BW-BH02U reset failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 12:25:18 -0000 Hello Maksim, [...] > actually, i have added support for firmware download in ng_ubt(4) > driver and ported Broadcom firmware download utility from Linux. > this will be included into the next snapshot which will be realeased > in a few days. It's good news. I'll try it. [...] > > Could not execute command "initialize". Invalid argument > > this tells me that your userland and kernel are out of sync. you need > to recompile all userland tools. when upgrading please follow these > steps I've re-compiled with following operation. To fixed this error. > 1) download latest snapshot > > 2) extract it into your home directory. please *do not* extract > shapshot into /usr. you *should* build snapshot *outside* of > main FreeBSD source tree. > > 3) build and install kernel modules > > cd $snapshot_dir/src/sys/modules/netgraph/bluetooth > make depend > make > make install > make cleandir > > 4) build and install userspace tools > > cd $snapshot_dir/src/usr.bin/bluetooth > make depend > make > make install > make cleandir > > cd $snapshot_dir/src/usr.sbin/bluetooth > make depend > make > make install > make cleandir > > 5) build and install ports (optional) > > IMPORTANT: > > - build snapshot *outside* of FreeBSD main source tree. *Do not* > update sources in /usr/src. If you run 'cvsup' then all your > changes to /usr/src *will be lost*. > > - always update your userspace tools > > - after bulding and installing new kernel *do not* forget to > re-compile/re-install Bluetooth kernel modules (from snapshot). > you need this because kernel build will install old (stock) > Bluetooth modules > > - after making "word" please *do not* forget to re-compile/re-install > both kernel modules and userland tools from snapshot. > [...] It's good information for me. I was cvsup'd after copy bluetooth tree to /usr/src and build everything. It's very hard and waist time. This time, I understand how bluetooth tree build to make shorty and correctly. > this is different. M_NOWAIT/M_DONTWAIT and M_WAITOK/N_NOWAIT flags > have chanaged again :( this is related to the following commit: > > ====================================================================== > Revision 1.114 / (download) - annotate - [select for diffs], Mon Mar 10 > 19:39:53 2003 UTC (3 weeks ago) by phk [...] > I understand. I can separate this topic. Thank you. Takahiko -- miniyan From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 04:27:54 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7452737B401 for ; Wed, 2 Apr 2003 04:27:54 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 258F643FA3 for ; Wed, 2 Apr 2003 04:27:53 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id WAA00066; Wed, 2 Apr 2003 22:27:38 +1000 Date: Wed, 2 Apr 2003 22:27:37 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Sheldon Hearn In-Reply-To: <20030402115816.GN725@starjuice.net> Message-ID: <20030402221002.I26615@gamplex.bde.org> References: <20030402015226.E64602-100000@mail.chesapeake.net> <20030402091300.GG725@starjuice.net> <20030402212503.N26453@gamplex.bde.org> <20030402115816.GN725@starjuice.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Jeff Roberson cc: current@freebsd.org Subject: Re: ULE nice behavior fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 12:27:54 -0000 On Wed, 2 Apr 2003, Sheldon Hearn wrote: > On (2003/04/02 21:48), Bruce Evans wrote: > > > > Some of us have been waiting for that behaviour for a long time (long > > > before you started working on ULE). > > > > Er, this is the normal behaviour in FreeBSD-3.0 through FreeBSD-4.8, > > so you shouldn't have waited more than negative 4 years for it :-). > > The strict implementation of this behaviour in these releases causes > > priority inversion problems, but the problems apparently aren't very > > important. The scaling of niceness was re-broken in -current about 3 > > years ago to "fix" the priority inversion problems. > > I should have realized that "a long time" would mean different things to > different people, with respect to HEAD. I remember being involved in a > flamefest on this issue a few years back. You were involved too. :-) > > However, are you sure the "nice 20 only gets unwanted CPU" behaviour is > actually what you get in RELENG_4 (as opposed to your heavily patched > version)? I tested RELENG_4 while replying :-). I don't have any significant patches in it. "nice 20 only gets unwanted CPU" was the intended behaviour, and it still seems to work. I found it hard to see it working since I used 2.5-months-noncurrent -current utilities. I use some hacks to unbreak things like test(1) using a syscall that doesn't exist in RELENG_4, but the hacks don't extend to making ps or top work, so I couldn't use them to see what the processes were doing. Normally I use simple tests like: %%% for i in 0 20 do nice -$i sh -c "while :; do echo -n;done" & done top -o time %%% to debug scheduling of long-running (cpu hog) processes. If niceness is working right, then the priority of the nice +0 should never reach that of the nice +20 process (actually the actual priorities (actual = displayed + PZERO) mod 4). You can normally see what is happening by watching top for a while and predict what will/should happen with some practice. Bruce From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 05:10:46 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 426F537B41C; Wed, 2 Apr 2003 05:10:45 -0800 (PST) Received: from diomedes.noc.ntua.gr (diomedes.noc.ntua.gr [147.102.222.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C24D43FD7; Wed, 2 Apr 2003 05:10:43 -0800 (PST) (envelope-from past@noc.ntua.gr) Received: from ajax.noc.ntua.gr (ajax.noc.ntua.gr [147.102.220.1]) by diomedes.noc.ntua.gr (8.11.6p2/8.11.6) with ESMTP id h32DAdd67605; Wed, 2 Apr 2003 16:10:39 +0300 (EEST) Received: from noc.ntua.gr (hal.noc.ntua.gr [147.102.220.45]) by ajax.noc.ntua.gr (8.12.6p2/8.12.6) with ESMTP id h32DAc4v031485; Wed, 2 Apr 2003 16:10:38 +0300 (EEST) (envelope-from past@noc.ntua.gr) Message-ID: <3E8AE14E.8070408@noc.ntua.gr> Date: Wed, 02 Apr 2003 16:10:38 +0300 From: Panagiotis Astithas Organization: NTUA/NMC User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en, el MIME-Version: 1.0 To: current@freebsd.org X-Enigmail-Version: 0.71.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/mixed; boundary="------------040201080802090209020500" cc: Sam Leffler Subject: [PATCH] ubsec driver update for Sun Crypto Accelerator 1000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 13:10:47 -0000 This is a multi-part message in MIME format. --------------040201080802090209020500 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi, I have made a few modifications to the ubsec driver, in order to recognize and configure the Sun Crypto Accelerator 1000 PCI card. The card uses a Broadcom 5821 chip, so the modifications were minimal, but I still don't get very verbose info using "pciconf -lv": ubsec0@pci0:18:0: class=0x100000 card=0x5455108e chip=0x5454108e rev=0x01 hdr=0x00 vendor = 'Sun Microsystems' You can see that the card number and the chip number are slightly different, but not in any way similar to the other cards in my machine, so I can't figure out what to do. I also don't know how to parse the class number. dmesg output shows: ubsec0 mem 0xe2000000-0xe200ffff irq 12 at device 18.0 on pci0 ubsec0: Sun 5821 and the machine functions OK. The system is: FreeBSD devil.test.noc.ntua.gr 5.0-CURRENT FreeBSD 5.0-CURRENT #3: Wed Apr 2 10:24:39 GMT 2003 root@devil.test.noc.ntua.gr:/usr/obj/usr/src/sys/DEVIL i386 and the affected file version are: ubsec/ubsec.c: $FreeBSD: src/sys/dev/ubsec/ubsec.c,v 1.20 2003/03/18 08:45:22 phk Exp $ $OpenBSD: ubsec.c,v 1.115 2002/09/24 18:33:26 jason Exp $ ubsec/ubsecreg.h: $FreeBSD: src/sys/dev/ubsec/ubsecreg.h,v 1.4 2003/02/27 21:10:20 sam Exp $ $OpenBSD: ubsecreg.h,v 1.27 2002/09/11 22:40:31 jason Exp $ Comments are welcome. Cheers, -- Panagiotis Astithas Electrical & Computer Engineer, PhD Network Management Center National Technical University of Athens, Greece --------------040201080802090209020500 Content-Type: text/plain; name="ubsec.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ubsec.patch" diff -wu ubsec/ubsec.c /sys/dev/ubsec/ubsec.c --- ubsec/ubsec.c Tue Apr 1 15:53:55 2003 +++ /sys/dev/ubsec/ubsec.c Wed Apr 2 09:24:36 2003 @@ -194,6 +194,10 @@ static int ubsec_probe(device_t dev) { + if (pci_get_vendor(dev) == PCI_VENDOR_SUN && + pci_get_device(dev) == PCI_PRODUCT_SUN_5821 + ) + return (0); if (pci_get_vendor(dev) == PCI_VENDOR_BLUESTEEL && (pci_get_device(dev) == PCI_PRODUCT_BLUESTEEL_5501 || pci_get_device(dev) == PCI_PRODUCT_BLUESTEEL_5601)) @@ -232,6 +236,11 @@ case PCI_PRODUCT_BLUESTEEL_5601: return "Bluesteel 5601"; } return "Bluesteel unknown-part"; + case PCI_VENDOR_SUN: + switch (pci_get_device(sc->sc_dev)) { + case PCI_PRODUCT_SUN_5821: return "Sun 5821"; + } + return "Sun unknown-part"; } return "Unknown-vendor unknown-part"; } @@ -284,6 +293,15 @@ (pci_get_device(dev) == PCI_PRODUCT_BROADCOM_5821 || pci_get_device(dev) == PCI_PRODUCT_BROADCOM_5822 || pci_get_device(dev) == PCI_PRODUCT_BROADCOM_5823 )) { + /* NB: the 5821/5822 defines some additional status bits */ + sc->sc_statmask |= BS_STAT_MCR1_ALLEMPTY | + BS_STAT_MCR2_ALLEMPTY; + sc->sc_flags |= UBS_FLAGS_KEY | UBS_FLAGS_RNG | + UBS_FLAGS_LONGCTX | UBS_FLAGS_HWNORM | UBS_FLAGS_BIGKEY; + } + + if (pci_get_vendor(dev) == PCI_VENDOR_SUN && + pci_get_device(dev) == PCI_PRODUCT_SUN_5821) { /* NB: the 5821/5822 defines some additional status bits */ sc->sc_statmask |= BS_STAT_MCR1_ALLEMPTY | BS_STAT_MCR2_ALLEMPTY; diff -wu ubsec/ubsecreg.h /sys/dev/ubsec/ubsecreg.h --- ubsec/ubsecreg.h Tue Apr 1 15:18:21 2003 +++ /sys/dev/ubsec/ubsecreg.h Wed Apr 2 09:24:45 2003 @@ -46,6 +46,10 @@ #define PCI_VENDOR_BROADCOM 0x14e4 /* Broadcom */ #define PCI_VENDOR_BLUESTEEL 0x15ab /* Bluesteel Networks */ +#define PCI_VENDOR_SUN 0x108e /* Sun Microsystems */ + +/* Sun Microsystems */ +#define PCI_PRODUCT_SUN_5821 0x5454 /* BCM5821 */ /* Bluesteel Networks */ #define PCI_PRODUCT_BLUESTEEL_5501 0x0000 /* 5501 */ --------------040201080802090209020500-- From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 05:55:00 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92DA037B401; Wed, 2 Apr 2003 05:55:00 -0800 (PST) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1877D43FAF; Wed, 2 Apr 2003 05:55:00 -0800 (PST) (envelope-from qhwt@myrealbox.com) Received: from localhost qhwt@smtp-send.myrealbox.com [220.97.121.27] $ on Novell NetWare; Wed, 02 Apr 2003 06:55:03 -0700 Date: Wed, 2 Apr 2003 22:54:56 +0900 From: qhwt@myrealbox.com To: mdodd@freebsd.org Message-ID: <20030402135456.GA1421.qhwt@myrealbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i cc: current@freebsd.org Subject: RFC 3514 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 13:55:00 -0000 Hello, I'd be glad if you revert the change in rev 1.23 of sys/netinet/ip.h unless there's some special reason you can't undo your rfc3514 implementation. Thanks. (Yes, I regret not having been subscribed to cvs-all list...:) From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 06:00:34 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5E2337B401 for ; Wed, 2 Apr 2003 06:00:34 -0800 (PST) Received: from dsl093-019-250.msp1.dsl.speakeasy.net (dsl093-019-250.msp1.dsl.speakeasy.net [66.93.19.250]) by mx1.FreeBSD.org (Postfix) with SMTP id C53E443FAF for ; Wed, 2 Apr 2003 06:00:33 -0800 (PST) (envelope-from peter@jocose.org) Received: (qmail 54106 invoked from network); 2 Apr 2003 14:00:33 -0000 Received: from unknown (HELO jocose.org) (10.0.0.198) by 0 with SMTP; 2 Apr 2003 14:00:33 -0000 Message-ID: <3E8AED1B.10606@jocose.org> Date: Wed, 02 Apr 2003 08:00:59 -0600 From: Peter Schultz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030226 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-core@FreeBSD.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 14:00:35 -0000 Hi, I hope that core will approve removing sendmail from FreeBSD-CURRENT. Thank you, Pete... From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 06:07:40 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5965F37B401 for ; Wed, 2 Apr 2003 06:07:40 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C3EF43F3F for ; Wed, 2 Apr 2003 06:07:39 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0051.cvx21-bradley.dialup.earthlink.net ([209.179.192.51] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190itb-00014R-00; Wed, 02 Apr 2003 06:07:20 -0800 Message-ID: <3E8AEE1E.AB0583B0@mindspring.com> Date: Wed, 02 Apr 2003 06:05:18 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Alexander Leidinger References: <20030402070515.40396.qmail@web41803.mail.yahoo.com> <20030402132252.23f4e6f3.Alexander@Leidinger.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4f17c28a00ea016a4bfa358b3d4b1a815350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: Jeff Roberson cc: csujun@21cn.com cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 14:07:40 -0000 Alexander Leidinger wrote: > On Tue, 01 Apr 2003 23:28:01 -0800 > Terry Lambert wrote: > > The primary performance reasoning behind a 1:1 kernel threading > > implementation, relative to the user space single kernel entry > > scheduler in the libc_r implementation is SMP scalability for > > threaded applications. > > I think Jeff (or someone else?) said, that some web browsers gain > "something" too (serialization issues with libc_r)? I had the impression > that this also applies to UP systems. > > Do I misremember this? If not, does it not apply to UP systems as well? FWIW: the libc_r reentrancy isn't fixed by a 1:1 model for anything but calls for which there are no non-blocking alternative kernel APIs. That means you are saved on things like System V IPC interfaces (which you were saved on before, if you used my kqueue patch for System V IPC to turn it into events), but the file I/O, which is mostly what a browser is doing, is not significantly improved. And for calls for which entrancy must be serialized, like the resolver, you are stuck serializing in user space. There is potential for some additional interleaved I/O occurring, when the kernel is multiply entrant, rather than EWOULDBLOCK plus a call conversion using a non-blocking file descriptor, that's true. I'm not sure that anything is gained by this in the UP case, however. Oh, and your process gets to compete for quantum as if it were "number of threads" processes. This is actually wrong, if you are PTHREAD_SCOPE_PROCESS, and setting the other option, PTHREAD_SCOPE_SYSTEM, requires root priviledges (but is on by default in the libthr implementation, because a 1:1 model requires more sophisticated scheduler support). You can get this same "cheat for extra quantum" effect with libc_r by using the same root priviledge to "nice" your process to a higher priority relative to the default. The other issue with going from the user space model to a kernel 1:1 model is that you are trading additional context switch overhead, by way of not fully utilizing your quantum, when you go into the kernel to block, instead of doing the call conversion: when you go to sleep, you hand the remainder of your quantum back to the system in 1:1, whereas with the libc_r, you hand it to another of your own threads. This is also what the N:M addresses. This also makes you less efficient when it comes to context switch overhead, since without thread-in-group affinity, when you give up the quantum, you are likely to take a full context switch (%cr3 reload for a different process; for example, cron runs once a second, and there are other "standard" system processes which are far from idle). In other words, you only see a benefit for a lone threaded application on a relatively quiecent system, which is OK, I guess, for a microbenchmark, but pretty poor when it comes to real world systems, which tend to be more heavily loaded. The last time and of this difference in overhead between the models was measured in any meaningful way (AFAIK) was in an article in (November?) 2001 in: Parallel and Distributed Systems, IEEE Trans. on (T-PDS) Which is where most of the academic work on scheduling and load balancing for parallel and distributed systems takes place. Unfortunately, these papers are not available online, unless you are an IEEE member, who also subscribes to T-PDS. Maybe you can find them, if you work at IBM and have access to a good technical library (e.g. Almaden), or if you have access to the Berkeley or Stanford libraries, or some other good technical library. There could have been a more recent paper, starting about 8 months back, which I don't know about (I need to take a trip to the library myself ;^)). The bottom line is that the 1:1 model is primarily useful for improving SMP scalability at this time, and that the overhead tradeoffs that are there right now don't really favor it, IMO, in a UP system. FreeBSD's libc_r has been in developement for nearly a decade; it is a *very good* pthreads implementation, and the only places it falls down, really, are in SMP scalability, and some blocking system calls that aren't amenable to conversion. You'll note that the System V IPC interfaces are not supported in a threaded environment by the POSIX standard; most of these blocking cases aren't really a problem. User space serialization in things like the resolver, which only opens one socket to do lookups, and can only deal with a single response context are a cross everyone bears. Mostly this bothers no one, because all browsers cache responses, there is response locality, and it's not a problem unless you compile in support for multiple protocol families (IPv4 + IPv6 support in the same browser usually means waiting for an IPv6 lookup timeout, if the remote host is not an RFC compliant DNS server, and fails to return an immediate reject response, like it's supposed to do). If you "fix" that for libthr, you also "fix" it for libc_r. -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 06:13:39 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57E0937B401 for ; Wed, 2 Apr 2003 06:13:39 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6E9B43F85 for ; Wed, 2 Apr 2003 06:13:38 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0051.cvx21-bradley.dialup.earthlink.net ([209.179.192.51] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190izh-0002MD-00; Wed, 02 Apr 2003 06:13:37 -0800 Message-ID: <3E8AEFBF.D1D640E3@mindspring.com> Date: Wed, 02 Apr 2003 06:12:15 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Schultz References: <3E8AED1B.10606@jocose.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4f17c28a00ea016a4ac3328327dae5d5b350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 14:13:39 -0000 Peter Schultz wrote: > Hi, > > I hope that core will approve removing sendmail from FreeBSD-CURRENT. I'm pretty sure they will, just as soon as someone provides patches to make installed base system components like sendmail into "preinstalled packages", and then steps up and makes some other MTA and MSA able to be installed by default instead, so that things like "/etc/daily", "/etc/weekly", and so on can still send an email to the local "root" user upon completion. PS: This comes up every time a sendmail CERT advisory happens, but then no one provides the necessary patches to make email continue to work with sendmail deinstalled, or the package files to allow it to be deinstalled and replaces easily. -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 06:20:57 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AEAB37B401 for ; Wed, 2 Apr 2003 06:20:57 -0800 (PST) Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCCAC43F85 for ; Wed, 2 Apr 2003 06:20:56 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: from blackhelicopters.org (mwlucas@localhost [127.0.0.1]) by blackhelicopters.org (8.12.8/8.12.8) with ESMTP id h32EKtDn031929 for ; Wed, 2 Apr 2003 09:20:55 -0500 (EST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.12.8/8.12.8/Submit) id h32EKtRf031928 for current@FreeBSD.org; Wed, 2 Apr 2003 09:20:55 -0500 (EST) Date: Wed, 2 Apr 2003 09:20:55 -0500 From: "Michael W . Lucas" To: current@FreeBSD.org Message-ID: <20030402092055.A31850@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Subject: breakage this morning X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 14:20:57 -0000 While I'm all for a sense of humor, and agree that implementation of the IP_EVIL flag is vital for FreeBSD to be a modern operating system, it stops being funny when it breaks world. ... ===> sbin/ping cc -O -pipe -march=pentiumpro -DIPSEC -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/sbin/ping/ping.c /usr/src/sbin/ping/ping.c: In function `main': /usr/src/sbin/ping/ping.c:605: `IP_EVIL' undeclared (first use in this function) /usr/src/sbin/ping/ping.c:605: (Each undeclared identifier is reported only once /usr/src/sbin/ping/ping.c:605: for each function it appears in.) /usr/src/sbin/ping/ping.c: In function `pr_pack': /usr/src/sbin/ping/ping.c:1004: `IP_EVIL' undeclared (first use in this function) *** Error code 1 Stop in /usr/src/sbin/ping. ... ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org http://www.BlackHelicopters.org/~mwlucas/ Absolute BSD: http://www.AbsoluteBSD.com/ From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 06:30:12 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5A6337B401 for ; Wed, 2 Apr 2003 06:30:12 -0800 (PST) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF56C43F3F for ; Wed, 2 Apr 2003 06:30:10 -0800 (PST) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 4.12) id 190jF9-0000Fd-00; Wed, 02 Apr 2003 16:29:35 +0200 Date: Wed, 2 Apr 2003 16:29:35 +0200 From: Sheldon Hearn To: Terry Lambert Message-ID: <20030402142935.GA790@starjuice.net> Mail-Followup-To: Terry Lambert , Alexander Leidinger , Jeff Roberson , csujun@21cn.com, current@freebsd.org References: <20030402070515.40396.qmail@web41803.mail.yahoo.com> <20030402132252.23f4e6f3.Alexander@Leidinger.net> <3E8AEE1E.AB0583B0@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E8AEE1E.AB0583B0@mindspring.com> User-Agent: Mutt/1.5.4i Sender: Sheldon Hearn cc: Alexander Leidinger cc: csujun@21cn.com cc: current@freebsd.org cc: Jeff Roberson Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 14:30:13 -0000 On (2003/04/02 06:05), Terry Lambert wrote: > > I think Jeff (or someone else?) said, that some web browsers gain > > "something" too (serialization issues with libc_r)? I had the impression > > that this also applies to UP systems. > > > > Do I misremember this? If not, does it not apply to UP systems as well? > > FWIW: the libc_r reentrancy isn't fixed by a 1:1 model for > anything but calls for which there are no non-blocking > alternative kernel APIs. [...long ramble...] For all the rambling, I'm happy to report that my SCHED_ULE + libthr UP workstation feels noticibly more responsive when I have several Mozilla tabs all loading pages simultaneously while I'm trying to make a threaded Java IDE do something sensible. It's possible that I'm actually seeing the impact of other changes that have been committed in the last week, I suppose. Ciao, Sheldon. From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 06:30:59 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D87DA37B401 for ; Wed, 2 Apr 2003 06:30:59 -0800 (PST) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7D6B43F75 for ; Wed, 2 Apr 2003 06:30:58 -0800 (PST) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 4.12) id 190jGR-0000Fz-00; Wed, 02 Apr 2003 16:30:55 +0200 Date: Wed, 2 Apr 2003 16:30:55 +0200 From: Sheldon Hearn To: "Michael W . Lucas" Message-ID: <20030402143055.GB790@starjuice.net> Mail-Followup-To: "Michael W . Lucas" , current@FreeBSD.org References: <20030402092055.A31850@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030402092055.A31850@blackhelicopters.org> User-Agent: Mutt/1.5.4i Sender: Sheldon Hearn cc: current@FreeBSD.org Subject: Re: breakage this morning X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 14:31:00 -0000 On (2003/04/02 09:20), Michael W . Lucas wrote: > While I'm all for a sense of humor, and agree that implementation of > the IP_EVIL flag is vital for FreeBSD to be a modern operating system, > it stops being funny when it breaks world. You sure you didn't get caught in the middle of a cvsup mirror sync? I have an IP_EVIL world and kernel running fine here. Ciao, Sheldon. From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 06:37:13 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF7A737B401 for ; Wed, 2 Apr 2003 06:37:13 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A6AE43F85 for ; Wed, 2 Apr 2003 06:37:13 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.9/8.12.9) with SMTP id h32EbMYY034818; Wed, 2 Apr 2003 09:37:23 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 2 Apr 2003 09:37:22 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Sheldon Hearn In-Reply-To: <20030402142935.GA790@starjuice.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Alexander Leidinger cc: csujun@21cn.com cc: current@freebsd.org cc: Jeff Roberson Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 14:37:14 -0000 On Wed, 2 Apr 2003, Sheldon Hearn wrote: > On (2003/04/02 06:05), Terry Lambert wrote: > > > > I think Jeff (or someone else?) said, that some web browsers gain > > > "something" too (serialization issues with libc_r)? I had the impression > > > that this also applies to UP systems. > > > > > > Do I misremember this? If not, does it not apply to UP systems as well? > > > > FWIW: the libc_r reentrancy isn't fixed by a 1:1 model for > > anything but calls for which there are no non-blocking > > alternative kernel APIs. [...long ramble...] > > For all the rambling, I'm happy to report that my SCHED_ULE + libthr UP > workstation feels noticibly more responsive when I have several Mozilla > tabs all loading pages simultaneously while I'm trying to make a > threaded Java IDE do something sensible. > > It's possible that I'm actually seeing the impact of other changes that > have been committed in the last week, I suppose. You should notice marked interactivity and UI latency improvements with threaded GUI apps over libc_r because GUI threads will generally no longer be blocked when disk I/O and blocking I/O occurs. For example, applications like Open Office, Netscape, et al, really get a lot better with 1:1. Likewise, non-interactive applications that are disk I/O-intensive, such as mysql, will also perform substantially better because a thread that hits blocking using an interface that doesn't support non-blocking I/O (such as the file system) won't clog up the application. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 06:43:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CB9537B401 for ; Wed, 2 Apr 2003 06:43:38 -0800 (PST) Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5703343FA3 for ; Wed, 2 Apr 2003 06:43:35 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: from blackhelicopters.org (mwlucas@localhost [127.0.0.1]) by blackhelicopters.org (8.12.8/8.12.8) with ESMTP id h32EhYDn032202 for ; Wed, 2 Apr 2003 09:43:34 -0500 (EST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.12.8/8.12.8/Submit) id h32EhYTU032201 for current@FreeBSD.org; Wed, 2 Apr 2003 09:43:34 -0500 (EST) Date: Wed, 2 Apr 2003 09:43:34 -0500 From: "Michael W . Lucas" To: current@FreeBSD.org Message-ID: <20030402094334.C31850@blackhelicopters.org> References: <20030402092055.A31850@blackhelicopters.org> <20030402143055.GB790@starjuice.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030402143055.GB790@starjuice.net>; from sheldonh@starjuice.net on Wed, Apr 02, 2003 at 04:30:55PM +0200 Subject: Re: breakage this morning X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 14:43:38 -0000 On Wed, Apr 02, 2003 at 04:30:55PM +0200, Sheldon Hearn wrote: > On (2003/04/02 09:20), Michael W . Lucas wrote: > > > While I'm all for a sense of humor, and agree that implementation of > > the IP_EVIL flag is vital for FreeBSD to be a modern operating system, > > it stops being funny when it breaks world. > > You sure you didn't get caught in the middle of a cvsup mirror sync? I > have an IP_EVIL world and kernel running fine here. According to some folks on IRC, it was renamed to "IP_EF" in src/sys/netinet/ip.h, but not renamed in ping.c. I just finished re-supping from cvsup16, and while I got some updates, an update to ping_c was not among them... ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org http://www.BlackHelicopters.org/~mwlucas/ Absolute BSD: http://www.AbsoluteBSD.com/ From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 06:45:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B4ED37B404 for ; Wed, 2 Apr 2003 06:45:38 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2590F43FCB for ; Wed, 2 Apr 2003 06:45:37 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0051.cvx21-bradley.dialup.earthlink.net ([209.179.192.51] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190jUQ-0000iB-00; Wed, 02 Apr 2003 06:45:23 -0800 Message-ID: <3E8AF723.A7D00C14@mindspring.com> Date: Wed, 02 Apr 2003 06:43:47 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn References: <20030402070515.40396.qmail@web41803.mail.yahoo.com> <20030402132252.23f4e6f3.Alexander@Leidinger.net> <3E8AEE1E.AB0583B0@mindspring.com> <20030402142935.GA790@starjuice.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4351c49459e4f41d74a4e787fcca89fde350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: Alexander Leidinger cc: csujun@21cn.com cc: current@freebsd.org cc: Jeff Roberson Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 14:45:38 -0000 Sheldon Hearn wrote: > On (2003/04/02 06:05), Terry Lambert wrote: > > > Do I misremember this? If not, does it not apply to UP systems as well? > > > > FWIW: the libc_r reentrancy isn't fixed by a 1:1 model for > > anything but calls for which there are no non-blocking > > alternative kernel APIs. [...long ramble...] When someone asks you a question and you answer it, it's not a "ramble", it's an "answer". 8-). > For all the rambling, I'm happy to report that my SCHED_ULE + libthr > UP workstation feels noticibly more responsive when I have several > Mozilla tabs all loading pages simultaneously while I'm trying to make a > threaded Java IDE do something sensible. You need to read things. I already explained that you were competing unfairly for quantum with other processes, in violation of POSIX.1, by virtue of defaulting to PTHREAD_SCOPE_SYSTEM. If you want to use PTHREAD_SCOPE_SYSTEM, you are supposed to have priviledges. Also, as I suggested, try nice'ing up your old version of Mozilla, and see if that gets you the same priority boost. 8-). > It's possible that I'm actually seeing the impact of other changes that > have been committed in the last week, I suppose. Jeff's recent sceduler changes have improved performance, in general, for most people who have tried them. It's naieve to change 8 or 9 things, and then attribute something as subjective perceived performance to one of them in particular. 8-) 8-). -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 06:51:15 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DF8737B401 for ; Wed, 2 Apr 2003 06:51:15 -0800 (PST) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id E92BA43F3F for ; Wed, 2 Apr 2003 06:51:13 -0800 (PST) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 4.12) id 190jZs-0000J8-00; Wed, 02 Apr 2003 16:51:00 +0200 Date: Wed, 2 Apr 2003 16:51:00 +0200 From: Sheldon Hearn To: "Michael W . Lucas" Message-ID: <20030402145100.GC790@starjuice.net> Mail-Followup-To: "Michael W . Lucas" , current@FreeBSD.org References: <20030402092055.A31850@blackhelicopters.org> <20030402143055.GB790@starjuice.net> <20030402094334.C31850@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030402094334.C31850@blackhelicopters.org> User-Agent: Mutt/1.5.4i Sender: Sheldon Hearn cc: current@FreeBSD.org Subject: Re: breakage this morning X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 14:51:15 -0000 On (2003/04/02 09:43), Michael W . Lucas wrote: > > You sure you didn't get caught in the middle of a cvsup mirror sync? I > > have an IP_EVIL world and kernel running fine here. > > According to some folks on IRC, it was renamed to "IP_EF" in > src/sys/netinet/ip.h, but not renamed in ping.c. > > I just finished re-supping from cvsup16, and while I got some updates, > an update to ping_c was not among them... Ah, so it's me who got lucky, not you who got unlucky. Sorry. Ciao, Sheldon. From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 06:54:12 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6286A37B401 for ; Wed, 2 Apr 2003 06:54:12 -0800 (PST) Received: from relay.macomnet.ru (relay.macomnet.ru [195.128.64.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCCFC43FB1 for ; Wed, 2 Apr 2003 06:54:10 -0800 (PST) (envelope-from maxim@macomnet.ru) Received: from news1.macomnet.ru (news1.macomnet.ru [195.128.64.14]) by relay.macomnet.ru (8.11.6/8.11.6) with ESMTP id h32ErMp2454990; Wed, 2 Apr 2003 18:53:22 +0400 (MSD) Date: Wed, 2 Apr 2003 18:53:22 +0400 (MSD) From: Maxim Konovalov To: Sheldon Hearn In-Reply-To: <20030402145100.GC790@starjuice.net> Message-ID: <20030402185307.H79922@news1.macomnet.ru> References: <20030402092055.A31850@blackhelicopters.org> <20030402143055.GB790@starjuice.net> <20030402145100.GC790@starjuice.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: breakage this morning X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 14:54:12 -0000 On 16:51+0200, Apr 2, 2003, Sheldon Hearn wrote: > On (2003/04/02 09:43), Michael W . Lucas wrote: > > > > You sure you didn't get caught in the middle of a cvsup mirror sync? I > > > have an IP_EVIL world and kernel running fine here. > > > > According to some folks on IRC, it was renamed to "IP_EF" in > > src/sys/netinet/ip.h, but not renamed in ping.c. > > > > I just finished re-supping from cvsup16, and while I got some updates, > > an update to ping_c was not among them... > > Ah, so it's me who got lucky, not you who got unlucky. fixed. -- Maxim Konovalov, maxim@macomnet.ru, maxim@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 06:57:01 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D99337B401 for ; Wed, 2 Apr 2003 06:57:01 -0800 (PST) Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BAC843F3F for ; Wed, 2 Apr 2003 06:56:58 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: from blackhelicopters.org (mwlucas@localhost [127.0.0.1]) by blackhelicopters.org (8.12.8/8.12.8) with ESMTP id h32EuvDn032372; Wed, 2 Apr 2003 09:56:57 -0500 (EST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.12.8/8.12.8/Submit) id h32Euv9V032371; Wed, 2 Apr 2003 09:56:57 -0500 (EST) Date: Wed, 2 Apr 2003 09:56:57 -0500 From: "Michael W . Lucas" To: Maxim Konovalov Message-ID: <20030402095657.A32353@blackhelicopters.org> References: <20030402092055.A31850@blackhelicopters.org> <20030402143055.GB790@starjuice.net> <20030402094334.C31850@blackhelicopters.org> <20030402145100.GC790@starjuice.net> <20030402185307.H79922@news1.macomnet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030402185307.H79922@news1.macomnet.ru>; from maxim@macomnet.ru on Wed, Apr 02, 2003 at 06:53:22PM +0400 cc: current@freebsd.org Subject: Re: breakage this morning X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 14:57:01 -0000 On Wed, Apr 02, 2003 at 06:53:22PM +0400, Maxim Konovalov wrote: > On 16:51+0200, Apr 2, 2003, Sheldon Hearn wrote: > > > On (2003/04/02 09:43), Michael W . Lucas wrote: > > > > > > You sure you didn't get caught in the middle of a cvsup mirror sync? I > > > > have an IP_EVIL world and kernel running fine here. > > > > > > According to some folks on IRC, it was renamed to "IP_EF" in > > > src/sys/netinet/ip.h, but not renamed in ping.c. > > > > > > I just finished re-supping from cvsup16, and while I got some updates, > > > an update to ping_c was not among them... > > > > Ah, so it's me who got lucky, not you who got unlucky. > > fixed. Thank you very much! ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org http://www.BlackHelicopters.org/~mwlucas/ Absolute BSD: http://www.AbsoluteBSD.com/ From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 07:00:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9AD537B401 for ; Wed, 2 Apr 2003 07:00:38 -0800 (PST) Received: from dsl093-019-250.msp1.dsl.speakeasy.net (dsl093-019-250.msp1.dsl.speakeasy.net [66.93.19.250]) by mx1.FreeBSD.org (Postfix) with SMTP id DBE6443F75 for ; Wed, 2 Apr 2003 07:00:37 -0800 (PST) (envelope-from peter@jocose.org) Received: (qmail 54256 invoked from network); 2 Apr 2003 15:00:37 -0000 Received: from unknown (HELO jocose.org) (10.0.0.198) by 0 with SMTP; 2 Apr 2003 15:00:37 -0000 Message-ID: <3E8AFB2F.3040701@jocose.org> Date: Wed, 02 Apr 2003 09:01:03 -0600 From: Peter Schultz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030226 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Terry Lambert References: <3E8AED1B.10606@jocose.org> <3E8AEFBF.D1D640E3@mindspring.com> In-Reply-To: <3E8AEFBF.D1D640E3@mindspring.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 15:00:39 -0000 Terry Lambert wrote: > Peter Schultz wrote: > >>Hi, >> >>I hope that core will approve removing sendmail from FreeBSD-CURRENT. > > > I'm pretty sure they will, just as soon as someone provides > patches to make installed base system components like sendmail > into "preinstalled packages", and then steps up and makes some > other MTA and MSA able to be installed by default instead, so > that things like "/etc/daily", "/etc/weekly", and so on can > still send an email to the local "root" user upon completion. > Why not just have these logged by default instead? Like /var/log/daily, and whatnot. Anyone with half a care about this stuff can easily make their own modifications, those who don't care will never know the difference. On a simple installation where the user is careless, these e-mails are spamming roots mailbox. Imagine the hundreds if not thousands of ignored messages. > PS: This comes up every time a sendmail CERT advisory happens, > but then no one provides the necessary patches to make email > continue to work with sendmail deinstalled, or the package > files to allow it to be deinstalled and replaces easily. > I'm sorry for beating a dead horse. A guy and I from tcbug were just trying to fix his postfix installation, he does not know what happened, it just stopped working. There would not have been a problem if sendmail wasn't tied into the system so closely. I'm just hoping core will say, "submit a working solution and it will be done," so that there's a little inspiration here. Pete... From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 07:07:00 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C29137B401 for ; Wed, 2 Apr 2003 07:07:00 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 872FB43F85 for ; Wed, 2 Apr 2003 07:06:59 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.8/8.12.8) with ESMTP id h32F6eSM083488; Wed, 2 Apr 2003 17:06:46 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: Peter Schultz From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 02 Apr 2003 09:01:03 MDT." <3E8AFB2F.3040701@jocose.org> Date: Wed, 02 Apr 2003 17:06:40 +0200 Message-ID: <83487.1049296000@critter.freebsd.dk> cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 15:07:00 -0000 In message <3E8AFB2F.3040701@jocose.org>, Peter Schultz writes: >I'm sorry for beating a dead horse. This is the best summary so far on this subject. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 07:31:51 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C529C37B401 for ; Wed, 2 Apr 2003 07:31:51 -0800 (PST) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4806D43FB1 for ; Wed, 2 Apr 2003 07:31:51 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0051.cvx21-bradley.dialup.earthlink.net ([209.179.192.51] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190kDN-0001ZQ-00; Wed, 02 Apr 2003 07:31:50 -0800 Message-ID: <3E8B01F2.B3E02FC8@mindspring.com> Date: Wed, 02 Apr 2003 07:29:54 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Schultz References: <3E8AED1B.10606@jocose.org> <3E8AEFBF.D1D640E3@mindspring.com> <3E8AFB2F.3040701@jocose.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4815ed0c6e37358739ba83da35aa9f7ec350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 15:31:52 -0000 Peter Schultz wrote: > Why not just have these logged by default instead? Like /var/log/daily, > and whatnot. Anyone with half a care about this stuff can easily make > their own modifications, those who don't care will never know the > difference. Because syslog is unreliable. See "BUGS" section of the man page. > I'm sorry for beating a dead horse. That's OK; it happens every CERT advisory, and every time someone dails to install Postfix or whatever. > I'm just hoping core > will say, "submit a working solution and it will be done," so that > there's a little inspiration here. Not likely; that's not really the function of "core". They aren't the architectural board, or the people concerned with the installer, they are a governing body and a court of last appeal. If you look over the historical cases of this discussion, you'll see that the answer always comes down to "make the system more modular, so people can replace XXX with YYY and quit bothering us; please send patches". 8-) 8-). -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 07:40:21 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8122937B401; Wed, 2 Apr 2003 07:40:21 -0800 (PST) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE73F43FD7; Wed, 2 Apr 2003 07:40:18 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0051.cvx21-bradley.dialup.earthlink.net ([209.179.192.51] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190kLY-0002l4-00; Wed, 02 Apr 2003 07:40:18 -0800 Message-ID: <3E8B03E6.36871704@mindspring.com> Date: Wed, 02 Apr 2003 07:38:14 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Robert Watson References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a488150adf550016d05c72c5c5a17c2e503ca473d225a0f487350badd9bab72f9c350badd9bab72f9c cc: Alexander Leidinger cc: csujun@21cn.com cc: current@freebsd.org cc: Jeff Roberson Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 15:40:21 -0000 Robert Watson wrote: > You should notice marked interactivity and UI latency improvements with > threaded GUI apps over libc_r because GUI threads will generally no longer > be blocked when disk I/O and blocking I/O occurs. For example, > applications like Open Office, Netscape, et al, really get a lot better > with 1:1. Likewise, non-interactive applications that are disk > I/O-intensive, such as mysql, will also perform substantially better > because a thread that hits blocking using an interface that doesn't > support non-blocking I/O (such as the file system) won't clog up the > application. Is the disk I/O really that big of an issue? All writes will be on underlying non-blocking descriptors; I guess you are saying that the interleaved I/O is more important, further down the system call interface than the top, and this becomes an issue? It seems to me that maybe the correct fix for this is to use AIO instead of non-blocking I/O, then? The GUI thread issues are something I hadn't considered; I don't generally think of user space CPU intensive operations like that, but I guess it has to be rendered some time. 8-). Has anyone tried compiling X11 to use libthr? Also, any ETA on the per process signal mask handing bug in libthr? Might not be safe to convert everything up front, in a rush of eager enthusiasm... -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 07:47:29 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C4BE37B401; Wed, 2 Apr 2003 07:47:29 -0800 (PST) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1FF743FCB; Wed, 2 Apr 2003 07:47:26 -0800 (PST) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 4.12) id 190kSK-0000QF-00; Wed, 02 Apr 2003 17:47:16 +0200 Date: Wed, 2 Apr 2003 17:47:16 +0200 From: Sheldon Hearn To: Terry Lambert Message-ID: <20030402154716.GE790@starjuice.net> Mail-Followup-To: Terry Lambert , Robert Watson , Alexander Leidinger , csujun@21cn.com, current@freebsd.org, Jeff Roberson References: <3E8B03E6.36871704@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E8B03E6.36871704@mindspring.com> User-Agent: Mutt/1.5.4i Sender: Sheldon Hearn cc: Alexander Leidinger cc: csujun@21cn.com cc: Robert Watson cc: current@freebsd.org cc: Jeff Roberson Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 15:47:29 -0000 On (2003/04/02 07:38), Terry Lambert wrote: > Is the disk I/O really that big of an issue? All writes will > be on underlying non-blocking descriptors; I guess you are > saying that the interleaved I/O is more important, further > down the system call interface than the top, and this becomes > an issue? Dude, you should really try this stuff for yourself before naysaying performance improvements on principle. It's actually quite impressive for desktop users (at least). Ciao, Sheldon. From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 07:49:39 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8854A37B401 for ; Wed, 2 Apr 2003 07:49:39 -0800 (PST) Received: from MAILSERVER.ofw.fi (ns.ofw.fi [194.111.144.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6C4C43FB1 for ; Wed, 2 Apr 2003 07:49:38 -0800 (PST) (envelope-from dan.naumov@ofw.fi) Received: from [172.16.161.81] by MAILSERVER.ofw.fi (NTMail 7.00.0022/NT1439.00.90501b21) with ESMTP id uqaejaaa for freebsd-current@freebsd.org; Wed, 2 Apr 2003 18:48:48 +0300 Date: Wed, 2 Apr 2003 18:53:11 +0300 From: Dan Naumov To: freebsd-current@freebsd.org Message-Id: <20030402185311.599cb0d3.dan.naumov@ofw.fi> X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 15:49:39 -0000 Terry Lambert wrote: > Because syslog is unreliable. See "BUGS" section of the man page. Don't you think that if syslog is unreliable, then it should be fixed ? If things are as you say, we have 2 problems: Sendmail gettings CERTs every other day and an unreliable system logger. Would you rather just let things be as they are ? Sincerely, -- Dan Naumov From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 07:54:56 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8189F37B401 for ; Wed, 2 Apr 2003 07:54:56 -0800 (PST) Received: from mail.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3DB643FA3 for ; Wed, 2 Apr 2003 07:54:55 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 3926 invoked from network); 2 Apr 2003 15:54:58 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 2 Apr 2003 15:54:58 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.8/8.12.8) with ESMTP id h32FsrOv022979; Wed, 2 Apr 2003 10:54:53 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3E8AFB2F.3040701@jocose.org> Date: Wed, 02 Apr 2003 10:54:54 -0500 (EST) From: John Baldwin To: Peter Schultz cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 15:54:56 -0000 On 02-Apr-2003 Peter Schultz wrote: > I'm sorry for beating a dead horse. A guy and I from tcbug were just > trying to fix his postfix installation, he does not know what happened, > it just stopped working. There would not have been a problem if > sendmail wasn't tied into the system so closely. I'm just hoping core > will say, "submit a working solution and it will be done," so that > there's a little inspiration here. > > Pete... First, core@ is not the appropriate body for that type of request. Both current@ and arch@ are much better targets. Second, is NO_SENDMAIL + the postfix port inadequate? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 07:56:40 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E529937B401 for ; Wed, 2 Apr 2003 07:56:40 -0800 (PST) Received: from calis.blacksun.org (calis.blacksun.org [216.254.108.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68E9243F85 for ; Wed, 2 Apr 2003 07:56:40 -0800 (PST) (envelope-from don@calis.blacksun.org) Received: by calis.blacksun.org (Postfix, from userid 1001) id 954A617058; Wed, 2 Apr 2003 10:59:44 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by calis.blacksun.org (Postfix) with ESMTP id 938A717054; Wed, 2 Apr 2003 10:59:44 -0500 (EST) Date: Wed, 2 Apr 2003 10:59:44 -0500 (EST) From: Don To: Dan Naumov In-Reply-To: <20030402185311.599cb0d3.dan.naumov@ofw.fi> Message-ID: <20030402105556.Y98713@calis.blacksun.org> References: <20030402185311.599cb0d3.dan.naumov@ofw.fi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 15:56:41 -0000 > Don't you think that if syslog is unreliable, then it should be fixed ? > If things are as you say, we have 2 problems: Sendmail gettings CERTs > every other day and an unreliable system logger. Would you rather just > let things be as they are ? Absolutely not! Fix the problems and they would be happy to commit your fixes. Seriously though, I _always_ replace sendmail with postfix and I have never had a problem doing so. Other than one or two really trivial anyway. What problems do people run into when replacing sendmail? How many of those problems come as a result of not reading the install messages for the particular port? -Don From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 08:01:00 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C218537B401 for ; Wed, 2 Apr 2003 08:01:00 -0800 (PST) Received: from dsl093-019-250.msp1.dsl.speakeasy.net (dsl093-019-250.msp1.dsl.speakeasy.net [66.93.19.250]) by mx1.FreeBSD.org (Postfix) with SMTP id 9090643FDF for ; Wed, 2 Apr 2003 08:00:59 -0800 (PST) (envelope-from peter@jocose.org) Received: (qmail 54366 invoked from network); 2 Apr 2003 16:00:58 -0000 Received: from unknown (HELO jocose.org) (10.0.0.198) by 0 with SMTP; 2 Apr 2003 16:00:58 -0000 Message-ID: <3E8B0954.3030905@jocose.org> Date: Wed, 02 Apr 2003 10:01:24 -0600 From: Peter Schultz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030226 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Schultz References: <20030331153829.636FE4F2EB@smtp.us2.messagingengine.com> <20030331235443.GB32627@HAL9000.homeunix.com> In-Reply-To: <20030331235443.GB32627@HAL9000.homeunix.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Thanjee Neefam cc: freebsd-current@FreeBSD.ORG Subject: Re: MIDI X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 16:01:01 -0000 X-List-Received-Date: Wed, 02 Apr 2003 16:01:01 -0000 David Schultz wrote: > Thus spake Thanjee Neefam : > >>I was very happy when compiling my 5.0 kernel. For the first time "device >>midi" compiled without giving any errors. This abnormal excitement only >>led to misery when I discovered after rebooting that there still was no >>MIDI. >>Is MIDI going to be implemented soon? Who is working on it? Can I help >>them? (I am not a very good programmer, but I can hack pre existing code, >>and I am good at testing). MIDI is the ONLY thing stopping me from >>running FreeBSD exclusively. > > > FYI, the non-free OSS driver supports MIDI: > > http://www.opensound.com/bsd.html Apparently even this is not complete, however: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1250661+0+archive/2003/freebsd-current/20030323.freebsd-current One interesting thing to note from that thread, is that Yuriy Tsibizov is into the development of this stuff, but does not have all the equipment needed to conduct testing. I don't know what hardware you have, but this is what he's been working on: http://chibis.persons.gfk.ru/audigy/ Pete... From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 08:01:12 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 836BE37B405 for ; Wed, 2 Apr 2003 08:01:12 -0800 (PST) Received: from mail.liwing.de (mail.liwing.de [213.70.188.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88EDD43F75 for ; Wed, 2 Apr 2003 08:01:07 -0800 (PST) (envelope-from rehsack@liwing.de) Received: (qmail 72602 invoked from network); 2 Apr 2003 16:01:01 -0000 Received: from stingray.liwing.de (HELO liwing.de) ([213.70.188.164]) (envelope-sender ) by mail.liwing.de (qmail-ldap-1.03) with SMTP for ; 2 Apr 2003 16:01:01 -0000 Message-ID: <3E8B093D.4010500@liwing.de> Date: Wed, 02 Apr 2003 18:01:01 +0200 From: Jens Rehsack Organization: LiWing IT-Services User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 16:01:12 -0000 John Baldwin wrote: > On 02-Apr-2003 Peter Schultz wrote: > >>I'm sorry for beating a dead horse. A guy and I from tcbug were just >>trying to fix his postfix installation, he does not know what happened, >>it just stopped working. There would not have been a problem if >>sendmail wasn't tied into the system so closely. I'm just hoping core >>will say, "submit a working solution and it will be done," so that >>there's a little inspiration here. >> >>Pete... > > > First, core@ is not the appropriate body for that type of request. > Both current@ and arch@ are much better targets. Second, is > NO_SENDMAIL + the postfix port inadequate? > The problem I see with that is, that even a minimalistic base install installs things like sendmail, ppp, atm-stuff, g77 and so on. I really think splitting the base in some sub-parts would it make much easier to do NO_SENDMAIL on my own. So I had to remove each not required file separately. That's no good solution. Regards, Jens From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 08:03:43 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B36B037B401 for ; Wed, 2 Apr 2003 08:03:43 -0800 (PST) Received: from seed.net.tw (sn12.seed.net.tw [139.175.54.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B83943F75 for ; Wed, 2 Apr 2003 08:03:42 -0800 (PST) (envelope-from leafy@leafy.idv.tw) Received: from [211.74.130.123] (port=49190 helo=leafy.idv.tw) by seed.net.tw with esmtp (Seednet 4.10:3) id 190kiD-000IfB-00 for freebsd-current@freebsd.org; Thu, 03 Apr 2003 00:03:41 +0800 Received: from leafy.idv.tw (nobody@localhost [127.0.0.1]) by leafy.idv.tw (8.12.9/8.12.9) with ESMTP id h32G3fcT099000 for ; Thu, 3 Apr 2003 00:03:41 +0800 (CST) (envelope-from leafy@leafy.idv.tw) Received: (from leafy@localhost) by leafy.idv.tw (8.12.9/8.12.9/Submit) id h32G3eRu098999 for freebsd-current@freebsd.org; Thu, 3 Apr 2003 00:03:41 +0800 (CST) (envelope-from leafy) Date: Thu, 3 Apr 2003 00:03:40 +0800 From: leafy To: freebsd-current@freebsd.org Message-ID: <20030402160340.GA98978@leafy.idv.tw> Mail-Followup-To: freebsd-current@freebsd.org References: <3E8B03E6.36871704@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Disposition: inline In-Reply-To: <3E8B03E6.36871704@mindspring.com> User-Agent: Mutt/1.5.4i Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 16:03:44 -0000 On Wed, Apr 02, 2003 at 07:38:14AM -0800, Terry Lambert wrote: > Has anyone tried compiling X11 to use libthr? Someone reported success with KDE, so it should serve as a sign of working X11. Jiawei -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 08:10:40 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A238937B401; Wed, 2 Apr 2003 08:10:40 -0800 (PST) Received: from ns.gfk.ru (ns.gfk.ru [62.205.179.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DD5D43FDD; Wed, 2 Apr 2003 08:10:27 -0800 (PST) (envelope-from Yuriy.Tsibizov@gfk.ru) Received: from mx.gfk.ru ([10.0.0.30]) by ns.gfk.ru ([62.205.179.194]) with SMTP (MDaemon.PRO.v6.5.2.R); Wed, 02 Apr 2003 20:08:52 +0400 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Wed, 2 Apr 2003 20:08:50 +0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MIDI Thread-Index: AcL5MW1oexsqM3UtQH+voj3dp31VKAAABNuw From: "Yuriy Tsibizov" To: "Peter Schultz" , "David Schultz" X-MDRemoteIP: 10.0.0.30 X-Return-Path: Yuriy.Tsibizov@gfk.ru cc: Thanjee Neefam cc: freebsd-current@FreeBSD.ORG Subject: RE: MIDI X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 16:10:40 -0000 X-List-Received-Date: Wed, 02 Apr 2003 16:10:40 -0000 > From: Peter Schultz [mailto:peter@jocose.org] >=20 >One interesting thing to note from that thread, is that Yuriy Tsibizov=20 >is into the development of this stuff, but does not have all the=20 >equipment needed to conduct testing. I don't know what hardware you=20 >have, but this is what he's been working on: >http://chibis.persons.gfk.ru/audigy/ No! I'm not a MIDI subsystem developer! The only thing I do is an = attempt to add MIDI I/O to Live/Audigy cards. If MIDI subsystem is not = compllete I'll stop this work. I'm going to do only card-specific = drivers, not to fix possible broken in-kernel MIDI. Yuriy From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 08:10:44 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87E0837B401 for ; Wed, 2 Apr 2003 08:10:44 -0800 (PST) Received: from dsl093-019-250.msp1.dsl.speakeasy.net (dsl093-019-250.msp1.dsl.speakeasy.net [66.93.19.250]) by mx1.FreeBSD.org (Postfix) with SMTP id A3A4A43FAF for ; Wed, 2 Apr 2003 08:10:43 -0800 (PST) (envelope-from peter@jocose.org) Received: (qmail 54409 invoked from network); 2 Apr 2003 16:10:43 -0000 Received: from unknown (HELO jocose.org) (10.0.0.198) by 0 with SMTP; 2 Apr 2003 16:10:43 -0000 Message-ID: <3E8B0B9D.6010300@jocose.org> Date: Wed, 02 Apr 2003 10:11:09 -0600 From: Peter Schultz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030226 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Terry Lambert References: <3E8AED1B.10606@jocose.org> <3E8AEFBF.D1D640E3@mindspring.com> <3E8AFB2F.3040701@jocose.org> <3E8B01F2.B3E02FC8@mindspring.com> In-Reply-To: <3E8B01F2.B3E02FC8@mindspring.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 16:10:44 -0000 Terry Lambert wrote: > If you look over the historical cases of this discussion, > you'll see that the answer always comes down to "make the > system more modular, so people can replace XXX with YYY and > quit bothering us; please send patches". 8-) 8-). > Thanks for your help on this. I've been getting so many search results that I've been unable to determine the exact problem myself. So, one absolute requirement is that the system have both an mta, and an msa. When you say msa, does this include pop&imap capabilities? Pete... From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 08:19:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 267F137B401 for ; Wed, 2 Apr 2003 08:19:38 -0800 (PST) Received: from hotmail.com (f132.pav1.hotmail.com [64.4.31.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8DDF43F93 for ; Wed, 2 Apr 2003 08:19:37 -0800 (PST) (envelope-from evantd@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 2 Apr 2003 08:19:36 -0800 Received: from 128.208.59.99 by pv1fd.pav1.hotmail.msn.com with HTTP; Wed, 02 Apr 2003 16:19:36 GMT X-Originating-IP: [128.208.59.99] X-Originating-Email: [evantd@hotmail.com] From: "Evan Dower" To: freebsd-current@freebsd.org Date: Wed, 02 Apr 2003 08:19:36 -0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 02 Apr 2003 16:19:36.0941 (UTC) FILETIME=[A78BF1D0:01C2F933] Subject: sendmail: no local mailer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 16:19:38 -0000 Sendmail has not been working on my system for some time now. I can't say exactly how long, but my guess is that it broke when I upgraded to RELENG_5_0. This is how sendmail is invoked (by default) and it's output. # sendmail -L sm-mta -bd -q30m -ODaemonPortOptions=Addr=localhost 451 4.0.0 No local mailer defined: Bad address 554 5.0.0 QueueDirectory (Q) option must be set The same thing happens if I change "localhost" to "127.0.0.1". I suspect that the second error (554) will disappear when I get rid of the first one (451). Does anyone know why it might be misbehaving like this? Thanks, Evan Dower P.S.: relevent info to follow: # uname -a FreeBSD lojak.washington.edu 5.0-RELEASE-p6 FreeBSD 5.0-RELEASE-p6 #0: Wed Mar 26 10:29:59 PST 2003 evantd@lojak.washington.edu:/usr/obj/usr/src/sys/CUSTOM i386 _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 08:26:22 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D675F37B401 for ; Wed, 2 Apr 2003 08:26:22 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B440443FCB for ; Wed, 2 Apr 2003 08:26:21 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.9/8.12.9) with SMTP id h32GQXYY035742; Wed, 2 Apr 2003 11:26:33 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 2 Apr 2003 11:26:32 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Terry Lambert In-Reply-To: <3E8B03E6.36871704@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Alexander Leidinger cc: csujun@21cn.com cc: current@freebsd.org cc: Jeff Roberson Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 16:26:23 -0000 On Wed, 2 Apr 2003, Terry Lambert wrote: > Is the disk I/O really that big of an issue? All writes will be on > underlying non-blocking descriptors; I guess you are saying that the > interleaved I/O is more important, further down the system call > interface than the top, and this becomes an issue? The I/O issue is a big deal for things like mysql, yes. > It seems to me that maybe the correct fix for this is to use AIO instead > of non-blocking I/O, then? Well, they're both fixes. Another issue for applications that are threaded and may be bumping up against the system memory limits is whether or not the whole process stalls on a page fault or memory mapping fault, or whether it's just the thread. If you have an application that is accessing a large memory mapped file, there may be some long kernel sleeps as you pull in the pages. Certainly, you can argue that the application should be structured to make all I/O explicit and asynchronous, but for various reasons, that's not the case :-). Our VM and VFS subsystems may have limited concurrency from an SMPng perspective, but probably have enough that a marked benefit should be seen there too (you might have to wait for another thread to block in the subsystem, but that will be a short period of time compared to how long it takes to service the page from disk). > The GUI thread issues are something I hadn't considered; I don't > generally think of user space CPU intensive operations like that, but I > guess it has to be rendered some time. 8-). One of the problems I've run into is where you lose interactivity during file saves and other disk-intensive operations in OpenOffice. Other windows could in theory still be processing UI events, such as menu clicks, etc, but since you're dumping several megabytes of data to disk or doing interactive file operations that require waiting on disk latency, you end up with a fairly nasty user experience. One way to explore this effect is to do a side-by-side comparison of the behavior of OpenOffice and Mozilla linked against libc_r and linuxthreads. I haven't actually instrumented the kernel, but it might be quite interesting to do so--attempt to estimate the total impact of disk stalls on libc_r. From a purely qualitivative perspective, there is quite a noticeable difference. > Has anyone tried compiling X11 to use libthr? Not sure. > Also, any ETA on the per process signal mask handing bug in libthr? > Might not be safe to convert everything up front, in a rush of eager > enthusiasm... Can't speculate on that, except one thing that is useful to note is that many serious threaded applications are already being linked against linuxthreads on FreeBSD, which arguably has poorer semantics when it comes to signals, credentials, etc, than libthr already :-). For example, most sites I've talked to that deploy mysql do it with linuxthreads rather than libc_r to avoid the I/O issues, as well as avoid deadlocks. There are enough bits of the kernel (for example, POSIX fifos) that don't handle non-blocking operation that libc_r can stall or get into I/O buffer deadlocks. I seem to recall someone mentioning (but can't confirm easily) that Netscape at one point relied on using pipes to handle some sorts of asynchronous events and wakeups within the same process. If that pipe filled, the process would block on a pipe write for a pipe that would never drain. I can think of a couple of other interesting excercises to explore the problem -- implementing AIO "better" using the KSE primitives mixed between userspace and kernel, reimplementing libc_r to attempt to use AIO rather than a select loop where possible, etc. It might be quite interesting to see whether (for a bounded number of threads, due to our AIO implementation), a libc_r that used AIO rather than select demonstrated some of the performance improvements we see with 1:1 via linuxthreads (and now libthr). I'm not sure if there are any open source tools available to easily track process and thread scheduling and blocking, but there have been several pretty useful visual analysis and tracing tools for realtime. Some basic tools for thread tracing and visualization exist for Mac OS X, and presumably other COTS platforms. ktrace on FreeBSD makes some attempt to track context switches, but without enough context (har har) to be useful for this kind of analysis. I've been thinking about tweaking the local scheduler to put a bit more information into ktr and alq about blocking circumstances as well as some way to constrain the tracing to a particular bit of the process hierarchy with an inheritance flag of some sort. It might be quite helpful for understanding some of the nasty threading blocking/timing issues that we already run into with libc_r, and will continue to run into as our threading evolves. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 08:34:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75E8437B401; Wed, 2 Apr 2003 08:34:07 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7513A43F85; Wed, 2 Apr 2003 08:34:06 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.8/8.12.8) with ESMTP id h32GXxSM099029; Wed, 2 Apr 2003 18:34:04 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: Jens Rehsack From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 02 Apr 2003 18:01:01 +0200." <3E8B093D.4010500@liwing.de> Date: Wed, 02 Apr 2003 18:33:59 +0200 Message-ID: <99028.1049301239@critter.freebsd.dk> cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 16:34:07 -0000 In message <3E8B093D.4010500@liwing.de>, Jens Rehsack writes: >The problem I see with that is, that even a minimalistic base install >installs things like sendmail, ppp, atm-stuff, g77 and so on. > >I really think splitting the base in some sub-parts would it make much >easier to do NO_SENDMAIL on my own. So I had to remove each not required >file separately. That's no good solution. The trick is to split along some unambigous subsystem lines and to have only one layer with no dependencies. For instance, you can separate out things like ATM and ISDN4BSD, but not NetGraph (because both of the above depends on it) and so on. The main stumblingblock is the shortage of brave souls willing to venture into make release and sysinstall. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 08:37:14 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A062737B404 for ; Wed, 2 Apr 2003 08:37:14 -0800 (PST) Received: from horsey.gshapiro.net (horsey.gshapiro.net [64.105.95.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D5A343F3F for ; Wed, 2 Apr 2003 08:37:14 -0800 (PST) (envelope-from gshapiro@gshapiro.net) Received: from horsey.gshapiro.net (localhost [127.0.0.1]) id h32GbD5k025227 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Apr 2003 08:37:13 -0800 (PST) Received: (from gshapiro@localhost)h32GbDUx025224; Wed, 2 Apr 2003 08:37:13 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16011.4537.279737.406477@horsey.gshapiro.net> Date: Wed, 2 Apr 2003 08:37:13 -0800 From: Gregory Neil Shapiro To: "Evan Dower" In-Reply-To: References: X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid cc: freebsd-current@freebsd.org Subject: Re: sendmail: no local mailer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 16:37:14 -0000 evantd> Sendmail has not been working on my system for some time now. I evantd> can't say exactly how long, but my guess is that it broke when I evantd> upgraded to RELENG_5_0. This is how sendmail is invoked (by evantd> default) and it's output. evantd> # sendmail -L sm-mta -bd -q30m -ODaemonPortOptions=Addr=localhost evantd> 451 4.0.0 No local mailer defined: Bad address evantd> 554 5.0.0 QueueDirectory (Q) option must be set /etc/mail/sendmail.cf is a bogus (empty?) file. One way to fix this is: cd /etc/mail mv sendmail.cf sendmail.cf~bogus make make restart From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 08:41:53 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id 4D40D37B401; Wed, 2 Apr 2003 08:41:53 -0800 (PST) Date: Wed, 2 Apr 2003 10:41:53 -0600 From: Juli Mallett To: Bruce Evans Message-ID: <20030402104153.A76332@FreeBSD.org> References: <20030329190908R.matusita@jp.FreeBSD.org> <3E857E9C.F7476A32@mindspring.com><20030331150348.GD21700@sunbay.com> <20030402151519.U25349@gamplex.bde.org> <20030402104439.GA26900@sunbay.com> <20030402215049.G26531@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030402215049.G26531@gamplex.bde.org>; from bde@zeta.org.au on Wed, Apr 02, 2003 at 10:07:28PM +1000 Organisation: The FreeBSD Project X-Alternate-Addresses: , , , , X-Towel: Yes X-Negacore: Yes X-Title: Code Maven X-Authentication-Warning: localhost: juli pwned teh intarweb cc: Makoto Matsushita cc: current@freebsd.org Subject: Re: FreeBSD/alpha kern.flp flood X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 16:41:53 -0000 * De: Bruce Evans [ Data: 2003-04-02 ] [ Subjecte: Re: FreeBSD/alpha kern.flp flood ] > > I'd hardly call it a bug, since style(9) explicitly says C files > > should use __FBSDID(). > > Another bug. __FBSDID() is is not normally used in the kernel. E.g., > rev.1.1 of almost every file in libkern is about removing (sccs) id > strings since their bloat is not wanted in the kernel. It is true > that __FBSDID() and suitable stripping can handle this more configurably, > but no one ever cared enough to change n,000 $FreeBSD$'s to __FBSDID()'s > in the kernel (ugh) or provide infrastructure (#define lint doesn't count) > for stripping the ids. #define STRIP_FBSDID does, however, count I think. It would work just fine in opt_global.h, too, if someone threw the necessary options bit in, and then users could decide, as well as strip(1)ers. -- juli mallett. email: jmallett@freebsd.org; aim: bsdflata; efnet: juli; From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 08:59:01 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8CA837B401 for ; Wed, 2 Apr 2003 08:59:01 -0800 (PST) Received: from dsl093-019-250.msp1.dsl.speakeasy.net (dsl093-019-250.msp1.dsl.speakeasy.net [66.93.19.250]) by mx1.FreeBSD.org (Postfix) with SMTP id 8730343F93 for ; Wed, 2 Apr 2003 08:59:00 -0800 (PST) (envelope-from peter@jocose.org) Received: (qmail 54530 invoked from network); 2 Apr 2003 16:59:00 -0000 Received: from unknown (HELO jocose.org) (10.0.0.198) by 0 with SMTP; 2 Apr 2003 16:59:00 -0000 Message-ID: <3E8B16ED.1090300@jocose.org> Date: Wed, 02 Apr 2003 10:59:25 -0600 From: Peter Schultz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030226 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 16:59:02 -0000 John Baldwin wrote: > On 02-Apr-2003 Peter Schultz wrote: > >>I'm sorry for beating a dead horse. A guy and I from tcbug were just >>trying to fix his postfix installation, he does not know what happened, >>it just stopped working. There would not have been a problem if >>sendmail wasn't tied into the system so closely. I'm just hoping core >>will say, "submit a working solution and it will be done," so that >>there's a little inspiration here. >> >>Pete... > > > First, core@ is not the appropriate body for that type of request. > Both current@ and arch@ are much better targets. I understand, thanks for clarifying. > Second, is NO_SENDMAIL + the postfix port inadequate? > I guess. I was helping him on #tcbug this morning, and he certainly missed something somewhere between the two. He claimed it "just stopped working." I don't know what all he did, but he was sure going crazy trying to fix it. I helped him get around the problem, but I couldn't help but think it would be nice for FreeBSD administrators to have a smoother solution. How about requiring a decision at install time, during the final configuration: [x] sendmail ... (default) [ ] postfix ... [ ] exim ... [ ] qmail ... [ ] none (caution: desktop users only, insecure use of syslog) Pete... From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 09:07:24 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D405437B404; Wed, 2 Apr 2003 09:07:24 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56F4843F85; Wed, 2 Apr 2003 09:07:23 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.9/8.12.7) with ESMTP id h32H78D0059386; Wed, 2 Apr 2003 09:07:12 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h32H6xdP059379; Wed, 2 Apr 2003 09:06:59 -0800 (PST) Date: Wed, 2 Apr 2003 09:06:59 -0800 From: "David O'Brien" To: Ruslan Ermilov Message-ID: <20030402170659.GA59231@dragon.nuxi.com> Mail-Followup-To: David O'Brien , Ruslan Ermilov , Bruce Evans , Makoto Matsushita , current@freebsd.org References: <20030329190908R.matusita@jp.FreeBSD.org> <3E857E9C.F7476A32@mindspring.com> <20030329203005.GB94956@sunbay.com> <20030331150348.GD21700@sunbay.com> <20030401194712.GA10151@dragon.nuxi.com> <20030402151519.U25349@gamplex.bde.org> <20030402104439.GA26900@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030402104439.GA26900@sunbay.com> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: Makoto Matsushita cc: current@freebsd.org Subject: Re: FreeBSD/alpha kern.flp flood X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 17:07:25 -0000 On Wed, Apr 02, 2003 at 01:44:39PM +0300, Ruslan Ermilov wrote: > > Most of the savings from stripping commits is from removing verbose compiler > > id "GCC: (GNU) 3.2.1 [FreeBSD] 20021119 (release)". ... > David, can we get rid of the .comment section for the normal > builds too, or at least not put these long GCC strings into? "GCC: (GNU) 3.2.1" is the version string that the FSF STRONGLY wants to remain. They also strongly push us to add to that string so it is clear this compiler is a derivative. Bug reports are also useless with "3.2.1" and "20021119". From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 09:09:15 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9B5237B401 for ; Wed, 2 Apr 2003 09:09:15 -0800 (PST) Received: from MAILSERVER.ofw.fi (ns.ofw.fi [194.111.144.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD63343FBD for ; Wed, 2 Apr 2003 09:09:14 -0800 (PST) (envelope-from dan.naumov@ofw.fi) Received: from [172.16.161.81] by MAILSERVER.ofw.fi (NTMail 7.00.0022/NT1439.00.90501b21) with ESMTP id juaejaaa for freebsd-current@freebsd.org; Wed, 2 Apr 2003 20:08:24 +0300 Date: Wed, 2 Apr 2003 20:12:47 +0300 From: Dan Naumov To: freebsd-current@freebsd.org Message-Id: <20030402201247.340f4cc1.dan.naumov@ofw.fi> In-Reply-To: <3E8B16ED.1090300@jocose.org> References: <3E8B16ED.1090300@jocose.org> X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 17:09:16 -0000 On Wed, 02 Apr 2003 10:59:25 -0600 Peter Schultz wrote: > [x] sendmail ... (default) > [ ] postfix ... > [ ] exim ... > [ ] qmail ... > [ ] none (caution: desktop users only, insecure use of syslog) AFAIK, "sendmail", "postfix" and "none" are the options presented to the user during the installation of a NetBSD system. I think it's a good idea. Sincerely, -- Dan Naumov From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 09:14:05 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCA9337B401; Wed, 2 Apr 2003 09:14:05 -0800 (PST) Received: from hotmail.com (f69.pav1.hotmail.com [64.4.31.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 305BA43F3F; Wed, 2 Apr 2003 09:14:05 -0800 (PST) (envelope-from evantd@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 2 Apr 2003 09:14:04 -0800 Received: from 128.208.59.99 by pv1fd.pav1.hotmail.msn.com with HTTP; Wed, 02 Apr 2003 17:14:04 GMT X-Originating-IP: [128.208.59.99] X-Originating-Email: [evantd@hotmail.com] From: "Evan Dower" To: gshapiro@freebsd.org Date: Wed, 02 Apr 2003 09:14:04 -0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 02 Apr 2003 17:14:04.0613 (UTC) FILETIME=[433B1F50:01C2F93B] cc: freebsd-current@freebsd.org Subject: Re: sendmail: no local mailer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 17:14:06 -0000 Hurray! With the addition of a make install, that worked wonderfully. I have no idea what was wrong with my sendmail.cf but at least now I can read the output from periodic. Thanks a lot, Evan Dower >From: Gregory Neil Shapiro >To: "Evan Dower" >CC: freebsd-current@freebsd.org >Subject: Re: sendmail: no local mailer >Date: Wed, 2 Apr 2003 08:37:13 -0800 >MIME-Version: 1.0 >Received: from horsey.gshapiro.net ([64.105.95.154]) by >mc4-f22.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Wed, 2 Apr >2003 08:37:14 -0800 >Received: from horsey.gshapiro.net (localhost [127.0.0.1])by >horsey.gshapiro.net (8.13.0.PreAlpha1/8.13.0.PreAlpha1) with ESMTP id >h32GbD5k025227(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 >verify=NO);Wed, 2 Apr 2003 08:37:13 -0800 (PST) >Received: (from gshapiro@localhost)by horsey.gshapiro.net >(8.13.0.PreAlpha1/8.12.7/Submit) id h32GbDUx025224;Wed, 2 Apr 2003 08:37:13 >-0800 (PST) >X-Message-Info: JGTYoYF78jEHjJx36Oi8+Q1OJDRSDidP >Message-ID: <16011.4537.279737.406477@horsey.gshapiro.net> >In-Reply-To: >References: >X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid >Return-Path: gshapiro@gshapiro.net >X-OriginalArrivalTime: 02 Apr 2003 16:37:15.0054 (UTC) >FILETIME=[1E3B2CE0:01C2F936] > >evantd> Sendmail has not been working on my system for some time now. I >evantd> can't say exactly how long, but my guess is that it broke when I >evantd> upgraded to RELENG_5_0. This is how sendmail is invoked (by >evantd> default) and it's output. > >evantd> # sendmail -L sm-mta -bd -q30m -ODaemonPortOptions=Addr=localhost >evantd> 451 4.0.0 No local mailer defined: Bad address >evantd> 554 5.0.0 QueueDirectory (Q) option must be set > >/etc/mail/sendmail.cf is a bogus (empty?) file. One way to fix this is: > >cd /etc/mail >mv sendmail.cf sendmail.cf~bogus >make >make restart > _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 09:21:30 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 290B837B404; Wed, 2 Apr 2003 09:21:30 -0800 (PST) Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id C777643FA3; Wed, 2 Apr 2003 09:21:28 -0800 (PST) (envelope-from nate@yogotech.com) Received: from emerger.yogotech.com (emerger.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3p2/8.9.3) with ESMTP id KAA17412; Wed, 2 Apr 2003 10:21:26 -0700 (MST) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by emerger.yogotech.com (8.12.8/8.12.8) id h32HLMgG032087; Wed, 2 Apr 2003 10:21:22 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16011.7185.945210.92101@emerger.yogotech.com> Date: Wed, 2 Apr 2003 10:21:21 -0700 To: Terry Lambert In-Reply-To: <3E8B03E6.36871704@mindspring.com> References: <3E8B03E6.36871704@mindspring.com> X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid cc: Robert Watson cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Nate Williams List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 17:21:30 -0000 > > You should notice marked interactivity and UI latency improvements with > > threaded GUI apps over libc_r because GUI threads will generally no longer > > be blocked when disk I/O and blocking I/O occurs. For example, > > applications like Open Office, Netscape, et al, really get a lot better > > with 1:1. Likewise, non-interactive applications that are disk > > I/O-intensive, such as mysql, will also perform substantially better > > because a thread that hits blocking using an interface that doesn't > > support non-blocking I/O (such as the file system) won't clog up the > > application. > > Is the disk I/O really that big of an issue? In my experience, yes. Disk I/O is blocking, since you can't reliably use non-blocking descriptors for disk I/O, since you don't know if it will block, and for how long. Again, in my experience, it was much easier to setup non-blocking networking descriptors, since unlike disk I/O, you needed to deal with things not get written at the application. With disk I/O it was much harder to determine what if anything got written if you did non-blocking writes, and if you needed things written both effeciently and reliably to disk, you *have* to know how much was written successfully, and byte-at-a-time I/O is simply un-acceptably slow. I'm sure others have run into this problem as well. > It seems to me that maybe the correct fix for this is to use > AIO instead of non-blocking I/O, then? AIO is non-portable. Nate From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 09:26:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DD5C37B401; Wed, 2 Apr 2003 09:26:07 -0800 (PST) Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9CAA43F93; Wed, 2 Apr 2003 09:26:05 -0800 (PST) (envelope-from nate@yogotech.com) Received: from emerger.yogotech.com (emerger.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3p2/8.9.3) with ESMTP id KAA17445; Wed, 2 Apr 2003 10:26:03 -0700 (MST) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by emerger.yogotech.com (8.12.8/8.12.8) id h32HQ3c3032106; Wed, 2 Apr 2003 10:26:03 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16011.7467.322808.498405@emerger.yogotech.com> Date: Wed, 2 Apr 2003 10:26:03 -0700 To: Gregory Neil Shapiro In-Reply-To: <16011.4537.279737.406477@horsey.gshapiro.net> References: <16011.4537.279737.406477@horsey.gshapiro.net> X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid cc: freebsd-current@freebsd.org Subject: Re: sendmail: no local mailer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Nate Williams List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 17:26:07 -0000 > evantd> Sendmail has not been working on my system for some time now. I > evantd> can't say exactly how long, but my guess is that it broke when I > evantd> upgraded to RELENG_5_0. This is how sendmail is invoked (by > evantd> default) and it's output. > > evantd> # sendmail -L sm-mta -bd -q30m -ODaemonPortOptions=Addr=localhost > evantd> 451 4.0.0 No local mailer defined: Bad address > evantd> 554 5.0.0 QueueDirectory (Q) option must be set > > /etc/mail/sendmail.cf is a bogus (empty?) file. One way to fix this is: > > cd /etc/mail > mv sendmail.cf sendmail.cf~bogus > make > make restart This happened on one of my -stable boxes lately when doing a upgrade using buildworld. For some (unknown) reason m4 bombed out and created an empty .cf file. I fixed it by doing something similar to what was done above, although why m4 failed is a mystery.... Nate From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 09:27:06 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 866E337B407 for ; Wed, 2 Apr 2003 09:27:06 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6374743F85 for ; Wed, 2 Apr 2003 09:27:05 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h32HR4A8047926; Wed, 2 Apr 2003 10:27:04 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200304021727.h32HR4A8047926@harmony.village.org> To: Peter Schultz In-reply-to: Your message of "Wed, 02 Apr 2003 08:00:59 CST." <3E8AED1B.10606@jocose.org> References: <3E8AED1B.10606@jocose.org> Date: Wed, 02 Apr 2003 10:27:04 -0700 From: Warner Losh cc: current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 17:27:06 -0000 In message <3E8AED1B.10606@jocose.org> Peter Schultz writes: : I hope that core will approve removing sendmail from FreeBSD-CURRENT. Request denied. 1) you made no case for it: Everybdoy knows this is a contentious issue, yet no reasons were given. 2) You cc'd core and a public mailing list. Don't ever do that again. 3) Get consensus on arch@ first. If you can't, then chances are good that there won't be support for this. Be sure to include how basic systems will do email, and be prepared to supply patches to the install system. Warner From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 09:31:05 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1516A37B401 for ; Wed, 2 Apr 2003 09:31:05 -0800 (PST) Received: from ion.gank.org (ion.gank.org [198.78.66.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7034843F75 for ; Wed, 2 Apr 2003 09:31:04 -0800 (PST) (envelope-from craig@xfoil.gank.org) Received: from owen1492.uf.corelab.com (unknown [206.50.138.222]) by ion.gank.org (GankMail) with ESMTP id 2D32D2BF58 for ; Wed, 2 Apr 2003 11:31:04 -0600 (CST) From: Craig Boston To: freebsd-current@freebsd.org Content-Type: text/plain Organization: Message-Id: <1049304662.10796.27.camel@owen1492.uf.corelab.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 02 Apr 2003 11:31:02 -0600 Content-Transfer-Encoding: 7bit Subject: IPv6 MTU bug? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 17:31:05 -0000 I was trying some network diagnostics yesterday and needed to generate a continuous stream of small packets going across a few routers. So I used ifconfig to set my MTU to some very low values (100, 300, 500, and a few others). I know there's probably a better way to accomplish that, but couldn't think of any at the time so that's what I did :) Anyway, when I was done, I reset the MTU on my ethernet interface back to 1500. IPv4 is working fine, but IPv6 is still acting like I have a low MTU set. All IPv6 TCP connections are limiting the MSS to around 28 bytes of data per packet, and ping6 complains with ping sizes more than around 50. I think I've tracked down the problem to this code in nd6.c, specifically in nd6_setmtu(ifp). Note that at this point ndi->maxmtu has just been set to MIN([user-requested MTU], [biggest MTU possible for this interface type]). ndi->linkmtu hasn't been touched yet and is still set to whatever the previous linkmtu was. if (ndi->linkmtu == 0 || ndi->maxmtu < ndi->linkmtu) { ndi->linkmtu = ndi->maxmtu; /* also adjust in6_maxmtu if necessary. */ if (oldlinkmtu == 0) { /* * XXX: the case analysis is grotty, but * it is not efficient to call in6_setmaxmtu() * here when we are during the initialization * procedure. */ if (in6_maxmtu < ndi->linkmtu) in6_maxmtu = ndi->linkmtu; } else in6_setmaxmtu(); } It looks to me that in the case of raising an interface's MTU, ndi->maxmtu will be >= ndi->linkmtu, causing linkmtu to never get reset. I may be missing something, but I can't quite figure out the logical reason for that test. Luckily I had a kernel.debug lying around so I used gdb to peek into the kernel memory. In the nd_ifinfo for that interface, linkmtu=100 and maxmtu=1500. Once I manually reset linkmtu to 1500, IPv6 started working properly again, without having to sacrifice my uptime :) Anyway, the behavior looks like a bug, but the code makes it look like this may be an intentional effect. Any kernel networking gurus care to comment? Thanks, Craig From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 10:01:26 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E47BD37B401; Wed, 2 Apr 2003 10:01:26 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39B8F43F85; Wed, 2 Apr 2003 10:01:26 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.9/8.12.7) with ESMTP id h32I1BD0068498; Wed, 2 Apr 2003 10:01:11 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h32I1AjG068497; Wed, 2 Apr 2003 10:01:10 -0800 (PST) Date: Wed, 2 Apr 2003 10:01:09 -0800 From: "David O'Brien" To: Jens Rehsack Message-ID: <20030402180108.GA68454@dragon.nuxi.com> References: <3E8B093D.4010500@liwing.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E8B093D.4010500@liwing.de> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@FreeBSD.org cc: John Baldwin Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-current@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 18:01:27 -0000 On Wed, Apr 02, 2003 at 06:01:01PM +0200, Jens Rehsack wrote: > The problem I see with that is, that even a minimalistic base install > installs things like sendmail, ppp, atm-stuff, g77 and so on. I would love to see the toolchain broken out into its own tarball like NetBSD. It isn't a simple 10min change though. From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 10:08:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C65537B401 for ; Wed, 2 Apr 2003 10:08:38 -0800 (PST) Received: from mail.liwing.de (mail.liwing.de [213.70.188.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6637043F93 for ; Wed, 2 Apr 2003 10:08:36 -0800 (PST) (envelope-from rehsack@liwing.de) Received: (qmail 3482 invoked from network); 2 Apr 2003 18:08:33 -0000 Received: from stingray.liwing.de (HELO liwing.de) ([213.70.188.164]) (envelope-sender ) by mail.liwing.de (qmail-ldap-1.03) with SMTP for ; 2 Apr 2003 18:08:33 -0000 Message-ID: <3E8B2720.4080000@liwing.de> Date: Wed, 02 Apr 2003 20:08:32 +0200 From: Jens Rehsack Organization: LiWing IT-Services User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org References: <3E8B093D.4010500@liwing.de> <20030402180108.GA68454@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: obrien@FreeBSD.ORG cc: John Baldwin Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 18:08:38 -0000 David O'Brien wrote: > On Wed, Apr 02, 2003 at 06:01:01PM +0200, Jens Rehsack wrote: > >>The problem I see with that is, that even a minimalistic base install >>installs things like sendmail, ppp, atm-stuff, g77 and so on. > > I would love to see the toolchain broken out into its own tarball like > NetBSD. It isn't a simple 10min change though. > I know. If it would someone had done before :-) It more a wish than a real expectation. Is somewhere a todo list how going on when trying to add eg. NO_PPP? Maybe: update your source to current check directories belong to patch Makefile(s) save patches buildworld reboot to single user mode rm usr/bin usr/lib usr/sbin /usr/libexec make installworld Are there any tests for the world available? If not, maybe a good point starting is writing a test suite which checks working of each not deselected world-component as good as it get's. Regards, Jens From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 10:12:08 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74BB337B407 for ; Wed, 2 Apr 2003 10:12:08 -0800 (PST) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94A4243FAF for ; Wed, 2 Apr 2003 10:12:07 -0800 (PST) (envelope-from winter@jurai.net) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.9/8.12.9) with ESMTP id h32IC1EF096706; Wed, 2 Apr 2003 13:12:05 -0500 (EST) (envelope-from winter@jurai.net) Date: Wed, 2 Apr 2003 13:12:01 -0500 (EST) From: "Matthew N. Dodd" To: "Michael W . Lucas" In-Reply-To: <20030402095657.A32353@blackhelicopters.org> Message-ID: <20030402131114.F46852@sasami.jurai.net> References: <20030402092055.A31850@blackhelicopters.org> <20030402143055.GB790@starjuice.net> <20030402145100.GC790@starjuice.net> <20030402095657.A32353@blackhelicopters.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: breakage this morning X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 18:12:08 -0000 On Wed, 2 Apr 2003, Michael W . Lucas wrote: > Thank you very much! Sorry about the breakage. -- | 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 | For Great Justice! | ISO8802.5 4ever | From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 11:29:33 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AB5F37B401 for ; Wed, 2 Apr 2003 11:29:33 -0800 (PST) Received: from mail.speakeasy.net (mail15.speakeasy.net [216.254.0.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A8B043FBD for ; Wed, 2 Apr 2003 11:29:32 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 28582 invoked from network); 2 Apr 2003 19:29:37 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 2 Apr 2003 19:29:37 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.8/8.12.8) with ESMTP id h32JTTOv023621; Wed, 2 Apr 2003 14:29:29 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3E8B093D.4010500@liwing.de> Date: Wed, 02 Apr 2003 14:29:30 -0500 (EST) From: John Baldwin To: Jens Rehsack cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 19:29:33 -0000 On 02-Apr-2003 Jens Rehsack wrote: > John Baldwin wrote: >> On 02-Apr-2003 Peter Schultz wrote: >> >>>I'm sorry for beating a dead horse. A guy and I from tcbug were just >>>trying to fix his postfix installation, he does not know what happened, >>>it just stopped working. There would not have been a problem if >>>sendmail wasn't tied into the system so closely. I'm just hoping core >>>will say, "submit a working solution and it will be done," so that >>>there's a little inspiration here. >>> >>>Pete... >> >> >> First, core@ is not the appropriate body for that type of request. >> Both current@ and arch@ are much better targets. Second, is >> NO_SENDMAIL + the postfix port inadequate? >> > > The problem I see with that is, that even a minimalistic base install > installs things like sendmail, ppp, atm-stuff, g77 and so on. Unless you are building an embedded device these are not really all that significant. If you are building an embedded device, you probably are better off building an in-house custom release. NO_SENDMAIL, etc. can aid in simplifying the build of such a release and help prevent breakage to an existing environment during world upgrades. That seems to be a fairly decent solution to me. > I really think splitting the base in some sub-parts would it make much > easier to do NO_SENDMAIL on my own. So I had to remove each not required > file separately. That's no good solution. [stepping back a bit ] I find an odd situation here whenever this topic comes up. One the one hand, people are always wanting to split the entire base system up into small packages for each little piece of the base. On the other hand, one of FreeBSD's selling points in real-world environments is that it doesn't have a bunch of little packages for the base system like Linux distros. Do people really prefer something like having rpm's for /bin/ps to having one lump base dist for all of /bin, /sbin, etc.? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 11:40:00 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9152337B404; Wed, 2 Apr 2003 11:40:00 -0800 (PST) Received: from aeimail.aei.ca (aeimail.aei.ca [206.123.6.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA76543FBF; Wed, 2 Apr 2003 11:39:58 -0800 (PST) (envelope-from anarcat@anarcat.ath.cx) Received: from shall.anarcat.ath.cx (a7r7eha2sx79cthb@dsl-133-253.aei.ca [66.36.133.253]) by aeimail.aei.ca (8.11.6/8.10.1) with ESMTP id h32JdvA05608; Wed, 2 Apr 2003 14:39:57 -0500 (EST) Received: from lenny.anarcat.ath.cx (lenny.anarcat.ath.cx [192.168.0.4]) by shall.anarcat.ath.cx (Postfix) with SMTP id 5C37AE3; Wed, 2 Apr 2003 14:39:56 -0500 (EST) Received: by lenny.anarcat.ath.cx (sSMTP sendmail emulation); Wed, 2 Apr 2003 14:40:05 -0500 Date: Wed, 2 Apr 2003 14:40:05 -0500 From: The Anarcat To: John Baldwin Message-ID: <20030402194005.GL616@lenny.anarcat.ath.cx> Mail-Followup-To: John Baldwin , Jens Rehsack , freebsd-current@freebsd.org References: <3E8B093D.4010500@liwing.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="umrsQkkrw7viUWFs" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.3i cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 19:40:00 -0000 --umrsQkkrw7viUWFs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed Apr 02, 2003 at 02:29:30PM -0500, John Baldwin wrote: >=20 > > I really think splitting the base in some sub-parts would it make much= =20 > > easier to do NO_SENDMAIL on my own. So I had to remove each not require= d=20 > > file separately. That's no good solution. >=20 > [stepping back a bit ] >=20 > I find an odd situation here whenever this topic comes up. One the > one hand, people are always wanting to split the entire base system > up into small packages for each little piece of the base. On the > other hand, one of FreeBSD's selling points in real-world environments > is that it doesn't have a bunch of little packages for the base system > like Linux distros. Do people really prefer something like having > rpm's for /bin/ps to having one lump base dist for all of /bin, /sbin, > etc.? Those two aren't necessarly in contradiction. We could provide a myriad of small packages and a "wrapper package" containing them all. Debian has "tasks" to deal with this, it's a meta package that solely depend on other packages. We could do something similar, or even better: make a meta package that actually embeds the other package files. No I don't have any patches. A. --=20 Advertisers, not governments, are the primary censors of media content=20 in the United States today. - C. Edwin Baker http://www.ad-mad.co.uk/quotes/freespeech.htm --umrsQkkrw7viUWFs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+izyUttcWHAnWiGcRAtDJAJ9IEogA6wCaGdKvXJkjmaEFoBCGdwCfV3Rp o5EyXXLSNJtamCxzhHb4qCA= =yb5c -----END PGP SIGNATURE----- --umrsQkkrw7viUWFs-- From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 11:41:10 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2797C37B401; Wed, 2 Apr 2003 11:41:10 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCF0043FB1; Wed, 2 Apr 2003 11:41:08 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.8/8.12.8) with ESMTP id h32Jf6SM032261; Wed, 2 Apr 2003 21:41:07 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: John Baldwin From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 02 Apr 2003 14:29:30 CDT." Date: Wed, 02 Apr 2003 21:41:06 +0200 Message-ID: <32260.1049312466@critter.freebsd.dk> cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 19:41:10 -0000 In message , John Baldwin writes: >I find an odd situation here whenever this topic comes up. One the >one hand, people are always wanting to split the entire base system >up into small packages for each little piece of the base. On the >other hand, one of FreeBSD's selling points in real-world environments >is that it doesn't have a bunch of little packages for the base system >like Linux distros. Do people really prefer something like having >rpm's for /bin/ps to having one lump base dist for all of /bin, /sbin, >etc.? I am, like any other geek, totally unable to resist anything with many controls, handles, levers and indicators. So of course I want total control of every aspect, inside my immediate grasp at the flick of simple switch. On the other hand, I have in the last 20 years found that after a few weeks I can seldomly remember how I had all the switches set last time, and therefore wasted precious time figuring it out (again). So all in all, Unless I run out of diskspace, I generally install the entire thing. The only place where I can see a sufficient benefit from being able to chop off stuff from the FreeBSD tree is in the embedded systems area, and for that having the controls in /etc/make.conf works fine for me. I think the only gadget I miss is a web-page somewhere with a set of buttons, one for each option, and a "calculate total size needed" submit button which tell me how many files, bytes etc the chosen configuration takes up on the specified FreeBSD version. Maybe this page could also contain an option to show the list of files, and maybe even a "backwards" option to tell which options are involved in a particular file or directorys existence. So, to answer you question: I like it as it is where I can disable stuff in /etc/make.conf, but I could used increased visibility into "what all them dang switches might do". -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 11:50:29 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFFC137B401 for ; Wed, 2 Apr 2003 11:50:29 -0800 (PST) Received: from neptune.he.net (neptune.he.net [216.218.166.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4371843F3F for ; Wed, 2 Apr 2003 11:50:29 -0800 (PST) (envelope-from fluid@sfmidimafia.com) Received: from sfmidimafia.com (stalwart.codysbooks.COM [209.133.54.175]) by neptune.he.net (8.8.6p2003-03-31/8.8.2) with ESMTP id LAA19954 for ; Wed, 2 Apr 2003 11:50:33 -0800 Message-ID: <3E8B3F06.80408@sfmidimafia.com> Date: Wed, 02 Apr 2003 11:50:30 -0800 From: "Scott R." Organization: Cody's Books User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030326 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Some ports not -current compatible? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 19:50:30 -0000 I tried soliciting ports@ and questions@ for answers to these questions, but no answers were volunteered which leads me to believe that these issues may be specific to -current. I'm hoping someone can give me a clue as to what the problem is or at least give me a pointer (have searched extensively on google and the list archives only to find my same questions unanswered). First, I'm trying to get wine to work and I'm having a really hard time with it. It compiles and installs okay, but when I run it, I get: err:ddeml:DdeConnect Done with INITIATE, but no Server window available This is when I try to run the install program from a simple solitaire game. Does anyone have wine working with -current? If so, how did you get it to work? The second problem I'm seeing is with ymessenger. Again, it builds and installs just fine, but when I run it, I get: /usr/libexec/ld-elf.so.1: /usr/local/lib/libintl.so.4: Undefined symbol "stpcpy" The only examples I found of other people running into this were when they upgraded from 4.x to 5.x and the old libraries were being linked, but this box was initially installed with 5.0-RELEASE so that couldn't be it. Any ideas? Thanks, Scott From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 11:50:42 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FEFB37B405; Wed, 2 Apr 2003 11:50:42 -0800 (PST) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E61A43FA3; Wed, 2 Apr 2003 11:50:39 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by rwcrmhc51.attbi.com (rwcrmhc51) with ESMTP id <2003040219503805100aeamce>; Wed, 2 Apr 2003 19:50:38 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA17348; Wed, 2 Apr 2003 11:50:37 -0800 (PST) Date: Wed, 2 Apr 2003 11:50:36 -0800 (PST) From: Julian Elischer To: Poul-Henning Kamp In-Reply-To: <32260.1049312466@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 19:50:42 -0000 On Wed, 2 Apr 2003, Poul-Henning Kamp wrote: > > Maybe this page could also contain an option to show the list of > files, and maybe even a "backwards" option to tell which options > are involved in a particular file or directorys existence. > > So, to answer you question: I like it as it is where I can disable > stuff in /etc/make.conf, but I could used increased visibility into > "what all them dang switches might do". > Amen From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 11:50:58 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7852437B408 for ; Wed, 2 Apr 2003 11:50:55 -0800 (PST) Received: from MAILSERVER.ofw.fi (ns.ofw.fi [194.111.144.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76FAE43FD7 for ; Wed, 2 Apr 2003 11:50:54 -0800 (PST) (envelope-from dan.naumov@ofw.fi) Received: from [172.16.161.81] by MAILSERVER.ofw.fi (NTMail 7.00.0022/NT1439.00.90501b21) with ESMTP id hhbejaaa for freebsd-current@freebsd.org; Wed, 2 Apr 2003 22:50:02 +0300 Date: Wed, 2 Apr 2003 22:54:27 +0300 From: Dan Naumov To: freebsd-current@freebsd.org Message-Id: <20030402225427.586c463a.dan.naumov@ofw.fi> In-Reply-To: References: <3E8B093D.4010500@liwing.de> X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 19:50:59 -0000 On Wed, 02 Apr 2003 14:29:30 -0500 (EST) John Baldwin wrote: > I find an odd situation here whenever this topic comes up. One the > one hand, people are always wanting to split the entire base system > up into small packages for each little piece of the base. On the > other hand, one of FreeBSD's selling points in real-world environments > is that it doesn't have a bunch of little packages for the base system > like Linux distros. Do people really prefer something like having > rpm's for /bin/ps to having one lump base dist for all of /bin, /sbin, > etc.? It really depends on where you draw the line. Personally, I'd rather have a very minimal base system that's kept as a "whole" with additional packages avaible for those who want them. Basically if I was to decide on such things, I'd throw out CVS, BIND, g77, GDB, OpenSSL, SendMail, games and crypto out of base and making them avaible through ports. But that's all IMHO and not very likely to happen to FreeBSD in my lifetime ;) Sincerely, -- Dan Naumov From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 11:56:45 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBD6F37B401; Wed, 2 Apr 2003 11:56:45 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5BF843FD7; Wed, 2 Apr 2003 11:56:42 -0800 (PST) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.9/8.12.9) with ESMTP id h32Jufik000659; Wed, 2 Apr 2003 21:56:41 +0200 (CEST) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.9/8.12.9/Submit) id h32JufkK000654; Wed, 2 Apr 2003 21:56:41 +0200 (CEST) Date: Wed, 2 Apr 2003 21:56:40 +0200 From: Wilko Bulte To: John Baldwin Message-ID: <20030402195640.GA318@freebie.xs4all.nl> References: <3E8B093D.4010500@liwing.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-OS: FreeBSD 4.8-RC X-PGP: finger wilko@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 19:56:46 -0000 On Wed, Apr 02, 2003 at 02:29:30PM -0500, John Baldwin wrote: ... > [stepping back a bit ] > > I find an odd situation here whenever this topic comes up. One the > one hand, people are always wanting to split the entire base system > up into small packages for each little piece of the base. On the > other hand, one of FreeBSD's selling points in real-world environments > is that it doesn't have a bunch of little packages for the base system > like Linux distros. Do people really prefer something like having > rpm's for /bin/ps to having one lump base dist for all of /bin, /sbin, > etc.? One of the worst mis-features of Linux in my book. -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 12:02:03 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 911E037B408 for ; Wed, 2 Apr 2003 12:02:03 -0800 (PST) Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de [193.174.154.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 457D543F93 for ; Wed, 2 Apr 2003 12:02:00 -0800 (PST) (envelope-from brandt@fokus.fraunhofer.de) Received: from beagle (beagle [193.175.132.100])h32K1wE16484; Wed, 2 Apr 2003 22:01:58 +0200 (MEST) Date: Wed, 2 Apr 2003 22:01:58 +0200 (CEST) From: Harti Brandt To: Dan Naumov In-Reply-To: <20030402225427.586c463a.dan.naumov@ofw.fi> Message-ID: <20030402215654.K29076@beagle.fokus.fraunhofer.de> References: <3E8B093D.4010500@liwing.de> <20030402225427.586c463a.dan.naumov@ofw.fi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 20:02:03 -0000 On Wed, 2 Apr 2003, Dan Naumov wrote: DN>On Wed, 02 Apr 2003 14:29:30 -0500 (EST) DN>John Baldwin wrote: DN> DN>> I find an odd situation here whenever this topic comes up. One the DN>> one hand, people are always wanting to split the entire base system DN>> up into small packages for each little piece of the base. On the DN>> other hand, one of FreeBSD's selling points in real-world environments DN>> is that it doesn't have a bunch of little packages for the base system DN>> like Linux distros. Do people really prefer something like having DN>> rpm's for /bin/ps to having one lump base dist for all of /bin, /sbin, DN>> etc.? DN> DN>It really depends on where you draw the line. Personally, I'd rather DN>have a very minimal base system that's kept as a "whole" with additional DN>packages avaible for those who want them. Basically if I was to decide DN>on such things, I'd throw out CVS, BIND, g77, GDB, OpenSSL, SendMail, DN>games and crypto out of base and making them avaible through ports. But DN>that's all IMHO and not very likely to happen to FreeBSD in my lifetime DN>;) I hope so. I have two fears with regard to splitting up the system: things in ports will start to rot. Developers will 'make world' and this will just compile the basic stuff. People will forget about the packages. Second, the last time I tried Linux (this was a couple of years ago) I got immediatly tired of foo-X.Y needs libbar-A.B bar-Z.T needs libbar-C.D and unfortunately you cannot have libbar-A.B and libbar-C.D together. Splitting up without dependencies between the packages is likely to be very hard if not impossible. harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fraunhofer.de, harti@freebsd.org From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 12:11:25 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5FEB37B401 for ; Wed, 2 Apr 2003 12:11:25 -0800 (PST) Received: from ztxmail05.ztx.compaq.com (ztxmail05.ztx.compaq.com [161.114.1.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id D45A943FAF for ; Wed, 2 Apr 2003 12:11:24 -0800 (PST) (envelope-from john.cagle@hp.com) Received: from cceexg12.americas.cpqcorp.net (cceexg12.americas.cpqcorp.net [16.110.250.124]) by ztxmail05.ztx.compaq.com (Postfix) with ESMTP id 0F5B2802D for ; Wed, 2 Apr 2003 14:11:24 -0600 (CST) Received: from cceexc19.americas.cpqcorp.net ([16.110.250.85]) by cceexg12.americas.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.2966); Wed, 2 Apr 2003 14:11:23 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C2F954.07B9BE86" Date: Wed, 2 Apr 2003 14:11:22 -0600 Message-ID: X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: sio problem in -current (COM1) Thread-Index: AcL5T8Iw1W6+BxD6TSa0+feHD5nFogAAxMAw From: "Cagle, John (ISS-Houston)" To: X-OriginalArrivalTime: 02 Apr 2003 20:11:23.0847 (UTC) FILETIME=[08B56570:01C2F954] Subject: sio problem in -current (COM1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 20:11:26 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2F954.07B9BE86 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I'm having a problem with -current on a ProLiant BL10e blade server. On the blade server, we use a serial console on sio0/COM1. This works perfectly with 4.8, but for some reason, the sio driver doesn't see COM1 at all, and assigns COM2 resources to sio0. Any pointers to where I should look would be greatly appreciated. I've attached dmesg output for 4.8 and -current on this blade. Thanks, John -------------------------------- John Cagle john.cagle@hp.com Principal Member Technical Staff Industry Standard Servers Hewlett-Packard Company ------_=_NextPart_001_01C2F954.07B9BE86 Content-Type: text/plain; name="dmesg48.txt" Content-Transfer-Encoding: base64 Content-Description: dmesg48.txt Content-Disposition: attachment; filename="dmesg48.txt" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDMgVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0IChj KSAxOTc5LCAxOTgwLCAxOTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAxOTkzLCAx OTk0CglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlhLiBBbGwgcmln aHRzIHJlc2VydmVkLgpGcmVlQlNEIDQuOC1SQyAjMzogVHVlIEFwciAgMSAyMDoyNjoxMSBDU1Qg MjAwMwogICAgcm9vdEBidXN5ZC5hbWVyaWNhcy5jcHFjb3JwLm5ldDovdXNyL29iai91c3Ivc3Jj L3N5cy9CTDEwRQpUaW1lY291bnRlciAiaTgyNTQiICBmcmVxdWVuY3kgMTE5MzE4MiBIegpDUFU6 IE1vYmlsZSBJbnRlbChSKSBQZW50aXVtKFIpIElJSSBDUFUgLSBNICAgOTAwTUh6ICg4ODkuODUt TUh6IDY4Ni1jbGFzcyBDUFUpCiAgT3JpZ2luID0gIkdlbnVpbmVJbnRlbCIgIElkID0gMHg2YjQg IFN0ZXBwaW5nID0gNAogIEZlYXR1cmVzPTB4MzgzZjlmZjxGUFUsVk1FLERFLFBTRSxUU0MsTVNS LFBBRSxNQ0UsQ1g4LFNFUCxNVFJSLFBHRSxNQ0EsQ01PVixQQVQsUFNFMzYsTU1YLEZYU1IsU1NF PgpyZWFsIG1lbW9yeSAgPSA1MzY4NTQ1MjggKDUyNDI3MksgYnl0ZXMpCmNvbmZpZz4gZGkgc2lv Mgpjb25maWc+IGRpIHBwYzAKY29uZmlnPiBkaSBidDAKY29uZmlnPiBkaSBhdGExCmNvbmZpZz4g ZGkgYWljMApjb25maWc+IGRpIGFoYTAKY29uZmlnPiBkaSBhZHYwCmNvbmZpZz4gcQphdmFpbCBt ZW1vcnkgPSA1MTc1MTczMTIgKDUwNTM4OEsgYnl0ZXMpClByZWxvYWRlZCBlbGYga2VybmVsICJr ZXJuZWwiIGF0IDB4YzA0YzAwMDAuClByZWxvYWRlZCB1c2VyY29uZmlnX3NjcmlwdCAiL2Jvb3Qv a2VybmVsLmNvbmYiIGF0IDB4YzA0YzAwOWMuClBlbnRpdW0gUHJvIE1UUlIgc3VwcG9ydCBlbmFi bGVkCm1kMDogTWFsbG9jIGRpc2sKbnB4MDogPG1hdGggcHJvY2Vzc29yPiBvbiBtb3RoZXJib2Fy ZApucHgwOiBJTlQgMTYgaW50ZXJmYWNlCnBjaWIwOiA8U2VydmVyV29ya3MgTkI2NjM1IDMuMExF IGhvc3QgdG8gUENJIGJyaWRnZT4gb24gbW90aGVyYm9hcmQKcGNpMDogPFBDSSBidXM+IG9uIHBj aWIwCnBjaTA6IDx1bmtub3duIGNhcmQ+ICh2ZW5kb3I9MHgwZTExLCBkZXY9MHhhMGYwKSBhdCAx LjAgaXJxIDUKcGNpMDogPEFUSSBNYWNoNjQtR1IgZ3JhcGhpY3MgYWNjZWxlcmF0b3I+IGF0IDIu MCBpcnEgNwpmeHAwOiA8SW50ZWwgUHJvIDEwLzEwMEIvMTAwKyBFdGhlcm5ldD4gcG9ydCAweDI4 MDAtMHgyODNmIG1lbSAweGM0ZTAwMDAwLTB4YzRlZmZmZmYsMHhjNGZmZTAwMC0weGM0ZmZlZmZm IGlycSAxMCBhdCBkZXZpY2UgMy4wIG9uIHBjaTAKZnhwMDogRXRoZXJuZXQgYWRkcmVzcyAwMDow ODowMjphMzpmZjphYQppbnBoeTA6IDxpODI1NTUgMTAvMTAwIG1lZGlhIGludGVyZmFjZT4gb24g bWlpYnVzMAppbnBoeTA6ICAxMGJhc2VULCAxMGJhc2VULUZEWCwgMTAwYmFzZVRYLCAxMDBiYXNl VFgtRkRYLCBhdXRvCmZ4cDE6IDxJbnRlbCBQcm8gMTAvMTAwQi8xMDArIEV0aGVybmV0PiBwb3J0 IDB4Mjg0MC0weDI4N2YgbWVtIDB4YzRjMDAwMDAtMHhjNGNmZmZmZiwweGM0ZGZmMDAwLTB4YzRk ZmZmZmYgaXJxIDExIGF0IGRldmljZSA0LjAgb24gcGNpMApmeHAxOiBFdGhlcm5ldCBhZGRyZXNz IDAwOjA4OjAyOmEzOmZmOmFiCmlucGh5MTogPGk4MjU1NSAxMC8xMDAgbWVkaWEgaW50ZXJmYWNl PiBvbiBtaWlidXMxCmlucGh5MTogIDEwYmFzZVQsIDEwYmFzZVQtRkRYLCAxMDBiYXNlVFgsIDEw MGJhc2VUWC1GRFgsIGF1dG8KaXNhYjA6IDxQQ0kgdG8gSVNBIGJyaWRnZSAodmVuZG9yPTExNjYg ZGV2aWNlPTAyMDEpPiBhdCBkZXZpY2UgMTUuMCBvbiBwY2kwCmlzYTA6IDxJU0EgYnVzPiBvbiBp c2FiMAphdGFwY2kwOiA8U2VydmVyV29ya3MgQ1NCNSBBVEExMDAgY29udHJvbGxlcj4gcG9ydCAw eDIwMDAtMHgyMDBmLDB4Mzc0LTB4Mzc3LDB4MTcwLTB4MTc3LDB4M2Y0LTB4M2Y3LDB4MWYwLTB4 MWY3IGF0IGRldmljZSAxNS4xIG9uIHBjaTAKYXRhMDogYXQgMHgxZjAgaXJxIDE0IG9uIGF0YXBj aTAKYXRhMTogYXQgMHgxNzAgaXJxIDE1IG9uIGF0YXBjaTAKb2hjaTA6IDxPSENJIChnZW5lcmlj KSBVU0IgY29udHJvbGxlcj4gbWVtIDB4YzRiZmYwMDAtMHhjNGJmZmZmZiBpcnEgNyBhdCBkZXZp Y2UgMTUuMiBvbiBwY2kwCnVzYjA6IE9IQ0kgdmVyc2lvbiAxLjAsIGxlZ2FjeSBzdXBwb3J0CnVz YjA6IFNNTSBkb2VzIG5vdCByZXNwb25kLCByZXNldHRpbmcKdXNiMDogPE9IQ0kgKGdlbmVyaWMp IFVTQiBjb250cm9sbGVyPiBvbiBvaGNpMAp1c2IwOiBVU0IgcmV2aXNpb24gMS4wCnVodWIwOiAo MHgxMTY2KSBPSENJIHJvb3QgaHViLCBjbGFzcyA5LzAsIHJldiAxLjAwLzEuMDAsIGFkZHIgMQp1 aHViMDogNCBwb3J0cyB3aXRoIDQgcmVtb3ZhYmxlLCBzZWxmIHBvd2VyZWQKcGNpYjI6IDxTZXJ2 ZXJXb3JrcyBOQjY2MzUgMy4wTEUgaG9zdCB0byBQQ0kgYnJpZGdlPiBvbiBtb3RoZXJib2FyZApw Y2kyOiA8UENJIGJ1cz4gb24gcGNpYjIKcGNpYjE6IDxIb3N0IHRvIFBDSSBicmlkZ2U+IG9uIG1v dGhlcmJvYXJkCnBjaTE6IDxQQ0kgYnVzPiBvbiBwY2liMQplaXNhMDogPEVJU0EgYnVzPiBvbiBt b3RoZXJib2FyZAptYWluYm9hcmQwOiA8Q1BRMDcyNSAoU3lzdGVtIEJvYXJkKT4gb24gZWlzYTAg c2xvdCAwCm9ybTA6IDxPcHRpb24gUk9Ncz4gYXQgaW9tZW0gMHhjMDAwMC0weGM3ZmZmLDB4Yzgw MDAtMHhjOTdmZiwweGUwMDAwLTB4ZTdmZmYgb24gaXNhMApmZGMwOiA8TkVDIDcyMDY1QiBvciBj bG9uZT4gYXQgcG9ydCAweDNmMC0weDNmNSwweDNmNyBpcnEgNiBkcnEgMiBvbiBpc2EwCmZkYzA6 IEZJRk8gZW5hYmxlZCwgOCBieXRlcyB0aHJlc2hvbGQKZmQwOiA8MTQ0MC1LQiAzLjUiIGRyaXZl PiBvbiBmZGMwIGRyaXZlIDAKYXRrYmRjMDogPEtleWJvYXJkIGNvbnRyb2xsZXIgKGk4MDQyKT4g YXQgcG9ydCAweDYwLDB4NjQgb24gaXNhMAp2Z2EwOiA8R2VuZXJpYyBJU0EgVkdBPiBhdCBwb3J0 IDB4M2MwLTB4M2RmIGlvbWVtIDB4YTAwMDAtMHhiZmZmZiBvbiBpc2EwCnNjMDogPFN5c3RlbSBj b25zb2xlPiBhdCBmbGFncyAweDEwMCBvbiBpc2EwCnNjMDogVkdBIDwxNiB2aXJ0dWFsIGNvbnNv bGVzLCBmbGFncz0weDEwMD4Kc2lvMCBhdCBwb3J0IDB4M2Y4LTB4M2ZmIGlycSA0IGZsYWdzIDB4 MTAgb24gaXNhMApzaW8wOiB0eXBlIDE2NTUwQSwgY29uc29sZQpzaW8xIGF0IHBvcnQgMHgyZjgt MHgyZmYgaXJxIDMgb24gaXNhMApzaW8xOiB0eXBlIDE2NTUwQQphZDA6IDM4MTU0TUIgPEhJVEFD SElfREsyM0VCLTQwPiBbNzc1MjAvMTYvNjNdIGF0IGF0YTAtbWFzdGVyIFVETUExMDAKTW91bnRp bmcgcm9vdCBmcm9tIHVmczovZGV2L2FkMHMxYQo= ------_=_NextPart_001_01C2F954.07B9BE86 Content-Type: text/plain; name="dmesg50.txt" Content-Transfer-Encoding: base64 Content-Description: dmesg50.txt Content-Disposition: attachment; filename="dmesg50.txt" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDMgVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0IChj KSAxOTc5LCAxOTgwLCAxOTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAxOTkzLCAx OTk0CglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlhLiBBbGwgcmln aHRzIHJlc2VydmVkLgpGcmVlQlNEIDUuMC1DVVJSRU5UICMyOiBUdWUgQXByICAxIDIwOjA0OjU1 IEdNVCAyMDAzCiAgICByb290QGp1bmtldC5hbWVyaWNhcy5jcHFjb3JwLm5ldDovdXNyL29iai91 c3Ivc3JjL3N5cy9CTDEwRQpQcmVsb2FkZWQgZWxmIGtlcm5lbCAiL2Jvb3Qva2VybmVsL2tlcm5l bCIgYXQgMHhjMDRlMzAwMC4KUHJlbG9hZGVkIGVsZiBtb2R1bGUgIi9ib290L2tlcm5lbC9hY3Bp LmtvIiBhdCAweGMwNGUzMGE4LgpUaW1lY291bnRlciAiaTgyNTQiICBmcmVxdWVuY3kgMTE5MzE4 MiBIegpUaW1lY291bnRlciAiVFNDIiAgZnJlcXVlbmN5IDg4OTg0ODkwNCBIegpDUFU6IE1vYmls ZSBJbnRlbChSKSBQZW50aXVtKFIpIElJSSBDUFUgLSBNICAgOTAwTUh6ICg4ODkuODUtTUh6IDY4 Ni1jbGFzcyBDUFUpCiAgT3JpZ2luID0gIkdlbnVpbmVJbnRlbCIgIElkID0gMHg2YjQgIFN0ZXBw aW5nID0gNAogIEZlYXR1cmVzPTB4MzgzZjlmZjxGUFUsVk1FLERFLFBTRSxUU0MsTVNSLFBBRSxN Q0UsQ1g4LFNFUCxNVFJSLFBHRSxNQ0EsQ01PVixQQVQsUFNFMzYsTU1YLEZYU1IsU1NFPgpyZWFs IG1lbW9yeSAgPSA1MzY4NTQ1MjggKDUxMSBNQikKYXZhaWwgbWVtb3J5ID0gNTE2MjE0Nzg0ICg0 OTIgTUIpCkFsbG9jYXRpbmcgbWFqb3IjMjUzIHRvICJuZXQiCkFsbG9jYXRpbmcgbWFqb3IjMjUy IHRvICJnX2N0bCIKQWxsb2NhdGluZyBtYWpvciMyNTEgdG8gInBjaSIKUGVudGl1bSBQcm8gTVRS UiBzdXBwb3J0IGVuYWJsZWQKbnB4MDogPG1hdGggcHJvY2Vzc29yPiBvbiBtb3RoZXJib2FyZApu cHgwOiBJTlQgMTYgaW50ZXJmYWNlCmFjcGkwOiA8Q09NUEFRIEkwMyAgICAgPiBvbiBtb3RoZXJi b2FyZAogICAgQUNQSS0wNjI1OiAqKiogSW5mbzogR1BFIEJsb2NrMCBkZWZpbmVkIGFzIEdQRTAg dG8gR1BFMzEKYWNwaTA6IHBvd2VyIGJ1dHRvbiBpcyBoYW5kbGVkIGFzIGEgZml4ZWQgZmVhdHVy ZSBwcm9ncmFtbWluZyBtb2RlbC4KVGltZWNvdW50ZXIgIkFDUEktc2FmZSIgIGZyZXF1ZW5jeSAz NTc5NTQ1IEh6CnBjaWJpb3M6IEJJT1MgdmVyc2lvbiAyLjEwCmFjcGlfdGltZXIwOiA8MzItYml0 IHRpbWVyIGF0IDMuNTc5NTQ1TUh6PiBwb3J0IDB4ZjgwOC0weGY4MGIgb24gYWNwaTAKYWNwaV9j cHUwOiA8Q1BVPiBvbiBhY3BpMAphY3BpX3R6MDogPHRoZXJtYWwgem9uZT4gb24gYWNwaTAKcGNp YjA6IDxBQ1BJIEhvc3QtUENJIGJyaWRnZT4gb24gYWNwaTAKcGNpMDogPEFDUEkgUENJIGJ1cz4g b24gcGNpYjAKcGNpMDogPGJhc2UgcGVyaXBoZXJhbD4gYXQgZGV2aWNlIDEuMCAobm8gZHJpdmVy IGF0dGFjaGVkKQpwY2kwOiA8ZGlzcGxheSwgVkdBPiBhdCBkZXZpY2UgMi4wIChubyBkcml2ZXIg YXR0YWNoZWQpCmZ4cDA6IDxJbnRlbCA4MjU1Ny84LzkgRXRoZXJFeHByZXNzIFByby8xMDAoQikg RXRoZXJuZXQ+IHBvcnQgMHgyODAwLTB4MjgzZiBtZW0gMHhjNGUwMDAwMC0weGM0ZWZmZmZmLDB4 YzRmZmUwMDAtMHhjNGZmZWZmZiBpcnEgMTAgYXQgZGV2aWNlIDMuMCBvbiBwY2kwCmZ4cDA6IEV0 aGVybmV0IGFkZHJlc3MgMDA6MDg6MDI6YTM6ZmY6ODIKbWlpYnVzMDogPE1JSSBidXM+IG9uIGZ4 cDAKaW5waHkwOiA8aTgyNTU1IDEwLzEwMCBtZWRpYSBpbnRlcmZhY2U+IG9uIG1paWJ1czAKaW5w aHkwOiAgMTBiYXNlVCwgMTBiYXNlVC1GRFgsIDEwMGJhc2VUWCwgMTAwYmFzZVRYLUZEWCwgYXV0 bwpmeHAxOiA8SW50ZWwgODI1NTcvOC85IEV0aGVyRXhwcmVzcyBQcm8vMTAwKEIpIEV0aGVybmV0 PiBwb3J0IDB4Mjg0MC0weDI4N2YgbWVtIDB4YzRjMDAwMDAtMHhjNGNmZmZmZiwweGM0ZGZmMDAw LTB4YzRkZmZmZmYgaXJxIDExIGF0IGRldmljZSA0LjAgb24gcGNpMApmeHAxOiBFdGhlcm5ldCBh ZGRyZXNzIDAwOjA4OjAyOmEzOmZmOjgzCm1paWJ1czE6IDxNSUkgYnVzPiBvbiBmeHAxCmlucGh5 MTogPGk4MjU1NSAxMC8xMDAgbWVkaWEgaW50ZXJmYWNlPiBvbiBtaWlidXMxCmlucGh5MTogIDEw YmFzZVQsIDEwYmFzZVQtRkRYLCAxMDBiYXNlVFgsIDEwMGJhc2VUWC1GRFgsIGF1dG8KaXNhYjA6 IDxQQ0ktSVNBIGJyaWRnZT4gYXQgZGV2aWNlIDE1LjAgb24gcGNpMAppc2EwOiA8SVNBIGJ1cz4g b24gaXNhYjAKYXRhcGNpMDogPFNlcnZlcldvcmtzIENTQjUgVURNQTEwMCBjb250cm9sbGVyPiBw b3J0IDB4MjAwMC0weDIwMGYsMHgzNzQtMHgzNzcsMHgxNzAtMHgxNzcsMHgzZjQtMHgzZjcsMHgx ZjAtMHgxZjcgYXQgZGV2aWNlIDE1LjEgb24gcGNpMAphdGEwOiBhdCAweDFmMCBpcnEgMTQgb24g YXRhcGNpMAphdGExOiBhdCAweDE3MCBpcnEgMTUgb24gYXRhcGNpMApvaGNpMDogPE9IQ0kgKGdl bmVyaWMpIFVTQiBjb250cm9sbGVyPiBtZW0gMHhjNGJmZjAwMC0weGM0YmZmZmZmIGlycSA3IGF0 IGRldmljZSAxNS4yIG9uIHBjaTAKdXNiMDogT0hDSSB2ZXJzaW9uIDEuMCwgbGVnYWN5IHN1cHBv cnQKdXNiMDogU01NIGRvZXMgbm90IHJlc3BvbmQsIHJlc2V0dGluZwp1c2IwOiA8T0hDSSAoZ2Vu ZXJpYykgVVNCIGNvbnRyb2xsZXI+IG9uIG9oY2kwCnVzYjA6IFVTQiByZXZpc2lvbiAxLjAKdWh1 YjA6ICgweDExNjYpIE9IQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2IDEuMDAvMS4wMCwgYWRk ciAxCnVodWIwOiA0IHBvcnRzIHdpdGggNCByZW1vdmFibGUsIHNlbGYgcG93ZXJlZApwY2liMTog PEFDUEkgSG9zdC1QQ0kgYnJpZGdlPiBvbiBhY3BpMApwY2liMTogY291bGQgbm90IGdldCBQQ0kg aW50ZXJydXB0IHJvdXRpbmcgdGFibGUgZm9yIFxcX1NCXy5QQ0kxIC0gQUVfTk9UX0ZPVU5ECnBj aTI6IDxBQ1BJIFBDSSBidXM+IG9uIHBjaWIxCmFjcGlfYnV0dG9uMDogPFBvd2VyIEJ1dHRvbj4g b24gYWNwaTAKYXRrYmRjMDogPEtleWJvYXJkIGNvbnRyb2xsZXIgKGk4MDQyKT4gcG9ydCAweDY0 LDB4NjAgaXJxIDEgb24gYWNwaTAKYXRrYmQwOiA8QVQgS2V5Ym9hcmQ+IGZsYWdzIDB4MSBpcnEg MSBvbiBhdGtiZGMwCmtiZDAgYXQgYXRrYmQwCnNpbzAgcG9ydCAweDJmOC0weDJmZiBpcnEgMyBv biBhY3BpMApzaW8wOiB0eXBlIDE2NTUwQSwgY29uc29sZQpmZGMwOiA8RW5oYW5jZWQgZmxvcHB5 IGNvbnRyb2xsZXIgKGk4MjA3NywgTkU3MjA2NSBvciBjbG9uZSk+IHBvcnQgMHgzZjcsMHgzZjIt MHgzZjUgaXJxIDYgZHJxIDIgb24gYWNwaTAKZmRjMDogRklGTyBlbmFibGVkLCA4IGJ5dGVzIHRo cmVzaG9sZApmZDA6IDwxNDQwLUtCIDMuNSIgZHJpdmU+IG9uIGZkYzAgZHJpdmUgMApBbGxvY2F0 aW5nIG1ham9yIzI1MCB0byAiZGV2c3RhdCIKcG10aW1lcjAgb24gaXNhMApvcm0wOiA8T3B0aW9u IFJPTXM+IGF0IGlvbWVtIDB4ZTAwMDAtMHhlN2ZmZiwweGM4MDAwLTB4Yzk3ZmYsMHhjMDAwMC0w eGM3ZmZmIG9uIGlzYTAKc2MwOiA8U3lzdGVtIGNvbnNvbGU+IG9uIGlzYTAKc2MwOiBWR0EgPDE2 IHZpcnR1YWwgY29uc29sZXMsIGZsYWdzPTB4MD4KdmdhMDogPEdlbmVyaWMgSVNBIFZHQT4gYXQg cG9ydCAweDNjMC0weDNkZiBpb21lbSAweGEwMDAwLTB4YmZmZmYgb24gaXNhMApUaW1lY291bnRl cnMgdGljayBldmVyeSAxMC4wMDAgbXNlYwphY3BpX2NwdTogdGhyb3R0bGluZyBlbmFibGVkLCAx NiBzdGVwcyAoMTAwJSB0byA2LjIlKSwgY3VycmVudGx5IDEwMC4wJQphZDA6IERNQSBsaW1pdGVk IHRvIFVETUEzMywgbm9uLUFUQTY2IGNhYmxlIG9yIGRldmljZQphZDA6IDM4MTU0TUIgPEhJVEFD SElfREsyM0VCLTQwPiBbNzc1MjAvMTYvNjNdIGF0IGF0YTAtbWFzdGVyIFVETUEzMwpNb3VudGlu ZyByb290IGZyb20gdWZzOi9kZXYvYWQwczFhCg== ------_=_NextPart_001_01C2F954.07B9BE86-- From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 12:25:22 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78D0637B401 for ; Wed, 2 Apr 2003 12:25:22 -0800 (PST) Received: from MAILSERVER.ofw.fi (ns.ofw.fi [194.111.144.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8612043FD7 for ; Wed, 2 Apr 2003 12:25:21 -0800 (PST) (envelope-from dan.naumov@ofw.fi) Received: from [172.16.161.81] by MAILSERVER.ofw.fi (NTMail 7.00.0022/NT1439.00.90501b21) with ESMTP id vibejaaa for freebsd-current@freebsd.org; Wed, 2 Apr 2003 23:24:28 +0300 Date: Wed, 2 Apr 2003 23:28:53 +0300 From: Dan Naumov To: freebsd-current@freebsd.org Message-Id: <20030402232853.4d218710.dan.naumov@ofw.fi> In-Reply-To: <20030402195640.GA318@freebie.xs4all.nl> References: <3E8B093D.4010500@liwing.de> <20030402195640.GA318@freebie.xs4all.nl> X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 20:25:22 -0000 On Wed, 2 Apr 2003 21:56:40 +0200 Wilko Bulte wrote: > On Wed, Apr 02, 2003 at 02:29:30PM -0500, John Baldwin wrote: > > > > I find an odd situation here whenever this topic comes up. One the > > one hand, people are always wanting to split the entire base system > > up into small packages for each little piece of the base. On the > > other hand, one of FreeBSD's selling points in real-world > > environments is that it doesn't have a bunch of little packages for > > the base system like Linux distros. Do people really prefer > > something like having rpm's for /bin/ps to having one lump base dist > > for all of /bin, /sbin, etc.? > > One of the worst mis-features of Linux in my book. I think being able to update just about ANYTHING, except the kernel without the need for a reboot is one of the best features of Linux and actual advantages it has over FreeBSD. Sincerely, -- Dan Naumov From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 12:32:37 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C072437B401; Wed, 2 Apr 2003 12:32:37 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id C029E43FB1; Wed, 2 Apr 2003 12:32:36 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h32KWZs70224; Wed, 2 Apr 2003 15:32:35 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Wed, 2 Apr 2003 15:32:35 -0500 (EST) From: Jeff Roberson To: Terry Lambert In-Reply-To: <3E8B03E6.36871704@mindspring.com> Message-ID: <20030402152516.J64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Alexander Leidinger cc: csujun@21cn.com cc: Robert Watson cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 20:32:38 -0000 On Wed, 2 Apr 2003, Terry Lambert wrote: > Robert Watson wrote: > > You should notice marked interactivity and UI latency improvements with > > threaded GUI apps over libc_r because GUI threads will generally no longer > > be blocked when disk I/O and blocking I/O occurs. For example, > > applications like Open Office, Netscape, et al, really get a lot better > > with 1:1. Likewise, non-interactive applications that are disk > > I/O-intensive, such as mysql, will also perform substantially better > > because a thread that hits blocking using an interface that doesn't > > support non-blocking I/O (such as the file system) won't clog up the > > application. > > Is the disk I/O really that big of an issue? All writes will > be on underlying non-blocking descriptors; I guess you are > saying that the interleaved I/O is more important, further > down the system call interface than the top, and this becomes > an issue? UNIX distinguishes between short term and long term blocking calls. Non blocking io only avoids blocking for indeterminate periods of time. The 20ms or so you're paying per IO on an IDE system is 20ms that no other threads can run. This makes a difference. > It seems to me that maybe the correct fix for this is to use > AIO instead of non-blocking I/O, then? Our AIO implementation needs some rethinking. I'm not sure how effecient it actually is. > The GUI thread issues are something I hadn't considered; I > don't generally think of user space CPU intensive operations > like that, but I guess it has to be rendered some time. 8-). > > Has anyone tried compiling X11 to use libthr? > > Also, any ETA on the per process signal mask handing bug in > libthr? Might not be safe to convert everything up front, in > a rush of eager enthusiasm... Which bug is that? I'm not aware of it. From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 12:33:20 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEF5737B401 for ; Wed, 2 Apr 2003 12:33:20 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60B3743FBD for ; Wed, 2 Apr 2003 12:33:19 -0800 (PST) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.9/8.12.9) with ESMTP id h32KXIik001072; Wed, 2 Apr 2003 22:33:18 +0200 (CEST) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.9/8.12.9/Submit) id h32KXIYt001071; Wed, 2 Apr 2003 22:33:18 +0200 (CEST) Date: Wed, 2 Apr 2003 22:33:18 +0200 From: Wilko Bulte To: Dan Naumov Message-ID: <20030402203318.GB971@freebie.xs4all.nl> References: <3E8B093D.4010500@liwing.de> <20030402195640.GA318@freebie.xs4all.nl> <20030402232853.4d218710.dan.naumov@ofw.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030402232853.4d218710.dan.naumov@ofw.fi> User-Agent: Mutt/1.4i X-OS: FreeBSD 4.8-RC X-PGP: finger wilko@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 20:33:21 -0000 On Wed, Apr 02, 2003 at 11:28:53PM +0300, Dan Naumov wrote: > On Wed, 2 Apr 2003 21:56:40 +0200 > Wilko Bulte wrote: > > > On Wed, Apr 02, 2003 at 02:29:30PM -0500, John Baldwin wrote: > > > > > > I find an odd situation here whenever this topic comes up. One the > > > one hand, people are always wanting to split the entire base system > > > up into small packages for each little piece of the base. On the > > > other hand, one of FreeBSD's selling points in real-world > > > environments is that it doesn't have a bunch of little packages for > > > the base system like Linux distros. Do people really prefer > > > something like having rpm's for /bin/ps to having one lump base dist > > > for all of /bin, /sbin, etc.? > > > > One of the worst mis-features of Linux in my book. > > I think being able to update just about ANYTHING, except the kernel > without the need for a reboot is one of the best features of Linux and > actual advantages it has over FreeBSD. Then go and run Linux. I like my FreeBSD bikeshed better ;) -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 12:35:28 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id 2ACFE37B401; Wed, 2 Apr 2003 12:35:28 -0800 (PST) Date: Wed, 2 Apr 2003 14:35:28 -0600 From: Juli Mallett To: Jeff Roberson Message-ID: <20030402143527.A96165@FreeBSD.org> References: <3E8B03E6.36871704@mindspring.com> <20030402152516.J64602-100000@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030402152516.J64602-100000@mail.chesapeake.net>; from jroberson@chesapeake.net on Wed, Apr 02, 2003 at 03:32:35PM -0500 Organisation: The FreeBSD Project X-Alternate-Addresses: , , , , X-Towel: Yes X-Negacore: Yes X-Title: Code Maven X-Authentication-Warning: localhost: juli pwned teh intarweb cc: Robert Watson cc: Alexander Leidinger cc: csujun@21cn.com cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 20:35:28 -0000 * De: Jeff Roberson [ Data: 2003-04-02 ] [ Subjecte: Re: libthr and 1:1 threading. ] > On Wed, 2 Apr 2003, Terry Lambert wrote: > > Also, any ETA on the per process signal mask handing bug in > > libthr? Might not be safe to convert everything up front, in > > a rush of eager enthusiasm... > > Which bug is that? I'm not aware of it. I think Terry is referring to the Uncertainty & Doubt as if it were a bug over the lack of a process sigmask (moved into the threads), as raised by the M:N group. -- juli mallett. email: jmallett@freebsd.org; aim: bsdflata; efnet: juli; From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 12:39:31 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F15A37B401 for ; Wed, 2 Apr 2003 12:39:31 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 7078443FE0 for ; Wed, 2 Apr 2003 12:39:30 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 12243 invoked by uid 1000); 2 Apr 2003 20:39:30 -0000 Date: Wed, 2 Apr 2003 12:39:30 -0800 (PST) From: Nate Lawson To: current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: mbuf LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 20:39:31 -0000 I was testing some changes to make fxp MPSAFE and got a LOR in allocating the mbuf cluster and then finally a panic when trying to dereference the cluster header. Is the mbuf system MPSAFE? Is it ok to call m_getcl with a device lock held (but not Giant)? The lock reversal was: 1. fxp softc lock, 2. Giant. Traceback: zalloc... malloc() mb_pop_cont() mb_alloc() m_getcl() fxp_add_rfabuf() fxp_intr_body() fxp_intr() -- locks fxp softc -Nate From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 12:42:41 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5611937B405 for ; Wed, 2 Apr 2003 12:42:41 -0800 (PST) Received: from web40306.mail.yahoo.com (web40306.mail.yahoo.com [66.218.78.85]) by mx1.FreeBSD.org (Postfix) with SMTP id AD8B343FBF for ; Wed, 2 Apr 2003 12:42:40 -0800 (PST) (envelope-from m_evmenkin@yahoo.com) Message-ID: <20030402204240.7293.qmail@web40306.mail.yahoo.com> Received: from [165.193.27.35] by web40306.mail.yahoo.com via HTTP; Wed, 02 Apr 2003 12:42:40 PST Date: Wed, 2 Apr 2003 12:42:40 -0800 (PST) From: Maksim Yevmenkin Re: IBM T30 USB issue: kernel: uhub2: device problem, disabling port 1 To: mobile@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: current@freebsd.org Subject: Re: IBM T30 USB issue: kernel: uhub2: device problem, disabling X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 20:42:41 -0000 Dear Hackers, [ for archive purposes ] all the USB stack debug traces are available at http://www.geocities.com/m_evmenkin/usb/ i also managed to get USB dumps from W2K that runs on the same laptop. http://www.geocities.com/m_evmenkin/usb/USB_HUB.LOG trace when W2K attach the second hub inside the docking station http://www.geocities.com/m_evmenkin/usb/BT3C_USB.LOG trace when W2K attaches the device i plug into hub i tried the following with out any success 1) use polling for uhci(4) (just to make sure we are not missing interrupt or something like that). i did not make any difference even when i set polling interval to very small value. 2) increase the number of retries, i.e. i tried to call usbd_new_device in a loop from uhub_explore. 3) increase various time constants (power up time etc.) 4) i even went crazy and re-wrote the uhub_explore() function to do very similar (to Linux) things, i.e. all these port debounce stuff etc. it did not work :( one thing i noticed is that device will either work right away or will not work at all. it does not matter how many tries you have. at this point i do not know what to do. i have sent e-mail to Lennart but did not receive any reply yet. if any USB expert care to comment i'm all ears :) thanks, max > On Tue, Apr 01, 2003 at 10:02:47AM -0800, Lee Damon wrote: > > >> When I try to activate a Bluetooth USB device, I get the following >> error: >> Apr 1 09:57:26 tylendel kernel: uhub2: device problem, disabling >> port 1 >> >> I am reasonably convinced it isn't a problem with the bluetooth daughter >> card (but can be convinced otherwise, of course). > > > > Additional hints on this can be found in the freebsd-mobile archive, > look for posts were the topic contains 'Bluetooth on IBM T30' which are > about a week old. > > This is a problem that exists for some time, and I am also willing to > help fix it. It is not specific for IBM T30, but happens on a varety of > laptops, and probably as well on desktops that have an usb hub connected. > > Also, I get the same error on my T30 when I resume it from suspend mode > with 4.8 Prerelease, then the usb mouse dies. This did NOT happen with > a 4.7 stable built some time around december 2002. But then I have no > idea if this is related to the above problem. > > kind regards, t. __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 12:43:27 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE1CF37B401 for ; Wed, 2 Apr 2003 12:43:27 -0800 (PST) Received: from mailout10.sul.t-online.com (mailout10.sul.t-online.com [194.25.134.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01E2E43FB1 for ; Wed, 2 Apr 2003 12:43:20 -0800 (PST) (envelope-from der_julian@web.de) Received: from fwd02.sul.t-online.de by mailout10.sul.t-online.com with smtp id 190p4n-0006bZ-01; Wed, 02 Apr 2003 22:43:17 +0200 Received: from jmmr.no-ip.com (520088592922-0001@[80.135.63.100]) by fmrl02.sul.t-online.com with esmtp id 190p4b-12r4AiC; Wed, 2 Apr 2003 22:43:05 +0200 Received: from jmmr.no-ip.com (blitz@localhost [127.0.0.1]) by jmmr.no-ip.com (8.12.8/8.12.8) with ESMTP id h32Kgmo8061309 for ; Wed, 2 Apr 2003 22:42:53 +0200 (CEST) (envelope-from der_julian@web.de) Received: (from blitz@localhost) by jmmr.no-ip.com (8.12.8/8.12.8/Submit) id h32KgiQx061306 for current@freebsd.org; Wed, 2 Apr 2003 22:42:44 +0200 (CEST) (envelope-from der_julian@web.de) X-Authentication-Warning: jmmr.no-ip.com: blitz set sender to der_julian@web.de using -f From: "Julian St." To: FreeBSD-current In-Reply-To: <20030402232853.4d218710.dan.naumov@ofw.fi> References: <3E8B093D.4010500@liwing.de> <20030402195640.GA318@freebie.xs4all.nl> <20030402232853.4d218710.dan.naumov@ofw.fi> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-jR+pIfM9TgoxQtZUMYNw" Organization: Message-Id: <1049316161.61181.2.camel@jmmr.no-ip.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 02 Apr 2003 22:42:43 +0200 X-Sender: 520088592922-0001@t-dialin.net Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: der_julian@web.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 20:43:28 -0000 --=-jR+pIfM9TgoxQtZUMYNw Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Am Mi, 2003-04-02 um 22.28 schrieb Dan Naumov: > I think being able to update just about ANYTHING, except the kernel > without the need for a reboot is one of the best features of Linux and > actual advantages it has over FreeBSD. I see no real barriers at updating while running FreeBSD in comparison to GNU/Linux. -- Julian Stecklina Have I made my point yet? --=-jR+pIfM9TgoxQtZUMYNw Content-Type: application/pgp-signature; name=signature.asc Content-Description: Dies ist ein digital signierter Nachrichtenteil -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQA+i0tANdiNDtZbKrURAkhNAJ9jw8aWBeDt+VmiYJhOQs1fwQ9g2wCdGirZ S6M0nRgvm6ufGIxL8UM2hZ4= =qGiF -----END PGP SIGNATURE----- --=-jR+pIfM9TgoxQtZUMYNw-- From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 12:46:57 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38A8037B401 for ; Wed, 2 Apr 2003 12:46:57 -0800 (PST) Received: from dsl093-019-250.msp1.dsl.speakeasy.net (dsl093-019-250.msp1.dsl.speakeasy.net [66.93.19.250]) by mx1.FreeBSD.org (Postfix) with SMTP id 5C32943F85 for ; Wed, 2 Apr 2003 12:46:56 -0800 (PST) (envelope-from peter@dsl093-019-250.msp1.dsl.speakeasy.net) Received: (qmail 55046 invoked by uid 1008); 2 Apr 2003 20:46:55 -0000 Date: Wed, 2 Apr 2003 14:46:55 -0600 From: Peter Schultz To: Warner Losh Message-ID: <20030402144655.A54742@jocose.org> References: <3E8AED1B.10606@jocose.org> <200304021727.h32HR4A8047926@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200304021727.h32HR4A8047926@harmony.village.org>; from imp@harmony.village.org on Wed, Apr 02, 2003 at 10:27:04AM -0700 cc: current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 20:46:57 -0000 On Wed, Apr 02, 2003 at 10:27:04AM -0700, Warner Losh wrote: > In message <3E8AED1B.10606@jocose.org> Peter Schultz writes: > : I hope that core will approve removing sendmail from FreeBSD-CURRENT. > > Request denied. > > 1) you made no case for it: Everybdoy knows this is a contentious > issue, yet no reasons were given. > 2) You cc'd core and a public mailing list. Don't ever do that again. Duly noted. > 3) Get consensus on arch@ first. If you can't, then chances are good > that there won't be support for this. Be sure to include how basic > systems will do email, and be prepared to supply patches to the > install system. > I'll try one list at a time then. 1) Coordination between gshapiro@, as the apparent src tree maintainer, and dinoex@, as with the port, to prepare sendmail for it's switch. 2) Find out how NetBSD is solving not having a mailer. Anyone here know, or have a friend that can help? 3) Notify relevant ports maintainers of the impending change. 4) Discuss where to present this during installation, implement. I know that I cannot fix this problem by myself, so I kindly ask for your assistance. I do not endorse the "parting out" of FreeBSD either, only to remove it's dependance on sendmail. I think we can all see how this is related to perl, where a lot of people are going to have it one way or the other, they might as well have it with the flexibilty and ease-of-use from using ports. Pete... From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 12:49:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA19B37B401; Wed, 2 Apr 2003 12:49:07 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD02143FAF; Wed, 2 Apr 2003 12:49:06 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h32Kn6c80551; Wed, 2 Apr 2003 15:49:06 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Wed, 2 Apr 2003 15:49:06 -0500 (EST) From: Jeff Roberson To: Juli Mallett In-Reply-To: <20030402143527.A96165@FreeBSD.org> Message-ID: <20030402154406.N64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Alexander Leidinger cc: csujun@21cn.com cc: Robert Watson cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 20:49:08 -0000 On Wed, 2 Apr 2003, Juli Mallett wrote: > * De: Jeff Roberson [ Data: 2003-04-02 ] > [ Subjecte: Re: libthr and 1:1 threading. ] > > On Wed, 2 Apr 2003, Terry Lambert wrote: > > > Also, any ETA on the per process signal mask handing bug in > > > libthr? Might not be safe to convert everything up front, in > > > a rush of eager enthusiasm... > > > > Which bug is that? I'm not aware of it. > > I think Terry is referring to the Uncertainty & Doubt as if it were > a bug over the lack of a process sigmask (moved into the threads), > as raised by the M:N group. POSIX specifically says that the signal mask is per thread. I'd be very surprised if the 1:1 sigmask/sigpending stuff was wrong. I don't think signal handling in M:N has really been totally worked out. Their concerns were more like 'how do we do this given the new signal restructuring' Perhaps I should start quoting posix. I wonder what my legal rights are given the copyright. hm.. Cheers, Jeff From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 12:49:28 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D25BF37B401 for ; Wed, 2 Apr 2003 12:49:28 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFAE643F85 for ; Wed, 2 Apr 2003 12:49:27 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.9/8.12.9) with SMTP id h32KnnYY038534 for ; Wed, 2 Apr 2003 15:49:49 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 2 Apr 2003 15:49:48 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Something in NFS server calling vrele() not vput()? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 20:49:29 -0000 Unfortunately, I don't have too much information here. The scenario is as follows: cboss: NFS file/build server crash2: NFS diskless client I built world on cboss; I then did installworld in crash2. I intended to installworld to a DESTDIR on a local disk on crash2, but I failed to mount it first, so the installworld had both the source and target in NFS. When I realizes this had happened, I proceeded to rm -Rf the DESTDIR tree. Shortly thereafter, rm -Rf hung on a vnode lock, and other processes started to stack up going up the directory tree. I have a little debugging information below that may be relevant--show lockedvnods shoes two directories where the locks are held by rm (0x40a25a0), a later ls (0xc48bd2d0). The last there entries are worring because the refcounts on each of these vnodes is 0, and the VI_FREE flag is set. Earlier in the debugging session, the VI_FREE flag wasn't set, so presumably the vnode was being free'd following a removal (not unlikely with installs, renames, and removals). Interestingly, the last three entries in the locked vnode list were apparently grabbed by the nfs daemon. Unfortunately, we lost of the pid entry in the lock structure so I can't tell if the thread pointer is stale and the struct thread has been reused or not. I suspect given that the nfsd thread pool is pretty much static that the locks were indeed grabbed by NFS, so some NFS operation may be calling vrele() instead of vput() (or the like). Alternatively, perhaps there's a race somewhere during ufs_inactive() between it and an NFS operation? Any other thoughts would be welcome; unfortunately, no core dump is available. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories db> show lockedvnods Locked vnodes 0xc5a2bc8c: tag ufs, type VDIR, usecount 3, writecount 0, refcount 1, flags (VV_OBJBUF), lock type ufs: EXCL (count 1) by thread 0xc48bd2d0 ino 619588, on dev ad0s1g (4, 18) 0xc4fbd6d8: tag ufs, type VDIR, usecount 4, writecount 0, refcount 1, flags (VV_OBJBUF), lock type ufs: EXCL (count 1) by thread 0xc40a25a0 with 1 pending ino 1129851, on dev ad0s1g (4, 18) 0xc4d456d8: tag ufs, type VREG, usecount 1, writecount 0, refcount 0, flags (VV_OBJBUF), lock type ufs: EXCL (count 1) by thread 0xc3f78c30 with 1 pending ino 1129935, on dev ad0s1g (4, 18) 0xc5046248: tag ufs, type VREG, usecount 0, writecount 0, refcount 0, flags (VI_FREE|VV_OBJBUF), lock type ufs: EXCL (count 1) by thread 0xc3f78c30 ino 1215822, on dev ad0s1g (4, 18) 0xc41fe920: tag ufs, type VREG, usecount 0, writecount 0, refcount 0, flags (VI_FREE|VV_OBJBUF), lock type ufs: EXCL (count 1) by thread 0xc3f78c30 ino 1216038, on dev ad0s1g (4, 18) db> cont -> cboss# db> trace 13805 mi_switch(c40a25a0,50,c5c4536c,dba91c40,0) at mi_switch+0x181 msleep(c4d45794,c058a2a0,50,c04fabf4,0) at msleep+0x43c acquire(dba919d0,1000040,600,689bd73c,c40a25a0) at acquire+0xa0 lockmgr(c4d45794,1010002,c4d456d8,c40a25a0,dba919ec) at lockmgr+0x3f7 vop_stdlock(dba91a14,dba919f8,c0440778,dba91a14,dba91a38) at vop_stdlock+0x2c vop_defaultop(dba91a14,dba91a38,c036629e,dba91a14,c4603e10) at vop_defaultop+0x1 8 ufs_vnoperate(dba91a14,c4603e10,dba91a5c,c043cb34,2) at ufs_vnoperate+0x18 vn_lock(c4d456d8,10002,c40a25a0,c034ca3a,c5bd7de2) at vn_lock+0x11e vget(c4d456d8,2,c40a25a0,1064428,c40a25a0) at vget+0x100 vfs_cache_lookup(dba91b54,dba91b80,c0352122,dba91b54,20002) at vfs_cache_lookup+ 0x1ed ufs_vnoperate(dba91b54,20002,c40a25a0,dba91b0c,c40a25a0) at ufs_vnoperate+0x18 lookup(dba91c18,c46f1800,400,dba91c34,c40a25a0) at lookup+0x302 namei(dba91c18,80bd948,60,0,c40a25a0) at namei+0x20b lstat(c40a25a0,dba91d10,8,c40a25a0,2) at lstat+0x52 syscall(2f,2f,2f,80bda00,80b7040) at syscall+0x2aa Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (190, FreeBSD ELF32, lstat), eip = 0x804b45f, esp = 0xbfbff53c, ebp = 0xbfbff5c8 --- (kgdb) inspect ((struct thread *)0xc3f78c30)->td_proc.p_pid $1 = 404 (kgdb) inspect ((struct thread *)0xc3f78c30)->td_proc.p_comm $2 = "nfsd\0er", '\0' From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 12:56:08 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7B6B37B401 for ; Wed, 2 Apr 2003 12:56:08 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C9DB43F93 for ; Wed, 2 Apr 2003 12:56:08 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id 2FCF82A8A5; Wed, 2 Apr 2003 12:56:08 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Terry Lambert In-Reply-To: <3E8A9101.66FE4135@mindspring.com> Date: Wed, 02 Apr 2003 12:56:08 -0800 From: Peter Wemm Message-Id: <20030402205608.2FCF82A8A5@canning.wemm.org> cc: csujun@21cn.com cc: current@FreeBSD.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 20:56:09 -0000 Terry Lambert wrote: > Jun Su wrote: > > > [ ... 1:1 kernel threads implementation ... ] > > > > A benchmark would be interested. > > This request doesn't make sense. > > The primary performance reasoning behind a 1:1 kernel threading > implementation, relative to the user space single kernel entry > scheduler in the libc_r implementation is SMP scalability for > threaded applications. No. It gives the ability for a thread to block on a syscall without stalling the entire system. Just try using mysqld on a system using libc_r and heavy disk IO. You can't select() on a read() from disk. Thats the ultimate reason to do it. The SMP parallelism is a bonus. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 12:58:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 63EC037B401; Wed, 2 Apr 2003 12:58:04 -0800 (PST) Received: from core.zp.ua (core.zp.ua [193.108.112.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3242543FBF; Wed, 2 Apr 2003 12:58:02 -0800 (PST) (envelope-from oleg@core.zp.ua) Received: from core.zp.ua (oleg@localhost [127.0.0.1]) by core.zp.ua with ESMTPœ id h32Kvt4k078371; Wed, 2 Apr 2003 23:57:55 +0300 (EEST) (envelope-from oleg@core.zp.ua)œ Received: (from oleg@localhost) by core.zp.ua id h32Kvs6A078370; Wed, 2 Apr 2003 23:57:54 +0300 (EEST) Date: Wed, 2 Apr 2003 23:57:54 +0300 From: "Oleg V. Nauman" To: Nate Williams Message-ID: <20030402205754.GF75212@core.zp.ua> Mail-Followup-To: Nate Williams , Gregory Neil Shapiro , freebsd-current@freebsd.org References: <16011.4537.279737.406477@horsey.gshapiro.net> <16011.7467.322808.498405@emerger.yogotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <16011.7467.322808.498405@emerger.yogotech.com> User-Agent: Mutt/1.5.3i cc: Gregory Neil Shapiro cc: freebsd-current@freebsd.org Subject: Re: sendmail: no local mailer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 20:58:04 -0000 On Wed, Apr 02, 2003 at 10:26:03AM -0700, Nate Williams wrote: > > evantd> Sendmail has not been working on my system for some time now. I > > evantd> can't say exactly how long, but my guess is that it broke when I > > evantd> upgraded to RELENG_5_0. This is how sendmail is invoked (by > > evantd> default) and it's output. > > > > evantd> # sendmail -L sm-mta -bd -q30m -ODaemonPortOptions=Addr=localhost > > evantd> 451 4.0.0 No local mailer defined: Bad address > > evantd> 554 5.0.0 QueueDirectory (Q) option must be set > > > > /etc/mail/sendmail.cf is a bogus (empty?) file. One way to fix this is: > > > > cd /etc/mail > > mv sendmail.cf sendmail.cf~bogus > > make > > make restart > > This happened on one of my -stable boxes lately when doing a upgrade > using buildworld. For some (unknown) reason m4 bombed out and created > an empty .cf file. > > I fixed it by doing something similar to what was done above, although > why m4 failed is a mystery.... Some patch: --- /usr/src/etc/sendmail/Makefile.orig Wed Apr 2 23:51:19 2003 +++ /usr/src/etc/sendmail/Makefile Wed Apr 2 23:51:50 2003 @@ -1,7 +1,7 @@ # @(#)Makefile 8.19 (Berkeley) 1/14/97 # $FreeBSD: src/etc/sendmail/Makefile,v 1.21 2002/07/29 09:40:06 ru Exp $ -M4= m4 +M4= /usr/bin/m4 CHMOD= chmod ROMODE= 444 RM= rm -f > > > > Nate > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- NO37-RIPE From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 13:10:05 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C03737B404; Wed, 2 Apr 2003 13:10:05 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A13C43F75; Wed, 2 Apr 2003 13:10:04 -0800 (PST) (envelope-from eischen@pcnet1.pcnet.com) Received: from pcnet1.pcnet.com (localhost [127.0.0.1]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h32L9wBg029890; Wed, 2 Apr 2003 16:09:58 -0500 (EST) Received: from localhost (eischen@localhost)h32L9vOl029885; Wed, 2 Apr 2003 16:09:57 -0500 (EST) Date: Wed, 2 Apr 2003 16:09:57 -0500 (EST) From: Daniel Eischen To: Jeff Roberson In-Reply-To: <20030402154406.N64602-100000@mail.chesapeake.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Alexander Leidinger cc: Robert Watson cc: csujun@21cn.com cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 21:10:06 -0000 On Wed, 2 Apr 2003, Jeff Roberson wrote: > On Wed, 2 Apr 2003, Juli Mallett wrote: > > > * De: Jeff Roberson [ Data: 2003-04-02 ] > > [ Subjecte: Re: libthr and 1:1 threading. ] > > > On Wed, 2 Apr 2003, Terry Lambert wrote: > > > > Also, any ETA on the per process signal mask handing bug in > > > > libthr? Might not be safe to convert everything up front, in > > > > a rush of eager enthusiasm... > > > > > > Which bug is that? I'm not aware of it. > > > > I think Terry is referring to the Uncertainty & Doubt as if it were > > a bug over the lack of a process sigmask (moved into the threads), > > as raised by the M:N group. > > POSIX specifically says that the signal mask is per thread. I'd be very Yes, but you've moved the mask into the kernel thread, whereas in libkse threads are in the UTS. Mulitple threads can be run in one kernel thread, and the UTS doesn't want to enter the kernel to set the signal mask. -- Dan Eischen From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 13:13:12 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60BD737B401 for ; Wed, 2 Apr 2003 13:13:12 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7979843FAF for ; Wed, 2 Apr 2003 13:13:11 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.8/8.12.8) with ESMTP id h32LD9SM048853 for ; Wed, 2 Apr 2003 23:13:10 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: current@freebsd.org From: "Poul-Henning Kamp" Date: Wed, 02 Apr 2003 23:13:09 +0200 Message-ID: <48852.1049317989@critter.freebsd.dk> Subject: more robust handling of removable devices in GEOM. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 21:13:12 -0000 This commit (hopefully) improves the situation when a media is removed quickly after it appeared. (A number of people have reported this with USB devices). There are still a couple of minor races. Poul-Henning In message <200304022110.h32LA4WX029838@repoman.freebsd.org>, Poul-Henning Kamp writes: >phk 2003/04/02 13:10:04 PST > > FreeBSD src repository > > Modified files: > sys/geom geom.h geom_bsd.c geom_disk.c geom_dump.c > geom_event.c geom_int.h geom_mbr.c > geom_pc98.c > Log: > Add handling for cancelled events in the g_call_me() methods. > > Revision Changes Path > 1.53 +2 -0 src/sys/geom/geom.h > 1.44 +8 -4 src/sys/geom/geom_bsd.c > 1.65 +15 -2 src/sys/geom/geom_disk.c > 1.24 +6 -3 src/sys/geom/geom_dump.c > 1.26 +2 -0 src/sys/geom/geom_event.c > 1.19 +0 -1 src/sys/geom/geom_int.h > 1.36 +5 -2 src/sys/geom/geom_mbr.c > 1.29 +5 -2 src/sys/geom/geom_pc98.c > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 13:13:13 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C45237B401; Wed, 2 Apr 2003 13:13:13 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E37E43FAF; Wed, 2 Apr 2003 13:13:12 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0303.cvx22-bradley.dialup.earthlink.net ([209.179.199.48] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190pXc-0006n4-00; Wed, 02 Apr 2003 13:13:05 -0800 Message-ID: <3E8B51FC.63F8BE55@mindspring.com> Date: Wed, 02 Apr 2003 13:11:24 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn References: <3E8B03E6.36871704@mindspring.com> <20030402154716.GE790@starjuice.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a456960d1adceca2a30f3deb1760084ef42601a10902912494350badd9bab72f9c350badd9bab72f9c cc: Alexander Leidinger cc: csujun@21cn.com cc: Robert Watson cc: current@freebsd.org cc: Jeff Roberson Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 21:13:13 -0000 Sheldon Hearn wrote: > On (2003/04/02 07:38), Terry Lambert wrote: > > Is the disk I/O really that big of an issue? All writes will > > be on underlying non-blocking descriptors; I guess you are > > saying that the interleaved I/O is more important, further > > down the system call interface than the top, and this becomes > > an issue? > > Dude, you should really try this stuff for yourself before naysaying > performance improvements on principle. It's actually quite impressive > for desktop users (at least). I have. I can't tell if it's the scheduler quantums or the concurrency from the threads. I'm going to have to specifically write code to find out, and it may take me a while to do it; I have to figure out a way to put the user space stalls back for descriptor accesses, so the tests run on an equal footing. Right now, I have to decide whether it's worth the hassle of combining the libc_r and libthr code to do that, or if I should just drop it, and let you guys turn FreeBSD's threads into Linux. PS: My gut tells me it's not the concurrency; the resolver is the bottleneck for things like Mozilla (IMO), and it still has to stall concurrency. PPS: I'll get back to you after I size the job, and decide. -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 13:15:26 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD22137B401; Wed, 2 Apr 2003 13:15:26 -0800 (PST) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8EAE43F93; Wed, 2 Apr 2003 13:15:25 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by sccrmhc03.attbi.com (sccrmhc03) with ESMTP id <20030402211524003001vdbve>; Wed, 2 Apr 2003 21:15:25 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA18030; Wed, 2 Apr 2003 13:15:23 -0800 (PST) Date: Wed, 2 Apr 2003 13:15:22 -0800 (PST) From: Julian Elischer To: Juli Mallett In-Reply-To: <20030402143527.A96165@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Jeff Roberson cc: csujun@21cn.com cc: Robert Watson cc: current@freebsd.org cc: Alexander Leidinger Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 21:15:27 -0000 On Wed, 2 Apr 2003, Juli Mallett wrote: > * De: Jeff Roberson [ Data: 2003-04-02 ] > [ Subjecte: Re: libthr and 1:1 threading. ] > > On Wed, 2 Apr 2003, Terry Lambert wrote: > > > Also, any ETA on the per process signal mask handing bug in > > > libthr? Might not be safe to convert everything up front, in > > > a rush of eager enthusiasm... > > > > Which bug is that? I'm not aware of it. > > I think Terry is referring to the Uncertainty & Doubt as if it were > a bug over the lack of a process sigmask (moved into the threads), > as raised by the M:N group. I think this IS a problem. We need a per-process mask. to block signals that no thread is interested in. Since M:N threads do not have a kernel thread for each userland thread, there is nowhere to store this info any more. I'd be happy to have it be a per-ksegrp mask actually.. (to help deliver the signal to the right group to lower the interaction between UTS's in different groups.) From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 13:25:20 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C60D37B407; Wed, 2 Apr 2003 13:25:20 -0800 (PST) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3F8843FAF; Wed, 2 Apr 2003 13:25:18 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by sccrmhc02.attbi.com (sccrmhc02) with ESMTP id <2003040221251700200774mke>; Wed, 2 Apr 2003 21:25:18 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA18095; Wed, 2 Apr 2003 13:25:16 -0800 (PST) Date: Wed, 2 Apr 2003 13:25:15 -0800 (PST) From: Julian Elischer To: Jeff Roberson In-Reply-To: <20030402154406.N64602-100000@mail.chesapeake.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Alexander Leidinger cc: Robert Watson cc: csujun@21cn.com cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 21:25:20 -0000 On Wed, 2 Apr 2003, Jeff Roberson wrote: > On Wed, 2 Apr 2003, Juli Mallett wrote: > > > * De: Jeff Roberson [ Data: 2003-04-02 ] > > [ Subjecte: Re: libthr and 1:1 threading. ] > > > On Wed, 2 Apr 2003, Terry Lambert wrote: > > > > Also, any ETA on the per process signal mask handing bug in > > > > libthr? Might not be safe to convert everything up front, in > > > > a rush of eager enthusiasm... > > > > > > Which bug is that? I'm not aware of it. > > > > I think Terry is referring to the Uncertainty & Doubt as if it were > > a bug over the lack of a process sigmask (moved into the threads), > > as raised by the M:N group. > > POSIX specifically says that the signal mask is per thread. I'd be very > surprised if the 1:1 sigmask/sigpending stuff was wrong. I don't think > signal handling in M:N has really been totally worked out. Their concerns > were more like 'how do we do this given the new signal restructuring' > > Perhaps I should start quoting posix. I wonder what my legal rights > are given the copyright. hm.. Posix defines the interface at the 'top' of the library. In M:N threads, the process gets signals that are not blocked by any thread. There may be 10,000 threads, only 3 of which the kernel has any knowledge. The signal needs to be checked againsta a per-process mask before being routed to the UTS for forwarding to the apropriate thread. To achieve that efficiently we will have a per-process mask, and use that. 1:1 threads (and non-threaded processes) will continue to use the per-thread mask. On switching to M:N mode, we'll just clone the active thread's mask into the process mask. No biggie.. just needs code :-) When M:N threads are involved psignal() will just check against a different mask, and delivery is already handled in a different manner. The UTS will update the per-process mask as needed as only it knows what all the threads are masking (since the kernel doesn't even know what threads exist). From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 13:27:21 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC03D37B401 for ; Wed, 2 Apr 2003 13:27:21 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64EED43F75 for ; Wed, 2 Apr 2003 13:27:21 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0303.cvx22-bradley.dialup.earthlink.net ([209.179.199.48] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190plO-000209-00; Wed, 02 Apr 2003 13:27:19 -0800 Message-ID: <3E8B555E.5FCF55A6@mindspring.com> Date: Wed, 02 Apr 2003 13:25:50 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dan Naumov References: <20030402185311.599cb0d3.dan.naumov@ofw.fi> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4a7798e55920f12d9394de4d097417b48350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 21:27:22 -0000 Dan Naumov wrote: > Terry Lambert wrote: > > Because syslog is unreliable. See "BUGS" section of the man page. > > Don't you think that if syslog is unreliable, then it should be fixed ? Sure. You should definitely fix it; you'll need to figure out a way to know whether we've run out of mbufs, or can't connect to the syslogd over TCP, or are experiencing a denial of service attack, etc.. > If things are as you say, we have 2 problems: Sendmail gettings CERTs > every other day and an unreliable system logger. Would you rather just > let things be as they are ? If you insist on painting this bikeshed... Put any other mail server out there in place of Sendmail, and all you will accomplish is a different set of CERTs. Sendmail gets a bad rap because of the amount of attention that's being focussed on it. Any time there's an SSL vulnerability, for example OpenPKG-SA-2002.008, Postfix and everyone else who supports StartTLS gets hit, too. The system logger is unreliable because the transport mechanism has too many causal links where it can be attacked. I am always suspicious of people who want to replace the default MTA/MSA code, and aren't willing to do the actual work in making it possible to plug a different one in place of their own favorite: it's too much like advocacy of their favorite MTA/MSA code, if they aren't willing to make it possible for people who don't like *their* MTA/MSA to use a different one. -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 13:28:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B19CB37B401 for ; Wed, 2 Apr 2003 13:28:32 -0800 (PST) Received: from mail.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EFC143F3F for ; Wed, 2 Apr 2003 13:28:32 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 13906 invoked from network); 2 Apr 2003 21:28:39 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 2 Apr 2003 21:28:39 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.8/8.12.8) with ESMTP id h32LSTOv024079; Wed, 2 Apr 2003 16:28:30 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20030402232853.4d218710.dan.naumov@ofw.fi> Date: Wed, 02 Apr 2003 16:28:29 -0500 (EST) From: John Baldwin To: Dan Naumov cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 21:28:33 -0000 On 02-Apr-2003 Dan Naumov wrote: > On Wed, 2 Apr 2003 21:56:40 +0200 > Wilko Bulte wrote: > >> On Wed, Apr 02, 2003 at 02:29:30PM -0500, John Baldwin wrote: >> > >> > I find an odd situation here whenever this topic comes up. One the >> > one hand, people are always wanting to split the entire base system >> > up into small packages for each little piece of the base. On the >> > other hand, one of FreeBSD's selling points in real-world >> > environments is that it doesn't have a bunch of little packages for >> > the base system like Linux distros. Do people really prefer >> > something like having rpm's for /bin/ps to having one lump base dist >> > for all of /bin, /sbin, etc.? >> >> One of the worst mis-features of Linux in my book. > > > I think being able to update just about ANYTHING, except the kernel > without the need for a reboot is one of the best features of Linux and > actual advantages it has over FreeBSD. You have to reboot to do a 'make install' in src/bin/ps? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 13:36:43 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDFC437B401; Wed, 2 Apr 2003 13:36:43 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4D3543FBD; Wed, 2 Apr 2003 13:36:42 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0303.cvx22-bradley.dialup.earthlink.net ([209.179.199.48] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190puR-000463-00; Wed, 02 Apr 2003 13:36:40 -0800 Message-ID: <3E8B579B.AB82C225@mindspring.com> Date: Wed, 02 Apr 2003 13:35:23 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jens Rehsack References: <3E8B093D.4010500@liwing.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a489af54f683575533a8aae41515b63948548b785378294e88350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org cc: John Baldwin Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: config@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 21:36:44 -0000 Jens Rehsack wrote: > John Baldwin wrote: > > First, core@ is not the appropriate body for that type of request. > > Both current@ and arch@ are much better targets. Second, is > > NO_SENDMAIL + the postfix port inadequate? > > The problem I see with that is, that even a minimalistic base install > installs things like sendmail, ppp, atm-stuff, g77 and so on. > > I really think splitting the base in some sub-parts would it make much > easier to do NO_SENDMAIL on my own. So I had to remove each not required > file separately. That's no good solution. So we are back to: o breaking the base system into packages, o either pre-installed with package alternatives to allow deinstall and reinstall, OR o we are into seperately packaging all mail servers, picking the current one as default, and hacking the heck out of sysinstall to make sure there's a seperate choice item to get one installed ...all so that programs that require the ability to send local mail, many of them base systems components, can function. That's what I said in the first place. So we are agreed. The correct mailing lists for this discussion are config@freebsd.org and install@freebsd.org. I've set followups to config@freebsd.org to indicate my own bias and the total lack of space for more sysinstall code on the install floppy... -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 13:38:03 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88B6C37B405 for ; Wed, 2 Apr 2003 13:38:03 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0312143FB1 for ; Wed, 2 Apr 2003 13:38:03 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0303.cvx22-bradley.dialup.earthlink.net ([209.179.199.48] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190pvf-0004Ll-00; Wed, 02 Apr 2003 13:37:55 -0800 Message-ID: <3E8B57E1.B140A989@mindspring.com> Date: Wed, 02 Apr 2003 13:36:33 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: leafy References: <20030402160340.GA98978@leafy.idv.tw> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a489af54f683575533006f00608aa5b865548b785378294e88350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 21:38:04 -0000 leafy wrote: > On Wed, Apr 02, 2003 at 07:38:14AM -0800, Terry Lambert wrote: > > Has anyone tried compiling X11 to use libthr? > > Someone reported success with KDE, so it should serve as a sign of working X11. Not X11 clients. The X11 server. -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 13:39:00 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id 5FC5937B401; Wed, 2 Apr 2003 13:39:00 -0800 (PST) Date: Wed, 2 Apr 2003 15:39:00 -0600 From: Juli Mallett To: Terry Lambert Message-ID: <20030402153900.A3984@FreeBSD.org> References: <20030402160340.GA98978@leafy.idv.tw> <3E8B57E1.B140A989@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3E8B57E1.B140A989@mindspring.com>; from tlambert2@mindspring.com on Wed, Apr 02, 2003 at 01:36:33PM -0800 Organisation: The FreeBSD Project X-Alternate-Addresses: , , , , X-Towel: Yes X-Negacore: Yes X-Title: Code Maven X-Authentication-Warning: localhost: juli pwned teh intarweb cc: freebsd-current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 21:39:00 -0000 * De: Terry Lambert [ Data: 2003-04-02 ] [ Subjecte: Re: libthr and 1:1 threading. ] > leafy wrote: > > On Wed, Apr 02, 2003 at 07:38:14AM -0800, Terry Lambert wrote: > > > Has anyone tried compiling X11 to use libthr? > > > > Someone reported success with KDE, so it should serve as a sign of working X11. > > Not X11 clients. > > The X11 server. In any case, "compiling" there is bogus. Just replace (symlink) lc_r. -- juli mallett. email: jmallett@freebsd.org; aim: bsdflata; efnet: juli; From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 13:39:58 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E02D37B404 for ; Wed, 2 Apr 2003 13:39:58 -0800 (PST) Received: from mail.speakeasy.net (mail16.speakeasy.net [216.254.0.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BDFA43F93 for ; Wed, 2 Apr 2003 13:39:58 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 11590 invoked from network); 2 Apr 2003 21:40:06 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 2 Apr 2003 21:40:06 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.8/8.12.8) with ESMTP id h32LdsOv024110; Wed, 2 Apr 2003 16:39:55 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3E8B57E1.B140A989@mindspring.com> Date: Wed, 02 Apr 2003 16:39:54 -0500 (EST) From: John Baldwin To: Terry Lambert cc: freebsd-current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 21:39:58 -0000 On 02-Apr-2003 Terry Lambert wrote: > leafy wrote: >> On Wed, Apr 02, 2003 at 07:38:14AM -0800, Terry Lambert wrote: >> > Has anyone tried compiling X11 to use libthr? >> >> Someone reported success with KDE, so it should serve as a sign of working X11. > > Not X11 clients. > > The X11 server. Gee, I wonder if they like ran it locally on a local server? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 13:46:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E16437B401 for ; Wed, 2 Apr 2003 13:46:04 -0800 (PST) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4B4843F93 for ; Wed, 2 Apr 2003 13:46:03 -0800 (PST) (envelope-from scott_long@btc.adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h32LiZZ05544; Wed, 2 Apr 2003 13:44:35 -0800 Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [10.100.0.52]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id NAA22722; Wed, 2 Apr 2003 13:45:37 -0800 (PST) Received: from btc.adaptec.com ([10.20.80.159]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id OAA12470; Wed, 2 Apr 2003 14:45:19 -0700 (MST) Message-ID: <3E8B59EC.8090501@btc.adaptec.com> Date: Wed, 02 Apr 2003 14:45:16 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2.1) Gecko/20030206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Terry Lambert References: <20030402160340.GA98978@leafy.idv.tw> <3E8B57E1.B140A989@mindspring.com> In-Reply-To: <3E8B57E1.B140A989@mindspring.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 21:46:04 -0000 Terry Lambert wrote: > leafy wrote: > >>On Wed, Apr 02, 2003 at 07:38:14AM -0800, Terry Lambert wrote: >> >>>Has anyone tried compiling X11 to use libthr? >> >>Someone reported success with KDE, so it should serve as a sign of working X11. > > > Not X11 clients. > > The X11 server. > > -- Terry > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" The X server is not threaded: [junior] ~> ldd /usr/X11R6/bin/X /usr/X11R6/bin/X: libc.so.5 => /usr/lib/libc.so.5 (0x2806a000) That was supposed to be one of the great goals of X11R6, but it was never completed, and I believe that most of the (incomplete) work has long since been removed from XFree86. Scott From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 13:46:34 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86DEE37B401 for ; Wed, 2 Apr 2003 13:46:34 -0800 (PST) Received: from ns2.gnf.org (ns2.gnf.org [63.196.132.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E58043F75 for ; Wed, 2 Apr 2003 13:46:32 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: from EXCHCLUSTER01.lj.gnf.org (exch02.lj.gnf.org [172.25.10.20]) by ns2.gnf.org (8.12.6p2/8.12.3) with ESMTP id h32LkQ8V015368 for ; Wed, 2 Apr 2003 13:46:26 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: from roark.gnf.org ([172.25.24.15]) by EXCHCLUSTER01.lj.gnf.org with Microsoft SMTPSVC(5.0.2195.5329); Wed, 2 Apr 2003 13:46:29 -0800 Received: from roark.gnf.org (localhost [127.0.0.1]) by roark.gnf.org (8.12.9/8.12.9) with ESMTP id h32LkSNB069757 for ; Wed, 2 Apr 2003 13:46:28 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: (from gtetlow@localhost) by roark.gnf.org (8.12.9/8.12.9/Submit) id h32LkSVN069756 for current@FreeBSD.org; Wed, 2 Apr 2003 13:46:28 -0800 (PST) Date: Wed, 2 Apr 2003 13:46:28 -0800 From: Gordon Tetlow To: current@FreeBSD.org Message-ID: <20030402214628.GA69100@roark.gnf.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq" Content-Disposition: inline User-Agent: Mutt/1.4i X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-OriginalArrivalTime: 02 Apr 2003 21:46:29.0121 (UTC) FILETIME=[51511F10:01C2F961] Subject: LOR in PCM (big suprise there) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 21:46:34 -0000 --45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Just thought I would report it: lock order reversal 1st 0xc61f5940 pcm0 (sound softc) @ /local/usr.src/sys/dev/sound/pci/cmi.c:520 2nd 0xc6209e80 pcm0:play:0 (pcm channel) @ /local/usr.src/sys/dev/sound/pcm/channel.c:440 Stack backtrace: backtrace(c04e759f,c6209e80,c61a9b54,c06a2127,c06a21a5) at backtrace+0x17 witness_lock(c6209e80,8,c06a21a5,1b8,c61a9b00) at witness_lock+0x692 _mtx_lock_flags(c6209e80,0,c06a21a5,1b8,800000c1) at _mtx_lock_flags+0xb2 chn_intr(c61a9b00,c,10000,208,c61f5a40) at chn_intr+0x2f cmi_intr(c61a9c00,0,c04e258e,217,c61a43c0) at cmi_intr+0xa6 ithread_loop(c61fa980,df0f0d48,c04e23fe,314,c21c9390) at ithread_loop+0x16c fork_exit(c02e7dd0,c61fa980,df0f0d48) at fork_exit+0xc4 fork_trampoline() at fork_trampoline+0x1a --- trap 0x1, eip = 0, esp = 0xdf0f0d7c, ebp = 0 --- -gordon --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+i1o0Ru2t9DV9ZfsRAkW1AJ4kek4/YxYq9U3m90iMVujjDkOiNACglcHt P1IRDxj0VW/YASxh1h8tigo= =z2e7 -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq-- From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 13:55:03 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BEC937B429 for ; Wed, 2 Apr 2003 13:55:03 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CEB943FAF for ; Wed, 2 Apr 2003 13:55:00 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0303.cvx22-bradley.dialup.earthlink.net ([209.179.199.48] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190qC9-0000Z1-00; Wed, 02 Apr 2003 13:54:58 -0800 Message-ID: <3E8B5BE5.644EF723@mindspring.com> Date: Wed, 02 Apr 2003 13:53:41 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Schultz References: <3E8AED1B.10606@jocose.org> <3E8AEFBF.D1D640E3@mindspring.com> <3E8AFB2F.3040701@jocose.org> <3E8B01F2.B3E02FC8@mindspring.com> <3E8B0B9D.6010300@jocose.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4de10f470e868703bafba791a3e834110350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 21:55:03 -0000 Peter Schultz wrote: > Terry Lambert wrote: > > If you look over the historical cases of this discussion, > > you'll see that the answer always comes down to "make the > > system more modular, so people can replace XXX with YYY and > > quit bothering us; please send patches". 8-) 8-). > > Thanks for your help on this. I've been getting so many search results > that I've been unable to determine the exact problem myself. So, one > absolute requirement is that the system have both an mta, and an msa. > When you say msa, does this include pop&imap capabilities? MTA: Mail Transfer Agent; used for transferring mail via the SMTP protocol to other platforms over the network; this is where most security vulnerabilities surface, because the port is generally open to public attack, if people fail to use a proxy firewall. MSA: Mail Submission Agent; used for local submission of mail messages, for either later or immediate delivery by an MTA or an MDA. MDA: Mail Delivery Agent; used for delivery of mail that has been submitted via an MSA to a mail transport or to an endpoint; an MDA that delivers mail to local mailboxes is called a "Local Delivery Agent". MUA: Mail User Agent; used for interacting with an MSA and/or a Message Store; usually an MUA can do both, e.g. the program /usr/bin/mail operates "mbox" formatted message stores located in /var/mail/$USER and ~/mbox by default. MS: Message Store; an MS can be simple filesystem storage, such as a single "mbox" format file (see "MUA", above), or "maildir" format (one file per message), a POP3 or IMAP4 database protected and accessed only via a wire protocol, etc.. The MS is usually directly accessible in some form through direct file manipulation by *some* form of MUA. Minimal requirements for supporting local mail to the root user as a result of security script processing (for example) are an MUA, an MSA, and an MDA. Clear? If you decide your MS is Cyrus IMAP from ports, for example, then you will need to provide an MUA replacement for /bin/mail, minimally for reading mail sent to root, since Cyrus keeps its messages in an internalized database format not understood by /usr/bin/mail. There are other examples where an impedence mismatch is possible, of course, but you specifically mentiond POP3/IMAP4. -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 14:00:54 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C77DF37B404 for ; Wed, 2 Apr 2003 14:00:54 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13F5A43FDD for ; Wed, 2 Apr 2003 14:00:50 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0303.cvx22-bradley.dialup.earthlink.net ([209.179.199.48] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190qHl-0001xF-00; Wed, 02 Apr 2003 14:00:45 -0800 Message-ID: <3E8B5D40.56C256D9@mindspring.com> Date: Wed, 02 Apr 2003 13:59:28 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Evan Dower References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4de10f470e868703b4fc515dddff6e594350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org Subject: Re: sendmail: no local mailer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 22:00:55 -0000 Note: This should have been posted to -questions, not -current. Evan Dower wrote: > Sendmail has not been working on my system for some time now. I can't say > exactly how long, but my guess is that it broke when I upgraded to > RELENG_5_0. This is how sendmail is invoked (by default) and it's output. > > # sendmail -L sm-mta -bd -q30m -ODaemonPortOptions=Addr=localhost > 451 4.0.0 No local mailer defined: Bad address You are missing a local mailer. A local mailer is defined by a line similar to: Mlocal, P=/usr/libexec/mail.local, F=lsDFMAw5:/|@qPSXfmnz9, S=EnvFromSMT P/HdrFromL, R=EnvToL/HdrToL, T=DNS/RFC822/SMTP, A=mail.local -l in /etc/mail/sendmail.cf. Probably, you updated and failed to rebuild and install the sendmail configuration files located in /etc/mail/. > 554 5.0.0 QueueDirectory (Q) option must be set You are missing a line similar to: # queue directory O QueueDirectory=/var/spool/mqueue in /etc/mail/sendmail.cf. Probably this has the same root cause. > The same thing happens if I change "localhost" to "127.0.0.1". I > suspect that the second error (554) will disappear when I get rid > of the first one (451). Does anyone know why it might be misbehaving > like this? Pilot error. -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 14:08:16 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6B3E37B401 for ; Wed, 2 Apr 2003 14:08:16 -0800 (PST) Received: from mail.liwing.de (mail.liwing.de [213.70.188.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id D293F43FBD for ; Wed, 2 Apr 2003 14:08:14 -0800 (PST) (envelope-from rehsack@liwing.de) Received: (qmail 61158 invoked from network); 2 Apr 2003 22:08:13 -0000 Received: from stingray.liwing.de (HELO liwing.de) ([213.70.188.164]) (envelope-sender ) by mail.liwing.de (qmail-ldap-1.03) with SMTP for ; 2 Apr 2003 22:08:13 -0000 Message-ID: <3E8B5F4D.8020301@liwing.de> Date: Thu, 03 Apr 2003 00:08:13 +0200 From: Jens Rehsack Organization: LiWing IT-Services User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: config@freebsd.org References: <3E8B093D.4010500@liwing.de> <3E8B579B.AB82C225@mindspring.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: John Baldwin Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 22:08:17 -0000 Terry Lambert wrote: > Jens Rehsack wrote: > >>John Baldwin wrote: >> >>>First, core@ is not the appropriate body for that type of request. >>>Both current@ and arch@ are much better targets. Second, is >>>NO_SENDMAIL + the postfix port inadequate? >> >>The problem I see with that is, that even a minimalistic base install >>installs things like sendmail, ppp, atm-stuff, g77 and so on. >> >>I really think splitting the base in some sub-parts would it make much >>easier to do NO_SENDMAIL on my own. So I had to remove each not required >>file separately. That's no good solution. > > > > So we are back to: > > o breaking the base system into packages, As it's already done with crypto, krb5, src, ... > o either pre-installed with package alternatives to > allow deinstall and reinstall, OR No, not deinstall. Decide on first binary sysinstall, maybe with writing a template /etc/make.conf respecting the packages you didn't want. > o we are into seperately packaging all mail servers, > picking the current one as default, and hacking the > heck out of sysinstall to make sure there's a seperate > choice item to get one installed No, if someone decides not having eg. an mta (s)he should know about the risk and consequences. > ...all so that programs that require the ability to send local > mail, many of them base systems components, can function. Only if the wrapper is configured correct (eg. for mail) or not, eg. if ppp or g77 is required but not available. > That's what I said in the first place. > > So we are agreed. I meant other. Maybe now it's more clear. > The correct mailing lists for this discussion are config@freebsd.org > and install@freebsd.org. > > I've set followups to config@freebsd.org to indicate my own > bias and the total lack of space for more sysinstall code on the > install floppy... Just 2 more lists to subscribe :-) - may local folder list get slowly huge :-) Regards, Jens From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 14:09:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 336BA37B401 for ; Wed, 2 Apr 2003 14:09:32 -0800 (PST) Received: from thalia.otenet.gr (thalia.otenet.gr [195.170.0.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CFA743F75 for ; Wed, 2 Apr 2003 14:09:30 -0800 (PST) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.gr (patr530-b130.otenet.gr [212.205.244.138]) by thalia.otenet.gr (8.12.9/8.12.9) with ESMTP id h32M9PFh009455; Thu, 3 Apr 2003 01:09:26 +0300 (EEST) Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.12.8/8.12.8) with ESMTP id h32M9Ox7054120; Thu, 3 Apr 2003 01:09:24 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.gr (8.12.8/8.12.8/Submit) id h32M9O98054119; Thu, 3 Apr 2003 01:09:24 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Thu, 3 Apr 2003 01:09:24 +0300 From: Giorgos Keramidas To: Dan Naumov Message-ID: <20030402220924.GA53920@gothmog.gr> References: <3E8B093D.4010500@liwing.de> <20030402195640.GA318@freebie.xs4all.nl> <20030402232853.4d218710.dan.naumov@ofw.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030402232853.4d218710.dan.naumov@ofw.fi> cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 22:09:32 -0000 On 2003-04-02 23:28, Dan Naumov wrote: >On Wed, 2 Apr 2003 21:56:40 +0200 >Wilko Bulte wrote: >>On Wed, Apr 02, 2003 at 02:29:30PM -0500, John Baldwin wrote: >>> >>> I find an odd situation here whenever this topic comes up. One the >>> one hand, people are always wanting to split the entire base system >>> up into small packages for each little piece of the base. On the >>> other hand, one of FreeBSD's selling points in real-world >>> environments is that it doesn't have a bunch of little packages for >>> the base system like Linux distros. Do people really prefer >>> something like having rpm's for /bin/ps to having one lump base dist >>> for all of /bin, /sbin, etc.? >> >> One of the worst mis-features of Linux in my book. > > I think being able to update just about ANYTHING, except the kernel > without the need for a reboot is one of the best features of Linux and > actual advantages it has over FreeBSD. Well, this can be done in FreeBSD too. In general, you can update parts with: # cd /usr/src/some/path # make clean # make depend && make all # make install You will find that this often requires a lot of care and attention, and a whole lot of effort, just to avoid ending up with a mess. I'm positively sure that the same sort of care should be used when upgrading parts of a Linux system too. After 6 years of being a Slackware user who upgraded everything by compiling tarballs, apart from the occasional libc version which I installed as a precompiled package, I can tell you it felt like walking on a slippery slope a lot of the time :-) It's good to be able to upgrade a "base system" in one fell swoop. At least, it's good to me. - Giorgos From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 14:18:28 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33F8E37B401; Wed, 2 Apr 2003 14:18:28 -0800 (PST) Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1246143FB1; Wed, 2 Apr 2003 14:18:25 -0800 (PST) (envelope-from nate@yogotech.com) Received: from emerger.yogotech.com (emerger.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3p2/8.9.3) with ESMTP id PAA19620; Wed, 2 Apr 2003 15:18:18 -0700 (MST) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by emerger.yogotech.com (8.12.8/8.12.8) id h32MII3d000684; Wed, 2 Apr 2003 15:18:18 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16011.25002.138504.661813@emerger.yogotech.com> Date: Wed, 2 Apr 2003 15:18:18 -0700 To: "Oleg V. Nauman" In-Reply-To: <20030402205754.GF75212@core.zp.ua> References: <16011.4537.279737.406477@horsey.gshapiro.net> <16011.7467.322808.498405@emerger.yogotech.com> <20030402205754.GF75212@core.zp.ua> X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid cc: Nate Williams cc: Gregory Neil Shapiro cc: freebsd-current@freebsd.org Subject: Re: sendmail: no local mailer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Nate Williams List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 22:18:28 -0000 > > > evantd> Sendmail has not been working on my system for some time now. I > > > evantd> can't say exactly how long, but my guess is that it broke when I > > > evantd> upgraded to RELENG_5_0. This is how sendmail is invoked (by > > > evantd> default) and it's output. > > > > > > evantd> # sendmail -L sm-mta -bd -q30m -ODaemonPortOptions=Addr=localhost > > > evantd> 451 4.0.0 No local mailer defined: Bad address > > > evantd> 554 5.0.0 QueueDirectory (Q) option must be set > > > > > > /etc/mail/sendmail.cf is a bogus (empty?) file. One way to fix this is: > > > > > > cd /etc/mail > > > mv sendmail.cf sendmail.cf~bogus > > > make > > > make restart > > > > This happened on one of my -stable boxes lately when doing a upgrade > > using buildworld. For some (unknown) reason m4 bombed out and created > > an empty .cf file. > > > > I fixed it by doing something similar to what was done above, although > > why m4 failed is a mystery.... > > Some patch: > > --- /usr/src/etc/sendmail/Makefile.orig Wed Apr 2 23:51:19 2003 > +++ /usr/src/etc/sendmail/Makefile Wed Apr 2 23:51:50 2003 > @@ -1,7 +1,7 @@ > # @(#)Makefile 8.19 (Berkeley) 1/14/97 > # $FreeBSD: src/etc/sendmail/Makefile,v 1.21 2002/07/29 09:40:06 ru Exp $ > > -M4= m4 > +M4= /usr/bin/m4 > CHMOD= chmod > ROMODE= 444 > RM= rm -f > This shouldn't be necessary, since m4 is in the path in buildworld, is it not? Otherwise, we wouldn't be able to run make, cc, or any other tools. Nate From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 14:20:02 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0B7E37B401 for ; Wed, 2 Apr 2003 14:20:02 -0800 (PST) Received: from mail.speakeasy.net (mail15.speakeasy.net [216.254.0.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2312243F93 for ; Wed, 2 Apr 2003 14:20:02 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 10244 invoked from network); 2 Apr 2003 22:20:09 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 2 Apr 2003 22:20:09 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.8/8.12.8) with ESMTP id h32MJxOv024263; Wed, 2 Apr 2003 17:19:59 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3E8B5D40.56C256D9@mindspring.com> Date: Wed, 02 Apr 2003 17:19:59 -0500 (EST) From: John Baldwin To: Terry Lambert cc: freebsd-current@freebsd.org Subject: Re: sendmail: no local mailer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 22:20:03 -0000 On 02-Apr-2003 Terry Lambert wrote: > Note: This should have been posted to -questions, not -current. Please read the other replies before sending your own. His sendmail.cf was empty and the problem was quickly diagnosed and fixed a while ago. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 14:30:30 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9751C37B401; Wed, 2 Apr 2003 14:30:30 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CF1643FA3; Wed, 2 Apr 2003 14:30:29 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h32MUKf48719; Wed, 2 Apr 2003 17:30:20 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Wed, 2 Apr 2003 17:30:20 -0500 (EST) From: Jeff Roberson To: Julian Elischer In-Reply-To: Message-ID: <20030402172900.I64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Juli Mallett cc: Alexander Leidinger cc: csujun@21cn.com cc: Robert Watson cc: current@FreeBSD.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 22:30:30 -0000 On Wed, 2 Apr 2003, Julian Elischer wrote: > > > On Wed, 2 Apr 2003, Juli Mallett wrote: > > > * De: Jeff Roberson [ Data: 2003-04-02 ] > > [ Subjecte: Re: libthr and 1:1 threading. ] > > > On Wed, 2 Apr 2003, Terry Lambert wrote: > > > > Also, any ETA on the per process signal mask handing bug in > > > > libthr? Might not be safe to convert everything up front, in > > > > a rush of eager enthusiasm... > > > > > > Which bug is that? I'm not aware of it. > > > > I think Terry is referring to the Uncertainty & Doubt as if it were > > a bug over the lack of a process sigmask (moved into the threads), > > as raised by the M:N group. > > I think this IS a problem. We need a per-process mask. > to block signals that no thread is interested in. > Since M:N threads do not have a kernel thread for each userland thread, > there is nowhere to store this info any more. > Then set the mask to be the same on all threads in the process. The mask is set in swapcontext though so it seems reasonable to me that it is atomically updated when you schedule a new user thread on a kse. > I'd be happy to have it be a per-ksegrp mask actually.. > (to help deliver the signal to the right group to lower the interaction > between UTS's in different groups.) > From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 14:35:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A89737B404 for ; Wed, 2 Apr 2003 14:35:32 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 690D143FA3 for ; Wed, 2 Apr 2003 14:35:31 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.9/8.12.9) with ESMTP id h32MZSMS008702 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 2 Apr 2003 17:35:28 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h32MZNp31130; Wed, 2 Apr 2003 17:35:23 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16011.26027.758879.203450@grasshopper.cs.duke.edu> Date: Wed, 2 Apr 2003 17:35:23 -0500 (EST) To: Nate Lawson In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: current@freebsd.org Subject: Re: mbuf LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 22:35:32 -0000 Nate Lawson writes: > I was testing some changes to make fxp MPSAFE and got a LOR in allocating > the mbuf cluster and then finally a panic when trying to dereference the > cluster header. Is the mbuf system MPSAFE? Is it ok to call m_getcl > with a device lock held (but not Giant)? > > The lock reversal was: 1. fxp softc lock, 2. Giant. > > Traceback: > zalloc... > malloc() > mb_pop_cont() > mb_alloc() > m_getcl() > fxp_add_rfabuf() > fxp_intr_body() > fxp_intr() -- locks fxp softc I thought that this had been fixed. Which zalloc() exactly? Drew From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 14:36:56 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BA5A37B401; Wed, 2 Apr 2003 14:36:56 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id D80A843FA3; Wed, 2 Apr 2003 14:36:55 -0800 (PST) (envelope-from eischen@pcnet1.pcnet.com) Received: from pcnet1.pcnet.com (localhost [127.0.0.1]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h32MahBg011853; Wed, 2 Apr 2003 17:36:44 -0500 (EST) Received: from localhost (eischen@localhost)h32MahlH011849; Wed, 2 Apr 2003 17:36:43 -0500 (EST) Date: Wed, 2 Apr 2003 17:36:43 -0500 (EST) From: Daniel Eischen To: Jeff Roberson In-Reply-To: <20030402172900.I64602-100000@mail.chesapeake.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Robert Watson cc: Julian Elischer cc: Alexander Leidinger cc: csujun@21cn.com cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 22:36:56 -0000 On Wed, 2 Apr 2003, Jeff Roberson wrote: > On Wed, 2 Apr 2003, Julian Elischer wrote: > > > > > > > On Wed, 2 Apr 2003, Juli Mallett wrote: > > > > > * De: Jeff Roberson [ Data: 2003-04-02 ] > > > [ Subjecte: Re: libthr and 1:1 threading. ] > > > > On Wed, 2 Apr 2003, Terry Lambert wrote: > > > > > Also, any ETA on the per process signal mask handing bug in > > > > > libthr? Might not be safe to convert everything up front, in > > > > > a rush of eager enthusiasm... > > > > > > > > Which bug is that? I'm not aware of it. > > > > > > I think Terry is referring to the Uncertainty & Doubt as if it were > > > a bug over the lack of a process sigmask (moved into the threads), > > > as raised by the M:N group. > > > > I think this IS a problem. We need a per-process mask. > > to block signals that no thread is interested in. > > Since M:N threads do not have a kernel thread for each userland thread, > > there is nowhere to store this info any more. > > > > Then set the mask to be the same on all threads in the process. The mask > is set in swapcontext though so it seems reasonable to me that it is > atomically updated when you schedule a new user thread on a kse. Jeff, are you _listening_ to us? We've said multiple times that the UTS does not enter the kernel when performing thread switches. The UTS does NOT use setcontext(), getcontext(), or swapcontext(). -- Dan Eischen From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 14:41:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AF3E37B401; Wed, 2 Apr 2003 14:41:04 -0800 (PST) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F9E443F85; Wed, 2 Apr 2003 14:41:03 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0303.cvx22-bradley.dialup.earthlink.net ([209.179.199.48] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190quc-0002cX-00; Wed, 02 Apr 2003 14:40:55 -0800 Message-ID: <3E8B66A8.7EB82D40@mindspring.com> Date: Wed, 02 Apr 2003 14:39:36 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Robert Watson References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a40307442bcc94c3cac57e3e2577b8a6d9a8438e0f32a48e08350badd9bab72f9c350badd9bab72f9c cc: Alexander Leidinger cc: csujun@21cn.com cc: current@freebsd.org cc: Jeff Roberson Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 22:41:04 -0000 Robert Watson wrote: > On Wed, 2 Apr 2003, Terry Lambert wrote: > > Is the disk I/O really that big of an issue? All writes will be on > > underlying non-blocking descriptors; I guess you are saying that the > > interleaved I/O is more important, further down the system call > > interface than the top, and this becomes an issue? > > The I/O issue is a big deal for things like mysql, yes. I'm not interested in the MySQL code; I've been in that threads code, deep (made it work on AIX). There are a lot better ways to deal with MySQL's latency issues. For example, the two phase commit stall that it has is not necessary on a Soft Updates FS, but, like qmail, it does it anyway, introducing latency. But Mozilla... the only issue I could see is interleaved network I/O, but that should not be an issue; HTTP is request/response, with the lion's share of the data coming as a result of the response. In other words, the rendering engine's going to have to wait for data back from the remote server, and that's got to be the primary latency. The only way I see for disk I/O to be involved in Mozilla is in local cache? You can turn that off. > > It seems to me that maybe the correct fix for this is to use AIO > > instead of non-blocking I/O, then? > > Well, they're both fixes. Another issue for applications that are > threaded and may be bumping up against the system memory limits is whether > or not the whole process stalls on a page fault or memory mapping fault, > or whether it's just the thread. This is what I meant by "deeper in the system calll layer". IMO, if you are stalled on something like this on an async fd, then it should queue the fault anyway, and return to user space for the next request. This may just be a bug in the kernel processing of demand faults on vnodes associated with async fd's (FWIW, System V and Solaris both queue the fault for kernel processing, and then return to user space). > If you have an application that is accessing a large memory mapped > file, there may be some long kernel sleeps as you pull in the pages. Again, this stall, if the fd in question is async, should be taken as system time, not as an application stall. That's a little harder, in this case, because you want to fail the pagein with the moral equivalent of "EAGAIN" plus a forced threads context switch after queing the fault request. It's a lot easier if we are talking about an explicit read() request, and not a fault, (obviously 8-)), since it should be expecting the possibility of an EAGAIN in the read() case. I guess, in this case, without an N:M upcall to indicate the forced context switch, you would just stall. This, though, doesn't seem to be an issue for Mozilla, to me. > Certainly, you can argue that the application should be structured > to make all I/O explicit and asynchronous, but for various reasons, > that's not the case :-). The mmap'ed file case is obviously not something that can be handled without an explicit contract between user and kernel for notification of the pagein temporary failure (I would use a signal for that, probably, as a gross first approximation, but per-process signal handling is currently not happy...). > Our VM and VFS subsystems may have limited concurrency from > an SMPng perspective, but probably have enough that a marked > benefit should be seen there too (you might have to wait for > another thread to block in the subsystem, but that will be a > short period of time compared to how long it takes to service > the page from disk). I would argue that this was in error, at least for explicit handing of non-blocking I/O. SVR4 and Solaris don't suffer from a stall, in the face of a missing page in a demand page-in on an async fd. The process of servicing the page-in is really independent of the process of retrying the call to see if the page is there yet. I think this is probably classifiable as a serious deficiency in the FreeBSD VM page handling, and in the decoupling of the fd and the VM backing object. I'm not sure how I'd go about fixing it; you'd have to pass the fd struct down as well, to get the flags, I think. Actually, people have wanted this for a while, in order to properly support per open instance data on cloned devices (e.g. this is needed in order to support multiple instances of VMWare on a single FreeBSD host). > > The GUI thread issues are something I hadn't considered; I don't > > generally think of user space CPU intensive operations like that, > > but I guess it has to be rendered some time. 8-). > > One of the problems I've run into is where you lose interactivity during > file saves and other disk-intensive operations in OpenOffice. Other > windows could in theory still be processing UI events, such as menu > clicks, etc, but since you're dumping several megabytes of data to disk or > doing interactive file operations that require waiting on disk latency, > you end up with a fairly nasty user experience. One way to explore this > effect is to do a side-by-side comparison of the behavior of OpenOffice > and Mozilla linked against libc_r and linuxthreads. I don't think this is enough, actually. I think you will find X11 over-the-wire stall barriers here. This is one of the reasons I asked about X11 itself. There are a lot of places in a lot of code where people call "Xsync". I don't think there's a reasonable way to avoid this, given the usual reason it's being called (e.g. to render individual widgets atomically, in order to provide for the appearance of speed from "draw individual widgets fast, rather than all widgets at the same time, slow"). > I haven't actually instrumented the kernel, but it might be quite > interesting to do so--attempt to estimate the total impact of disk > stalls on libc_r. Yes, it would be very interesting. The only approach I could come up with for this, though, is to force the libthr 1:1 code through the fd locking code from libc_r (per my previous suggestion on benchmarking) to seperate out the stall domains. I think this would be a lot of work; I'm still considering whether it really needs to be done enough for me to jump in and do it, given that the world is going to change out from under us yet again on N:M. I don't want to provide an excuse for people to complain about "lack of benchmarks showing the value of N:M over 1:1, when there are `obviously' benchmarks available" (give them two columns, and they will insist on three later). However, if we are talking disk I/O, looking again at the paging path for vnode_pager as it operates on demand-pages for not-present pages being demanded as a result of reads on async fd's, it's clear that there is some "low hanging fruit" that libthr gets by virtue of multiple blocking contexts that libc_r cannot (at present) get. 8-(. > From a purely qualitivative perspective, there is quite a noticeable > difference. I understand that. I've noticed it myself. I just can't be as sure as everyone else seems to think they are about where it is coming from. 8-) 8-). > > Has anyone tried compiling X11 to use libthr? > > Not sure. If it won a significant speedup, it would be overwhelming evidence, I think... (hint hint to some reader 8-)). > > Also, any ETA on the per process signal mask handing bug in libthr? > > Might not be safe to convert everything up front, in a rush of eager > > enthusiasm... > > Can't speculate on that, except one thing that is useful to note is that > many serious threaded applications are already being linked against > linuxthreads on FreeBSD, which arguably has poorer semantics when it comes > to signals, credentials, etc, than libthr already :-). For example, most > sites I've talked to that deploy mysql do it with linuxthreads rather than > libc_r to avoid the I/O issues, as well as avoid deadlocks. There are > enough bits of the kernel (for example, POSIX fifos) that don't handle > non-blocking operation that libc_r can stall or get into I/O buffer > deadlocks. I seem to recall someone mentioning (but can't confirm easily) > that Netscape at one point relied on using pipes to handle some sorts of > asynchronous events and wakeups within the same process. If that pipe > filled, the process would block on a pipe write for a pipe that would > never drain. I understand that. I guess I view these deadlocks as a failure to adhere to the defined API, and so would call them application bugs. And then ignore them as irrelevent. 8-). > I can think of a couple of other interesting excercises to explore the > problem -- implementing AIO "better" using the KSE primitives mixed > between userspace and kernel, reimplementing libc_r to attempt to use AIO > rather than a select loop where possible, etc. It might be quite > interesting to see whether (for a bounded number of threads, due to our > AIO implementation), a libc_r that used AIO rather than select > demonstrated some of the performance improvements we see with 1:1 via > linuxthreads (and now libthr). I would expect that if this were a paging stall issue, and you were right about where the speedup is actually coming from, that you would see the same improvements. It could be that there is just a terrible case in Mozilla, where it makes a blocking system call on a FIFO or something, alarms out of it, and continues on its way, vastly exaggerating the library differences. That's the problem with subjective differences in behaviour, rather than objective differences. I think the only think that would help there is if someone were to profile Mozilla operations that "feel faster" under libthr with both libc_r and libthr, and see where the time is actually being spent. Instead of merely noting "it feels faster". I guess that's "an exercise for the student"... maybe someone else can do it, or maybe DSL availability will fly out of SBC's rear-end into my area. 8-|. > I'm not sure if there are any open source > tools available to easily track process and thread scheduling and > blocking, but there have been several pretty useful visual analysis and > tracing tools for realtime. Some basic tools for thread tracing and > visualization exist for Mac OS X, and presumably other COTS platforms. > ktrace on FreeBSD makes some attempt to track context switches, but > without enough context (har har) to be useful for this kind of analysis. Profiling should show this out, once you prune epicycles from the scheduling. I don't think it will work at all for libthr, at this point, though. 8-(. > I've been thinking about tweaking the local scheduler to put a bit more > information into ktr and alq about blocking circumstances as well as some > way to constrain the tracing to a particular bit of the process hierarchy > with an inheritance flag of some sort. It might be quite helpful for > understanding some of the nasty threading blocking/timing issues that we > already run into with libc_r, and will continue to run into as our > threading evolves. Yes. I'd really like to see *where* the difference comes from; as I said, short of building my own libthr that incorporates parts of libc_r, I can't see how to do this on the current FreeBSD. Just knowing there's a qualitative difference "from somewhere" is useless, IMO. Maybe someone who needs a Master's degree will get the approval of their Thesis adviser, and step up and do the work we are both talking about but not doing... ;^). -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 14:42:11 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0156337B401; Wed, 2 Apr 2003 14:42:11 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAC8043FCB; Wed, 2 Apr 2003 14:42:09 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h32Mg5R55681; Wed, 2 Apr 2003 17:42:05 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Wed, 2 Apr 2003 17:42:05 -0500 (EST) From: Jeff Roberson To: Daniel Eischen In-Reply-To: Message-ID: <20030402173720.W64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Robert Watson cc: Julian Elischer cc: Alexander Leidinger cc: csujun@21cn.com cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 22:42:11 -0000 On Wed, 2 Apr 2003, Daniel Eischen wrote: > On Wed, 2 Apr 2003, Jeff Roberson wrote: > > On Wed, 2 Apr 2003, Julian Elischer wrote: > > > > > > > > > > > On Wed, 2 Apr 2003, Juli Mallett wrote: > > > > > > > * De: Jeff Roberson [ Data: 2003-04-02 ] > > > > [ Subjecte: Re: libthr and 1:1 threading. ] > > > > > On Wed, 2 Apr 2003, Terry Lambert wrote: > > > > > > Also, any ETA on the per process signal mask handing bug in > > > > > > libthr? Might not be safe to convert everything up front, in > > > > > > a rush of eager enthusiasm... > > > > > > > > > > Which bug is that? I'm not aware of it. > > > > > > > > I think Terry is referring to the Uncertainty & Doubt as if it were > > > > a bug over the lack of a process sigmask (moved into the threads), > > > > as raised by the M:N group. > > > > > > I think this IS a problem. We need a per-process mask. > > > to block signals that no thread is interested in. > > > Since M:N threads do not have a kernel thread for each userland thread, > > > there is nowhere to store this info any more. > > > > > > > Then set the mask to be the same on all threads in the process. The mask > > is set in swapcontext though so it seems reasonable to me that it is > > atomically updated when you schedule a new user thread on a kse. > > Jeff, are you _listening_ to us? We've said multiple times > that the UTS does not enter the kernel when performing thread > switches. The UTS does NOT use setcontext(), getcontext(), > or swapcontext(). I had not seen anyone mention this. If this is the case then I suggest the masks and pending sets be kept in user space. You can install blank handlers for everything so that they are kept pending until the uts has a chance to pick them up in the upcall. If you really want a process wide mask allow me to do it. The single code is quite tricky and it's already been butchered enough. I think we should discuss this a bit more first though. Cheers, Jeff From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 14:48:11 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E0FB37B404 for ; Wed, 2 Apr 2003 14:48:11 -0800 (PST) Received: from mail.speakeasy.net (mail16.speakeasy.net [216.254.0.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF43C43F3F for ; Wed, 2 Apr 2003 14:48:09 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 31474 invoked from network); 2 Apr 2003 22:48:19 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 2 Apr 2003 22:48:19 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.8/8.12.8) with ESMTP id h32Mm0Ov024374; Wed, 2 Apr 2003 17:48:02 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3E8B66A8.7EB82D40@mindspring.com> Date: Wed, 02 Apr 2003 17:47:59 -0500 (EST) From: John Baldwin To: Terry Lambert cc: Robert Watson cc: Jeff Roberson cc: csujun@21cn.com cc: current@freebsd.org cc: Alexander Leidinger Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 22:48:11 -0000 On 02-Apr-2003 Terry Lambert wrote: > The only way I see for disk I/O to be involved in Mozilla is in > local cache? You can turn that off. Umm, the idea here is to actually make threaded programs _useful_. Not to require that you trim their functionality down before we handle them in a sane way. Less FUD more signal please. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 14:51:29 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46CC737B401; Wed, 2 Apr 2003 14:51:29 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id B07EC43F3F; Wed, 2 Apr 2003 14:51:28 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id 8B7112A8A7; Wed, 2 Apr 2003 14:51:28 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: John Baldwin In-Reply-To: Date: Wed, 02 Apr 2003 14:51:28 -0800 From: Peter Wemm Message-Id: <20030402225128.8B7112A8A7@canning.wemm.org> cc: Robert Watson cc: csujun@21cn.com cc: current@freebsd.org cc: Alexander Leidinger cc: Jeff Roberson Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 22:51:29 -0000 John Baldwin wrote: > > On 02-Apr-2003 Terry Lambert wrote: > > The only way I see for disk I/O to be involved in Mozilla is in > > local cache? You can turn that off. > > Umm, the idea here is to actually make threaded programs > _useful_. Not to require that you trim their functionality > down before we handle them in a sane way. Less FUD more signal > please. Just a reminder, we can selectively moderate folks with the new mailing list software.. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 14:52:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C39A37B405 for ; Wed, 2 Apr 2003 14:52:04 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D07E43FDD for ; Wed, 2 Apr 2003 14:52:03 -0800 (PST) (envelope-from eischen@pcnet1.pcnet.com) Received: from pcnet1.pcnet.com (localhost [127.0.0.1]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h32MpuBg013962; Wed, 2 Apr 2003 17:51:56 -0500 (EST) Received: from localhost (eischen@localhost)h32Mpu6C013959; Wed, 2 Apr 2003 17:51:56 -0500 (EST) Date: Wed, 2 Apr 2003 17:51:56 -0500 (EST) From: Daniel Eischen To: Jeff Roberson In-Reply-To: <20030402173720.W64602-100000@mail.chesapeake.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Julian Elischer cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 22:52:04 -0000 [ CC list trimmed somewhat ] On Wed, 2 Apr 2003, Jeff Roberson wrote: > On Wed, 2 Apr 2003, Daniel Eischen wrote: > > On Wed, 2 Apr 2003, Jeff Roberson wrote: > > > > > > Then set the mask to be the same on all threads in the process. The mask > > > is set in swapcontext though so it seems reasonable to me that it is > > > atomically updated when you schedule a new user thread on a kse. > > > > Jeff, are you _listening_ to us? We've said multiple times > > that the UTS does not enter the kernel when performing thread > > switches. The UTS does NOT use setcontext(), getcontext(), > > or swapcontext(). > > I had not seen anyone mention this. This is only the 3rd or 4th time that I've sent or CC'd you with email on the topic, most probably on the KSE list. I know that Julian has sent several also. You must be filtering us :-) > If this is the case then I suggest > the masks and pending sets be kept in user space. You can install blank > handlers for everything so that they are kept pending until the uts has a > chance to pick them up in the upcall. Well, they are kept in user-space. The kse mailbox has the currently running thread's signal mask. The thread structure also has a pending signal set, and there is also a global pending signal set for signals pending on the process. It's just that the kernel doesn't know about it. > If you really want a process wide mask allow me to do it. The single code > is quite tricky and it's already been butchered enough. I think we should > discuss this a bit more first though. Sure, we're discussing signal stuff on the kse list now. Are you still monitoring that list? Perhaps that's partially why you haven't seen any of our email? -- Dan Eischen From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 14:57:46 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EFF137B404; Wed, 2 Apr 2003 14:57:46 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1E4D43FA3; Wed, 2 Apr 2003 14:57:45 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0303.cvx22-bradley.dialup.earthlink.net ([209.179.199.48] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190rAo-0007fw-00; Wed, 02 Apr 2003 14:57:39 -0800 Message-ID: <3E8B6A91.821EBA6B@mindspring.com> Date: Wed, 02 Apr 2003 14:56:17 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4fcbd92af012184e0651fcd3b95d52e89667c3043c0873f7e350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 22:57:46 -0000 John Baldwin wrote: > On 02-Apr-2003 Jens Rehsack wrote: > > I really think splitting the base in some sub-parts would it make much > > easier to do NO_SENDMAIL on my own. So I had to remove each not required > > file separately. That's no good solution. > > [stepping back a bit ] > > I find an odd situation here whenever this topic comes up. One the > one hand, people are always wanting to split the entire base system > up into small packages for each little piece of the base. On the > other hand, one of FreeBSD's selling points in real-world environments > is that it doesn't have a bunch of little packages for the base system > like Linux distros. Do people really prefer something like having > rpm's for /bin/ps to having one lump base dist for all of /bin, /sbin, > etc.? I don't think so. I think people just want to get to the same place with layered software that VAX/VMS and VAX/Ultrix achieved back in 1985 or so. In other words, we want to get to the point where, when people complain about some base system component, we can tell them: 1. pkg_delete FOO 2. pkg_add FEE 3. Go away Works for Sendmail vs. Postfix, works for TenDRA vs. Gcc, etc.; also lets you tell people to "Go away" if they install non-default components, since they are not "Tested configurations". The important part is that we are tired of revisiting this same ground, over and over, every time there's a CERT advisory against a "default" component, particularly when we just *replaced* it with some other functionally similar former default component because of a CERT advisory. And we are tired of CERT advisories listing FreeBSD as vulnerable, instead of blaming the third party software, because we install the third party software by default (I think that was the original motiviation for the delete request this time... and last time). Or to recap, the issues, IMO, always boil down to: 1) Technical support load shedding 2) Disconnecting politics from process 3) Advocacy -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 15:01:22 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 682DA37B401 for ; Wed, 2 Apr 2003 15:01:22 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99A7743FAF for ; Wed, 2 Apr 2003 15:01:21 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h32N1H867059; Wed, 2 Apr 2003 18:01:17 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Wed, 2 Apr 2003 18:01:17 -0500 (EST) From: Jeff Roberson To: Daniel Eischen In-Reply-To: Message-ID: <20030402175924.U64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Julian Elischer cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 23:01:22 -0000 On Wed, 2 Apr 2003, Daniel Eischen wrote: > [ CC list trimmed somewhat ] > > On Wed, 2 Apr 2003, Jeff Roberson wrote: > > On Wed, 2 Apr 2003, Daniel Eischen wrote: > > > On Wed, 2 Apr 2003, Jeff Roberson wrote: > > > > > > > > Then set the mask to be the same on all threads in the process. The mask > > > > is set in swapcontext though so it seems reasonable to me that it is > > > > atomically updated when you schedule a new user thread on a kse. > > > > > > Jeff, are you _listening_ to us? We've said multiple times > > > that the UTS does not enter the kernel when performing thread > > > switches. The UTS does NOT use setcontext(), getcontext(), > > > or swapcontext(). > > > > I had not seen anyone mention this. > > This is only the 3rd or 4th time that I've sent or CC'd you > with email on the topic, most probably on the KSE list. I > know that Julian has sent several also. You must be filtering > us :-) It depends on where things have been CC'd. I should probably adjust my filter so that things sent directly to me hit my inbox only. I have been quite overloaded with mail lately. Both from FreeBSD and other endeavours. I apologize, it must have been frustrating to tell me so many times. > > If this is the case then I suggest > > the masks and pending sets be kept in user space. You can install blank > > handlers for everything so that they are kept pending until the uts has a > > chance to pick them up in the upcall. > > Well, they are kept in user-space. The kse mailbox has the > currently running thread's signal mask. The thread structure > also has a pending signal set, and there is also a global > pending signal set for signals pending on the process. > It's just that the kernel doesn't know about it. > > > If you really want a process wide mask allow me to do it. The single code > > is quite tricky and it's already been butchered enough. I think we should > > discuss this a bit more first though. > > Sure, we're discussing signal stuff on the kse list now. > Are you still monitoring that list? Perhaps that's > partially why you haven't seen any of our email? I'll go look over it soon. Sorry for the misunderstanding. > -- > Dan Eischen > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 15:04:15 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CE1937B401 for ; Wed, 2 Apr 2003 15:04:15 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id A975F43F85 for ; Wed, 2 Apr 2003 15:04:14 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0303.cvx22-bradley.dialup.earthlink.net ([209.179.199.48] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190rHA-0001MU-00; Wed, 02 Apr 2003 15:04:13 -0800 Message-ID: <3E8B6C1D.4F30B534@mindspring.com> Date: Wed, 02 Apr 2003 15:02:53 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Cagle, John (ISS-Houston)" References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4fcbd92af012184e01707c5800230466f350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org Subject: Re: sio problem in -current (COM1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 23:04:15 -0000 "Cagle, John (ISS-Houston)" wrote: > I'm having a problem with -current on a ProLiant BL10e blade server. On > the blade server, we use a serial console on sio0/COM1. This works > perfectly with 4.8, but for some reason, the sio driver doesn't see COM1 > at all, and assigns COM2 resources to sio0. Any pointers to where I > should look would be greatly appreciated. > > I've attached dmesg output for 4.8 and -current on this blade. sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A Don't these things have a "magic" SMM port on COM1: by default? Looks like you need to disable the "System Management Port" option in your BIOS? -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 15:11:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1586A37B401; Wed, 2 Apr 2003 15:11:38 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DEDA43F3F; Wed, 2 Apr 2003 15:11:37 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0303.cvx22-bradley.dialup.earthlink.net ([209.179.199.48] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190rOI-0002yl-00; Wed, 02 Apr 2003 15:11:35 -0800 Message-ID: <3E8B6DD5.7231C0F6@mindspring.com> Date: Wed, 02 Apr 2003 15:10:13 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jeff Roberson References: <20030402152516.J64602-100000@mail.chesapeake.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a42587ce21ee35e74cb7ace936e774089fa2d4e88014a4647c350badd9bab72f9c350badd9bab72f9c cc: Alexander Leidinger cc: csujun@21cn.com cc: Robert Watson cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 23:11:38 -0000 Jeff Roberson wrote: > On Wed, 2 Apr 2003, Terry Lambert wrote: > > Is the disk I/O really that big of an issue? All writes will > > be on underlying non-blocking descriptors; I guess you are > > saying that the interleaved I/O is more important, further > > down the system call interface than the top, and this becomes > > an issue? > > UNIX distinguishes between short term and long term blocking calls. Non > blocking io only avoids blocking for indeterminate periods of time. The > 20ms or so you're paying per IO on an IDE system is 20ms that no other > threads can run. This makes a difference. See other message. The fault should be tripped, but the process should not wait around for the result, if it was tripped as the result of a read on an async fd. Instead an EAGAIN should go to user space, and that 20ms should be used for something else in user space, while the drive gets busy with the DMA. This is arguably a bug in FreeBSD's handling of demand faults on non-blocking fd's, compared to SVR4 and Solaris' handling. > > It seems to me that maybe the correct fix for this is to use > > AIO instead of non-blocking I/O, then? > > Our AIO implementation needs some rethinking. I'm not sure how > effecient it actually is. I will guess it suffers from the same "faulting == halting" problem... > > Also, any ETA on the per process signal mask handing bug in > > libthr? Might not be safe to convert everything up front, in > > a rush of eager enthusiasm... > > Which bug is that? I'm not aware of it. KSE mailing list, starting Monday or so: ] We still haven't heard from jeff with regard to the process ] signal mask removal. -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 15:13:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCB0F37B401; Wed, 2 Apr 2003 15:13:07 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 598E943F75; Wed, 2 Apr 2003 15:13:07 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0303.cvx22-bradley.dialup.earthlink.net ([209.179.199.48] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190rPk-0003DN-00; Wed, 02 Apr 2003 15:13:04 -0800 Message-ID: <3E8B6E1E.F8E1B73A@mindspring.com> Date: Wed, 02 Apr 2003 15:11:26 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Juli Mallett References: <3E8B03E6.36871704@mindspring.com> <20030402152516.J64602-100000@mail.chesapeake.net> <20030402143527.A96165@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a42587ce21ee35e74cb23f23bb656753d42601a10902912494350badd9bab72f9c350badd9bab72f9c cc: Robert Watson cc: Jeff Roberson cc: csujun@21cn.com cc: current@freebsd.org cc: Alexander Leidinger Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 23:13:08 -0000 Juli Mallett wrote: > * De: Jeff Roberson [ Data: 2003-04-02 ] > > On Wed, 2 Apr 2003, Terry Lambert wrote: > > > Also, any ETA on the per process signal mask handing bug in > > > libthr? Might not be safe to convert everything up front, in > > > a rush of eager enthusiasm... > > > > Which bug is that? I'm not aware of it. > > I think Terry is referring to the Uncertainty & Doubt as if it were > a bug over the lack of a process sigmask (moved into the threads), > as raised by the M:N group. Yes. This is the issue in question. -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 15:13:46 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E467D37B401 for ; Wed, 2 Apr 2003 15:13:46 -0800 (PST) Received: from ns2.gnf.org (ns2.gnf.org [63.196.132.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E01543F93 for ; Wed, 2 Apr 2003 15:13:46 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: from EXCHCLUSTER01.lj.gnf.org (exch02.lj.gnf.org [172.25.10.20]) by ns2.gnf.org (8.12.6p2/8.12.3) with ESMTP id h32NDh8V016960 for ; Wed, 2 Apr 2003 15:13:43 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: from roark.gnf.org ([172.25.24.15]) by EXCHCLUSTER01.lj.gnf.org with Microsoft SMTPSVC(5.0.2195.5329); Wed, 2 Apr 2003 15:13:45 -0800 Received: from roark.gnf.org (localhost [127.0.0.1]) by roark.gnf.org (8.12.9/8.12.9) with ESMTP id h32NDjNB072121 for ; Wed, 2 Apr 2003 15:13:45 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: (from gtetlow@localhost) by roark.gnf.org (8.12.9/8.12.9/Submit) id h32NDjW8072120 for current@FreeBSD.org; Wed, 2 Apr 2003 15:13:45 -0800 (PST) Date: Wed, 2 Apr 2003 15:13:45 -0800 From: Gordon Tetlow To: current@FreeBSD.org Message-ID: <20030402231345.GF69100@roark.gnf.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4f28nU6agdXSinmL" Content-Disposition: inline User-Agent: Mutt/1.4i X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-OriginalArrivalTime: 02 Apr 2003 23:13:45.0985 (UTC) FILETIME=[82BB2710:01C2F96D] Subject: LOR on libthr exit (iirc) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 23:13:47 -0000 --4f28nU6agdXSinmL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I think it was a libthr linked app after I killed it: lock order reversal 1st 0xc679d248 process lock (process lock) @ /local/usr.src/sys/kern/kern_exit. c:134 2nd 0xc05394a0 Giant (Giant) @ /local/usr.src/sys/kern/kern_exit.c:142 Stack backtrace: backtrace(c04e759f,c05394a0,c04e3f7f,c04e3f7f,c04e2359) at backtrace+0x17 witness_lock(c05394a0,8,c04e2359,8e,0) at witness_lock+0x692 _mtx_lock_flags(c05394a0,0,c04e2359,8e,c6d9deac) at _mtx_lock_flags+0xb2 exit1(c6d9de40,f00,c04e2359,63,e9971d40) at exit1+0x174 sys_exit(c6d9de40,e9971d14,c04ff422,404,1) at sys_exit+0x41 syscall(2f,2f,2f,0,ffffffff) at syscall+0x24e Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (1), eip = 0x280ef90f, esp = 0xbf91071c, ebp = 0xbf910738 --- -gordon --4f28nU6agdXSinmL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+i26pRu2t9DV9ZfsRAlr3AKCkSxtDqTkYq+f/yxgn7yWoU5O9XgCdFGtY mOz1Y1BHwi5Gyjm+baRjXA8= =RUsf -----END PGP SIGNATURE----- --4f28nU6agdXSinmL-- From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 15:13:47 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65E5B37B401; Wed, 2 Apr 2003 15:13:47 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0834543F93; Wed, 2 Apr 2003 15:13:47 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id D83692A8A7; Wed, 2 Apr 2003 15:13:46 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Terry Lambert In-Reply-To: <3E8B6DD5.7231C0F6@mindspring.com> Date: Wed, 02 Apr 2003 15:13:46 -0800 From: Peter Wemm Message-Id: <20030402231346.D83692A8A7@canning.wemm.org> cc: Robert Watson cc: Jeff Roberson cc: csujun@21cn.com cc: current@freebsd.org cc: Alexander Leidinger Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 23:13:47 -0000 Terry Lambert wrote: > KSE mailing list, starting Monday or so: > ] We still haven't heard from jeff with regard to the process > ] signal mask removal. We can add new mailing lists really easily now - it takes about 20-30 seconds. Would it be worth adding a freebsd-threads and/or freebsd-kse type list where it is a bit higher profile? Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 15:16:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC7EE37B401 for ; Wed, 2 Apr 2003 15:16:07 -0800 (PST) Received: from ns2.gnf.org (ns2.gnf.org [63.196.132.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9F1F43F85 for ; Wed, 2 Apr 2003 15:16:06 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: from EXCHCLUSTER01.lj.gnf.org (exch02.lj.gnf.org [172.25.10.20]) by ns2.gnf.org (8.12.6p2/8.12.3) with ESMTP id h32NG38V016988 for ; Wed, 2 Apr 2003 15:16:03 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: from roark.gnf.org ([172.25.24.15]) by EXCHCLUSTER01.lj.gnf.org with Microsoft SMTPSVC(5.0.2195.5329); Wed, 2 Apr 2003 15:16:06 -0800 Received: from roark.gnf.org (localhost [127.0.0.1]) by roark.gnf.org (8.12.9/8.12.9) with ESMTP id h32NG6NB072202 for ; Wed, 2 Apr 2003 15:16:06 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: (from gtetlow@localhost) by roark.gnf.org (8.12.9/8.12.9/Submit) id h32NG6HM072201 for current@FreeBSD.org; Wed, 2 Apr 2003 15:16:06 -0800 (PST) Date: Wed, 2 Apr 2003 15:16:06 -0800 From: Gordon Tetlow To: current@FreeBSD.org Message-ID: <20030402231606.GG69100@roark.gnf.org> References: <20030402214628.GA69100@roark.gnf.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YH9Qf6Fh2G5kB/85" Content-Disposition: inline In-Reply-To: <20030402214628.GA69100@roark.gnf.org> User-Agent: Mutt/1.4i X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-OriginalArrivalTime: 02 Apr 2003 23:16:06.0611 (UTC) FILETIME=[D68CFA30:01C2F96D] Subject: Re: LOR in PCM X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 23:16:08 -0000 --YH9Qf6Fh2G5kB/85 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I just wanted to apologize for my poor taste in the subject. It wasn't really called for. -gordon On Wed, Apr 02, 2003 at 01:46:28PM -0800, Gordon Tetlow wrote: > Just thought I would report it: >=20 > lock order reversal > 1st 0xc61f5940 pcm0 (sound softc) @ /local/usr.src/sys/dev/sound/pci/cmi= .c:520 > 2nd 0xc6209e80 pcm0:play:0 (pcm channel) @ /local/usr.src/sys/dev/sound/= pcm/channel.c:440 > Stack backtrace: > backtrace(c04e759f,c6209e80,c61a9b54,c06a2127,c06a21a5) at backtrace+0x17 > witness_lock(c6209e80,8,c06a21a5,1b8,c61a9b00) at witness_lock+0x692 > _mtx_lock_flags(c6209e80,0,c06a21a5,1b8,800000c1) at _mtx_lock_flags+0xb2 > chn_intr(c61a9b00,c,10000,208,c61f5a40) at chn_intr+0x2f > cmi_intr(c61a9c00,0,c04e258e,217,c61a43c0) at cmi_intr+0xa6 > ithread_loop(c61fa980,df0f0d48,c04e23fe,314,c21c9390) at ithread_loop+0x1= 6c > fork_exit(c02e7dd0,c61fa980,df0f0d48) at fork_exit+0xc4 > fork_trampoline() at fork_trampoline+0x1a > --- trap 0x1, eip =3D 0, esp =3D 0xdf0f0d7c, ebp =3D 0 --- >=20 > -gordon --YH9Qf6Fh2G5kB/85 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+i282Ru2t9DV9ZfsRAnHcAKDEOKH8faUNSdUPw2DB24gV9GJMQQCeM+Du 2EWb7F1hARJ+KWcFf3H8vww= =eAdZ -----END PGP SIGNATURE----- --YH9Qf6Fh2G5kB/85-- From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 15:18:29 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 199B737B401 for ; Wed, 2 Apr 2003 15:18:29 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5151143FAF for ; Wed, 2 Apr 2003 15:18:28 -0800 (PST) (envelope-from arr@watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h32NIeYX040073; Wed, 2 Apr 2003 18:18:40 -0500 (EST) (envelope-from arr@watson.org) Received: from localhost (arr@localhost)h32NIefF040070; Wed, 2 Apr 2003 18:18:40 -0500 (EST) X-Authentication-Warning: fledge.watson.org: arr owned process doing -bs Date: Wed, 2 Apr 2003 18:18:39 -0500 (EST) From: "Andrew R. Reiter" To: Peter Wemm In-Reply-To: <20030402231346.D83692A8A7@canning.wemm.org> Message-ID: <20030402181731.E39197@fledge.watson.org> References: <20030402231346.D83692A8A7@canning.wemm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Robert Watson cc: csujun@21cn.com cc: current@freebsd.org cc: Alexander Leidinger cc: Jeff Roberson Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 23:18:29 -0000 On Wed, 2 Apr 2003, Peter Wemm wrote: :Terry Lambert wrote: : :> KSE mailing list, starting Monday or so: :> ] We still haven't heard from jeff with regard to the process :> ] signal mask removal. : :We can add new mailing lists really easily now - it takes about 20-30 seconds. :Would it be worth adding a freebsd-threads and/or freebsd-kse type list :where it is a bit higher profile? : :Cheers, :-Peter :-- I would like this. I seem to remember a mail awhile back stating that there was a 'secret' list going on for thread discussion. Since this is a big part of -CURRENT (and has been, duh), it's sorta scary to have it be hidden. Did I miss a message regarding how to sign up for this? -- Andrew R. Reiter arr@watson.org arr@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 15:18:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05F8B37B404 for ; Wed, 2 Apr 2003 15:18:38 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5058043FB1 for ; Wed, 2 Apr 2003 15:18:37 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h32NIWH77574; Wed, 2 Apr 2003 18:18:32 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Wed, 2 Apr 2003 18:18:32 -0500 (EST) From: Jeff Roberson To: Gordon Tetlow In-Reply-To: <20030402231345.GF69100@roark.gnf.org> Message-ID: <20030402181809.O64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: LOR on libthr exit (iirc) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 23:18:38 -0000 On Wed, 2 Apr 2003, Gordon Tetlow wrote: > I think it was a libthr linked app after I killed it: Yeah, this is a problem with the thread single exit and suspend code. I haven't fixed it yet. Thanks for the report. > lock order reversal > 1st 0xc679d248 process lock (process lock) @ /local/usr.src/sys/kern/kern_exit. > c:134 > 2nd 0xc05394a0 Giant (Giant) @ /local/usr.src/sys/kern/kern_exit.c:142 > Stack backtrace: > backtrace(c04e759f,c05394a0,c04e3f7f,c04e3f7f,c04e2359) at backtrace+0x17 > witness_lock(c05394a0,8,c04e2359,8e,0) at witness_lock+0x692 > _mtx_lock_flags(c05394a0,0,c04e2359,8e,c6d9deac) at _mtx_lock_flags+0xb2 > exit1(c6d9de40,f00,c04e2359,63,e9971d40) at exit1+0x174 > sys_exit(c6d9de40,e9971d14,c04ff422,404,1) at sys_exit+0x41 > syscall(2f,2f,2f,0,ffffffff) at syscall+0x24e > Xint0x80_syscall() at Xint0x80_syscall+0x1d > --- syscall (1), eip = 0x280ef90f, esp = 0xbf91071c, ebp = 0xbf910738 --- > > -gordon > From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 15:29:42 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2F6337B401; Wed, 2 Apr 2003 15:29:42 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47F8C43FA3; Wed, 2 Apr 2003 15:29:42 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0303.cvx22-bradley.dialup.earthlink.net ([209.179.199.48] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190rfn-0006tz-00; Wed, 02 Apr 2003 15:29:40 -0800 Message-ID: <3E8B7210.C098838@mindspring.com> Date: Wed, 02 Apr 2003 15:28:16 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jeff Roberson References: <20030402154406.N64602-100000@mail.chesapeake.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a40fb066c8ff3aa9292768c7175c29e22a548b785378294e88350badd9bab72f9c350badd9bab72f9c cc: Alexander Leidinger cc: Robert Watson cc: csujun@21cn.com cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 23:29:43 -0000 Jeff Roberson wrote: > Perhaps I should start quoting posix. I wonder what my legal rights > are given the copyright. hm.. Educational use. FWIW, my reading of POSIX.1 says "Per process mask, per threads masks". The real question is "What happens when I kill -9/-15 a libthr process with a lot of threads?". Yeah, the KSE people are sorting out signals, too, but they were quite upset with the change, from their perspective, to the KSE kernel API semantics. Maybe they just felt rushed? Dunno... which is why I asked for an ETA: I think you should be talking to them. -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 15:32:43 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0F5637B401 for ; Wed, 2 Apr 2003 15:32:43 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7021C43FB1 for ; Wed, 2 Apr 2003 15:32:43 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0303.cvx22-bradley.dialup.earthlink.net ([209.179.199.48] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190rie-00010j-00; Wed, 02 Apr 2003 15:32:36 -0800 Message-ID: <3E8B72C2.343AAEBD@mindspring.com> Date: Wed, 02 Apr 2003 15:31:14 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm References: <20030402205608.2FCF82A8A5@canning.wemm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a40fb066c8ff3aa929e4c43be8b8c277cc350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: csujun@21cn.com cc: current@FreeBSD.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 23:32:44 -0000 Peter Wemm wrote: > No. It gives the ability for a thread to block on a syscall without > stalling the entire system. Just try using mysqld on a system using libc_r > and heavy disk IO. You can't select() on a read() from disk. Thats the > ultimate reason to do it. The SMP parallelism is a bonus. Bug in FreeBSD's NBIO implementation. A read() that would result in page-in needs to queue the request, but return EAGAIN to user space to indicate the request cannot be satisfied. Making select() come true for disk I/O after the fault is satisfied is a seperate issue. Probably need to pass the fd all the way down. -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 15:37:28 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 26EB637B404 for ; Wed, 2 Apr 2003 15:37:28 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E41543F75 for ; Wed, 2 Apr 2003 15:37:27 -0800 (PST) (envelope-from eischen@pcnet1.pcnet.com) Received: from pcnet1.pcnet.com (localhost [127.0.0.1]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h32NbLBg020303; Wed, 2 Apr 2003 18:37:21 -0500 (EST) Received: from localhost (eischen@localhost)h32NbLwf020298; Wed, 2 Apr 2003 18:37:21 -0500 (EST) Date: Wed, 2 Apr 2003 18:37:21 -0500 (EST) From: Daniel Eischen To: Peter Wemm In-Reply-To: <20030402231346.D83692A8A7@canning.wemm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: kse@elischer.org cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 23:37:28 -0000 On Wed, 2 Apr 2003, Peter Wemm wrote: > Terry Lambert wrote: > > > KSE mailing list, starting Monday or so: > > ] We still haven't heard from jeff with regard to the process > > ] signal mask removal. > > We can add new mailing lists really easily now - it takes about 20-30 seconds. > Would it be worth adding a freebsd-threads and/or freebsd-kse type list > where it is a bit higher profile? That's up to the folks here (on the KSE list) I guess. Is it possible to make it non-public? The nice thing about the current kse list is it's relatively low volume and lack of spam. -- Dan Eischen From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 15:39:39 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6074E37B401 for ; Wed, 2 Apr 2003 15:39:39 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96E0943F75 for ; Wed, 2 Apr 2003 15:39:38 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h32NdYL88952; Wed, 2 Apr 2003 18:39:34 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Wed, 2 Apr 2003 18:39:33 -0500 (EST) From: Jeff Roberson To: Terry Lambert In-Reply-To: <3E8B72C2.343AAEBD@mindspring.com> Message-ID: <20030402183406.O64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: csujun@21cn.com cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 23:39:39 -0000 On Wed, 2 Apr 2003, Terry Lambert wrote: > Peter Wemm wrote: > > No. It gives the ability for a thread to block on a syscall without > > stalling the entire system. Just try using mysqld on a system using libc_r > > and heavy disk IO. You can't select() on a read() from disk. Thats the > > ultimate reason to do it. The SMP parallelism is a bonus. > > Bug in FreeBSD's NBIO implementation. A read() that would result > in page-in needs to queue the request, but return EAGAIN to user > space to indicate the request cannot be satisfied. Making select() > come true for disk I/O after the fault is satisfied is a seperate > issue. Probably need to pass the fd all the way down. > Please quote the standard that defines this behavior. This is entirely counter to everything that I have ever read on the subject. From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 15:40:16 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C54137B401 for ; Wed, 2 Apr 2003 15:40:16 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3192543FA3 for ; Wed, 2 Apr 2003 15:40:16 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id 1550D2A8A7; Wed, 2 Apr 2003 15:40:16 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Terry Lambert In-Reply-To: <3E8B72C2.343AAEBD@mindspring.com> Date: Wed, 02 Apr 2003 15:40:16 -0800 From: Peter Wemm Message-Id: <20030402234016.1550D2A8A7@canning.wemm.org> cc: csujun@21cn.com cc: current@FreeBSD.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 23:40:16 -0000 Terry Lambert wrote: > Peter Wemm wrote: > > No. It gives the ability for a thread to block on a syscall without > > stalling the entire system. Just try using mysqld on a system using libc_r > > and heavy disk IO. You can't select() on a read() from disk. Thats the > > ultimate reason to do it. The SMP parallelism is a bonus. > > Bug in FreeBSD's NBIO implementation. A read() that would result > in page-in needs to queue the request, but return EAGAIN to user > space to indicate the request cannot be satisfied. Making select() > come true for disk I/O after the fault is satisfied is a seperate > issue. Probably need to pass the fd all the way down. Umm Terry.. we have zero infrastructure to support this. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 15:41:56 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFE4B37B401 for ; Wed, 2 Apr 2003 15:41:56 -0800 (PST) Received: from ns2.gnf.org (ns2.gnf.org [63.196.132.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id D681843FA3 for ; Wed, 2 Apr 2003 15:41:55 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: from EXCHCLUSTER01.lj.gnf.org (exch02.lj.gnf.org [172.25.10.20]) by ns2.gnf.org (8.12.6p2/8.12.3) with ESMTP id h32Nfq8V017528 for ; Wed, 2 Apr 2003 15:41:52 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: from roark.gnf.org ([172.25.24.15]) by EXCHCLUSTER01.lj.gnf.org with Microsoft SMTPSVC(5.0.2195.5329); Wed, 2 Apr 2003 15:41:55 -0800 Received: from roark.gnf.org (localhost [127.0.0.1]) by roark.gnf.org (8.12.9/8.12.9) with ESMTP id h32NftNB072693; Wed, 2 Apr 2003 15:41:55 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: (from gtetlow@localhost) by roark.gnf.org (8.12.9/8.12.9/Submit) id h32NfsLE072692; Wed, 2 Apr 2003 15:41:54 -0800 (PST) Date: Wed, 2 Apr 2003 15:41:54 -0800 From: Gordon Tetlow To: Daniel Eischen Message-ID: <20030402234154.GK69100@roark.gnf.org> References: <20030402231346.D83692A8A7@canning.wemm.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OOq1TgGhe8eTwFBO" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-OriginalArrivalTime: 02 Apr 2003 23:41:55.0569 (UTC) FILETIME=[71CD3610:01C2F971] cc: kse@elischer.org cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 23:41:57 -0000 --OOq1TgGhe8eTwFBO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 02, 2003 at 06:37:21PM -0500, Daniel Eischen wrote: > On Wed, 2 Apr 2003, Peter Wemm wrote: >=20 > > Terry Lambert wrote: > >=20 > > > KSE mailing list, starting Monday or so: > > > ] We still haven't heard from jeff with regard to the process > > > ] signal mask removal. > >=20 > > We can add new mailing lists really easily now - it takes about 20-30 s= econds. > > Would it be worth adding a freebsd-threads and/or freebsd-kse type list > > where it is a bit higher profile? >=20 > That's up to the folks here (on the KSE list) I guess. > Is it possible to make it non-public? The nice thing > about the current kse list is it's relatively low > volume and lack of spam. That kind of flies in the face of the way we do things. I would imagine if nothing else, being able to read the archives would be a good thing. -gordon --OOq1TgGhe8eTwFBO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+i3VCRu2t9DV9ZfsRArdYAKCFRQWbqOPIBRXS7eczTjJ7q/KrSQCdEph4 GwHMOekxroG4arECzVPq2+8= =UMoI -----END PGP SIGNATURE----- --OOq1TgGhe8eTwFBO-- From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 15:51:43 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 682F837B404 for ; Wed, 2 Apr 2003 15:51:43 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 3C4AC43FBF for ; Wed, 2 Apr 2003 15:51:42 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 12604 invoked by uid 1000); 2 Apr 2003 23:51:43 -0000 Date: Wed, 2 Apr 2003 15:51:43 -0800 (PST) From: Nate Lawson To: Juli Mallett In-Reply-To: <20030331193755.A60987@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Re: Odd issues with USB SmartMedia Reader/Writer (PNY) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2003 23:51:43 -0000 On Mon, 31 Mar 2003, Juli Mallett wrote: > I have a PNY USB SmartMedia reader which works excellently with 5.x > with 8M media, but which blows up with 32M media. I'd assume this is > due to improper geometry or something, but I really have no idea. > Insert-reinsert produces no change in results, etc. Below are bits > from dmesg, with the smaller then the larger. It's likely the 32M media is a different chipset than the 8M. Please see this page: http://www.root.org/~nate/freebsd/quirks.html Then read the quirks sections of the listed files to get an idea of how the quirks are used. > %%% --> With the 32M SmartMedia > umass0: Alcor Mass Storage Device, rev 1.10/1.00, addr 5 > umass0: Get Max Lun not supported (STALLED) > umass0:0:0:-1: Attached to scbus0 as device 0 > pass0 at umass-sim0 bus 0 target 0 lun 0 > pass0: Removable Direct Access SCSI-0 device > pass0: 1.000MB/s transfers > GEOM: new disk da0 > (da0:umass-sim0:0:0:0): error 6 > (da0:umass-sim0:0:0:0): Unretryable Error I'd try a scsi_da.c quirk of DA_Q_NO_6_BYTE first. You can just use "Generic", "*", "*" to start with. -Nate From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 16:00:01 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73C4537B401 for ; Wed, 2 Apr 2003 16:00:01 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0543243FBF for ; Wed, 2 Apr 2003 16:00:01 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.9/8.12.6) with ESMTP id h33000VI087107; Wed, 2 Apr 2003 16:00:00 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9/8.12.6/Submit) id h33000uO087097; Wed, 2 Apr 2003 16:00:00 -0800 (PST) Date: Wed, 2 Apr 2003 16:00:00 -0800 (PST) From: Matthew Dillon Message-Id: <200304030000.h33000uO087097@apollo.backplane.com> To: Peter Wemm References: <20030402234016.1550D2A8A7@canning.wemm.org> cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 00:00:01 -0000 :Terry Lambert wrote: :> Peter Wemm wrote: :> > No. It gives the ability for a thread to block on a syscall without :> > stalling the entire system. Just try using mysqld on a system using libc_r :> > and heavy disk IO. You can't select() on a read() from disk. Thats the :> > ultimate reason to do it. The SMP parallelism is a bonus. :> :> Bug in FreeBSD's NBIO implementation. A read() that would result :> in page-in needs to queue the request, but return EAGAIN to user :> space to indicate the request cannot be satisfied. Making select() :> come true for disk I/O after the fault is satisfied is a seperate :> issue. Probably need to pass the fd all the way down. : :Umm Terry.. we have zero infrastructure to support this. : :Cheers, :-Peter :-- :Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com :"All of this is for nothing if we don't go to the stars" - JMS/B5 It would be a very bad idea anyway. If someone is that dependant on detecting page-fault or page-in behavior during I/O then they ought to be using AIO (which does queue the request), not, read(), or they should wire the memory in question. I think I know what Terry wants... the best of both worlds when faced with the classic performance tradeoff between a cached synchronous operation and an asynchronous operation. Giving read() + NBIO certain asynchronous characteristics solves the performance problem but breaks the read() API (with or without NBIO) in a major way. A better solution would be to give AIO the capability to operate synchronously if the operation would occur in a non-blocking fashion (inclusive of blockages on page faults), and asynchronously otherwise. -Matt Matthew Dillon From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 16:01:18 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65F6537B401 for ; Wed, 2 Apr 2003 16:01:18 -0800 (PST) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F50B43F3F for ; Wed, 2 Apr 2003 16:01:16 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from localhost (localhost [127.0.0.1]) by cain.gsoft.com.au (8.12.9/8.12.6) with ESMTP id h3301721076013; Thu, 3 Apr 2003 09:31:07 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Jeff Roberson , current@freebsd.org Date: Thu, 3 Apr 2003 09:31:06 +0930 User-Agent: KMail/1.5 References: <20030402015226.E64602-100000@mail.chesapeake.net> In-Reply-To: <20030402015226.E64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304030931.06619.doconnor@gsoft.com.au> X-Spam-Score: -0.7 () CARRIAGE_RETURNS,IN_REP_TO,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) Subject: Re: ULE nice behavior fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 00:01:18 -0000 On Wed, 2 Apr 2003 16:24, Jeff Roberson wrote: > It probably still needs some tweaking but it seems to be MUCH better now. > New algorithm entirely. > > nice +20 processes will not run if anything else wants to. > > idleprio is still not working correctly. bde reports that this causes a > 3% perf degradation for buildworld. Isn't nice +20 == idle prio then? My understanding was that idle prio didn't run unless nothing else wanted the CPU which is what you describe nice +20 as doing :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 16:08:17 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3524037B401 for ; Wed, 2 Apr 2003 16:08:17 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB25C43FA3 for ; Wed, 2 Apr 2003 16:08:16 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id AEB842A8A7; Wed, 2 Apr 2003 16:08:16 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Matthew Dillon In-Reply-To: <200304030000.h33000uO087097@apollo.backplane.com> Date: Wed, 02 Apr 2003 16:08:16 -0800 From: Peter Wemm Message-Id: <20030403000816.AEB842A8A7@canning.wemm.org> cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 00:08:17 -0000 Matthew Dillon wrote: > A better solution would be to give AIO the capability to > operate synchronously if the operation would occur in a > non-blocking fashion (inclusive of blockages on page faults), > and asynchronously otherwise. Without wanting to get too far off into the weeds, squid does something interesting. They need to be able to nonblock for everything including open(), read(), unlink(), readdir() etc. So what they do is implement a fairly significant superset of the traditional AIO stuff using pthreads. It seems to work pretty well for them, even with linuxthreads style threads. Granted, squid's needs are not exactly typical. But I did want to point out that a good part of the delays come not only from data IO but operations like opening a file (pathname traversal), creating or removing a file, reading a directory etc. This is a particular problem when the disk is really busy. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 16:09:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E69F37B401; Wed, 2 Apr 2003 16:09:07 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id A48D643FBF; Wed, 2 Apr 2003 16:09:06 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0436.cvx22-bradley.dialup.earthlink.net ([209.179.199.181] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190sHk-0001FX-00; Wed, 02 Apr 2003 16:08:53 -0800 Message-ID: <3E8B7B16.B27BD31D@mindspring.com> Date: Wed, 02 Apr 2003 16:06:46 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm References: <20030402231346.D83692A8A7@canning.wemm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a43068a134cc57bdd99dd1d19d620b05c5350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: Robert Watson cc: Jeff Roberson cc: csujun@21cn.com cc: current@freebsd.org cc: Alexander Leidinger Subject: Re: FreeBSD threads list suggestion (was libthr and 1:1 threading.) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 00:09:07 -0000 Peter Wemm wrote: > Terry Lambert wrote: > > > KSE mailing list, starting Monday or so: > > ] We still haven't heard from jeff with regard to the process > > ] signal mask removal. > > We can add new mailing lists really easily now - it takes about 20-30 seconds. > Would it be worth adding a freebsd-threads and/or freebsd-kse type list > where it is a bit higher profile? Probably a threads or even a threads-arch list. I think the KSE people are happy off on the InterJet hosted list that Julian has been running forever, but the introduction of the libthr code has thrown a new element out there. It's not technically under the KSE umbrella. My own big concern is that KSE not be abandoned, just because Linux uses 1:1 and some Solaris engineers thought they could reduce their bug-count by not supporting a more complex (and useful) model. The problem is that libthr wasn't supposed to compete with KSE, but there are people posting as if it does, and the only shared forum is where the postings were made. Most of these people are historical Linux threading model advocates who are tired of waiting for KSE, or "if it doesn't work in 30 days, rip it out" types. Some things take time. In any case, it's definitely worth moving this type of discussion off -current, IMO. Maybe even banning it (and the questions that started it) on -current altogether. -- Historical footnote -- I think we would have had the same problem in 1993/4, if we had enough people, when 386BSD/FreeBSD rejected the SVR3 fixed mapping shared libary model, in favor of a BSD shared libary/PIC model. It took a relatively long time to get the PIC model, and the SVR3 implementation was done for a long time (PIC required compiler work by Jeffrey Hsu to be practical, which took until almost June 1994). -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 16:09:50 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9531D37B401; Wed, 2 Apr 2003 16:09:50 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CC5E43F3F; Wed, 2 Apr 2003 16:09:50 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id 1AF142A8A7; Wed, 2 Apr 2003 16:09:50 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: freebsd-alpha@FreeBSD.org, freebsd-current@freebsd.org In-Reply-To: <20030403000725.65B7A43FA3@mx1.FreeBSD.org> Content-Transfer-Encoding: 8bit Date: Wed, 02 Apr 2003 16:09:50 -0800 From: Peter Wemm Message-Id: <20030403000950.1AF142A8A7@canning.wemm.org> Subject: Re: failure notice X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 00:09:50 -0000 MAILER-DAEMON@norton.palomine.net wrote: > Hi. This is the qmail-send program at norton.palomine.net. > I'm afraid I wasn't able to deliver your message to the following addresses. > This is a permanent error; I've given up. Sorry it didn't work out. GRRR. a spammer is sending out a batch of spam right now and using forged @freebsd.org addresses in the From: line. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 16:17:43 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F1F137B401 for ; Wed, 2 Apr 2003 16:17:43 -0800 (PST) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3216E43FAF for ; Wed, 2 Apr 2003 16:17:41 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from localhost (localhost [127.0.0.1]) by cain.gsoft.com.au (8.12.9/8.12.6) with ESMTP id h330HQ21076283; Thu, 3 Apr 2003 09:47:28 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Don , Dan Naumov Date: Thu, 3 Apr 2003 09:47:25 +0930 User-Agent: KMail/1.5 References: <20030402185311.599cb0d3.dan.naumov@ofw.fi> <20030402105556.Y98713@calis.blacksun.org> In-Reply-To: <20030402105556.Y98713@calis.blacksun.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304030947.25940.doconnor@gsoft.com.au> X-Spam-Score: -2.1 () CARRIAGE_RETURNS,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02,TO_LOCALPART_EQ_REAL,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: freebsd-current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 00:17:43 -0000 On Thu, 3 Apr 2003 01:29, Don wrote: > Seriously though, I _always_ replace sendmail with postfix and I have > never had a problem doing so. Other than one or two really trivial > anyway. > > What problems do people run into when replacing sendmail? How many of > those problems come as a result of not reading the install messages for > the particular port? I think the worse problem is when you have to update the base sendmail with the ports version.. Come next installworld + mergemaster things can get pretty hairy as you try and decide which version to continue using, and if you change how to revert so the base system still does what you want etc.. It can be quite annoying to deal with :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 16:23:43 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09AE137B410 for ; Wed, 2 Apr 2003 16:23:43 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EC8143F85 for ; Wed, 2 Apr 2003 16:23:42 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0436.cvx22-bradley.dialup.earthlink.net ([209.179.199.181] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190sW1-0004Pt-00; Wed, 02 Apr 2003 16:23:38 -0800 Message-ID: <3E8B7EAD.EAAD8533@mindspring.com> Date: Wed, 02 Apr 2003 16:22:05 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jeff Roberson References: <20030402183406.O64602-100000@mail.chesapeake.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a429b0264bfe50ac3033146ede650efb25a2d4e88014a4647c350badd9bab72f9c350badd9bab72f9c cc: csujun@21cn.com cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 00:23:43 -0000 Jeff Roberson wrote: > On Wed, 2 Apr 2003, Terry Lambert wrote: > > Peter Wemm wrote: > > > No. It gives the ability for a thread to block on a syscall without > > > stalling the entire system. Just try using mysqld on a system using libc_r > > > and heavy disk IO. You can't select() on a read() from disk. Thats the > > > ultimate reason to do it. The SMP parallelism is a bonus. > > > > Bug in FreeBSD's NBIO implementation. A read() that would result > > in page-in needs to queue the request, but return EAGAIN to user > > space to indicate the request cannot be satisfied. Making select() > > come true for disk I/O after the fault is satisfied is a seperate > > issue. Probably need to pass the fd all the way down. > > Please quote the standard that defines this behavior. This is entirely > counter to everything that I have ever read on the subject. There's no "standard" that specifies this behaviour, but there's code that defines it. I believe this is the way BSD 4.2 and 4.3 worked. You could maybe as Kirk about it, if you don't want to believe me on it. The thing that broke it was the switch to the vnode abstraction seperation from the fd, going to a vnode-based pager, and the switch to a unified VM and buffer cache. At that point, the non-blocking I/O flags weren't available to the pager to enable it to make a decision on whether or not to block the process pending completion of the paging operation. SVR4 and Solaris both support doing this; I used it to great effect in SVR4.0.2 in 1994 for NetWare for UNIX, at Novell. It's pretty clear from just thinking about the idea that it makes sense, if you are using non-blocking I/O, to start the operation and return early. It's the same effect that's exploited by having a seperate context to use for each blocking operation. -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 16:26:27 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38BC437B401 for ; Wed, 2 Apr 2003 16:26:27 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA47F43F93 for ; Wed, 2 Apr 2003 16:26:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.9/8.12.6) with ESMTP id h330QQVI087257; Wed, 2 Apr 2003 16:26:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9/8.12.6/Submit) id h330QQbH087256; Wed, 2 Apr 2003 16:26:26 -0800 (PST) Date: Wed, 2 Apr 2003 16:26:26 -0800 (PST) From: Matthew Dillon Message-Id: <200304030026.h330QQbH087256@apollo.backplane.com> To: Peter Wemm References: <20030403000816.AEB842A8A7@canning.wemm.org> cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 00:26:27 -0000 That's a cute trick. The ultimate solution is to implement a semi-synchronous message passing API to replace the myrid system calls we have now. Roughly speaking, what the Amiga did for messages, ports, and I/O, is far superior then what is done in Linux and *BSD. You get the benefit of being able to operate syncnronously when possible, and having a convenient cup-holder for the operation state if you decide you have to 'block' the operation (instead of the state being strewn all over the call stack in a syscall implementation). Userland can decide whether to block or not block on an operation entirely independant of the OS deciding whether to block or not block on an operation. -Matt Matthew Dillon :Without wanting to get too far off into the weeds, squid does something :interesting. They need to be able to nonblock for everything including :open(), read(), unlink(), readdir() etc. So what they do is implement a :fairly significant superset of the traditional AIO stuff using pthreads. It :seems to work pretty well for them, even with linuxthreads style threads. :Granted, squid's needs are not exactly typical. But I did want to point :out that a good part of the delays come not only from data IO but operations :like opening a file (pathname traversal), creating or removing a file, :reading a directory etc. This is a particular problem when the disk :is really busy. : :Cheers, :-Peter :-- :Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com :"All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 16:31:14 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D556837B401 for ; Wed, 2 Apr 2003 16:31:14 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03FDE43FCB for ; Wed, 2 Apr 2003 16:31:14 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h330V6x19198; Wed, 2 Apr 2003 19:31:06 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Wed, 2 Apr 2003 19:31:06 -0500 (EST) From: Jeff Roberson To: "Daniel O'Connor" In-Reply-To: <200304030931.06619.doconnor@gsoft.com.au> Message-ID: <20030402193018.H64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: ULE nice behavior fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 00:31:15 -0000 On Thu, 3 Apr 2003, Daniel O'Connor wrote: > On Wed, 2 Apr 2003 16:24, Jeff Roberson wrote: > > It probably still needs some tweaking but it seems to be MUCH better now. > > New algorithm entirely. > > > > nice +20 processes will not run if anything else wants to. > > > > idleprio is still not working correctly. bde reports that this causes a > > 3% perf degradation for buildworld. > > Isn't nice +20 == idle prio then? > > My understanding was that idle prio didn't run unless nothing else wanted the > CPU which is what you describe nice +20 as doing :) > It's actually a seperate priority class. It doesn't have anything to do with nice. This is now fixed in ULE. We treat the classes specially now where before everything went onto the same run queue. Cheers, Jeff From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 16:36:10 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BCD137B401 for ; Wed, 2 Apr 2003 16:36:10 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4891843F93 for ; Wed, 2 Apr 2003 16:36:09 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h330Zxr22087; Wed, 2 Apr 2003 19:35:59 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Wed, 2 Apr 2003 19:35:59 -0500 (EST) From: Jeff Roberson To: Bruce Evans In-Reply-To: <20030402212503.N26453@gamplex.bde.org> Message-ID: <20030402193352.T64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: ULE nice behavior fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 00:36:10 -0000 On Wed, 2 Apr 2003, Bruce Evans wrote: > On Wed, 2 Apr 2003, Sheldon Hearn wrote: > > > On (2003/04/02 01:54), Jeff Roberson wrote: > > > > > It probably still needs some tweaking but it seems to be MUCH better now. > > > New algorithm entirely. > > > > > > nice +20 processes will not run if anything else wants to. > > > > Some of us have been waiting for that behaviour for a long time (long > > before you started working on ULE). > > Er, this is the normal behaviour in FreeBSD-3.0 through FreeBSD-4.8, > so you shouldn't have waited more than negative 4 years for it :-). > The strict implementation of this behaviour in these releases causes > priority inversion problems, but the problems apparently aren't very > important. The scaling of niceness was re-broken in -current about 3 > years ago to "fix" the priority inversion problems. This is with > SCHED_4BSD. SCHED_ULE has larger problems. > Do you know of any problem other than idlepri breakage? I just fixed that. I'm about to get on a plane so I don't have time to benchmark it. If you have a chance I'd love to see how the most recent fixes effect your buildworld time. I still have to microoptimize the code a bit to get rid of switch statements etc, but it all works. Cheers, Jeff From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 16:42:28 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 695EB37B401 for ; Wed, 2 Apr 2003 16:42:28 -0800 (PST) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3F9A43F85 for ; Wed, 2 Apr 2003 16:42:27 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0436.cvx22-bradley.dialup.earthlink.net ([209.179.199.181] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190so9-0003FO-00; Wed, 02 Apr 2003 16:42:23 -0800 Message-ID: <3E8B8307.4C5DF9D2@mindspring.com> Date: Wed, 02 Apr 2003 16:40:39 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm References: <20030402234016.1550D2A8A7@canning.wemm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a447bfd328ddd2488114e92edc9b7c3d73387f7b89c61deb1d350badd9bab72f9c350badd9bab72f9c cc: csujun@21cn.com cc: current@FreeBSD.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 00:42:28 -0000 Peter Wemm wrote: > Terry Lambert wrote: > > Peter Wemm wrote: > > > No. It gives the ability for a thread to block on a syscall without > > > stalling the entire system. Just try using mysqld on a system using libc_r > > > and heavy disk IO. You can't select() on a read() from disk. Thats the > > > ultimate reason to do it. The SMP parallelism is a bonus. > > > > Bug in FreeBSD's NBIO implementation. A read() that would result > > in page-in needs to queue the request, but return EAGAIN to user > > space to indicate the request cannot be satisfied. Making select() > > come true for disk I/O after the fault is satisfied is a seperate > > issue. Probably need to pass the fd all the way down. > > Umm Terry.. we have zero infrastructure to support this. There are a couple of PROC_LOCK()/PROC_UNLOCK() pairs in trap_pfault(), and there's the translation of the fault for emulators, which isn't protected at all in trap(), but there's not really any proc references which are held for a long time in the fault handing path, at least for T_PAGEFLT. Hmm. The problem comes down to the vnops version of the struct fileops, which comes down to VOP_READ which comes down to ffs_read, which then falls down to "try get the data from the object using vm tricks" -- uioread(). Is ENABLE_VFS_IOOPT permanently disabled? Nope -- enabled; I see a prototype unconditionalized in uio.h. This doesn't look too hard to implement on a per struct fileops, per-VFS basis; it's not like there's sleeping on a process, rather than a vnode lock or anything; mostly everything is marked "GIANT_REQUIRED" after a certain point. Worst case, you could create a kernel-only thread pool in whose context you operated, after validating credentials (obviously). -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 16:56:00 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1610337B401 for ; Wed, 2 Apr 2003 16:56:00 -0800 (PST) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79FCF43FB1 for ; Wed, 2 Apr 2003 16:55:59 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0436.cvx22-bradley.dialup.earthlink.net ([209.179.199.181] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190t1H-0006WT-00; Wed, 02 Apr 2003 16:55:56 -0800 Message-ID: <3E8B8631.67435BC8@mindspring.com> Date: Wed, 02 Apr 2003 16:54:09 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon References: <20030402234016.1550D2A8A7@canning.wemm.org> <200304030000.h33000uO087097@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a489ccf3259ccd0c83b1ec8186f447c1973ca473d225a0f487350badd9bab72f9c350badd9bab72f9c cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 00:56:00 -0000 Matthew Dillon wrote: >Peter Wemm wrote: > :Terry Lambert wrote: > :> > No. It gives the ability for a thread to block on a syscall without > :> > stalling the entire system. Just try using mysqld on a system using libc_r > :> > and heavy disk IO. You can't select() on a read() from disk. Thats the > :> > ultimate reason to do it. The SMP parallelism is a bonus. > :> > :> Bug in FreeBSD's NBIO implementation. A read() that would result > :> in page-in needs to queue the request, but return EAGAIN to user > :> space to indicate the request cannot be satisfied. Making select() > :> come true for disk I/O after the fault is satisfied is a seperate > :> issue. Probably need to pass the fd all the way down. > : > :Umm Terry.. we have zero infrastructure to support this. > > It would be a very bad idea anyway. If someone is that dependant > on detecting page-fault or page-in behavior during I/O then they > ought to be using AIO (which does queue the request), not, read(), > or they should wire the memory in question. ??? I don't understand this statement. Specifically, we're not talking about a "dependency", we are talking about optimizing the number of stalls in that case that a page-in becomes necessary in uioread(), and it is a result of a read on a non-blocking file descriptor. The only thing really missing is knowing the original request was a read() of a non-blocking descriptor at the time you initiated the uioread() operation. That's one parameter to two functions, and a struct fileops flag, and a struct vnops flag additional to get the information to where it's needed. And then a flag to the underlying uioread "VM pig tricks" code to tell it to come back after triggering the fault. What am I missing? > I think I know what Terry wants... the best of both worlds when > faced with the classic performance tradeoff between a cached > synchronous operation and an asynchronous operation. Giving > read() + NBIO certain asynchronous characteristics solves the > performance problem but breaks the read() API (with or without > NBIO) in a major way. How does this break the read() API? The read() API, when called on a NBIO fd is *supposed* to return EAGAIN, if the request cannot be immediately satisfied, but could be satisfied later. Right now, it blocks. This looks like breakage of disk I/O introducing a stall, when socket I/O doesn't. If this breaks read() semantics, then socket I/O needs fixing to unbreak them, right? > A better solution would be to give AIO the capability to > operate synchronously if the operation would occur in a > non-blocking fashion (inclusive of blockages on page faults), > and asynchronously otherwise. This is a useful optimization, but it's different from what I want. What I want is disk I/O "in the pipeline" to not stall a read() request on an NBIO fd, the *same* way that network I/O "in the pipeline" doesn't stall a read() request on an NBIO fd. Does this make more sense? I actually think Peter definitely "gets" what I want; I just think he thinks it's harder to implement than it actually is: there's not a lot of "infrastructure" required, I think. -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 17:02:24 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35B9437B404 for ; Wed, 2 Apr 2003 17:02:24 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47A5443F3F for ; Wed, 2 Apr 2003 17:02:23 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h3312Mh41491 for ; Wed, 2 Apr 2003 20:02:22 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Wed, 2 Apr 2003 20:02:22 -0500 (EST) From: Jeff Roberson To: current@freebsd.org Message-ID: <20030402200117.T64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: I'll be gone for a week. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 01:02:24 -0000 I'm letting you all know since I wont be able to look at thr bugs for a week. Also, I'm very interested in hearing comments on ULE when I get back. Cheers, Jeff From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 17:02:45 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AD7437B401 for ; Wed, 2 Apr 2003 17:02:45 -0800 (PST) Received: from quicksilver.ukc.ac.uk (quicksilver.ukc.ac.uk [129.12.21.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77E9D43F93 for ; Wed, 2 Apr 2003 17:02:42 -0800 (PST) (envelope-from mark@markdnet.demon.co.uk) Received: from stue9f4.ukc.ac.uk ([129.12.233.244] helo=markdnet.demon.co.uk) by quicksilver.ukc.ac.uk with esmtp (Exim 3.22 #4) id 190t7W-0002h1-00; Thu, 03 Apr 2003 02:02:22 +0100 Message-ID: <3E8B88A6.6060108@markdnet.demon.co.uk> Date: Thu, 03 Apr 2003 02:04:38 +0100 From: Mark Dixon User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2.1) Gecko/20030208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Michael W . Lucas" References: <20030402092055.A31850@blackhelicopters.org> In-Reply-To: <20030402092055.A31850@blackhelicopters.org> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms050303010006000600070902" X-UKC-Mail-System: No virus detected cc: current@FreeBSD.org Subject: Re: breakage this morning X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 01:02:45 -0000 This is a cryptographically signed message in MIME format. --------------ms050303010006000600070902 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Michael W . Lucas wrote: >While I'm all for a sense of humor, and agree that implementation of >the IP_EVIL flag is vital for FreeBSD to be a modern operating system, >it stops being funny when it breaks world. > > Its a pathetic waste of everyones time when it breaks world. Mark --------------ms050303010006000600070902 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJwjCC AzgwggKhoAMCAQICEGZFcrfMdPXPY3ZFhNAukQEwDQYJKoZIhvcNAQEEBQAwgdExCzAJBgNV BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vydmlj ZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkG CSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMDA4MzAwMDAw MDBaFw0wNDA4MjcyMzU5NTlaMIGSMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBD YXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xDzANBgNVBAoTBlRoYXd0ZTEdMBsGA1UECxMUQ2Vy dGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVtYWlsIFJTQSAyMDAw LjguMzAwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAN4zMqZjxwklRT7SbngnZ4HF2ogZ gpcO40QpimM1Km1wPPrcrvfudG8wvDOQf/k0caCjbZjxw0+iZdsN+kvx1t1hpfmFzVWaNRqd knWoJ67Ycvm6AvbXsJHeHOmr4BgDqHxDQlBRh4M88Dm0m1SKE4f/s5udSWYALQmJ7JRr6aFp AgMBAAGjTjBMMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwxLTI5NzAS BgNVHRMBAf8ECDAGAQH/AgEAMAsGA1UdDwQEAwIBBjANBgkqhkiG9w0BAQQFAAOBgQAxsUtH XfkBceX1U2xdedY9mMAmE2KBIqcS+CKV6BtJtyd7BDm6/ObyJOuR+r3sDSo491BVqGz3Da1M G7wD9LXrokefbKIMWI0xQgkRbLAaadErErJAXWr5edDqLiXdiuT82w0fnQLzWtvKPPZE6iZp h39Ins6ln+eE2MliYq0FxjCCAz8wggKooAMCAQICAwj96jANBgkqhkiG9w0BAQQFADCBkjEL MAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du MQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYD VQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMwMB4XDTAzMDEwMjAxMTg0MloX DTA0MDEwMjAxMTg0MlowajEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEoMCYG CSqGSIb3DQEJARYZbWFya0BtYXJrZG5ldC5kZW1vbi5jby51azEdMBsGCSqGSIb3DQEJARYO bW5kMkB1a2MuYWMudWswggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDYrKoEATH1 Y2pyiXHKkTjJOpChOcAu3JvvdungyR4uuMvL/njiZy2HrAp6WbpsBZmwnT5evj892azw/Zxx +UYvBeuuH4JVXen5xb2IseZiy31iHBIjE71ImM7wpW/E+H86cM72Q1dvVH960xfDusxj/vYP k1B2lI4Rz+6LRUxN0pUNYyfi2SK1qtbRDzRTtXEbvf+oW0vTZKHi47CdaVA04a/jRS/lmMUM 0c/fWlnJuPnc6vFPwy/PuAsafkfQgglEGpUAzWX7+WklfzR+mVBwOOlYsQy1M7oUlGybUvBG ghGaiSrJQqZWDqCM/I8RK2Zn42gKOgl2AKW73lIx/inNAgMBAAGjRjBEMDQGA1UdEQQtMCuB GW1hcmtAbWFya2RuZXQuZGVtb24uY28udWuBDm1uZDJAdWtjLmFjLnVrMAwGA1UdEwEB/wQC MAAwDQYJKoZIhvcNAQEEBQADgYEAU/sgEU5iLT5HRbO1bxCyG5qS/eZbEOc4i4o5gw8Sch9x Y89KLyHrotm3VRnvKbp8I2tHcj+73kqnZYmqyepwTIO6nxlRGBXSysXiq8hwHHUfFpnVG7sN IBG+PReM8wI01vUgMK0va3mtrg1Mz+Ig2kvTJoLH/C2FoJ7scra+/pYwggM/MIICqKADAgEC AgMI/eowDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJu IENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRD ZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIw MDAuOC4zMDAeFw0wMzAxMDIwMTE4NDJaFw0wNDAxMDIwMTE4NDJaMGoxHzAdBgNVBAMTFlRo YXd0ZSBGcmVlbWFpbCBNZW1iZXIxKDAmBgkqhkiG9w0BCQEWGW1hcmtAbWFya2RuZXQuZGVt b24uY28udWsxHTAbBgkqhkiG9w0BCQEWDm1uZDJAdWtjLmFjLnVrMIIBIjANBgkqhkiG9w0B AQEFAAOCAQ8AMIIBCgKCAQEA2KyqBAEx9WNqcolxypE4yTqQoTnALtyb73bp4MkeLrjLy/54 4mcth6wKelm6bAWZsJ0+Xr4/Pdms8P2ccflGLwXrrh+CVV3p+cW9iLHmYst9YhwSIxO9SJjO 8KVvxPh/OnDO9kNXb1R/etMXw7rMY/72D5NQdpSOEc/ui0VMTdKVDWMn4tkitarW0Q80U7Vx G73/qFtL02Sh4uOwnWlQNOGv40Uv5ZjFDNHP31pZybj53OrxT8Mvz7gLGn5H0IIJRBqVAM1l +/lpJX80fplQcDjpWLEMtTO6FJRsm1LwRoIRmokqyUKmVg6gjPyPEStmZ+NoCjoJdgClu95S Mf4pzQIDAQABo0YwRDA0BgNVHREELTArgRltYXJrQG1hcmtkbmV0LmRlbW9uLmNvLnVrgQ5t bmQyQHVrYy5hYy51azAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GBAFP7IBFOYi0+ R0WztW8Qshuakv3mWxDnOIuKOYMPEnIfcWPPSi8h66LZt1UZ7ym6fCNrR3I/u95Kp2WJqsnq cEyDup8ZURgV0srF4qvIcBx1HxaZ1Ru7DSARvj0XjPMCNNb1IDCtL2t5ra4NTM/iINpL0yaC x/wthaCe7HK2vv6WMYID1TCCA9ECAQEwgZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxX ZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYD VQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwg UlNBIDIwMDAuOC4zMAIDCP3qMAkGBSsOAwIaBQCgggIPMBgGCSqGSIb3DQEJAzELBgkqhkiG 9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAzMDQwMzAxMDQzOFowIwYJKoZIhvcNAQkEMRYEFOL9 nayrGKBEqhVBGf1FigQb5TrDMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZI hvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGrBgkr BgEEAYI3EAQxgZ0wgZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUx EjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZp Y2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4z MAIDCP3qMIGtBgsqhkiG9w0BCRACCzGBnaCBmjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgT DFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAb BgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFp bCBSU0EgMjAwMC44LjMwAgMI/eowDQYJKoZIhvcNAQEBBQAEggEAktWqV5rP5RrZ71gyWH1n xVzt3s0Sd14xqOd0YrfZyvo0wvNxuatn6jxAo8M5aUn9yiIBOIyTc4Gk/MktcD9x8yg8I7uS ftE3rcVrlcp9haRgow0a+MhrRrLTmply8VyqS2azv8M800Z5rFhzHl8qGDwjyu8pSBShoqu9 shPh4H7pR+bsM3YV7WK1sJQlQXGyvj+Rpnr+pxdvl3UBgdb/pEWTnCH4cVJjPyOV6Kql4rGM DDPjrItqlX1OmGp15Y8uCRgnrOv9eRhrrKN7+VzuWpdz3AF9wCzGcVEdyapWWHAb6pECZyrA TqLtxDTM01Ldzba4HLkEQ28JiovOg0P8RgAAAAAAAA== --------------ms050303010006000600070902-- From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 17:14:29 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00CE537B401 for ; Wed, 2 Apr 2003 17:14:29 -0800 (PST) Received: from pc-80-195-57-71-ll.blueyonder.co.uk (pc-80-195-57-71-ll.blueyonder.co.uk [80.195.57.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2173E43FAF for ; Wed, 2 Apr 2003 17:14:28 -0800 (PST) (envelope-from andrew@cream.org) Received: from cream.org (spatula.home [192.168.0.4]) by gateway.home (Postfix) with ESMTP id D113354EA; Thu, 3 Apr 2003 02:14:25 +0100 (BST) Message-ID: <3E8B8AF1.4010303@cream.org> Date: Thu, 03 Apr 2003 02:14:25 +0100 From: Andrew Boothman User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030321 X-Accept-Language: en-gb, en, en-us MIME-Version: 1.0 To: Terry Lambert References: <20030331225124.W64602-100000@mail.chesapeake.net> <20030402083026.GB83512@pcwin002.win.tue.nl> <3E8AAAA1.CB4B51B0@mindspring.com> In-Reply-To: <3E8AAAA1.CB4B51B0@mindspring.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Jeff Roberson cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 01:14:29 -0000 Terry Lambert wrote: >Stijn Hoop wrote: > > >>On Mon, Mar 31, 2003 at 10:54:45PM -0500, Jeff Roberson wrote: >> >> >>>I have commited libthr. To try this out you'll need to do the following >>> >>> >>I know very very little about threads, but I'm interested as to what the >>purpose is of this library. Is there a document available somewhere that >>describes the relationships between this, KSE, libc_r, pthreads, the >>Giant-unwinding-make-SMP-work-better project and some of the other >>threads and SMP related libraries and terminology? >> >> > >Here's a thumbnail sketch, though (forgive me, KSE folks, if I mung >it too badly): > Good explanations Terry! Even I could understand it :) If this is all reasonably accurate enough for everyone, could it be marked up for a FAQ or Handbook entry? As we move towards a 5-STABLE I think it would be useful to have a document to point to that describes these things. I'm happy to do the markup if you're happy for your words (or a close approximation) to be used. Thanks. Andrew. From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 17:29:24 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3751337B401; Wed, 2 Apr 2003 17:29:24 -0800 (PST) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6432F43FB1; Wed, 2 Apr 2003 17:29:23 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by sccrmhc01.attbi.com (sccrmhc01) with ESMTP id <20030403012921001009uig7e>; Thu, 3 Apr 2003 01:29:22 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA19863; Wed, 2 Apr 2003 17:29:20 -0800 (PST) Date: Wed, 2 Apr 2003 17:29:17 -0800 (PST) From: Julian Elischer To: Peter Wemm In-Reply-To: <20030402231346.D83692A8A7@canning.wemm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Robert Watson cc: csujun@21cn.com cc: current@freebsd.org cc: Alexander Leidinger cc: Jeff Roberson Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 01:29:24 -0000 Yes I think so.. I think 'threads is a better name thatn 'kse' though kse is good in that it's real quick to type :-) On Wed, 2 Apr 2003, Peter Wemm wrote: > Terry Lambert wrote: > > > KSE mailing list, starting Monday or so: > > ] We still haven't heard from jeff with regard to the process > > ] signal mask removal. > > We can add new mailing lists really easily now - it takes about 20-30 seconds. > Would it be worth adding a freebsd-threads and/or freebsd-kse type list > where it is a bit higher profile? > > Cheers, > -Peter > -- > Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 17:57:44 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E1DE37B404 for ; Wed, 2 Apr 2003 17:57:44 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4913643F93 for ; Wed, 2 Apr 2003 17:57:43 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.9/8.12.6) with ESMTP id h331vgVI087638; Wed, 2 Apr 2003 17:57:43 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9/8.12.6/Submit) id h331veVm087635; Wed, 2 Apr 2003 17:57:40 -0800 (PST) Date: Wed, 2 Apr 2003 17:57:40 -0800 (PST) From: Matthew Dillon Message-Id: <200304030157.h331veVm087635@apollo.backplane.com> To: Terry Lambert References: <20030402234016.1550D2A8A7@canning.wemm.org> <3E8B8631.67435BC8@mindspring.com> cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 01:57:45 -0000 :How does this break the read() API? The read() API, when called :on a NBIO fd is *supposed* to return EAGAIN, if the request cannot :be immediately satisfied, but could be satisfied later. Right now, :it blocks. This looks like breakage of disk I/O introducing a :stall, when socket I/O doesn't. : :If this breaks read() semantics, then socket I/O needs fixing to :unbreak them, right? Oh please. You know very well that every single UNIX out there operates on disk files as if their data was immediately available regardless of whether the process blocks in an uninterruptable disk wait or not. What you are suggesting is that we make our file interface incompatible with every other unix out there... ours will return EAGAIN in situations where programs wouldn't expect it. Additionally, the EAGAIN operation would be highly non-deterministic and it would be fairly difficult for a program to rely on it because there would be no easy way (short of experiementation or a sysctl) for it to determine whether the 'feature' is present or not. Also, the idea that the resulting block I/O operation is then queued and one returns immediately from way down deep in the filesystem device driver code, and that this whole mess is then tied into select()/kqueue()/ poll(), is just asking for more non-determinism... now it would depend on the filesystem AND the OS supporting the feature, and other UNIX implementations (if they were to adopt the mechanism) would likely wind up with slightly different semantics, just like O_NONBLOCK on listen() sockets has wound up being broken on things like HPUX. For example, how would one deal with, say, issuing a million of these special non-blocking reads() all of which fail. Do we queue a million I/Os? Do we queue just the last requested I/O? You see the problem? The API would be unstable and almost certainly implemented differently on each OS platform. A better solution would be to implement a new system call, similar to pread(), which simply checks the buffer cache and returns a short read or an error if the data is not present. If the call fails you would then know that reading that data would block in the disk subsystem and you could back-off to a more expensive mechanism like AIO. If want to select() on it you would then simply use kqueue with EVFILT_AIO and AIO. A system call pread_cache(), or perhaps we could even use recvmsg() with a flag. Such an interface would not have to touch the filesystem code, only the buffer cache and the VM page cache, and could be implemented in less then a day. -Matt From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 18:10:20 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A60EF37B401 for ; Wed, 2 Apr 2003 18:10:20 -0800 (PST) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F56A43F85 for ; Wed, 2 Apr 2003 18:10:20 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by rwcrmhc51.attbi.com (rwcrmhc51) with ESMTP id <20030403021019051001j78ce>; Thu, 3 Apr 2003 02:10:19 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id SAA20191; Wed, 2 Apr 2003 18:10:16 -0800 (PST) Date: Wed, 2 Apr 2003 18:10:14 -0800 (PST) From: Julian Elischer To: Matthew Dillon In-Reply-To: <200304030157.h331veVm087635@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 02:10:20 -0000 A thought on 'fixing AIO..' On Wed, 2 Apr 2003, Matthew Dillon wrote: > > A better solution would be to implement a new system call, similar to > pread(), which simply checks the buffer cache and returns a short read > or an error if the data is not present. If the call fails you would > then know that reading that data would block in the disk subsystem and > you could back-off to a more expensive mechanism like AIO. If want > to select() on it you would then simply use kqueue with EVFILT_AIO and > AIO. A system call pread_cache(), or perhaps we could even use > recvmsg() with a flag. Such an interface would not have to touch the > filesystem code, only the buffer cache and the VM page cache, and > could be implemented in less then a day. > Just as a point of interest, we now have the ability for a non-threaded program to have several threads in the kernel.. By this I mean, it would be theoretically possible to re-implement aioread() in terms of some background threads (doing synchronous IO) in the kernel, that the program is not aware of.. We don't have this hapen at teh moment.. (hmm actually we do but...only in KSE programs) but we have the infrastructure that would allow it to be done by someone who has a spare day or so.. Basically teh aioread would return, but the process would have left a worker thread in the kernel, completing the work, and since the thread is attached to the process, when it is reactivated on data arrival, the correct address space would be there automatically.. All 'exit' cases would be handled automatically.. etc. etc. From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 18:34:56 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5698937B407; Wed, 2 Apr 2003 18:34:56 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id B23E843FAF; Wed, 2 Apr 2003 18:34:55 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id 8F2882A8A7; Wed, 2 Apr 2003 18:34:55 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Julian Elischer In-Reply-To: Date: Wed, 02 Apr 2003 18:34:55 -0800 From: Peter Wemm Message-Id: <20030403023455.8F2882A8A7@canning.wemm.org> cc: Robert Watson cc: csujun@21cn.com cc: current@freebsd.org cc: Alexander Leidinger cc: Jeff Roberson Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 02:34:56 -0000 Julian Elischer wrote: > Yes I think so.. > I think 'threads is a better name thatn 'kse' though kse > is good in that it's real quick to type :-) OK, done. It seems to me we've needed one for a while now. Subscribe by either: http://lists.freebsd.org/mailman/listinfo/freebsd-threads or echo "subscribe" | mail freebsd-threads-request@freebsd.org or echo "anything at all" | mail freebsd-threads-subscribe@freebsd.org > On Wed, 2 Apr 2003, Peter Wemm wrote: > > > Terry Lambert wrote: > > > > > KSE mailing list, starting Monday or so: > > > ] We still haven't heard from jeff with regard to the process > > > ] signal mask removal. > > > > We can add new mailing lists really easily now - it takes about 20-30 secon ds. > > Would it be worth adding a freebsd-threads and/or freebsd-kse type list > > where it is a bit higher profile? > > > > Cheers, > > -Peter > > -- > > Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com > > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 18:54:11 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C387637B401 for ; Wed, 2 Apr 2003 18:54:11 -0800 (PST) Received: from angelica.unixdaemons.com (angelica.unixdaemons.com [209.148.64.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3E4043F75 for ; Wed, 2 Apr 2003 18:54:10 -0800 (PST) (envelope-from bmilekic@unixdaemons.com) Received: from angelica.unixdaemons.com (localhost.unixdaemons.com [127.0.0.1])h332s5Zl092147; Wed, 2 Apr 2003 21:54:05 -0500 (EST) Received: (from bmilekic@localhost) by angelica.unixdaemons.com (8.12.9/8.12.1/Submit) id h332s47a092146; Wed, 2 Apr 2003 21:54:04 -0500 (EST) (envelope-from bmilekic@unixdaemons.com) X-Authentication-Warning: angelica.unixdaemons.com: bmilekic set sender to bmilekic@unixdaemons.com using -f Date: Wed, 2 Apr 2003 21:54:04 -0500 From: Bosko Milekic To: Nate Lawson Message-ID: <20030403025404.GA90770@unixdaemons.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: mbuf LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 02:54:12 -0000 On Wed, Apr 02, 2003 at 12:39:30PM -0800, Nate Lawson wrote: > I was testing some changes to make fxp MPSAFE and got a LOR in allocating > the mbuf cluster and then finally a panic when trying to dereference the > cluster header. Is the mbuf system MPSAFE? Is it ok to call m_getcl > with a device lock held (but not Giant)? Not necessarily if you're doing a TRYWAIT mbuf allocation. Notably, the TRYWAIT allocation may end up in a call to the reclaim routine which calls the protocol drain routines which may end up in an LOR if you're holding some lock that can also be touched from the drain routines. So, in other words, if you do do that you'd have to be very careful. But there is another problem. kmem_malloc() still requires Giant for blockable allocations (TRYWAIT in this case) and so Giant must be held going in there if you're doing a TRYWAIT allocation. For what concerns DONTWAIT, you should theoretically be allowed to hold a driver lock. But again, there may be a problem. Specifically, I see that UMA code has some explicit Giant acquires/frees in certain places. When the UMA code gets called from the malloc() code while the bucket is being internally allocated in mb_alloc, you may be hitting one of those paths. In fact, unless you have a specific Giant acquire in the fxp_* routines you list in your trace below, that is undoubtedly what is happening because there are no explicit Giant acquires in the code path from m_getcl() to malloc(), so they must be happening higher up in the call stack. > The lock reversal was: 1. fxp softc lock, 2. Giant. > > Traceback: > zalloc... > malloc() > mb_pop_cont() > mb_alloc() > m_getcl() > fxp_add_rfabuf() > fxp_intr_body() > fxp_intr() -- locks fxp softc > > -Nate -- Bosko Milekic bmilekic@unixdaemons.com bmilekic@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 18:58:29 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3710337B401; Wed, 2 Apr 2003 18:58:29 -0800 (PST) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17DF843F75; Wed, 2 Apr 2003 18:58:28 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by sccrmhc03.attbi.com (sccrmhc03) with ESMTP id <20030403025826003001ujm4e>; Thu, 3 Apr 2003 02:58:26 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id SAA20464; Wed, 2 Apr 2003 18:58:25 -0800 (PST) Date: Wed, 2 Apr 2003 18:58:23 -0800 (PST) From: Julian Elischer To: Peter Wemm In-Reply-To: <20030403023455.8F2882A8A7@canning.wemm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Robert Watson cc: csujun@21cn.com cc: current@freebsd.org cc: Alexander Leidinger cc: Jeff Roberson Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 02:58:29 -0000 can we have a subject ID? the KSE list prefixes with [KSE] and I've grown used to not ignoring those :-) On Wed, 2 Apr 2003, Peter Wemm wrote: > Julian Elischer wrote: > > Yes I think so.. > > I think 'threads is a better name thatn 'kse' though kse > > is good in that it's real quick to type :-) > > OK, done. It seems to me we've needed one for a while now. > > Subscribe by either: > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > or > echo "subscribe" | mail freebsd-threads-request@freebsd.org > or > echo "anything at all" | mail freebsd-threads-subscribe@freebsd.org > > > On Wed, 2 Apr 2003, Peter Wemm wrote: > > > > > Terry Lambert wrote: > > > > > > > KSE mailing list, starting Monday or so: > > > > ] We still haven't heard from jeff with regard to the process > > > > ] signal mask removal. > > > > > > We can add new mailing lists really easily now - it takes about 20-30 secon > ds. > > > Would it be worth adding a freebsd-threads and/or freebsd-kse type list > > > where it is a bit higher profile? > > > > > > Cheers, > > > -Peter > > > -- > > > Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com > > > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > > > > > _______________________________________________ > > > freebsd-current@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > > > > Cheers, > -Peter > -- > Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 19:08:16 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C234737B401 for ; Wed, 2 Apr 2003 19:08:16 -0800 (PST) Received: from moghedien.mukappabeta.net (moghedien.mukappabeta.net [194.145.150.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 156EB43F3F for ; Wed, 2 Apr 2003 19:08:16 -0800 (PST) (envelope-from mkb@moghedien.mukappabeta.net) Received: by moghedien.mukappabeta.net (Postfix, from userid 1000) id 8C9622C9B; Thu, 3 Apr 2003 05:08:30 +0200 (CEST) Date: Thu, 3 Apr 2003 05:08:30 +0200 From: Matthias Buelow To: freebsd-current@freebsd.org Message-ID: <20030403030829.GD3941@moghedien.mukappabeta.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: linux-emu ioctl not implemented w/ quake3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 03:08:17 -0000 Hi folks, I'm running 5.0-RELEASE-p7 on i386 and investigated how quake3 (linux) would be doing at the moment. I had some relative success on 4.7 (quake3 ran ok, in 3d acceleration, but only for about 30 seconds, at which point the whole machine froze solid) so I hoped it might just work out. This time at least it didn't freeze but I don't even get so far. When I run quake3.x86, I get the following: quake3 spits: Using XFree86-VidModeExtension Version 2.2 XFree86-VidModeExtension Activated at 640x480 libGL error: failed to open DRM: Operation not permitted ... (at which point it offers me to use Mesa software rendering as a fallback which, of course, works...) and the kernel says: Apr 3 04:59:23 reiher kernel: linux: 'ioctl' fd=13, cmd=0x6401 ('d',1) not implemented Does anybody know what ioctl that would be? I didn't get that on 4.7, is linux-emu divergent between -stable and -current? The relevant ktrace excerpt follows: ... 1713 quake3.x86 RET old.setrlimit 12/0xc 1713 quake3.x86 CALL ftruncate 1713 quake3.x86 RET ftruncate 1000/0x3e8 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri" 1713 quake3.x86 NAMI "/dev/dri" 1713 quake3.x86 RET setrlimit 0 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card0" 1713 quake3.x86 NAMI "/dev/dri/card0" 1713 quake3.x86 RET setrlimit 0 1713 quake3.x86 CALL open(0xbfbfeb00,0x2,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card0" 1713 quake3.x86 NAMI "/dev/dri/card0" 1713 quake3.x86 RET open 13/0xd 1713 quake3.x86 CALL ioctl(0xd,0xc0086401 ,0xbfbfec00) 1713 quake3.x86 RET ioctl -1 errno -22 Unknown error: -22 1713 quake3.x86 CALL close(0xd) 1713 quake3.x86 RET close 0 1713 quake3.x86 CALL ftruncate 1713 quake3.x86 RET ftruncate 1000/0x3e8 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri" 1713 quake3.x86 NAMI "/dev/dri" 1713 quake3.x86 RET setrlimit 0 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card1" 1713 quake3.x86 NAMI "/dev/dri/card1" 1713 quake3.x86 RET setrlimit JUSTRETURN 1713 quake3.x86 CALL ftruncate 1713 quake3.x86 RET ftruncate 1000/0x3e8 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri" 1713 quake3.x86 NAMI "/dev/dri" 1713 quake3.x86 RET setrlimit 0 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card2" 1713 quake3.x86 NAMI "/dev/dri/card2" 1713 quake3.x86 RET setrlimit JUSTRETURN 1713 quake3.x86 CALL ftruncate 1713 quake3.x86 RET ftruncate 1000/0x3e8 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri" 1713 quake3.x86 NAMI "/dev/dri" 1713 quake3.x86 RET setrlimit 0 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card3" 1713 quake3.x86 NAMI "/dev/dri/card3" 1713 quake3.x86 RET setrlimit JUSTRETURN 1713 quake3.x86 CALL ftruncate 1713 quake3.x86 RET ftruncate 1000/0x3e8 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri" 1713 quake3.x86 NAMI "/dev/dri" 1713 quake3.x86 RET setrlimit 0 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card4" 1713 quake3.x86 NAMI "/dev/dri/card4" 1713 quake3.x86 RET setrlimit JUSTRETURN 1713 quake3.x86 CALL ftruncate 1713 quake3.x86 RET ftruncate 1000/0x3e8 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri" 1713 quake3.x86 NAMI "/dev/dri" 1713 quake3.x86 RET setrlimit 0 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card5" 1713 quake3.x86 NAMI "/dev/dri/card5" 1713 quake3.x86 RET setrlimit JUSTRETURN 1713 quake3.x86 CALL ftruncate 1713 quake3.x86 RET ftruncate 1000/0x3e8 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri" 1713 quake3.x86 NAMI "/dev/dri" 1713 quake3.x86 RET setrlimit 0 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card6" 1713 quake3.x86 NAMI "/dev/dri/card6" 1713 quake3.x86 RET setrlimit JUSTRETURN 1713 quake3.x86 CALL ftruncate 1713 quake3.x86 RET ftruncate 1000/0x3e8 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri" 1713 quake3.x86 NAMI "/dev/dri" 1713 quake3.x86 RET setrlimit 0 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card7" 1713 quake3.x86 NAMI "/dev/dri/card7" 1713 quake3.x86 RET setrlimit JUSTRETURN 1713 quake3.x86 CALL ftruncate 1713 quake3.x86 RET ftruncate 1000/0x3e8 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri" 1713 quake3.x86 NAMI "/dev/dri" 1713 quake3.x86 RET setrlimit 0 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card8" 1713 quake3.x86 NAMI "/dev/dri/card8" 1713 quake3.x86 RET setrlimit JUSTRETURN 1713 quake3.x86 CALL ftruncate 1713 quake3.x86 RET ftruncate 1000/0x3e8 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri" 1713 quake3.x86 NAMI "/dev/dri" 1713 quake3.x86 RET setrlimit 0 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card9" 1713 quake3.x86 NAMI "/dev/dri/card9" 1713 quake3.x86 RET setrlimit JUSTRETURN 1713 quake3.x86 CALL ftruncate 1713 quake3.x86 RET ftruncate 1000/0x3e8 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri" 1713 quake3.x86 NAMI "/dev/dri" 1713 quake3.x86 RET setrlimit 0 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card10" 1713 quake3.x86 NAMI "/dev/dri/card10" 1713 quake3.x86 RET setrlimit JUSTRETURN 1713 quake3.x86 CALL ftruncate 1713 quake3.x86 RET ftruncate 1000/0x3e8 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri" 1713 quake3.x86 NAMI "/dev/dri" 1713 quake3.x86 RET setrlimit 0 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card11" 1713 quake3.x86 NAMI "/dev/dri/card11" 1713 quake3.x86 RET setrlimit JUSTRETURN 1713 quake3.x86 CALL ftruncate 1713 quake3.x86 RET ftruncate 1000/0x3e8 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri" 1713 quake3.x86 NAMI "/dev/dri" 1713 quake3.x86 RET setrlimit 0 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card12" 1713 quake3.x86 NAMI "/dev/dri/card12" 1713 quake3.x86 RET setrlimit JUSTRETURN 1713 quake3.x86 CALL ftruncate 1713 quake3.x86 RET ftruncate 1000/0x3e8 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri" 1713 quake3.x86 NAMI "/dev/dri" 1713 quake3.x86 RET setrlimit 0 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card13" 1713 quake3.x86 NAMI "/dev/dri/card13" 1713 quake3.x86 RET setrlimit JUSTRETURN 1713 quake3.x86 CALL ftruncate 1713 quake3.x86 RET ftruncate 1000/0x3e8 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri" 1713 quake3.x86 NAMI "/dev/dri" 1713 quake3.x86 RET setrlimit 0 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card14" 1713 quake3.x86 NAMI "/dev/dri/card14" 1713 quake3.x86 RET setrlimit JUSTRETURN 1713 quake3.x86 CALL write(0x2,0xbfbfc540,0x39) 1713 quake3.x86 GIO fd 2 wrote 57 bytes "libGL error: failed to open DRM: Operation not permitted " 1713 quake3.x86 RET write 57/0x39 ... --mkb From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 19:17:11 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E89937B401 for ; Wed, 2 Apr 2003 19:17:11 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id C906C43F85 for ; Wed, 2 Apr 2003 19:17:09 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id NAA20785; Thu, 3 Apr 2003 13:16:49 +1000 Date: Thu, 3 Apr 2003 13:16:48 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: "Cagle, John (ISS-Houston)" In-Reply-To: Message-ID: <20030403130503.T28990@gamplex.bde.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: sio problem in -current (COM1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 03:17:11 -0000 On Wed, 2 Apr 2003, Cagle, John (ISS-Houston) wrote: > I'm having a problem with -current on a ProLiant BL10e blade server. On > the blade server, we use a serial console on sio0/COM1. This works > perfectly with 4.8, but for some reason, the sio driver doesn't see COM1 > at all, and assigns COM2 resources to sio0. Any pointers to where I > should look would be greatly appreciated. > > I've attached dmesg output for 4.8 and -current on this blade. 4.8: > ... > config> di sio2 Maybe this helps. sio2's irq is often the same as sio0's, and this can sometimes cause problems. Workarounds for some of these problems have been broken and turned off since FreeBSD-2. > ... > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A, console > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A -current: > ... > sio0 port 0x2f8-0x2ff irq 3 on acpi0 > sio0: type 16550A, console acpi sometimes does this for reasons that no one understands AFAIK. Booting with -v should show the usual sio0 being probed and something about why the probe failed, provided sio0 is in hints. The probe order may be relevant. Bruce From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 19:37:56 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEF3937B401 for ; Wed, 2 Apr 2003 19:37:56 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB42243F93 for ; Wed, 2 Apr 2003 19:37:55 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id NAA23784; Thu, 3 Apr 2003 13:37:45 +1000 Date: Thu, 3 Apr 2003 13:37:44 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Jeff Roberson In-Reply-To: <20030402193352.T64602-100000@mail.chesapeake.net> Message-ID: <20030403132059.V29067@gamplex.bde.org> References: <20030402193352.T64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: ULE nice behavior fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 03:37:57 -0000 On Wed, 2 Apr 2003, Jeff Roberson wrote: > On Wed, 2 Apr 2003, Bruce Evans wrote: > > ... The scaling of niceness was re-broken in -current about 3 > > years ago to "fix" the priority inversion problems. This is with > > SCHED_4BSD. SCHED_ULE has larger problems. > > Do you know of any problem other than idlepri breakage? I just fixed > that. I'm about to get on a plane so I don't have time to benchmark it. > If you have a chance I'd love to see how the most recent fixes effect your > buildworld time. Nothing very important. Many scheduler-related fields shown by ps are now useless since they only have a dummy entry in them. IIRC, one is worse than useless since the dummy entry doesn't fit in the field width. Bruce From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 20:16:00 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3602837B401 for ; Wed, 2 Apr 2003 20:16:00 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6462243F3F for ; Wed, 2 Apr 2003 20:15:59 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h334FtW44043; Wed, 2 Apr 2003 23:15:55 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Wed, 2 Apr 2003 23:15:55 -0500 (EST) From: Jeff Roberson To: Bruce Evans In-Reply-To: <20030403132059.V29067@gamplex.bde.org> Message-ID: <20030402231142.I64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: ULE nice behavior fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 04:16:00 -0000 On Thu, 3 Apr 2003, Bruce Evans wrote: > On Wed, 2 Apr 2003, Jeff Roberson wrote: > > > On Wed, 2 Apr 2003, Bruce Evans wrote: > > > ... The scaling of niceness was re-broken in -current about 3 > > > years ago to "fix" the priority inversion problems. This is with > > > SCHED_4BSD. SCHED_ULE has larger problems. > > > > Do you know of any problem other than idlepri breakage? I just fixed > > that. I'm about to get on a plane so I don't have time to benchmark it. > > If you have a chance I'd love to see how the most recent fixes effect your > > buildworld time. > > Nothing very important. Many scheduler-related fields shown by ps are > now useless since they only have a dummy entry in them. IIRC, one is > worse than useless since the dummy entry doesn't fit in the field width. > Ah, right, you're talking about the weighted cpu? Some of these corners need to be cleaned up. I wanted to get other behavior cleaned up first. What is your impression of ULE? What do you think would be required for it to become the default scheduler? I mean, other than lots of time and benchmarking to prove it. I need to work on the cpu rebalancing code a bit more. I also want to do a fuzzy rescheduling mode that will notice how many interactive threads there are and mi_switch less agressively if there are none. My measurements show that this could have a huge perf impact on some workloads. Cheers, Jeff From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 21:34:25 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E96CA37B404 for ; Wed, 2 Apr 2003 21:34:25 -0800 (PST) Received: from ztxmail03.ztx.compaq.com (ztxmail03.ztx.compaq.com [161.114.1.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8F1543FAF for ; Wed, 2 Apr 2003 21:34:24 -0800 (PST) (envelope-from john.cagle@hp.com) Received: from cceexg13.americas.cpqcorp.net (cceexg13.americas.cpqcorp.net [16.110.250.119]) by ztxmail03.ztx.compaq.com (Postfix) with ESMTP id 64C1C83E1; Wed, 2 Apr 2003 23:34:24 -0600 (CST) Received: from cceexc19.americas.cpqcorp.net ([16.110.250.85]) by cceexg13.americas.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.2966); Wed, 2 Apr 2003 23:34:24 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 2 Apr 2003 23:34:23 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: sio problem in -current (COM1) Thread-Index: AcL5j4YgUfOE1PwtRWKfVLafkgddAwAEYVyw From: "Cagle, John (ISS-Houston)" To: "Bruce Evans" X-OriginalArrivalTime: 03 Apr 2003 05:34:24.0201 (UTC) FILETIME=[AF5E5B90:01C2F9A2] cc: freebsd-current@freebsd.org Subject: RE: sio problem in -current (COM1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 05:34:26 -0000 Thanks! It was an ACPI-related problem. I disabled ACPI (hint.acpi.0.disabled=3D"1" in /boot/device.hints) and rebooted and now both com ports show up properly as they did with FreeBSD 4.8. (These are just standard com ports, btw.) I didn't realize ACPI was involved in legacy com port detection. That's weird. Thanks, John > -----Original Message----- > From: Bruce Evans [mailto:bde@zeta.org.au]=20 > Sent: Wednesday, April 02, 2003 9:17 PM > To: Cagle, John (ISS-Houston) > Cc: freebsd-current@freebsd.org > Subject: Re: sio problem in -current (COM1) >=20 >=20 > On Wed, 2 Apr 2003, Cagle, John (ISS-Houston) wrote: >=20 > > I'm having a problem with -current on a ProLiant BL10e=20 > blade server. =20 > > On the blade server, we use a serial console on sio0/COM1. =20 > This works=20 > > perfectly with 4.8, but for some reason, the sio driver doesn't see=20 > > COM1 at all, and assigns COM2 resources to sio0. Any pointers to=20 > > where I should look would be greatly appreciated. > > > > I've attached dmesg output for 4.8 and -current on this blade. >=20 > 4.8: > > ... > > config> di sio2 >=20 > Maybe this helps. sio2's irq is often the same as sio0's,=20 > and this can sometimes cause problems. Workarounds for some=20 > of these problems have been broken and turned off since FreeBSD-2. >=20 > > ... > > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > > sio0: type 16550A, console > > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > > sio1: type 16550A >=20 > -current: > > ... > > sio0 port 0x2f8-0x2ff irq 3 on acpi0 > > sio0: type 16550A, console >=20 > acpi sometimes does this for reasons that no one understands=20 > AFAIK. Booting with -v should show the usual sio0 being=20 > probed and something about why the probe failed, provided=20 > sio0 is in hints. The probe order may be relevant. >=20 > Bruce From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 21:53:54 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE50B37B401 for ; Wed, 2 Apr 2003 21:53:54 -0800 (PST) Received: from perrin.int.nxad.com (internal.ext.nxad.com [69.1.70.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 350CA43FAF for ; Wed, 2 Apr 2003 21:53:54 -0800 (PST) (envelope-from sean@perrin.int.nxad.com) Received: by perrin.int.nxad.com (Postfix, from userid 1001) id 9BE022107B; Wed, 2 Apr 2003 21:53:53 -0800 (PST) Date: Wed, 2 Apr 2003 21:53:53 -0800 From: Sean Chittenden To: Jeff Roberson Message-ID: <20030403055353.GE64139@perrin.int.nxad.com> References: <20030331225124.W64602-100000@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030331225124.W64602-100000@mail.chesapeake.net> User-Agent: Mutt/1.4i X-PGP-Key: finger seanc@FreeBSD.org X-PGP-Fingerprint: 3849 3760 1AFE 7B17 11A0 83A6 DD99 E31F BC84 B341 X-Web-Homepage: http://sean.chittenden.org/ cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 05:53:55 -0000 > I have commited libthr. To try this out you'll need to do the following > > 1. cvsup > 2. rebuild world and kernel > 3. install world and kernel > 4. build libthr from src/lib/libthr > 5. Either replace /usr/lib/libc_r.so.5 with /usr/lib/libthr.so.1 or > relink your applications against libthr.so.1 > > This works with mozilla and open office. Point of reference, it works well with KDE, but there's something non-kosher someplace. I've been getting this periodically and haven't tracked down where or why I'm getting it. On a different note, SCHED_4BSD causes the kernel to hang hard on KDE's startup during the loading peripherals phase. I'm not home and don't have any way of debugging this from a remote machine. Here's the backtrace for konsole. -sc 0x29063b63 in wait4 () from /usr/lib/libc.so.5 #0 0x29063b63 in wait4 () from /usr/lib/libc.so.5 #1 0x29055035 in waitpid () from /usr/lib/libc.so.5 #2 0x290105e5 in _waitpid (wpid=7, status=0x7, options=7) at /usr/src/lib/libthr/thread/thr_syscalls.c:386 #3 0x286d7b8a in KCrash::defaultCrashHandler(int) (sig=6) at kcrash.cpp:235 #4 #5 0x29063843 in kill () from /usr/lib/libc.so.5 #6 0x29345603 in TEPty::makePty(bool) (this=0xbfbfead8) at TEPty.cpp:534 #7 0x2934568a in TEPty::startPgm(char const*, QValueList&, char const*) (this=0x81c7a00, pgm=0x7 , args=@0x81c7a28, term=0x8124920 "xterm-color") at TEPty.cpp:550 #8 0x29345eca in TEPty::commSetupDoneC() (this=0x81c7a00) at qcstring.h:295 #9 0x28681189 in KProcess::start(KProcess::RunMode, KProcess::Communication) ( this=0x81c7a00, runmode=7, comm=NoCommunication) at kprocess.cpp:320 #10 0x29344ee6 in TEPty::run(char const*, QStrList&, char const*, bool, char const*, char const*) (this=0x81c7a00, _pgm=0x7 , _args=@0x7, _term=0x7 , _addutmp=true, _konsole_dcop=0x7 , _konsole_dcop_session=0x7 ) at TEPty.cpp:321 #11 0x29369979 in TESession::run() (this=0x81cc300) at qcstring.h:295 #12 0x2936b7b9 in TESession::qt_invoke(int, QUObject*) (this=0x81cc300, _id=2, _o=0xbfbfef30) at session.moc:201 #13 0x28a25308 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/X11R6/lib/libqt-mt.so.3 #14 0x28cf17ad in QSignal::signal(QVariant const&) () from /usr/X11R6/lib/libqt-mt.so.3 #15 0x28a3eca8 in QSignal::activate() () from /usr/X11R6/lib/libqt-mt.so.3 #16 0x28a45a53 in QSingleShotTimer::event(QEvent*) () from /usr/X11R6/lib/libqt-mt.so.3 #17 0x289c8535 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/X11R6/lib/libqt-mt.so.3 #18 0x289c82fb in QApplication::notify(QObject*, QEvent*) () from /usr/X11R6/lib/libqt-mt.so.3 #19 0x2864c1a9 in KApplication::notify(QObject*, QEvent*) (this=0x7, receiver=0x80ba080, event=0xbfbff1d0) at kapplication.cpp:453 #20 0x289a48d7 in QEventLoop::activateTimers() () from /usr/X11R6/lib/libqt-mt.so.3 #21 0x28983cb1 in QEventLoop::processEvents(unsigned) () from /usr/X11R6/lib/libqt-mt.so.3 #22 0x289dbf20 in QEventLoop::enterLoop() () from /usr/X11R6/lib/libqt-mt.so.3 #23 0x289dbe58 in QEventLoop::exec() () from /usr/X11R6/lib/libqt-mt.so.3 #24 0x289c86c1 in QApplication::exec() () from /usr/X11R6/lib/libqt-mt.so.3 #25 0x2934a83d in main (argc=7, argv=0x7) at main.cpp:435 #26 0x0804cb16 in launch (argc=1, _name=0x805bc04 "konsole", args=0x805bc0c "\001", cwd=0x0, envc=1, envs=0x805bc1d "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x7 ) at kinit.cpp:547 #27 0x0804d906 in handle_launcher_request (sock=7) at kinit.cpp:1021 #28 0x0804de57 in handle_requests (waitForPid=0) at kinit.cpp:1189 #29 0x0804ef43 in main (argc=3, argv=0xbfbffbac, envp=0x7) at kinit.cpp:1540 #30 0x0804b115 in _start () -- Sean Chittenden From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 22:16:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 173B937B401 for ; Wed, 2 Apr 2003 22:16:07 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC2DB43FAF for ; Wed, 2 Apr 2003 22:16:05 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id QAA13157; Thu, 3 Apr 2003 16:15:52 +1000 Date: Thu, 3 Apr 2003 16:15:51 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: "Daniel O'Connor" In-Reply-To: <200304030931.06619.doconnor@gsoft.com.au> Message-ID: <20030403154330.P29472@gamplex.bde.org> References: <20030402015226.E64602-100000@mail.chesapeake.net> <200304030931.06619.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Jeff Roberson cc: current@freebsd.org Subject: Re: ULE nice behavior fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 06:16:07 -0000 On Thu, 3 Apr 2003, Daniel O'Connor wrote: > On Wed, 2 Apr 2003 16:24, Jeff Roberson wrote: > > It probably still needs some tweaking but it seems to be MUCH better now. > > New algorithm entirely. > > > > nice +20 processes will not run if anything else wants to. > > > > idleprio is still not working correctly. bde reports that this causes a > > 3% perf degradation for buildworld. > > Isn't nice +20 == idle prio then? > > My understanding was that idle prio didn't run unless nothing else wanted the > CPU which is what you describe nice +20 as doing :) Not quite: - there are 32 different idle priority classes. All of them give infinitely lower (numerically, non-infinitely higher) priority than each other and nice +20. - nice +20 should only only gives infinitely lower priority relative to nice +0 or +1. I hope SCHED_ULE implements this and not what the above says. Otherwise, nice +20 would just be a 33rd idle priority class. Actually, I plan to deprecate rtprio(2) and make nice +31 through +52 correspond to the 32 idle priority classes. Bruce From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 22:23:03 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0170D37B401 for ; Wed, 2 Apr 2003 22:23:03 -0800 (PST) Received: from hotmail.com (f20.pav1.hotmail.com [64.4.31.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 908DF43FB1 for ; Wed, 2 Apr 2003 22:23:02 -0800 (PST) (envelope-from evantd@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 2 Apr 2003 22:23:00 -0800 Received: from 128.208.59.99 by pv1fd.pav1.hotmail.msn.com with HTTP; Thu, 03 Apr 2003 06:22:57 GMT X-Originating-IP: [128.208.59.99] X-Originating-Email: [evantd@hotmail.com] From: "Evan Dower" To: tlambert2@mindspring.com Date: Wed, 02 Apr 2003 22:22:57 -0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 03 Apr 2003 06:23:00.0438 (UTC) FILETIME=[7994CF60:01C2F9A9] cc: freebsd-current@freebsd.org Subject: Re: sendmail: no local mailer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 06:23:03 -0000 I agree. In fact, it was. I only posted to -current after receiving no response for a few days (since I suspected that it might have been related to my upgrade to 5.0). I personally have never messed with sendmail's configuration because on my system it functions only as a local mailer. I guess that may be one reason for proposing that sendmail be moved out of the base system. It has all the power (and the complexity that comes with that power) of a full-featured mailer, yet most machines are not mail servers. Well, anyway, there's my two cents. Evan Dower >From: Terry Lambert >To: Evan Dower >CC: freebsd-current@freebsd.org >Subject: Re: sendmail: no local mailer >Date: Wed, 02 Apr 2003 13:59:28 -0800 >MIME-Version: 1.0 >Received: from stork.mail.pas.earthlink.net ([207.217.120.188]) by >mc10-f32.bay6.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Wed, 2 Apr >2003 14:00:48 -0800 >Received: from pool0303.cvx22-bradley.dialup.earthlink.net >([209.179.199.48] helo=mindspring.com)by stork.mail.pas.earthlink.net with >asmtp (SSLv3:RC4-MD5:128)(Exim 3.33 #1)id 190qHl-0001xF-00; Wed, 02 Apr >2003 14:00:45 -0800 >X-Message-Info: JGTYoYF78jEHjJx36Oi8+Q1OJDRSDidP >Message-ID: <3E8B5D40.56C256D9@mindspring.com> >X-Mailer: Mozilla 4.79 [en] (Win98; U) >X-Accept-Language: en >References: >X-ELNK-Trace: >b1a02af9316fbb217a47c185c03b154d40683398e744b8a4de10f470e868703b4fc515dddff6e594350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c >Return-Path: tlambert2@mindspring.com >X-OriginalArrivalTime: 02 Apr 2003 22:00:48.0845 (UTC) >FILETIME=[51C097D0:01C2F963] > >Note: This should have been posted to -questions, not -current. > > >Evan Dower wrote: > > Sendmail has not been working on my system for some time now. I can't >say > > exactly how long, but my guess is that it broke when I upgraded to > > RELENG_5_0. This is how sendmail is invoked (by default) and it's >output. > > > > # sendmail -L sm-mta -bd -q30m -ODaemonPortOptions=Addr=localhost > > 451 4.0.0 No local mailer defined: Bad address > >You are missing a local mailer. A local mailer is defined by a line >similar to: > >Mlocal, P=/usr/libexec/mail.local, F=lsDFMAw5:/|@qPSXfmnz9, >S=EnvFromSMT >P/HdrFromL, R=EnvToL/HdrToL, > T=DNS/RFC822/SMTP, > A=mail.local -l > >in /etc/mail/sendmail.cf. > >Probably, you updated and failed to rebuild and install the sendmail >configuration files located in /etc/mail/. > > > > 554 5.0.0 QueueDirectory (Q) option must be set > >You are missing a line similar to: > ># queue directory >O QueueDirectory=/var/spool/mqueue > >in /etc/mail/sendmail.cf. Probably this has the same root cause. > > > > The same thing happens if I change "localhost" to "127.0.0.1". I > > suspect that the second error (554) will disappear when I get rid > > of the first one (451). Does anyone know why it might be misbehaving > > like this? > >Pilot error. > >-- Terry _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 23:08:28 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 643C937B401 for ; Wed, 2 Apr 2003 23:08:28 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65E8843FAF for ; Wed, 2 Apr 2003 23:08:27 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h3378F619753; Thu, 3 Apr 2003 02:08:17 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Thu, 3 Apr 2003 02:08:15 -0500 (EST) From: Jeff Roberson To: Bruce Evans In-Reply-To: <20030403154330.P29472@gamplex.bde.org> Message-ID: <20030403020547.H64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: ULE nice behavior fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 07:08:28 -0000 On Thu, 3 Apr 2003, Bruce Evans wrote: > On Thu, 3 Apr 2003, Daniel O'Connor wrote: > > > On Wed, 2 Apr 2003 16:24, Jeff Roberson wrote: > > > It probably still needs some tweaking but it seems to be MUCH better now. > > > New algorithm entirely. > > > > > > nice +20 processes will not run if anything else wants to. > > > > > > idleprio is still not working correctly. bde reports that this causes a > > > 3% perf degradation for buildworld. > > > > Isn't nice +20 == idle prio then? > > > > My understanding was that idle prio didn't run unless nothing else wanted the > > CPU which is what you describe nice +20 as doing :) > > Not quite: > - there are 32 different idle priority classes. All of them give infinitely > lower (numerically, non-infinitely higher) priority than each other and > nice +20. > - nice +20 should only only gives infinitely lower priority relative to nice > +0 or +1. I hope SCHED_ULE implements this and not what the above says. > Otherwise, nice +20 would just be a 33rd idle priority class. Actually, > I plan to deprecate rtprio(2) and make nice +31 through +52 correspond to > the 32 idle priority classes. > It implements idle prio as a seperate run queue that is only checked when there is nothing to do, not even nice +20. It is also not hard bound to nice +20. Only ksegs with nice values that are within 20 of the least nice process are given slices. The slices size is inversely proportional to the distance of the ksegs nice from the least nice kseg. It ended up being fairly clean. I do hope you'll look it over some time. Cheers, Jeff From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 23:24:24 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B38837B401 for ; Wed, 2 Apr 2003 23:24:24 -0800 (PST) Received: from MX2.estpak.ee (ld3.estpak.ee [194.126.101.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id B449C43F75 for ; Wed, 2 Apr 2003 23:24:22 -0800 (PST) (envelope-from kalts@estpak.ee) Received: from kevad.internal (80-235-38-172-dsl.mus.estpak.ee [80.235.38.172]) by MX2.estpak.ee (Postfix) with ESMTP id 1BEC573583; Thu, 3 Apr 2003 10:22:49 +0300 (EEST) Received: (from vallo@localhost) by kevad.internal (8.12.9/8.12.9/Submit) id h337O9OR001562; Thu, 3 Apr 2003 10:24:09 +0300 (EEST) (envelope-from vallo) Date: Thu, 3 Apr 2003 10:24:09 +0300 From: Vallo Kallaste To: Jeff Roberson Message-ID: <20030403072409.GA1429@kevad.internal> References: <20030402212503.N26453@gamplex.bde.org> <20030402193352.T64602-100000@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030402193352.T64602-100000@mail.chesapeake.net> User-Agent: Mutt/1.5.3i-ja.1 cc: current@freebsd.org Subject: Re: ULE nice behavior fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kalts@estpak.ee List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 07:24:24 -0000 On Wed, Apr 02, 2003 at 07:35:59PM -0500, Jeff Roberson wrote: > Do you know of any problem other than idlepri breakage? I just fixed > that. I'm about to get on a plane so I don't have time to benchmark it. > If you have a chance I'd love to see how the most recent fixes effect your > buildworld time. > > I still have to microoptimize the code a bit to get rid of switch > statements etc, but it all works. Interactivity is still worse under ULE. It's quite noticeable and I tested it on two SMP boxes by running two simple loops in kind of: for ((;;)); do let $((4+4)); done # this is bash specific The loops ran under nice +20. Typing in the xterm is jerky, characters will not show up immediately, but in small "bursts". I mean that about three characters typed in will show up immediately, then small pause happens and a burst of characters (which queued up in the pause) will show up. This is annoying. Starting up xterm takes more time as well, but I can live with that. -- Vallo Kallaste From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 23:25:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24DE237B401 for ; Wed, 2 Apr 2003 23:25:32 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF79F43F3F for ; Wed, 2 Apr 2003 23:25:28 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0038.cvx21-bradley.dialup.earthlink.net ([209.179.192.38] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190z6D-0006Gy-00; Wed, 02 Apr 2003 23:25:25 -0800 Message-ID: <3E8BE193.7BD9AD1C@mindspring.com> Date: Wed, 02 Apr 2003 23:24:03 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon References: <20030402234016.1550D2A8A7@canning.wemm.org> <3E8B8631.67435BC8@mindspring.com> <200304030157.h331veVm087635@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a49d92cb2d0efdd44e188959fe900d2a9fa7ce0e8f8d31aa3f350badd9bab72f9c350badd9bab72f9c cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 07:25:32 -0000 Matthew Dillon wrote: > :How does this break the read() API? The read() API, when called > :on a NBIO fd is *supposed* to return EAGAIN, if the request cannot > :be immediately satisfied, but could be satisfied later. Right now, > :it blocks. This looks like breakage of disk I/O introducing a > :stall, when socket I/O doesn't. > : > :If this breaks read() semantics, then socket I/O needs fixing to > :unbreak them, right? > > Oh please. You know very well that every single UNIX out there > operates on disk files as if their data was immediately available > regardless of whether the process blocks in an uninterruptable > disk wait or not. False. SVR4.0.2 and SVR4.2 do not. They act as I describe. The code was written by a guy named Steve Baumel. > What you are suggesting is that we make our file interface > incompatible with every other unix out there... ours will > return EAGAIN in situations where programs wouldn't expect it. According to the FreeBSD 5.x man page for read(2): [EAGAIN] The file was marked for non-blocking I/O, and no data were ready to be read. ...in other words, they mark it for non-blocking I/O, they *better* expect it! And at least /usr/src/lib/libc_r/uthread/uthread_read[v].c expects it from the kernel. /* Perform a non-blocking read syscall: */ while ((ret = __sys_read(fd, buf, nbytes)) < 0) { if ((_thread_fd_getflags(fd) & O_NONBLOCK) == 0 && (errno == EWOULDBLOCK || errno == EAGAIN)) { curthread->data.fd.fd = fd; _thread_kern_set_timeout(NULL); The kernel also certainly expects, if not EAGAIN, EWOULDBLOCK: if ((error = fo_read(fp, &auio, td->td_ucred, flags, td))) { if (auio.uio_resid != cnt && (error == ERESTART || error == EINTR || error == EWOULDBLOCK)) error = 0; } cnt -= auio.uio_resid; > Additionally, the EAGAIN operation would be highly non-deterministic > and it would be fairly difficult for a program to rely on it because > there would be no easy way (short of experiementation or a sysctl) for > it to determine whether the 'feature' is present or not. ??? It's in the man page! You *must* handle it, if it's in the man page! You know that there are a number of VOP_CLOSE routines that can return EAGAIN, right? Including ufs_close(). > Also, the idea that the resulting block I/O operation is then queued > and one returns immediately from way down deep in the filesystem device > driver code, and that this whole mess is then tied into select()/kqueue()/ > poll(), is just asking for more non-determinism... now it would > depend on the filesystem AND the OS supporting the feature, and other > UNIX implementations (if they were to adopt the mechanism) would likely > wind up with slightly different semantics, just like O_NONBLOCK on > listen() sockets has wound up being broken on things like HPUX. No. It creates no obligations on the part of applications or other UNIX implementations which are not already there. It doesn't break POSIX semantics. > For example, how would one deal with, say, issuing a million of these > special non-blocking reads() all of which fail. Do we queue a million > I/Os? Do we queue just the last requested I/O? You see the problem? > The API would be unstable and almost certainly implemented differently > on each OS platform. They aren't "special". You handle them by issuing an EAGAIN, if they can't be immediately satisfied. Just like the man page says. I don't think you are understanding. This is not a replacement for AIO. It's a way of touching pages to force them into the buffer cache, rather than blocking. It's permitted by POSIX for read(2) to return EAGAIN to do this. There's no requirement on the queuing of the I/O. I'd suggest that you don't attempt more than one simultaneously on a descriptor though, since it's not going to do anything for you, since each one that fails is going to also fail to use the "resid" value to update the file pointer. So if you issue a million of these for one page, well... you've just asked for the same page to be loaded into memory a million times, because the read(2) system call doesn't advance the file pointer except by the amount of its non-negative return value. 8-) 8-). > A better solution would be to implement a new system call, similar to > pread(), which simply checks the buffer cache and returns a short read > or an error if the data is not present. If the call fails you would > then know that reading that data would block in the disk subsystem and > you could back-off to a more expensive mechanism like AIO. If want > to select() on it you would then simply use kqueue with EVFILT_AIO and > AIO. A system call pread_cache(), or perhaps we could even use > recvmsg() with a flag. Such an interface would not have to touch the > filesystem code, only the buffer cache and the VM page cache, and > could be implemented in less then a day. The pread(2) call isn't even really supported in libc_r. You might as well call this function read(2); I think the same amount of time would be necessary in both cases, and there's no reason to introduce yet another system call. People reading fd's are not supposed to care what they point to under the covers, only about POSIX semantics. I'm not really convinced by your argument that some people might be ignoring the manual page and the POSIX.1 standard, and so be unduly surprised by EAGAIN from a read(2) call on an fd open to an FS file instead of some other fd to a socket or FIFO or some other FS object. -- Terry From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 23:31:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB53D37B401 for ; Wed, 2 Apr 2003 23:31:04 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0131C43F75 for ; Wed, 2 Apr 2003 23:31:04 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h337V1Z30208; Thu, 3 Apr 2003 02:31:01 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Thu, 3 Apr 2003 02:31:01 -0500 (EST) From: Jeff Roberson To: Vallo Kallaste In-Reply-To: <20030403072409.GA1429@kevad.internal> Message-ID: <20030403022937.J64602-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: ULE nice behavior fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 07:31:05 -0000 On Thu, 3 Apr 2003, Vallo Kallaste wrote: > On Wed, Apr 02, 2003 at 07:35:59PM -0500, Jeff Roberson > wrote: > > > Do you know of any problem other than idlepri breakage? I just fixed > > that. I'm about to get on a plane so I don't have time to benchmark it. > > If you have a chance I'd love to see how the most recent fixes effect your > > buildworld time. > > > > I still have to microoptimize the code a bit to get rid of switch > > statements etc, but it all works. > > Interactivity is still worse under ULE. It's quite noticeable and I > tested it on two SMP boxes by running two simple loops in kind of: > for ((;;)); do let $((4+4)); done # this is bash specific > > The loops ran under nice +20. Typing in the xterm is jerky, > characters will not show up immediately, but in small "bursts". I > mean that about three characters typed in will show up immediately, > then small pause happens and a burst of characters (which queued up > in the pause) will show up. This is annoying. Starting up xterm > takes more time as well, but I can live with that. > -- This is strange, I am not seeing any of this behavior. What is the version of your sched_ule.c? I made more changes very recently. Thanks, Jeff From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 23:34:28 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB58E37B401 for ; Wed, 2 Apr 2003 23:34:28 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B75343FB1 for ; Wed, 2 Apr 2003 23:34:27 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id RAA24798; Thu, 3 Apr 2003 17:34:15 +1000 Date: Thu, 3 Apr 2003 17:34:14 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: "Cagle, John (ISS-Houston)" In-Reply-To: Message-ID: <20030403172912.A29833@gamplex.bde.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: RE: sio problem in -current (COM1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 07:34:29 -0000 On Wed, 2 Apr 2003, Cagle, John (ISS-Houston) wrote: > Thanks! It was an ACPI-related problem. I disabled ACPI > (hint.acpi.0.disabled="1" in /boot/device.hints) and rebooted and now > both com ports show up properly as they did with FreeBSD 4.8. (These > are just standard com ports, btw.) We still don't know why acpi sometimes gets this wrong. > I didn't realize ACPI was involved in legacy com port detection. That's > weird. It seems to be used for most legacy ports. IIRC, it found all except 2 or 3 devices according to your boot messages, with the vga devices being an interesting exception (most vga devices are too new to even support pci). Bruce From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 00:58:16 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C581F37B405 for ; Thu, 3 Apr 2003 00:58:11 -0800 (PST) Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de [193.174.154.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BF7643F3F for ; Thu, 3 Apr 2003 00:58:10 -0800 (PST) (envelope-from brandt@fokus.fraunhofer.de) Received: from beagle (beagle [193.175.132.100])h338w9E04619 for ; Thu, 3 Apr 2003 10:58:09 +0200 (MEST) Date: Thu, 3 Apr 2003 10:58:09 +0200 (CEST) From: Harti Brandt To: current@freebsd.org In-Reply-To: <20030403025404.GA90770@unixdaemons.com> Message-ID: <20030403104607.T615@beagle.fokus.fraunhofer.de> References: <20030403025404.GA90770@unixdaemons.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: mbuf LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 08:58:16 -0000 On Wed, 2 Apr 2003, Bosko Milekic wrote: BM> For what concerns DONTWAIT, you should theoretically be allowed to BM> hold a driver lock. But again, there may be a problem. Specifically, BM> I see that UMA code has some explicit Giant acquires/frees in certain BM> places. When the UMA code gets called from the malloc() code while BM> the bucket is being internally allocated in mb_alloc, you may be BM> hitting one of those paths. In fact, unless you have a specific Giant BM> acquire in the fxp_* routines you list in your trace below, that is BM> undoubtedly what is happening because there are no explicit Giant BM> acquires in the code path from m_getcl() to malloc(), so they must be BM> happening higher up in the call stack. Well, that's interesting. A month ago or so I sent a patch to smp@ with an update to the malloc page documenting the locking requirements. I got only one response. I wonder, how people are expected to correctly use an API, when that API is poorly documented (malloc(9) in this case, but mbuf(9) does not mention 'lock' either). I would ask people knowing the topic to comment on this. As soon as this EC proposal nightmare is over, I may try to write a corresponding section for mbuf(9). Regards, harti Index: malloc.9 =================================================================== RCS file: /home/ncvs/src/share/man/man9/malloc.9,v retrieving revision 1.30 diff -u -r1.30 malloc.9 --- malloc.9 24 Feb 2003 05:53:27 -0000 1.30 +++ malloc.9 17 Mar 2003 15:06:14 -0000 @@ -147,44 +147,22 @@ to return .Dv NULL if the request cannot be immediately fulfilled due to resource shortage. -Otherwise, the current process may be put to sleep to wait for -resources to be released by other processes. -If this flag is set, -.Fn malloc -will return -.Dv NULL -rather than block. Note that .Dv M_NOWAIT -is defined to be 0, meaning that blocking operation is the default. -Also note that -.Dv M_NOWAIT is required when running in an interrupt context. -.Pp -Programmers should be careful not to confuse -.Dv M_NOWAIT , -the -.Fn malloc -flag, with -.Dv M_DONTWAIT , -an -.Xr mbuf 9 -allocation flag, which is not a valid argument to -.Fn malloc . .It Dv M_WAITOK -Indicates that it is Ok to wait for resources. It is unconveniently -defined as 0 so care should be taken never to compare against this value -directly or try to AND it as a flag. The default operation is to block -until the memory allocation succeeds. +Indicates that it is ok to wait for resources. +If the request cannot be immediately fulfilled the current process is put +to sleep to wait for resources to be released by other processes. The .Fn malloc , .Fn realloc , and .Fn reallocf -functions can only return +functions cannot return .Dv NULL if -.Dv M_NOWAIT +.Dv M_WAITOK is specified. .It Dv M_USE_RESERVE Indicates that the system can dig into its reserve in order to obtain the @@ -194,6 +172,12 @@ programming. .El .Pp +Exactly one of either +.Dv M_WAITOK +or +.Dv M_NOWAIT +must be specified. +.Pp The .Fa type argument is used to perform statistics on memory usage, and for @@ -244,11 +228,37 @@ While it should not be relied upon, this information may be useful for optimizing the efficiency of memory use. .Pp -Malloc flags documented above should -.Em NOT -be used with +Programmers should be careful not to confuse the malloc flags +.Dv M_NOWAIT +and +.Dv M_WAITOK +with the .Xr mbuf 9 -routines as it will cause undesired results. +flags +.Dv M_DONTWAIT +and +.Dv M_TRYWAIT . +.Sh LOCKING CONSIDERATIONS +.Fn malloc , +.Fn realloc +and +.Fn reallocf +may not be called from fast interrupts handlers. +When called from threaded interrupts +.Ar flag +must contain +.Dv M_NOWAIT . +.Pp +.Fn malloc , +.Fn realloc +and +.Fn reallocf +must not be called with +.Dv M_WAITOK +while a mutex other than Giant is held. +Giant may or may not be held when +.Fn free +is called. .Pp Any calls to .Fn malloc -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fraunhofer.de, harti@freebsd.org From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 03:19:42 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A687D37B426; Thu, 3 Apr 2003 03:19:41 -0800 (PST) Received: from pop015.verizon.net (pop015pub.verizon.net [206.46.170.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id B037F43F85; Thu, 3 Apr 2003 03:19:40 -0800 (PST) (envelope-from mtm@identd.net) Received: from kokeb.ambesa.net ([138.88.47.167]) by pop015.verizon.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP id <20030403111939.QDSE1728.pop015.verizon.net@kokeb.ambesa.net>; Thu, 3 Apr 2003 05:19:39 -0600 Date: Thu, 3 Apr 2003 06:19:38 -0500 From: Mike Makonnen To: freebsd-current@freebsd.org X-Mailer: Sylpheed version 0.8.10 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at pop015.verizon.net from [138.88.47.167] at Thu, 3 Apr 2003 05:19:39 -0600 Message-Id: <20030403111939.QDSE1728.pop015.verizon.net@kokeb.ambesa.net> Subject: resource limits Giant patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 11:19:42 -0000 The following patches at http://people.freebsd.org/~mtm remove process resource limits out from under Giant. I have been bouncing them off jhb for a while now, and I think they are ready. I would appreciate a review/testing.... There are 4 incremental patches for your reviewing pleasure :-) infrastructure.diff - The necessary infrastructure to do the locking users.diff - Modify consumers of resource limits to use the locks giant.diff - actually remove Giant from (most of) those areas regen.diff - Regenerated files, if you don't care to regenerate your own The basic implementation: Each plimit now has an associated mutex. To read an individual limit it is sufficient that the proc lock is held. To modify a limit or in situations where you need a consitent view of a particular limit(s) both the proc lock and the plimit locks are held. Three new functions can be use to get limits: lim_cur(), lim_max(), and lim_rlimit(), that can be used to obtain the current limit, the hard limit, and the entire rlimit structure, respectively. A limit_lock has been defined to protect the following three globals: maxfiles, maxfilesperproc, and maxprocperuid They each now have their own sysctl proc that grabs the limit_lock in order to write them. Cheers. -- Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc mtm@identd.net | D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9 From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 03:27:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B945E37B401 for ; Thu, 3 Apr 2003 03:27:04 -0800 (PST) Received: from pop017.verizon.net (pop017pub.verizon.net [206.46.170.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id D86B043F93 for ; Thu, 3 Apr 2003 03:27:03 -0800 (PST) (envelope-from mtm@identd.net) Received: from kokeb.ambesa.net ([138.88.47.167]) by pop017.verizon.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP id <20030403112702.PTBE1817.pop017.verizon.net@kokeb.ambesa.net> for ; Thu, 3 Apr 2003 05:27:02 -0600 Date: Thu, 3 Apr 2003 06:27:02 -0500 From: Mike Makonnen To: freebsd-current@freebsd.org In-Reply-To: <20030403111939.QDSE1728.pop015.verizon.net@kokeb.ambesa.net> References: <20030403111939.QDSE1728.pop015.verizon.net@kokeb.ambesa.net> X-Mailer: Sylpheed version 0.8.10 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at pop017.verizon.net from [138.88.47.167] at Thu, 3 Apr 2003 05:27:02 -0600 Message-Id: <20030403112702.PTBE1817.pop017.verizon.net@kokeb.ambesa.net> Subject: Re: resource limits Giant patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 11:27:05 -0000 err http://people.freebsd.org/~mtm/limits From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 04:40:47 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C0E637B401 for ; Thu, 3 Apr 2003 04:40:47 -0800 (PST) Received: from MX3.estpak.ee (ld3.estpak.ee [194.126.101.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DE6543F85 for ; Thu, 3 Apr 2003 04:40:46 -0800 (PST) (envelope-from kalts@estpak.ee) Received: from kevad.internal (80-235-38-172-dsl.mus.estpak.ee [80.235.38.172]) by MX3.estpak.ee (Postfix) with ESMTP id 4495288059; Thu, 3 Apr 2003 15:40:40 +0300 (EEST) Received: (from vallo@localhost) by kevad.internal (8.12.9/8.12.9/Submit) id h33CecTA002911; Thu, 3 Apr 2003 15:40:38 +0300 (EEST) (envelope-from vallo) Date: Thu, 3 Apr 2003 15:40:38 +0300 From: Vallo Kallaste To: Jeff Roberson Message-ID: <20030403124038.GA2852@kevad.internal> References: <20030403072409.GA1429@kevad.internal> <20030403022937.J64602-100000@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030403022937.J64602-100000@mail.chesapeake.net> User-Agent: Mutt/1.5.3i-ja.1 cc: current@freebsd.org Subject: Re: ULE nice behavior fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kalts@estpak.ee List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 12:40:47 -0000 On Thu, Apr 03, 2003 at 02:31:01AM -0500, Jeff Roberson wrote: > > Interactivity is still worse under ULE. It's quite noticeable and I > > tested it on two SMP boxes by running two simple loops in kind of: > > for ((;;)); do let $((4+4)); done # this is bash specific > > > > The loops ran under nice +20. Typing in the xterm is jerky, > > characters will not show up immediately, but in small "bursts". I > > mean that about three characters typed in will show up immediately, > > then small pause happens and a burst of characters (which queued up > > in the pause) will show up. This is annoying. Starting up xterm > > takes more time as well, but I can live with that. > > This is strange, I am not seeing any of this behavior. What is the > version of your sched_ule.c? I made more changes very recently. /usr/src/sys/kern/sched_ule.c: $FreeBSD: src/sys/kern/sched_ule.c,v 1.19 2003/04/02 08:22:33 jeff Exp $ I see it's up to version 1.20 now, will it matter? ULE seems faster to me than 4BSD when the loops aren't running or only one loop is running. Anyway, you are definitely making progress in huge steps, it's much-much better than it was when you first committed it. Thank you. -- Vallo Kallaste From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 05:09:36 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A06E337B401 for ; Thu, 3 Apr 2003 05:09:36 -0800 (PST) Received: from ib.com.ua (ib.com.ua [217.144.67.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC76943FDF for ; Thu, 3 Apr 2003 05:09:32 -0800 (PST) (envelope-from toha@ib.com.ua) Received: from ib.com.ua (localhost.ib.com.ua [127.0.0.1]) by ib.com.ua (8.12.9/8.12.7) with ESMTP id h33D6SFJ029827 for ; Thu, 3 Apr 2003 16:06:28 +0300 (EEST) (envelope-from toha@ib.com.ua) Received: (from toha@localhost) by ib.com.ua (8.12.9/8.12.8/Submit) id h33D6RrG029826 for freebsd-current@freebsd.org; Thu, 3 Apr 2003 16:06:27 +0300 (EEST) Date: Thu, 3 Apr 2003 16:06:27 +0300 (EEST) From: Anton Yudin Message-Id: <200304031306.h33D6RrG029826@ib.com.ua> To: freebsd-current@freebsd.org Subject: release and floppies X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 13:09:36 -0000 How to fix problem with floppies > 1457664 bytes? P.S. please, CC me From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 05:42:09 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 652C337B401 for ; Thu, 3 Apr 2003 05:42:09 -0800 (PST) Received: from quicksilver.ukc.ac.uk (quicksilver.ukc.ac.uk [129.12.21.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E7B543FD7 for ; Thu, 3 Apr 2003 05:42:08 -0800 (PST) (envelope-from mark@markdnet.demon.co.uk) Received: from stue9f4.ukc.ac.uk ([129.12.233.244] helo=markdnet.demon.co.uk) by quicksilver.ukc.ac.uk with esmtp (Exim 3.22 #4) id 1914w5-0005nX-00 for freebsd-current@freebsd.org; Thu, 03 Apr 2003 14:39:21 +0100 Message-ID: <3E8C3A35.6060704@markdnet.demon.co.uk> Date: Thu, 03 Apr 2003 14:42:13 +0100 From: Mark Dixon User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-gb, en, en-us MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-UKC-Mail-System: No virus detected Subject: Re: Kernel panic - never had one before, what do I do? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 13:42:09 -0000 > > >I just got a panic. As I have never had one before, I don't know what to >do. It's on another system so I don't have to reboot immediately (that >would solve the problem temporarily, wouldn't it?) if someone would give >me some advice, I could try to help debug it; however, as I'm not a >coder (not a real one anyway), I don't know how much help I would be. > I've got a nasty one booting with today's current. Think I vaguely recall seeing it before, so sorry if this is known. I'm gathering this data using the pen 'n paper approach, so if its not exactly right, you knwo why: ad4 READ Command timeout tag=0 serv=0 -resetting ata2: resetting devices Fatal trap 12: page fault while in kernel mode fault virtual address: 0x0 fault code: supervisor read, page not present instr pointer: 0x8:0xC0160441 [note this is a custom kernel] stack pointer: 0x10:0xd1d6fc84 frame pointer: 0x10:0xd1d6fc8c code segment: base 0x0 limit 0xfffff type 0x1b DPL 0, pres 1, defy2 1, gron 1 processor effage: interrupt enabled, rswen, IOPC=0 current process = 12 (swi7: tty:sio check) kernel: type 12 trap, code = 0 stopped at reinit_bus+0xb: movl[something i can't read] 0(%esi), %eaf db> trace [i saw someone else do this] reinit_bus(0,2,c11f0c00, d1d6fcbc, c0146462) at reinit_bus+0x0 atapicam_reinit_bus(c11f0c00, 1, c338da80, c3470800, c015732c) at atapi_cam_reinit_bus+0x13 ata_reinit(c11f0c00, 7, c338da0, d1d6fcf0, c024c071) at ata_reinit+[something - possibly 0x34c] [more stuff - losing the will to live at this stage] Hope that helps somebody, shame i can't read my own writing. Mark From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 05:45:02 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 541FE37B401 for ; Thu, 3 Apr 2003 05:45:02 -0800 (PST) Received: from fiinbeck.math.ntnu.no (fiinbeck.math.ntnu.no [129.241.15.140]) by mx1.FreeBSD.org (Postfix) with SMTP id A3BC943F3F for ; Thu, 3 Apr 2003 05:45:00 -0800 (PST) (envelope-from hanche@math.ntnu.no) Received: (qmail 76486 invoked from network); 3 Apr 2003 13:44:59 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 3 Apr 2003 13:44:59 -0000 To: toha@ib.com.ua In-Reply-To: <200304031306.h33D6RrG029826@ib.com.ua> References: <200304031306.h33D6RrG029826@ib.com.ua> X-Mailer: Mew version 1.94.2 on Emacs 21.2 / Mule 5.0 (SAKAKI) X-URL: http://www.math.ntnu.no/~hanche/ Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 8bit Message-Id: <20030403154459W.hanche@math.ntnu.no> Date: Thu, 03 Apr 2003 15:44:59 +0200 From: Harald Hanche-Olsen X-Dispatcher: imput version 20000228(IM140) Lines: 11 cc: freebsd-current@freebsd.org Subject: Re: release and floppies X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 13:45:02 -0000 + Anton Yudin : | How to fix problem with floppies > 1457664 bytes? By not downloading a new release before it's announced. Just wait, a corrected version of 4.8-RELEASE without this problem will appear. Wait a little longer, for the official announcement. Then get it. OK? - Harald From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 06:05:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E30737B401 for ; Thu, 3 Apr 2003 06:05:38 -0800 (PST) Received: from ib.com.ua (ib.com.ua [217.144.67.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id D660D43F75 for ; Thu, 3 Apr 2003 06:05:35 -0800 (PST) (envelope-from toha@ib.com.ua) Received: from ib.com.ua (localhost.ib.com.ua [127.0.0.1]) by ib.com.ua (8.12.9/8.12.7) with ESMTP id h33E2VFJ030976; Thu, 3 Apr 2003 17:02:31 +0300 (EEST) (envelope-from toha@ib.com.ua) Received: (from toha@localhost) by ib.com.ua (8.12.9/8.12.8/Submit) id h33E2Vbn030975; Thu, 3 Apr 2003 17:02:31 +0300 (EEST) Date: Thu, 3 Apr 2003 17:02:31 +0300 (EEST) From: Anton Yudin Message-Id: <200304031402.h33E2Vbn030975@ib.com.ua> To: hanche@math.ntnu.no, toha@ib.com.ua In-Reply-To: <20030403154459W.hanche@math.ntnu.no> cc: freebsd-current@freebsd.org Subject: Re: release and floppies X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 14:05:38 -0000 > + Anton Yudin : > > | How to fix problem with floppies > 1457664 bytes? > > By not downloading a new release before it's announced. Just wait, a > corrected version of 4.8-RELEASE without this problem will appear. > Wait a little longer, for the official announcement. Then get it. > > OK? but i'm building 5.0-CURRENT, not STABLE From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 06:51:47 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1BCB37B401; Thu, 3 Apr 2003 06:51:47 -0800 (PST) Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74EF543F93; Thu, 3 Apr 2003 06:51:46 -0800 (PST) (envelope-from mb@imp.ch) Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9]) by mail.imp.ch (8.12.6p2/8.12.3) with ESMTP id h33EpiNT087780; Thu, 3 Apr 2003 16:51:45 +0200 (CEST) (envelope-from Martin.Blapp@imp.ch) Date: Thu, 3 Apr 2003 16:51:43 +0200 (CEST) From: Martin Blapp To: freebsd-current@freebsd.org Message-ID: <20030403164959.B91371@cvs.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: jeffr@freebsd.org Subject: Apache2 in per-child mode (was Re: libthr and 1:1 threading) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 14:51:48 -0000 Hi all, Just a note. Apache2 in per-child mode now works with freebsd, while it deadlocked in the old libc_r on STABLE and CURRENT. Thank you very much ! Martin From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 07:24:23 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 072E537B401 for ; Thu, 3 Apr 2003 07:24:23 -0800 (PST) Received: from goku.city-net.com (mail.city-net.com [198.144.32.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 450F243F93 for ; Thu, 3 Apr 2003 07:24:22 -0800 (PST) (envelope-from billm@craftmfg.com) Received: from mail.craftmfg.com ([198.144.45.208]) by goku.city-net.com (8.12.1/8.12.1) with ESMTP id h33FVG6d19293832 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 3 Apr 2003 10:31:16 -0500 (EST) Received: from newws3 ([172.24.56.97]) by mail.craftmfg.com (8.12.6p2/8.12.6) with SMTP id h33FOKIk008573 for ; Thu, 3 Apr 2003 10:24:20 -0500 (EST) (envelope-from billm@craftmfg.com) Message-ID: <002101c2f9f5$199eb390$613818ac@craftmfg.com> From: "Bill Moran" To: Date: Thu, 3 Apr 2003 10:24:21 -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 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: DVD burning under 5.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 15:24:23 -0000 I'm looking at creating a machine for backing up/archiving other FreeBSD servers. One of the requirements will be burning DVDs (as some archives are 2-3g directories - difficult to break up) So the question I'm asking is: Is anyone actually using DVD burning under FreeBSD 5? If so, what make/model burner? Also, how compatible are the resultant DVDs? (i.e. can I toss one in a Windows XP machine DVD reader and browse the files?) Any problems or gotchas? Looking for success stories and real-world information. I know the release notes claim compatibiltiy, but I'm curious as to folks experiences. Also, I'm aware of the status of 5 as -CURRENT still, and I'm posting a second email asking for opinions on stability. Thanks in advance for any information. -Bill From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 07:30:11 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA0D737B401 for ; Thu, 3 Apr 2003 07:30:11 -0800 (PST) Received: from goku.city-net.com (mail.city-net.com [198.144.32.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FFEE43FCB for ; Thu, 3 Apr 2003 07:30:10 -0800 (PST) (envelope-from billm@craftmfg.com) Received: from mail.craftmfg.com ([198.144.45.208]) by goku.city-net.com (8.12.1/8.12.1) with ESMTP id h33Fb46d19280501 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 3 Apr 2003 10:37:04 -0500 (EST) Received: from newws3 ([172.24.56.97]) by mail.craftmfg.com (8.12.6p2/8.12.6) with SMTP id h33FU8Ik008604 for ; Thu, 3 Apr 2003 10:30:08 -0500 (EST) (envelope-from billm@craftmfg.com) Message-ID: <002901c2f9f5$e909c2f0$613818ac@craftmfg.com> From: "Bill Moran" To: Date: Thu, 3 Apr 2003 10:30:09 -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 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Overall "feel" for the stability of FreeBSD 5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 15:30:12 -0000 I'm considering setting up a FreeBSD 5 machine as a dedicated backup/archive computer on a network I administer. I'm curious to hear some opinions on how wise this is. I know that 5 is still in a -CURRENT status and I've seen (and repeated) the warnings that it's not really production quality yet. So I'm curious as to a number of facets of its capibilities: 1) With the current developmet effort ... does it seem like 5.1 will be -STABLE ... or do folks feel that a -STABLE brand is further off (5.2?) 2) For a dedicated backup server, that can tolerate the performance problems that folks have been reporting, and won't upset the entire office if it panics on occasion, is 5 good enough at this point? I know this is inviting a lot of opinion and conjecture ... but I need some idea of where I can go with this. These folks need a solution soon, and I don't want to pass on something that's not ready yet. On the flip side, the nature of the beast means that it doesn't NEED to be a reliable as I normally expect a FreeBSD server to be, so there's a little more tolerance than usual. Any input is greatly appreciated. -Bill From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 10:26:37 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68A4D37B401 for ; Thu, 3 Apr 2003 10:26:37 -0800 (PST) Received: from goku.city-net.com (mail.city-net.com [198.144.32.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 746DD43FE0 for ; Thu, 3 Apr 2003 10:26:36 -0800 (PST) (envelope-from billm@craftmfg.com) Received: from mail.craftmfg.com (mail.craftmfg.com [198.144.45.208]) by goku.city-net.com (8.12.1/8.12.1) with ESMTP id h33IXP6d19505736 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 3 Apr 2003 13:33:25 -0500 (EST) Received: from newws3 ([172.24.56.97]) by mail.craftmfg.com (8.12.6p2/8.12.6) with SMTP id h33IQWIk009238; Thu, 3 Apr 2003 13:26:32 -0500 (EST) (envelope-from billm@craftmfg.com) Message-ID: <001001c2fa0e$8dca5990$613818ac@craftmfg.com> From: "Bill Moran" To: "Matthew Emmerton" , References: <002901c2f9f5$e909c2f0$613818ac@craftmfg.com> <003b01c2fa01$257ac7b0$1200a8c0@gsicomp.on.ca> Date: Thu, 3 Apr 2003 13:26:33 -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 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Re: Overall "feel" for the stability of FreeBSD 5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 18:26:37 -0000 From: "Matthew Emmerton" > From: "Bill Moran" > > I'm considering setting up a FreeBSD 5 machine as a dedicated > > backup/archive computer on a network I administer. > > > > I'm curious to hear some opinions on how wise this is. I know > > that 5 is still in a -CURRENT status and I've seen (and repeated) > > the warnings that it's not really production quality yet. > > > > So I'm curious as to a number of facets of its capibilities: > > 1) With the current developmet effort ... does it seem like 5.1 > > will be -STABLE ... or do folks feel that a -STABLE brand > > is further off (5.2?) > > 2) For a dedicated backup server, that can tolerate the > > performance problems that folks have been reporting, and > > won't upset the entire office if it panics on occasion, is 5 > > good enough at this point? > > > > I know this is inviting a lot of opinion and conjecture ... but I need > > some idea of where I can go with this. These folks need a solution > > soon, and I don't want to pass on something that's not ready yet. > > On the flip side, the nature of the beast means that it doesn't NEED > > to be a reliable as I normally expect a FreeBSD server to be, so > > there's a little more tolerance than usual. > > > > Any input is greatly appreciated. > > What's wrong with 4.8-RELEASE? Doesn't support DVD burning. Sorry ... forgot to specify my reasons ;) From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 10:36:14 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D23737B401 for ; Thu, 3 Apr 2003 10:36:13 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A84A43F75 for ; Thu, 3 Apr 2003 10:36:12 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.9/8.12.9) with ESMTP id h33IaBMS029205 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 3 Apr 2003 13:36:11 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h33Ia6A32496; Thu, 3 Apr 2003 13:36:06 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16012.32534.331966.216694@grasshopper.cs.duke.edu> Date: Thu, 3 Apr 2003 13:36:06 -0500 (EST) To: Nate Lawson In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: current@freebsd.org Subject: Re: mbuf LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 18:36:14 -0000 Nate Lawson writes: > I was testing some changes to make fxp MPSAFE and got a LOR in allocating > the mbuf cluster and then finally a panic when trying to dereference the > cluster header. Is the mbuf system MPSAFE? Is it ok to call m_getcl > with a device lock held (but not Giant)? > > The lock reversal was: 1. fxp softc lock, 2. Giant. > > Traceback: > zalloc... > malloc() > mb_pop_cont() > mb_alloc() > m_getcl() > fxp_add_rfabuf() > fxp_intr_body() > fxp_intr() -- locks fxp softc > > -Nate I think the only place it can be coming from is slab_zalloc(). Does the appended (untested) patch help? BTW, I don't think that there is any need to get Giant for the zone allocators in the M_NOWAIT case, but I'm not really familar with the code, and I don't know if the sparc64 uma_small_alloc needs Giant. BTW, my MPSAFE driver never sees this, but then again, I never allocate clusters. I use jumbo frames, and carve out my own recv buffers, so I'm only allocating mbufs, not clusters. Drew Index: uma_core.c =================================================================== RCS file: /home/ncvs/src/sys/vm/uma_core.c,v retrieving revision 1.51 diff -u -r1.51 uma_core.c --- uma_core.c 26 Mar 2003 18:44:53 -0000 1.51 +++ uma_core.c 3 Apr 2003 18:22:14 -0000 @@ -703,10 +703,14 @@ wait &= ~M_ZERO; if (booted || (zone->uz_flags & UMA_ZFLAG_PRIVALLOC)) { - mtx_lock(&Giant); - mem = zone->uz_allocf(zone, - zone->uz_ppera * UMA_SLAB_SIZE, &flags, wait); - mtx_unlock(&Giant); + if ((wait & M_NOWAIT) == 0) { + mtx_lock(&Giant); + mem = zone->uz_allocf(zone, + zone->uz_ppera * UMA_SLAB_SIZE, &flags, wait); + mtx_unlock(&Giant); + } else { + mem = NULL; + } if (mem == NULL) { ZONE_LOCK(zone); return (NULL); From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 10:53:02 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CAD237B401 for ; Thu, 3 Apr 2003 10:53:02 -0800 (PST) Received: from tomts12-srv.bellnexxia.net (tomts12.bellnexxia.net [209.226.175.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1F0943FB1 for ; Thu, 3 Apr 2003 10:53:00 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from gabby.gsicomp.on.ca ([65.95.176.5]) by tomts12-srv.bellnexxia.netESMTP <20030403185258.VBJR20288.tomts12-srv.bellnexxia.net@gabby.gsicomp.on.ca>; Thu, 3 Apr 2003 13:52:58 -0500 Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by gabby.gsicomp.on.ca (8.12.6/8.12.6) with SMTP id h33InviG046739; Thu, 3 Apr 2003 13:49:57 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <00ed01c2fa12$00534e10$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Bill Moran" , References: <002901c2f9f5$e909c2f0$613818ac@craftmfg.com> <003b01c2fa01$257ac7b0$1200a8c0@gsicomp.on.ca> <001001c2fa0e$8dca5990$613818ac@craftmfg.com> Date: Thu, 3 Apr 2003 13:51:13 -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 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Re: Overall "feel" for the stability of FreeBSD 5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 18:53:02 -0000 ----- Original Message ----- From: "Bill Moran" To: "Matthew Emmerton" ; Sent: Thursday, April 03, 2003 1:26 PM Subject: Re: Overall "feel" for the stability of FreeBSD 5 > From: "Matthew Emmerton" > > From: "Bill Moran" > > > I'm considering setting up a FreeBSD 5 machine as a dedicated > > > backup/archive computer on a network I administer. > > > > > > I'm curious to hear some opinions on how wise this is. I know > > > that 5 is still in a -CURRENT status and I've seen (and repeated) > > > the warnings that it's not really production quality yet. > > > > > > So I'm curious as to a number of facets of its capibilities: > > > 1) With the current developmet effort ... does it seem like 5.1 > > > will be -STABLE ... or do folks feel that a -STABLE brand > > > is further off (5.2?) > > > 2) For a dedicated backup server, that can tolerate the > > > performance problems that folks have been reporting, and > > > won't upset the entire office if it panics on occasion, is 5 > > > good enough at this point? > > > > > > I know this is inviting a lot of opinion and conjecture ... but I need > > > some idea of where I can go with this. These folks need a solution > > > soon, and I don't want to pass on something that's not ready yet. > > > On the flip side, the nature of the beast means that it doesn't NEED > > > to be a reliable as I normally expect a FreeBSD server to be, so > > > there's a little more tolerance than usual. > > > > > > Any input is greatly appreciated. > > > > What's wrong with 4.8-RELEASE? > > Doesn't support DVD burning. > > Sorry ... forgot to specify my reasons ;) What is the piece you're missing -- UDF filesystem support or ata driver support? I've seen patches to 4-STABLE to add UDF filesystem support. Perhaps that's all you need. -- Matt Emmerton From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 10:58:30 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E447937B401 for ; Thu, 3 Apr 2003 10:58:30 -0800 (PST) Received: from goku.city-net.com (mail.city-net.com [198.144.32.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id F100043FAF for ; Thu, 3 Apr 2003 10:58:29 -0800 (PST) (envelope-from billm@craftmfg.com) Received: from mail.craftmfg.com (mail.craftmfg.com [198.144.45.208]) by goku.city-net.com (8.12.1/8.12.1) with ESMTP id h33J5K6d19552252 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 3 Apr 2003 14:05:20 -0500 (EST) Received: from newws3 ([172.24.56.97]) by mail.craftmfg.com (8.12.6p2/8.12.6) with SMTP id h33IwRIk009378; Thu, 3 Apr 2003 13:58:27 -0500 (EST) (envelope-from billm@craftmfg.com) Message-ID: <002001c2fa13$0358d070$613818ac@craftmfg.com> From: "Bill Moran" To: "Matthew Emmerton" , References: <002901c2f9f5$e909c2f0$613818ac@craftmfg.com> <003b01c2fa01$257ac7b0$1200a8c0@gsicomp.on.ca> <001001c2fa0e$8dca5990$613818ac@craftmfg.com> <00ed01c2fa12$00534e10$1200a8c0@gsicomp.on.ca> Date: Thu, 3 Apr 2003 13:58:28 -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 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Re: Overall "feel" for the stability of FreeBSD 5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 18:58:31 -0000 From: "Matthew Emmerton" > From: "Bill Moran" > > From: "Matthew Emmerton" > > > From: "Bill Moran" > > > > I'm considering setting up a FreeBSD 5 machine as a dedicated > > > > backup/archive computer on a network I administer. > > > > > > > > I'm curious to hear some opinions on how wise this is. I know > > > > that 5 is still in a -CURRENT status and I've seen (and repeated) > > > > the warnings that it's not really production quality yet. > > > > > > > > So I'm curious as to a number of facets of its capibilities: > > > > 1) With the current developmet effort ... does it seem like 5.1 > > > > will be -STABLE ... or do folks feel that a -STABLE brand > > > > is further off (5.2?) > > > > 2) For a dedicated backup server, that can tolerate the > > > > performance problems that folks have been reporting, and > > > > won't upset the entire office if it panics on occasion, is 5 > > > > good enough at this point? > > > > > > > > I know this is inviting a lot of opinion and conjecture ... but I need > > > > some idea of where I can go with this. These folks need a solution > > > > soon, and I don't want to pass on something that's not ready yet. > > > > On the flip side, the nature of the beast means that it doesn't NEED > > > > to be a reliable as I normally expect a FreeBSD server to be, so > > > > there's a little more tolerance than usual. > > > > > > > > Any input is greatly appreciated. > > > > > > What's wrong with 4.8-RELEASE? > > > > Doesn't support DVD burning. > > > > Sorry ... forgot to specify my reasons ;) > > What is the piece you're missing -- UDF filesystem support or ata driver > support? I don't know ... hence my posting. I'm still in the "planning" stages of this project. Budget doesn't allow me to purchase the required hardware until I'm fairly certain that I have a method to make it work (obviously, there's always some chance of unexpected problems, but I'm trying to gather enough information to minimize that) > I've seen patches to 4-STABLE to add UDF filesystem support. Perhaps that's > all you need. I'll google a bit ... but links would be welcome ;) Thanks for the help so far, Matt. -Bill From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 11:01:42 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BC9637B401 for ; Thu, 3 Apr 2003 11:01:42 -0800 (PST) Received: from alpha.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74D0C43FA3 for ; Thu, 3 Apr 2003 11:01:40 -0800 (PST) (envelope-from culverk@yumyumyum.org) Received: from alpha.yumyumyum.org (localhost [127.0.0.1]) by alpha.yumyumyum.org (8.12.8/8.12.6) with ESMTP id h33J14sF083242; Thu, 3 Apr 2003 14:01:04 -0500 (EST) (envelope-from culverk@yumyumyum.org) Received: from localhost (culverk@localhost)h33J13iT083239; Thu, 3 Apr 2003 14:01:03 -0500 (EST) (envelope-from culverk@yumyumyum.org) X-Authentication-Warning: alpha.yumyumyum.org: culverk owned process doing -bs Date: Thu, 3 Apr 2003 14:01:03 -0500 (EST) From: Kenneth Culver To: Matthias Buelow In-Reply-To: <20030403030829.GD3941@moghedien.mukappabeta.net> Message-ID: <20030403140028.J83219-100000@alpha.yumyumyum.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-2.1 required=5.0 tests=IN_REP_TO,X_AUTH_WARNING,DOUBLE_CAPSWORD,AWL version=2.31 cc: freebsd-current@freebsd.org Subject: Re: linux-emu ioctl not implemented w/ quake3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 19:01:42 -0000 I'd say this is a video card driver issue, because with my geforce3 and the nvidia drivers I could run q3 for as long as I wanted without any issues. Ken On Thu, 3 Apr 2003, Matthias Buelow wrote: > Hi folks, > > I'm running 5.0-RELEASE-p7 on i386 and investigated how quake3 (linux) > would be doing at the moment. I had some relative success on 4.7 > (quake3 ran ok, in 3d acceleration, but only for about 30 seconds, at > which point the whole machine froze solid) so I hoped it might just > work out. This time at least it didn't freeze but I don't even get so > far. When I run quake3.x86, I get the following: > > quake3 spits: > > Using XFree86-VidModeExtension Version 2.2 > XFree86-VidModeExtension Activated at 640x480 > libGL error: failed to open DRM: Operation not permitted > ... > (at which point it offers me to use Mesa software rendering > as a fallback which, of course, works...) > > and the kernel says: > > Apr 3 04:59:23 reiher kernel: linux: 'ioctl' fd=13, cmd=0x6401 ('d',1) not implemented > > Does anybody know what ioctl that would be? I didn't get that on 4.7, > is linux-emu divergent between -stable and -current? > > The relevant ktrace excerpt follows: > > ... > 1713 quake3.x86 RET old.setrlimit 12/0xc > 1713 quake3.x86 CALL ftruncate > 1713 quake3.x86 RET ftruncate 1000/0x3e8 > 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri" > 1713 quake3.x86 NAMI "/dev/dri" > 1713 quake3.x86 RET setrlimit 0 > 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card0" > 1713 quake3.x86 NAMI "/dev/dri/card0" > 1713 quake3.x86 RET setrlimit 0 > 1713 quake3.x86 CALL open(0xbfbfeb00,0x2,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card0" > 1713 quake3.x86 NAMI "/dev/dri/card0" > 1713 quake3.x86 RET open 13/0xd > 1713 quake3.x86 CALL ioctl(0xd,0xc0086401 ,0xbfbfec00) > 1713 quake3.x86 RET ioctl -1 errno -22 Unknown error: -22 > 1713 quake3.x86 CALL close(0xd) > 1713 quake3.x86 RET close 0 > 1713 quake3.x86 CALL ftruncate > 1713 quake3.x86 RET ftruncate 1000/0x3e8 > 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri" > 1713 quake3.x86 NAMI "/dev/dri" > 1713 quake3.x86 RET setrlimit 0 > 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card1" > 1713 quake3.x86 NAMI "/dev/dri/card1" > 1713 quake3.x86 RET setrlimit JUSTRETURN > 1713 quake3.x86 CALL ftruncate > 1713 quake3.x86 RET ftruncate 1000/0x3e8 > 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri" > 1713 quake3.x86 NAMI "/dev/dri" > 1713 quake3.x86 RET setrlimit 0 > 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card2" > 1713 quake3.x86 NAMI "/dev/dri/card2" > 1713 quake3.x86 RET setrlimit JUSTRETURN > 1713 quake3.x86 CALL ftruncate > 1713 quake3.x86 RET ftruncate 1000/0x3e8 > 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri" > 1713 quake3.x86 NAMI "/dev/dri" > 1713 quake3.x86 RET setrlimit 0 > 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card3" > 1713 quake3.x86 NAMI "/dev/dri/card3" > 1713 quake3.x86 RET setrlimit JUSTRETURN > 1713 quake3.x86 CALL ftruncate > 1713 quake3.x86 RET ftruncate 1000/0x3e8 > 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri" > 1713 quake3.x86 NAMI "/dev/dri" > 1713 quake3.x86 RET setrlimit 0 > 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card4" > 1713 quake3.x86 NAMI "/dev/dri/card4" > 1713 quake3.x86 RET setrlimit JUSTRETURN > 1713 quake3.x86 CALL ftruncate > 1713 quake3.x86 RET ftruncate 1000/0x3e8 > 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri" > 1713 quake3.x86 NAMI "/dev/dri" > 1713 quake3.x86 RET setrlimit 0 > 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card5" > 1713 quake3.x86 NAMI "/dev/dri/card5" > 1713 quake3.x86 RET setrlimit JUSTRETURN > 1713 quake3.x86 CALL ftruncate > 1713 quake3.x86 RET ftruncate 1000/0x3e8 > 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri" > 1713 quake3.x86 NAMI "/dev/dri" > 1713 quake3.x86 RET setrlimit 0 > 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card6" > 1713 quake3.x86 NAMI "/dev/dri/card6" > 1713 quake3.x86 RET setrlimit JUSTRETURN > 1713 quake3.x86 CALL ftruncate > 1713 quake3.x86 RET ftruncate 1000/0x3e8 > 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri" > 1713 quake3.x86 NAMI "/dev/dri" > 1713 quake3.x86 RET setrlimit 0 > 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card7" > 1713 quake3.x86 NAMI "/dev/dri/card7" > 1713 quake3.x86 RET setrlimit JUSTRETURN > 1713 quake3.x86 CALL ftruncate > 1713 quake3.x86 RET ftruncate 1000/0x3e8 > 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri" > 1713 quake3.x86 NAMI "/dev/dri" > 1713 quake3.x86 RET setrlimit 0 > 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card8" > 1713 quake3.x86 NAMI "/dev/dri/card8" > 1713 quake3.x86 RET setrlimit JUSTRETURN > 1713 quake3.x86 CALL ftruncate > 1713 quake3.x86 RET ftruncate 1000/0x3e8 > 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri" > 1713 quake3.x86 NAMI "/dev/dri" > 1713 quake3.x86 RET setrlimit 0 > 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card9" > 1713 quake3.x86 NAMI "/dev/dri/card9" > 1713 quake3.x86 RET setrlimit JUSTRETURN > 1713 quake3.x86 CALL ftruncate > 1713 quake3.x86 RET ftruncate 1000/0x3e8 > 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri" > 1713 quake3.x86 NAMI "/dev/dri" > 1713 quake3.x86 RET setrlimit 0 > 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card10" > 1713 quake3.x86 NAMI "/dev/dri/card10" > 1713 quake3.x86 RET setrlimit JUSTRETURN > 1713 quake3.x86 CALL ftruncate > 1713 quake3.x86 RET ftruncate 1000/0x3e8 > 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri" > 1713 quake3.x86 NAMI "/dev/dri" > 1713 quake3.x86 RET setrlimit 0 > 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card11" > 1713 quake3.x86 NAMI "/dev/dri/card11" > 1713 quake3.x86 RET setrlimit JUSTRETURN > 1713 quake3.x86 CALL ftruncate > 1713 quake3.x86 RET ftruncate 1000/0x3e8 > 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri" > 1713 quake3.x86 NAMI "/dev/dri" > 1713 quake3.x86 RET setrlimit 0 > 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card12" > 1713 quake3.x86 NAMI "/dev/dri/card12" > 1713 quake3.x86 RET setrlimit JUSTRETURN > 1713 quake3.x86 CALL ftruncate > 1713 quake3.x86 RET ftruncate 1000/0x3e8 > 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri" > 1713 quake3.x86 NAMI "/dev/dri" > 1713 quake3.x86 RET setrlimit 0 > 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card13" > 1713 quake3.x86 NAMI "/dev/dri/card13" > 1713 quake3.x86 RET setrlimit JUSTRETURN > 1713 quake3.x86 CALL ftruncate > 1713 quake3.x86 RET ftruncate 1000/0x3e8 > 1713 quake3.x86 CALL setrlimit(0x2cea6c30,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri" > 1713 quake3.x86 NAMI "/dev/dri" > 1713 quake3.x86 RET setrlimit 0 > 1713 quake3.x86 CALL setrlimit(0xbfbfeb00,0xbfbfea00,0) > 1713 quake3.x86 NAMI "/compat/linux/dev/dri/card14" > 1713 quake3.x86 NAMI "/dev/dri/card14" > 1713 quake3.x86 RET setrlimit JUSTRETURN > 1713 quake3.x86 CALL write(0x2,0xbfbfc540,0x39) > 1713 quake3.x86 GIO fd 2 wrote 57 bytes > "libGL error: failed to open DRM: Operation not permitted > " > 1713 quake3.x86 RET write 57/0x39 > ... > > --mkb > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 11:05:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4912637B404; Thu, 3 Apr 2003 11:05:30 -0800 (PST) Received: from core.zp.ua (core.zp.ua [193.108.112.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id E08BC43F75; Thu, 3 Apr 2003 11:05:15 -0800 (PST) (envelope-from oleg@core.zp.ua) Received: from core.zp.ua (oleg@localhost [127.0.0.1]) by core.zp.ua with ESMTPœ id h33J574k084877; Thu, 3 Apr 2003 22:05:07 +0300 (EEST) (envelope-from oleg@core.zp.ua)œ Received: (from oleg@localhost) by core.zp.ua id h33J539G084876; Thu, 3 Apr 2003 22:05:03 +0300 (EEST) Date: Thu, 3 Apr 2003 22:05:03 +0300 From: "Oleg V. Nauman" To: Nate Williams Message-ID: <20030403190503.GC82393@core.zp.ua> Mail-Followup-To: Nate Williams , Gregory Neil Shapiro , freebsd-current@freebsd.org References: <16011.4537.279737.406477@horsey.gshapiro.net> <16011.7467.322808.498405@emerger.yogotech.com> <20030402205754.GF75212@core.zp.ua> <16011.25002.138504.661813@emerger.yogotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <16011.25002.138504.661813@emerger.yogotech.com> User-Agent: Mutt/1.5.3i cc: Gregory Neil Shapiro cc: freebsd-current@freebsd.org Subject: Re: sendmail: no local mailer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 19:05:33 -0000 On Wed, Apr 02, 2003 at 03:18:18PM -0700, Nate Williams wrote: > > > > evantd> Sendmail has not been working on my system for some time now. I > > > > evantd> can't say exactly how long, but my guess is that it broke when I > > > > evantd> upgraded to RELENG_5_0. This is how sendmail is invoked (by > > > > evantd> default) and it's output. > > > > > > > > evantd> # sendmail -L sm-mta -bd -q30m -ODaemonPortOptions=Addr=localhost > > > > evantd> 451 4.0.0 No local mailer defined: Bad address > > > > evantd> 554 5.0.0 QueueDirectory (Q) option must be set > > > > > > > > /etc/mail/sendmail.cf is a bogus (empty?) file. One way to fix this is: > > > > > > > > cd /etc/mail > > > > mv sendmail.cf sendmail.cf~bogus > > > > make > > > > make restart > > > > > > This happened on one of my -stable boxes lately when doing a upgrade > > > using buildworld. For some (unknown) reason m4 bombed out and created > > > an empty .cf file. > > > > > > I fixed it by doing something similar to what was done above, although > > > why m4 failed is a mystery.... > > > > Some patch: > > > > --- /usr/src/etc/sendmail/Makefile.orig Wed Apr 2 23:51:19 2003 > > +++ /usr/src/etc/sendmail/Makefile Wed Apr 2 23:51:50 2003 > > @@ -1,7 +1,7 @@ > > # @(#)Makefile 8.19 (Berkeley) 1/14/97 > > # $FreeBSD: src/etc/sendmail/Makefile,v 1.21 2002/07/29 09:40:06 ru Exp $ > > > > -M4= m4 > > +M4= /usr/bin/m4 > > CHMOD= chmod > > ROMODE= 444 > > RM= rm -f > > > > This shouldn't be necessary, since m4 is in the path in buildworld, is installworld, you meant? > it not? Otherwise, we wouldn't be able to run make, cc, or any other > tools. ok... this was under slightly patched /usr/src/etc/sendmail/Makefile: --- /usr/src/etc/sendmail/Makefile.orig Thu Apr 3 19:47:54 2003 +++ /usr/src/etc/sendmail/Makefile Thu Apr 3 21:18:23 2003 @@ -18,6 +18,7 @@ .mc.cf: ${M4FILES} ${RM} ${.TARGET} (cd ${.CURDIR} && \ + set | /usr/bin/grep PATH > /tmp/installworld.path 2>&1 ; \ ${M4} -D_CF_DIR_=${CFDIR}/ ${SENDMAIL_M4_FLAGS} \ ${CFDIR}/m4/cf.m4 ${@:R}.mc) > ${.TARGET} ${CHMOD} ${ROMODE} ${.TARGET} So, after some installworld's activity: rm -f /etc/mail/vega.cf (cd /usr/src/etc/sendmail && set | /usr/bin/grep PATH > /tmp/installworld.path 2>&1 ; m4 -D_CF_DIR_=/usr/src/etc/sendmail/../../contrib/sendmail/cf/ /usr/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 /etc/mail/vega.mc) > /etc/mail/vega.cf m4: not found ^^^^^^^^^^^^^ *** Error code 127 Stop in /usr/src/etc/sendmail. *** Error code 1 Stop in /usr/src/etc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. # more /tmp/installworld.path GROFF_FONT_PATH=/usr/obj/usr/src/i386/usr/share/groff_font PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/s rc/i386/usr/games:/tmp/install.84736 GROFF_TMAC_PATH=/usr/obj/usr/src/i386/usr/share/tmac GROFF_BIN_PATH=/usr/obj/usr/src/i386/usr/bin OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec #sh # export PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr /obj/usr/src/i386/usr/games:/tmp/install.84736 # /usr/bin/which m4 # ^D # which m4 /usr/bin/m4 # ls -al /etc/mail/*.cf -rw-r--r-- 1 root wheel 57079 Apr 3 20:45 /etc/mail/sendmail.cf -rw-r--r-- 1 root wheel 0 Apr 3 21:33 /etc/mail/vega.cf ^^^^ # uname -a FreeBSD vega.reis.zp.ua 4.8-RC FreeBSD 4.8-RC #1: Sun Mar 30 12:52:49 EEST 2003 root@vega.reis.zp.ua:/usr/src/sys/compile/Vega i386 Yes, this was attempt to 'make installworld' from NFS-mounted /usr/src and /usr/obj. So, /usr/src/etc/sendmail/Makefile definitely should define M4 as /usr/bin/m4. > > > > Nate -- NO37-RIPE From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 11:05:36 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CD4E37B401 for ; Thu, 3 Apr 2003 11:05:36 -0800 (PST) Received: from tomts15-srv.bellnexxia.net (tomts15.bellnexxia.net [209.226.175.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D40143FA3 for ; Thu, 3 Apr 2003 11:05:34 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from gabby.gsicomp.on.ca ([65.95.176.5]) by tomts17-srv.bellnexxia.netESMTP <20030403165222.QIEY2665.tomts17-srv.bellnexxia.net@gabby.gsicomp.on.ca>; Thu, 3 Apr 2003 11:52:22 -0500 Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by gabby.gsicomp.on.ca (8.12.6/8.12.6) with SMTP id h33GnJiG046397; Thu, 3 Apr 2003 11:49:19 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <003b01c2fa01$257ac7b0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Bill Moran" , References: <002901c2f9f5$e909c2f0$613818ac@craftmfg.com> Date: Thu, 3 Apr 2003 11:50:33 -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 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Re: Overall "feel" for the stability of FreeBSD 5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 19:05:37 -0000 ----- Original Message ----- From: "Bill Moran" To: Sent: Thursday, April 03, 2003 10:30 AM Subject: Overall "feel" for the stability of FreeBSD 5 > I'm considering setting up a FreeBSD 5 machine as a dedicated > backup/archive computer on a network I administer. > > I'm curious to hear some opinions on how wise this is. I know > that 5 is still in a -CURRENT status and I've seen (and repeated) > the warnings that it's not really production quality yet. > > So I'm curious as to a number of facets of its capibilities: > 1) With the current developmet effort ... does it seem like 5.1 > will be -STABLE ... or do folks feel that a -STABLE brand > is further off (5.2?) > 2) For a dedicated backup server, that can tolerate the > performance problems that folks have been reporting, and > won't upset the entire office if it panics on occasion, is 5 > good enough at this point? > > I know this is inviting a lot of opinion and conjecture ... but I need > some idea of where I can go with this. These folks need a solution > soon, and I don't want to pass on something that's not ready yet. > On the flip side, the nature of the beast means that it doesn't NEED > to be a reliable as I normally expect a FreeBSD server to be, so > there's a little more tolerance than usual. > > Any input is greatly appreciated. What's wrong with 4.8-RELEASE? -- Matt Emmerton From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 12:22:33 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81C3937B404 for ; Thu, 3 Apr 2003 12:22:33 -0800 (PST) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF75743FDF for ; Thu, 3 Apr 2003 12:22:32 -0800 (PST) (envelope-from scott_long@btc.adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h33KKuZ06165; Thu, 3 Apr 2003 12:20:56 -0800 Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [10.100.0.52]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id MAA20692; Thu, 3 Apr 2003 12:21:43 -0800 (PST) Received: from btc.adaptec.com ([10.20.80.159]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id NAA13016; Thu, 3 Apr 2003 13:21:37 -0700 (MST) Message-ID: <3E8C97CE.3060205@btc.adaptec.com> Date: Thu, 03 Apr 2003 13:21:34 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2.1) Gecko/20030206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthew Emmerton References: <002901c2f9f5$e909c2f0$613818ac@craftmfg.com> <003b01c2fa01$257ac7b0$1200a8c0@gsicomp.on.ca> <001001c2fa0e$8dca5990$613818ac@craftmfg.com> <00ed01c2fa12$00534e10$1200a8c0@gsicomp.on.ca> In-Reply-To: <00ed01c2fa12$00534e10$1200a8c0@gsicomp.on.ca> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Bill Moran cc: freebsd-current@freebsd.org Subject: Re: Overall "feel" for the stability of FreeBSD 5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 20:22:33 -0000 Matthew Emmerton wrote: > ----- Original Message ----- > From: "Bill Moran" > To: "Matthew Emmerton" ; > Sent: Thursday, April 03, 2003 1:26 PM > Subject: Re: Overall "feel" for the stability of FreeBSD 5 > > > >>From: "Matthew Emmerton" >> >>>From: "Bill Moran" >>> >>>>I'm considering setting up a FreeBSD 5 machine as a dedicated >>>>backup/archive computer on a network I administer. >>>> >>>>I'm curious to hear some opinions on how wise this is. I know >>>>that 5 is still in a -CURRENT status and I've seen (and repeated) >>>>the warnings that it's not really production quality yet. >>>> >>>>So I'm curious as to a number of facets of its capibilities: >>>>1) With the current developmet effort ... does it seem like 5.1 >>>> will be -STABLE ... or do folks feel that a -STABLE brand >>>> is further off (5.2?) >>>>2) For a dedicated backup server, that can tolerate the >>>> performance problems that folks have been reporting, and >>>> won't upset the entire office if it panics on occasion, is 5 >>>> good enough at this point? >>>> >>>>I know this is inviting a lot of opinion and conjecture ... but I need >>>>some idea of where I can go with this. These folks need a solution >>>>soon, and I don't want to pass on something that's not ready yet. >>>>On the flip side, the nature of the beast means that it doesn't NEED >>>>to be a reliable as I normally expect a FreeBSD server to be, so >>>>there's a little more tolerance than usual. >>>> >>>>Any input is greatly appreciated. >>> >>>What's wrong with 4.8-RELEASE? >> >>Doesn't support DVD burning. >> >>Sorry ... forgot to specify my reasons ;) > > > What is the piece you're missing -- UDF filesystem support or ata driver > support? > The UDF support in 5.x is for reading only. DVD data disks do not require the UDF filesystem and can in fact work just fine with cd9660 or even UFS. DVD video disks usually require UDF as dvd players don't understand anything else, but editing and mastering a dvd video disk is well beyond the scope of this and I would highly recommend using a Mac. Burning some of the DVD formats requires special support, while others can be burned just like a CD. I thought that 4.x and 5.x were at the same level for this support, but Soeren would have the definitive answer. > I've seen patches to 4-STABLE to add UDF filesystem support. Perhaps that's > all you need. Really? I thought that the backporting effort had died out. Can you provide a link? Scott From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 12:30:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9E8E37B401; Thu, 3 Apr 2003 12:30:06 -0800 (PST) Received: from goku.city-net.com (mail.city-net.com [198.144.32.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DCE343F85; Thu, 3 Apr 2003 12:30:05 -0800 (PST) (envelope-from billm@craftmfg.com) Received: from mail.craftmfg.com (mail.craftmfg.com [198.144.45.208]) by goku.city-net.com (8.12.1/8.12.1) with ESMTP id h33Kar6d19417218 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 3 Apr 2003 15:36:54 -0500 (EST) Received: from newws3 ([172.24.56.97]) by mail.craftmfg.com (8.12.6p2/8.12.6) with SMTP id h33KTwIk009851; Thu, 3 Apr 2003 15:29:58 -0500 (EST) (envelope-from billm@craftmfg.com) Message-ID: <005001c2fa1f$cd756bf0$613818ac@craftmfg.com> From: "Bill Moran" To: "Scott Long" , "Matthew Emmerton" References: <002901c2f9f5$e909c2f0$613818ac@craftmfg.com> <003b01c2fa01$257ac7b0$1200a8c0@gsicomp.on.ca> <001001c2fa0e$8dca5990$613818ac@craftmfg.com> <00ed01c2fa12$00534e10$1200a8c0@gsicomp.on.ca> <3E8C97CE.3060205@btc.adaptec.com> Date: Thu, 3 Apr 2003 15:30:00 -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 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 cc: freebsd-current@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: Overall "feel" for the stability of FreeBSD 5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 20:30:07 -0000 This discussion is getting off-topic for this list, I think. I'm redirecting to -questions, unless you feel your reply is relevent to 5, please remove the cc to -current if you reply (more below) ... From: "Scott Long" > Matthew Emmerton wrote: > > From: "Bill Moran" > >>From: "Matthew Emmerton" > >> > >>>From: "Bill Moran" > >>> > >>>>I'm considering setting up a FreeBSD 5 machine as a dedicated > >>>>backup/archive computer on a network I administer. > >>>> > >>>>I'm curious to hear some opinions on how wise this is. I know > >>>>that 5 is still in a -CURRENT status and I've seen (and repeated) > >>>>the warnings that it's not really production quality yet. > >>>> > >>>>So I'm curious as to a number of facets of its capibilities: > >>>>1) With the current developmet effort ... does it seem like 5.1 > >>>> will be -STABLE ... or do folks feel that a -STABLE brand > >>>> is further off (5.2?) > >>>>2) For a dedicated backup server, that can tolerate the > >>>> performance problems that folks have been reporting, and > >>>> won't upset the entire office if it panics on occasion, is 5 > >>>> good enough at this point? > >>>> > >>>>I know this is inviting a lot of opinion and conjecture ... but I need > >>>>some idea of where I can go with this. These folks need a solution > >>>>soon, and I don't want to pass on something that's not ready yet. > >>>>On the flip side, the nature of the beast means that it doesn't NEED > >>>>to be a reliable as I normally expect a FreeBSD server to be, so > >>>>there's a little more tolerance than usual. > >>>> > >>>>Any input is greatly appreciated. > >>> > >>>What's wrong with 4.8-RELEASE? > >> > >>Doesn't support DVD burning. > >> > >>Sorry ... forgot to specify my reasons ;) > > > > What is the piece you're missing -- UDF filesystem support or ata driver > > support? > > The UDF support in 5.x is for reading only. DVD data disks do not > require the UDF filesystem and can in fact work just fine with cd9660 or > even UFS. DVD video disks usually require UDF as dvd players don't > understand anything else, but editing and mastering a dvd video disk is > well beyond the scope of this and I would highly recommend using a Mac. For the record ... my only requirement at this time is to burn data DVDs that are compatible across multiple OSes (specifically, FreeBSD, Mac, and Windows). From what I'm hearing, I can accomplish this with cd9660 fs. I wasn't aware of this ... I thought I needed UDF support for 4G filesystems, but that's all the more reason I'm glad I asked. > Burning some of the DVD formats requires special support, while others > can be burned just like a CD. I thought that 4.x and 5.x were at the > same level for this support, but Soeren would have the definitive > answer. > > > I've seen patches to 4-STABLE to add UDF filesystem support. Perhaps that's > > all you need. > > Really? I thought that the backporting effort had died out. Can you > provide a link? I found this: http://www.whiterose.net/~mrpink/freebsd/dvdr.php Which seemed very promising. I contacted the author and he says that he's been burning DVD data backups with no problems ever since he wrote the article. I assume the capibilities in 5 are equal or better than those in 4, but (as you stated) Soeren would know for sure. I'll try to contact him next ... I'm sure he's been doing nothing but sitting around waiting for someone like me to pester him ;) Thanks for the input, Bill From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 12:40:58 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFCA137B401 for ; Thu, 3 Apr 2003 12:40:58 -0800 (PST) Received: from moghedien.mukappabeta.net (moghedien.mukappabeta.net [194.145.150.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25B3A43F3F for ; Thu, 3 Apr 2003 12:40:58 -0800 (PST) (envelope-from mkb@moghedien.mukappabeta.net) Received: by moghedien.mukappabeta.net (Postfix, from userid 1000) id 500A82C9B; Thu, 3 Apr 2003 22:41:14 +0200 (CEST) Date: Thu, 3 Apr 2003 22:41:14 +0200 From: Matthias Buelow To: freebsd-current@freebsd.org Message-ID: <20030403204113.GA4910@moghedien.mukappabeta.net> References: <20030403030829.GD3941@moghedien.mukappabeta.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030403030829.GD3941@moghedien.mukappabeta.net> User-Agent: Mutt/1.4.1i Subject: Re: linux-emu ioctl not implemented w/ quake3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 20:40:59 -0000 I wrote: >Using XFree86-VidModeExtension Version 2.2 >XFree86-VidModeExtension Activated at 640x480 >libGL error: failed to open DRM: Operation not permitted Ok, I hadn't seen so far the instructions for 5.0 on Eric Anholts website... in fact, I needed to include a few lines into the kernel config and rebuild; in my case: device mgadrm options COMPAT_LINUX options DRM_LINUX did the trick. Now quake seems to work stable, although it seems to be much slower than on Windoze, the cinematics don't work and I get a good amount of garbage (flickering etc.) between frames but it's playable, and above all, doesn't crash the machine. --mkb From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 12:55:55 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C915D37B401 for ; Thu, 3 Apr 2003 12:55:55 -0800 (PST) Received: from ns.altadena.net (ns.altadena.net [207.151.161.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02F8743FD7 for ; Thu, 3 Apr 2003 12:55:53 -0800 (PST) (envelope-from pete@ns.altadena.net) Received: from ns.altadena.net (localhost [127.0.0.1]) by ns.altadena.net (8.12.6p2/8.12.3) with ESMTP id h33KtmLn011649 for ; Thu, 3 Apr 2003 12:55:48 -0800 (PST) (envelope-from pete@ns.altadena.net) Received: (from pete@localhost) by ns.altadena.net (8.12.6p2/8.12.3/Submit) id h33KtmsX011648 for current@freebsd.org; Thu, 3 Apr 2003 12:55:48 -0800 (PST) (envelope-from pete) From: Pete Carah Message-Id: <200304032055.h33KtmsX011648@ns.altadena.net> To: current@freebsd.org Date: Thu, 3 Apr 2003 12:55:48 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit Subject: FXP breakage X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 20:55:56 -0000 This may be just my infamous vaio acting up again, but since the recent commit to fxp driver (Monday?) I get a panic on device probe (page fault in kernel mode). That and the way the pccbb act up (always return 0 for event and status register reads, and don't reset pending interrupt on event reg write) make me think that something is awry with the way acpi/pci allocate memory for the device windows. I know there is something funny with the aml/asl since almost everything ends up on irq 9 also... I also sometimes see the lock order problem with pcm but mostly just missing interrupts (choppy sound that comes out slow but in the right order). PCM is responding to display interrupts... -- Pete From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 12:55:40 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8A7037B401; Thu, 3 Apr 2003 12:55:40 -0800 (PST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE6EF43FBF; Thu, 3 Apr 2003 12:55:39 -0800 (PST) (envelope-from marks@ripe.net) Received: from laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.9/8.11.6) with SMTP id h33KtcRp018050; Thu, 3 Apr 2003 22:55:38 +0200 Received: (nullmailer pid 3161 invoked by uid 1000); Thu, 03 Apr 2003 20:55:25 -0000 Date: Thu, 3 Apr 2003 22:55:25 +0200 From: Mark Santcroos To: Craig Boston Message-ID: <20030403205524.GA2346@laptop.6bone.nl> References: <1049304662.10796.27.camel@owen1492.uf.corelab.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1049304662.10796.27.camel@owen1492.uf.corelab.com> User-Agent: Mutt/1.4.1i X-Handles: MS6-6BONE, MS18417-RIPE X-Mailman-Approved-At: Thu, 03 Apr 2003 12:59:24 -0800 cc: net@freebsd.org Subject: Re: IPv6 MTU bug? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 20:55:41 -0000 [ moved to net@; current@ bcc'ed ] Hi Craig, I think I saw the same behaviour while developing a path-mtu discovery tool. As I'm quite busy right now I didn't really dig into it, but I will at some point. I took the liberty to reply to freebsd-net@, because this is not only a -CURRENT problem. Mark On Wed, Apr 02, 2003 at 11:31:02AM -0600, Craig Boston wrote: > I was trying some network diagnostics yesterday and needed to generate a > continuous stream of small packets going across a few routers. So I > used ifconfig to set my MTU to some very low values (100, 300, 500, and > a few others). I know there's probably a better way to accomplish that, > but couldn't think of any at the time so that's what I did :) > > Anyway, when I was done, I reset the MTU on my ethernet interface back > to 1500. IPv4 is working fine, but IPv6 is still acting like I have a > low MTU set. All IPv6 TCP connections are limiting the MSS to around 28 > bytes of data per packet, and ping6 complains with ping sizes more than > around 50. > > I think I've tracked down the problem to this code in nd6.c, > specifically in nd6_setmtu(ifp). > > Note that at this point ndi->maxmtu has just been set to > MIN([user-requested MTU], [biggest MTU possible for this interface > type]). ndi->linkmtu hasn't been touched yet and is still set to > whatever the previous linkmtu was. > > if (ndi->linkmtu == 0 || > ndi->maxmtu < ndi->linkmtu) { > ndi->linkmtu = ndi->maxmtu; > /* also adjust in6_maxmtu if necessary. */ > if (oldlinkmtu == 0) { > /* > * XXX: the case analysis is grotty, but > * it is not efficient to call in6_setmaxmtu() > * here when we are during the initialization > * procedure. > */ > if (in6_maxmtu < ndi->linkmtu) > in6_maxmtu = ndi->linkmtu; > } else > in6_setmaxmtu(); > } > > It looks to me that in the case of raising an interface's MTU, > ndi->maxmtu will be >= ndi->linkmtu, causing linkmtu to never get > reset. I may be missing something, but I can't quite figure out the > logical reason for that test. > > Luckily I had a kernel.debug lying around so I used gdb to peek into the > kernel memory. In the nd_ifinfo for that interface, linkmtu=100 and > maxmtu=1500. Once I manually reset linkmtu to 1500, IPv6 started > working properly again, without having to sacrifice my uptime :) > > Anyway, the behavior looks like a bug, but the code makes it look like > this may be an intentional effect. Any kernel networking gurus care to > comment? > > Thanks, > Craig > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 12:59:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB5BE37B405 for ; Thu, 3 Apr 2003 12:59:35 -0800 (PST) Received: from moghedien.mukappabeta.net (moghedien.mukappabeta.net [194.145.150.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id A938243F3F for ; Thu, 3 Apr 2003 12:59:32 -0800 (PST) (envelope-from mkb@moghedien.mukappabeta.net) Received: by moghedien.mukappabeta.net (Postfix, from userid 1000) id A8CCE2C9B; Thu, 3 Apr 2003 22:59:48 +0200 (CEST) Date: Thu, 3 Apr 2003 22:59:48 +0200 From: Matthias Buelow To: Bill Moran Message-ID: <20030403205948.GA4929@moghedien.mukappabeta.net> References: <002901c2f9f5$e909c2f0$613818ac@craftmfg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002901c2f9f5$e909c2f0$613818ac@craftmfg.com> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: Overall "feel" for the stability of FreeBSD 5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 20:59:38 -0000 Bill Moran writes: >2) For a dedicated backup server, that can tolerate the > performance problems that folks have been reporting, and > won't upset the entire office if it panics on occasion, is 5 > good enough at this point? If the system isn't really too critical, I'd go for it. I'm running 5.0 in workstation use and had some problems with agp and X11 up until 5.0-RELEASE-p7, on which I haven't had a crash or freeze yet and all seems to be stable. I'm using scsi and ide on that machine. Apart from the agp/graphics/X11 problem and one (I think) related kernel panic I've experienced with < -p7, I've not seen any problems. IMHO it's stable enough for use in a relaxed production environment. The more people who engage in testing it, the more problems (also cutting edges in the userland) get ironed out, and the faster that will happen. --mkb From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 12:59:39 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E74837B408 for ; Thu, 3 Apr 2003 12:59:39 -0800 (PST) Received: from mail.tcoip.com.br (erato.tco.net.br [200.220.254.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5823F43FDD for ; Thu, 3 Apr 2003 12:59:36 -0800 (PST) (envelope-from dcs@tcoip.com.br) Received: from tcoip.com.br ([10.0.2.6]) by mail.tcoip.com.br (8.11.6/8.11.6) with ESMTP id h33KxT927890 for ; Thu, 3 Apr 2003 17:59:29 -0300 Message-ID: <3E8CA0B0.8060200@tcoip.com.br> Date: Thu, 03 Apr 2003 17:59:28 -0300 From: "Daniel C. Sobral" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030326 X-Accept-Language: en-us, en, pt-br, ja MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Panic on fxp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 20:59:39 -0000 It seems recent current doesn't like my fxp. A current from some 10 hours ago keeps complaining about device timeout and dma timeout. I don't *know* it's fxp fault (for one thing, because it says "unknown"), but... So, two hours ago, I cvsupped and tried a new world. This one panics on boot, while doing something with fxp (attaching, I think), and doesn't even get me a core dump. I'll try a new world tomorrow. People tweaking fxp, do please try to get it fixed? -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: Daniel.Capo@tco.net.br Daniel.Sobral@tcoip.com.br dcs@tcoip.com.br Outros: dcs@newsguy.com dcs@freebsd.org capo@notorious.bsdconspiracy.net Experience is something you don't get until just after you need it. -- Olivier From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 13:02:14 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF14F37B401 for ; Thu, 3 Apr 2003 13:02:14 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 681F643F85 for ; Thu, 3 Apr 2003 13:02:14 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id 519B42A8A5; Thu, 3 Apr 2003 13:02:14 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: "Daniel C. Sobral" In-Reply-To: <3E8CA0B0.8060200@tcoip.com.br> Date: Thu, 03 Apr 2003 13:02:14 -0800 From: Peter Wemm Message-Id: <20030403210214.519B42A8A5@canning.wemm.org> cc: current@freebsd.org Subject: Re: Panic on fxp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 21:02:15 -0000 "Daniel C. Sobral" wrote: > It seems recent current doesn't like my fxp. A current from some 10 > hours ago keeps complaining about device timeout and dma timeout. I > don't *know* it's fxp fault (for one thing, because it says "unknown"), > but... > > So, two hours ago, I cvsupped and tried a new world. This one panics on > boot, while doing something with fxp (attaching, I think), and doesn't > even get me a core dump. > > I'll try a new world tomorrow. People tweaking fxp, do please try to get > it fixed? Some details would be useful. Pencil and paper perhaps? Serial cable to another machine and boot -h? Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 13:06:26 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2AD5537B401 for ; Thu, 3 Apr 2003 13:06:26 -0800 (PST) Received: from mail.tcoip.com.br (erato.tco.net.br [200.220.254.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30A5B43F3F for ; Thu, 3 Apr 2003 13:06:24 -0800 (PST) (envelope-from dcs@tcoip.com.br) Received: from tcoip.com.br ([10.0.2.6]) by mail.tcoip.com.br (8.11.6/8.11.6) with ESMTP id h33L6G928143; Thu, 3 Apr 2003 18:06:16 -0300 Message-ID: <3E8CA248.7010000@tcoip.com.br> Date: Thu, 03 Apr 2003 18:06:16 -0300 From: "Daniel C. Sobral" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030326 X-Accept-Language: en-us, en, pt-br, ja MIME-Version: 1.0 To: Peter Wemm References: <20030403210214.519B42A8A5@canning.wemm.org> In-Reply-To: <20030403210214.519B42A8A5@canning.wemm.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: Panic on fxp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 21:06:26 -0000 Peter Wemm wrote: > "Daniel C. Sobral" wrote: > >>It seems recent current doesn't like my fxp. A current from some 10 >>hours ago keeps complaining about device timeout and dma timeout. I >>don't *know* it's fxp fault (for one thing, because it says "unknown"), >>but... >> >>So, two hours ago, I cvsupped and tried a new world. This one panics on >>boot, while doing something with fxp (attaching, I think), and doesn't >>even get me a core dump. >> >>I'll try a new world tomorrow. People tweaking fxp, do please try to get >>it fixed? > > > Some details would be useful. Pencil and paper perhaps? Serial cable > to another machine and boot -h? I'll have to see if I can manage a serial cable here. It shouldn't be difficult, I just have never done it before, let alone on this computer, so I don't know what traps I might fall into. If not that, I'll get at least the functions and the offset of the first few. But not today. Tomorrow, after a new cvsup and a new world. I see there were at least two commits to fxp since my last cvsup. -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: Daniel.Capo@tco.net.br Daniel.Sobral@tcoip.com.br dcs@tcoip.com.br Outros: dcs@newsguy.com dcs@freebsd.org capo@notorious.bsdconspiracy.net No wonder you're tired! You understood so much today. From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 13:09:51 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C84637B401 for ; Thu, 3 Apr 2003 13:09:51 -0800 (PST) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCB5E43F93 for ; Thu, 3 Apr 2003 13:09:50 -0800 (PST) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id 9DEE02ED40E; Thu, 3 Apr 2003 13:09:50 -0800 (PST) Date: Thu, 3 Apr 2003 23:09:50 +0200 From: Maxime Henrion To: "Daniel C. Sobral" Message-ID: <20030403210950.GN1750@elvis.mu.org> References: <20030403210214.519B42A8A5@canning.wemm.org> <3E8CA248.7010000@tcoip.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E8CA248.7010000@tcoip.com.br> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: Panic on fxp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 21:09:51 -0000 Daniel C. Sobral wrote: > Peter Wemm wrote: > >"Daniel C. Sobral" wrote: > > > >>It seems recent current doesn't like my fxp. A current from some 10 > >>hours ago keeps complaining about device timeout and dma timeout. I > >>don't *know* it's fxp fault (for one thing, because it says "unknown"), > >>but... > >> > >>So, two hours ago, I cvsupped and tried a new world. This one panics on > >>boot, while doing something with fxp (attaching, I think), and doesn't > >>even get me a core dump. > >> > >>I'll try a new world tomorrow. People tweaking fxp, do please try to get > >>it fixed? > > > > > >Some details would be useful. Pencil and paper perhaps? Serial cable > >to another machine and boot -h? > > I'll have to see if I can manage a serial cable here. It shouldn't be > difficult, I just have never done it before, let alone on this computer, > so I don't know what traps I might fall into. > > If not that, I'll get at least the functions and the offset of the first > few. But not today. Tomorrow, after a new cvsup and a new world. I see > there were at least two commits to fxp since my last cvsup. This should be fixed in revision 1.30 of if_fxpreg.h that I committed recently. Sorry for that guys. Cheers, Maxime From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 13:10:11 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4422537B41A for ; Thu, 3 Apr 2003 13:10:11 -0800 (PST) Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B9B843F3F for ; Thu, 3 Apr 2003 13:10:10 -0800 (PST) (envelope-from Robin.Blanchard@gactr.uga.edu) Received: (qmail 82409 invoked from network); 3 Apr 2003 21:10:04 -0000 Received: from unknown (HELO ex.gactr.uga.edu) ([10.10.11.21]) (envelope-sender ) by mail.servers.gactr.gc.nat (qmail-ldap-1.03) with SMTP for ; 3 Apr 2003 21:10:04 -0000 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Thu, 3 Apr 2003 16:10:04 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Panic on fxp Thread-Index: AcL6JOl10Fh/a24ETviqEHwZETl6aQAABcbw From: "Robin P. Blanchard" To: Subject: RE: Panic on fxp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 21:10:11 -0000 I'm seeing the same thing. A kernel from first thing this morning = paniced the kernel whilst attempting to probe the device. I saw a commit go in = shortly after 15.00 and rebuilt the kernel. Kernel built on that commit allows = the box to boot, but the device simply doesn't pass (or see) any traffic...Reverted back to a working kernel from 10March. # ls -ltr /usr/src/sys/dev/fxp/ total 116 -rw-r--r-- 1 root wheel 21318 Oct 25 2001 rcvbundl.h -rw-r--r-- 1 root wheel 8190 Apr 2 13:00 if_fxpvar.h -rw-r--r-- 1 root wheel 73326 Apr 3 11:46 if_fxp.c -rw-r--r-- 1 root wheel 12975 Apr 3 15:14 if_fxpreg.h Peter Wemm wrote: > "Daniel C. Sobral" wrote: >=20 >>It seems recent current doesn't like my fxp. A current from some 10 >>hours ago keeps complaining about device timeout and dma timeout. I=20 >>don't *know* it's fxp fault (for one thing, because it says = "unknown"),=20 >>but... >> >>So, two hours ago, I cvsupped and tried a new world. This one panics=20 >>on >>boot, while doing something with fxp (attaching, I think), and doesn't = >>even get me a core dump. >> >>I'll try a new world tomorrow. People tweaking fxp, do please try to=20 >>get >>it fixed? >=20 >=20 > Some details would be useful. Pencil and paper perhaps? Serial cable = > to another machine and boot -h? From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 13:11:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C4DE37B404 for ; Thu, 3 Apr 2003 13:11:04 -0800 (PST) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id B38DB43F3F for ; Thu, 3 Apr 2003 13:11:03 -0800 (PST) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id A2A3A2ED416; Thu, 3 Apr 2003 13:11:03 -0800 (PST) Date: Thu, 3 Apr 2003 23:11:03 +0200 From: Maxime Henrion To: Pete Carah Message-ID: <20030403211103.GO1750@elvis.mu.org> References: <200304032055.h33KtmsX011648@ns.altadena.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200304032055.h33KtmsX011648@ns.altadena.net> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: FXP breakage X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 21:11:04 -0000 Pete Carah wrote: > This may be just my infamous vaio acting up again, but since the > recent commit to fxp driver (Monday?) I get a panic on device probe > (page fault in kernel mode). This should be fixed in revision 1.30 of if_fxpreg.h that I committed some time ago. Sorry for the inconvenience. Cheers, Maxime From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 13:39:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6A3837B401 for ; Thu, 3 Apr 2003 13:39:38 -0800 (PST) Received: from web14802.mail.yahoo.com (web14802.mail.yahoo.com [216.136.224.218]) by mx1.FreeBSD.org (Postfix) with SMTP id DFF3F43F3F for ; Thu, 3 Apr 2003 13:39:37 -0800 (PST) (envelope-from mccrobie2000@yahoo.com) Message-ID: <20030403213937.48714.qmail@web14802.mail.yahoo.com> Received: from [68.165.211.163] by web14802.mail.yahoo.com via HTTP; Thu, 03 Apr 2003 13:39:37 PST Date: Thu, 3 Apr 2003 13:39:37 -0800 (PST) From: Chuck McCrobie To: Pete Carah In-Reply-To: <200304032055.h33KtmsX011648@ns.altadena.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-current@freebsd.org Subject: Re: FXP breakage X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 21:39:38 -0000 --- Pete Carah wrote: > This may be just my infamous vaio acting up again, > but since the > recent commit to fxp driver (Monday?) I get a panic > on device probe > (page fault in kernel mode). > > That and the way the pccbb act up (always return 0 > for event and > status register reads, and don't reset pending > interrupt on event reg > write) make me think that something is awry with the > way acpi/pci > allocate memory for the device windows. > > I know there is something funny with the aml/asl > since almost everything > ends up on irq 9 also... > > I also sometimes see the lock order problem with pcm > but mostly just missing > interrupts (choppy sound that comes out slow but in > the right order). > PCM is responding to display interrupts... > > -- Pete I wondered what that crash was on boot-up. Sometimes it does boot though! Anyway... I also have almost everything on IRQ9. I'm not sure its FreeBSD - I think its the Vaio :( Just checked Windows 2000 and it lists USB, video, network, firewire, audio _ALL_ on IRQ9. Perhaps your pcm problems come from the interrupt not being delivered at all - try moving a USB mouse while your audio is playing. I have a hacky-hack to make my vaio's audio play normally. I noticed that since the audio and usb share an interrupt, moving a USB mouse gets the pcm interrupt handler called - which results in normal sound. Sorry, I don't have my own web page address handy - I never go there ;) I'll send it privately. Chuck McCrobie mccrobie2000@yahoo.com __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 13:45:54 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06F3637B401 for ; Thu, 3 Apr 2003 13:45:54 -0800 (PST) Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BC4543F75 for ; Thu, 3 Apr 2003 13:45:53 -0800 (PST) (envelope-from Robin.Blanchard@gactr.uga.edu) Received: (qmail 86516 invoked from network); 3 Apr 2003 21:45:52 -0000 Received: from unknown (HELO ex.gactr.uga.edu) ([10.10.11.21]) (envelope-sender ) by mail.servers.gactr.gc.nat (qmail-ldap-1.03) with SMTP for ; 3 Apr 2003 21:45:52 -0000 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Thu, 3 Apr 2003 16:45:52 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Fxp breakage Thread-Index: AcL6KmXp7s6nCv5FR7WIrPURhMsg2Q== From: "Robin P. Blanchard" To: Subject: Fxp breakage X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 21:45:54 -0000 Ok. Hopefully some useful information here....Using a kernel built = against the below fxp sources, the interface simply does not pass or see any = traffic. Reverting back to kernel from 01 April permits the intrace to function properly. fxp0: flags=3D18843 mtu 1500 inet 10.10.10.201 netmask 0xffff0000 broadcast 10.10.255.255 ether 00:90:27:66:62:1a media: Ethernet autoselect (100baseTX ) status: active fxp0: port = 0xe000-0xe03f mem=20 0xf9000000-0xf90fffff,0xf9101000-0xf9101fff irq 10 at device 11.0 on = pci0 fxp0: Ethernet address 00:90:27:66:62:1a fxp0@pci0:11:0: class=3D0x020000 card=3D0x000c8086 chip=3D0x12298086 = rev=3D0x08 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82557/8/9 EtherExpress PRO/100(B) Ethernet Adapter' class =3D network subclass =3D ethernet * $FreeBSD: src/sys/dev/fxp/if_fxpreg.h,v 1.30 2003/04/03 18:39:48 mux = Exp $ # ls -ltr /usr/src/sys/dev/fxp/ total 116 -rw-r--r-- 1 root wheel 21318 Oct 25 2001 rcvbundl.h -rw-r--r-- 1 root wheel 8190 Apr 2 13:00 if_fxpvar.h -rw-r--r-- 1 root wheel 73326 Apr 3 11:46 if_fxp.c -rw-r--r-- 1 root wheel 12975 Apr 3 15:14 if_fxpreg.h ---------------------------------------- Robin P. Blanchard Systems Integration Specialist Georgia Center for Continuing Education fon: 706.542.2404 <|> fax: 706.542.6546 ---------------------------------------- From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 14:08:48 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CD6937B401 for ; Thu, 3 Apr 2003 14:08:48 -0800 (PST) Received: from mail.speakeasy.net (mail14.speakeasy.net [216.254.0.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2A1E43F3F for ; Thu, 3 Apr 2003 14:08:47 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 30132 invoked from network); 3 Apr 2003 22:08:55 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 3 Apr 2003 22:08:55 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.8/8.12.8) with ESMTP id h33M8jOv028421; Thu, 3 Apr 2003 17:08:45 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20030403023827.JfzY5155@hun.org> Date: Thu, 03 Apr 2003 17:08:46 -0500 (EST) From: John Baldwin To: Dr Daniel Flickinger cc: current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 22:08:48 -0000 On 03-Apr-2003 Dr Daniel Flickinger wrote: > Secondly, I add the following to /etc/rc.conf: > > mta_start_script="" # 2917: block their startup stealth attack > sendmail_enable="NO" > sendmail_outbound_enable="NO" > sendmail_msp_queue_enable="NO" > sendmail_submit_enable="NO" sendmail_enable="NONE" should be all you need for rc.conf. Note "NONE" rather than "NO". -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 14:21:28 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 562FD37B401; Thu, 3 Apr 2003 14:21:28 -0800 (PST) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id B50CB43F85; Thu, 3 Apr 2003 14:21:27 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by rwcrmhc52.attbi.com (rwcrmhc52) with ESMTP id <20030403222127052003ktege>; Thu, 3 Apr 2003 22:21:27 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA28212; Thu, 3 Apr 2003 14:21:26 -0800 (PST) Date: Thu, 3 Apr 2003 14:21:25 -0800 (PST) From: Julian Elischer To: Bill Moran In-Reply-To: <005001c2fa1f$cd756bf0$613818ac@craftmfg.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Scott Long cc: freebsd-current@freebsd.org cc: freebsd-questions@freebsd.org Subject: Burning DVDs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 22:21:28 -0000 On Thu, 3 Apr 2003, Bill Moran wrote: > This discussion is getting off-topic for this list, I think. > I'm redirecting to -questions, unless you feel your reply is > relevent to 5, please remove the cc to -current if you reply > (more below) ... > > From: "Scott Long" > > > > The UDF support in 5.x is for reading only. DVD data disks do not > > require the UDF filesystem and can in fact work just fine with cd9660 or > > even UFS. DVD video disks usually require UDF as dvd players don't > > understand anything else, but editing and mastering a dvd video disk is > > well beyond the scope of this and I would highly recommend using a Mac. > > For the record ... my only requirement at this time is to burn data DVDs > that are compatible across multiple OSes (specifically, FreeBSD, Mac, and > Windows). From what I'm hearing, I can accomplish this with cd9660 fs. > I wasn't aware of this ... I thought I needed UDF support for 4G filesystems, > but that's all the more reason I'm glad I asked. > > > Burning some of the DVD formats requires special support, while others > > can be burned just like a CD. I thought that 4.x and 5.x were at the > > same level for this support, but Soeren would have the definitive > > answer. > > the mkisofs port can make UDF images.. add teh -u (I think) option.. seems to work on MACs and Win machines that report the output to be a UDF disk. From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 14:41:42 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F4E637B401 for ; Thu, 3 Apr 2003 14:41:42 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5E5943F93 for ; Thu, 3 Apr 2003 14:41:41 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.9/8.12.7) with ESMTP id h33MfQD0035369; Thu, 3 Apr 2003 14:41:30 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h33MfQ3s035368; Thu, 3 Apr 2003 14:41:26 -0800 (PST) Date: Thu, 3 Apr 2003 14:41:25 -0800 From: "David O'Brien" To: "Robin P. Blanchard" Message-ID: <20030403224125.GA34932@dragon.nuxi.com> Mail-Followup-To: David O'Brien , "Robin P. Blanchard" , current@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: current@freebsd.org Subject: Re: Panic on fxp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 22:41:42 -0000 On Thu, Apr 03, 2003 at 04:10:04PM -0500, Robin P. Blanchard wrote: > # ls -ltr /usr/src/sys/dev/fxp/ > total 116 > -rw-r--r-- 1 root wheel 21318 Oct 25 2001 rcvbundl.h > -rw-r--r-- 1 root wheel 8190 Apr 2 13:00 if_fxpvar.h > -rw-r--r-- 1 root wheel 73326 Apr 3 11:46 if_fxp.c > -rw-r--r-- 1 root wheel 12975 Apr 3 15:14 if_fxpreg.h "fgrep '$FreeBSD' *fxp*" would be more useful. From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 15:19:58 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E953037B401 for ; Thu, 3 Apr 2003 15:19:57 -0800 (PST) Received: from ns1.gnf.org (ns1.gnf.org [63.196.132.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id B79B343FA3 for ; Thu, 3 Apr 2003 15:19:56 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: from EXCHCLUSTER01.lj.gnf.org (exch02.lj.gnf.org [172.25.10.20]) by ns1.gnf.org (8.12.6p2/8.12.3) with ESMTP id h33NJsZu052562 for ; Thu, 3 Apr 2003 15:19:54 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: from roark.gnf.org ([172.25.24.15]) by EXCHCLUSTER01.lj.gnf.org with Microsoft SMTPSVC(5.0.2195.5329); Thu, 3 Apr 2003 15:19:56 -0800 Received: from roark.gnf.org (localhost [127.0.0.1]) by roark.gnf.org (8.12.9/8.12.9) with ESMTP id h33NJuNB086107 for ; Thu, 3 Apr 2003 15:19:56 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: (from gtetlow@localhost) by roark.gnf.org (8.12.9/8.12.9/Submit) id h33NJthN086106 for current@FreeBSD.org; Thu, 3 Apr 2003 15:19:55 -0800 (PST) Date: Thu, 3 Apr 2003 15:19:55 -0800 From: Gordon Tetlow To: current@FreeBSD.org Message-ID: <20030403231955.GS69100@roark.gnf.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CPn8Wy5ME997YUMW" Content-Disposition: inline User-Agent: Mutt/1.4i X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-OriginalArrivalTime: 03 Apr 2003 23:19:56.0306 (UTC) FILETIME=[89DF6720:01C2FA37] Subject: core dump with libthr X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 23:19:58 -0000 --CPn8Wy5ME997YUMW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I got a userland core dump while using privoxy linked against libthr. I don't know if this is libthr specific, but I thought I would report it anyway. This might also explain why kde apps always crash on exit (possibly, not really sure). -gordon GNU gdb 5.2.1 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-undermydesk-freebsd"... (no debugging symbols found)... Core was generated by `privoxy'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libthr.so.1...done. Loaded symbols for /usr/lib/libthr.so.1 Reading symbols from /usr/lib/libc.so.5...done. Loaded symbols for /usr/lib/libc.so.5 Reading symbols from /usr/libexec/ld-elf.so.1...done. Loaded symbols for /usr/libexec/ld-elf.so.1 #0 0x28156824 in flockfile () from /usr/lib/libc.so.5 (gdb) bt #0 0x28156824 in flockfile () from /usr/lib/libc.so.5 #1 0x2813c33a in fgets () from /usr/lib/libc.so.5 #2 0x28136b60 in gethostent () from /usr/lib/libc.so.5 #3 0x28136d87 in _ht_gethostbyname () from /usr/lib/libc.so.5 #4 0x28136663 in nsdispatch () from /usr/lib/libc.so.5 #5 0x28135eac in gethostbyname2 () from /usr/lib/libc.so.5 #6 0x28135e35 in gethostbyname () from /usr/lib/libc.so.5 #7 0x0805a923 in getsockname () #8 0x0805a3f6 in getsockname () #9 0x0805a090 in getsockname () #10 0x0805b0f7 in getsockname () #11 0x0805bd14 in getsockname () #12 0x2809c0f1 in _thread_start (thread=3D0x809df40) at /local/usr.src/lib/libthr/thread/thr_create.c:216 #13 0x28140f33 in _ctx_start () from /usr/lib/libc.so.5 (gdb) frame 12 #12 0x2809c0f1 in _thread_start (thread=3D0x809df40) at /local/usr.src/lib/libthr/thread/thr_create.c:216 216 pthread_exit(thread->start_routine(thread->arg)); (gdb) list 211 _thread_start(pthread_t thread) 212 { 213 thread->arch_id =3D _set_curthread(thread); 214 =20 215 /* Run the current thread's start routine with argument: */ 216 pthread_exit(thread->start_routine(thread->arg)); 217 =20 218 /* This point should never be reached. */ 219 PANIC("Thread has resumed after exit"); 220 } --CPn8Wy5ME997YUMW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+jMGbRu2t9DV9ZfsRAvTbAJ0b3gSoMLFyy8Svf7AItqm7i2aBoACeIGtM OKG/XzBmgoawBEow7RC1P2I= =WwY4 -----END PGP SIGNATURE----- --CPn8Wy5ME997YUMW-- From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 15:22:10 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47AE237B401 for ; Thu, 3 Apr 2003 15:22:10 -0800 (PST) Received: from ns1.gnf.org (ns1.gnf.org [63.196.132.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B88C43FCB for ; Thu, 3 Apr 2003 15:22:09 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: from EXCHCLUSTER01.lj.gnf.org (exch02.lj.gnf.org [172.25.10.20]) by ns1.gnf.org (8.12.6p2/8.12.3) with ESMTP id h33NM7Zu052589 for ; Thu, 3 Apr 2003 15:22:07 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: from roark.gnf.org ([172.25.24.15]) by EXCHCLUSTER01.lj.gnf.org with Microsoft SMTPSVC(5.0.2195.5329); Thu, 3 Apr 2003 15:22:09 -0800 Received: from roark.gnf.org (localhost [127.0.0.1]) by roark.gnf.org (8.12.9/8.12.9) with ESMTP id h33NM8NB086183 for ; Thu, 3 Apr 2003 15:22:08 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: (from gtetlow@localhost) by roark.gnf.org (8.12.9/8.12.9/Submit) id h33NM8Yg086182 for current@FreeBSD.org; Thu, 3 Apr 2003 15:22:08 -0800 (PST) Date: Thu, 3 Apr 2003 15:22:08 -0800 From: Gordon Tetlow To: current@FreeBSD.org Message-ID: <20030403232208.GT69100@roark.gnf.org> References: <20030403231955.GS69100@roark.gnf.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qjXtncIm5b3tWrFJ" Content-Disposition: inline In-Reply-To: <20030403231955.GS69100@roark.gnf.org> User-Agent: Mutt/1.4i X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-OriginalArrivalTime: 03 Apr 2003 23:22:09.0183 (UTC) FILETIME=[D912D2F0:01C2FA37] Subject: Re: core dump with libthr X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 23:22:10 -0000 --qjXtncIm5b3tWrFJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I forgot to mention, this is on a dual Athlon MP 1900+. Here's the appropriate part of the dmesg: CPU: AMD Athlon(TM) MP 1900+ (1600.07-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 Features=0x383fbff AMD Features=0xc0480000 real memory = 1073659904 (1023 MB) avail memory = 1035481088 (987 MB) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 -gordon --qjXtncIm5b3tWrFJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+jMIgRu2t9DV9ZfsRAtLNAJ9iNIm1mv987OPJ+GBmFmj92TP6qgCff+n2 8qHaOgXciTwl5J+RV7mKlN4= =sPl8 -----END PGP SIGNATURE----- --qjXtncIm5b3tWrFJ-- From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 15:43:53 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBAE037B401; Thu, 3 Apr 2003 15:43:53 -0800 (PST) Received: from pop017.verizon.net (pop017pub.verizon.net [206.46.170.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id D857D43FAF; Thu, 3 Apr 2003 15:43:52 -0800 (PST) (envelope-from mtm@identd.net) Received: from kokeb.ambesa.net ([138.88.47.167]) by pop017.verizon.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP id <20030403234352.UJMM1817.pop017.verizon.net@kokeb.ambesa.net>; Thu, 3 Apr 2003 17:43:52 -0600 Date: Thu, 3 Apr 2003 18:43:51 -0500 From: Mike Makonnen To: John Baldwin In-Reply-To: References: <20030403023827.JfzY5155@hun.org> X-Mailer: Sylpheed version 0.8.10 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at pop017.verizon.net from [138.88.47.167] at Thu, 3 Apr 2003 17:43:51 -0600 Message-Id: <20030403234352.UJMM1817.pop017.verizon.net@kokeb.ambesa.net> cc: current@freebsd.org Subject: Re: Removing Sendmail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 23:43:54 -0000 On Thu, 03 Apr 2003 17:08:46 -0500 (EST) John Baldwin wrote: > > On 03-Apr-2003 Dr Daniel Flickinger wrote: > > Secondly, I add the following to /etc/rc.conf: > > > > mta_start_script="" # 2917: block their startup stealth attack > > sendmail_enable="NO" > > sendmail_outbound_enable="NO" > > sendmail_msp_queue_enable="NO" > > sendmail_submit_enable="NO" > > sendmail_enable="NONE" should be all you need for rc.conf. Note > "NONE" rather than "NO". This is deprecated. It's a non-standard option that complicates rc.conf handling. Cheers -- Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc mtm@identd.net | D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9 From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 16:07:05 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3077B37B401; Thu, 3 Apr 2003 16:07:05 -0800 (PST) Received: from ns1.gnf.org (ns1.gnf.org [63.196.132.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C00543F3F; Thu, 3 Apr 2003 16:07:04 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: from EXCHCLUSTER01.lj.gnf.org (exch02.lj.gnf.org [172.25.10.20]) by ns1.gnf.org (8.12.6p2/8.12.3) with ESMTP id h34071Zu052935; Thu, 3 Apr 2003 16:07:01 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: from roark.gnf.org ([172.25.24.15]) by EXCHCLUSTER01.lj.gnf.org with Microsoft SMTPSVC(5.0.2195.5329); Thu, 3 Apr 2003 16:07:03 -0800 Received: from roark.gnf.org (localhost [127.0.0.1]) by roark.gnf.org (8.12.9/8.12.9) with ESMTP id h34073NB087037; Thu, 3 Apr 2003 16:07:03 -0800 (PST) (envelope-from gtetlow@gnf.org) Received: (from gtetlow@localhost) by roark.gnf.org (8.12.9/8.12.9/Submit) id h34073tL087036; Thu, 3 Apr 2003 16:07:03 -0800 (PST) Date: Thu, 3 Apr 2003 16:07:03 -0800 From: Gordon Tetlow To: threads@freebsd.org, current@freebsd.org Message-ID: <20030404000703.GX69100@roark.gnf.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PyWBHxIrsGpYNMFw" Content-Disposition: inline User-Agent: Mutt/1.4i X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-OriginalArrivalTime: 04 Apr 2003 00:07:04.0014 (UTC) FILETIME=[1F5166E0:01C2FA3E] Subject: Yet another libthr crash X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 00:07:05 -0000 --PyWBHxIrsGpYNMFw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I'm just hitting all the fun bugs today..... No core dump from this one. Privoxy seems to be a good app to test multiple io threads and is simple enough to be debug. Here's what I got this time: $ /usr/local/sbin/privoxy --no-daemon /usr/local/etc/privoxy/config Apr 03 15:50:49 Privoxy(134709248) Info: loading configuration file '/usr/local/etc/privoxy/config': ... Apr 03 15:51:09 Privoxy(134922240) Request: www.dilbert.com/images/ffffff_dot.gif Apr 03 15:51:09 Privoxy(134922240) Error: could not resolve hostname www.dilbert.com Apr 03 15:51:09 Privoxy(134925312) Request: www.dilbert.com/comics/dilbert/images/dilbertawards_250x50.gif Apr 03 15:51:09 Privoxy(134992896) Request: www.dilbert.com/comics/dilbert/images/current_features_bullet.gif gif Apr 03 15:51:09 Privoxy(134992896) Request: www.dilbert.com/comics/dilbert/images/current_features_bullApr 03 15:51:09 Privoxy(134929408) Request: www.dilbert.com/comics/dilbert/images/current_features_border_righFatal error 'Illegal call from signal handler' at line 1542 in file /local/usr.src/lib/libthr/thread/thr_mutex.c (errno = 2) $ Kind of odd how the requests are interleaved. And then it seems to have died somewhere in thr_mutex.c::mutex_queue_enq(). -gordon --PyWBHxIrsGpYNMFw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+jMynRu2t9DV9ZfsRAgKPAKCZK/YTWkOnBqN/L58YP220YWSICACfW9v5 eThRA2AGv2+qvw/MrJOncKo= =XxFc -----END PGP SIGNATURE----- --PyWBHxIrsGpYNMFw-- From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 16:32:16 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7810737B401; Thu, 3 Apr 2003 16:32:16 -0800 (PST) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB96643FB1; Thu, 3 Apr 2003 16:32:13 -0800 (PST) (envelope-from larse@ISI.EDU) Received: from isi.edu (nik.isi.edu [128.9.168.58]) by boreas.isi.edu (8.11.6p2/8.11.2) with ESMTP id h340W7100206; Thu, 3 Apr 2003 16:32:07 -0800 (PST) Message-ID: <3E8CD287.2010408@isi.edu> Date: Thu, 03 Apr 2003 16:32:07 -0800 From: Lars Eggert User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030402 X-Accept-Language: en-us, de-de MIME-Version: 1.0 To: Gordon Tetlow References: <20030404000703.GX69100@roark.gnf.org> In-Reply-To: <20030404000703.GX69100@roark.gnf.org> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms050708030505060502020409" cc: threads@freebsd.org cc: current@freebsd.org Subject: Re: Yet another libthr crash X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 00:32:16 -0000 This is a cryptographically signed message in MIME format. --------------ms050708030505060502020409 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Gordon Tetlow wrote: > > No core dump from this one. Privoxy seems to be a good app to test > multiple io threads and is simple enough to be debug. The source is also pretty Linux-centric, so some issues you finds may be related to that. (But I am all for fixing privoxy on -current, so I can start using it instead of guidescope, which fails to reap its kids due to some linux emulator change - see "zombies from linux binaries" thread on -current, circa 10/01/02.) Lars -- Lars Eggert USC Information Sciences Institute --------------ms050708030505060502020409 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJtjCC AzgwggKhoAMCAQICEGZFcrfMdPXPY3ZFhNAukQEwDQYJKoZIhvcNAQEEBQAwgdExCzAJBgNV BAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vydmlj ZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkG CSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMDA4MzAwMDAw MDBaFw0wNDA4MjcyMzU5NTlaMIGSMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBD YXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xDzANBgNVBAoTBlRoYXd0ZTEdMBsGA1UECxMUQ2Vy dGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVtYWlsIFJTQSAyMDAw LjguMzAwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAN4zMqZjxwklRT7SbngnZ4HF2ogZ gpcO40QpimM1Km1wPPrcrvfudG8wvDOQf/k0caCjbZjxw0+iZdsN+kvx1t1hpfmFzVWaNRqd knWoJ67Ycvm6AvbXsJHeHOmr4BgDqHxDQlBRh4M88Dm0m1SKE4f/s5udSWYALQmJ7JRr6aFp AgMBAAGjTjBMMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwxLTI5NzAS BgNVHRMBAf8ECDAGAQH/AgEAMAsGA1UdDwQEAwIBBjANBgkqhkiG9w0BAQQFAAOBgQAxsUtH XfkBceX1U2xdedY9mMAmE2KBIqcS+CKV6BtJtyd7BDm6/ObyJOuR+r3sDSo491BVqGz3Da1M G7wD9LXrokefbKIMWI0xQgkRbLAaadErErJAXWr5edDqLiXdiuT82w0fnQLzWtvKPPZE6iZp h39Ins6ln+eE2MliYq0FxjCCAzkwggKioAMCAQICAwglQTANBgkqhkiG9w0BAQQFADCBkjEL MAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du MQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYD VQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMwMB4XDTAyMDgyNDE4NTMzOVoX DTAzMDgyNDE4NTMzOVowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYD VQQDEwtMYXJzIEVnZ2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCCASIwDQYJ KoZIhvcNAQEBBQADggEPADCCAQoCggEBANI2Rrt4ggaQ/IrOsDeOm2H4/R5FRIL6JjDY3StE aogp1r23WKniQ1Vj98Nu5WxlaZ3Iam3Jen5T66H8u7rtMNpK4qAeAGoBsVeyVr1+CTFeuv+m xCh7BvBJwhLdm0zDaoDT05YKYZaqtsT+F286FWJQg31Xtf+vTKLVVrHcsafnteyal2NEt7Ac yZZfjsVLwxp2Lq3cwYfRQRoo7/yCVzS7HsgM6jmbO4taEMo4yC2rpnUbWEUCDTaCYgpAXzAl oiNk7GDh0wz2s5ZSnHRvNSBMAjCmpNtSYHfXFI1ANwrrrHIJ7Ei83+XN32PWY4OPzO3iown9 VR+vM+8lNx9OX28CAwEAAaNWMFQwKgYFK2UBBAEEITAfAgEAMBowGAIBBAQTTDJ1TXlmZkJO VWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1MAwGA1UdEwEB/wQCMAAwDQYJ KoZIhvcNAQEEBQADgYEAXcrIlKmPLM/r8r3oz2ZLPLaT1AyMjYTZY2qq/R7SUtFa9BNlTIFh DG78QKfJ9lo2LMzTPQqMZgNLmj95GbNPI8P8OIq2K6MeCZWz08ROackqTFP6xWbIFIfXcBVR 1dZnDDyDKBBh05KkvyTPawSQyOBUeNBfQUyO4TE+3o58U8UwggM5MIICoqADAgECAgMIJUEw DQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUx EjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZp Y2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4z MDAeFw0wMjA4MjQxODUzMzlaFw0wMzA4MjQxODUzMzlaMFQxDzANBgNVBAQTBkVnZ2VydDEN MAsGA1UEKhMETGFyczEUMBIGA1UEAxMLTGFycyBFZ2dlcnQxHDAaBgkqhkiG9w0BCQEWDWxh cnNlQGlzaS5lZHUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDSNka7eIIGkPyK zrA3jpth+P0eRUSC+iYw2N0rRGqIKda9t1ip4kNVY/fDbuVsZWmdyGptyXp+U+uh/Lu67TDa SuKgHgBqAbFXsla9fgkxXrr/psQoewbwScIS3ZtMw2qA09OWCmGWqrbE/hdvOhViUIN9V7X/ r0yi1Vax3LGn57XsmpdjRLewHMmWX47FS8Madi6t3MGH0UEaKO/8glc0ux7IDOo5mzuLWhDK OMgtq6Z1G1hFAg02gmIKQF8wJaIjZOxg4dMM9rOWUpx0bzUgTAIwpqTbUmB31xSNQDcK66xy CexIvN/lzd9j1mODj8zt4qMJ/VUfrzPvJTcfTl9vAgMBAAGjVjBUMCoGBStlAQQBBCEwHwIB ADAaMBgCAQQEE0wydU15ZmZCTlViTkpKY2RaMnMwGAYDVR0RBBEwD4ENbGFyc2VAaXNpLmVk dTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GBAF3KyJSpjyzP6/K96M9mSzy2k9QM jI2E2WNqqv0e0lLRWvQTZUyBYQxu/ECnyfZaNizM0z0KjGYDS5o/eRmzTyPD/DiKtiujHgmV s9PETmnJKkxT+sVmyBSH13AVUdXWZww8gygQYdOSpL8kz2sEkMjgVHjQX0FMjuExPt6OfFPF MYID1TCCA9ECAQEwgZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUx EjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZp Y2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4z MAIDCCVBMAkGBSsOAwIaBQCgggIPMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI hvcNAQkFMQ8XDTAzMDQwNDAwMzIwN1owIwYJKoZIhvcNAQkEMRYEFFl6QLt+eKGAuWmnVk9b RnTph2itMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0G CCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGrBgkrBgEEAYI3EAQxgZ0w gZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNh cGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNl czEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDCCVBMIGtBgsq hkiG9w0BCRACCzGBnaCBmjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw ZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRp ZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44 LjMwAgMIJUEwDQYJKoZIhvcNAQEBBQAEggEAYJNx0RH/u1MwndxgD8sbW/RZYm99bL1xXXPf x3JcVlwB8FcLqjSRxWESShT7zILiFtAMYZ89hVC+KitL9TkQpj9G8A5tSwCpbeBZ+FGrdhRr dCouib+noTjjAELyc0DdnwyWpllwwmuS57TATFx6a1L8Mzbf2GZyTzGNSnvqMNVBYynJPGfK KbaUqE0/pKbFM7niatM5ts1yrcGyHFF1/cv4ZRddJg9W93SI2DQC/fI4+gIwMxqSQPfhTPBS rn49XE0IPqsULw2MOoGXBjVHLSjdPKu2+qZynn1uhSe08UCdZg17PDW8h8Nfp4pazv59gpMR Sui3ZTktx2FRw9J4EQAAAAAAAA== --------------ms050708030505060502020409-- From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 18:19:39 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F7E737B401 for ; Thu, 3 Apr 2003 18:19:39 -0800 (PST) Received: from thalia.otenet.gr (thalia.otenet.gr [195.170.0.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id F38D843FA3 for ; Thu, 3 Apr 2003 18:19:37 -0800 (PST) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.gr (patr530-b122.otenet.gr [212.205.244.130]) by thalia.otenet.gr (8.12.9/8.12.9) with ESMTP id h342JWt0025566; Fri, 4 Apr 2003 05:19:34 +0300 (EEST) Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.12.9/8.12.9) with ESMTP id h342JV4C019246; Fri, 4 Apr 2003 05:19:31 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.gr (8.12.9/8.12.9/Submit) id h342JQPB019245; Fri, 4 Apr 2003 05:19:26 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Fri, 4 Apr 2003 05:19:26 +0300 From: Giorgos Keramidas To: "Oleg V. Nauman" Message-ID: <20030404021926.GA18960@gothmog.gr> References: <16011.4537.279737.406477@horsey.gshapiro.net> <16011.7467.322808.498405@emerger.yogotech.com> <20030402205754.GF75212@core.zp.ua> <16011.25002.138504.661813@emerger.yogotech.com> <20030403190503.GC82393@core.zp.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030403190503.GC82393@core.zp.ua> cc: freebsd-current@freebsd.org Subject: Re: sendmail: no local mailer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 02:19:39 -0000 On 2003-04-03 22:05, "Oleg V. Nauman" wrote: >On Wed, Apr 02, 2003 at 03:18:18PM -0700, Nate Williams wrote: >>>> This happened on one of my -stable boxes lately when doing a upgrade >>>> using buildworld. For some (unknown) reason m4 bombed out and created >>>> an empty .cf file. >>>> >>>> I fixed it by doing something similar to what was done above, although >>>> why m4 failed is a mystery.... >>> >>> Some patch: >>> >>> --- /usr/src/etc/sendmail/Makefile.orig Wed Apr 2 23:51:19 2003 >>> +++ /usr/src/etc/sendmail/Makefile Wed Apr 2 23:51:50 2003 >>> @@ -1,7 +1,7 @@ >>> # @(#)Makefile 8.19 (Berkeley) 1/14/97 >>> # $FreeBSD: src/etc/sendmail/Makefile,v 1.21 2002/07/29 09:40:06 ru Exp $ >>> >>> -M4= m4 >>> +M4= /usr/bin/m4 >>> CHMOD= chmod >>> ROMODE= 444 >>> RM= rm -f >> >> This shouldn't be necessary, since m4 is in the path in buildworld, is > > installworld, you meant? Actually no. One of the last things done during buildworld is (wrapped to fit under 80 columns): : ===> etc/sendmail : rm -f freebsd.cf : (cd /usr/src/etc/sendmail && \ : m4 -D_CF_DIR_=/usr/src/etc/sendmail/../../contrib/sendmail/cf/ \ : /usr/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 freebsd.mc) \ : > freebsd.cf : chmod 444 freebsd.cf : rm -f /etc/mail/gothmog.cf : (cd /usr/src/etc/sendmail && \ : m4 -D_CF_DIR_=/usr/src/etc/sendmail/../../contrib/sendmail/cf/ \ : /usr/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 \ : /etc/mail/gothmog.mc) > /etc/mail/gothmog.cf : chmod 444 /etc/mail/gothmog.cf : rm -f /etc/mail/gothmog.submit.cf : (cd /usr/src/etc/sendmail && \ : m4 -D_CF_DIR_=/usr/src/etc/sendmail/../../contrib/sendmail/cf/ \ : /usr/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 \ : /etc/mail/gothmog.submit.mc) > /etc/mail/gothmog.submit.cf : chmod 444 /etc/mail/gothmog.submit.cf From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 00:01:06 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4355E37B401 for ; Fri, 4 Apr 2003 00:01:06 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id D8A9843F3F for ; Fri, 4 Apr 2003 00:01:05 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 15825 invoked by uid 1000); 4 Apr 2003 08:01:08 -0000 Date: Fri, 4 Apr 2003 00:01:08 -0800 (PST) From: Nate Lawson To: current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: MPSAFE fxp m_pkthdr not valid X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 08:01:06 -0000 I have gotten fxp running with MPSAFE and did a large scp transfer. It ran for a few minutes and then paniced. It was trap 12 (page fault) at address 0x24. Here is where it crashed: fxp_start+0xcc 0xc0194a4c is in fxp_start (../../../dev/fxp/if_fxp.c:1263). 1258 * been computed and stored in the checksum field 1259 * in the TCP header. The stack should have 1260 * already done this for us. 1261 */ 1262 1263 if (mb_head->m_pkthdr.csum_flags) { 1264 if (mb_head->m_pkthdr.csum_flags & CSUM_DELAY_DATA) { 1265 txp->tx_cb->ipcb_ip_activation_high = 1266 FXP_IPCB_HARDWAREPARSING_ENABLE; 1267 txp->tx_cb->ipcb_ip_schedule = The deref of mb_head->m_pkthdr is invalid. Note that my fxp_intr function acquires the fxp lock right away so this shouldn't be a race in fxp. There is still the slab_zalloc LOR which I will describe further in another email. -Nate From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 00:03:10 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90A9137B401 for ; Fri, 4 Apr 2003 00:03:10 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 1807D43FB1 for ; Fri, 4 Apr 2003 00:03:10 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 15840 invoked by uid 1000); 4 Apr 2003 08:03:12 -0000 Date: Fri, 4 Apr 2003 00:03:12 -0800 (PST) From: Nate Lawson To: Andrew Gallatin In-Reply-To: <16012.32534.331966.216694@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: mbuf LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 08:03:10 -0000 On Thu, 3 Apr 2003, Andrew Gallatin wrote: > Nate Lawson writes: > > I was testing some changes to make fxp MPSAFE and got a LOR in allocating > > the mbuf cluster and then finally a panic when trying to dereference the > > cluster header. Is the mbuf system MPSAFE? Is it ok to call m_getcl > > with a device lock held (but not Giant)? > > > > The lock reversal was: 1. fxp softc lock, 2. Giant. > > I think the only place it can be coming from is slab_zalloc(). > Does the appended (untested) patch help? > > BTW, I don't think that there is any need to get Giant for the zone > allocators in the M_NOWAIT case, but I'm not really familar with the > code, and I don't know if the sparc64 uma_small_alloc needs Giant. > > BTW, my MPSAFE driver never sees this, but then again, I never > allocate clusters. I use jumbo frames, and carve out my own recv > buffers, so I'm only allocating mbufs, not clusters. > > Drew > > > Index: uma_core.c > =================================================================== > RCS file: /home/ncvs/src/sys/vm/uma_core.c,v > retrieving revision 1.51 > diff -u -r1.51 uma_core.c > --- uma_core.c 26 Mar 2003 18:44:53 -0000 1.51 > +++ uma_core.c 3 Apr 2003 18:22:14 -0000 > @@ -703,10 +703,14 @@ > wait &= ~M_ZERO; > > if (booted || (zone->uz_flags & UMA_ZFLAG_PRIVALLOC)) { > - mtx_lock(&Giant); > - mem = zone->uz_allocf(zone, > - zone->uz_ppera * UMA_SLAB_SIZE, &flags, wait); > - mtx_unlock(&Giant); > + if ((wait & M_NOWAIT) == 0) { > + mtx_lock(&Giant); > + mem = zone->uz_allocf(zone, > + zone->uz_ppera * UMA_SLAB_SIZE, &flags, wait); > + mtx_unlock(&Giant); > + } else { > + mem = NULL; > + } > if (mem == NULL) { > ZONE_LOCK(zone); > return (NULL); You're right about where the problem is (top of stack trace and listing below). However, your patch causes an immediate panic on boot due to a NULL deref. I don't think you want it to always return NULL if called with M_NOWAIT set. :) Other ideas? slab_zalloc + 0xdf uma_zone_slab + 0xd8 uma_zalloc_bucket + 0x15d uma_zalloc_arg + 0x307 malloc ... m_getcl (gdb) l *slab_zalloc+0xdf 0xc02f646f is in slab_zalloc (../../../vm/uma_core.c:707). 702 else 703 wait &= ~M_ZERO; 704 705 if (booted || (zone->uz_flags & UMA_ZFLAG_PRIVALLOC)) { 706 mtx_lock(&Giant); 707 mem = zone->uz_allocf(zone, 708 zone->uz_ppera * UMA_SLAB_SIZE, &flags, wait); 709 mtx_unlock(&Giant); 710 if (mem == NULL) { 711 ZONE_LOCK(zone); -Nate From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 00:05:55 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4EFAF37B401 for ; Fri, 4 Apr 2003 00:05:55 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id E602943FAF for ; Fri, 4 Apr 2003 00:05:54 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 15848 invoked by uid 1000); 4 Apr 2003 08:05:57 -0000 Date: Fri, 4 Apr 2003 00:05:57 -0800 (PST) From: Nate Lawson To: current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: cbb0: Could not map register memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 08:05:55 -0000 I cannot use my cardbus slots on -current. My dmesg is: cbb0: mem 0x50000000-0x50000fff irq 11 at device 0.0 on pci2 cbb0: Could not map register memory device_probe_and_attach: cbb0 attach returned 12 cbb0: mem 0x51000000-0x51000fff irq 11 at device 0.1 on pci2 cbb0: Could not map register memory device_probe_and_attach: cbb0 attach returned 12 I am running with the following in device.hints: hw.acpi.ec.event_driven="1" hw.cbb.start_memory="0x20000000" hw.cbb.debug="1" hw.cardbus.debug="1" hw.cardbus.cis_debug="1" hw.pccard.debug="1" hw.pccard.cis_debug="1" I get the same errors whether or not ACPI is enabled. This is on a IBM T23, 1 ghz, 384 MB ram. -Nate From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 00:55:58 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B756137B401 for ; Fri, 4 Apr 2003 00:55:58 -0800 (PST) Received: from highway.seet.dk (seet.dk [80.62.87.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B1C443FDD for ; Fri, 4 Apr 2003 00:55:57 -0800 (PST) (envelope-from inbox@seet.dk) Received: by highway.seet.dk (Postfix, from userid 1013) id BD928AB0B; Fri, 4 Apr 2003 10:55:55 +0200 (CEST) Received: from laptop (laptop.wireless.seet.dk [10.0.0.2]) by highway.seet.dk (Postfix) with SMTP id D5405A96B for ; Fri, 4 Apr 2003 10:55:49 +0200 (CEST) Date: Fri, 4 Apr 2003 10:55:46 +0200 From: =?ISO-8859-1?Q?S=F8ren?= Vrist To: freebsd-current@freebsd.org Message-Id: <20030404105546.03fda73e.inbox@seet.dk> In-Reply-To: References: X-Mailer: Sylpheed version 0.8.9 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, hits=-26.1 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: Re: cbb0: Could not map register memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 08:55:59 -0000 On Fri, 4 Apr 2003 00:05:57 -0800 (PST) Nate Lawson wrote: > I cannot use my cardbus slots on -current. My dmesg is: >=20 > cbb0: mem 0x50000000-0x50000fff irq 11 at > device 0.0 on pci2 > cbb0: Could not map register memory > device_probe_and_attach: cbb0 attach returned 12 > cbb0: mem 0x51000000-0x51000fff irq 11 at > device 0.1 on pci2 > cbb0: Could not map register memory > device_probe_and_attach: cbb0 attach returned 12 I seem to recall that i had a smililar problem with my Asus L1400. I tried with=20 hw.pci.allow_unsupported_io_range=3D"1" in my /boot/loader.conf hope that helps kind regards S=F8ren Vrist From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 01:56:25 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D285437B401 for ; Fri, 4 Apr 2003 01:56:25 -0800 (PST) Received: from mail.cordis.lu (mail.cordis.lu [212.190.217.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4416243FBF for ; Fri, 4 Apr 2003 01:56:24 -0800 (PST) (envelope-from a.carter@cordis.lu) Received: from mailsvr.intrasoft.lu (mail.intrasoft.lu [212.190.217.251]) by mail.cordis.lu (8.12.8/8.12.8) with ESMTP id h34A02nf015533 for ; Fri, 4 Apr 2003 12:00:03 +0200 Received: by mail.intrasoft.lu with Internet Mail Service (5.5.2656.59) id <2HMPCKAY>; Fri, 4 Apr 2003 11:53:50 +0200 Received: from intra241.intrasoft.lu (212.190.217.170 [212.190.217.170]) by mailsvr.intrasoft.lu with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59) id 2HMPCKAX; Fri, 4 Apr 2003 11:53:46 +0200 From: CARTER Anthony To: freebsd-current@freebsd.org Organization: Intrasoft Date: Fri, 4 Apr 2003 11:56:37 +0200 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304041156.38051.a.carter@intrasoft.lu> X-Spam-Status: No, hits=-100.0 required=4.2 tests=USER_AGENT,USER_IN_WHITELIST version=2.50 X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: OOOPS - portupgrade/Swapfile/??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 09:56:26 -0000 Hey guys, Just did a CVSup, and did a portupgrade -rRa. I watched it install libxml update and fontconfig and apache2. I then left it to its things and went to get a coffee.... On return, I got the login screen for KDE??? So I logged in and tried to run portupgrade -rRa again just to confirm everything was done and it returned me to the login screen. I rebooted into console and ran the same command. I then get repeated application kills due to swap file full...Never had that before. Watching with swapinfo, my 500Mb (256 Mb Ram) swapfile just fills up...on stopping portupgrade, swap file is emptied... Any ideas what is going on? Thanks, Anthony just a quick snip: pr 4 10:52:23 intra241 su: carteran to root on /dev/ttyp6 Apr 4 11:05:01 intra241 kernel: swap_pager: out of swap space Apr 4 11:05:02 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:03 intra241 kernel: pid 589 (kdeinit), uid 1001, was killed: out of swap space Apr 4 11:05:04 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:08 intra241 last message repeated 246 times Apr 4 11:05:08 intra241 kernel: pid 517 (XFree86), uid 0, was killed: out of swap space Apr 4 11:05:16 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:16 intra241 last message repeated 5 times Apr 4 11:05:14 intra241 kdm[508]: Server for display :0 terminated unexpectedly Apr 4 11:05:16 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:20 intra241 last message repeated 173 times Apr 4 11:05:20 intra241 kernel: pid 2746 (kdeinit), uid 1001, was killed: out of swap space Apr 4 11:05:21 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:28 intra241 last message repeated 224 times Apr 4 11:05:28 intra241 kernel: pid 1187 (kmail), uid 1001, was killed: out of swap space Apr 4 11:05:30 intra241 kernel: pid 1187 (kmail), uid 1001, was killed: out of swap space Apr 4 11:05:30 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:34 intra241 last message repeated 129 times Apr 4 11:05:34 intra241 kernel: pid 575 (kdeinit), uid 1001, was killed: out of swap space Apr 4 11:05:34 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:38 intra241 last message repeated 196 times Apr 4 11:05:38 intra241 kernel: pid 561 (kdeinit), uid 1001, was killed: out of swap space Apr 4 11:05:39 intra241 kernel: pid 561 (kdeinit), uid 1001, was killed: out of swap space 1%Apr 4 09:00:00 intra241 newsyslog[2088]: logfile turned over due to size>100K Apr 4 09:27:51 intra241 su: carteran to root on /dev/ttyp0 Apr 4 10:01:34 intra241 su: carteran to root on /dev/ttyp1 Apr 4 10:17:23 intra241 su: carteran to root on /dev/ttyp2 Apr 4 10:27:45 intra241 su: carteran to root on /dev/ttyp3 Apr 4 10:41:23 intra241 kernel: pid 15130 (conftest), uid 0: exited on signal 12 (core dumped) Apr 4 10:51:21 intra241 su: carteran to root on /dev/ttyp5 Apr 4 10:52:23 intra241 su: carteran to root on /dev/ttyp6 Apr 4 11:05:01 intra241 kernel: swap_pager: out of swap space Apr 4 11:05:02 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:03 intra241 kernel: pid 589 (kdeinit), uid 1001, was killed: out of swap space Apr 4 11:05:04 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:08 intra241 last message repeated 246 times Apr 4 11:05:08 intra241 kernel: pid 517 (XFree86), uid 0, was killed: out of swap space Apr 4 11:05:16 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:16 intra241 last message repeated 5 times Apr 4 11:05:14 intra241 kdm[508]: Server for display :0 terminated unexpectedly Apr 4 11:05:16 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:05:20 intra241 last message repeated 173 times From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 02:02:28 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDD6937B401 for ; Fri, 4 Apr 2003 02:02:28 -0800 (PST) Received: from mail.cordis.lu (mail.cordis.lu [212.190.217.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5ED1E43F93 for ; Fri, 4 Apr 2003 02:02:27 -0800 (PST) (envelope-from a.carter@cordis.lu) Received: from mailsvr.intrasoft.lu (mail.intrasoft.lu [212.190.217.251]) by mail.cordis.lu (8.12.8/8.12.8) with ESMTP id h34A66nf015947 for ; Fri, 4 Apr 2003 12:06:06 +0200 Received: by mail.intrasoft.lu with Internet Mail Service (5.5.2656.59) id <2HMPCKBW>; Fri, 4 Apr 2003 11:59:53 +0200 Received: from intra241.intrasoft.lu (212.190.217.170 [212.190.217.170]) by mailsvr.intrasoft.lu with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59) id 2HMPCKBV; Fri, 4 Apr 2003 11:59:52 +0200 From: CARTER Anthony To: freebsd-current@freebsd.org Organization: Intrasoft Date: Fri, 4 Apr 2003 12:02:43 +0200 User-Agent: KMail/1.5 References: <200304041156.38051.a.carter@intrasoft.lu> In-Reply-To: <200304041156.38051.a.carter@intrasoft.lu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304041202.43939.a.carter@intrasoft.lu> X-Spam-Status: No, hits=-126.1 required=4.2 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT,USER_IN_WHITELIST version=2.50 X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: Re: OOOPS - portupgrade/Swapfile/??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 10:02:29 -0000 More....This time outside of X11 and KDE...Just in console: Apr 4 11:26:43 intra241 kernel: pid 476 (httpd), uid 80, was killed: out of swap space Apr 4 11:26:43 intra241 kernel: pid 11877 (sort), uid 0, was killed: out of swap space Apr 4 11:26:43 intra241 last message repeated 2 times Apr 4 11:26:44 intra241 kernel: pid 475 (httpd), uid 80, was killed: out of swap space Apr 4 11:26:44 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:26:44 intra241 kernel: pid 2780 (sort), uid 0, was killed: out of swap space Apr 4 11:26:45 intra241 kernel: swap_pager: out of swap space Apr 4 11:26:45 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:26:45 intra241 kernel: pid 11914 (sort), uid 0, was killed: out of swap space Apr 4 11:26:45 intra241 kernel: pid 11942 (sort), uid 0, was killed: out of swap space Apr 4 11:26:45 intra241 kernel: pid 11961 (sort), uid 0, was killed: out of swap space Apr 4 11:26:46 intra241 kernel: pid 11998 (sort), uid 0, was killed: out of swap space Apr 4 11:26:46 intra241 kernel: pid 12026 (sort), uid 0, was killed: out of swap space Apr 4 11:26:46 intra241 kernel: pid 12045 (sort), uid 0, was killed: out of swap space Apr 4 11:26:46 intra241 kernel: pid 12082 (sort), uid 0, was killed: out of swap space Apr 4 11:26:47 intra241 kernel: pid 12110 (sort), uid 0, was killed: out of swap space Apr 4 11:26:47 intra241 kernel: pid 12129 (sort), uid 0, was killed: out of swap space Apr 4 11:26:47 intra241 kernel: pid 12166 (sort), uid 0, was killed: out of swap space Apr 4 11:26:47 intra241 kernel: pid 12194 (sort), uid 0, was killed: out of swap space Apr 4 11:26:47 intra241 kernel: pid 12213 (sort), uid 0, was killed: out of swap space Apr 4 11:26:48 intra241 kernel: pid 12250 (sort), uid 0, was killed: out of swap space Apr 4 11:26:48 intra241 kernel: pid 12250 (sort), uid 0, was killed: out of swap space Apr 4 11:26:48 intra241 kernel: pid 12278 (sort), uid 0, was killed: out of swap space Apr 4 11:26:48 intra241 kernel: pid 12297 (sort), uid 0, was killed: out of swap space Apr 4 11:26:48 intra241 kernel: pid 12334 (sort), uid 0, was killed: out of swap space Apr 4 11:26:49 intra241 kernel: pid 10948 (python2.2), uid 91, was killed: out of swap space Apr 4 11:26:49 intra241 kernel: pid 12363 (sort), uid 0, was killed: out of swap space Apr 4 11:26:49 intra241 kernel: pid 12381 (sort), uid 0, was killed: out of swap space Apr 4 11:26:49 intra241 kernel: pid 12418 (sort), uid 0, was killed: out of swap space Apr 4 11:26:49 intra241 kernel: pid 12446 (sort), uid 0, was killed: out of swap space Apr 4 11:26:50 intra241 kernel: pid 12465 (sort), uid 0, was killed: out of swap space Apr 4 11:26:50 intra241 kernel: pid 12502 (sort), uid 0, was killed: out of swap space Apr 4 11:26:50 intra241 kernel: pid 521 (python2.2), uid 91, was killed: out of swap space Apr 4 11:26:51 intra241 kernel: swap_pager: out of swap space Apr 4 11:26:51 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:26:51 intra241 kernel: pid 12530 (sort), uid 0, was killed: out of swap space Apr 4 11:26:51 intra241 kernel: pid 12550 (sort), uid 0, was killed: out of swap space Apr 4 11:26:51 intra241 kernel: pid 12586 (sort), uid 0, was killed: out of swap space Apr 4 11:26:51 intra241 kernel: pid 12614 (sort), uid 0, was killed: out of swap space Apr 4 11:26:52 intra241 kernel: pid 12633 (sort), uid 0, was killed: out of swap space Apr 4 11:26:52 intra241 kernel: pid 12633 (sort), uid 0, was killed: out of swap space Apr 4 11:26:52 intra241 kernel: pid 2341 (sort), uid 0, was killed: out of swap space Apr 4 11:26:53 intra241 kernel: swap_pager: out of swap space Apr 4 11:26:53 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:26:54 intra241 kernel: pid 12700 (sort), uid 0, was killed: out of swap space Apr 4 11:26:54 intra241 kernel: pid 12670 (sort), uid 0, was killed: out of swap space Apr 4 11:26:54 intra241 kernel: pid 12719 (sort), uid 0, was killed: out of swap space Apr 4 11:26:54 intra241 kernel: pid 12756 (sort), uid 0, was killed: out of swap space Apr 4 11:26:55 intra241 kernel: pid 12784 (sort), uid 0, was killed: out of swap space Apr 4 11:26:55 intra241 kernel: pid 12803 (sort), uid 0, was killed: out of swap space Apr 4 11:26:55 intra241 kernel: pid 12840 (sort), uid 0, was killed: out of swap space Apr 4 11:26:55 intra241 kernel: pid 12868 (sort), uid 0, was killed: out of swap space Apr 4 11:26:56 intra241 kernel: pid 12887 (sort), uid 0, was killed: out of swap space Apr 4 11:26:56 intra241 kernel: pid 12924 (sort), uid 0, was killed: out of swap space Apr 4 11:26:56 intra241 kernel: pid 12952 (sort), uid 0, was killed: out of swap space Apr 4 11:26:56 intra241 kernel: pid 12971 (sort), uid 0, was killed: out of swap space Apr 4 11:26:56 intra241 kernel: pid 13008 (sort), uid 0, was killed: out of swap space Apr 4 11:26:57 intra241 kernel: pid 13036 (sort), uid 0, was killed: out of swap space Apr 4 11:26:57 intra241 kernel: pid 13055 (sort), uid 0, was killed: out of swap space Apr 4 11:26:57 intra241 kernel: pid 2677 (sort), uid 0, was killed: out of swap space Apr 4 11:26:58 intra241 kernel: swap_pager: out of swap space Apr 4 11:26:58 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:26:58 intra241 kernel: pid 13092 (sort), uid 0, was killed: out of swap space Apr 4 11:26:58 intra241 kernel: pid 13120 (sort), uid 0, was killed: out of swap space Apr 4 11:26:59 intra241 kernel: pid 13139 (sort), uid 0, was killed: out of swap space Apr 4 11:26:59 intra241 kernel: pid 13176 (sort), uid 0, was killed: out of swap space Apr 4 11:26:43 intra241 kernel: pid 476 (httpd), uid 80, was killed: out of swap space Apr 4 11:26:43 intra241 kernel: pid 11877 (sort), uid 0, was killed: out of swap space Apr 4 11:26:43 intra241 last message repeated 2 times Apr 4 11:26:44 intra241 kernel: pid 475 (httpd), uid 80, was killed: out of swap space Apr 4 11:26:44 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:26:44 intra241 kernel: pid 2780 (sort), uid 0, was killed: out of swap space Apr 4 11:26:45 intra241 kernel: swap_pager: out of swap space Apr 4 11:26:45 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:26:45 intra241 kernel: pid 11914 (sort), uid 0, was killed: out of swap space Apr 4 11:26:45 intra241 kernel: pid 11942 (sort), uid 0, was killed: out of swap space Apr 4 11:26:45 intra241 kernel: pid 11961 (sort), uid 0, was killed: out of swap space Apr 4 11:26:46 intra241 kernel: pid 11998 (sort), uid 0, was killed: out of swap space Apr 4 11:26:46 intra241 kernel: pid 12026 (sort), uid 0, was killed: out of swap space Apr 4 11:26:46 intra241 kernel: pid 12045 (sort), uid 0, was killed: out of swap space Apr 4 11:26:46 intra241 kernel: pid 12082 (sort), uid 0, was killed: out of swap space Apr 4 11:26:47 intra241 kernel: pid 12110 (sort), uid 0, was killed: out of swap space Apr 4 11:26:47 intra241 kernel: pid 12129 (sort), uid 0, was killed: out of swap space Apr 4 11:26:47 intra241 kernel: pid 12166 (sort), uid 0, was killed: out of swap space Apr 4 11:26:47 intra241 kernel: pid 12194 (sort), uid 0, was killed: out of swap space Apr 4 11:26:47 intra241 kernel: pid 12213 (sort), uid 0, was killed: out of swap space Apr 4 11:26:48 intra241 kernel: pid 12250 (sort), uid 0, was killed: out of swap space Apr 4 11:26:48 intra241 kernel: pid 12250 (sort), uid 0, was killed: out of swap space Apr 4 11:26:48 intra241 kernel: pid 12278 (sort), uid 0, was killed: out of swap space Apr 4 11:26:48 intra241 kernel: pid 12297 (sort), uid 0, was killed: out of swap space Apr 4 11:26:48 intra241 kernel: pid 12334 (sort), uid 0, was killed: out of swap space Apr 4 11:26:49 intra241 kernel: pid 10948 (python2.2), uid 91, was killed: out of swap space Apr 4 11:26:49 intra241 kernel: pid 12363 (sort), uid 0, was killed: out of swap space Apr 4 11:26:49 intra241 kernel: pid 12381 (sort), uid 0, was killed: out of swap space Apr 4 11:26:49 intra241 kernel: pid 12418 (sort), uid 0, was killed: out of swap space Apr 4 11:26:49 intra241 kernel: pid 12446 (sort), uid 0, was killed: out of swap space Apr 4 11:26:50 intra241 kernel: pid 12465 (sort), uid 0, was killed: out of swap space Apr 4 11:26:50 intra241 kernel: pid 12502 (sort), uid 0, was killed: out of swap space Apr 4 11:26:50 intra241 kernel: pid 521 (python2.2), uid 91, was killed: out of swap space Apr 4 11:26:51 intra241 kernel: swap_pager: out of swap space Apr 4 11:26:51 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:26:51 intra241 kernel: pid 12530 (sort), uid 0, was killed: out of swap space Apr 4 11:26:51 intra241 kernel: pid 12550 (sort), uid 0, was killed: out of swap space Apr 4 11:26:51 intra241 kernel: pid 12586 (sort), uid 0, was killed: out of swap space Apr 4 11:26:51 intra241 kernel: pid 12614 (sort), uid 0, was killed: out of swap space Apr 4 11:26:52 intra241 kernel: pid 12633 (sort), uid 0, was killed: out of swap space Apr 4 11:26:52 intra241 kernel: pid 12633 (sort), uid 0, was killed: out of swap space Apr 4 11:26:52 intra241 kernel: pid 2341 (sort), uid 0, was killed: out of swap space Apr 4 11:26:53 intra241 kernel: swap_pager: out of swap space Apr 4 11:26:53 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:26:54 intra241 kernel: pid 12700 (sort), uid 0, was killed: out of swap space Apr 4 11:26:54 intra241 kernel: pid 12670 (sort), uid 0, was killed: out of swap space Apr 4 11:26:54 intra241 kernel: pid 12719 (sort), uid 0, was killed: out of swap space Apr 4 11:26:54 intra241 kernel: pid 12756 (sort), uid 0, was killed: out of swap space Apr 4 11:26:55 intra241 kernel: pid 12784 (sort), uid 0, was killed: out of swap space Apr 4 11:26:55 intra241 kernel: pid 12803 (sort), uid 0, was killed: out of swap space Apr 4 11:26:55 intra241 kernel: pid 12840 (sort), uid 0, was killed: out of swap space Apr 4 11:26:55 intra241 kernel: pid 12868 (sort), uid 0, was killed: out of swap space Apr 4 11:26:56 intra241 kernel: pid 12887 (sort), uid 0, was killed: out of swap space Apr 4 11:26:56 intra241 kernel: pid 12924 (sort), uid 0, was killed: out of swap space Apr 4 11:26:56 intra241 kernel: pid 12952 (sort), uid 0, was killed: out of swap space Apr 4 11:26:56 intra241 kernel: pid 12971 (sort), uid 0, was killed: out of swap space Apr 4 11:26:56 intra241 kernel: pid 13008 (sort), uid 0, was killed: out of swap space Apr 4 11:26:57 intra241 kernel: pid 13036 (sort), uid 0, was killed: out of swap space Apr 4 11:26:57 intra241 kernel: pid 13055 (sort), uid 0, was killed: out of swap space Apr 4 11:26:57 intra241 kernel: pid 2677 (sort), uid 0, was killed: out of swap space Apr 4 11:26:58 intra241 kernel: swap_pager: out of swap space Apr 4 11:26:58 intra241 kernel: swap_pager_getswapspace: failed Apr 4 11:26:58 intra241 kernel: pid 13092 (sort), uid 0, was killed: out of swap space Apr 4 11:26:58 intra241 kernel: pid 13120 (sort), uid 0, was killed: out of swap space Apr 4 11:26:59 intra241 kernel: pid 13139 (sort), uid 0, was killed: out of swap space Apr 4 11:26:59 intra241 kernel: pid 13176 (sort), uid 0, was killed: out of swap space On Friday 04 April 2003 11:56, CARTER Anthony wrote: > Hey guys, > > Just did a CVSup, and did a portupgrade -rRa. > > I watched it install libxml update and fontconfig and apache2. I then left > it to its things and went to get a coffee.... > > On return, I got the login screen for KDE??? > > So I logged in and tried to run portupgrade -rRa again just to confirm > everything was done and it returned me to the login screen. I rebooted into > console and ran the same command. I then get repeated application kills due > to swap file full...Never had that before. > > Watching with swapinfo, my 500Mb (256 Mb Ram) swapfile just fills up...on > stopping portupgrade, swap file is emptied... > > Any ideas what is going on? > > Thanks, > Anthony > > just a quick snip: > > pr 4 10:52:23 intra241 su: carteran to root on /dev/ttyp6 > Apr 4 11:05:01 intra241 kernel: swap_pager: out of swap space > Apr 4 11:05:02 intra241 kernel: swap_pager_getswapspace: failed > Apr 4 11:05:03 intra241 kernel: pid 589 (kdeinit), uid 1001, was killed: > out of swap space > Apr 4 11:05:04 intra241 kernel: swap_pager_getswapspace: failed > Apr 4 11:05:08 intra241 last message repeated 246 times > Apr 4 11:05:08 intra241 kernel: pid 517 (XFree86), uid 0, was killed: out > of swap space > Apr 4 11:05:16 intra241 kernel: swap_pager_getswapspace: failed > Apr 4 11:05:16 intra241 last message repeated 5 times > Apr 4 11:05:14 intra241 kdm[508]: Server for display :0 terminated > unexpectedly > Apr 4 11:05:16 intra241 kernel: swap_pager_getswapspace: failed > Apr 4 11:05:20 intra241 last message repeated 173 times > Apr 4 11:05:20 intra241 kernel: pid 2746 (kdeinit), uid 1001, was killed: > out of swap space > Apr 4 11:05:21 intra241 kernel: swap_pager_getswapspace: failed > Apr 4 11:05:28 intra241 last message repeated 224 times > Apr 4 11:05:28 intra241 kernel: pid 1187 (kmail), uid 1001, was killed: > out of swap space > Apr 4 11:05:30 intra241 kernel: pid 1187 (kmail), uid 1001, was killed: > out of swap space > Apr 4 11:05:30 intra241 kernel: swap_pager_getswapspace: failed > Apr 4 11:05:34 intra241 last message repeated 129 times > Apr 4 11:05:34 intra241 kernel: pid 575 (kdeinit), uid 1001, was killed: > out of swap space > Apr 4 11:05:34 intra241 kernel: swap_pager_getswapspace: failed > Apr 4 11:05:38 intra241 last message repeated 196 times > Apr 4 11:05:38 intra241 kernel: pid 561 (kdeinit), uid 1001, was killed: > out of swap space > Apr 4 11:05:39 intra241 kernel: pid 561 (kdeinit), uid 1001, was killed: > out of swap space > 1%Apr 4 09:00:00 intra241 newsyslog[2088]: logfile turned over due to > size>100K > Apr 4 09:27:51 intra241 su: carteran to root on /dev/ttyp0 > Apr 4 10:01:34 intra241 su: carteran to root on /dev/ttyp1 > Apr 4 10:17:23 intra241 su: carteran to root on /dev/ttyp2 > Apr 4 10:27:45 intra241 su: carteran to root on /dev/ttyp3 > Apr 4 10:41:23 intra241 kernel: pid 15130 (conftest), uid 0: exited on > signal 12 (core dumped) > Apr 4 10:51:21 intra241 su: carteran to root on /dev/ttyp5 > Apr 4 10:52:23 intra241 su: carteran to root on /dev/ttyp6 > Apr 4 11:05:01 intra241 kernel: swap_pager: out of swap space > Apr 4 11:05:02 intra241 kernel: swap_pager_getswapspace: failed > Apr 4 11:05:03 intra241 kernel: pid 589 (kdeinit), uid 1001, was killed: > out of swap space > Apr 4 11:05:04 intra241 kernel: swap_pager_getswapspace: failed > Apr 4 11:05:08 intra241 last message repeated 246 times > Apr 4 11:05:08 intra241 kernel: pid 517 (XFree86), uid 0, was killed: out > of swap space > Apr 4 11:05:16 intra241 kernel: swap_pager_getswapspace: failed > Apr 4 11:05:16 intra241 last message repeated 5 times > Apr 4 11:05:14 intra241 kdm[508]: Server for display :0 terminated > unexpectedly > Apr 4 11:05:16 intra241 kernel: swap_pager_getswapspace: failed > Apr 4 11:05:20 intra241 last message repeated 173 times > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 02:09:10 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3375E37B401 for ; Fri, 4 Apr 2003 02:09:10 -0800 (PST) Received: from tao.xtaz.co.uk (pc-62-30-69-139-az.blueyonder.co.uk [62.30.69.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB84C43FB1 for ; Fri, 4 Apr 2003 02:09:08 -0800 (PST) (envelope-from matt@xtaz.co.uk) Received: from webmail.xtaz.co.uk (matt@localhost.xtaz.co.uk [127.0.0.1]) by tao.xtaz.co.uk (8.12.9/8.12.9) with ESMTP id h34A95Hs011609; Fri, 4 Apr 2003 11:09:05 +0100 (BST) (envelope-from matt@xtaz.co.uk) From: "Matt" To: CARTER Anthony , freebsd-current@freebsd.org Date: Fri, 4 Apr 2003 10:09:04 +0000 Message-Id: <20030404100459.M67134@xtaz.co.uk> In-Reply-To: <200304041156.38051.a.carter@intrasoft.lu> References: <200304041156.38051.a.carter@intrasoft.lu> X-Mailer: Open WebMail 2.00 20030325 X-OriginatingIP: 193.35.129.161 (matt) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: Re: OOOPS - portupgrade/Swapfile/??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 10:09:10 -0000 On Fri, 4 Apr 2003 11:56:37 +0200, CARTER Anthony wrote > > Watching with swapinfo, my 500Mb (256 Mb Ram) swapfile just fills > up...on stopping portupgrade, swap file is emptied... I have exactly the same thing, just my machine can cope with it a bit better as I have 512M physical and 1gig swap. It's currently running a portupgrade -rai and doing all the recent gnome commits. The first 6 or 7 upgrades of installed ports went without a hitch but since then at the points where it says "Building ...." and "Registering installation for ...." I get this: OK? [yes] ---> Build of x11/gnomesession started at: Fri, 04 Apr 2003 11:04:52 +0100 ---> Building '/usr/ports/x11/gnomesession' make: Max recursion level (500) exceeded.: Resource temporarily unavailable and the physical ram in use just goes up and up and up until it runs out and then the swap space does the same. After a few minutes (luckily before it runs out) it stops. All the ram is free'd and the portupgrade carries on. During this time looking at a "top" it appears it's due to around ten "sort" processes doing something or other at the time. This looks more like a portupgrade issue rather than a -CURRENT issue however. Matt. From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 02:25:20 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6552E37B401 for ; Fri, 4 Apr 2003 02:25:20 -0800 (PST) Received: from mail.cordis.lu (mail.cordis.lu [212.190.217.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F48743FB1 for ; Fri, 4 Apr 2003 02:25:19 -0800 (PST) (envelope-from a.carter@cordis.lu) Received: from mailsvr.intrasoft.lu (mail.intrasoft.lu [212.190.217.251]) by mail.cordis.lu (8.12.8/8.12.8) with ESMTP id h34ASwnf016798; Fri, 4 Apr 2003 12:28:58 +0200 Received: by mail.intrasoft.lu with Internet Mail Service (5.5.2656.59) id <2HMPCKDX>; Fri, 4 Apr 2003 12:22:45 +0200 Received: from intra241.intrasoft.lu (212.190.217.170 [212.190.217.170]) by mailsvr.intrasoft.lu with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59) id 2HMPCKDW; Fri, 4 Apr 2003 12:22:42 +0200 From: CARTER Anthony To: Matt , CARTER Anthony , freebsd-current@freebsd.org Organization: Intrasoft Date: Fri, 4 Apr 2003 12:25:33 +0200 User-Agent: KMail/1.5 References: <200304041156.38051.a.carter@intrasoft.lu> <20030404100459.M67134@xtaz.co.uk> In-Reply-To: <20030404100459.M67134@xtaz.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304041225.33721.a.carter@intrasoft.lu> X-Spam-Status: No, hits=-126.1 required=4.2 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT,USER_IN_WHITELIST version=2.50 X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: Re: OOOPS - portupgrade/Swapfile/??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 10:25:20 -0000 Did portupgrade get updated then? I am not using gnome... The only thing I can think of is that an update has created a loop within itself, thereby launching subsequent sorts...I get 10 or so sorts, about 20-30 make's, kill them they come back... Anthony On Friday 04 April 2003 12:09, Matt wrote: > On Fri, 4 Apr 2003 11:56:37 +0200, CARTER Anthony wrote > > > Watching with swapinfo, my 500Mb (256 Mb Ram) swapfile just fills > > up...on stopping portupgrade, swap file is emptied... > > I have exactly the same thing, just my machine can cope with it a bit > better as I have 512M physical and 1gig swap. It's currently running a > portupgrade -rai and doing all the recent gnome commits. The first 6 or 7 > upgrades of installed ports went without a hitch but since then at the > points where it says "Building ...." and "Registering installation for > ...." I get this: > > OK? [yes] > ---> Build of x11/gnomesession started at: Fri, 04 Apr 2003 11:04:52 +0100 > ---> Building '/usr/ports/x11/gnomesession' > make: Max recursion level (500) exceeded.: Resource temporarily unavailable > > and the physical ram in use just goes up and up and up until it runs out > and then the swap space does the same. After a few minutes (luckily before > it runs out) it stops. All the ram is free'd and the portupgrade carries > on. > > During this time looking at a "top" it appears it's due to around ten > "sort" processes doing something or other at the time. > > This looks more like a portupgrade issue rather than a -CURRENT issue > however. > > Matt. From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 02:35:27 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E091837B401 for ; Fri, 4 Apr 2003 02:35:27 -0800 (PST) Received: from tao.xtaz.co.uk (pc-62-30-69-139-az.blueyonder.co.uk [62.30.69.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0EDF43FBF for ; Fri, 4 Apr 2003 02:35:26 -0800 (PST) (envelope-from matt@xtaz.co.uk) Received: from webmail.xtaz.co.uk (matt@localhost.xtaz.co.uk [127.0.0.1]) by tao.xtaz.co.uk (8.12.9/8.12.9) with ESMTP id h34AZOHs012280; Fri, 4 Apr 2003 11:35:24 +0100 (BST) (envelope-from matt@xtaz.co.uk) From: "Matt" To: CARTER Anthony , freebsd-current@freebsd.org Date: Fri, 4 Apr 2003 10:35:24 +0000 Message-Id: <20030404103425.M46944@xtaz.co.uk> In-Reply-To: <200304041225.33721.a.carter@intrasoft.lu> References: <200304041156.38051.a.carter@intrasoft.lu> <20030404100459.M67134@xtaz.co.uk> <200304041225.33721.a.carter@intrasoft.lu> X-Mailer: Open WebMail 2.00 20030325 X-OriginatingIP: 193.35.129.161 (matt) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: Re: OOOPS - portupgrade/Swapfile/??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 10:35:28 -0000 On Fri, 4 Apr 2003 12:25:33 +0200, CARTER Anthony wrote > Did portupgrade get updated then? > > I am not using gnome... > > The only thing I can think of is that an update has created a loop > within itself, thereby launching subsequent sorts...I get 10 or so > sorts, about 20-30 make's, kill them they come back... > > Anthony I guess this could be related to the problem Kris Kennaway just reported on ports@ regarding "Index Build Failed". Matt. From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 03:21:13 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4C1737B401 for ; Fri, 4 Apr 2003 03:21:13 -0800 (PST) Received: from mail.cordis.lu (mail.cordis.lu [212.190.217.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87E0643F75 for ; Fri, 4 Apr 2003 03:21:12 -0800 (PST) (envelope-from a.carter@cordis.lu) Received: from mailsvr.intrasoft.lu (mail.intrasoft.lu [212.190.217.251]) by mail.cordis.lu (8.12.8/8.12.8) with ESMTP id h34BOqnf018287; Fri, 4 Apr 2003 13:24:53 +0200 Received: by mail.intrasoft.lu with Internet Mail Service (5.5.2656.59) id <2HMPCKJH>; Fri, 4 Apr 2003 13:18:39 +0200 Received: from intra241.intrasoft.lu (212.190.217.170 [212.190.217.170]) by mailsvr.intrasoft.lu with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59) id 2HMPCKJG; Fri, 4 Apr 2003 13:18:34 +0200 From: CARTER Anthony To: Matt , CARTER Anthony , freebsd-current@freebsd.org Organization: Intrasoft Date: Fri, 4 Apr 2003 13:21:25 +0200 User-Agent: KMail/1.5 References: <200304041156.38051.a.carter@intrasoft.lu> <200304041225.33721.a.carter@intrasoft.lu> <20030404103425.M46944@xtaz.co.uk> In-Reply-To: <20030404103425.M46944@xtaz.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304041321.25821.a.carter@intrasoft.lu> X-Spam-Status: No, hits=-126.1 required=4.2 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT,USER_IN_WHITELIST version=2.50 X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: Re: OOOPS - portupgrade/Swapfile/??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 11:21:14 -0000 Can you let me know about this, or forward a copy of the post, or even tell me what you mean by "ports@"...Is this another mailing list? Thanks, Anthony On Friday 04 April 2003 12:35, Matt wrote: > On Fri, 4 Apr 2003 12:25:33 +0200, CARTER Anthony wrote > > > Did portupgrade get updated then? > > > > I am not using gnome... > > > > The only thing I can think of is that an update has created a loop > > within itself, thereby launching subsequent sorts...I get 10 or so > > sorts, about 20-30 make's, kill them they come back... > > > > Anthony > > I guess this could be related to the problem Kris Kennaway just reported on > ports@ regarding "Index Build Failed". > > Matt. From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 03:24:35 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 051AE37B401 for ; Fri, 4 Apr 2003 03:24:35 -0800 (PST) Received: from tao.xtaz.co.uk (pc-62-30-69-139-az.blueyonder.co.uk [62.30.69.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC9C643FD7 for ; Fri, 4 Apr 2003 03:24:33 -0800 (PST) (envelope-from matt@xtaz.co.uk) Received: from webmail.xtaz.co.uk (matt@localhost.xtaz.co.uk [127.0.0.1]) by tao.xtaz.co.uk (8.12.9/8.12.9) with ESMTP id h34BOVHs012843; Fri, 4 Apr 2003 12:24:31 +0100 (BST) (envelope-from matt@xtaz.co.uk) From: "Matt" To: CARTER Anthony , freebsd-current@freebsd.org Date: Fri, 4 Apr 2003 11:24:31 +0000 Message-Id: <20030404112214.M12266@xtaz.co.uk> In-Reply-To: <200304041321.25821.a.carter@intrasoft.lu> References: <200304041156.38051.a.carter@intrasoft.lu> <200304041225.33721.a.carter@intrasoft.lu> <20030404103425.M46944@xtaz.co.uk> <200304041321.25821.a.carter@intrasoft.lu> X-Mailer: Open WebMail 2.00 20030325 X-OriginatingIP: 193.35.129.161 (matt) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: Re: OOOPS - portupgrade/Swapfile/??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 11:24:35 -0000 On Fri, 4 Apr 2003 13:21:25 +0200, CARTER Anthony wrote > Can you let me know about this, or forward a copy of the post, or > even tell me what you mean by "ports@"...Is this another mailing list? > > Thanks, > Anthony Sorry. I always assume people are on the same lists as me :) http://docs.freebsd.org/cgi/getmsg.cgi?fetch=605942+0+current/freebsd-ports and http://docs.freebsd.org/cgi/getmsg.cgi?fetch=620081+0+current/freebsd-ports is what I'm referring to. A circular dependancy in the ports tree. Which would explain the looping during package tool use. Matt. From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 03:34:18 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16C2837B401 for ; Fri, 4 Apr 2003 03:34:18 -0800 (PST) Received: from mail.cordis.lu (mail.cordis.lu [212.190.217.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC34D43FAF for ; Fri, 4 Apr 2003 03:34:16 -0800 (PST) (envelope-from a.carter@cordis.lu) Received: from mailsvr.intrasoft.lu (mail.intrasoft.lu [212.190.217.251]) by mail.cordis.lu (8.12.8/8.12.8) with ESMTP id h34Bbvnf018611; Fri, 4 Apr 2003 13:37:57 +0200 Received: by mail.intrasoft.lu with Internet Mail Service (5.5.2656.59) id <2HMPCKKV>; Fri, 4 Apr 2003 13:31:43 +0200 Received: from intra241.intrasoft.lu (212.190.217.170 [212.190.217.170]) by mailsvr.intrasoft.lu with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59) id 2HMPCKK4; Fri, 4 Apr 2003 13:31:42 +0200 From: CARTER Anthony To: Matt , CARTER Anthony , freebsd-current@freebsd.org Organization: Intrasoft Date: Fri, 4 Apr 2003 13:34:34 +0200 User-Agent: KMail/1.5 References: <200304041156.38051.a.carter@intrasoft.lu> <200304041321.25821.a.carter@intrasoft.lu> <20030404112214.M12266@xtaz.co.uk> In-Reply-To: <20030404112214.M12266@xtaz.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304041334.34159.a.carter@intrasoft.lu> X-Spam-Status: No, hits=-126.1 required=4.2 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT,USER_IN_WHITELIST version=2.50 X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: Re: OOOPS - portupgrade/Swapfile/??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 11:34:18 -0000 I can get it to do it with portupgrade -r Mesa...so we can limit it to Mesa and/or one of its dependencies...NO? I don't use gnome, i use KDE. Maybe a library? Anthony P.S. Matt, can you post this to port@ (put me in CC for replies) as I don't want to cross-post. Thanks On Friday 04 April 2003 13:24, Matt wrote: > On Fri, 4 Apr 2003 13:21:25 +0200, CARTER Anthony wrote > > > Can you let me know about this, or forward a copy of the post, or > > even tell me what you mean by "ports@"...Is this another mailing list? > > > > Thanks, > > Anthony > > Sorry. I always assume people are on the same lists as me :) > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=605942+0+current/freebsd-ports > and > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=620081+0+current/freebsd-ports > is what I'm referring to. A circular dependancy in the ports tree. Which > would explain the looping during package tool use. > > Matt. From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 03:57:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB60E37B401 for ; Fri, 4 Apr 2003 03:57:32 -0800 (PST) Received: from rrcs-se-24-73-205-166.biz.rr.com (rrcs-se-24-73-205-166.biz.rr.com [24.73.205.166]) by mx1.FreeBSD.org (Postfix) with SMTP id 7A23E43FCB for ; Fri, 4 Apr 2003 03:57:31 -0800 (PST) (envelope-from wade@ezri.org) Received: (qmail 95470 invoked from network); 4 Apr 2003 11:57:30 -0000 Received: from unknown (HELO ezri.org) (192.168.0.46) by rrcs-se-24-73-205-166.biz.rr.com with SMTP; 4 Apr 2003 11:57:30 -0000 Message-ID: <3E8D7326.4080006@ezri.org> Date: Fri, 04 Apr 2003 06:57:26 -0500 From: Wade Majors User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030403 X-Accept-Language: en-us, en MIME-Version: 1.0 To: CARTER Anthony References: <200304041156.38051.a.carter@intrasoft.lu> <200304041321.25821.a.carter@intrasoft.lu> <20030404112214.M12266@xtaz.co.uk> <200304041334.34159.a.carter@intrasoft.lu> In-Reply-To: <200304041334.34159.a.carter@intrasoft.lu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: OOOPS - portupgrade/Swapfile/??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 11:57:33 -0000 CARTER Anthony wrote: > I can get it to do it with portupgrade -r Mesa...so we can limit it to Mesa > and/or one of its dependencies...NO? > This bit me this morning, too. I believe Xft is where the circle happens, at least thats what i had to neuter to get other stuff building. -Wade From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 04:03:36 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 596BD37B401 for ; Fri, 4 Apr 2003 04:03:36 -0800 (PST) Received: from mail.cordis.lu (mail.cordis.lu [212.190.217.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 383C943FB1 for ; Fri, 4 Apr 2003 04:03:35 -0800 (PST) (envelope-from a.carter@cordis.lu) Received: from mailsvr.intrasoft.lu (mail.intrasoft.lu [212.190.217.251]) by mail.cordis.lu (8.12.8/8.12.8) with ESMTP id h34C6jnf019460; Fri, 4 Apr 2003 14:06:45 +0200 Received: by mail.intrasoft.lu with Internet Mail Service (5.5.2656.59) id <2HMPCK3K>; Fri, 4 Apr 2003 14:00:31 +0200 Received: from intra241.intrasoft.lu (212.190.217.170 [212.190.217.170]) by mailsvr.intrasoft.lu with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59) id 2HMPCK3J; Fri, 4 Apr 2003 14:00:25 +0200 From: CARTER Anthony To: Wade Majors , CARTER Anthony Organization: Intrasoft Date: Fri, 4 Apr 2003 14:03:17 +0200 User-Agent: KMail/1.5 References: <200304041156.38051.a.carter@intrasoft.lu> <200304041334.34159.a.carter@intrasoft.lu> <3E8D7326.4080006@ezri.org> In-Reply-To: <3E8D7326.4080006@ezri.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304041403.17150.a.carter@intrasoft.lu> X-Spam-Status: No, hits=-126.1 required=4.2 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT,USER_IN_WHITELIST version=2.50 X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: freebsd-current@freebsd.org Subject: Re: OOOPS - portupgrade/Swapfile/??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 12:03:36 -0000 How do you prevent a particular package from updating when doing a large portupgrade, or did you just do one at a time? Anthony On Friday 04 April 2003 13:57, Wade Majors wrote: > CARTER Anthony wrote: > > I can get it to do it with portupgrade -r Mesa...so we can limit it to > > Mesa and/or one of its dependencies...NO? > > This bit me this morning, too. I believe Xft is where the circle > happens, at least thats what i had to neuter to get other stuff building. > > -Wade From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 04:04:15 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 157E137B401 for ; Fri, 4 Apr 2003 04:04:15 -0800 (PST) Received: from lupinella.troll.no (lupinella.troll.no [80.232.37.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63E7843FA3 for ; Fri, 4 Apr 2003 04:04:14 -0800 (PST) (envelope-from bhughes@trolltech.com) Received: from reticent.troll.no ([80.232.37.28]:52492 "EHLO reticent.troll.no"; Fri, 4 Apr 2003 14:03:51 +0200 From: Bradley T Hughes Organization: Trolltech AS To: Wade Majors , CARTER Anthony Date: Fri, 4 Apr 2003 14:03:00 +0200 User-Agent: KMail/1.5 References: <200304041156.38051.a.carter@intrasoft.lu> <200304041334.34159.a.carter@intrasoft.lu> <3E8D7326.4080006@ezri.org> In-Reply-To: <3E8D7326.4080006@ezri.org> Sender: bhughes@trolltech.com MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304041403.00754.bhughes@trolltech.com> cc: freebsd-current@freebsd.org Subject: Re: OOOPS - portupgrade/Swapfile/??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 12:04:15 -0000 On Friday 04 April 2003 13:57, Wade Majors wrote: > This bit me this morning, too. I believe Xft is where the circle > happens, at least thats what i had to neuter to get other stuff > building. It seems you are right: Xft depends on XFree86-4-fontEncodings XFree86-4-fontEncodings depends on XFree86-4-clients XFree86-4-clients depends on Xft :/ > -Wade -- Bradley T. Hughes - bhughes at trolltech.com Trolltech AS - Waldemar Thranes gt. 98 N-0175 Oslo, Norway From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 04:06:44 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7E6B37B401 for ; Fri, 4 Apr 2003 04:06:44 -0800 (PST) Received: from lupinella.troll.no (lupinella.troll.no [80.232.37.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB17643FB1 for ; Fri, 4 Apr 2003 04:06:43 -0800 (PST) (envelope-from bhughes@trolltech.com) Received: from reticent.troll.no ([80.232.37.28]:52748 "EHLO reticent.troll.no"; Fri, 4 Apr 2003 14:06:19 +0200 From: Bradley T Hughes Organization: Trolltech AS To: Wade Majors , CARTER Anthony Date: Fri, 4 Apr 2003 14:05:28 +0200 User-Agent: KMail/1.5 References: <200304041156.38051.a.carter@intrasoft.lu> <3E8D7326.4080006@ezri.org> <200304041403.00754.bhughes@trolltech.com> In-Reply-To: <200304041403.00754.bhughes@trolltech.com> Sender: bhughes@trolltech.com MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304041405.28944.bhughes@trolltech.com> cc: freebsd-current@freebsd.org Subject: Re: OOOPS - portupgrade/Swapfile/??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 12:06:44 -0000 On Friday 04 April 2003 14:03, Bradley T Hughes wrote: > On Friday 04 April 2003 13:57, Wade Majors wrote: > > This bit me this morning, too. I believe Xft is where the circle > > happens, at least thats what i had to neuter to get other stuff > > building. > > It seems you are right: > > Xft depends on XFree86-4-fontEncodings Xft also depends on XFree86-4-fontScalable and XFree86-4-fontScalable depends on XFree86-4-clients... > XFree86-4-fontEncodings depends on XFree86-4-clients > XFree86-4-clients depends on Xft > > :/ -- Bradley T. Hughes - bhughes at trolltech.com Trolltech AS - Waldemar Thranes gt. 98 N-0175 Oslo, Norway From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 04:12:43 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5EAB37B417 for ; Fri, 4 Apr 2003 04:12:40 -0800 (PST) Received: from tao.xtaz.co.uk (pc-62-30-69-139-az.blueyonder.co.uk [62.30.69.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A8F443FB1 for ; Fri, 4 Apr 2003 04:12:39 -0800 (PST) (envelope-from matt@xtaz.co.uk) Received: from webmail.xtaz.co.uk (matt@localhost.xtaz.co.uk [127.0.0.1]) by tao.xtaz.co.uk (8.12.9/8.12.9) with ESMTP id h34CCYHs013675; Fri, 4 Apr 2003 13:12:34 +0100 (BST) (envelope-from matt@xtaz.co.uk) From: "Matt" To: Bradley T Hughes , Wade Majors , CARTER Anthony Date: Fri, 4 Apr 2003 12:12:33 +0000 Message-Id: <20030404120935.M13069@xtaz.co.uk> In-Reply-To: <200304041405.28944.bhughes@trolltech.com> References: <200304041156.38051.a.carter@intrasoft.lu> <3E8D7326.4080006@ezri.org> <200304041403.00754.bhughes@trolltech.com> <200304041405.28944.bhughes@trolltech.com> X-Mailer: Open WebMail 2.00 20030325 X-OriginatingIP: 193.35.129.161 (matt) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 cc: freebsd-current@freebsd.org Subject: Re: OOOPS - portupgrade/Swapfile/??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 12:12:44 -0000 Regarding this issue it has been tracked to the Xft port and noted on the freebsd-ports mailing list. So I guess it'll be fixed shortly. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=629561+0+current/freebsd-ports I would suggest any further conversation regarding it be done on that list as it's a bit off topic for this list. Regards, Matt. From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 04:28:42 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4E8337B401 for ; Fri, 4 Apr 2003 04:28:42 -0800 (PST) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81A3443F3F for ; Fri, 4 Apr 2003 04:28:42 -0800 (PST) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id 73B4A2ED413; Fri, 4 Apr 2003 04:28:42 -0800 (PST) Date: Fri, 4 Apr 2003 14:28:42 +0200 From: Maxime Henrion To: Nate Lawson Message-ID: <20030404122842.GP1750@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: MPSAFE fxp m_pkthdr not valid X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 12:28:43 -0000 Nate Lawson wrote: > I have gotten fxp running with MPSAFE and did a large scp transfer. It > ran for a few minutes and then paniced. It was trap 12 (page fault) at > address 0x24. Here is where it crashed: > > fxp_start+0xcc > 0xc0194a4c is in fxp_start (../../../dev/fxp/if_fxp.c:1263). > 1258 * been computed and stored in the checksum field > 1259 * in the TCP header. The stack should have > 1260 * already done this for us. > 1261 */ > 1262 > 1263 if (mb_head->m_pkthdr.csum_flags) { > 1264 if (mb_head->m_pkthdr.csum_flags & CSUM_DELAY_DATA) { > 1265 txp->tx_cb->ipcb_ip_activation_high = > 1266 FXP_IPCB_HARDWAREPARSING_ENABLE; > 1267 txp->tx_cb->ipcb_ip_schedule = > > The deref of mb_head->m_pkthdr is invalid. Note that my fxp_intr function > acquires the fxp lock right away so this shouldn't be a race in fxp. Since fxp_start() will usually be called by ether_output(), I don't see how acquiring the lock in fxp_intr() can protect you from such a race. You need to acquire the lock in fxp_start() before touching the interface queue, otherwise it may be preempted by an interrupt and this will lead to a race if fxp_intr() ends up calling fxp_start(). It really looks like that's what happened. Cheers, Maxime From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 04:44:25 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EBD337B401 for ; Fri, 4 Apr 2003 04:44:25 -0800 (PST) Received: from 72pixel.at (chello080110051025.501.15.vie.surfer.at [80.110.51.25]) by mx1.FreeBSD.org (Postfix) with SMTP id D4A8043FBF for ; Fri, 4 Apr 2003 04:44:23 -0800 (PST) (envelope-from ok@72pixel.at) Received: (qmail 24053 invoked from network); 4 Apr 2003 12:44:16 -0000 Received: from pc-00060 (HELO 72pixel.at) (10.1.0.60) by home.72pixel.at (10.1.0.10) with ESMTP; 04 Apr 2003 12:44:16 -0000 Message-ID: <3E8D7E1E.7000808@72pixel.at> Date: Fri, 04 Apr 2003 14:44:14 +0200 From: Otto Kucera User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: (no subject) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 12:44:25 -0000 -- ----------------------------------- Otto Kucera A-1020 Wien Engerthstrasse 137/6/7 Tel: +43 699 1 942 30 91 [neue Nummer!] Email: ok@72pixel.at Icq: 65351173 ----------------------------------- And root said rm -rf / ......and there was nothing Your mailserver MUST resolve properly (Fully Qualified Domain Name) or the mail will not go through! From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 07:03:37 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F0F337B401; Fri, 4 Apr 2003 07:03:37 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8486343F93; Fri, 4 Apr 2003 07:03:36 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.9/8.12.9) with ESMTP id h34F3ZMS027071 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 4 Apr 2003 10:03:36 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h34F3UT34041; Fri, 4 Apr 2003 10:03:30 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16013.40642.784712.453084@grasshopper.cs.duke.edu> Date: Fri, 4 Apr 2003 10:03:30 -0500 (EST) To: Nate Lawson In-Reply-To: References: <16012.32534.331966.216694@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: jeffr@freebsd.org cc: current@freebsd.org cc: jake@freebsd.org Subject: Giant required by uma (was Re: mbuf LOR) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 15:03:37 -0000 Nate Lawson writes: > > You're right about where the problem is (top of stack trace and listing > below). However, your patch causes an immediate panic on boot due to a > NULL deref. I don't think you want it to always return NULL if called > with M_NOWAIT set. :) Other ideas? > I suppose the only alternative is to "do it right" and remove Giant from the uma zone alloc code. >From looking at the code for a little while this morning, it looks like there are 3 allocators that could be called at this point in the code: 1) page_alloc(): Calls kmem_malloc(). Should be MPSAFE on NOWAIT allocations. Needs Giant on WAITOK allocations. 2) obj_alloc(): Calls vm_page_alloc() -- that's MPSAFE. Calls pmap_qenter() -- I've got no freaking clue if that's MPSAFE on all platforms. I think it is, since kmem_malloc is MPSAFE & it calls pmap_enter(), but I'm not sure. uma_small_alloc(): i386 - no uma_small_alloc, no problem alpha - uma_small_alloc is SMP safe ia64 - uma_small_alloc should be SMP safe, as it seems to be doing just the moral equivalent of PHYS_TO_K0SEG() to map the memory into the kernel. sparc64: I have no idea.. Drew > slab_zalloc + 0xdf > uma_zone_slab + 0xd8 > uma_zalloc_bucket + 0x15d > uma_zalloc_arg + 0x307 > malloc > ... > m_getcl > > (gdb) l *slab_zalloc+0xdf > 0xc02f646f is in slab_zalloc (../../../vm/uma_core.c:707). > 702 else > 703 wait &= ~M_ZERO; > 704 > 705 if (booted || (zone->uz_flags & UMA_ZFLAG_PRIVALLOC)) { > 706 mtx_lock(&Giant); > 707 mem = zone->uz_allocf(zone, > 708 zone->uz_ppera * UMA_SLAB_SIZE, &flags, wait); > 709 mtx_unlock(&Giant); > 710 if (mem == NULL) { > 711 ZONE_LOCK(zone); From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 07:27:40 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC38837B401 for ; Fri, 4 Apr 2003 07:27:40 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1174F43FBD for ; Fri, 4 Apr 2003 07:27:40 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.9/8.12.9) with ESMTP id h34FRdMS029001 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 4 Apr 2003 10:27:39 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h34FRY534061; Fri, 4 Apr 2003 10:27:34 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16013.42086.170914.788364@grasshopper.cs.duke.edu> Date: Fri, 4 Apr 2003 10:27:34 -0500 (EST) To: Nate Lawson In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: current@freebsd.org Subject: Re: MPSAFE fxp m_pkthdr not valid X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 15:27:41 -0000 Nate Lawson writes: > I have gotten fxp running with MPSAFE and did a large scp transfer. It > ran for a few minutes and then paniced. It was trap 12 (page fault) at > address 0x24. Here is where it crashed: > <..> > The deref of mb_head->m_pkthdr is invalid. Note that my fxp_intr function > acquires the fxp lock right away so this shouldn't be a race in fxp. Where else is the lock acquired? It would be easier to help if we could see a diff.. Drew From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 07:47:36 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A2D137B401 for ; Fri, 4 Apr 2003 07:47:36 -0800 (PST) Received: from ip68-14-60-78.no.no.cox.net (ip68-14-60-78.no.no.cox.net [68.14.60.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 633C943F3F for ; Fri, 4 Apr 2003 07:47:35 -0800 (PST) (envelope-from conrads@ip68-14-60-78.no.no.cox.net) Received: from ip68-14-60-78.no.no.cox.net (conrads@localhost [127.0.0.1]) h34FqapR011860 for ; Fri, 4 Apr 2003 09:52:36 -0600 (CST) (envelope-from conrads@ip68-14-60-78.no.no.cox.net) Received: (from conrads@localhost)h34FqaC3011859 for freebsd-current@freebsd.org; Fri, 4 Apr 2003 09:52:36 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 04 Apr 2003 09:52:36 -0600 (CST) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: Conrad Sabatier To: freebsd-current@freebsd.org Subject: So then, is fxp working OK again? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 15:47:36 -0000 Having had the same experiences as others described here recently with the fxp stuff, I'm just wondering if it's safe now to cvsup and try it again. I only have one machine here and if my net interface fails, I'm totally screwed. :-) -- Conrad Sabatier - "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 08:01:19 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D8B737B401 for ; Fri, 4 Apr 2003 08:01:19 -0800 (PST) Received: from rrcs-se-24-73-205-166.biz.rr.com (rrcs-se-24-73-205-166.biz.rr.com [24.73.205.166]) by mx1.FreeBSD.org (Postfix) with SMTP id 93A9243FA3 for ; Fri, 4 Apr 2003 08:01:18 -0800 (PST) (envelope-from wade@ezri.org) Received: (qmail 97555 invoked from network); 4 Apr 2003 16:00:39 -0000 Received: from unknown (HELO ezri.org) (192.168.0.46) by rrcs-se-24-73-205-166.biz.rr.com with SMTP; 4 Apr 2003 16:00:39 -0000 Message-ID: <3E8DAC22.80000@ezri.org> Date: Fri, 04 Apr 2003 11:00:34 -0500 From: Wade Majors User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030403 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Conrad Sabatier References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: So then, is fxp working OK again? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 16:01:19 -0000 Conrad Sabatier wrote: > Having had the same experiences as others described here recently with the > fxp stuff, I'm just wondering if it's safe now to cvsup and try it again. > I only have one machine here and if my net interface fails, I'm totally > screwed. :-) You can still boot your old kernel from the loader prompt, if such a thing happens. But everything appears normal to me so far. -Wade From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 08:12:12 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3A3937B404 for ; Fri, 4 Apr 2003 08:12:12 -0800 (PST) Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id B977143FB1 for ; Fri, 4 Apr 2003 08:12:11 -0800 (PST) (envelope-from ler@lerctr.org) Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) h34GC9YD028945 for ; Fri, 4 Apr 2003 10:12:09 -0600 (CST) Date: Fri, 4 Apr 2003 10:12:09 -0600 (CST) From: Larry Rosenman To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Subject: Building 5-CURRENT world under 4-STABLE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 16:12:13 -0000 Is it supported to be running under a 4-STABLE world and build a 5-CURRENT world? I have a dual-boot laptop with both 4 & 5 in separate partitions and cross-mounted appropriately. 5-RELEASE seems to occasionally Integer Exception out (seems to be with my wi card in), so I was wondering if it was supported to: cd /current/usr/src make buildworld Thanks, LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 08:16:12 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7599537B401 for ; Fri, 4 Apr 2003 08:16:12 -0800 (PST) Received: from ip68-14-60-78.no.no.cox.net (ip68-14-60-78.no.no.cox.net [68.14.60.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 988B643F85 for ; Fri, 4 Apr 2003 08:16:11 -0800 (PST) (envelope-from conrads@ip68-14-60-78.no.no.cox.net) Received: from ip68-14-60-78.no.no.cox.net (conrads@localhost [127.0.0.1]) h34GKipR012442; Fri, 4 Apr 2003 10:20:44 -0600 (CST) (envelope-from conrads@ip68-14-60-78.no.no.cox.net) Received: (from conrads@localhost)h34GKiVs012441; Fri, 4 Apr 2003 10:20:44 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3E8DAC22.80000@ezri.org> Date: Fri, 04 Apr 2003 10:20:44 -0600 (CST) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: Conrad Sabatier To: Wade Majors cc: freebsd-current@freebsd.org Subject: Re: So then, is fxp working OK again? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 16:16:12 -0000 On 04-Apr-2003 Wade Majors wrote: > Conrad Sabatier wrote: >> Having had the same experiences as others described here recently with >> the fxp stuff, I'm just wondering if it's safe now to cvsup and try it >> again. >> I only have one machine here and if my net interface fails, I'm totally >> screwed. :-) > > You can still boot your old kernel from the loader prompt, if such a > thing happens. But everything appears normal to me so far. Yes, except I ran into some problems this last time where, after successfully booting the new kernel in single-user mode, installing world, running mergemaster, rebooting and finding the new kernel didn't work, I couldn't get the old kernel to work, either. :-( Apparently, something had changed just enough somewhere to make the old kernel go kerplooey, too. -- Conrad Sabatier - "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 08:31:37 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5052637B401 for ; Fri, 4 Apr 2003 08:31:37 -0800 (PST) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC68343FBD for ; Fri, 4 Apr 2003 08:31:36 -0800 (PST) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id D41972ED431; Fri, 4 Apr 2003 08:31:36 -0800 (PST) Date: Fri, 4 Apr 2003 18:31:36 +0200 From: Maxime Henrion To: Conrad Sabatier Message-ID: <20030404163136.GQ1750@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: So then, is fxp working OK again? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 16:31:37 -0000 Conrad Sabatier wrote: > Having had the same experiences as others described here recently with the > fxp stuff, I'm just wondering if it's safe now to cvsup and try it again. > I only have one machine here and if my net interface fails, I'm totally > screwed. :-) It should. If it doesn't, I'm interested in knowing it. :-) Cheers, Maxime From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 08:57:44 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5A8537B401 for ; Fri, 4 Apr 2003 08:57:44 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-150.dsl.lsan03.pacbell.net [63.207.60.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0E2B43FAF for ; Fri, 4 Apr 2003 08:57:42 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 6F66266E2B; Fri, 4 Apr 2003 08:57:38 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 40AD312AA; Fri, 4 Apr 2003 08:57:38 -0800 (PST) Date: Fri, 4 Apr 2003 08:57:38 -0800 From: Kris Kennaway To: Larry Rosenman Message-ID: <20030404165738.GA21750@rot13.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i cc: freebsd-current@freebsd.org Subject: Re: Building 5-CURRENT world under 4-STABLE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 16:57:45 -0000 --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Apr 04, 2003 at 10:12:09AM -0600, Larry Rosenman wrote: > Is it supported to be running under a 4-STABLE world and build > a 5-CURRENT world? Yes. Kris --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+jbmCWry0BWjoQKURAg47AJ0Y4tEPHqCT2XiDnz05AEduD25tNwCcD5+5 lhuNV9rWWmD73AWh0toTsB8= =uN8g -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ-- From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 09:16:05 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1307237B401; Fri, 4 Apr 2003 09:16:05 -0800 (PST) Received: from mail.tcoip.com.br (erato.tco.net.br [200.220.254.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01EB243F3F; Fri, 4 Apr 2003 09:16:02 -0800 (PST) (envelope-from dcs@tcoip.com.br) Received: from tcoip.com.br ([10.0.2.6]) by mail.tcoip.com.br (8.11.6/8.11.6) with ESMTP id h34HFv919426; Fri, 4 Apr 2003 14:15:57 -0300 Message-ID: <3E8DBDCC.2070107@tcoip.com.br> Date: Fri, 04 Apr 2003 14:15:56 -0300 From: "Daniel C. Sobral" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030326 X-Accept-Language: en-us, en, pt-br, ja MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Konsole crash with libthr X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 17:16:05 -0000 It seems Konsole didn't like libthr a bit. And, now that I think about it, neither did licq, though I didn't notice it at the time I was closing the KDE Crash Handler windows. The trace I'm posting below is typical. I had some 20 windows with the same thing, and the error occured at startup. I have two main konsole windows, each with dozens of individual konsole tabs. One of the main windows did not come up at all, and the other one had just a few tabs. So it seems the error only shows up during it's startup, but it does not always happen. On a tentative guess, it might happen because it takes a LONG time for the start up to complete, so some timeout might not be reacting well to be expired (well, the fact that the error is related to wait4 contributed to that hypothesis). 0x29068b53 in wait4 () from /usr/lib/libc.so.5 #0 0x29068b53 in wait4 () from /usr/lib/libc.so.5 #1 0x2905a015 in waitpid () from /usr/lib/libc.so.5 #2 0x290155f5 in _waitpid (wpid=7, status=0x7, options=7) at /usr/src/lib/libthr/thread/thr_syscalls.c:386 #3 0x286d79aa in KCrash::defaultCrashHandler(int) (sig=6) at kcrash.cpp:235 #4 #5 0x29068833 in kill () from /usr/lib/libc.so.5 #6 0x2936b4f7 in TEPty::makePty(bool) () from /usr/local/lib/konsole.so #7 0x2936b58a in TEPty::startPgm(char const*, QValueList&, char const*) () from /usr/local/lib/konsole.so #8 0x2936bdaa in TEPty::commSetupDoneC() () from /usr/local/lib/konsole.so #9 0x286811b9 in KProcess::start(KProcess::RunMode, KProcess::Communication) ( this=0x81b6c00, runmode=7, comm=NoCommunication) at kprocess.cpp:320 #10 0x2936add6 in TEPty::run(char const*, QStrList&, char const*, bool, char const*, char const*) () from /usr/local/lib/konsole.so #11 0x2938f389 in TESession::run() () from /usr/local/lib/konsole.so #12 0x293911d9 in TESession::qt_invoke(int, QUObject*) () from /usr/local/lib/konsole.so #13 0x28a25358 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/X11R6/lib/libqt-mt.so.3 #14 0x28cf228d in QSignal::signal(QVariant const&) () from /usr/X11R6/lib/libqt-mt.so.3 #15 0x28a3ec38 in QSignal::activate() () from /usr/X11R6/lib/libqt-mt.so.3 #16 0x28a459f3 in QSingleShotTimer::event(QEvent*) () from /usr/X11R6/lib/libqt-mt.so.3 #17 0x289c85e5 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/X11R6/lib/libqt-mt.so.3 #18 0x289c83ab in QApplication::notify(QObject*, QEvent*) () from /usr/X11R6/lib/libqt-mt.so.3 #19 0x2864c1a9 in KApplication::notify(QObject*, QEvent*) (this=0x7, receiver=0x825a000, event=0xbfbff2a0) at kapplication.cpp:453 #20 0x289a48a7 in QEventLoop::activateTimers() () from /usr/X11R6/lib/libqt-mt.so.3 #21 0x28983ba1 in QEventLoop::processEvents(unsigned) () from /usr/X11R6/lib/libqt-mt.so.3 #22 0x289dc000 in QEventLoop::enterLoop() () from /usr/X11R6/lib/libqt-mt.so.3 #23 0x289dbf38 in QEventLoop::exec() () from /usr/X11R6/lib/libqt-mt.so.3 #24 0x289c8771 in QApplication::exec() () from /usr/X11R6/lib/libqt-mt.so.3 #25 0x2937057d in main () from /usr/local/lib/konsole.so #26 0x0804cb1f in launch (argc=3, _name=0x805ba84 "konsole", args=0x805bacd "", cwd=0x0, envc=0, envs=0x805bad1 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x7 ) at kinit.cpp:547 #27 0x0804d906 in handle_launcher_request (sock=7) at kinit.cpp:1021 #28 0x0804de57 in handle_requests (waitForPid=0) at kinit.cpp:1189 #29 0x0804ef53 in main (argc=3, argv=0xbfbffc78, envp=0x7) at kinit.cpp:1540 #30 0x0804b115 in _start () -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: Daniel.Capo@tco.net.br Daniel.Sobral@tcoip.com.br dcs@tcoip.com.br Outros: dcs@newsguy.com dcs@freebsd.org capo@notorious.bsdconspiracy.net Youth is when you blame all your troubles on your parents; maturity is when you learn that everything is the fault of the younger generation. From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 09:19:57 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F80C37B401 for ; Fri, 4 Apr 2003 09:19:57 -0800 (PST) Received: from mail.tcoip.com.br (erato.tco.net.br [200.220.254.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1E6343FBD for ; Fri, 4 Apr 2003 09:19:54 -0800 (PST) (envelope-from dcs@tcoip.com.br) Received: from tcoip.com.br ([10.0.2.6]) by mail.tcoip.com.br (8.11.6/8.11.6) with ESMTP id h34HJq919595 for ; Fri, 4 Apr 2003 14:19:52 -0300 Message-ID: <3E8DBEB8.70904@tcoip.com.br> Date: Fri, 04 Apr 2003 14:19:52 -0300 From: "Daniel C. Sobral" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030326 X-Accept-Language: en-us, en, pt-br, ja MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: panic: lockmgr: locking against myself X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 17:19:57 -0000 As always, whenever I crash before background fsck is finished... root@dcs:/opt/home/dcs$ gdb -k /usr/obj/usr/src/sys/DCS/kernel.debug /var/crash/vmcore.8 GNU gdb 5.2.1 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-undermydesk-freebsd"... panic: lockmgr: locking against myself panic messages: --- panic: lockmgr: locking against myself syncing disks, buffers remaining... 882 882 880 880 880 880 880 880 880 880 880 822 823 822 822 822 822 822 unknown: device timeout unknown: DMA timeout 824 822 827 822 822 822 822 822 822 822 822 822 822 822 822 822 822 822 822 822 822 822 822 giving up on 710 buffers Uptime: 4m41s Dumping 255 MB ata0: resetting devices .. done 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 --- Reading symbols from /boot/kernel/snd_cmi.ko...done. Loaded symbols for /boot/kernel/snd_cmi.ko Reading symbols from /boot/kernel/snd_pcm.ko...done. Loaded symbols for /boot/kernel/snd_pcm.ko Reading symbols from /usr/obj/usr/src/sys/DCS/modules/usr/src/sys/modules/acpi/acpi.ko.debug...done. Loaded symbols for /usr/obj/usr/src/sys/DCS/modules/usr/src/sys/modules/acpi/acpi.ko.debug Reading symbols from /boot/kernel/green_saver.ko...done. Loaded symbols for /boot/kernel/green_saver.ko Reading symbols from /usr/obj/usr/src/sys/DCS/modules/usr/src/sys/modules/linux/linux.ko.debug...done. Loaded symbols for /usr/obj/usr/src/sys/DCS/modules/usr/src/sys/modules/linux/linux.ko.debug #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:239 239 dumping++; (kgdb) bt full #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:239 No locals. #1 0xc01ec443 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:371 No locals. #2 0xc01ec743 in panic () at /usr/src/sys/kern/kern_shutdown.c:542 td = (struct thread *) 0xc29fc980 bootopt = 256 newpanic = 1 buf = "lockmgr: locking against myself", '\0' #3 0xc01d0c22 in lockmgr (lkp=0xc77cf97c, flags=34144290, interlkp=0x2000020, td=0xc29fc980) at /usr/src/sys/kern/kern_lock.c:447 error = 0 thr = (struct thread *) 0xc29fc980 extflags = 33554464 lockflags = 34144290 #4 0xc0245f10 in BUF_TIMELOCK (bp=0xc77cf97c, locktype=34144290, interlock=0x0, wmesg=0x0, catch=0, timo=0) at buf.h:319 ret = 0 #5 0xc0241528 in flushbuflist (blist=0xc77cf8b0, flags=4, vp=0xc2ef86d8, slpflag=0, slptimeo=0, errorp=0x0) at /usr/src/sys/kern/vfs_subr.c:1226 bp = (struct buf *) 0xc77cf97c nbp = (struct buf *) 0x2090022 found = 1 error = 0 #6 0xc02411d9 in vinvalbuf (vp=0xc2ef86d8, flags=4, cred=0x0, td=0x0, slpflag=0, slptimeo=0) at /usr/src/sys/kern/vfs_subr.c:1140 blist = (struct buf *) 0x0 error = 0 object = (struct vm_object *) 0xc038d420 #7 0xc027ef0a in ffs_truncate (vp=0xc2ef86d8, length=0, flags=2048, cred=0x0, td=0xc29fc980) at /usr/src/sys/ufs/ffs/ffs_inode.c:273 ovp = (struct vnode *) 0xc2ef86d8 oip = (struct inode *) 0xc2506510 bn = -4595188392983498048 lbn = -4595796903951530429 ---Type to continue, or q to quit--- lastblock = -3284296585705422848 lastiblock = {7825250020, 4294852608, 4294983680} indir_lbn = {-3284295173694292736, 0, -3976995127051695744} oldblks = {-4422543730025529563, -4597468310878027639, -4603193868120500600, 7560230888, 1545117794085, -4074619939888858781, 3530282736, -4603163193464072504, 3265263592, 591635055342, 24892416000, 1425736, 1427344, 3262735212, -4444941709473941328} newblks = {-4595796560354146749, -4595830507774119232, -4595689636071734605, -4602925638822930956, -3284296118623889348, -4595830507775840915, -4597472472701337599, -4422543733250063938, -3284296015545203986, -4597468307654643792, 16109450424, -3284295792166188672, -4597468310878027194, -4597197328506420774, -4595797247547378808} count = -3284296431086600192 blocksreleased = 0 datablocks = 96 fs = (struct fs *) 0xc279d000 bp = (struct buf *) 0xc0210643 needextclean = 0 softdepslowdown = 0 extblocks = 0 offset = -1024489768 size = 0 level = 0 nblocks = -764684924 i = -1024489768 error = 0 allerror = 0 osize = 3224950592 #8 0xc02825c0 in ffs_snapshot (mp=0xc25ecc00, snapfile=---Can't read userspace from dump, or kernel process--- ) at /usr/src/sys/ufs/ffs/ffs_snapshot.c:654 numblks = 262138 blkno = -4595798621938448829 blkp = (ufs2_daddr_t *) 0xc0387108 snapblklist = (ufs2_daddr_t *) 0xc03862a8 error = 5 cg = -1071577533 snaploc = 0 i = 0 ---Type to continue, or q to quit--- size = 0 len = -1033974784 loc = 0 flag = 220270592 starttime = {tv_sec = 0, tv_nsec = 0} endtime = {tv_sec = -1071577533, tv_nsec = -1070042672} saved_nice = 0 '\0' redo = 0 snaplistsize = 0 lp = (int32_t *) 0x0 space = (void *) 0xc0387108 copy_fs = (struct fs *) 0x0 fs = (struct fs *) 0xc279d000 snaphead = (struct snaphead *) 0xc02105db td = (struct thread *) 0xc29fc980 ip = (struct inode *) 0xc2506510 xp = (struct inode *) 0xd26bd7e8 bp = (struct buf *) 0xc77cf8b0 nbp = (struct buf *) 0xc038d320 ibp = (struct buf *) 0x0 sbp = (struct buf *) 0x0 nd = {ni_dirp = 0x80c1c80 ---Can't read userspace from dump, or kernel process--- -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: Daniel.Capo@tco.net.br Daniel.Sobral@tcoip.com.br dcs@tcoip.com.br Outros: dcs@newsguy.com dcs@freebsd.org capo@notorious.bsdconspiracy.net The rule on staying alive as a forcaster is to give 'em a number or give 'em a date, but never give 'em both at once. -- Jane Bryant Quinn From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 09:27:22 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61F7437B401 for ; Fri, 4 Apr 2003 09:27:22 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94C4B43F75 for ; Fri, 4 Apr 2003 09:27:21 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.9/8.12.9) with ESMTP id h34HRLMS009404 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 4 Apr 2003 12:27:21 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h34HRFi34160; Fri, 4 Apr 2003 12:27:15 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16013.49267.867140.38329@grasshopper.cs.duke.edu> Date: Fri, 4 Apr 2003 12:27:15 -0500 (EST) To: Nate Lawson In-Reply-To: References: <16012.32534.331966.216694@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: current@freebsd.org Subject: Re: mbuf LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 17:27:22 -0000 Nate Lawson writes: > You're right about where the problem is (top of stack trace and listing > below). However, your patch causes an immediate panic on boot due to a > NULL deref. I don't think you want it to always return NULL if called > with M_NOWAIT set. :) Other ideas? The following patch boots & passed the basic 'make -j16 buildworld' test on x86 SMP. As I outlined before, I'm not certain if it is safe on all platforms. I'm really eager to see your fxp locking diffs. Even if you're not comfortable sharing them with the world yet, I'd be interested in helping out on this. Drew Index: vm/uma_core.c =================================================================== RCS file: /home/ncvs/src/sys/vm/uma_core.c,v retrieving revision 1.51 diff -u -r1.51 uma_core.c --- vm/uma_core.c 26 Mar 2003 18:44:53 -0000 1.51 +++ vm/uma_core.c 4 Apr 2003 15:11:34 -0000 @@ -703,10 +703,15 @@ wait &= ~M_ZERO; if (booted || (zone->uz_flags & UMA_ZFLAG_PRIVALLOC)) { - mtx_lock(&Giant); - mem = zone->uz_allocf(zone, - zone->uz_ppera * UMA_SLAB_SIZE, &flags, wait); - mtx_unlock(&Giant); + if ((wait & M_NOWAIT) == 0) { + mtx_lock(&Giant); + mem = zone->uz_allocf(zone, + zone->uz_ppera * UMA_SLAB_SIZE, &flags, wait); + mtx_unlock(&Giant); + } else { + mem = zone->uz_allocf(zone, + zone->uz_ppera * UMA_SLAB_SIZE, &flags, wait); + } if (mem == NULL) { ZONE_LOCK(zone); return (NULL); From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 09:41:22 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B92037B401 for ; Fri, 4 Apr 2003 09:41:22 -0800 (PST) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A27143FAF for ; Fri, 4 Apr 2003 09:41:19 -0800 (PST) (envelope-from ru@whale.sunbay.crimea.ua) Received: from whale.sunbay.crimea.ua (ru@localhost [127.0.0.1]) h34HfEgg070669 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Apr 2003 20:41:15 +0300 (EEST) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.12.9/8.12.8/Submit) id h34HfE6l070664; Fri, 4 Apr 2003 20:41:14 +0300 (EEST) (envelope-from ru) Date: Fri, 4 Apr 2003 20:41:14 +0300 From: Ruslan Ermilov To: Kris Kennaway Message-ID: <20030404174114.GC67714@sunbay.com> References: <20030404165738.GA21750@rot13.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vOmOzSkFvhd7u8Ms" Content-Disposition: inline In-Reply-To: <20030404165738.GA21750@rot13.obsecurity.org> User-Agent: Mutt/1.5.4i cc: freebsd-current@freebsd.org cc: Larry Rosenman Subject: Re: Building 5-CURRENT world under 4-STABLE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 17:41:22 -0000 --vOmOzSkFvhd7u8Ms Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 04, 2003 at 08:57:38AM -0800, Kris Kennaway wrote: > On Fri, Apr 04, 2003 at 10:12:09AM -0600, Larry Rosenman wrote: > > Is it supported to be running under a 4-STABLE world and build > > a 5-CURRENT world? >=20 > Yes. >=20 Currently it is supported, but may not be soon. The issue was brought up with Technical Review Board who are currently in the process of voting on the supported upgrade path matrix (both native and cross arch), and one possibility might be that the only supported upgrade path will be from 4-STABLE to 5.0-RELEASE, and only then to 5.0-CURRENT. Even if this will be ratified, I will still continue to work on a wider update range that will be available in the form of patches. Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --vOmOzSkFvhd7u8Ms Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+jcO6Ukv4P6juNwoRAlPZAJ9wnwJt3fHgqz+d9Nud3Q6gC5N57gCbBTTp PDDX+Ym9eL9tVeIPyHCpjw0= =Uhmn -----END PGP SIGNATURE----- --vOmOzSkFvhd7u8Ms-- From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 09:45:42 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64E2537B401 for ; Fri, 4 Apr 2003 09:45:42 -0800 (PST) Received: from mail.tcoip.com.br (erato.tco.net.br [200.220.254.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EE2643F3F for ; Fri, 4 Apr 2003 09:45:40 -0800 (PST) (envelope-from dcs@tcoip.com.br) Received: from tcoip.com.br ([10.0.2.6]) by mail.tcoip.com.br (8.11.6/8.11.6) with ESMTP id h34HjW920236; Fri, 4 Apr 2003 14:45:32 -0300 Message-ID: <3E8DC4BC.7000607@tcoip.com.br> Date: Fri, 04 Apr 2003 14:45:32 -0300 From: "Daniel C. Sobral" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030326 X-Accept-Language: en-us, en, pt-br, ja MIME-Version: 1.0 To: Conrad Sabatier References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: So then, is fxp working OK again? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 17:45:42 -0000 Conrad Sabatier wrote: > Having had the same experiences as others described here recently with the > fxp stuff, I'm just wondering if it's safe now to cvsup and try it again. > I only have one machine here and if my net interface fails, I'm totally > screwed. :-) > reinstallkernel and boot-conf kernel.old are your friends. :-) -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: Daniel.Capo@tco.net.br Daniel.Sobral@tcoip.com.br dcs@tcoip.com.br Outros: dcs@newsguy.com dcs@freebsd.org capo@notorious.bsdconspiracy.net Vote for ME -- I'm well-tapered, half-cocked, ill-conceived and TAX-DEFERRED! From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 09:50:48 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E7D337B404 for ; Fri, 4 Apr 2003 09:50:48 -0800 (PST) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F40E43FBD for ; Fri, 4 Apr 2003 09:50:47 -0800 (PST) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9/8.12.9) with ESMTP id h34HokPn060106 for ; Fri, 4 Apr 2003 12:50:46 -0500 (EST) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9/8.12.9/Submit) id h34HokJq060105 for current@freebsd.org; Fri, 4 Apr 2003 12:50:46 -0500 (EST) (envelope-from barney) Date: Fri, 4 Apr 2003 12:50:45 -0500 From: Barney Wolff To: current@freebsd.org Message-ID: <20030404175045.GA60079@pit.databus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang) Subject: CPUTYPE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 17:50:48 -0000 I need to buildworld (current) and ports to run on both p3 and athlon-mp. What's a good value for CPUTYPE, or should I just leave it out? Thanks. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 10:02:35 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EF9037B405 for ; Fri, 4 Apr 2003 10:02:35 -0800 (PST) Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id D606243FEA for ; Fri, 4 Apr 2003 10:02:30 -0800 (PST) (envelope-from ler@lerctr.org) Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) h34I2RYD004633 for ; Fri, 4 Apr 2003 12:02:28 -0600 (CST) Date: Fri, 4 Apr 2003 12:02:27 -0600 (CST) From: Larry Rosenman To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Subject: Integer Exception/5-CURRENT/cbb related X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 18:02:35 -0000 I just upgraded my laptop's HDD from 20G to 60G, and set it up as a dual boot 4-STABLE and 5-CURRENT. When running under BOTH 5.0-RELEASE and 5.0-CURRENT from today, with my LinkSys WPC11 V3.0 card in, I get random Integer Exception panics. The 5.0-CURRENT dropped me in to DB, and the backtrace pointed to cbb. This is my first experience with 5.0, so I'm not sure what I need to do to get all the pieces for someone to look at it. I'm more than willing to get whatever information y'all need. Thanks, LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 10:23:44 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E902F37B401 for ; Fri, 4 Apr 2003 10:23:43 -0800 (PST) Received: from hak.cnd.mcgill.ca (hak.cnd.mcgill.ca [132.216.11.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D14543F93 for ; Fri, 4 Apr 2003 10:23:43 -0800 (PST) (envelope-from mat@hak.cnd.mcgill.ca) Received: from hak.cnd.mcgill.ca (localhost.cnd.mcgill.ca [127.0.0.1]) by hak.cnd.mcgill.ca (8.12.3p2/8.12.3) with ESMTP id h34IPvqC031167 for ; Fri, 4 Apr 2003 13:25:57 -0500 (EST) (envelope-from mat@hak.cnd.mcgill.ca) Received: (from mat@localhost) by hak.cnd.mcgill.ca (8.12.3p2/8.12.3/Submit) id h34IPv6B031166 for freebsd-current@freebsd.org; Fri, 4 Apr 2003 13:25:57 -0500 (EST) Date: Fri, 4 Apr 2003 13:25:57 -0500 From: Mathew Kanner To: freebsd-current@freebsd.org Message-ID: <20030404182557.GK17533@cnd.mcgill.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: I speak for myself, operating in Montreal, CANADA User-Agent: Mutt/1.5.3i Subject: midi problem, an isa device on a pci card X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 18:23:44 -0000 Hello, I've been fiddling with pci drivers in freebsd for a couple of months and up to now everything has ok, I did a midi driver for es137x which was relatively easy because the io was done on the pci bus. I was very pleased that there were enough resources for a newbie like me to dive into kernel hacking. Now I want to do one for the cmi card, but it seems to offer the midi device on the isa bus, as does a bunch of cards. I'm sure they did this to confuse me. Linux seems to be happy just inb,outb in their pci driver, which seems uncool to me. Also since I can program the mpu to appear to different locations I think the ISA bus driver can help determine the best one to use... Theory of Reality (mostly hand waving, as I've done no code yet) Drivers: cmi(pci), my pci sound, it's on board btw. mpushim(isa), the mpu401 from the tree but hacked to receive from the pci soundcard driver How I think should work: probe cmi, attach cmi, do { enable mpu401 at port region, probe attach mpushim while ( ! mpushim attached ) done Big question mark: How do I create isa devices from a pci device. Do I search up the soundcard tree for the pci bus then search down for the isa bus, then create_child(..."mpushim")? How do I tell the shim before the probe/attach what io region to look at, do I fiddle with ivars (or some internal structure), do I mess with hints via kenv(9) [Is there a kenv(9)? ] I think that these questions equally apply to joysticks. Thanks, --Mat -- Brain: Are you pondering what I'm pondering? Pinky: I think so, Brain, but if the plural of mouse is mice, wouldn't the plural of spouse be spice? From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 10:52:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1641437B404 for ; Fri, 4 Apr 2003 10:52:32 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.65.60]) by mx1.FreeBSD.org (Postfix) with SMTP id F039A43F85 for ; Fri, 4 Apr 2003 10:52:30 -0800 (PST) (envelope-from s.moeck@gmx.de) Received: (qmail 14015 invoked by uid 65534); 4 Apr 2003 18:52:29 -0000 Received: from dsl254-062-177.sea1.dsl.speakeasy.net (HELO xpn) (216.254.62.177) by mail.gmx.net (mp003-rz3) with SMTP; 04 Apr 2003 20:52:29 +0200 From: =?iso-8859-1?Q?Stephan_M=F6ck?= To: Date: Fri, 4 Apr 2003 11:52:15 +0200 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.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: imon on FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 18:52:32 -0000 I want to use imon inode monitor to watch file activity. Is it possible to do that with FreeBSD? And where can I get a update or a patch for the installation? From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 12:43:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51AAB37B401 for ; Fri, 4 Apr 2003 12:43:07 -0800 (PST) Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64DE743F93 for ; Fri, 4 Apr 2003 12:43:06 -0800 (PST) (envelope-from ler@lerctr.org) Received: from lerlaptop.iadfw.net (lerlaptop.iadfw.net [206.66.13.21]) (authenticated bits=0)h34Kh3YC015405 for ; Fri, 4 Apr 2003 14:43:03 -0600 (CST) Date: Fri, 04 Apr 2003 14:43:02 -0600 From: Larry Rosenman To: freebsd-current@freebsd.org Message-ID: <9400000.1049488982@lerlaptop.iadfw.net> In-Reply-To: References: X-Mailer: Mulberry/3.0.3 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Subject: Re: Integer Exception/5-CURRENT/cbb related X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 20:43:07 -0000 Ok, I got a panic dump: Script started on Fri Apr 4 14:25:59 2003 lerlaptop# shutdown -r now?[12`cd /?[K ?[Klerlaptop# k??[Kgdb -k kernel.1 vmcore.1 GNU gdb 5.2.1 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-undermydesk-freebsd"... panic: integer divide fault panic messages: --- Fatal trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xc0193d12 stack pointer = 0x10:0xd63cecc0 frame pointer = 0x10:0xd63cece0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, IOPL = 0 current process = 23 (irq11: cbb0 cbb1+++) trap number = 18 panic: integer divide fault syncing disks, buffers remaining... 3798 3798 3797 3797 3797 3797 3797 3797 3797 3797 3797 3797 3797 3797 3797 3797 3797 3797 3797 3797 3797 3797 giving up on 2250 buffers Uptime: 2m27s Dumping 503 MB ata0: resetting devices .. done 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448 464 480 496 --- Reading symbols from /usr/obj/usr/src/sys/LERLAPTOP/modules/usr/src/sys/modules/acpi/acpi.ko.deb ug...done. Loaded symbols for /usr/obj/usr/src/sys/LERLAPTOP/modules/usr/src/sys/modules/acpi/acpi.ko.deb ug Reading symbols from /usr/obj/usr/src/sys/LERLAPTOP/modules/usr/src/sys/modules/linux/linux.ko.d ebug...done. Loaded symbols for /usr/obj/usr/src/sys/LERLAPTOP/modules/usr/src/sys/modules/linux/linux.ko.d ebug #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:239 239 dumping++; (kgdb) bt #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:239 #1 0xc0245b1a in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:371 #2 0xc0245d93 in panic () at /usr/src/sys/kern/kern_shutdown.c:542 #3 0xc039a10e in trap_fatal (frame=0xc14eb130, eva=0) at /usr/src/sys/i386/i386/trap.c:843 #4 0xc0399c02 in trap (frame= {tf_fs = -1051852776, tf_es = -1051852784, tf_ds = -700710896, tf_edi = -1051807440, tf_esi = -1051832832, tf_ebp = -700650272, tf_isp = -700650324, tf_ebx = -1007012800, tf_edx = -546881536, tf_ecx = -1069393536, tf_eax = 0, tf_trapno = 18, tf_err = 0, tf_eip = -1072087790, tf_cs = 8, tf_eflags = 514, tf_esp = -1071394701, tf_ss = 132}) at /usr/src/sys/i386/i386/trap.c:640 #5 0xc038b318 in calltrap () at {standard input}:96 #6 0xc0234502 in ithread_loop (arg=0xc3f8aa00) at /usr/src/sys/kern/kern_intr.c:536 #7 0xc0233742 in fork_exit (callout=0xc02343b0 , arg=0x0, frame=0x0) at /usr/src/sys/kern/kern_fork.c:796 (kgdb) lerlaptop# ^D??exit Script done on Fri Apr 4 14:26:16 2003 I have the core, and the kernel. DMESG: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Fri Apr 4 12:04:46 CST 2003 ler@lerlaptop:/usr/obj/usr/src/sys/LERLAPTOP Preloaded elf kernel "/boot/kernel/kernel" at 0xc0573000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc05730a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1129573614 Hz CPU: Intel(R) Pentium(R) III Mobile CPU 1133MHz (1129.57-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383f9ff real memory = 527958016 (503 MB) avail memory = 506736640 (483 MB) Allocating major#253 to "net" Allocating major#252 to "g_ctl" Allocating major#251 to "pci" Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 ACPI-0625: *** Info: GPE Block1 defined as GPE16 to GPE31 pcibios: BIOS version 2.10 Using $PIR table, 9 entries at 0xc00fdf30 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0xfc08-0xfc0b on acpi0 acpi_cpu0: port 0x530-0x537 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe0000000-0xe007ffff,0xe8000000-0xefffffff irq 11 at device 2.0 on pci0 agp0: detected 8060k stolen memory agp0: aperture size is 128M pci0: at device 2.1 (no driver attached) uhci0: port 0x18c0-0x18df irq 11 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x18e0-0x18ff irq 11 at device 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pcib1: at device 30.0 on pci0 pci1: on pcib1 cbb0: irq 11 at device 10.0 on pci1 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: irq 11 at device 10.1 on pci1 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 rl0: port 0x2000-0x20ff mem 0xe0200800-0xe02008ff irq 11 at device 13.0 on pci1 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:e0:00:7e:d0:45 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fwohci0: vendor=10cf, dev=2010 fwohci0: <1394 Open Host Controller Interface> mem 0xe0200000-0xe02007ff irq 11 at device 14.0 on pci1 fwohci0: PCI bus latency is 64. fwohci0: Could not map memory device_probe_and_attach: fwohci0 attach returned 6 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1c20-0x1c2f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 mem 0xe0100000-0xe01003ff at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ichsmb0: port 0x1c00-0x1c1f irq 11 at device 31.3 on pci0 smbus0: on ichsmb0 smb0: on smbus0 pcm0: port 0x1880-0x18bf,0x1000-0x10ff irq 11 at device 31.5 on pci0 pcm0: pci0: at device 31.6 (no driver attached) acpi_button0: on acpi0 acpi_lid0: on acpi0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 speaker0 port 0x61 on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 acpi_ec0: port 0x66,0x62 on acpi0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2e8-0x2ef irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 1 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Allocating major#250 to "devstat" orm0: