From owner-freebsd-current Sun Aug 2 00:17:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10557 for freebsd-current-outgoing; Sun, 2 Aug 1998 00:17:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10548 for ; Sun, 2 Aug 1998 00:17:34 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id IAA22469; Sun, 2 Aug 1998 08:17:23 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199808020717.IAA22469@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: lcremean@tidalwave.net cc: Brian Somers , current@FreeBSD.ORG Subject: Re: Identd problems on -current of 980724 In-reply-to: Your message of "Sat, 01 Aug 1998 14:45:55 EDT." <19980801144555.A5316@st-lcremean.tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Aug 1998 08:17:22 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, Aug 01, 1998 at 01:30:00PM +0100, Brian Somers wrote: > > Does it make any difference if you remove the ``set mtu'' ? > > > Yes, it does. Removing all refs to "set mtu" and "pred1" make things work. I > wonder why that is... I've no idea - it was a guess ! I suspect however that there may have been a problem (out by one error?) because of the compressed data being larger than the original. That area of the implementation looks suspect. I'll investigate into it more. Thanks for your reply. > -- > Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) > A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did > $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net > FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) > My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code > -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 05:57:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08684 for freebsd-current-outgoing; Sun, 2 Aug 1998 05:57:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA08679 for ; Sun, 2 Aug 1998 05:57:15 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.8.8/8.8.7) with ESMTP id OAA09388 for ; Sun, 2 Aug 1998 14:57:07 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.8.7/8.7.3) with UUCP id OAA08488 for current@freebsd.org; Sun, 2 Aug 1998 14:57:07 +0200 (MET DST) Received: from localhost (root@localhost) by nihil.plaut.de (8.8.8/8.8.8) with SMTP id OAA00250 for ; Sun, 2 Aug 1998 14:56:10 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Sun, 2 Aug 1998 14:56:10 +0200 (CEST) From: Michael Reifenberger To: FreeBSD-Current Subject: DEVFS & PCMCIA progress Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, while trying to mount my JAZ-drive after getting recognized by the PCMCIA stuff I get: part 1, start=32, size=2093024 mbr: slice 0 too big (1ff000 \> 1fe82a:0 ) Mounting/disklabeling without DEVFS works. Any Ideas? More Info: ################ fdisk shows: ******* Working on device /dev/rsd0 ******* parameters extracted from in-core disklabel are: cylinders=1022 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=1022 heads=64 sectors/track=32 (2048 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 32, size 2093024 (1021 Meg), flag 0 beg: cyl 0/ sector 1/ head 1; end: cyl 1021/ sector 32/ head 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: disklabel shows: ################ # /dev/rsd0c: type: SCSI disk: sd1s2 label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 1021 sectors/unit: 2093024 rpm: 5400 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 2090976 0 4.2BSD 1024 8192 0 # (Cyl. 0 - 1020*) c: 2093024 0 unused 0 0 # (Cyl. 0 - 1021*) Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 08:19:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19648 for freebsd-current-outgoing; Sun, 2 Aug 1998 08:19:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19643 for ; Sun, 2 Aug 1998 08:19:37 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id RAA03701 for ; Sun, 2 Aug 1998 17:24:09 +0200 (CEST) (envelope-from regnauld@deepo.prosa.dk) X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id RAA28870 for ; Sun, 2 Aug 1998 17:24:38 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id RAA28085; Sun, 2 Aug 1998 17:22:04 +0200 (CEST) Message-ID: <19980802172204.50682@deepo.prosa.dk> Date: Sun, 2 Aug 1998 17:22:04 +0200 From: Philippe Regnauld To: freebsd-current@FreeBSD.ORG Subject: system lock-up (SMP, AHC_TAGENABLE, softupdates) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG System: GigaByte 586-DX, 2xP5-133, 48MB, on-board 7880 SCSI, 4GB IBM DCAS-34330W. Current as of CTM src-cur 3477 (< 48 hours). Softupdates enabled on _all_ filesystems: no problem, did two make buildworlds/installworld in a row, as long as AHC_TAGENABLE is off. If I enable AHC_TAGENABLE, and push the system a bit (lots of FS activity) -> freeze. Last time it happened was with X, so I'd have to do it again in text mode to write down the AHC TAG messages... Config file follows. # # TETARD # machine "i386" cpu "I586_CPU" ident TETARD-SMP maxusers 32 options SMP options APIC_IO options "CPU_FASTER_5X86_FPU" options INET options FFS options PROCFS options "CD9660" options "COMPAT_43" options UCONSOLE options KTRACE options DDB options USERCONFIG options VISUAL_USERCONFIG options SOFTUPDATES options SYSVSHM #SYSV shared memory options SYSVSEM #SYSV semaphores options SYSVMSG #SYSV messages options "SHMMAXPGS=1024" #Max shared memory pages (4Kb/page) options "SCSI_2_DEF" # Force CCS SCSI-I -> SCSI-II options "VM86" config kernel root on sd0 controller isa0 device npx0 at isa? port "IO_NPX" irq 13 vector npxintr controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller pci0 device ahc0 controller scbus0 options AHC_TAGENABLE # ? options AHC_ALLOW_MEMIO options AHC_SCBPAGING_ENABLE options SCSI_REPORT_GEOMETRY device sd0 #SCSI disks device st0 #SCSI tapes device cd0 #SCSI cdrom # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options "MAXCONS=12" #Max. virtual consoles device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr device lpt0 at isa? port? tty irq 7 vector lptintr device ed0 at isa? port 0x340 net irq 9 iomem 0xd0000 vector edintr pseudo-device loop #Loopback interface pseudo-device ether #Ethernet # ijppp uses tun instead of ppp device pseudo-device pty 32 #Pseudo ttys (telnet, xterm, etc...) pseudo-device gzip #Exec gzipped a.out's pseudo-device speaker #Beep pseudo-device tun 2 #Tunnel device pseudo-device snp 3 #Snoop devices pseudo-device bpfilter 4 #Berkeley Packet Filter pseudo-device vn #Vnode driver options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity options IPDIVERT #divert sockets # SoundBlaster 16 device pcm0 at isa? port 0x220 tty irq 10 drq 1 flags 0x15 vector pcmintr -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 08:22:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20003 for freebsd-current-outgoing; Sun, 2 Aug 1998 08:22:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.baldcom.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19997 for ; Sun, 2 Aug 1998 08:22:08 -0700 (PDT) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.baldcom.net (8.8.8/8.8.7) with SMTP id NAA01376; Sat, 1 Aug 1998 13:37:40 -0400 (EDT) Date: Sat, 1 Aug 1998 13:37:40 -0400 (EDT) From: Brian Feldman To: Terry Lambert cc: mike@smith.net.au, freebsd-current@FreeBSD.ORG Subject: Re: flock(2) problem & fix In-Reply-To: <199808010302.UAA06065@usr06.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think you're right, if nothing than for the fact that it's already the norm. This is the first time I've ever done kernel hacking, but I've tested the patch and made a final version of it, a correction of syntax, but it shouldn't be used because it breaks what you think it would, like apache, which have been using flocking wrong since the very beginning. But anyway, I'll post the correct patch, just because I don't want my dain-bramaged code floating around ;) Cheers, Brian Feldman green@unixhelp.org --- src/sys/kern/kern_descrip.c.orig Fri Jul 31 18:28:30 1998 +++ src/sys/kern/kern_descrip.c Sat Aug 1 13:01:10 1998@@ -986,6 +986,9 @@ register struct file *fp; struct vnode *vp; struct flock lf;+ struct stat fst;+ short gr;+ boolean_t ok = 0; if ((unsigned)uap->fd >= fdp->fd_nfiles || (fp = fdp->fd_ofiles[uap->fd]) == NULL)@@ -1007,10 +1010,27 @@ lf.l_type = F_RDLCK; else return (EBADF);+ vn_stat(vp, &fst, p);+ if (uap->how & LOCK_EX && p->p_cred->pc_ucred->cr_uid != 0 && + fst.st_uid != p->p_cred->pc_ucred->cr_uid && + !(fst.st_mode & S_IWOTH) && !(fst.st_mode & S_IWGRP)) + return (EPERM); + if (!(fst.st_mode & S_IWGRP)) + ok = 1; + else { + for (gr = 0; gr < p->p_cred->pc_ucred->cr_ngroups; gr++) + if (p->p_cred->pc_ucred->cr_groups[gr - 1] == fst.st_gid) { + ok = 1; + break; + } + } + if (ok) { fp->f_flag |= FHASLOCK; if (uap->how & LOCK_NB) return (VOP_ADVLOCK(vp, (caddr_t)fp, F_SETLK, &lf, F_FLOCK)); return (VOP_ADVLOCK(vp, (caddr_t)fp, F_SETLK, &lf, F_FLOCK|F_WAIT)); + } else + return (EPERM); } /* On Sat, 1 Aug 1998, Terry Lambert wrote: > > Whoops, I suppose you're right, I think I'll start testing it out =) With > > respect to Tom's comment, this won't cnvert an exclusive to a > > non-exclusive lock, it will return EPERM; also, the program SHOULDn't be > > using an exclusive lock, it should be using a shared lock. > > What if they are using it as a semaphore, and could care less whether > they were reading or writing the file? > > > I could see a case where a program opend a file for read only to > run an image of a program from a foreign architecture, for instance, > and would want to use read to ensure that the "swap store" was not > accidently corrupted by the simulator. > > They would want exclude modification of the image they intend only to > *read* out from under them. > > In other words, they want to simulate VEXEC for a read-only mapped > executable in user space. > > > > A secondard situation would be a set of non-work-to-do processing engines > working on a source data set. > > Program one opens the file, writes new data, closes it, and signals > program two. > > Program two uses the file and the output of program one to do work, and > then requests the original program to interpolate new data bsed on its > results, and the process repeats. > > Once could see this happening, for example, in a pseudo realtime data > analysis tool that could only accept new data on soft boundries, but > had two programs, one optimized for Fourier analysis, the other for > Gaussian reduction (maybe the Fourier analysis program was seperate > because it runs on a DSP and not on the main processor, and the DSP > is not part of the acquisition channel). > > You could use such a system for all sorts of biometric regconitions > (speech, speaker, retinal scanning, finger print, etc.). One could > even envision a "frozen" back propagation neural networking program > that had to be reset each time it was run because the outputs were > no longer being clamped by a human giving it feedback. > > > Anyway, suffice to say, I think exclusive locking a file without the > intention *or possibility* of writing is an "ok thing to do". > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 10:17:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28738 for freebsd-current-outgoing; Sun, 2 Aug 1998 10:17:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28731 for ; Sun, 2 Aug 1998 10:17:21 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id LAA07746; Sun, 2 Aug 1998 11:11:39 -0600 (MDT) Date: Sun, 2 Aug 1998 11:11:39 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199808021711.LAA07746@narnia.plutotech.com> To: Philippe Regnauld cc: current@FreeBSD.ORG Subject: Re: system lock-up (SMP, AHC_TAGENABLE, softupdates) Newsgroups: pluto.freebsd.current In-Reply-To: <19980802172204.50682@deepo.prosa.dk> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980802172204.50682@deepo.prosa.dk> you wrote: > System: GigaByte 586-DX, 2xP5-133, 48MB, on-board 7880 SCSI, > 4GB IBM DCAS-34330W. > Current as of CTM src-cur 3477 (< 48 hours). > > Softupdates enabled on _all_ filesystems: no problem, did > two make buildworlds/installworld in a row, as long > as AHC_TAGENABLE is off. > > If I enable AHC_TAGENABLE, and push the system a bit (lots > of FS activity) -> freeze. Last time it happened was with X, > so I'd have to do it again in text mode to write down the AHC > TAG messages... Assuming it is an AHC problem. I had a freeze not to long ago using the SCSI CAM code that only seemed to occur with soft-updates enabled. I haven't had the spare time to go re-enable soft-updates to reproduce this again, but considering the I/O regression tests I run successfully on this system when it's not running soft-updates, my inclination is to believe the bug is not in the Adaptec driver. Using tagged queuing may exacerbate the problem (most likely by tying up more kernel resources for pending I/O), but I doubt it is the root of the problem. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 10:21:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29180 for freebsd-current-outgoing; Sun, 2 Aug 1998 10:21:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29175 for ; Sun, 2 Aug 1998 10:21:04 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id TAA04919; Sun, 2 Aug 1998 19:25:30 +0200 (CEST) (envelope-from regnauld@deepo.prosa.dk) X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id TAA28979; Sun, 2 Aug 1998 19:26:00 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id TAA28638; Sun, 2 Aug 1998 19:23:27 +0200 (CEST) Message-ID: <19980802192327.02628@deepo.prosa.dk> Date: Sun, 2 Aug 1998 19:23:27 +0200 From: Philippe Regnauld To: "Justin T. Gibbs" Cc: current@FreeBSD.ORG Subject: Re: system lock-up (SMP, AHC_TAGENABLE, softupdates) References: <19980802172204.50682@deepo.prosa.dk> <199808021711.LAA07746@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199808021711.LAA07746@narnia.plutotech.com>; from Justin T. Gibbs on Sun, Aug 02, 1998 at 11:11:39AM -0600 X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Justin T. Gibbs writes: > > Assuming it is an AHC problem. I had a freeze not to long ago Well, last time I had these problems (before USENIX) I was running without SOFTUPDATES, and I had error messages like: ordered tag queued ordered tag send SCB 0x4 timed out ... (machine locked, with messages looping). This does not happen with a NCR875 and the maximum number of tags enabled. > Using tagged queuing may exacerbate the problem (most likely by tying > up more kernel resources for pending I/O), but I doubt it is the root > of the problem. I'll do more tests. -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 10:25:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29557 for freebsd-current-outgoing; Sun, 2 Aug 1998 10:25:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29533 for ; Sun, 2 Aug 1998 10:25:08 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id LAA10133; Sun, 2 Aug 1998 11:24:58 -0600 (MDT) Message-Id: <199808021724.LAA10133@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Philippe Regnauld cc: "Justin T. Gibbs" , current@FreeBSD.ORG Subject: Re: system lock-up (SMP, AHC_TAGENABLE, softupdates) In-reply-to: Your message of "Sun, 02 Aug 1998 19:23:27 +0200." <19980802192327.02628@deepo.prosa.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Aug 1998 11:19:26 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Using tagged queuing may exacerbate the problem (most likely by tying >> up more kernel resources for pending I/O), but I doubt it is the root >> of the problem. > > I'll do more tests. You should also try CAM. It is much more reliable than the SCSI driver in current. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 13:46:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18803 for freebsd-current-outgoing; Sun, 2 Aug 1998 13:46:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18782 for ; Sun, 2 Aug 1998 13:46:39 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id WAA10697; Sun, 2 Aug 1998 22:45:08 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id WAA17255; Sun, 2 Aug 1998 22:35:45 +0200 (CEST) (envelope-from andreas) Message-ID: <19980802223545.A17248@klemm.gtn.com> Date: Sun, 2 Aug 1998 22:35:45 +0200 From: Andreas Klemm To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: Sendmail-8.9.1 in -current & in 3.0-RELEASE??? References: <199808020022.EAA18943@serv.etrust.ru> <199808020418.MAA21585@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808020418.MAA21585@spinner.netplex.com.au>; from Peter Wemm on Sun, Aug 02, 1998 at 12:18:16PM +0800 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 02, 1998 at 12:18:16PM +0800, Peter Wemm wrote: > Sergey A. Osokin wrote: > > Hello! > > Does sendmail-8.9.1 containes in last -current version or in > > feature 3.0-RELEASE ? > > > > Rgdz, > > oZZ, > > osa@etrust.ru > > Yes, > > It will be imported within the next 12 hours. Great ! -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 16:58:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00448 for freebsd-current-outgoing; Sun, 2 Aug 1998 16:58:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00442 for ; Sun, 2 Aug 1998 16:58:24 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id QAA25147; Sun, 2 Aug 1998 16:58:16 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd025135; Sun Aug 2 16:58:13 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id QAA26831; Sun, 2 Aug 1998 16:58:04 -0700 (MST) From: Terry Lambert Message-Id: <199808022358.QAA26831@usr01.primenet.com> Subject: Re: Sendmail-8.9.1 in -current & in 3.0-RELEASE??? To: peter@netplex.com.au (Peter Wemm) Date: Sun, 2 Aug 1998 23:58:04 +0000 (GMT) Cc: osa@serv.etrust.ru, current@FreeBSD.ORG In-Reply-To: <199808020418.MAA21585@spinner.netplex.com.au> from "Peter Wemm" at Aug 2, 98 12:18:16 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hello! > > Does sendmail-8.9.1 containes in last -current version or in > > feature 3.0-RELEASE ? > > Yes, > > It will be imported within the next 12 hours. > > Cheers, > -Peter How are you going to resolve the "SneakyCat" licensing issues? Specifically, it's ability to change a UCB licensed program into a pseudo-GPL'ed program? (I use "pseudo" here because, unlike GPL, which poison-pills itself from coopting UCB licensed code because of the "claim credit" clause, the "SneakyCat" license has no such compunctions about socializing UCB licensed code...). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 17:35:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03562 for freebsd-current-outgoing; Sun, 2 Aug 1998 17:35:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (haiti-77.ppp.hooked.net [206.169.228.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03549 for ; Sun, 2 Aug 1998 17:35:49 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with ESMTP id RAA00347 for ; Sun, 2 Aug 1998 17:37:00 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Wed, 29 Jul 1998 16:47:18 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: current Subject: listen() and SOMAXCONN? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Welp, the subject of where to get the value for the maximum number of sockets listen() can handle safely. On most other systems SOMAXCONN is defined in sys/socket.h. A quick check of the man page informs me that I should use the MIB kern.somaxconn. Well, I checked the header files, and SOMAXCONN is defined to 128 in sys/socket.h, and there is no kern.somaxconn MIB. Any thoughts? - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 17:37:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03751 for freebsd-current-outgoing; Sun, 2 Aug 1998 17:37:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (haiti-77.ppp.hooked.net [206.169.228.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03745 for ; Sun, 2 Aug 1998 17:37:29 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with SMTP id RAA00397 for ; Sun, 2 Aug 1998 17:38:43 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sun, 2 Aug 1998 17:38:43 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: current Subject: ext2fs panic.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, in trying to "recover" the disk that I had dedicated for Linux recently, I decided to see if I could even read the partition under fbsd. Well, the partition (sd1s1) mounted fine, but paniced as soon as I ran the command sync. Since I was in single user mode at the time, no dump device was configured.. However, it paniced in ext2_sync, the trace looked something like: ext2_sync sync syscall Xsyscall - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 17:51:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05201 for freebsd-current-outgoing; Sun, 2 Aug 1998 17:51:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05196 for ; Sun, 2 Aug 1998 17:51:14 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id UAA21748; Sun, 2 Aug 1998 20:51:04 -0400 (EDT) (envelope-from wollman) Date: Sun, 2 Aug 1998 20:51:04 -0400 (EDT) From: Garrett Wollman Message-Id: <199808030051.UAA21748@khavrinen.lcs.mit.edu> To: Alex Cc: current Subject: listen() and SOMAXCONN? In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > defined in sys/socket.h. A quick check of the man page informs me that I > should use the MIB kern.somaxconn. Well, I checked the header files, and > SOMAXCONN is defined to 128 in sys/socket.h, and there is no > kern.somaxconn MIB. Any thoughts? Under FreeBSD, you should use -1. The MIB variable is in the kern.ipc subtree. For portability, you should be prepared to use SOMAXCONN on other systems. (It's easy to imagine an autoconf test which would determine whether -1 works or not, or you could just do it at run time.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 17:56:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06057 for freebsd-current-outgoing; Sun, 2 Aug 1998 17:56:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (haiti-77.ppp.hooked.net [206.169.228.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06048 for ; Sun, 2 Aug 1998 17:56:44 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with SMTP id RAA00535; Sun, 2 Aug 1998 17:57:52 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sun, 2 Aug 1998 17:57:51 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Garrett Wollman cc: current Subject: Re: listen() and SOMAXCONN? In-Reply-To: <199808030051.UAA21748@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 2 Aug 1998, Garrett Wollman wrote: > < said: > > > defined in sys/socket.h. A quick check of the man page informs me that I > > should use the MIB kern.somaxconn. Well, I checked the header files, and > > SOMAXCONN is defined to 128 in sys/socket.h, and there is no > > kern.somaxconn MIB. Any thoughts? > > Under FreeBSD, you should use -1. The MIB variable is in the kern.ipc > subtree. For portability, you should be prepared to use SOMAXCONN on > other systems. (It's easy to imagine an autoconf test which would > determine whether -1 works or not, or you could just do it at run > time.) Ahh, quite nifty indeed. Thanks :) - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 19:25:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12910 for freebsd-current-outgoing; Sun, 2 Aug 1998 19:25:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from soccer.ksg.com (ftw-tsa6-23.cyberramp.net [207.158.119.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12904 for ; Sun, 2 Aug 1998 19:25:04 -0700 (PDT) (envelope-from kgor@soccer.ksg.com) Received: (from kgor@localhost) by soccer.ksg.com (8.8.8/8.8.8) id VAA21857; Sun, 2 Aug 1998 21:29:04 -0500 (CDT) (envelope-from kgor) Date: Sun, 2 Aug 1998 21:29:04 -0500 (CDT) Message-Id: <199808030229.VAA21857@soccer.ksg.com> From: "Kent S. Gordon" To: current@FreeBSD.ORG Subject: Building kernel and lkm under -current elf? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently changed my system to use elf binaries, but have not been able to successfully build the linux lkm or a kernel. It seems that any aout binary I create core dump normally with floating point exception. Are other people having this problem? What aout libraries and objects are needed? Can they be compiled on the elf system? I lost my boot disk recently and rebuilt the boot disk starting from a 2.2.6 CDROM, so I have plenty of places to make a mistake. -- Kent S. Gordon KSG -- Unix, Network, Database Consulting Postal: 76 Corral Drive North, Keller, Texas 76248 e-mail: kgor@ksg.com Phone:(817)431-8775 Resume: http://www.ksg.com/resume.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 19:35:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13701 for freebsd-current-outgoing; Sun, 2 Aug 1998 19:35:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13686 for ; Sun, 2 Aug 1998 19:35:06 -0700 (PDT) (envelope-from rock@wurzelausix.cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id EAA05547 for ; Mon, 3 Aug 1998 04:34:55 +0200 (CEST) Received: from gate.ics (acc2-149.telip.uni-sb.de [134.96.112.149]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id EAA00594 for ; Mon, 3 Aug 1998 04:34:55 +0200 (CEST) Received: from doom.ics (doom.ics [192.168.0.254]) by gate.ics (8.9.0/1998061600) with ESMTP id EAA24475 for ; Mon, 3 Aug 1998 04:33:50 +0200 (CEST) Received: (from rock@localhost) by doom.ics (8.8.8+Sun/8.8.8) id EAA21221; Mon, 3 Aug 1998 04:35:17 +0200 (MET DST) From: "D. Rock" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 3 Aug 1998 04:35:16 +0200 (MET DST) To: current@FreeBSD.ORG Subject: IO performance (UFS read clustering), bad ZIP drive performance X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13765.8590.159445.703954@doom> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get unacceptable performance from my SCSI ZIP drive (compared to other operating systems). While UFS writing is OK (up to the capabilities of the drive: 600-1000 kB/s), everything else (UFS read, MSDOSFS r/w, mtools) is extremely slow (down to 80 kB/s). It seems the SCSI ZIP drive is only able to perform a maximum of 40-45 requests per second. UFS writes get clustered to larger chunks, resulting in good throughput. But it seems that reads don't get clustered at all. iostat tells me, it is doing 40-45 tps, resulting to a throughput of 160 kB/s with 4kB block size. MSDOSFS is worse with 2kB cluster size. And no read/write clustering at all. mtools perform best with the raw device (mtools are doing read/write clustering for themselves). But if I use the block device, I wouldn't expect the performance go down. But with block devices a single large request seems to be divided into several small ones (of 2k each). This can be verified with a simple dd run: # dd if=/dev/sd0 of=/dev/null bs=512k and in another window # iostat 1 tty sd0 cd0 cpu tin tout sps tps msps sps tps msps us ni sy in id 0 5 11 1 0.0 0 0 0.0 3 95 2 1 0 0 271828 454 0.0 0 0 0.0 0 88 9 4 0 0 271574 385 0.0 0 0 0.0 0 88 10 2 0 0 271778 438 0.0 0 0 0.0 0 84 14 2 0 I have seen this behaviour in 3 different setups, all with different SCSI controllers: Adaptec 2940UW, NCR810, AIC6360 chip Why doesn't read clustering on UFS work, but write clustering(*)? Why does the (now simulated?) block device divide I/O into chunks of only 2k? Only UFS read performance is of big interest to me (writes are OK). I don't use MSDOSFS on ZIP drives and can configure mtools to use the raw device. Daniel (*) A really old current (July 1997) doesn't have this problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 20:17:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17477 for freebsd-current-outgoing; Sun, 2 Aug 1998 20:17:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17472; Sun, 2 Aug 1998 20:17:42 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id XAA04257; Sun, 2 Aug 1998 23:17:34 -0400 (EDT) Date: Sun, 2 Aug 1998 23:17:33 -0400 (EDT) From: The Hermit Hacker To: scsi@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: Odd problems with -current... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Morning... I'm trying to debug a problem that I'm having on my home machine that has me totally baffled, and am hoping someone here can "show me the way"... I just put in a 2gig Seagate SCSI drive on my system, to replace a 2gig IDE drive, and after running for awhile, it *seems* that the drive is powering down, cause when I try to access something on that drive after leaving for a period of time, you can hear it power back up again. I've checked through /etc/rc.conf, to see if maybe I had some laptop related config items enabled, to "power save", but nothing jumped out at me. I just installed from current.freebsd.org:/3.0-19980711-SNAP, if that helps any... Is this something reasonably obvious that I'm doing wrong, or overlooking? Thanks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 20:53:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20040 for freebsd-current-outgoing; Sun, 2 Aug 1998 20:53:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA20030 for ; Sun, 2 Aug 1998 20:53:12 -0700 (PDT) (envelope-from imp@village.org) Received: from pencil-box.village.org [10.0.0.22] by rover.village.org with esmtp (Exim 1.71 #1) id 0z3BgE-0005st-00; Sun, 2 Aug 1998 21:53:02 -0600 Received: from pencil-box.village.org (localhost [127.0.0.1]) by pencil-box.village.org (8.8.8/8.8.3) with ESMTP id XAA06153; Sat, 1 Aug 1998 23:49:45 -0600 (MDT) Message-Id: <199808020549.XAA06153@pencil-box.village.org> To: Stefan Eggers Subject: Re: State of current... Cc: Henry Vogt , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 20 Jul 1998 12:10:47 +0200." <199807201010.MAA07091@semyam.dinoco.de> References: <199807201010.MAA07091@semyam.dinoco.de> Date: Sat, 01 Aug 1998 23:49:45 -0600 From: "M. Warner Losh" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807201010.MAA07091@semyam.dinoco.de> Stefan Eggers writes: : > So this appears to me like a new introduced bug in the shared memory handling : ? : > (Or am I wrong that the difference between :0.0 and :0.0 is the way : > IPC between X-Server and -Client ist handled ?) : : As far as I know :0.0 uses a Unix domain socket under /tmp while the : latter form uses TCP/IP. :0.0 is defined to use the best transport possible for the local machine, which in the case of all X servers for FreeBSD uses the unix domain socket. hostname:0.0 uses tcp/ip transport. shared memory is used only for pixmaps in the freebsd x server. Warner P.S. This is for both x inside (errr xig) and xfree86 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 22:44:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29735 for freebsd-current-outgoing; Sun, 2 Aug 1998 22:44:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29724 for ; Sun, 2 Aug 1998 22:44:12 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id NAA25528; Mon, 3 Aug 1998 13:41:48 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199808030541.NAA25528@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: osa@serv.etrust.ru, current@FreeBSD.ORG Subject: Re: Sendmail-8.9.1 in -current & in 3.0-RELEASE??? In-reply-to: Your message of "Sun, 02 Aug 1998 23:58:04 GMT." <199808022358.QAA26831@usr01.primenet.com> Date: Mon, 03 Aug 1998 13:41:47 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > Hello! > > > Does sendmail-8.9.1 containes in last -current version or in > > > feature 3.0-RELEASE ? > > > > Yes, > > > > It will be imported within the next 12 hours. > > > > Cheers, > > -Peter > > How are you going to resolve the "SneakyCat" licensing issues? Aren't you thinking of DB-2.0 from SleepyCat? Sendmail is a different kettle of fish. > Specifically, it's ability to change a UCB licensed program into > a pseudo-GPL'ed program? (I use "pseudo" here because, unlike > GPL, which poison-pills itself from coopting UCB licensed code > because of the "claim credit" clause, the "SneakyCat" license > has no such compunctions about socializing UCB licensed code...). Assuming you're talking about sendmail (which is what we're talking about :-) - in the UCB License, where does it prohibit you from adding extra restrictions? I see no conflict between the original UCB copyrighted code and the entire backage being under a more restricted "umbrella" license. Yes, it's unfortunate that there are extra restrictions, but that's life. Considering how sendmail development is now being funded, we came out of it pretty well I think. > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 23:28:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04394 for freebsd-current-outgoing; Sun, 2 Aug 1998 23:28:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-asfm08--167.sirius.net [205.134.241.167]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04383 for ; Sun, 2 Aug 1998 23:28:25 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.8.8/8.8.8) with ESMTP id XAA01496 for ; Sun, 2 Aug 1998 23:27:08 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199808030627.XAA01496@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: NFS diskless booting (NFS root/swap) broken in -current? X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Aug 1998 23:27:08 -0700 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't been able to boot my 486 test machine diskless with the latest -current. It used to boot (using nb8390.com under DOS) and run fine when my server was -stable, but I unfortunately haven't tried it in weeks and didn't keep a copy of the working sources to compare. My config file for the diskless node is unchanged from when it used to work. The same kernel can boot off of the local UIDE disk or entirely off of NFS (both root and swap). (I use it for testing CMD's UIDE chip and was trying to use it to debug the AppleTalk loop-back problem.) The latest -current kernel will boot off of the disk, but won't off of NFS. locore.s doesn't appear to recognize that it got a legit NFS boot request or a root and instead falls back to the default old-style boot (which fails for different reasons). Forcing it to boot NFS by adding BOOTP_NFSROOT in the config file causes this crash: panic: nfs_mountroot: socreate(0000): 43 It's correct in that the protocol is not supported, but it shouldn't be using 0 for the protocol family. It doesn't matter if I netboot the kernel, or copy it to the disk and then boot it. Did something change such that I need some new magic incantation in the config file now? (The BOOTP_NFSV3 option didn't make any difference.) When I boot (root and swap) off of the local disk, it is quite happy NFS-mounting my server, so I suspect some kernel change in the past few weeks broke diskless. I didn't notice anything obvious in the CVS logs for the few files I looked at, but I'm probably not looking at the right place. Thanks in advance for any help. -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 2 23:38:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06039 for freebsd-current-outgoing; Sun, 2 Aug 1998 23:38:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06033 for ; Sun, 2 Aug 1998 23:38:41 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id XAA21184; Sun, 2 Aug 1998 23:38:29 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp04.primenet.com, id smtpd021167; Sun Aug 2 23:38:23 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id XAA11787; Sun, 2 Aug 1998 23:38:14 -0700 (MST) From: Terry Lambert Message-Id: <199808030638.XAA11787@usr01.primenet.com> Subject: Re: Sendmail-8.9.1 in -current & in 3.0-RELEASE??? To: peter@netplex.com.au (Peter Wemm) Date: Mon, 3 Aug 1998 06:38:14 +0000 (GMT) Cc: tlambert@primenet.com, osa@serv.etrust.ru, current@FreeBSD.ORG In-Reply-To: <199808030541.NAA25528@spinner.netplex.com.au> from "Peter Wemm" at Aug 3, 98 01:41:47 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Assuming you're talking about sendmail (which is what we're talking about > :-) - in the UCB License, where does it prohibit you from adding extra > restrictions? It doesn't. I'm just interested in avoiding these particular restrictions. Otherwise we all might as well unsubscribe here and go subscribe to the Linux lists instead, since our reason for being here is largely eroded. > I see no conflict between the original UCB copyrighted code and the entire > backage being under a more restricted "umbrella" license. Yes, it's > unfortunate that there are extra restrictions, but that's life. Considering > how sendmail development is now being funded, we came out of it pretty well > I think. The Sleepycat license (the dbm code required by sendmail is under this license) is insidious in that it is effectively GPL. It's not possible to Use (as opposed to Utilize) the source code. In other words, it makes no contribution to advancement of the arts and sciences, since it only "raises the bar" for GPL and GPL-like users, and not for commercial and other entities who actually realize they need to be able to fund their efforts by amortizing costs. This is a dangerous precedent, unless you are already a radical Stallmanite and/or member of the American Communist Party. Certainly, all my future contributions are likely to contain a fifth restriction, restricting against requiring source code distribution in derivative works. I would encourage FreeBSD to adopt this as a blanket policy, and I would encourage XFree86 and other to do the same. If people want to GPL code in furtherance of a socio-political agenda, let them write their own damn code to do it. I prefer to write code that raises the bar for everyone; if I don't raise the bar for the commercial entities by making the code commercially usable by their competitors, then commercial entities are free to ignore the advancement, and wallow in the minimal necessary advances to ensure a continued revenue stream while minimizing engineering costs. We all know a company or two wallowing in that mire, don't we? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 00:04:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08468 for freebsd-current-outgoing; Mon, 3 Aug 1998 00:04:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08463 for ; Mon, 3 Aug 1998 00:04:39 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.8/8.7.3) id JAA00678; Mon, 3 Aug 1998 09:04:10 +0200 (CEST) From: Holm Tiffe Message-Id: <199808030704.JAA00678@magnet.geophysik.tu-freiberg.de> Subject: Re: No More CTM Deltas on ftp.freebsd.org ? In-Reply-To: <24015.901903367@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 31, 98 09:42:47 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 3 Aug 1998 09:04:10 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG Reply-To: freebsd@magnet.geophysik.tu-freiberg.de X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [..] > > > I think we shouldn't do such things, the FreeBSD CTM service > > has moved from on site to another several times, now this is > > enough. > > I think you're missing something fairly fundamental about free > software projects here - this happens, especially with CTM, and > there's no sense in saying "we shouldn't do such things" if such > things are happening whether we like it or not. Such things *must* not happen again and again! Since rzbsdi01.uni-trier.de (ctm.freebsd.org) has all the actual deltas, I can't understand why such things will happen. ftp.freebsd.org is our biggest advertisement, an our home too. > Are you volunteering > to take over CTM generation? Give me a disk, and I will do it. Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 00:26:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10871 for freebsd-current-outgoing; Mon, 3 Aug 1998 00:26:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10866 for ; Mon, 3 Aug 1998 00:26:12 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA16337; Mon, 3 Aug 1998 17:26:02 +1000 Date: Mon, 3 Aug 1998 17:26:02 +1000 From: Bruce Evans Message-Id: <199808030726.RAA16337@godzilla.zeta.org.au> To: current@FreeBSD.ORG, rock@cs.uni-sb.de Subject: Re: IO performance (UFS read clustering), bad ZIP drive performance Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I get unacceptable performance from my SCSI ZIP drive (compared to other >operating systems). While UFS writing is OK (up to the capabilities of the >drive: 600-1000 kB/s), everything else (UFS read, MSDOSFS r/w, mtools) >is extremely slow (down to 80 kB/s). ufs clustered reads have been broken (except on wd drives) since rev.1.18 (1998/01/24) of ufs_bmap.c. SCSI ZIPs have a huge command overhead (20 msec here on an ncr 53c810) and don't seem to support tags, so performance without clustering is poor. Fix: diff -c2 ufs_bmap.c~ ufs_bmap.c *** ufs_bmap.c~ Mon Jul 6 14:07:01 1998 --- ufs_bmap.c Mon Aug 3 16:08:26 1998 *************** *** 164,168 **** } ! if (maxrun == 0) { vp->v_maxio = DFLTPHYS; maxrun = DFLTPHYS / blksize; --- 164,168 ---- } ! if (maxrun <= 0) { vp->v_maxio = DFLTPHYS; maxrun = DFLTPHYS / blksize; Performance is poor for other normal disk file systems because clustering is only implemented for ufs (including ffs and ext2fs). Performance is poor for specfs since it uses a too-small block size and doesn't implement clustering. Since ufs normally uses clustered reads instead of plain read-ahead, even read-ahead has been broken. This is probably unimportant on modern drives, since the drive does the read-ahead. The breakage may even be an optimization - O/S read-ahead takes more CPU and may confuse the drive. Similarly for O/S read clustering except on drives with a large command overhead - it takes even more CPU and is even more likely to confuse the drive. This is probably why the breakage wasn't noticed before. >Why does the (now simulated?) block device divide I/O into chunks of only 2k? It has to use a fixed block size for various reasons. The size seems to be 2K for historical reasons. 2K was a lot of memory 20 years ago. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 02:22:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24856 for freebsd-current-outgoing; Mon, 3 Aug 1998 02:22:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24723; Mon, 3 Aug 1998 02:21:52 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id LAA14419; Mon, 3 Aug 1998 11:21:07 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id KAA20549; Mon, 3 Aug 1998 10:45:49 +0200 (MET DST) Message-ID: <19980803104548.08864@uriah.heep.sax.de> Date: Mon, 3 Aug 1998 10:45:48 +0200 From: J Wunsch To: The Hermit Hacker Cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Odd problems with -current... Reply-To: Joerg Wunsch References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from The Hermit Hacker on Sun, Aug 02, 1998 at 11:17:33PM -0400 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As The Hermit Hacker wrote: > I just put in a 2gig Seagate SCSI drive on my system, to replace a > 2gig IDE drive, and after running for awhile, it *seems* that the drive is > powering down, cause when I try to access something on that drive after > leaving for a period of time, you can hear it power back up again. I have been observing this for drives where the SCSI chain had term power problems. ISTR that it's been that more than one device was driving term power to the bus, and they apparently had some slightly conflicting idea about the actual term power level or such. So to be sure, it's IMHO always the sanest way to just have the host adapter driving term power, and have all drives leaving the term power line alone. This is unfortunately not the shipping state for most disk drives (i. e., they _do_ feed term power by default). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 04:36:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10365 for freebsd-current-outgoing; Mon, 3 Aug 1998 04:36:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10359 for ; Mon, 3 Aug 1998 04:36:37 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id NAA26131 for ; Mon, 3 Aug 1998 13:41:07 +0200 (CEST) (envelope-from regnauld@deepo.prosa.dk) X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id NAA00469 for ; Mon, 3 Aug 1998 13:41:47 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id NAA04050; Mon, 3 Aug 1998 13:39:16 +0200 (CEST) Message-ID: <19980803133915.52291@deepo.prosa.dk> Date: Mon, 3 Aug 1998 13:39:15 +0200 From: Philippe Regnauld To: freebsd-current@FreeBSD.ORG Subject: Ethernet interface names Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.88e X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a question+comment: Would it be very difficult to implement abstract naming on ethernet devices, à la Linux ? For example: eth0, eth1 instead of ed0, le1 I know there are potential problems with this (i.e.: user confusion, especially when building fw rules), but they already exist with multiple interfaces of the same type (ed0, ed1, ed2)... The advantage would be that you could pull out a dead card, plug a new (not necessarily of the same model), and there woudln't be any need to edit rc.conf, rc.firewall, etc... (Not that this had bothered me in any way). Also, what are the arguments in favor of _not_ doing this ? -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 04:53:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12772 for freebsd-current-outgoing; Mon, 3 Aug 1998 04:53:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12763 for ; Mon, 3 Aug 1998 04:53:33 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id HAA04994; Mon, 3 Aug 1998 07:53:16 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Philippe Regnauld cc: freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Ethernet interface names In-reply-to: Your message of "Mon, 03 Aug 1998 13:39:15 +0200." <19980803133915.52291@deepo.prosa.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Mon, 03 Aug 1998 07:53:16 -0400 Message-ID: <4990.902145196@gjp.erols.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id EAA12767 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Philippe Regnauld wrote in message ID <19980803133915.52291@deepo.prosa.dk>: > The advantage would be that you could pull out a dead card, plug > a new (not necessarily of the same model), and there woudln't > be any need to edit rc.conf, rc.firewall, etc... Thats assuming that the card is of the same bus type. If you replace an ISA card with a PCI card, you will probably end up with a different probe order, and hence the exact problems you highlight above. If you could do device numbering persistance like solaris does, so that devices don't change numbers over a reboot (just a reboot -r), then I think the `eth' scheme may work. I think the biggest thing stopping us doing it is POLA.... Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 05:56:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20220 for freebsd-current-outgoing; Mon, 3 Aug 1998 05:56:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA20187; Mon, 3 Aug 1998 05:56:46 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.5] (user5.dataplex.net [208.2.87.5]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id HAA17601; Mon, 3 Aug 1998 07:56:35 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <4990.902145196@gjp.erols.com> References: Your message of "Mon, 03 Aug 1998 13:39:15 +0200." <19980803133915.52291@deepo.prosa.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 3 Aug 1998 07:56:05 -0500 To: "Gary Palmer" From: Richard Wackerbarth Subject: Re: Ethernet interface names Cc: freebsd-current@FreeBSD.ORG, regnauld@deepo.prosa.dk Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Philippe Regnauld wrote in message ID ><19980803133915.52291@deepo.prosa.dk>: >> The advantage would be that you could pull out a dead card, plug >> a new (not necessarily of the same model), and there woudln't >> be any need to edit rc.conf, rc.firewall, etc... > >Thats assuming that the card is of the same bus type. If you replace an ISA >card with a PCI card, you will probably end up with a different probe order, Probe order creates a real problem. I can uniquely identify the interfaces by ethernet MAC. I still have to make assumptions about which "new" device is replacing which "old" one. If two change at the same time ... (Anyone got a paddle?) >and hence the exact problems you highlight above. If you could do device >numbering persistance like solaris does, so that devices don't change numbers >over a reboot (just a reboot -r), then I think the `eth' scheme may work. Persistance can be accomplished by using a database (implemented in shell variables) that links {kernel device id (ed0) <==> ethernet MAC} to get around the probe ordering and {ethernet MAC <==> logical interface (eth7)} Then you can write the "rules" using the logical interface. However, this doesn't solve the "replaced hardware" problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 06:23:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23825 for freebsd-current-outgoing; Mon, 3 Aug 1998 06:23:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA23807 for ; Mon, 3 Aug 1998 06:23:11 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA11385; Mon, 3 Aug 1998 22:23:03 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id WAA19278; Mon, 3 Aug 1998 22:32:20 +0900 (JST) Message-Id: <199808031332.WAA19278@zodiac.mech.utsunomiya-u.ac.jp> To: freebsd-current@FreeBSD.ORG Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: screen flicker in 3.0-CURRENT Date: Mon, 03 Aug 1998 22:32:19 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would be grateful if anybody who are having the following problem would apply the attached patch to /sys/i386/isa/syscons.c and report the result to me. There have been reports that the screen flicker is so bad when the mouse pointer is moved in 3.0-CURRENT and 2.2.7. 2.2.6 saw less of the problem. It has been observed that the problem is most apparent: a) in notebook computers, b) and/or in the systems with a C&T video chip. A possible workaround is to eliminate some I/O access to the chip. But, as I am not sure if this is OK with other VGA chip sets, we shall use a new configuration option SC_BAD_FLICKER. Define this option in the kernel configuration file to remove outb()/outw() calls in question. Thank you for your cooperation. Kazu yokota@freebsd.org --- syscons.c.orig Sun Aug 2 16:30:51 1998 +++ syscons.c Mon Aug 3 18:01:35 1998 @@ -4734,18 +4734,26 @@ outb(ATC, 0x20); /* enable palette */ #if SLOW_VGA +#ifndef SC_BAD_FLICKER outb(TSIDX, 0x00); outb(TSREG, 0x01); +#endif outb(TSIDX, 0x02); outb(TSREG, 0x04); outb(TSIDX, 0x04); outb(TSREG, 0x07); +#ifndef SC_BAD_FLICKER outb(TSIDX, 0x00); outb(TSREG, 0x03); +#endif outb(GDCIDX, 0x04); outb(GDCREG, 0x02); outb(GDCIDX, 0x05); outb(GDCREG, 0x00); outb(GDCIDX, 0x06); outb(GDCREG, 0x04); #else +#ifndef SC_BAD_FLICKER outw(TSIDX, 0x0100); +#endif outw(TSIDX, 0x0402); outw(TSIDX, 0x0704); +#ifndef SC_BAD_FLICKER outw(TSIDX, 0x0300); +#endif outw(GDCIDX, 0x0204); outw(GDCIDX, 0x0005); outw(GDCIDX, 0x0406); /* addr = a0000, 64kb */ @@ -4766,10 +4774,14 @@ outb(ATC, 0x20); /* enable palette */ #if SLOW_VGA +#ifndef SC_BAD_FLICKER outb(TSIDX, 0x00); outb(TSREG, 0x01); +#endif outb(TSIDX, 0x02); outb(TSREG, buf[0]); outb(TSIDX, 0x04); outb(TSREG, buf[1]); +#ifndef SC_BAD_FLICKER outb(TSIDX, 0x00); outb(TSREG, 0x03); +#endif outb(GDCIDX, 0x04); outb(GDCREG, buf[2]); outb(GDCIDX, 0x05); outb(GDCREG, buf[3]); if (crtc_addr == MONO_BASE) { @@ -4778,10 +4790,14 @@ outb(GDCIDX, 0x06); outb(GDCREG,(buf[4] & 0x03) | 0x0c); } #else +#ifndef SC_BAD_FLICKER outw(TSIDX, 0x0100); +#endif outw(TSIDX, 0x0002 | (buf[0] << 8)); outw(TSIDX, 0x0004 | (buf[1] << 8)); +#ifndef SC_BAD_FLICKER outw(TSIDX, 0x0300); +#endif outw(GDCIDX, 0x0004 | (buf[2] << 8)); outw(GDCIDX, 0x0005 | (buf[3] << 8)); if (crtc_addr == MONO_BASE) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 07:25:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01278 for freebsd-current-outgoing; Mon, 3 Aug 1998 07:25:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01259 for ; Mon, 3 Aug 1998 07:25:20 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id QAA06124 for ; Mon, 3 Aug 1998 16:24:59 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.1/8.9.1) with ESMTP id QAA01245 for ; Mon, 3 Aug 1998 16:24:59 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id QAA16531 for ; Mon, 3 Aug 1998 16:25:00 +0200 (CEST) Received: from server.us.tld(192.168.16.33) via SMTP by curry.mchp.siemens.de, id smtpdw16527; Mon Aug 3 16:24:57 1998 Received: (from daemon@localhost) by server.us.tld (8.8.8/8.8.8) id QAA21732 for ; Mon, 3 Aug 1998 16:24:57 +0200 (CEST) (envelope-from andre@bali.us.tld) Received: from bali.us.tld(192.168.21.100) via SMTP by server.us.tld, id smtpdf21624; Mon Aug 3 16:24:54 1998 Received: (from andre@localhost) by bali.us.tld (8.8.8/8.8.8) id QAA14695; Mon, 3 Aug 1998 16:24:54 +0200 (CEST) (envelope-from andre) From: Andre Albsmeier Message-Id: <199808031424.QAA14695@bali.us.tld> Subject: Re: screen flicker in 3.0-CURRENT In-Reply-To: <199808031332.WAA19278@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Aug 3, 98 10:32:19 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Mon, 3 Aug 1998 16:24:54 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I would be grateful if anybody who are having the following problem > would apply the attached patch to /sys/i386/isa/syscons.c and report > the result to me. > > There have been reports that the screen flicker is so bad when the > mouse pointer is moved in 3.0-CURRENT and 2.2.7. 2.2.6 saw less of > the problem. It has been observed that the problem is most apparent: > > a) in notebook computers, > b) and/or in the systems with a C&T video chip. > > A possible workaround is to eliminate some I/O access to the chip. > But, as I am not sure if this is OK with other VGA chip sets, we shall > use a new configuration option SC_BAD_FLICKER. Define this option in > the kernel configuration file to remove outb()/outw() calls in question. Hmm, I had this problem quite a while on a -STABLE system since 2.2.5 However, it went away after attaching a different monitor to it. The first monitor is definately OK, I have 4 of them and they all behaved equal. The video chip is a et4000 on a low cost ISA card. The symptoms were that when the mouse was used (moused and mousepointer enabled) the screen turned blank and reappeared after moving the mouse more. -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 08:18:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07788 for freebsd-current-outgoing; Mon, 3 Aug 1998 08:18:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07780 for ; Mon, 3 Aug 1998 08:18:35 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id LAA02183 for ; Mon, 3 Aug 1998 11:18:55 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Mon, 3 Aug 1998 11:18:55 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: current@FreeBSD.ORG Subject: can someone build me a custom boot floppy please? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG if anyone does a "make release" soon, could they include the "xl0" ethernet driver please in the boot kernel (and send me a URL to it)? a few people at work would like to try FreeBSD but we only have those 905b cards here. i'd really appreciate it, i kinda mucked around with building my own boot floppy but it's kinda complex for the time i have. plus i'm getting compiling errors on MFS_ROOT so i'm kinda confused. Is there a howto on this? thank you, Alfred Perlstein -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] There are operating systems, and then there's BSD. http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 09:08:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15205 for freebsd-current-outgoing; Mon, 3 Aug 1998 09:08:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fang.cs.sunyit.edu (fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15196 for ; Mon, 3 Aug 1998 09:08:47 -0700 (PDT) (envelope-from meyerd1@fang.cs.sunyit.edu) Received: from fang.cs.sunyit.edu (fang.cs.sunyit.edu [192.52.220.66]) by fang.cs.sunyit.edu (8.8.8/8.8.8) with SMTP id MAA14697 for ; Mon, 3 Aug 1998 12:07:36 -0400 (EDT) (envelope-from meyerd1@fang.cs.sunyit.edu) Date: Mon, 3 Aug 1998 12:07:36 -0400 (EDT) From: Daniel Aaron Meyer To: current@FreeBSD.ORG Subject: page faults and swapping Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ive been experiencing problems with my system crashing under heavy swapping (ex. make world). This started happening after a make world I did a few weeks ago. Not having heard from anyone having similar problems, Ive been trying to rule out problems on my side. Now Im finally baffled. I cvsuped and booted a 5/20 kernel.GENERIC which suprisingly enough aloud me to do a complete rebuild without any problems. Up until then, I was unable to make world without a crash. I tried a make world with the new kernel (8/2/98) and retrieve the following: pickle# gdb -k kernel.0 vmcore.0 GDB is free software and you are welcome to 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. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc...(no debugging symbols found)... IdlePTD 2392064 initial pcb at 22042c panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xf0132d9d stack pointer = 0x10:0xf4264cf0 frame pointer = 0x10:0xf4264cf4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 16441 (sh) interrupt mask = trap number = 12 panic: page fault syncing disks... 73 73 69 58 32 12 done dumping to dev 20001, offset 68812 dump 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 4 1 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 0xf01150b7 in boot () (kgdb) bt #0 0xf01150b7 in boot () #1 0xf0115386 in panic () #2 0xf01d6e4d in trap_fatal () #3 0xf01d68e0 in trap_pfault () #4 0xf01d653f in trap () #5 0xf0132d9d in cache_zap () #6 0xf01331ae in cache_enter () #7 0xf01b62dd in ufs_lookup () #8 0xf01bb071 in ufs_vnoperate () #9 0xf0133510 in vfs_cache_lookup () #10 0xf01bb071 in ufs_vnoperate () #11 0xf01352cd in lookup () #12 0xf0134d8c in namei () #13 0xf013a6d4 in stat () #14 0xf01d707f in syscall () #15 0x3cad5 in ?? () #16 0x51db in ?? () #17 0x4821 in ?? () #18 0x479b in ?? () #19 0x46a6 in ?? () #20 0xb5cf in ?? () #21 0xb4df in ?? () #22 0x107e in ?? () (kgdb) quit Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #6: Sun Aug 2 18:03:43 EDT 1998 meyerd1@pickle.local.sunyit.edu:/usr/src/sys/compile/PICKLE Timecounter "i8254" frequency 1193182 Hz cost 2114 ns Timecounter "TSC" frequency 233222363 Hz cost 98 ns CPU: Pentium/P55C (233.22-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bf real memory = 67108864 (65536K bytes) avail memory = 61636608 (60192K bytes) Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 vga0: rev 0x02 int a irq 11 on pci0.12.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x2a0-0x2bf irq 3 maddr 0xd0000 msize 8192 on isa ed0: address 00:00:c0:68:60:d4, type SMC8416T (16 bit) sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wd0: 3020MB (6185088 sectors), 6136 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, ovlap, $ wcd0: 5512Kb/sec, 256Kb cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: sbmidi0 at 0x330 on isa snd0: opl0 at 0x388 on isa snd0: Intel Pentium F00F detected, installing workaround changing root device to wd0s1a WARNING: / was not properly dismounted. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 09:18:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17981 for freebsd-current-outgoing; Mon, 3 Aug 1998 09:18:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from horst.bfd.com (horst.bfd.com [12.9.219.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17973 for ; Mon, 3 Aug 1998 09:18:31 -0700 (PDT) (envelope-from ejs@bfd.com) Received: from HARLIE.bfd.com (bastion.bfd.com [12.9.219.14]) by horst.bfd.com (8.9.1/8.9.1) with SMTP id JAA00363; Mon, 3 Aug 1998 09:16:59 -0700 (PDT) Date: Mon, 3 Aug 1998 09:16:59 -0700 (PDT) From: "Eric J. Schwertfeger" To: Terry Lambert cc: Peter Wemm , osa@serv.etrust.ru, current@FreeBSD.ORG Subject: Re: Sendmail-8.9.1 in -current & in 3.0-RELEASE??? In-Reply-To: <199808030638.XAA11787@usr01.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I see no conflict between the original UCB copyrighted code and the entire > > backage being under a more restricted "umbrella" license. Yes, it's > > unfortunate that there are extra restrictions, but that's life. Considering > > how sendmail development is now being funded, we came out of it pretty well > > I think. > > The Sleepycat license (the dbm code required by sendmail is under this > license) is insidious in that it is effectively GPL. Sendmail 8.9.1 has no problems using the FreeBSD db code, DB 2.0 is not required. I think the actual requirement is for something at least as new as 1.5, though they do talk about bugs in 1.5. In the future, DB < 2.00 compatibility may be phased out (not discussed, just being realistic) but it hasn't happened yet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 11:42:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14007 for freebsd-current-outgoing; Mon, 3 Aug 1998 11:42:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13999 for ; Mon, 3 Aug 1998 11:42:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA00340; Mon, 3 Aug 1998 11:40:45 -0700 (PDT) Message-Id: <199808031840.LAA00340@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Parag Patel cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS diskless booting (NFS root/swap) broken in -current? In-reply-to: Your message of "Sun, 02 Aug 1998 23:27:08 PDT." <199808030627.XAA01496@pinhead.parag.codegen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Aug 1998 11:40:44 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I haven't been able to boot my 486 test machine diskless with the > latest -current. It used to boot (using nb8390.com under DOS) and run > fine when my server was -stable, but I unfortunately haven't tried it > in weeks and didn't keep a copy of the working sources to compare. Do you have 'options NFS_ROOT' in your kernel config? > Forcing it to boot NFS by adding BOOTP_NFSROOT in the config file > causes this crash: > > panic: nfs_mountroot: socreate(0000): 43 Hmm, looks like you do. > It's correct in that the protocol is not supported, but it shouldn't be > using 0 for the protocol family. It doesn't matter if I netboot the > kernel, or copy it to the disk and then boot it. Did something change > such that I need some new magic incantation in the config file now? Apart from the above, no. > (The BOOTP_NFSV3 option didn't make any difference.) > > When I boot (root and swap) off of the local disk, it is quite happy > NFS-mounting my server, so I suspect some kernel change in the past few > weeks broke diskless. I didn't notice anything obvious in the CVS logs > for the few files I looked at, but I'm probably not looking at the > right place. It might help to check the nfs_diskless_valid flag, and maybe dump the nfs_diskless structure just to see whether it's coming in correctly. The family is set by the bootstrap, so if it's not copied, it's not going to work. Bruce's changes to the way the root filesystem is found *may* have something to do with this. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 12:06:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17613 for freebsd-current-outgoing; Mon, 3 Aug 1998 12:06:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17575 for ; Mon, 3 Aug 1998 12:06:13 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA18491; Mon, 3 Aug 1998 12:05:35 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd018466; Mon Aug 3 12:05:33 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id MAA00483; Mon, 3 Aug 1998 12:05:26 -0700 (MST) From: Terry Lambert Message-Id: <199808031905.MAA00483@usr07.primenet.com> Subject: Re: Sendmail-8.9.1 in -current & in 3.0-RELEASE??? To: ejs@bfd.com (Eric J. Schwertfeger) Date: Mon, 3 Aug 1998 19:05:26 +0000 (GMT) Cc: tlambert@primenet.com, peter@netplex.com.au, osa@serv.etrust.ru, current@FreeBSD.ORG In-Reply-To: from "Eric J. Schwertfeger" at Aug 3, 98 09:16:59 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The Sleepycat license (the dbm code required by sendmail is under this > > license) is insidious in that it is effectively GPL. > > Sendmail 8.9.1 has no problems using the FreeBSD db code, DB 2.0 is not > required. I think the actual requirement is for something at least as new > as 1.5, though they do talk about bugs in 1.5. In the future, DB < 2.00 > compatibility may be phased out (not discussed, just being realistic) but > it hasn't happened yet. Thanks for the info. It looks like there is no problem now, but that there will be, in the future. I defer my question until then. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 12:15:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19742 for freebsd-current-outgoing; Mon, 3 Aug 1998 12:15:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-asfm08--184.sirius.net [205.134.241.184]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19704 for ; Mon, 3 Aug 1998 12:15:16 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.8.8/8.8.8) with ESMTP id MAA20516; Mon, 3 Aug 1998 12:15:01 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199808031915.MAA20516@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS diskless booting (NFS root/swap) broken in -current? In-reply-to: Your message of "Mon, 03 Aug 1998 11:40:44 PDT." <199808031840.LAA00340@dingo.cdrom.com> X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Aug 1998 12:15:01 -0700 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Do you have 'options NFS_ROOT' in your kernel config? Yup, sure do. >It might help to check the nfs_diskless_valid flag, and maybe dump the >nfs_diskless structure just to see whether it's coming in correctly. >The family is set by the bootstrap, so if it's not copied, it's not >going to work. It's set to 0 (not valid). I'm dumping various structs out to see what's going on. So far, I've determined that netboot has initialized bootinfo.bi_nfs_diskless to something but accessing that pointer directly in cpu_rootconf() causes a crash, probably 'cause things have already been mapped and that addr is inaccessible(?). The pointer is 0x94320, but I don't know if it's OK yet. The rest of bootinfo looks OK (correct version at least). nfs_diskless.swap_nblks is zero where it should be 0x8000, so something's definitely wrong. I'm printing out some more fields in nfs_diskless to see if anything else is wrong there. netboot is happy with the freebsd.x.x.x.x file contents, displays the appropriate messages, and finds root and swap just fine. >Bruce's changes to the way the root filesystem is found *may* have >something to do with this. Perhaps - whatever's happening appears to be happening before this point, but I am continuing to dig into it... -- Parag To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 12:28:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22471 for freebsd-current-outgoing; Mon, 3 Aug 1998 12:28:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22384 for ; Mon, 3 Aug 1998 12:28:21 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA26500; Mon, 3 Aug 1998 12:27:54 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd026475; Mon Aug 3 12:27:52 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id MAA01657; Mon, 3 Aug 1998 12:27:49 -0700 (MST) From: Terry Lambert Message-Id: <199808031927.MAA01657@usr07.primenet.com> Subject: Re: IO performance (UFS read clustering), bad ZIP drive performance To: bde@zeta.org.au (Bruce Evans) Date: Mon, 3 Aug 1998 19:27:49 +0000 (GMT) Cc: current@FreeBSD.ORG, rock@cs.uni-sb.de In-Reply-To: <199808030726.RAA16337@godzilla.zeta.org.au> from "Bruce Evans" at Aug 3, 98 05:26:02 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I get unacceptable performance from my SCSI ZIP drive (compared to other > >operating systems). While UFS writing is OK (up to the capabilities of the > >drive: 600-1000 kB/s), everything else (UFS read, MSDOSFS r/w, mtools) > >is extremely slow (down to 80 kB/s). > > ufs clustered reads have been broken (except on wd drives) since rev.1.18 > (1998/01/24) of ufs_bmap.c. SCSI ZIPs have a huge command overhead > (20 msec here on an ncr 53c810) and don't seem to support tags, so > performance without clustering is poor. > > Fix: Is there a particula reason you are posting this to -current instead of to the CVS tree? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 12:31:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23105 for freebsd-current-outgoing; Mon, 3 Aug 1998 12:31:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23083 for ; Mon, 3 Aug 1998 12:30:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA00572; Mon, 3 Aug 1998 12:28:49 -0700 (PDT) Message-Id: <199808031928.MAA00572@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Parag Patel cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: NFS diskless booting (NFS root/swap) broken in -current? In-reply-to: Your message of "Mon, 03 Aug 1998 12:15:01 PDT." <199808031915.MAA20516@pinhead.parag.codegen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Aug 1998 12:28:48 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >Do you have 'options NFS_ROOT' in your kernel config? > > Yup, sure do. > > > >It might help to check the nfs_diskless_valid flag, and maybe dump the > >nfs_diskless structure just to see whether it's coming in correctly. > >The family is set by the bootstrap, so if it's not copied, it's not > >going to work. > > It's set to 0 (not valid). If it's set to zero, then locore.c has not copied the structure in from low memory. You might want to be looking at this fragment there: #ifdef NFS #ifndef BOOTP_NFSV3 /* * If we have a nfs_diskless structure copy it in */ movl BI_NFS_DISKLESS(%ebx),%esi cmpl $0,%esi je olddiskboot movl $R(_nfs_diskless),%edi movl $NFSDISKLESS_SIZE,%ecx cld rep movsb movl $R(_nfs_diskless_valid),%edi movl $1,(%edi) #endif #endif The nfs_diskless_valid flag is also fiddled in sys/nfs/bootp_subr.c; a quick look at the code leaves me a little seasick, but it's not clear at all that the nfs_diskless structure is properly populated in that case. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 12:34:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23806 for freebsd-current-outgoing; Mon, 3 Aug 1998 12:34:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23783 for ; Mon, 3 Aug 1998 12:34:15 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id FAA23134; Tue, 4 Aug 1998 05:33:44 +1000 Date: Tue, 4 Aug 1998 05:33:44 +1000 From: Bruce Evans Message-Id: <199808031933.FAA23134@godzilla.zeta.org.au> To: bde@zeta.org.au, tlambert@primenet.com Subject: Re: IO performance (UFS read clustering), bad ZIP drive performance Cc: current@FreeBSD.ORG, rock@cs.uni-sb.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Is there a particula reason you are posting this to -current instead of >to the CVS tree? Someone asked here, and I already have too many things to commit. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 12:50:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27971 for freebsd-current-outgoing; Mon, 3 Aug 1998 12:50:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27949 for ; Mon, 3 Aug 1998 12:50:35 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA00737; Mon, 3 Aug 1998 12:48:58 -0700 (PDT) Message-Id: <199808031948.MAA00737@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Bruce Evans cc: tlambert@primenet.com, current@FreeBSD.ORG, rock@cs.uni-sb.de Subject: Re: IO performance (UFS read clustering), bad ZIP drive performance In-reply-to: Your message of "Tue, 04 Aug 1998 05:33:44 +1000." <199808031933.FAA23134@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Aug 1998 12:48:58 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Is there a particula reason you are posting this to -current instead of > >to the CVS tree? > > Someone asked here, and I already have too many things to commit. Should it be committed? You could have included that information in-band in the original posting, and I would have done so instead of filing it in my "to be worried about" folder. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 13:45:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05309 for freebsd-current-outgoing; Mon, 3 Aug 1998 13:45:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05252 for ; Mon, 3 Aug 1998 13:44:55 -0700 (PDT) (envelope-from stb@hanse.de) Received: from daemon.Hanse.DE (daemon.Hanse.DE [193.174.9.17]) by rrz.Hanse.DE (8.8.8/8.8.8) with ESMTP id WAA16270; Mon, 3 Aug 1998 22:38:05 +0200 (CEST) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id WAA16538; Mon, 3 Aug 1998 22:44:39 +0200 (CEST) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id WAA16850; Mon, 3 Aug 1998 22:42:12 +0200 (CEST) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Mon, 3 Aug 1998 22:42:11 +0200 (CEST) From: Stefan Bethke To: =?ISO-8859-1?Q?Dag-Erling_Coidan_Sm=F8rgrav?= cc: Jonah Kuo , current@FreeBSD.ORG Subject: Re: buildworld failures on same problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id NAA05278 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30 Jul 1998, Dag-Erling Coidan Smørgrav wrote: > *sigh* > > When will people learn to read the bloody FAQ and search the bloody > archives before asking the same bloody question as umpteen zillion > others before them? > > # cd /usr/src ; make -m /usr/src/share/mk world Being one of the persons having it learned the wrong way (thanks anyway!), I think it might be helpful to put a comment into the first lines of src/Makefile. At least it would remind myself, as I regularly check if anything significant has changed, and simply because I seam to be unable to remember the option's names, anyway... Cheers, Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 13:54:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06854 for freebsd-current-outgoing; Mon, 3 Aug 1998 13:54:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06732 for ; Mon, 3 Aug 1998 13:53:59 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id NAA27101; Mon, 3 Aug 1998 13:53:34 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd027012; Mon Aug 3 13:53:28 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id NAA27479; Mon, 3 Aug 1998 13:53:10 -0700 (MST) From: Terry Lambert Message-Id: <199808032053.NAA27479@usr04.primenet.com> Subject: Re: IO performance (UFS read clustering), bad ZIP drive performance To: bde@zeta.org.au (Bruce Evans) Date: Mon, 3 Aug 1998 20:53:10 +0000 (GMT) Cc: bde@zeta.org.au, tlambert@primenet.com, current@FreeBSD.ORG, rock@cs.uni-sb.de In-Reply-To: <199808031933.FAA23134@godzilla.zeta.org.au> from "Bruce Evans" at Aug 4, 98 05:33:44 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Is there a particula reason you are posting this to -current instead of > >to the CVS tree? > > Someone asked here, and I already have too many things to commit. If it's harder for a core team member to commit known good code than it is for them to post the code to the -current list, then there is a problem with the process. 8-(. It looks like source code control is moving out of CVS and into the -current list archives. This can only be a Bad Thing(tm) Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 14:24:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12810 for freebsd-current-outgoing; Mon, 3 Aug 1998 14:24:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-asfm08--165.sirius.net [205.134.241.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12805 for ; Mon, 3 Aug 1998 14:24:21 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.8.8/8.8.8) with ESMTP id OAA21264; Mon, 3 Aug 1998 14:24:07 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199808032124.OAA21264@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS diskless booting (NFS root/swap) broken in -current? In-reply-to: Your message of "Mon, 03 Aug 1998 12:28:48 PDT." <199808031928.MAA00572@dingo.cdrom.com> X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Aug 1998 14:24:07 -0700 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found the problem. The bug is in locore.s. The following patch fixes NFS booting. The change to use the newer opt_nfsroot.h instead of opt_nfs.h was good, but the #ifdef for NFS also needed to be changed to NFS_ROOT. That was it - locore just wasn't copying the NFS info from its passed-in args into the kernel global nfs_diskless, so there was no data for the kernel to use to boot. -- Parag Patel # cvs diff -c locore.s Index: locore.s =================================================================== RCS file: /src/freebsd/src/sys/i386/i386/locore.s,v retrieving revision 1.111 diff -c -r1.111 locore.s *** locore.s 1998/07/27 16:45:01 1.111 --- locore.s 1998/08/03 21:18:06 *************** *** 569,575 **** rep movsb ! #ifdef NFS #ifndef BOOTP_NFSV3 /* * If we have a nfs_diskless structure copy it in --- 569,575 ---- rep movsb ! #ifdef NFS_ROOT #ifndef BOOTP_NFSV3 /* * If we have a nfs_diskless structure copy it in To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 14:30:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14116 for freebsd-current-outgoing; Mon, 3 Aug 1998 14:30:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA14087; Mon, 3 Aug 1998 14:30:29 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA23824 (5.67b/IDA-1.5); Mon, 3 Aug 1998 22:49:16 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id WAA02844; Mon, 3 Aug 1998 22:01:27 +0200 (CEST) From: Wilko Bulte Message-Id: <199808032001.WAA02844@yedi.iaf.nl> Subject: Re: Odd problems with -current... In-Reply-To: <19980803104548.08864@uriah.heep.sax.de> from J Wunsch at "Aug 3, 98 10:45:48 am" To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 3 Aug 1998 22:01:27 +0200 (CEST) Cc: scrappy@hub.org, scsi@FreeBSD.ORG, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As J Wunsch wrote... > As The Hermit Hacker wrote: > > > I just put in a 2gig Seagate SCSI drive on my system, to replace a > > 2gig IDE drive, and after running for awhile, it *seems* that the drive is > > powering down, cause when I try to access something on that drive after > > leaving for a period of time, you can hear it power back up again. > > I have been observing this for drives where the SCSI chain had term > power problems. ISTR that it's been that more than one device was > driving term power to the bus, and they apparently had some slightly > conflicting idea about the actual term power level or such. So to be > sure, it's IMHO always the sanest way to just have the host adapter > driving term power, and have all drives leaving the term power line Yep. This also has the added advantage that shorting TERMPWR to ground does not smoke the cables. Each device is normally capable of sourcing > 1 A of current so it adds up.. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW: http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 14:32:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14477 for freebsd-current-outgoing; Mon, 3 Aug 1998 14:32:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14409 for ; Mon, 3 Aug 1998 14:32:40 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA01171; Mon, 3 Aug 1998 14:31:16 -0700 (PDT) Message-Id: <199808032131.OAA01171@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Parag Patel cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS diskless booting (NFS root/swap) broken in -current? In-reply-to: Your message of "Mon, 03 Aug 1998 14:24:07 PDT." <199808032124.OAA21264@pinhead.parag.codegen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Aug 1998 14:31:16 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I found the problem. The bug is in locore.s. The following patch fixes NFS booting. The change to use the newer opt_nfsroot.h instead of opt_nfs.h was good, but the #ifdef for NFS also needed to be changed to NFS_ROOT. > > That was it - locore just wasn't copying the NFS info from its passed-in args into the kernel global nfs_diskless, so there was no data for the kernel to use to boot. Thanks for tracking this down; I've just committed your fix. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 17:26:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04814 for freebsd-current-outgoing; Mon, 3 Aug 1998 17:26:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA04809; Mon, 3 Aug 1998 17:26:27 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z3Uvh-0006OW-00; Mon, 3 Aug 1998 18:26:17 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id SAA06411; Mon, 3 Aug 1998 18:16:35 -0600 (MDT) Message-Id: <199808040016.SAA06411@harmony.village.org> To: freebsd-ctm@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: CTM checksum errors? Date: Mon, 03 Aug 1998 18:16:35 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, am I the only one to get boatloads of CVS checksum errors when trying to apply cvs-cur 4493 and later? The number of such errors leads me to believe that somebody "oopsed" and is now generating the CTM diffs from a tree that is updated by cvsup with the new "ignore whitespace" option turned on, which is FUBARing the checksums for the CTM generation. Other than CTM being an orphan right now, comments? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 18:44:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12227 for freebsd-current-outgoing; Mon, 3 Aug 1998 18:44:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12222; Mon, 3 Aug 1998 18:44:56 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id UAA08699; Mon, 3 Aug 1998 20:42:29 -0400 (EDT) Date: Mon, 3 Aug 1998 20:42:28 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Warner Losh cc: freebsd-ctm@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: CTM checksum errors? In-Reply-To: <199808040016.SAA06411@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Aug 1998, Warner Losh wrote: > > Greetings, > am I the only one to get boatloads of CVS checksum errors when > trying to apply cvs-cur 4493 and later? The number of such errors > leads me to believe that somebody "oopsed" and is now generating the > CTM diffs from a tree that is updated by cvsup with the new "ignore > whitespace" option turned on, which is FUBARing the checksums for the > CTM generation. > > Other than CTM being an orphan right now, comments? I am not sure what a "CVS checksum error" is, but I'm up to 4522 now with ctm, and I haven't seen any error message at all. If you tell me what that error looks like, I'll see if I have it. I've been applying the deltas and updating my tree right along. BTW, ctm isn't really orphaned, Mark was kinda busy. Mark and I have both been watching ctm very closely, and there's been no interruption of service at all, just the missing deltas on wcarchive. Mail service hasn't missed a single one. I don't have that password, else I'd have fixed that one myself. There's a machine dedicated to making ctms, all right. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 18:49:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12595 for freebsd-current-outgoing; Mon, 3 Aug 1998 18:49:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA12586 for ; Mon, 3 Aug 1998 18:49:18 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z3WDs-0006Rg-00; Mon, 3 Aug 1998 19:49:08 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id TAA07359; Mon, 3 Aug 1998 19:49:58 -0600 (MDT) Message-Id: <199808040149.TAA07359@harmony.village.org> To: Chuck Robey Subject: Re: CTM checksum errors? Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 03 Aug 1998 20:42:28 EDT." References: Date: Mon, 03 Aug 1998 19:49:58 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Chuck Robey writes: : I am not sure what a "CVS checksum error" is, but I'm up to 4522 now : with ctm, and I haven't seen any error message at all. If you tell me : what that error looks like, I'll see if I have it. I've been applying : the deltas and updating my tree right along. Sounds like my tree got boogered at some point then. md5 checksum errors was what was being complained about.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 18:56:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13616 for freebsd-current-outgoing; Mon, 3 Aug 1998 18:56:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13604 for ; Mon, 3 Aug 1998 18:56:44 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id UAA08727; Mon, 3 Aug 1998 20:54:17 -0400 (EDT) Date: Mon, 3 Aug 1998 20:54:17 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Warner Losh cc: freebsd-current@FreeBSD.ORG Subject: Re: CTM checksum errors? In-Reply-To: <199808040149.TAA07359@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Aug 1998, Warner Losh wrote: > In message Chuck Robey writes: > : I am not sure what a "CVS checksum error" is, but I'm up to 4522 now > : with ctm, and I haven't seen any error message at all. If you tell me > : what that error looks like, I'll see if I have it. I've been applying > : the deltas and updating my tree right along. > > Sounds like my tree got boogered at some point then. md5 checksum > errors was what was being complained about.... If you mean errors reported by _ctm_, then you're right, your tree is "boogered" .... boogered, I like that. Maybe someone did you a "favor" and used cvsup on it? That would sure do it. > > Warner > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 19:27:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16265 for freebsd-current-outgoing; Mon, 3 Aug 1998 19:27:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA16258 for ; Mon, 3 Aug 1998 19:27:34 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z3Wou-0006T0-00; Mon, 3 Aug 1998 20:27:24 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id UAA00389; Mon, 3 Aug 1998 20:27:14 -0600 (MDT) Message-Id: <199808040227.UAA00389@harmony.village.org> To: Chuck Robey Subject: Re: CTM checksum errors? Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 03 Aug 1998 20:54:17 EDT." References: Date: Mon, 03 Aug 1998 20:27:14 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Chuck Robey writes: : Maybe someone did you a "favor" and used cvsup on it? That would sure : do it. That is not possible. I've been trying to get my CVS tree updated via CVSUP (well a copy of it) and can't get the socks option to work with it at all. :-(. One good thing about all of this, however. I think I may have found a way to get a reproducible crash with soft updates: ctm -b /part/with/soft/updates/CVS * where the current directory has ctm cvs-cur.1800A.gz through cvs-cur.4522.gz.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 21:05:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24520 for freebsd-current-outgoing; Mon, 3 Aug 1998 21:05:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24502; Mon, 3 Aug 1998 21:05:31 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id GAA04935; Tue, 4 Aug 1998 06:05:11 +0200 (SAT) From: John Hay Message-Id: <199808040405.GAA04935@zibbi.mikom.csir.co.za> Subject: Re: CTM checksum errors? In-Reply-To: <199808040016.SAA06411@harmony.village.org> from Warner Losh at "Aug 3, 98 06:16:35 pm" To: imp@village.org (Warner Losh) Date: Tue, 4 Aug 1998 06:05:10 +0200 (SAT) Cc: freebsd-ctm@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Greetings, > am I the only one to get boatloads of CVS checksum errors when > trying to apply cvs-cur 4493 and later? The number of such errors > leads me to believe that somebody "oopsed" and is now generating the > CTM diffs from a tree that is updated by cvsup with the new "ignore > whitespace" option turned on, which is FUBARing the checksums for the > CTM generation. Well I don't have any problems and I'm up to cvs-cur.4525 at the moment. > Other than CTM being an orphan right now, comments? I don't think it really is an orphan. I think Mark Murray is just still recovering from his overseas trip and that is probably why he haven't chipped in yet. At the moment I'm still getting the output of every ctm generation and there is no problems on that machine as far as I can see. What I think happened is that we lost the mailing lists again when hub died. I had to resubscribe to a lot of lists afterwards. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 3 21:05:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24563 for freebsd-current-outgoing; Mon, 3 Aug 1998 21:05:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24541; Mon, 3 Aug 1998 21:05:44 -0700 (PDT) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id XAA29490; Mon, 3 Aug 1998 23:05:27 -0500 (CDT) Received: (from bruce@localhost) by zuhause.mn.org (8.8.8/8.8.7) id XAA04003; Mon, 3 Aug 1998 23:01:54 -0500 (CDT) From: Bruce Albrecht Date: Mon, 3 Aug 1998 23:01:54 -0500 (CDT) To: The Hermit Hacker Cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Odd problems with -current... In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13766.34658.202254.310696@zuhause.zuhause.mn.org> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker writes: > I'm trying to debug a problem that I'm having on my home machine > that has me totally baffled, and am hoping someone here can "show me the > way"... > > I just put in a 2gig Seagate SCSI drive on my system, to replace a > 2gig IDE drive, and after running for awhile, it *seems* that the drive is > powering down, cause when I try to access something on that drive after > leaving for a period of time, you can hear it power back up again. Are you sure that it's not powering down because it's overheating? I've got a couple of Hawk drives that shut down until I added extra fans. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 00:47:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12853 for freebsd-current-outgoing; Tue, 4 Aug 1998 00:47:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12843; Tue, 4 Aug 1998 00:47:19 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id JAA00627; Tue, 4 Aug 1998 09:47:03 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Tue, 4 Aug 1998 09:47:02 +0200 (MET DST) Mime-Version: 1.0 To: hackers@FreeBSD.ORG, current@FreeBSD.ORG, wpaul@FreeBSD.ORG Subject: Etherlink XL driver Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 04 Aug 1998 09:47:02 +0200 Message-ID: Lines: 7 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id AAA12845 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Etherlink XL driver seems to be working fine. How about committing it to -current and removing the XL probe/attach code from the vx driver? DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 01:22:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16281 for freebsd-current-outgoing; Tue, 4 Aug 1998 01:22:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16275; Tue, 4 Aug 1998 01:22:51 -0700 (PDT) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (root@shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.8.8/8.8.8) with ESMTP id MAA12778; Tue, 4 Aug 1998 12:22:34 +0400 (MSD) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (tarkhil@minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.8/8.8.7) with ESMTP id MAA12251; Tue, 4 Aug 1998 12:22:54 +0400 (MSD) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199808040822.MAA12251@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG cc: hackers@FreeBSD.ORG Reply-To: tarkhil@asteroid.svib.ru Subject: What does it mean? X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Date: Tue, 04 Aug 1998 12:22:53 +0400 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Some time ago, squid on my FreeBSD asteroid.svib.ru 3.0-CURRENT FreeBSD 3.0-CURRENT #1: Tue Feb 24 12:34:41 MSK 1998 root@asteroid.svib.ru:/data/src/sys/compile/ASTEROID i386 box stopped responding. ps tells me that ps axlw | grep squid 0 12762 12654 1 -6 0 952 636 piperd S+ p0 0:00.01 grep squid 65534 328 316 0 -22 0 17392 10076 vmpfw D con- 12:35.05 squid -sY what does it mean? Who/whot/how deadlocked squid? It is in D state, and immunet even to kill -9 :-( Alex. -- Alexander B. Povolotsky [2:5020/145] [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru] [Urgent messages: 234-9696 ÁÂ.#35442 or tarkhil@pager.express.ru] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 02:26:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23216 for freebsd-current-outgoing; Tue, 4 Aug 1998 02:26:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23209 for ; Tue, 4 Aug 1998 02:26:39 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id LAA08373 for freebsd-current@FreeBSD.ORG; Tue, 4 Aug 1998 11:26:23 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id D80111516; Tue, 4 Aug 1998 11:07:01 +0200 (CEST) Message-ID: <19980804110701.A13697@keltia.freenix.fr> Date: Tue, 4 Aug 1998 11:07:01 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: CTM checksum errors? Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199808040149.TAA07359@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199808040149.TAA07359@harmony.village.org>; from Warner Losh on Mon, Aug 03, 1998 at 07:49:58PM -0600 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4518 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Warner Losh: > Sounds like my tree got boogered at some point then. md5 checksum > errors was what was being complained about.... I can confirm it is probably something on your side, I'm almost up to 4522 too (waiting for the last two chunks :-)). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #62: Mon Jul 27 20:47:08 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 02:26:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23254 for freebsd-current-outgoing; Tue, 4 Aug 1998 02:26:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23237 for ; Tue, 4 Aug 1998 02:26:46 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id LAA08374 for freebsd-current@FreeBSD.ORG; Tue, 4 Aug 1998 11:26:34 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 1B5371516; Tue, 4 Aug 1998 11:09:40 +0200 (CEST) Message-ID: <19980804110940.B13697@keltia.freenix.fr> Date: Tue, 4 Aug 1998 11:09:40 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: CTM checksum errors? Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199808040227.UAA00389@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199808040227.UAA00389@harmony.village.org>; from Warner Losh on Mon, Aug 03, 1998 at 08:27:14PM -0600 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4518 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Warner Losh: > One good thing about all of this, however. I think I may have found a > way to get a reproducible crash with soft updates: > ctm -b /part/with/soft/updates/CVS * It used to be a very easy way to crash them on my box too. They seem to be pretty stable now. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #62: Mon Jul 27 20:47:08 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 03:15:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA28522 for freebsd-current-outgoing; Tue, 4 Aug 1998 03:15:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA28517 for ; Tue, 4 Aug 1998 03:15:56 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.8/8.7.3) id MAA02061 for freebsd-current@freebsd.org; Tue, 4 Aug 1998 12:15:33 +0200 (CEST) From: Holm Tiffe Message-Id: <199808041015.MAA02061@magnet.geophysik.tu-freiberg.de> Subject: state of unionfs ? To: freebsd-current@FreeBSD.ORG Date: Tue, 4 Aug 1998 12:15:33 +0200 (CEST) Reply-To: freebsd@magnet.geophysik.tu-freiberg.de X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Can someone here explain what the state of UNIONFS in -current is ? I have a little bit tested now but I can't see the contents of the directory in the mountpoint. Example: # ls /usr8/src COPYRIGHT bin gnu minst.log usr.bin CVS build.log include release usr.sbin Makefile contrib kerberosIV sbin Makefile.alpha doc lib share Makefile.orig etc libexec sys README games lkm tools # mount -t union -o -b /usr8/src /home/holm/sys # mount /dev/sd0s1a on / (local, writes: sync 735 async 2806) /dev/sd0s1e on /usr (NFS exported, local, writes: sync 131 async 1560) /dev/sd1e on /usr8 (NFS exported, local, writes: sync 273 async 791) procfs on /proc (local) amd:114 on /hosts red-bull:/usr12 on /mnt_tmp/red-bull/usr12 :/usr8/src on /usr/home/holm/sys (noclusterw) # ls /usr/home/holm/sys # Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 03:24:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29642 for freebsd-current-outgoing; Tue, 4 Aug 1998 03:24:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29637 for ; Tue, 4 Aug 1998 03:24:51 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id MAA01406; Tue, 4 Aug 1998 12:21:40 +0200 (CEST) To: Daniel Aaron Meyer cc: current@FreeBSD.ORG Subject: Re: page faults and swapping In-reply-to: Your message of "Mon, 03 Aug 1998 12:07:36 EDT." Date: Tue, 04 Aug 1998 12:21:40 +0200 Message-ID: <1404.902226100@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This means that either you hit a race condition in vnode management, or your memory is hosed by something slapping random pointers around or your hardware has trouble. Can you reproduce this problem ? Poul-Henning >#4 0xf01d653f in trap () >#5 0xf0132d9d in cache_zap () >#6 0xf01331ae in cache_enter () >#7 0xf01b62dd in ufs_lookup () -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 04:50:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10983 for freebsd-current-outgoing; Tue, 4 Aug 1998 04:50:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10977 for ; Tue, 4 Aug 1998 04:50:29 -0700 (PDT) (envelope-from ehritz@dbai.tuwien.ac.at) Received: from arcturus.dbai.tuwien.ac.at (arcturus.dbai.tuwien.ac.at [128.130.111.20]) by vexpert.dbai.tuwien.ac.at (8.8.8/8.8.8) with ESMTP id NAA16641 for ; Tue, 4 Aug 1998 13:50:17 +0200 (MET-DST) From: Gerald Ehritz Received: (from ehritz@localhost) by arcturus.dbai.tuwien.ac.at (8.8.5/8.8.5) id NAA15805 for freebsd-current@freebsd.org; Tue, 4 Aug 1998 13:50:16 +0200 (MET DST) Date: Tue, 4 Aug 1998 13:50:16 +0200 (MET DST) Message-Id: <199808041150.NAA15805@arcturus.dbai.tuwien.ac.at> To: freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 /3.0-980725 completely X-Sun-Charset: US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi to all who contributed to this, I made a test with FreeBSD 3.0-19980725 today, and both versions of pine 3.96 and 4.02 locks up the pc! Here is the history: 1.) We used a FreeBSD 2.2 box for modem login since 2 years. In June i upgraded to 3.0 snap and everything works except pine locks up the pc. 2.) We allways had NFS mounted mail- and user- dirs! ( and it worked). No changes on the server (SunOS 4.1.3_U1). 3.) All versions of pine (2.2.6 code, 3.0 code, version 3.96, 4.0 and 4.02) kill the machine IF i write out an attachment ( may be > 100k size) to the home dir (NFS mounted), works if write it to /tmp! 4.) Pine works IF i only read and write mails (mail NFS mounted)! Will pine ever work across NFS ? If not we have to switch to another mail reader! I am asking me, why it had worked on an old FreeBSD (2.2) system. Any ideas? Gerald To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 05:39:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17378 for freebsd-current-outgoing; Tue, 4 Aug 1998 05:39:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17373 for ; Tue, 4 Aug 1998 05:39:26 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl1.philips.com with ESMTP id OAA04704 for ; Tue, 4 Aug 1998 14:39:14 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id OAA18083 for ; Tue, 4 Aug 1998 14:39:13 +0200 (MET DST) Received: (qmail 11523 invoked by uid 666); 4 Aug 1998 12:37:17 -0000 Message-ID: <19980804143717.B8574@hal.mpn.cp.philips.com> Date: Tue, 4 Aug 1998 14:37:17 +0200 From: Jos Backus To: Gerald Ehritz , freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 /3.0-980725 completely Mail-Followup-To: Gerald Ehritz , freebsd-current@FreeBSD.ORG References: <199808041150.NAA15805@arcturus.dbai.tuwien.ac.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808041150.NAA15805@arcturus.dbai.tuwien.ac.at>; from Gerald Ehritz on Tue, Aug 04, 1998 at 01:50:16PM +0200 X-Files: The Truth is out there! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 04, 1998 at 01:50:16PM +0200, Gerald Ehritz wrote: > Any ideas? Locking and NFS are an interesting combo, to say the least (I've heard that the upcoming BSD/OS 4.0 does do locking properly over NFS (as far as that is possible)). However, you could sidestep the issue by delivering mail to Maildirs and using the Maildir patches to pine. This entails switching from sendmail to another MTA called qmail (mostly easy, depending on your setup/amount of local hacks). See http://www.qmail.org for details. Good luck! Hth, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 05:58:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19928 for freebsd-current-outgoing; Tue, 4 Aug 1998 05:58:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19922 for ; Tue, 4 Aug 1998 05:58:25 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id WAA01326; Tue, 4 Aug 1998 22:58:00 +1000 Date: Tue, 4 Aug 1998 22:58:00 +1000 From: Bruce Evans Message-Id: <199808041258.WAA01326@godzilla.zeta.org.au> To: bde@zeta.org.au, mike@smith.net.au Subject: Re: IO performance (UFS read clustering), bad ZIP drive performance Cc: current@FreeBSD.ORG, rock@cs.uni-sb.de, tlambert@primenet.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Should it be committed? You could have included that information >in-band in the original posting, and I would have done so instead of >filing it in my "to be worried about" folder. It depends :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 06:06:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21290 for freebsd-current-outgoing; Tue, 4 Aug 1998 06:06:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from enterprise.cs.unm.edu (enterprise-atm.cs.unm.edu [198.83.90.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA21232 for ; Tue, 4 Aug 1998 06:05:56 -0700 (PDT) (envelope-from cfaehl@cs.unm.edu) Received: from avarice.cs.unm.edu [198.83.92.131] by enterprise.cs.unm.edu with esmtp (Exim 1.80 #2) id 0z3gmR-0004Yd-00; Tue, 4 Aug 1998 07:05:31 -0600 X-Mailer: exmh version 2.0.2 2/24/98 To: Gerald Ehritz cc: freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 /3.0-980725 completely In-reply-to: Your message of "Tue, 04 Aug 1998 13:50:16 +0200." <199808041150.NAA15805@arcturus.dbai.tuwien.ac.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 07:05:24 -0600 From: "Chris D. Faehl" Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi to all who contributed to this, > > I made a test with FreeBSD 3.0-19980725 today, and both versions of pine 3.96 and 4.02 locks up the pc! > > Here is the history: > > 1.) We used a FreeBSD 2.2 box for modem login since 2 years. In June i upgraded to 3.0 snap and everything works except pine locks up the pc. > > 2.) We allways had NFS mounted mail- and user- dirs! ( and it worked). No changes on the server (SunOS 4.1.3_U1). > > 3.) All versions of pine (2.2.6 code, 3.0 code, version 3.96, 4.0 and 4.02) kill the machine IF i write out an attachment ( may be > 100k size) to the home dir (NFS mounted), works if write it to /tmp! > > 4.) Pine works IF i only read and write mails (mail NFS mounted)! > > > Will pine ever work across NFS ? > If not we have to switch to another mail reader! > > I am asking me, why it had worked on an old FreeBSD (2.2) system. > > Any ideas? Sure. If I recall, the consensus was, "NFS client bugs in -current". So, the problem has been recognized (not sure if it's been duplicated widely, though). Likely it'll get fixed. My Really Big Idea is: FreeBSD 3.0 is in situ. You appear to be treating it like it's a production system. Perhaps you really want to be running -stable. > > Gerald > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ------------------------------------------------------------------------------- Chris Faehl | Email: cfaehl@cs.unm.edu The University of New Mexico | URL: http://www.cs.unm.edu/~cfaehl Computer Science Dept., Rm. FEC 313 | Phone: 505/277-3016 Albuquerque, NM 87131 USA | FAX: 505/277-6927 ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 06:24:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24395 for freebsd-current-outgoing; Tue, 4 Aug 1998 06:24:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24390 for ; Tue, 4 Aug 1998 06:24:24 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id WAA19702 for ; Tue, 4 Aug 1998 22:54:10 +0930 (CST) Received: by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA07551; Tue, 4 Aug 1998 22:54:10 +0930 Date: Tue, 4 Aug 1998 22:54:10 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: current@FreeBSD.ORG Subject: Softupdates panic Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm getting a repeatable softupdates-related panic doing a 'make test' on the itcl3.0a2 source tree (from ftp://ftp.tcltk.com/pub/itcl/itcl3.0a2.tar.gz), when I run the following as a regular user (this is actually executed as part of the master 'make test', but this is the specific part which seems to be gumming up the works): cd /usr2/itcl3.0a2/tcl8.0.3-2/unix (echo cd ../tests\;source interp.test) | ./tcltest This test seems to leave the machine in an inconsistent state; running any further tests (e.g. fCmd.test, which always fails for me for whatever reason; or just running the make test from the top of the tree) will invariably panic the machine with the following: handle_workitem_remove: bad file delta Debugger("panic") stopped at _Debugger+0x36:movb $0,_in_Debugger:98 db> trace _Debugger(f0116a21) at _Debugger+0x36 _panic(f01bb240,f08b9860,0,0,f01e4fbc) at _panic+0x5a _handle_workitem_remove(f08b9860) at _handle_workitem_remove+0x69 _softdep_process_worklist(0) at _softdep_process_worklist+0xe9 _sched_sync(f39eabf3,f013c528,f02348bc,3000000,f01e3aba) at _sched_sync+0x1ae _kproc_start(f02348bc) at _proc_start+0x31 _fork_trampoline() at _form_trampoline+0x19 db> Unfortunately, I don't have my partitions set up right to enable crashdumps. I first noticed this a few weeks back, and the problem still persists with my kernel current as of yesterday. My softupdates source files are: ffs_softdep.c: $Id: ffs_softdep.c,v 1.12 1998/06/12 21:21:26 julian Exp $ softdep.h: $Id: softdep.h,v 1.4 1998/05/19 23:07:25 julian Exp $ and I have softupdates running on two partitions: /dev/wd0s2a on / (NFS exported, local, writes: sync 3 async 60) /dev/wd0s2f on /usr (local, soft-updates, writes: sync 2 async 119) /dev/wd1s3e on /usr2 (local, soft-updates, writes: sync 2 async 22) /dev/wd1s3f on /home (local, writes: sync 11 async 32) /dev/wd0s2e on /var (local, writes: sync 115 async 116) /dev/wd0s1 on /c (local) /dev/wd1s1 on /d (local) /dev/wd1s5 on /e (local) procfs on /proc (local) mfs:30 on /tmp (asynchronous, local, writes: sync 3 async 8) localhost:/ on /crypt Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 06:24:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24472 for freebsd-current-outgoing; Tue, 4 Aug 1998 06:24:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24454 for ; Tue, 4 Aug 1998 06:24:53 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id WAA19707 for ; Tue, 4 Aug 1998 22:54:41 +0930 (CST) Received: by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA01386; Tue, 4 Aug 1998 22:54:41 +0930 Date: Tue, 4 Aug 1998 22:54:40 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: current@FreeBSD.ORG Subject: DEVFS/SLICE & extended partitions Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does DEVFS/SLICE support MSDOS Extended partitions? Running a devfs/slice-enabled kernel doesnt present me with the mountpoints I've been using with a "regular" kernel: [morden|root] 22:35 ~ mount ... /dev/wd0s1 on /c (local) /dev/wd1s1 on /d (local) /dev/wd1s5 on /e (local) ... [morden|root] 22:35 ~ fdisk wd1 ******* Working on device /dev/rwd1 ******* parameters extracted from in-core disklabel are: cylinders=620 heads=128 sectors/track=63 (8064 blks/cyl) parameters to be used for BIOS calculations are: cylinders=620 heads=128 sectors/track=63 (8064 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 6,(Primary 'big' DOS (> 32MB)) start 63, size 2048193 (1000 Meg), flag 0 beg: cyl 0/ sector 1/ head 1; end: cyl 253/ sector 63/ head 127 The data for partition 2 is: sysid 5,(Extended DOS) start 2048256, size 1024128 (500 Meg), flag 0 beg: cyl 254/ sector 1/ head 0; end: cyl 380/ sector 63/ head 127 The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 3072384, size 1927296 (941 Meg), flag 80 (active) beg: cyl 381/ sector 1/ head 0; end: cyl 619/ sector 63/ head 127 The data for partition 4 is: Thanks, Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 07:26:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06393 for freebsd-current-outgoing; Tue, 4 Aug 1998 07:26:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles210.castles.com [208.214.165.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06371; Tue, 4 Aug 1998 07:26:23 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id HAA00482; Tue, 4 Aug 1998 07:25:24 -0700 (PDT) Message-Id: <199808041425.HAA00482@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG, wpaul@FreeBSD.ORG Subject: Re: Etherlink XL driver In-reply-to: Your message of "04 Aug 1998 09:47:02 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Tue, 04 Aug 1998 07:25:23 -0700 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id HAA06380 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The Etherlink XL driver seems to be working fine. How about committing > it to -current and removing the XL probe/attach code from the vx > driver? The fact that Bill hasn't committed it already tends to indicate he's still in testing. I wouldn't want to rush him *too* much. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 07:36:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08725 for freebsd-current-outgoing; Tue, 4 Aug 1998 07:36:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles210.castles.com [208.214.165.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08692 for ; Tue, 4 Aug 1998 07:36:09 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id HAA00558; Tue, 4 Aug 1998 07:34:38 -0700 (PDT) Message-Id: <199808041434.HAA00558@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Bruce Evans cc: mike@smith.net.au, current@FreeBSD.ORG, rock@cs.uni-sb.de, tlambert@primenet.com Subject: Re: IO performance (UFS read clustering), bad ZIP drive performance In-reply-to: Your message of "Tue, 04 Aug 1998 22:58:00 +1000." <199808041258.WAA01326@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 07:34:37 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Should it be committed? You could have included that information > >in-band in the original posting, and I would have done so instead of > >filing it in my "to be worried about" folder. > > It depends :-). Given that you hold the "depends" criteria, will you be assessing them and taking the ultimately requisite action, or should I just commit the patch and wait for your complaint(s) in the hope that they're more illuminating? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 07:42:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09775 for freebsd-current-outgoing; Tue, 4 Aug 1998 07:42:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles210.castles.com [208.214.165.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09686 for ; Tue, 4 Aug 1998 07:42:23 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id HAA00599; Tue, 4 Aug 1998 07:41:19 -0700 (PDT) Message-Id: <199808041441.HAA00599@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Kris Kennaway cc: current@FreeBSD.ORG Subject: Re: DEVFS/SLICE & extended partitions In-reply-to: Your message of "Tue, 04 Aug 1998 22:54:40 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 07:41:18 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Does DEVFS/SLICE support MSDOS Extended partitions? It doesn't seem to properly. > Running a > devfs/slice-enabled kernel doesnt present me with the mountpoints I've > been using with a "regular" kernel: > > [morden|root] 22:35 ~ mount > > .... > /dev/wd0s1 on /c (local) > /dev/wd1s1 on /d (local) > /dev/wd1s5 on /e (local) s5 is the "extended" slice, but it should be being scanned for more slices. I remember talking to Julian at Usenix about this; I don't think he's committed anything based on the outcome of that yet. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 08:05:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15414 for freebsd-current-outgoing; Tue, 4 Aug 1998 08:05:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15409 for ; Tue, 4 Aug 1998 08:05:35 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id LAA01850; Tue, 4 Aug 1998 11:05:18 -0400 (EDT) (envelope-from wollman) Date: Tue, 4 Aug 1998 11:05:18 -0400 (EDT) From: Garrett Wollman Message-Id: <199808041505.LAA01850@khavrinen.lcs.mit.edu> To: current@FreeBSD.ORG Cc: dillon@backplane.com, hag@ai.mit.edu Subject: Bizarre deadlock Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My Diablo news box is falling over at regular, annoying intervals. I had initially thought it was some sort of priority-inversion deadlock, but now it looks even more serious.... After spending about 45 minutes tracing through the system with DDB, I found: 1) Most processes are blocked on the inode for the root directory. (Of course, this means that any time a process wakes up and tries to do some I/O, it will get blocked.) 2) I could follow the chain of inode locks down through NINE processes. The process holding the root directory should only have been using it to do a lookup. 3) The lock on the inode at the end of the chain was wanted by three processes, but was either totally free, or was being held shared (oops, no way to tell by whom). I didn't write down enough information, unfortunately, to identify precisely which inode this was. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 08:16:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17790 for freebsd-current-outgoing; Tue, 4 Aug 1998 08:16:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17608 for ; Tue, 4 Aug 1998 08:16:00 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id BAA10574; Wed, 5 Aug 1998 01:15:40 +1000 Date: Wed, 5 Aug 1998 01:15:40 +1000 From: Bruce Evans Message-Id: <199808041515.BAA10574@godzilla.zeta.org.au> To: bde@zeta.org.au, mike@smith.net.au Subject: Re: IO performance (UFS read clustering), bad ZIP drive performance Cc: current@FreeBSD.ORG, rock@cs.uni-sb.de, tlambert@primenet.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Given that you hold the "depends" criteria, will you be assessing them >and taking the ultimately requisite action, or should I just commit the >patch and wait for your complaint(s) in the hope that they're more >illuminating? The change is in my version so I won't forget about it. You can assess it if you want. Note that it is just a quick (but probably correct) fix for "not mature" support for larger I/O clusters. The problem could also be fixed by initializing d_maxio to nonzero in devswitches for all disk devices. Then the < 0 case would only occur for disk devices that you forgot. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 08:51:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26510 for freebsd-current-outgoing; Tue, 4 Aug 1998 08:51:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tor-dev1.nbc.netcom.ca (tor-dev1.nbc.netcom.ca [207.181.89.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26491 for ; Tue, 4 Aug 1998 08:50:43 -0700 (PDT) (envelope-from dacole@netcom.ca) Received: from localhost (dacole@localhost) by tor-dev1.nbc.netcom.ca (8.8.8/8.8.8) with SMTP id LAA23655 for ; Tue, 4 Aug 1998 11:50:03 -0400 (EDT) X-Authentication-Warning: tor-dev1.nbc.netcom.ca: dacole owned process doing -bs Date: Tue, 4 Aug 1998 11:50:02 -0400 (EDT) From: Dave Cole X-Sender: dacole@tor-dev1.nbc.netcom.ca To: current@FreeBSD.ORG Subject: booting with verbosity by default? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to force my systems to always boot with '-v'.. Is there any way to do this without operator intervention? ---------------------------------------------------------------- Dave Cole (DC1110) | dacole@netcom.ca Systems Administrator |* dacole@rik.net * | office/~dacole/ Netcom Canada |* www.rik.net/~dacole/ * 905 King Street West, Toronto, M6K 3G9 | phone - 416.341.5801 Toronto, Ontario, Canada, Earth, Sol | fax - 416.341.5725 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 09:17:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01973 for freebsd-current-outgoing; Tue, 4 Aug 1998 09:17:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01943; Tue, 4 Aug 1998 09:16:38 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id SAA27947; Tue, 4 Aug 1998 18:16:25 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Tue, 4 Aug 1998 18:16:24 +0200 (MET DST) Mime-Version: 1.0 To: Mike Smith Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG, wpaul@FreeBSD.ORG Subject: Re: Etherlink XL driver References: <199808041425.HAA00482@antipodes.cdrom.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 04 Aug 1998 18:16:24 +0200 In-Reply-To: Mike Smith's message of "Tue, 04 Aug 1998 07:25:23 -0700" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA01948 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > > The Etherlink XL driver seems to be working fine. How about committing > > it to -current and removing the XL probe/attach code from the vx > > driver? > The fact that Bill hasn't committed it already tends to indicate he's > still in testing. I wouldn't want to rush him *too* much. 8) Well, this is what -current is for, after all. And considering that noone has reported any serious trouble so far, and that there is a fallback driver (vx) in case problems arise, I don't see any reason not to commit it. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 09:44:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06331 for freebsd-current-outgoing; Tue, 4 Aug 1998 09:44:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06299 for ; Tue, 4 Aug 1998 09:44:37 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id JAA22586; Tue, 4 Aug 1998 09:39:18 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdP22574; Tue Aug 4 16:39:09 1998 Date: Tue, 4 Aug 1998 09:39:00 -0700 (PDT) From: Julian Elischer To: Kris Kennaway cc: current@FreeBSD.ORG Subject: Re: DEVFS/SLICE & extended partitions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG groan, I'd forgotten that I still have to write the 'extended' handler. sorry about that.. maybe this weekend. julian On Tue, 4 Aug 1998, Kris Kennaway wrote: > Does DEVFS/SLICE support MSDOS Extended partitions? Running a > devfs/slice-enabled kernel doesnt present me with the mountpoints I've > been using with a "regular" kernel: > > [morden|root] 22:35 ~ mount > > ... > /dev/wd0s1 on /c (local) > /dev/wd1s1 on /d (local) > /dev/wd1s5 on /e (local) > ... > > [morden|root] 22:35 ~ fdisk wd1 > > ******* Working on device /dev/rwd1 ******* > parameters extracted from in-core disklabel are: > cylinders=620 heads=128 sectors/track=63 (8064 blks/cyl) > > parameters to be used for BIOS calculations are: > cylinders=620 heads=128 sectors/track=63 (8064 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 6,(Primary 'big' DOS (> 32MB)) > start 63, size 2048193 (1000 Meg), flag 0 > beg: cyl 0/ sector 1/ head 1; > end: cyl 253/ sector 63/ head 127 > The data for partition 2 is: > sysid 5,(Extended DOS) > start 2048256, size 1024128 (500 Meg), flag 0 > beg: cyl 254/ sector 1/ head 0; > end: cyl 380/ sector 63/ head 127 > The data for partition 3 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 3072384, size 1927296 (941 Meg), flag 80 (active) > beg: cyl 381/ sector 1/ head 0; > end: cyl 619/ sector 63/ head 127 > The data for partition 4 is: > > > Thanks, > > Kris > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 10:04:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11278 for freebsd-current-outgoing; Tue, 4 Aug 1998 10:04:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11247 for ; Tue, 4 Aug 1998 10:04:28 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA23612; Tue, 4 Aug 1998 10:00:53 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdk23599; Tue Aug 4 17:00:46 1998 Date: Tue, 4 Aug 1998 10:00:36 -0700 (PDT) From: Julian Elischer To: Garrett Wollman cc: current@FreeBSD.ORG, dillon@backplane.com, hag@ai.mit.edu Subject: Re: Bizarre deadlock In-Reply-To: <199808041505.LAA01850@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG was there any 'mount' operation going on? there are some suspicious paths related to locking mounts and the root vn julian On Tue, 4 Aug 1998, Garrett Wollman wrote: > My Diablo news box is falling over at regular, annoying intervals. I > had initially thought it was some sort of priority-inversion deadlock, > but now it looks even more serious.... > > After spending about 45 minutes tracing through the system with DDB, I > found: > > 1) Most processes are blocked on the inode for the root directory. > (Of course, this means that any time a process wakes up and tries to > do some I/O, it will get blocked.) > > 2) I could follow the chain of inode locks down through NINE > processes. The process holding the root directory should only have > been using it to do a lookup. > > 3) The lock on the inode at the end of the chain was wanted by three > processes, but was either totally free, or was being held shared > (oops, no way to tell by whom). I didn't write down enough > information, unfortunately, to identify precisely which inode this > was. > > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > wollman@lcs.mit.edu | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 10:14:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13364 for freebsd-current-outgoing; Tue, 4 Aug 1998 10:14:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13319 for ; Tue, 4 Aug 1998 10:13:49 -0700 (PDT) (envelope-from dillon@backplane.com) Received: (dillon@localhost) by apollo.backplane.com (8.8.8/8.6.5) id KAA02861; Tue, 4 Aug 1998 10:13:30 -0700 (PDT) Date: Tue, 4 Aug 1998 10:13:30 -0700 (PDT) From: Matthew Dillon Message-Id: <199808041713.KAA02861@apollo.backplane.com> To: Julian Elischer Cc: Garrett Wollman , current@FreeBSD.ORG, hag@ai.mit.edu Subject: Re: Bizarre deadlock Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :was there any 'mount' operation going on? :there are some suspicious paths related to locking mounts and the root vn : :julian : I dunno re: garrett's box, but my test box running -current/SMP/SoftUpdates locked up in a similar manner two weeks ago. Definitely no mount op going on. I didn't get a dump, unfortunately. The lockup occured when I tried to do a 'df'. That is, everything was fine until I did the 'df', and that caused the machine to lockup (or perhaps the sync df does caused the machine to lockup). -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 10:41:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20428 for freebsd-current-outgoing; Tue, 4 Aug 1998 10:41:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20358 for ; Tue, 4 Aug 1998 10:41:31 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id NAA14599; Tue, 4 Aug 1998 13:41:05 -0400 (EDT) Date: Tue, 4 Aug 1998 13:41:05 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Dave Cole cc: current@FreeBSD.ORG Subject: Re: booting with verbosity by default? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Take a look at what boot(8) has to say about /boot.config. On Tue, 4 Aug 1998, Dave Cole wrote: > I would like to force my systems to always boot with '-v'.. Is there > any way to do this without operator intervention? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 10:55:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23189 for freebsd-current-outgoing; Tue, 4 Aug 1998 10:55:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23024 for ; Tue, 4 Aug 1998 10:54:28 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA26016; Tue, 4 Aug 1998 10:49:38 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdj26014; Tue Aug 4 17:49:36 1998 Message-ID: <35C749AD.1CFBAE39@whistle.com> Date: Tue, 04 Aug 1998 10:49:33 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Kris Kennaway CC: current@FreeBSD.ORG Subject: Re: Softupdates panic References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I confirm this panic and am working on isolating it.. Kris Kennaway wrote: > > I'm getting a repeatable softupdates-related panic doing a 'make test' on > the itcl3.0a2 source tree (from > ftp://ftp.tcltk.com/pub/itcl/itcl3.0a2.tar.gz), when I run the following > as a regular user (this is actually executed as part of the master 'make > test', but this is the specific part which seems to be gumming up the > works): > > cd /usr2/itcl3.0a2/tcl8.0.3-2/unix > (echo cd ../tests\;source interp.test) | ./tcltest > > This test seems to leave the machine in an inconsistent state; running any > further tests (e.g. fCmd.test, which always fails for me for whatever > reason; or just running the make test from the top of the tree) will > invariably panic the machine with the following: > > handle_workitem_remove: bad file delta > Debugger("panic") > stopped at _Debugger+0x36:movb $0,_in_Debugger:98 > db> trace > _Debugger(f0116a21) at _Debugger+0x36 > _panic(f01bb240,f08b9860,0,0,f01e4fbc) at _panic+0x5a > _handle_workitem_remove(f08b9860) at _handle_workitem_remove+0x69 > _softdep_process_worklist(0) at _softdep_process_worklist+0xe9 > _sched_sync(f39eabf3,f013c528,f02348bc,3000000,f01e3aba) at _sched_sync+0x1ae > _kproc_start(f02348bc) at _proc_start+0x31 > _fork_trampoline() at _form_trampoline+0x19 > db> > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 11:04:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25546 for freebsd-current-outgoing; Tue, 4 Aug 1998 11:04:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25432 for ; Tue, 4 Aug 1998 11:04:18 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA26250; Tue, 4 Aug 1998 10:53:48 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdW26245; Tue Aug 4 17:53:47 1998 Message-ID: <35C74AA8.3F54BC7E@whistle.com> Date: Tue, 04 Aug 1998 10:53:44 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Matthew Dillon CC: Garrett Wollman , current@FreeBSD.ORG, hag@ai.mit.edu Subject: Re: Bizarre deadlock References: <199808041713.KAA02861@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > :was there any 'mount' operation going on? > :there are some suspicious paths related to locking mounts and the root vn > : > :julian > : > > I dunno re: garrett's box, but my test box running -current/SMP/SoftUpdates > locked up in a similar manner two weeks ago. Definitely no mount op going > on. I didn't get a dump, unfortunately. The lockup occured when I tried > to do a 'df'. That is, everything was fine until I did the 'df', and > that caused the machine to lockup (or perhaps the sync df does caused > the machine to lockup). > > -Matt > > Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet > Communications > (Please include original email in any response) there once was a bug where df would crash the system as it did an open on the device which did a NON-IO operation on the drive which preemted the IO operations and forgot to restart them when it finished.. this was in sd.c but I would have expected to have heard of this a lot more if this bug had resurfaced. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 11:35:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02195 for freebsd-current-outgoing; Tue, 4 Aug 1998 11:35:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt053nd2.san.rr.com (dt053nd2.san.rr.com [204.210.34.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02189 for ; Tue, 4 Aug 1998 11:35:46 -0700 (PDT) (envelope-from Studded@dal.net) Received: from dal.net (Studded@localhost [127.0.0.1]) by dt053nd2.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA05121; Tue, 4 Aug 1998 11:35:27 -0700 (PDT) (envelope-from Studded@dal.net) Message-ID: <35C7546F.F80BEBE1@dal.net> Date: Tue, 04 Aug 1998 11:35:27 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE-0507 i386) MIME-Version: 1.0 To: Dave Cole CC: current@FreeBSD.ORG Subject: Re: booting with verbosity by default? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dave Cole wrote: > > I would like to force my systems to always boot with '-v'.. Is there > any way to do this without operator intervention? echo -v > /boot.config 'man boot' for more info. Doug PS, next time please send questions of this sort to freebsd-questions@freebsd.org -- *** Chief Operations Officer, DALnet IRC network *** When you don't know where you're going, every road will take you there. - Yiddish Proverb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 12:00:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05768 for freebsd-current-outgoing; Tue, 4 Aug 1998 12:00:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05735 for ; Tue, 4 Aug 1998 12:00:20 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id UAA00670; Tue, 4 Aug 1998 20:56:43 +0200 (CEST) To: Daniel Aaron Meyer cc: current@FreeBSD.ORG Subject: Re: page faults and swapping In-reply-to: Your message of "Tue, 04 Aug 1998 14:39:54 EDT." Date: Tue, 04 Aug 1998 20:56:43 +0200 Message-ID: <668.902257003@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Danie l Aaron Meyer writes: > > The problem could be reproduced, but I was able to isolate a bad >simm and that took care of my problems. You have no idea how happy I am to hear that: I was the last one to muck with the vfs name cache :-) Poul-Henning -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 12:26:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09874 for freebsd-current-outgoing; Tue, 4 Aug 1998 12:26:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09848 for ; Tue, 4 Aug 1998 12:26:04 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA00302; Tue, 4 Aug 1998 12:13:53 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpddhk296; Tue Aug 4 19:13:50 1998 Message-ID: <35C75D6A.FF6D5DF@whistle.com> Date: Tue, 04 Aug 1998 12:13:46 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Kris Kennaway CC: current@FreeBSD.ORG Subject: Re: Softupdates panic References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > [...] > cd /usr2/itcl3.0a2/tcl8.0.3-2/unix > (echo cd ../tests\;source interp.test) | ./tcltest > Actually the damage is done by the test 'fCmd.test' but the pannic will not occur for 16 seconds which is about how long that data takes to be flushed.. whatever happens to be running 16 seconds later (e.g. interp.test) gets blamed.. julian (on the trail of it) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 12:33:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11194 for freebsd-current-outgoing; Tue, 4 Aug 1998 12:33:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fang.cs.sunyit.edu (fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11180 for ; Tue, 4 Aug 1998 12:33:43 -0700 (PDT) (envelope-from meyerd1@fang.cs.sunyit.edu) Received: from fang.cs.sunyit.edu (fang.cs.sunyit.edu [192.52.220.66]) by fang.cs.sunyit.edu (8.8.8/8.8.8) with SMTP id OAA21630; Tue, 4 Aug 1998 14:39:55 -0400 (EDT) (envelope-from meyerd1@fang.cs.sunyit.edu) Date: Tue, 4 Aug 1998 14:39:54 -0400 (EDT) From: Daniel Aaron Meyer To: Poul-Henning Kamp cc: current@FreeBSD.ORG Subject: Re: page faults and swapping In-Reply-To: <1404.902226100@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem could be reproduced, but I was able to isolate a bad simm and that took care of my problems. Unfortunately I had memory hole enabled in the bios and this made it much more difficult to isolate the problem. The kernel's memory probe would only pick up the first 16384K. The MAXMEM option had to be enabled for anything more than 16384K. Thanks to all those who gave suggestions, -Dan > > This means that either you hit a race condition in vnode management, > or your memory is hosed by something slapping random pointers around > or your hardware has trouble. > > Can you reproduce this problem ? > > Poul-Henning > > >#4 0xf01d653f in trap () > >#5 0xf0132d9d in cache_zap () > >#6 0xf01331ae in cache_enter () > >#7 0xf01b62dd in ufs_lookup () > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 13:12:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17892 for freebsd-current-outgoing; Tue, 4 Aug 1998 13:12:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17835 for ; Tue, 4 Aug 1998 13:12:10 -0700 (PDT) (envelope-from stb@hanse.de) Received: from daemon.Hanse.DE (daemon.Hanse.DE [193.174.9.17]) by rrz.Hanse.DE (8.8.8/8.8.8) with ESMTP id WAA27513; Tue, 4 Aug 1998 22:05:10 +0200 (CEST) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id WAA02775; Tue, 4 Aug 1998 22:11:25 +0200 (CEST) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id WAA27278; Tue, 4 Aug 1998 22:08:32 +0200 (CEST) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Tue, 4 Aug 1998 22:08:31 +0200 (CEST) From: Stefan Bethke Reply-To: Stefan Bethke To: Julian Elischer cc: Parag Patel , current@FreeBSD.ORG Subject: Re: Netatalk name-registering problem with -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 1 Aug 1998, Julian Elischer wrote: > yes there is a problem with -current and netatalk name registration. > > it's on my list of things to look at.. > there are two suspicious areas.. I've delved a bit into this and think I've found the problem. In net/ether_output, around line 365, if_simloop() is called with a fixed LLC header length of ETHER_HDR_LEN, instead of whatever length the header has (in case of a SNAP frame [Phase 2], its a LLC header). Currently testing, patch forthcoming... Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 13:37:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22549 for freebsd-current-outgoing; Tue, 4 Aug 1998 13:37:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22533 for ; Tue, 4 Aug 1998 13:37:18 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id WAA07825 for current@FreeBSD.ORG; Tue, 4 Aug 1998 22:30:08 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id WAA05724 for current@FreeBSD.ORG; Tue, 4 Aug 1998 22:21:53 +0200 (CEST) (envelope-from andreas) Message-ID: <19980804222153.A5282@klemm.gtn.com> Date: Tue, 4 Aug 1998 22:21:53 +0200 From: Andreas Klemm To: current@FreeBSD.ORG Subject: make world failure in ...doc/smm/08.sendmailop Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> share/doc/smm/05.fastfs --- _stamp.extraobjs --- touch _stamp.extraobjs --- paper.ascii.gz --- (cd /home/src/share/doc/smm/05.fastfs; groff -mtty-char -Tascii -e -t -ms -o1- / home/src/share/doc/smm/05.fastfs/0.t /home/src/share/doc/smm/05.fastfs/1.t /home /src/share/doc/smm/05.fastfs/2.t /home/src/share/doc/smm/05.fastfs/3.t /home/src /share/doc/smm/05.fastfs/4.t /home/src/share/doc/smm/05.fastfs/5.t /home/src/sha re/doc/smm/05.fastfs/6.t) | gzip -cn > paper.ascii.gz /home/src/share/doc/smm/05.fastfs/3.t:159: warning: indent cannot be negative /home/src/share/doc/smm/05.fastfs/3.t:194: warning: indent cannot be negative /home/src/share/doc/smm/05.fastfs/4.t:117: warning: indent cannot be negative ===> share/doc/smm/06.nfs --- _stamp.extraobjs --- touch _stamp.extraobjs --- paper.ascii.gz --- (cd /home/src/share/doc/smm/06.nfs; groff -mtty-char -Tascii -me -o1- /home/src/ share/doc/smm/06.nfs/0.t /home/src/share/doc/smm/06.nfs/1.t /home/src/share/doc/ smm/06.nfs/2.t /home/src/share/doc/smm/06.nfs/ref.t) | gzip -cn > paper.ascii.g z ===> share/doc/smm/08.sendmailop make: don't know how to make op.me. Stop *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 15:28:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07193 for freebsd-current-outgoing; Tue, 4 Aug 1998 15:28:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07176 for ; Tue, 4 Aug 1998 15:28:26 -0700 (PDT) (envelope-from ckempf@singularity.enigami.com) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id SAA02365; Tue, 4 Aug 1998 18:27:56 -0400 (EDT) To: freebsd-current@FreeBSD.ORG Subject: Maelstrom problems X-Copyright: Copyright (C) 1998 Cory Kempf. All Rights Reserved X-PGP-Fingerprint: 191E 2FB7 E27D 76C3 8E79 4D26 2B3B B20F 2A9C 1E1A X-PGP-Keyloc: ; finger ckempf@enigami.com From: Cory Kempf Date: 04 Aug 1998 18:27:56 -0400 In-Reply-To: Julian Elischer's message of "Tue, 4 Aug 1998 10:00:36 -0700 (PDT)" Message-ID: Lines: 23 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I built the Mailstrom port, and tried to run it. Maelstrom is not a happy camper: % Maelstrom X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 129 (MIT-SHM) Minor opcode of failed request: 3 (X_ShmPutImage) Serial number of failed request: 96 Current serial number in output stream: 97 Anyone know what this means? +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 15:30:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07507 for freebsd-current-outgoing; Tue, 4 Aug 1998 15:30:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07391 for ; Tue, 4 Aug 1998 15:30:04 -0700 (PDT) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with SMTP id SAA28418; Tue, 4 Aug 1998 18:29:33 -0400 (EDT) Date: Tue, 4 Aug 1998 18:29:33 -0400 (EDT) From: Brian Feldman To: Andreas Klemm cc: current@FreeBSD.ORG Subject: Re: make world failure in ...doc/smm/08.sendmailop In-Reply-To: <19980804222153.A5282@klemm.gtn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG well commit a fix :) i.e. --- src/share/doc/smm/08.sendmailop/Makefile.old Tue Aug 4 18:28:22 1998 +++ src/share/doc/smm/08.sendmailop/Makefile Tue Aug 4 18:26:19 1998 @@ -5,7 +5,7 @@ SRCS= op.me MACROS= -me -SRCDIR= ${.CURDIR}/../../../../usr.sbin/sendmail/doc/op +SRCDIR= ${.CURDIR}/../../../../contrib/sendmail/doc/op USE_PIC= yes USE_EQN= yes Cheers Brian On Tue, 4 Aug 1998, Andreas Klemm wrote: > ===> share/doc/smm/05.fastfs > --- _stamp.extraobjs --- > touch _stamp.extraobjs > --- paper.ascii.gz --- > (cd /home/src/share/doc/smm/05.fastfs; groff -mtty-char -Tascii -e -t -ms -o1- > / > home/src/share/doc/smm/05.fastfs/0.t /home/src/share/doc/smm/05.fastfs/1.t > /home > /src/share/doc/smm/05.fastfs/2.t /home/src/share/doc/smm/05.fastfs/3.t > /home/src > /share/doc/smm/05.fastfs/4.t /home/src/share/doc/smm/05.fastfs/5.t > /home/src/sha > re/doc/smm/05.fastfs/6.t) | gzip -cn > paper.ascii.gz > /home/src/share/doc/smm/05.fastfs/3.t:159: warning: indent cannot be negative > /home/src/share/doc/smm/05.fastfs/3.t:194: warning: indent cannot be negative > /home/src/share/doc/smm/05.fastfs/4.t:117: warning: indent cannot be negative > ===> share/doc/smm/06.nfs > --- _stamp.extraobjs --- > touch _stamp.extraobjs > --- paper.ascii.gz --- > (cd /home/src/share/doc/smm/06.nfs; groff -mtty-char -Tascii -me -o1- > /home/src/ > share/doc/smm/06.nfs/0.t /home/src/share/doc/smm/06.nfs/1.t > /home/src/share/doc/ > smm/06.nfs/2.t /home/src/share/doc/smm/06.nfs/ref.t) | gzip -cn > > paper.ascii.g > z > ===> share/doc/smm/08.sendmailop > make: don't know how to make op.me. Stop > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > > > -- > Andreas Klemm http://www.FreeBSD.ORG/~andreas > What gives you 90% more speed, for example, in kernel compilation ? > http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html > "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 16:04:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12265 for freebsd-current-outgoing; Tue, 4 Aug 1998 16:04:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12257 for ; Tue, 4 Aug 1998 16:04:14 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA09804; Tue, 4 Aug 1998 15:56:26 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdkf9800; Tue Aug 4 22:56:22 1998 Message-ID: <35C79191.7DE14518@whistle.com> Date: Tue, 04 Aug 1998 15:56:17 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Kris Kennaway CC: current@FreeBSD.ORG Subject: Re: Softupdates panic References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, here's the problem simplified: cd /tmp (assuming mounted soft-updates) mkdir d1 mkdir d1/d2 mkdir d2 mv d2 d1 rmdir d1/d2 rmdir d1 [system will panic in 15 seconds at 'sync' of that data.] fix to follow. (and checked in I guess) julian Kris Kennaway wrote: > > I'm getting a repeatable softupdates-related panic doing a 'make test' on > the itcl3.0a2 source tree (from > ftp://ftp.tcltk.com/pub/itcl/itcl3.0a2.tar.gz), when I run the following > as a regular user (this is actually executed as part of the master 'make > test', but this is the specific part which seems to be gumming up the > works): > > cd /usr2/itcl3.0a2/tcl8.0.3-2/unix > (echo cd ../tests\;source interp.test) | ./tcltest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 16:17:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13862 for freebsd-current-outgoing; Tue, 4 Aug 1998 16:17:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13856 for ; Tue, 4 Aug 1998 16:17:36 -0700 (PDT) (envelope-from stb@hanse.de) Received: from daemon.Hanse.DE (daemon.Hanse.DE [193.174.9.17]) by rrz.Hanse.DE (8.8.8/8.8.8) with ESMTP id AAA28917; Wed, 5 Aug 1998 00:40:02 +0200 (CEST) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id AAA10897; Wed, 5 Aug 1998 00:46:25 +0200 (CEST) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id AAA02134; Wed, 5 Aug 1998 00:43:55 +0200 (CEST) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Wed, 5 Aug 1998 00:43:55 +0200 (CEST) From: Stefan Bethke To: Julian Elischer cc: Parag Patel , current@FreeBSD.ORG Subject: Re: Netatalk name-registering problem with -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Aug 1998, Stefan Bethke wrote: > On Sat, 1 Aug 1998, Julian Elischer wrote: > > > yes there is a problem with -current and netatalk name registration. > > > > it's on my list of things to look at.. > > there are two suspicious areas.. > > I've delved a bit into this and think I've found the problem. > > In net/ether_output, around line 365, if_simloop() is called with a fixed > LLC header length of ETHER_HDR_LEN, instead of whatever length the header > has (in case of a SNAP frame [Phase 2], its a LLC header). There's a second problem: because packets for our own address are handed to ether_output, an aarpresolve() is tried. As it seems to me, our own MAC address isn't in the table, so a request goes out and is received by aarp_input(). aarp_input() however doesn't respond to requests coming from the address of the interface it was received from; so the packet is never delivered. The quick workaround is to call if_simloop() from ddp_output. The right thing to do would be to integrate AARP into the routing tables (as for ARP). If I could only figure out how this whole stuff works... Enought muttering: please test the following patch. At least you can successfully register, deregister, and query NBPs again; because my oldish IIcx went up in smoke the last night I have nothing to really test it against. --------- snip ---------- Index: src/sys/net/if_ethersubr.c =================================================================== RCS file: /home/ncvs/src/sys/net/if_ethersubr.c,v retrieving revision 1.51 diff -u -r1.51 if_ethersubr.c --- if_ethersubr.c 1998/06/14 20:58:14 1.51 +++ if_ethersubr.c 1998/08/04 20:13:12 @@ -132,6 +132,7 @@ register struct rtentry *rt; register struct ether_header *eh; int off, len = m->m_pkthdr.len, loop_copy = 0; + int hlen; /* link layer header lenght */ struct arpcom *ac = (struct arpcom *)ifp; if ((ifp->if_flags & (IFF_UP|IFF_RUNNING)) != (IFF_UP|IFF_RUNNING)) @@ -161,6 +162,7 @@ time_second < rt->rt_rmx.rmx_expire) senderr(rt == rt0 ? EHOSTDOWN : EHOSTUNREACH); } + hlen = ETHER_HDR_LEN; switch (dst->sa_family) { #ifdef INET case AF_INET: @@ -203,6 +205,7 @@ llc.llc_snap_ether_type = htons( ETHERTYPE_AT ); bcopy(&llc, mtod(m, caddr_t), sizeof(struct llc)); type = htons(m->m_pkthdr.len); + hlen = sizeof(struct llc) + ETHER_HDR_LEN; } else { type = htons(ETHERTYPE_AT); } @@ -362,10 +365,10 @@ if ((m->m_flags & M_BCAST) || (loop_copy > 0)) { struct mbuf *n = m_copy(m, 0, (int)M_COPYALL); - (void) if_simloop(ifp, n, dst, ETHER_HDR_LEN); + (void) if_simloop(ifp, n, dst, hlen); } else if (bcmp(eh->ether_dhost, eh->ether_shost, ETHER_ADDR_LEN) == 0) { - (void) if_simloop(ifp, m, dst, ETHER_HDR_LEN); + (void) if_simloop(ifp, m, dst, hlen); return(0); /* XXX */ } } Index: src/sys/netatalk/ddp_output.c =================================================================== RCS file: /home/ncvs/src/sys/netatalk/ddp_output.c,v retrieving revision 1.12 diff -u -r1.12 ddp_output.c --- ddp_output.c 1998/07/13 06:34:02 1.12 +++ ddp_output.c 1998/08/04 22:29:06 @@ -72,6 +72,11 @@ } deh->deh_bytes = htonl( deh->deh_bytes ); +#ifdef NETATALK_DEBUG + printf ("ddp_output: from %d.%d:%d to %d.%d:%d\n", + ntohs(deh->deh_snet), deh->deh_snode, deh->deh_sport, + ntohs(deh->deh_dnet), deh->deh_dnode, deh->deh_dport); +#endif return( ddp_route( m, &ddp->ddp_route )); } @@ -142,13 +147,24 @@ } } else { m_freem( m ); - return( EINVAL ); +#ifdef NETATALK_DEBUG + if (ro->ro_rt == NULL) + printf ("ddp_route: no ro_rt.\n"); + else if (ro->ro_rt->rt_ifa == NULL) + printf ("ddp_route: no ro_rt->rt_ifa\n"); + else + printf ("ddp_route: no ro_rt->rt_ifa->ifa_ifp\n"); +#endif + return( ENETUNREACH ); } if ( aa == NULL ) { -printf( "ddp_route: oops\n" ); +#ifdef NETATALK_DEBUG + printf( "ddp_route: no atalk address found for %s%d\n", + ifp->if_name, ifp->if_unit); +#endif m_freem( m ); - return( EINVAL ); + return( ENETUNREACH ); } /* @@ -189,7 +205,24 @@ } ro->ro_rt->rt_use++; +#ifdef NETATALK_DEBUG + printf ("ddp_route: from %d.%d to %d.%d, via %d.%d (%s%d)\n", + ntohs(satosat(&aa->aa_addr)->sat_addr.s_net), + satosat(&aa->aa_addr)->sat_addr.s_node, + ntohs(satosat(&ro->ro_dst)->sat_addr.s_net), + satosat(&ro->ro_dst)->sat_addr.s_node, + ntohs(gate.sat_addr.s_net), + gate.sat_addr.s_node, + ifp->if_name, ifp->if_unit); +#endif + + /* short-circuit the output if we're sending this to ourself */ + if ((satosat(&aa->aa_addr)->sat_addr.s_net == satosat(&ro->ro_dst)->sat_addr.s_net) && + (satosat(&aa->aa_addr)->sat_addr.s_node == satosat(&ro->ro_dst)->sat_addr.s_node)) + { + return (if_simloop(ifp, m, (struct sockaddr *)&gate, 0)); + } + return((*ifp->if_output)( ifp, m, (struct sockaddr *)&gate, NULL)); /* XXX */ } - ---------- snip ----------- Cheers, Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 16:28:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15325 for freebsd-current-outgoing; Tue, 4 Aug 1998 16:28:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa4-05.ix.netcom.com [207.93.136.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15307 for ; Tue, 4 Aug 1998 16:28:28 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id QAA08203; Tue, 4 Aug 1998 16:28:16 -0700 (PDT) (envelope-from tomdean) Date: Tue, 4 Aug 1998 16:28:16 -0700 (PDT) Message-Id: <199808042328.QAA08203@ix.netcom.com> From: Thomas Dean To: freebsd-current@FreeBSD.ORG Subject: Sendmail 8.8.9.1 is in /usr/src/contrib/sendmail Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A late cvsup, yesterday, put Sendmail 8.8.9.1 in src/contrib. When will this replace 8.8.8.4 in src/usr.sbin? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 17:41:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29512 for freebsd-current-outgoing; Tue, 4 Aug 1998 17:41:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29472 for ; Tue, 4 Aug 1998 17:40:59 -0700 (PDT) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.8.8/8.8.7) id UAA03187; Tue, 4 Aug 1998 20:40:30 -0400 (EDT) (envelope-from lee) Message-ID: <19980804204029.A3165@st-lcremean.tidalwave.net> Date: Tue, 4 Aug 1998 20:40:29 -0400 From: Lee Cremeans To: Cory Kempf , freebsd-current@FreeBSD.ORG Subject: Re: Maelstrom problems Reply-To: lcremean@tidalwave.net References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from Cory Kempf on Tue, Aug 04, 1998 at 06:27:56PM -0400 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 04, 1998 at 06:27:56PM -0400, Cory Kempf wrote: > > I built the Mailstrom port, and tried to run it. Maelstrom is not a > happy camper: > > % Maelstrom > X Error of failed request: BadAccess (attempt to access private resource denied) > Major opcode of failed request: 129 (MIT-SHM) ^^^^^^^ Do you have "options SYSVSHM" in your kernel config file? MIT-SHM can't work without it. -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 17:42:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29748 for freebsd-current-outgoing; Tue, 4 Aug 1998 17:42:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29688 for ; Tue, 4 Aug 1998 17:42:03 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA00768; Tue, 4 Aug 1998 17:40:32 -0700 (PDT) Message-Id: <199808050040.RAA00768@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Cory Kempf cc: freebsd-current@FreeBSD.ORG Subject: Re: Maelstrom problems In-reply-to: Your message of "04 Aug 1998 18:27:56 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 17:40:32 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I built the Mailstrom port, and tried to run it. Maelstrom is not a > happy camper: > > % Maelstrom > X Error of failed request: BadAccess (attempt to access private resource denied) > Major opcode of failed request: 129 (MIT-SHM) > Minor opcode of failed request: 3 (X_ShmPutImage) > Serial number of failed request: 96 > Current serial number in output stream: 97 > > > Anyone know what this means? It's related to the MIT-SHM feature. You could try removing the SYSV_SHM option from your kernel config, or tweak it to allocate more pages (in case you're running out). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 18:43:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09784 for freebsd-current-outgoing; Tue, 4 Aug 1998 18:43:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09779 for ; Tue, 4 Aug 1998 18:43:22 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id VAA06013; Tue, 4 Aug 1998 21:43:50 -0400 (EDT) Date: Tue, 4 Aug 1998 21:43:50 -0400 (EDT) From: Daniel Eischen Message-Id: <199808050143.VAA06013@pcnet1.pcnet.com> To: ckempf@enigami.com, freebsd-current@FreeBSD.ORG Subject: Re: Maelstrom problems Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I built the Mailstrom port, and tried to run it. Maelstrom is not a > happy camper: > > % Maelstrom > X Error of failed request: BadAccess (attempt to access private resource denied) > Major opcode of failed request: 129 (MIT-SHM) > Minor opcode of failed request: 3 (X_ShmPutImage) > Serial number of failed request: 96 > Current serial number in output stream: 97 > > Anyone know what this means? Do you have shared memory support built into the kernel? options SYSVSHM options SYSVSEM options SYSVMSG Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 19:17:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15266 for freebsd-current-outgoing; Tue, 4 Aug 1998 19:17:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15221 for ; Tue, 4 Aug 1998 19:17:12 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id TAA05247 for ; Tue, 4 Aug 1998 19:16:49 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd005227; Tue Aug 4 19:16:42 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id TAA01976 for current@freebsd.org; Tue, 4 Aug 1998 19:16:42 -0700 (MST) From: Terry Lambert Message-Id: <199808050216.TAA01976@usr02.primenet.com> Subject: Heads up on LFS To: current@FreeBSD.ORG Date: Wed, 5 Aug 1998 02:16:42 +0000 (GMT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks like the SpinOS people are using LFS. They are also using CAM. They credit FreeBSD on their web pages. They need Linux to build and FreeBSD to boot. 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 20:22:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26104 for freebsd-current-outgoing; Tue, 4 Aug 1998 20:22:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26098 for ; Tue, 4 Aug 1998 20:22:15 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id UAA25508; Tue, 4 Aug 1998 20:22:04 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd025492; Tue Aug 4 20:21:59 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id UAA06030; Tue, 4 Aug 1998 20:21:57 -0700 (MST) From: Terry Lambert Message-Id: <199808050321.UAA06030@usr02.primenet.com> Subject: Re: pine 3.96 locks 3.0-980621 /3.0-980725 completely To: Jos.Backus@nl.origin-it.com (Jos Backus) Date: Wed, 5 Aug 1998 03:21:56 +0000 (GMT) Cc: ehritz@dbai.tuwien.ac.at, freebsd-current@FreeBSD.ORG In-Reply-To: <19980804143717.B8574@hal.mpn.cp.philips.com> from "Jos Backus" at Aug 4, 98 02:37:17 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Locking and NFS are an interesting combo, to say the least (I've heard that > the upcoming BSD/OS 4.0 does do locking properly over NFS (as far as that is > possible)). It better. I gave them a pointer to my FreeBSD patches and my diatribe on fcntl(, F_POSIX,) and the (minor) user space code needed last time they asked for them... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 20:34:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA28013 for freebsd-current-outgoing; Tue, 4 Aug 1998 20:34:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27995 for ; Tue, 4 Aug 1998 20:34:26 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id UAA06133; Tue, 4 Aug 1998 20:34:12 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd006112; Tue Aug 4 20:34:06 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id UAA06891; Tue, 4 Aug 1998 20:34:05 -0700 (MST) From: Terry Lambert Message-Id: <199808050334.UAA06891@usr02.primenet.com> Subject: Re: Maelstrom problems To: ckempf@enigami.com (Cory Kempf) Date: Wed, 5 Aug 1998 03:34:05 +0000 (GMT) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from "Cory Kempf" at Aug 4, 98 06:27:56 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I built the Mailstrom port, and tried to run it. Maelstrom is not a > happy camper: > > % Maelstrom > X Error of failed request: BadAccess (attempt to access private resource denied) > Major opcode of failed request: 129 (MIT-SHM) > Minor opcode of failed request: 3 (X_ShmPutImage) > Serial number of failed request: 96 > Current serial number in output stream: 97 > > > Anyone know what this means? Generally, it means you haven't updated your kernel since the bogus AF_UNIX UNIX domain socket/named pipe change was backed out. If the problem goes away when you use "localhost:0.0" as your display name, then that's definitely what it is... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 21:20:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05085 for freebsd-current-outgoing; Tue, 4 Aug 1998 21:20:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA05080 for ; Tue, 4 Aug 1998 21:20:20 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z3v3Q-0002Iv-00; Tue, 4 Aug 1998 21:20:00 -0700 Date: Tue, 4 Aug 1998 21:19:57 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: Heads up on LFS In-Reply-To: <199808050216.TAA01976@usr02.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 5 Aug 1998, Terry Lambert wrote: > It looks like the SpinOS people are using LFS. They are also using > CAM. They credit FreeBSD on their web pages. What is SpinOS? Are you sure it is BSD LFS, or is there own LFS? > They need Linux to build and FreeBSD to boot. 8-) 8-). > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 22:04:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10527 for freebsd-current-outgoing; Tue, 4 Aug 1998 22:04:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10522 for ; Tue, 4 Aug 1998 22:04:10 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id XAA08393; Tue, 4 Aug 1998 23:03:45 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199808050503.XAA08393@panzer.plutotech.com> Subject: Re: Heads up on LFS In-Reply-To: <199808050216.TAA01976@usr02.primenet.com> from Terry Lambert at "Aug 5, 98 02:16:42 am" To: tlambert@primenet.com (Terry Lambert) Date: Tue, 4 Aug 1998 23:03:45 -0600 (MDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote... > It looks like the SpinOS people are using LFS. They are also using > CAM. They credit FreeBSD on their web pages. > > They need Linux to build and FreeBSD to boot. 8-) 8-). Do you have a URL? I'm curious at least to see how they're using CAM... Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 22:48:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16169 for freebsd-current-outgoing; Tue, 4 Aug 1998 22:48:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from wpaul@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16103; Tue, 4 Aug 1998 22:48:36 -0700 (PDT) (envelope-from wpaul) From: Bill Paul Message-Id: <199808050548.WAA16103@hub.freebsd.org> Subject: Re: Etherlink XL driver In-Reply-To: from =?ISO-8859-1?Q?Dag=2DErling_Coidan_Sm=F8rgrav?= at "Aug 4, 98 06:16:24 pm" To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=) Date: Tue, 4 Aug 1998 22:48:34 -0700 (PDT) Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG, mike@smith.net.au X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith writes: > > > The Etherlink XL driver seems to be working fine. How about committing > > > it to -current and removing the XL probe/attach code from the vx > > > driver? > > The fact that Bill hasn't committed it already tends to indicate he's > > still in testing. I wouldn't want to rush him *too* much. 8) > > Well, this is what -current is for, after all. And considering that > noone has reported any serious trouble so far, and that there is a > fallback driver (vx) in case problems arise, I don't see any reason > not to commit it. > Putting code in -current when you know there's something wrong with it is just... well, wrong. And I know there's at least one bug in the XL driver. I knew there were two until tonight, but I just fixed one. (Unfortunately, it was a problem I could not reproduce in the lab with the hardware that I have: the MII access code had a problem somewhere which caused it to fail to read any PHY registers on certain boards which a) report a PCI revision of 0 and b) were installed on relatively slow machines. Unfortunately, my 3c905B is integrated onto the motherboard of a 400Mhz PII, which makes it hard to move it to a slower machine. To compound matters, the problem card and its owner are in Brazil. Fortunately, the gentleman who owns (Hi Rodolfo!) it was able to give me access to the system via ssh and I was able to debug the problem using a hastily contrived LKM.) The remaining problem is that I know of at least one 3c900 board that doesn't work right. (Incidentally, since this is going to -hackers: if you're having a problem with the XL driver generating an error message that says 'MII without any PHY!' and you have a 3c905B card, please grab the latest version of the driver from www.freebsd.org/~wpaul/3Com and let me know if the problem goes away.) The -current branch may be bleeding edge, but I don't feel that means that I shouldn't try my best to work out all the bugs before I commit new code to it, which is what I'm doing, at least when I'm not being interrupted by Real Work (tm). That said, my plan is to commit the 3.0 version to -current sometime next week. After a couple more weeks there, I'll commit the 2.2 version. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 4 23:10:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19520 for freebsd-current-outgoing; Tue, 4 Aug 1998 23:10:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA19499 for ; Tue, 4 Aug 1998 23:10:41 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z3wmF-0003du-00; Tue, 4 Aug 1998 23:10:24 -0700 Date: Tue, 4 Aug 1998 23:10:20 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "Kenneth D. Merry" cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: Heads up on LFS In-Reply-To: <199808050503.XAA08393@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Aug 1998, Kenneth D. Merry wrote: > Terry Lambert wrote... > > It looks like the SpinOS people are using LFS. They are also using > > CAM. They credit FreeBSD on their web pages. > > > > They need Linux to build and FreeBSD to boot. 8-) 8-). > > Do you have a URL? I'm curious at least to see how they're using CAM... I've had to dig to find it (it is called "Spin", not "SpinOS"). http://www.cs.washington.edu/research/projects/spin/www/ > Ken > -- > Kenneth Merry > ken@plutotech.com Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 00:03:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28348 for freebsd-current-outgoing; Wed, 5 Aug 1998 00:03:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28341; Wed, 5 Aug 1998 00:03:48 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id JAA11961; Wed, 5 Aug 1998 09:03:35 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Wed, 5 Aug 1998 09:03:34 +0200 (MET DST) Mime-Version: 1.0 To: Bill Paul Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG, mike@smith.net.au Subject: Re: Etherlink XL driver References: <199808050548.WAA16103@hub.freebsd.org> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 05 Aug 1998 09:03:34 +0200 In-Reply-To: Bill Paul's message of "Tue, 4 Aug 1998 22:48:34 -0700 (PDT)" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id AAA28342 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Paul writes: > That said, my plan is to commit the 3.0 version to -current sometime > next week. After a couple more weeks there, I'll commit the 2.2 > version. Oh goody :) The lack of a proper driver for the XL range has been a major PITA (well, in my A at least) for some time. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 00:31:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA03177 for freebsd-current-outgoing; Wed, 5 Aug 1998 00:31:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA03171; Wed, 5 Aug 1998 00:31:35 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id AAA16591; Wed, 5 Aug 1998 00:30:28 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Bill Paul cc: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=), current@FreeBSD.ORG, mike@smith.net.au Subject: Re: Etherlink XL driver In-reply-to: Your message of "Tue, 04 Aug 1998 22:48:34 PDT." <199808050548.WAA16103@hub.freebsd.org> Date: Wed, 05 Aug 1998 00:30:28 -0700 Message-ID: <16587.902302228@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Directed just to -current, sparing -hackers from the evils of crossposting] > Putting code in -current when you know there's something wrong with it > is just... well, wrong. And I know there's at least one bug in the XL > driver. I knew there were two until tonight, but I just fixed one. Just to chime in here a bit - this is both true and not true. If something is truly a WIP and there's just no reason to release it prematurely, then everything you say above is true. If, however, putting it in -current will significantly increase its exposure to testers (and, incidently, get it into the SNAPshot releases for folks wishing to install using some piece of hardware which would be facilitated thusly) then it's a good idea. So just use your best judgement, folks - there are no hard and fast rules as far as this is concerned. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 00:52:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05265 for freebsd-current-outgoing; Wed, 5 Aug 1998 00:52:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05260 for ; Wed, 5 Aug 1998 00:52:08 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id AAA08610; Wed, 5 Aug 1998 00:51:56 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd008577; Wed Aug 5 00:51:46 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id AAA21008; Wed, 5 Aug 1998 00:51:43 -0700 (MST) From: Terry Lambert Message-Id: <199808050751.AAA21008@usr02.primenet.com> Subject: Re: Heads up on LFS To: tom@uniserve.com (Tom) Date: Wed, 5 Aug 1998 07:51:42 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: from "Tom" at Aug 4, 98 09:19:57 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It looks like the SpinOS people are using LFS. They are also using > > CAM. They credit FreeBSD on their web pages. > > What is SpinOS? Are you sure it is BSD LFS, or is there own LFS? An exokernel OS. It was one of the OS's voted for on the page pointed to on the OS War to Cure Cystic Fibrosis thread on the advocacy news group (there was an "OS war" in which you could pledge money in the name of your favorite OS). It's run by one of the universities -- I can't rememebr which one, sorry -- and it seems that AltaVista can't seem to find it. It's written in Modula 3 (of all things) and incorporates nullfs and lfs from FreeBSD, as well as CAM. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 01:02:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06613 for freebsd-current-outgoing; Wed, 5 Aug 1998 01:02:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06608 for ; Wed, 5 Aug 1998 01:02:15 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id BAA21587; Wed, 5 Aug 1998 01:01:58 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd021571; Wed Aug 5 01:01:53 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id BAA21512; Wed, 5 Aug 1998 01:01:51 -0700 (MST) From: Terry Lambert Message-Id: <199808050801.BAA21512@usr02.primenet.com> Subject: Re: Heads up on LFS To: tom@uniserve.com (Tom) Date: Wed, 5 Aug 1998 08:01:50 +0000 (GMT) Cc: ken@plutotech.com, tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: from "Tom" at Aug 4, 98 11:10:20 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > It looks like the SpinOS people are using LFS. They are also using > > > CAM. They credit FreeBSD on their web pages. > > > > > > They need Linux to build and FreeBSD to boot. 8-) 8-). > > > > Do you have a URL? I'm curious at least to see how they're using CAM... > > I've had to dig to find it (it is called "Spin", not "SpinOS"). > > http://www.cs.washington.edu/research/projects/spin/www/ Thanks for digging this out for me; I have it bookmarked at work. If only FreeBSD supported Lina Tupple Spaces (;-) another intriging hint at a technology to get me asked for another URL)... The specific pages of interest are: http://www-spin.cs.washington.edu/commands.html Click on "filesystems". Then click on "Domains". FreeBSD is not credited in the "Acknowledgements", but on: http://velvet.cs.washington.edu/spin/docs/overview.html It says: The device driver layer of x86-SPIN utilizes code from the FreeBSD Operating System. For this reason SPIN has to be booted on a machine that has a FreeBSD file system. We get this by doing a minimal install of FreeBSD on the x86 machines where SPIN will be run. In addition we have a boot loader program (salboot.com) that runs either from a dos partition on the disk or from a floppy. For historic reasons x86-SPIN needs to be built on a Linux machine. It may be possible to build x86-SPIN in a different posix environment but we have not attempted this and couldn't provide help if you ran into problems. In order to build the FreeBSD portions of SPIN on Linux, some cross development tools are required. Sources for these tools are available as a single file (bsdtools.tar.gz) here at our site. Terry "The Human AltaVista" Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 01:17:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08381 for freebsd-current-outgoing; Wed, 5 Aug 1998 01:17:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08374 for ; Wed, 5 Aug 1998 01:17:35 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA10585; Wed, 5 Aug 1998 18:17:15 +1000 Date: Wed, 5 Aug 1998 18:17:15 +1000 From: Bruce Evans Message-Id: <199808050817.SAA10585@godzilla.zeta.org.au> To: meyerd1@fang.cs.sunyit.edu, phk@critter.freebsd.dk Subject: Re: page faults and swapping Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem could be reproduced, but I was able to isolate a bad >simm and that took care of my problems. Unfortunately I had memory hole >enabled in the bios and this made it much more difficult to isolate the >problem. The kernel's memory probe would only pick up the first 16384K. >The MAXMEM option had to be enabled for anything more than 16384K. If there's any device memory in the hole, then you shouldn't be happy to let the probe look at any memory in the hole or above. The probe may be confused by device memory (it may think it is normal RAM), and the probe doesn't understand any holes except the ISA one at 640K-1M, so there is no way to probe memory above the hole without risking confusion. The BIOS may have protected against such problems by reporting the extended memory size as the amount below the hole. Setting MAXMEM may defeat this protection. Holes above 64MB would cause similar problems even if MAXMEM is not set. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 02:03:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12554 for freebsd-current-outgoing; Wed, 5 Aug 1998 02:03:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12543 for ; Wed, 5 Aug 1998 02:02:46 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA13552; Wed, 5 Aug 1998 19:02:31 +1000 Date: Wed, 5 Aug 1998 19:02:31 +1000 From: Bruce Evans Message-Id: <199808050902.TAA13552@godzilla.zeta.org.au> To: dacole@netcom.ca, Studded@dal.net Subject: Re: booting with verbosity by default? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I would like to force my systems to always boot with '-v'.. Is there >> any way to do this without operator intervention? > >echo -v > /boot.config You also have to fix the boot code to not gratuitously ignore -v. >'man boot' for more info. "You may put a BIOS drive number, a controller type, a unit number, a par- tition, a kernel file name and the -b, -D, -h or -P options in /boot.config to set defaults..." No mention of -v. -b and -P in also cleared early, but -b sort of works because turning it off doesn't work, and -P works because it is processed even earlier. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 02:49:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17539 for freebsd-current-outgoing; Wed, 5 Aug 1998 02:49:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17534 for ; Wed, 5 Aug 1998 02:49:38 -0700 (PDT) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id LAA25974; Wed, 5 Aug 1998 11:48:26 +0200 (CEST) Message-ID: <19980805114825.A25826@cons.org> Date: Wed, 5 Aug 1998 11:48:25 +0200 From: Martin Cracauer To: Bruce Evans , cracauer@cons.org, freebsd-current@FreeBSD.ORG Subject: Re: make/SIGINT (Re: cvs commit: src/bin/sh jobs.c) References: <199805221609.CAA04233@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199805221609.CAA04233@godzilla.zeta.org.au>; from Bruce Evans on Sat, May 23, 1998 at 02:09:25AM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199805221609.CAA04233@godzilla.zeta.org.au>, Bruce Evans wrote: > >> I'm not happy with most of the patches. Even the tiny newline fix > >> in the signal handler doesn't work quite right. > > > >I assume you mean the fix to mkdep. Please take in mind that this > >particular fix depends on the latest sh diff I sent, otherwise it will > >not work. > > > >If it's something else, I'm afraid you need to be more precise. > > I mean the fix for calling out2str("\n") (possibly recursively) in sh's > signal handler. Newlines now get printed to often, so the signal handler > must be being called too often. You mean that one that is replaced by write(STDERR_FILENO, "\n", 1); in error.c:onint()? What happens is that nested shells (like in recursive makes or test04.sh of my testsuite) each print their own newline. The right thing would be one newline at all, not one per shell. onint is not being called more than once for each shell, so I consider this cosmetic. Another nitpick is that the newline and the shell prompt are sometimes being printed before the last line(s) put out by the compiler driver in a recursive make. I don't know what this implies, but it doesn't prevent the build from working and from being interruptable. I think some wrong newlines when killing builds should not prevent the fix from being commited, so that other people run their system with it and can point to other application programs that need to exit with proper status before the next release (I already spotted rsync). I put the newest fixes and the newest version of my testsuite on freefall:/home/cracauer/public_html (http://www.freebsd.org/~cracauer/) These include the wait fixes. If your observations were done without them, please repeat them with the newest version. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer cracauer@wavehh.hanse.de (batched, preferred for large mails) Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 06:25:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13240 for freebsd-current-outgoing; Wed, 5 Aug 1998 06:25:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13229 for ; Wed, 5 Aug 1998 06:24:58 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id PAA14274 for ; Wed, 5 Aug 1998 15:29:32 +0200 (CEST) (envelope-from regnauld@deepo.prosa.dk) Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id PAA04378 for ; Wed, 5 Aug 1998 15:30:29 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id PAA27923; Wed, 5 Aug 1998 15:28:05 +0200 (CEST) Message-ID: <19980805152805.30244@deepo.prosa.dk> Date: Wed, 5 Aug 1998 15:28:05 +0200 From: Philippe Regnauld To: freebsd-current@FreeBSD.ORG Subject: -current & pccard Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I decided to upgrade my Libretto from 2.2.6 to -current, and that part went fine. Of course I can't run PAO anymore (not a big problem), except that I have no way to cut power to the PCCARD anymore -- apart from physically removing it -- this is a problem when travelling, as having the ethernet card/modem running continuously drains batteries quite fast... Any way to do this under -current ("pccardc power" doesn't work) ? Also, there is no option to spindown the disk in the Libretto's BIOS -- do we have an IOCTL for that ? -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 07:04:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19648 for freebsd-current-outgoing; Wed, 5 Aug 1998 07:04:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19589; Wed, 5 Aug 1998 07:03:58 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id KAA19895; Wed, 5 Aug 1998 10:04:27 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Wed, 5 Aug 1998 10:04:27 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: Bill Paul cc: current@FreeBSD.ORG Subject: Re: Etherlink XL driver In-Reply-To: <199808050548.WAA16103@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG using the first version of the driver posted on 100mb segement seemed to have not great performance. The admin here said he was able to get ~8megs/sec over the segment using Linux and 11megs/sec via Solaris, the FreeBSD driver was never over 4.5megs and averaged around 3-3.5. This is ftp transfers. It seems to grab a LOT of data, then "stall" then grab, stall over and over. I know this is an older driver, i'll compile him a new kernel with the latest snapshot to see if there is an improvement. Just thought to let you know. This is on a -current box with a PCI card 905b on 100/TX. The driver was acting in full duplex mode, perhaps it should have been set to half-duplex and it was tripping on itself? The driver seems quite stable though, playing mp3s over NFS, while not a true "benchmark" works fine. My personal workstation is on a 10mbit segment and has had an uptime of 2days so far, no problems i can see. On a 10mbit segment though the driver (perhaps it's the card as i've not heard great reviews about the 905b) seems not be as fast as the de driver on a tulip chipset. Again, sorry this is a older version of the driver. Both boxes will be setup with the newer snapshots and if you're interested i'll post the performance. Thank you, Alfred Perlstein -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- http://www.freebsd.org/ > (Incidentally, since this is going to -hackers: if you're having a > problem with the XL driver generating an error message that says > 'MII without any PHY!' and you have a 3c905B card, please grab the > latest version of the driver from www.freebsd.org/~wpaul/3Com and > let me know if the problem goes away.) > > The -current branch may be bleeding edge, but I don't feel that means > that I shouldn't try my best to work out all the bugs before I commit > new code to it, which is what I'm doing, at least when I'm not being > interrupted by Real Work (tm). > > That said, my plan is to commit the 3.0 version to -current sometime > next week. After a couple more weeks there, I'll commit the 2.2 > version. > > -Bill > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 07:27:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23177 for freebsd-current-outgoing; Wed, 5 Aug 1998 07:27:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23144 for ; Wed, 5 Aug 1998 07:27:00 -0700 (PDT) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id QAA26403; Wed, 5 Aug 1998 16:26:39 +0200 (CEST) Message-ID: <19980805162638.A26329@cons.org> Date: Wed, 5 Aug 1998 16:26:38 +0200 From: Martin Cracauer To: Bruce Evans , cracauer@cons.org, freebsd-current@FreeBSD.ORG Subject: Re: make/SIGINT (Re: cvs commit: src/bin/sh jobs.c) References: <199805221609.CAA04233@godzilla.zeta.org.au> <19980805114825.A25826@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <19980805114825.A25826@cons.org>; from Martin Cracauer on Wed, Aug 05, 1998 at 11:48:25AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What happens is that nested shells (like in recursive makes or > test04.sh of my testsuite) each print their own newline. The right > thing would be one newline at all, not one per shell. onint is not > being called more than once for each shell, so I consider this > cosmetic. This seems fixable by if (tcgetpgrp(0) == getpid()) write(STDERR_FILENO, "\n", 1); Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer cracauer@wavehh.hanse.de (batched, preferred for large mails) Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 09:04:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06952 for freebsd-current-outgoing; Wed, 5 Aug 1998 09:04:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles246.castles.com [208.214.165.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06943 for ; Wed, 5 Aug 1998 09:04:07 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA03275; Wed, 5 Aug 1998 08:58:26 -0700 (PDT) Message-Id: <199808051558.IAA03275@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Bruce Evans cc: meyerd1@fang.cs.sunyit.edu, phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: page faults and swapping In-reply-to: Your message of "Wed, 05 Aug 1998 18:17:15 +1000." <199808050817.SAA10585@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Aug 1998 08:58:26 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The problem could be reproduced, but I was able to isolate a bad > >simm and that took care of my problems. Unfortunately I had memory hole > >enabled in the bios and this made it much more difficult to isolate the > >problem. The kernel's memory probe would only pick up the first 16384K. > >The MAXMEM option had to be enabled for anything more than 16384K. > > If there's any device memory in the hole, then you shouldn't be happy to > let the probe look at any memory in the hole or above. The probe may > be confused by device memory (it may think it is normal RAM), and the > probe doesn't understand any holes except the ISA one at 640K-1M, so > there is no way to probe memory above the hole without risking confusion. > > The BIOS may have protected against such problems by reporting the > extended memory size as the amount below the hole. Setting MAXMEM > may defeat this protection. Holes above 64MB would cause similar > problems even if MAXMEM is not set. Fortunately, in -current with VM86 defined this isn't an issue, as we can query BIOS functions which are able to report the hole correctly. Another reason for VM86 to become the default. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 09:07:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07313 for freebsd-current-outgoing; Wed, 5 Aug 1998 09:07:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07300 for ; Wed, 5 Aug 1998 09:07:24 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id KAA10361; Wed, 5 Aug 1998 10:06:24 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199808051606.KAA10361@panzer.plutotech.com> Subject: Re: Heads up on LFS In-Reply-To: <199808050801.BAA21512@usr02.primenet.com> from Terry Lambert at "Aug 5, 98 08:01:50 am" To: tlambert@primenet.com (Terry Lambert) Date: Wed, 5 Aug 1998 10:06:24 -0600 (MDT) Cc: tom@uniserve.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote... > > > > It looks like the SpinOS people are using LFS. They are also using > > > > CAM. They credit FreeBSD on their web pages. > > > > > > > > They need Linux to build and FreeBSD to boot. 8-) 8-). > > > > > > Do you have a URL? I'm curious at least to see how they're using CAM... > > > > I've had to dig to find it (it is called "Spin", not "SpinOS"). > > > > http://www.cs.washington.edu/research/projects/spin/www/ > > Thanks for digging this out for me; I have it bookmarked at work. > If only FreeBSD supported Lina Tupple Spaces (;-) another intriging > hint at a technology to get me asked for another URL)... > > The specific pages of interest are: > > http://www-spin.cs.washington.edu/commands.html > > Click on "filesystems". > > Then click on "Domains". > > FreeBSD is not credited in the "Acknowledgements", but on: > > http://velvet.cs.washington.edu/spin/docs/overview.html > > It says: > > The device driver layer of x86-SPIN utilizes code from the > FreeBSD Operating System. For this reason SPIN has to be > booted on a machine that has a FreeBSD file system. We get > this by doing a minimal install of FreeBSD on the x86 machines > where SPIN will be run. In addition we have a boot loader > program (salboot.com) that runs either from a dos partition > on the disk or from a floppy. I looked around the web site, and I even downloaded the source. It looks like they're using FreeBSD kernel sources circa late '96 or early '97. If they're using a CAM implementation at all, it must be DEC's CAM implementation when they run on the Alpha with DEC UNIX. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 09:11:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08788 for freebsd-current-outgoing; Wed, 5 Aug 1998 09:11:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA08750 for ; Wed, 5 Aug 1998 09:11:14 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z4697-0000Mx-00; Wed, 5 Aug 1998 09:10:37 -0700 Date: Wed, 5 Aug 1998 09:10:36 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "Kenneth D. Merry" cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: Heads up on LFS In-Reply-To: <199808051606.KAA10361@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 5 Aug 1998, Kenneth D. Merry wrote: > I looked around the web site, and I even downloaded the source. It > looks like they're using FreeBSD kernel sources circa late '96 or early > '97. If they're using a CAM implementation at all, it must be DEC's CAM > implementation when they run on the Alpha with DEC UNIX. According to the Spin SMP page, the FreeBSD code used is from 2.1.7 They plan to update to 3.0 to get SMP running though. > Ken > -- > Kenneth Merry > ken@plutotech.com Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 09:44:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14844 for freebsd-current-outgoing; Wed, 5 Aug 1998 09:44:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14817; Wed, 5 Aug 1998 09:44:40 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with ESMTP id JAA22036; Wed, 5 Aug 1998 09:44:20 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 5 Aug 1998 09:44:20 -0700 (PDT) From: Doug White To: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG, wpaul@FreeBSD.ORG Subject: Re: Etherlink XL driver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 4 Aug 1998, Dag-Erling Coidan [iso-8859-1] Smørgrav wrote: > The Etherlink XL driver seems to be working fine. How about committing > it to -current and removing the XL probe/attach code from the vx > driver? Except the 3c905-T4, which crashes hardcore (sorry I haven't been able to get back to you Bill, but work & buying a new car took away my time...) Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 10:16:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19687 for freebsd-current-outgoing; Wed, 5 Aug 1998 10:16:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fleming.cs.strath.ac.uk (bell.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19652; Wed, 5 Aug 1998 10:16:47 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from cs.strath.ac.uk (posh.dmem.strath.ac.uk [130.159.202.3]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id SAA00878 Wed, 5 Aug 1998 18:16:33 +0100 (BST) Message-ID: <35C89370.A1EB29F8@cs.strath.ac.uk> Date: Wed, 05 Aug 1998 18:16:32 +0100 From: Roger Hardiman Organization: Strathclyde Uni X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-980520-SNAP i386) MIME-Version: 1.0 To: current@FreeBSD.ORG, roger@cs.strath.ac.uk, multimedia@FreeBSD.ORG Subject: Patch for Bt848 driver to detect new Hauppauge 404 Cards Content-Type: multipart/mixed; boundary="------------30D9845A3F7ACB1405A3769F" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------30D9845A3F7ACB1405A3769F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, Please can someone commit this patch for the bt848 driver. It allows the new Hauppauge WinCastTV 404 card with NTSC tuner to be detected. It also tidies up some of my earlier initialisation code Amancio commited for me. Thanks Roger Hardiman Strathclyde Uni Telepresence Group --------------30D9845A3F7ACB1405A3769F Content-Type: text/plain; charset=us-ascii; name="patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="patch" *** brooktree848.c Wed Aug 5 18:08:21 1998 --- new_brooktree848.c Wed Aug 5 18:11:04 1998 *************** *** 1,4 **** ! /* BT848 1.38 Driver for Brooktree's Bt848 based cards. The Brooktree BT848 Driver driver is based upon Mark Tinguely and Jim Lowe's driver for the Matrox Meteor PCI card . The Philips SAA 7116 and SAA 7196 are very different chipsets than --- 1,4 ---- ! /* BT848 1.39 Driver for Brooktree's Bt848 based cards. The Brooktree BT848 Driver driver is based upon Mark Tinguely and Jim Lowe's driver for the Matrox Meteor PCI card . The Philips SAA 7116 and SAA 7196 are very different chipsets than *************** *** 267,272 **** --- 267,279 ---- 1.38 Further improvements on Hauppauge's rely on eeprom[9] to determine the tuner type 8) + AVerMedia card type added + + 1.39 08/05/98 Roger Hardiman + Updated Hauppauge detection code for Tuner ID 0x0a + for newer NTSC WinCastTV 404 with Bt878 chipset. + Tidied up PAL default in video_open() + */ #define DDB(x) x *************** video_open( bktr_ptr_t bktr ) *** 1621,1639 **** BT848_IFORM_X_XT0 | BT848_IFORM_F_NTSCM; bktr->format_params = BT848_IFORM_F_NTSCM; - frame_rate = 30; } else { bt848->iform = BT848_IFORM_M_MUX1 | BT848_IFORM_X_XT1 | BT848_IFORM_F_PALBDGHI; - bt848->adelay = format_params[BT848_IFORM_F_PALBDGHI].adelay; - bt848->bdelay = format_params[BT848_IFORM_F_PALBDGHI].bdelay; bktr->format_params = BT848_IFORM_F_PALBDGHI; - frame_rate = 25; } bktr->flags = (bktr->flags & ~METEOR_DEV_MASK) | METEOR_DEV0; bktr->max_clip_node = 0; --- 1628,1646 ---- BT848_IFORM_X_XT0 | BT848_IFORM_F_NTSCM; bktr->format_params = BT848_IFORM_F_NTSCM; } else { bt848->iform = BT848_IFORM_M_MUX1 | BT848_IFORM_X_XT1 | BT848_IFORM_F_PALBDGHI; bktr->format_params = BT848_IFORM_F_PALBDGHI; } + bt848->adelay = format_params[bktr->format_params].adelay; + bt848->bdelay = format_params[bktr->format_params].bdelay; + frame_rate = format_params[bktr->format_params].frame_rate; + bktr->flags = (bktr->flags & ~METEOR_DEV_MASK) | METEOR_DEV0; bktr->max_clip_node = 0; *************** checkTuner: *** 4413,4418 **** --- 4420,4426 ---- bktr->card.tuner = &tuners[ PHILIPS_NTSC ]; goto checkDBX; + case 0x0a: case 0x12: case 0x17: bktr->card.tuner = &tuners[ PHILIPS_FR1236_NTSC ]; --------------30D9845A3F7ACB1405A3769F-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 12:15:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08347 for freebsd-current-outgoing; Wed, 5 Aug 1998 12:15:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from SungSung.Dorm10.NCTU.edu.tw (SungSung.Dorm10.NCTU.edu.tw [140.113.121.204]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08339 for ; Wed, 5 Aug 1998 12:15:33 -0700 (PDT) (envelope-from AlanSung@SungSung.Dorm10.NCTU.edu.tw) Received: (from AlanSung@localhost) by SungSung.Dorm10.NCTU.edu.tw (8.8.8/8.8.7) id DAA05098 for freebsd-current@FreeBSD.ORG; Thu, 6 Aug 1998 03:15:19 +0800 (CST) (envelope-from AlanSung) From: ·s¤ôºk³X«È Message-Id: <199808051915.DAA05098@SungSung.Dorm10.NCTU.edu.tw> Subject: About VCD (raw data reading) To: freebsd-current@FreeBSD.ORG Date: Thu, 6 Aug 1998 03:15:19 +0800 (CST) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id MAA08343 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd got http://www.mahoroba.ne.jp/~naoya/archives/vcdr.tar.gz and patched, but it seems not working.... [AlanSung@ttyp1(SungSung)][/usr/tmp] >./vcdr /dev/cd0c 2 Can't read RAW data.  Is there any new patch for 3.0-CURRENT? my cdrom is TEAC 532S thanks for any help:) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 12:17:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08722 for freebsd-current-outgoing; Wed, 5 Aug 1998 12:17:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08716 for ; Wed, 5 Aug 1998 12:17:12 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id MAA19201; Wed, 5 Aug 1998 12:16:58 -0700 (PDT) (envelope-from jdp) Message-Id: <199808051916.MAA19201@austin.polstra.com> To: ken@plutotech.com Subject: Re: Heads up on LFS In-Reply-To: <199808051606.KAA10361@panzer.plutotech.com> References: <199808051606.KAA10361@panzer.plutotech.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Wed, 05 Aug 1998 12:16:58 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I looked around the web site, and I even downloaded the source. It > looks like they're using FreeBSD kernel sources circa late '96 or early > '97. If they're using a CAM implementation at all, it must be DEC's CAM > implementation when they run on the Alpha with DEC UNIX. I'm 99% sure you're right. I've talked to the SPIN folks before. I remember they were complaining loudly about how big and bulky CAM is. But that conversation took place when FreeBSD-CAM was still just a glimmer in the eyes of Justin and you. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 12:39:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12280 for freebsd-current-outgoing; Wed, 5 Aug 1998 12:39:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bogus.cs.colorado.edu (bogus.cs.colorado.edu [128.138.192.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12273 for ; Wed, 5 Aug 1998 12:39:25 -0700 (PDT) (envelope-from garnett@bogus.cs.colorado.edu) Received: from bogus.cs.colorado.edu (IDENT:garnett@localhost.cs.colorado.edu [127.0.0.1]) by bogus.cs.colorado.edu (8.9.1/8.9.1) with ESMTP id NAA10755 for ; Wed, 5 Aug 1998 13:41:30 -0600 (MDT) Message-Id: <199808051941.NAA10755@bogus.cs.colorado.edu> To: current@FreeBSD.ORG Subject: Re: Heads up on LFS In-reply-to: Your message of "Wed, 05 Aug 1998 09:10:36 PDT." Date: Wed, 05 Aug 1998 13:41:29 -0600 From: James Garnett Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom (tom) wrote: > > On Wed, 5 Aug 1998, Kenneth D. Merry wrote: > > > I looked around the web site, and I even downloaded the source. It > > looks like they're using FreeBSD kernel sources circa late '96 or early > > '97. If they're using a CAM implementation at all, it must be DEC's CAM > > implementation when they run on the Alpha with DEC UNIX. > > According to the Spin SMP page, the FreeBSD code used is from 2.1.7 > They plan to update to 3.0 to get SMP running though. It's not clear how alive SPIN really is anymore; it would be surprising if they actually did this. In the OS research community the word is that it is "Spun Down" or anything along similiar lines; work could be tailing off on it, although you'd have to ask Brian Bershad to be sure. There haven't been any papers on it in some time, at least not in (for example) Operating Systems Review or at the last SOSP. The current US OS hotspots are Utah (Flux), MIT (Exokernel), and Harvard (VINO). ~james To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 15:09:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02918 for freebsd-current-outgoing; Wed, 5 Aug 1998 15:09:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coleridge.kublai.com (coleridge.kublai.com [207.96.1.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02913 for ; Wed, 5 Aug 1998 15:09:34 -0700 (PDT) (envelope-from shmit@natasya.kublai.com) Received: from natasya.kublai.com (natasya.kublai.com [207.172.25.236]) by coleridge.kublai.com (8.8.8/8.8.8) with ESMTP id SAA01994 for ; Wed, 5 Aug 1998 18:09:15 -0400 (EDT) (envelope-from shmit@natasya.kublai.com) Received: (from shmit@localhost) by natasya.kublai.com (8.8.8/8.8.8) id SAA10723; Wed, 5 Aug 1998 18:09:13 -0400 (EDT) Message-ID: <19980805180913.10635@kublai.com> Date: Wed, 5 Aug 1998 18:09:13 -0400 From: Brian Cully To: current@FreeBSD.ORG Subject: Pthreads woes Reply-To: shmit@kublai.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i X-Sender: If your mailer pays attention to this, it's broken. X-PGP-Info: finger shmit@kublai.com for my public key. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm working on a program that spawns a bunch of threads in a pool, each of which sits on a condition variable. The main thread waits for a RADIUS request on a socket, it signals the condition variable on one of the threads in the pool. The sequence of events is: main ---------------------- spawn threads loop { lock thread mutex wait for packet unlock mutex send signal to thread } threads ---------------------- loop { wait for signal do RADIUS crap } The mutex in question is the same one as used by pthread_cond_wait. The problem is that I have to wake up the same thread /twice/ before it answers a request (IOW, pthread_cond_signal is called twice before the thread wakes up and `does RADIUS crap'). I haven't been able to reproduce this in something that isn't so complicated (but I can give the full source to anyone who's interested), but I was hoping someone might be able to tell me off-the-bat if it's a known problem in some instances (or that it's a problem at all). If not, I'll see what I can do to make the test simpler. -- Brian Cully ``And when one of our comrades was taken prisoner, blindfolded, hung upside-down, shot, and burned, we thought to ourselves, `These are the best experiences of our lives''' -Pathology (Joe Frank, Somewhere Out There) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 15:57:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09341 for freebsd-current-outgoing; Wed, 5 Aug 1998 15:57:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09326 for ; Wed, 5 Aug 1998 15:57:43 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id JAA28909; Thu, 6 Aug 1998 09:02:19 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808052302.JAA28909@cimlogic.com.au> Subject: Re: Pthreads woes In-Reply-To: <19980805180913.10635@kublai.com> from Brian Cully at "Aug 5, 98 06:09:13 pm" To: shmit@kublai.com Date: Thu, 6 Aug 1998 09:02:19 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Cully wrote: > I'm working on a program that spawns a bunch of threads in a pool, each > of which sits on a condition variable. The main thread waits for > a RADIUS request on a socket, it signals the condition variable on one > of the threads in the pool. > > The sequence of events is: > > main > ---------------------- > spawn threads > loop { > lock thread mutex > wait for packet > unlock mutex You keep the mutex locked while you wait? > send signal to thread Signal a condition or a kill() signal? > } > > threads > ---------------------- > loop { > wait for signal > do RADIUS crap > } > > The mutex in question is the same one as used by pthread_cond_wait. > > The problem is that I have to wake up the same thread /twice/ before > it answers a request (IOW, pthread_cond_signal is called twice before > the thread wakes up and `does RADIUS crap'). > > I haven't been able to reproduce this in something that isn't so > complicated (but I can give the full source to anyone who's interested), > but I was hoping someone might be able to tell me off-the-bat if it's > a known problem in some instances (or that it's a problem at all). I do this all the time. In fact I stopped working on such an application to answer your message. > > If not, I'll see what I can do to make the test simpler. Does the code build cleanly (gcc -Wall) on -current, without using a GNU configure script, and is it C code (not C++)? If yes, yes and yes, I'll look at it. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 16:00:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10065 for freebsd-current-outgoing; Wed, 5 Aug 1998 16:00:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell.fcc.net (shell.fcc.net [207.198.253.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09978 for ; Wed, 5 Aug 1998 15:59:51 -0700 (PDT) (envelope-from nathan@shell.fcc.net) Received: (from nathan@localhost) by shell.fcc.net (8.8.8/8.8.8) id SAA00825; Wed, 5 Aug 1998 18:59:38 -0400 (EDT) (envelope-from nathan) Message-ID: <19980805185938.A820@fcc.net> Date: Wed, 5 Aug 1998 18:59:38 -0400 From: Nathan Dorfman To: current@FreeBSD.ORG Subject: buildworld dies on doscmd.kernel Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cvsup of just a few minutes ago: attempting to build world results in: ld -N -Bstatic -T 110000 -o doscmd.kernel crt0.o AsyncIO.o ParseBuffer.o bios.o callback.o cpu.o dos.o cmos.o config.o cwd.o debug.o disktab.o doscmd.o ems.o emuint.o exe.o i386-pinsn.o int.o int10.o int13.o int14.o int16.o int17.o int1a.o int2f.o intff.o mem.o mouse.o net.o port.o setver.o signal.o timer.o trace.o trap.o tty.o xms.o -L/usr/X11R6/lib -lX11 -L/usr/lib/aout -lgcc -lc doscmd.o: Undefined symbol `_i386_vm86' referenced from text segment doscmd.o: Undefined symbol `_i386_set_ioperm' referenced from text segment *** Error code 1 Stop. cd /usr/src/usr.bin/doscmd && make for the same exact result. Apologies if I'm reporting something known. What does it want to compile right? -- Nathan Dorfman | E-mail: nathan@fcc.net Frontline Communications | Front desk: 914-623-8553: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 16:44:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17335 for freebsd-current-outgoing; Wed, 5 Aug 1998 16:44:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17314 for ; Wed, 5 Aug 1998 16:44:14 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA23122; Wed, 5 Aug 1998 16:41:09 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdV23117; Wed Aug 5 23:41:03 1998 Date: Wed, 5 Aug 1998 16:40:59 -0700 (PDT) From: Julian Elischer To: current@FreeBSD.ORG cc: Kelly Yancey Subject: syscons update Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG here is the outcome from the discussion on this in 93 I seem to remember it stalled at this point. contributors at that time were: dawes@physics.su.OZ.AU Holger.Veit@gmd.de. terry@icarus.weber.edu mycroft@gnu.ai.mit.edu bsdealwi@undergrad.math.uwaterloo.ca ache@astral.msk.su hm@hcshh.hcs.de rgrimes@cdrom.com joerg_wunsch@uriah.sax.de sos@kmd-ac.dk vak@zebub.msk.su kojima@kuis.kyoto-u.ac.jp ukai@kuamp.kyoto-u.ac.jp rich@lamprey.utmb.edu --------------------------------------------- BASIC CONSOLE ARCHITECTURE: $Date: 93/07/30 23:42:04 $ $Revision: 1.6 $ Foreword: The basic model that I propose has drawn heavily from the comments by all the members of the group. I have decided that I will use some concepts from Object Oriented techniques in this, defining a number of "classes" that can be loaded at will, or in the absense of loadable modules, could be compiled in. ----------------------------------------------------------------------- Definitions: A CLASS defines a set of INSTANCES that have the same external interfaces, e.g. all terminal emulators must have the same interface. Two terminal emulators, (e.g. vt10 and wyse60) must have the same interface, however they have different code associated with them. They are still of the same CLASS. A DERIVED CLASS is the set of all INSTANCES that are both in the same class and also have the same code associated with them. (e.g. the set of all INSTANCES with the terminal emulator interface and running the vt100 code) The DERIVED CLASS supplies a table of methods, referenced by the INSTANCES of that DERIVED CLASS An INSTANCE is a specific instance of a CLASS and DERIVED CLASS, that contains it's own STATE. There is no state held in a CLASS or DERIVED CLASS. An INSTANCE is based around a structure which is defined by the CLASS, and which has a pointer to a table of pointers to methods (supplied by a particular DERIVED CLASS) and values, (defined in meaning by the CLASS, but representative of state for that INSTANCE only).. The structure defined for the INSTANCE by the CLASS has also a (void *) pointer to a structure that is only defined for each DERIVED CLASS and which code external to the DERIVED CLASS cannot interpret. This structure is used to hold the PRIVATE STATE of the INSTANCE, and can only be interretted by the METHODS supplied by that DERIVED CLASS. Each DERIVED CLASS supplies a single init routine, which when run will link the DERIVED CLASS into any needed global structures. e.g. "List of available terminal emulators". It also supplies a CONSTRUCTOR routine that when called (from the list above) will produce an INSTANCE of the required DERIVED CLASS. I imagine the list being of the form: (for example); TEs----->[name ]-->"vt100" /-->[name ]-->"wyse50" [constructor ]-->0xFE200016 | [constructor ]-->0xFE201542 [next ]----------------/ [next ]-->0 The various INSTANCES include both private data, private methods, public data and public methods. All DERIVED CLASSES put themselves into ASCII identified lists, so that a list of available (loaded) TE DERIVED CLASSES may look like, "vt100","adm3a","wyse60". VC's inherit all their INSTANCE DERIVED CLASSES from the base VC (or possibly the VC running at the time of creation), but can substitute an INSTANCE which is a member of a different DERIVED CLASS. e.g. replace an adm3a with a vt100. Whether the VC INSTANCE actually exists for each VC or is 'virtual' depends on whether we want a special body of code to call the other modules (INSTANCES) or whether they call each other, so that no explicitly written VC layer exists. In either case a VC STRUCTURE certainly exists for each VC. Each INSTANCE in the console system contains a backpointer to the VC structure with which it is associated, to allow it to identify state from the VC and also find other INSTANCES associated with that VC. It may be that the central VC code calls methods from each INSTANCE PLUS they might call methods from each other, (e.g. the VS 'refresh' method might call the renderer's methods directly in order to refresh the screen to the state it requires. The classes I have defined (so far) are: Terminal_emulator All terminal emulators are members of this class, though differnt VCs may use different instantiations of the same emulator DERIVED CLASS they may use differnt DERIVED CLASSES (e.g. a vt100 or a adm31a DERIVED CLASS of the TE class). i.e. they have the same public interfaces. The TE only talks to the VS (virtual screen) code when 'rendering'. The VS methods pass these calls on to the actual RENDERER methods only if that VC is actually ON-SCREEN. While this implies that a person COULD change TEs on the fly, it's more intended that a new VC could be created using a different TE to the TE that was running when it ws created. (a 3274 TE and a normal TE on differnt VC's). Changing TE's on the fly would require very careful state management and would probably not work (in initial versions, at least though I don't see this as being a needed feature). The state of each TE is internally held and considered private in scope. virt_screen The virt_screen CLASS defines a set of methods that the external world (e.g. the TE) can use to draw on the screen. It draws however on a 'virtual screen' regardless of what hardware is present and whether that VC is presently being shown on the real screen. When that VC is selected for display, it uses it's internal virtual screen to refresh the real screen, using the renderer methods form the VC's renderer INSTANCE. Requests to the methods that arrive while it is "on screen" are passed down to the annalogous renderer method. because virt_screen and renderer classes are so closely related they might even both be implimented as DERIVED CLASSES of the same RENDERER CLASS. (e.g. if VC's were not being supported, the renderer INSTANCE might be placed into the VS slot?). The virt_screen INSTANCE can store it's virtual screen in any way it likes, as that's private to the DERIVED CLASS, however, it will be handed characters in the 'internal' character set. I can imagine needing upto 32 bits per character position. (including attributes). The VS has NO IDEA what the characters look like. It has only the SYMBOLS. It is possible the the TE should hold the VS map and should redraw the screen through calls directly to the renderer when asked by the refresh() entrypoint. In that scenario there would be no VS objects. renderer The renderer supplies methods similar to the virtual screen, however they result in changes on the physical display. The VS INSTANCE talks to the renderer, and might instruct it to refresh the entire display or just write a single character and attribute to a fixed place. The renderer is hardware specific and could alternatively be called the "frame-buffer" driver, or "display driver". Terry points out that a hard-copy renderer might be of interest to allow screen dumps etc. The renderer might work in graphics mode, but the virtual screen INSTANCES and renderer methods are basically character oriented, using whatever means it can to render the internal character set elements, using information taken from the 'FONT' INSTANCE associated with that VC. It has also been pointed out that there could be such a thing as a 'serial line terminal' renderer. 8-) exter_intern_mapper For each external coding used by the user, there is a different DERIVED CLASS. The default DERIVED CLASS would simply deliver the bottom 8 bits of the internal representation the user and visa versa. (if we decide to use unicode as the internal representation then the default 8-bit code presented to the user would be ISO 8859-1). A VC that was using a JIS 208/212 external mapping would use an INSTANCE that did the appropriate (more complex) mapping. (Assuming that one was loaded). Keyboard_mapper Different DERIVED CLASSES would be used to map different national keyboards. The keyboard INSTANCE for each VT may be of different keyboard DERIVED CLASSES. NOTE: this is not the keyboard driver, which is responsible for handling different types of keyboards. There are two levels of keyboard handling. One of them knows what scancodes respond to what keys and produces a standard scancode set..(PS2?) and the other knows what internal code should be generated from each of those scancodes, for the language(s) presently being used.(and taking account of language 'SHIFT' effects). The present X interface would not use this INSTANCE, except when loading the default map. (I know this is not what Terry wants, but It fits in better with what X needs at the moment) Font A Font INSTANCE can return font information for any internally represented character, as well as information about the font. (including 'not supported.. use "BLOB"') This includes font size, ligature information etc. The font INSTANCE is used almost exclusively by the renderer, to impliment requests from the VS. It also has an interaction with the mode control code. There would probably be a method associated with enabling the rendering agent to efficiently and quickly load fonts into hardware. I can imagine a font INSTANCE that returns a particular version of a character depending on the surrounding characters.. e.g. arabic or indian linking of word-parts. This would be of little use for character based hardware, however graphics based hardware could make use of this in non-western languages. Other modules that could be defined in object form (but not neccesarily) include the VC control module and the Keyboard driver itself, though one might not necessarily want multiple instances of either. the overall picture looks as follows: (This is the connection and flow for a Single VC, another VC would talk to other instances of the 'CLASSES'). +-----------------------------------------+ | | TTY IN | | other | TTY OUT | | RAW | I/F |VC I/F |RAW I/F| I/F | | KBD | | | | | | I/F |----^----|-------|-------|---v-----| | | INT/EXT | | EXT/INT | | | CONV | | CONV | | < (int/ext| |(int/ext | | | object) | VC CODE | object)| | |----^----| |---v-----| | | | | | | | TE IN | | TE OUT | | | ( TE | | ( TE | | | object) | | object) | | |----^----| +------|---v-----| | | | | Font | | | < KBD MAP | |(Font | VS CODE | <-- The VS may become | |(kbd obj)| | obj) | | part of the TE |--^-------^-------^--^v----v------^v-----| | Keyboard driver | Renderer | | | and Mode control | | | | +-----------------------------------------+ The TE ,TTY, and EXT/INT modules are shown as separate in and out modules, however they would be in fact not split. That's just for clarity. Each VC has pointers to the following tables/INSTANCES in it's local table: font INSTANCE ext/int INSTANCE keyboard obj TE obj VS storage pointer (an INSTANCE?) renderer private info.(an INSTANCE?) TTY interface to use. The VS code you are probably wondering about is the Virtual Screen. each VC has a VS associated with which it talks in character oriented primatives. (at least the basic version would). If the VC is presently on screen, these calls are passed on to the renderer, otherwise, only the VS is updated. The VS is used to update the screen when a VC is 'exposed'. The VS code is not likely to need differnt versions of itself co-existing, so it is unlikely that it need be implimented as an 'object'. the same goes for the VC code. It may be worthwhile considering the VS code as an object, just so we get the encapsulation and to make it similar to the other modules. Possibly an enhansed VS could be written to support graphics actions. The present state of the art regarding X servers requires some support in the renderer, for Process notification on VC switch, but I don't think that the raw graphics interfaces can be expected to go through the VS layer. This would be a good 'project' for someone, and we should not consider that it will never happen. While the inclusion from the start of VCs may seem to over-specify, I feel that this is a feature that must be built in from the start. If it were not, then it would be very hard to retro-fit 'per VC' instances of each of the INSTANCES. All INSTANCES would be dynamically allocated, and the act of loading a new module and running it's "init" routine would be the equivalent of definign a new available DERIVED CLASS. By this I mean, the 'struct' is dynamically allocated. (public and private parts) The code will have to be either loaded using terry's stuff or compiled in. This need not be large or cumbersome. Properly coded in C this approach should lead to highly separatable and replacable modules, without much speed penalty. I see the implimentation being in C rather than C++ though this is more for non technical reasons. I briefly outline below some first sketches of the implimentation. -------------------------------------------------------------------- Preliminary example: Each 'INSTANCE' is based around a structure that is always the same. It has a pointer to the DERIVED CLASS (including methods), and a pointer to the PRIVATE STATE data. It also has a pointer to the VC with which it is associated. Control is passed around between the INSTANCES and the VC code so as to achieve the desired result. (and between the INSTANCES) All methods have as their first argument, the address of the INSTANCE they were called from ('this' in C++). Below is a quick sketch of how they would look. they are not complete, and the methods and variables needed for each INSTANCE are open to discussion. Each INSTANCE has a few items in common. A pointer back to the VC of which it is a part. A pointer (type void*) to that INSTANCE's private data (that could be differently defined for different DERIVED CLASSES (e.g. vt100 would keep different private data to wy50). A pointer to the DERIVED CLASS's methods. Each DERIVED CLASS in turn has: A name pointer (e.g. "vt100" or "ISO-8859-1") A pointer to a 'delete operation to delete all the resources used by this INSTANCE if that VC is destroyed, (or an alternate INSTANCE is swapped in) As well as these there are entry points to methods to allow the INSTANCE to do it's work. typedef long int externalchar; typedef long int internalchar; typedef long int attributes; typedef unsigned char scancode; /* short? */ typedef int status; /* Each VC has one of these that identifies each INSTANCE that makes it up */ struct virt_cons { struct virt_cons *next; struct c_baseobj *ext_int; struct c_baseobj *term; struct c_baseobj *kbd_map struct c_baseobj *font; struct c_baseobj *vs; struct c_baseobj *renderer; }; All the INSTANCES point to DERIVED CLASSES ALL the DERIVED CLASS structures contain the following information: These are the STANDARD ENTRIES and in C++ would be inherrited from the BASE CLASS char *name; status (print*)(struct c_baseobj *); /* print out an instance */ status (delete*)(struct c_baseobj *); /* delete an instance */ status (create*)(struct c_baseobj **); /* delete an instance */ as well as specialist methods (shown below) /* * the central struct for the translation module that translates the * internal code to whatever charater set the user wants to recieve data in. * Defines methods to translate incoming and outgoing data. */ struct extern_intern /* may need changing to suport multi-length codes */ { STANDARD ENTRIES plus: internalchar (fromuser*)(struct extern_intern *,externalchar); externalchar (fromte*)(struct extern_intern *,internalchar); }; /* * Methods and data for the terminal emulator, including: * a method to call with data from the user, * a method to call with data from the keyboard, */ struct term_emul { STANDARD ENTRIES plus: status (fromuser*)(struct term_emul *,internalchar); status (fromkbd*)(struct term_emul *,internalchar); }; /* * Methods and data for an object that translates scancode type data * from the keyboard, into internalchar form. * (Handles shift, meta, cntrl, alt etc.) */ struct kbd_map { STANDARD ENTRIES plus: internalchar (fromkbd*)(struct kbd_map *,scancode); }; /* * Methods and data for a particular font, * Including methods that return a pointer to a bitmap given an internalchar, * or given a font position, returns the internalchar it represents. */ struct font_type { STANDARD ENTRIES plus: int (mapchar*)(struct font_type *,internalchar); status (mapglyph*(struct font_type *,int,internalchar *); int height,width,number;/* what if 'variable' sized? */ }; /* * Methods and data for the hardware independent virtual screens */ struct virt_screen { STANDARD ENTRIES plus: status (drawchar*)(struct virt_screen *,internalchar, attributes,int,int); status (drawmany*)(struct virt_screen *,internalchar *, attributes *,int x,int y,int n); status (setsize*)(struct virt_screen *,int x,int y); /* x,y */ internalchar (returnchar)(struct virt_screen *,int x,int y,attribute *); /* the scrolls start at the {row/column} in the 2nd arg */ status (scrollup*)(struct virt_screen *,int); status (scrolldown*)(struct virt_screen *,int); status (scrollleft*)(struct virt_screen *,int); status (scrollright*)(struct virt_screen *,int); status (refresh*)(struct virt_screen *); /* tell VS */ /* to redraw entire screen, using renderer commands*/ }; /* * Methods and data for the hardware specific 'driver' */ struct renderer { STANDARD ENTRIES plus: status (drawchar*)(struct renderer *, internalchar, attributes,int x,int y); status (drawmany*)(struct renderer *, internalchar *, attributes *,int x,int y,int n); /* the scrolls start at the {row/column} in the 2nd arg */ status (scrollup*)(struct renderer *,int); status (scrolldown*)(struct renderer *,int); status (scrollleft*)(struct renderer *,int); status (scrollright*)(struct renderer *,int); status (setmode*)(struct renderer *);/* on VC switch to us */ char *modename; /* e.g. "80x25x9x15" or "640x480x256"*/ status (setnewmode*)(struct renderer *,mode); char *(listmodes*)(struct renderer *); status (addmode*)(struct renderer *,script); status (loadfont*)(struct renderer *); }; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 19:18:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08175 for freebsd-current-outgoing; Wed, 5 Aug 1998 19:18:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08050 for ; Wed, 5 Aug 1998 19:18:02 -0700 (PDT) (envelope-from reilly@zeta.org.au) Received: from zeta.org.au (d14.syd2.zeta.org.au [203.26.11.14]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id MAA10190 for ; Thu, 6 Aug 1998 12:17:45 +1000 Received: (qmail 4321 invoked by uid 1000); 6 Aug 1998 01:29:55 -0000 From: "Andrew Reilly" Message-ID: <19980806112955.A4299@reilly.home> Date: Thu, 6 Aug 1998 11:29:55 +1000 To: Terry Lambert , Tom Cc: current@FreeBSD.ORG Subject: Re: Heads up on LFS References: <199808050751.AAA21008@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808050751.AAA21008@usr02.primenet.com>; from Terry Lambert on Wed, Aug 05, 1998 at 07:51:42AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 05, 1998 at 07:51:42AM +0000, Terry Lambert wrote: > > What is SpinOS? Are you sure it is BSD LFS, or is there own LFS? > > An exokernel OS. > It's written in > Modula 3 (of all things) and incorporates nullfs and lfs from FreeBSD, > as well as CAM. I don't think that "of all things" is particularly fair: their reasoning for the entire viability of the project is that they rely on the strict typing and garbage collection of Modula-3 to prevent user-written kernel extensions from breaking other kernel bits. You couldn't really do it in C or even C++. The same logic is used by the Sun JavaOS folks (Java being Modula-3 in C clothes, that's hardly surprising.) The argument is interesting, but a bit too restrictive to be useful in a general purpose sense, I think. Now if you were prepared to rely on hardware memory /protection/ without using the hardware memory /mapping/, you could probably do the same thing in C or C++ (or assembly language). I believe that this has been tried in some of the Acorn ARM based OS's (RiscOS and the Newton OS.) -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 20:16:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14605 for freebsd-current-outgoing; Wed, 5 Aug 1998 20:16:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14600 for ; Wed, 5 Aug 1998 20:16:36 -0700 (PDT) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.9.1/kong/0.01) with ESMTP id HAA02220 for ; Thu, 6 Aug 1998 07:16:16 +0400 (MSD) (envelope-from kong@kong.dorms.spbu.ru) Date: Thu, 6 Aug 1998 07:16:16 +0400 (MSD) From: Hostas Red To: current@FreeBSD.ORG Subject: Still having big problems with 'w' Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Still having problems with idletimes, and not only them. It seems, that 'w/who/finger' is completely broken: kong@kong:~> w w: /dev//kong: No such file or directory 7:11 up 2:35, 3 users, load averages: 0.15, 0.07, 0.08 USER TTY FROM LOGIN@ IDLE WHAT kong v7 - 4:36 2:35 xinit /home/kong/.xini ttyp3 :0.0 7:09 2:34 - kong p4 - 01ÑÎ×70 2:35 -bash (bash) kong@kong:~> who kong ttyv7 6 Á×Ç 04:36 kong ttyp4 1 ÑÎ× 03:00 :0.0 kong 1 ÑÎ× 03:00 (ë#É5ttyp6) And such kind if things. It shows only 1-2-3 open sessions, but at present time i have at least 8 pty's open and 1 vty (this is correct). It seems that there is big problems with utmp/wtmp stuff. Any ideas? Adios, /KONG PS: I do not have 'noatime' mounts. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 20:27:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15939 for freebsd-current-outgoing; Wed, 5 Aug 1998 20:27:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA15932 for ; Wed, 5 Aug 1998 20:27:00 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z4GhH-0006Mc-00; Wed, 5 Aug 1998 20:26:35 -0700 Date: Wed, 5 Aug 1998 20:26:32 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Andrew Reilly cc: current@FreeBSD.ORG Subject: Re: Heads up on LFS In-Reply-To: <19980806112955.A4299@reilly.home> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Aug 1998, Andrew Reilly wrote: ... > Now if you were prepared to rely on hardware memory /protection/ > without using the hardware memory /mapping/, you could probably > do the same thing in C or C++ (or assembly language). I believe > that this has been tried in some of the Acorn ARM based OS's > (RiscOS and the Newton OS.) Most microkernel OSes are this way. QNX for x86 does something similar. The kernel is basically just a scheduler (a QNX kernel is less than 50K), and all other services that would normally be in the kernel are in their own address spaces, using strict IPC interfaces between modules. > -- > Andrew Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 20:35:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17031 for freebsd-current-outgoing; Wed, 5 Aug 1998 20:35:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17023 for ; Wed, 5 Aug 1998 20:35:08 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id NAA25420; Thu, 6 Aug 1998 13:04:34 +0930 (CST) Message-Id: <199808060334.NAA25420@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Hostas Red cc: current@FreeBSD.ORG Subject: Re: Still having big problems with 'w' In-reply-to: Your message of "Thu, 06 Aug 1998 07:16:16 +0400." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Thu, 06 Aug 1998 13:04:33 +0930 From: "Daniel O'Connor" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id UAA17027 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And such kind if things. It shows only 1-2-3 open sessions, but at present > time i have at least 8 pty's open and 1 vty (this is correct). Hmm.. well you may have an old version of xterm (or rxvt) which is screwing up the entries.. --------------------------------------------------------------------- |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 | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 20:39:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17832 for freebsd-current-outgoing; Wed, 5 Aug 1998 20:39:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17819 for ; Wed, 5 Aug 1998 20:39:05 -0700 (PDT) (envelope-from reilly@zeta.org.au) Received: from zeta.org.au (d7.syd2.zeta.org.au [203.26.11.7]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id NAA16270 for ; Thu, 6 Aug 1998 13:38:46 +1000 Received: (qmail 5014 invoked by uid 1000); 6 Aug 1998 03:36:31 -0000 Message-ID: <19980806033631.5013.qmail@gurney.reilly.home> From: "Andrew Reilly" Date: Thu, 6 Aug 1998 13:36:31 +1000 (EST) Subject: Re: Heads up on LFS To: tom@uniserve.com cc: reilly@zeta.org.au, current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom said: > > On Thu, 6 Aug 1998, Andrew Reilly wrote: > > ... >> Now if you were prepared to rely on hardware memory /protection/ >> without using the hardware memory /mapping/, you could probably >> do the same thing in C or C++ (or assembly language). I believe >> that this has been tried in some of the Acorn ARM based OS's >> (RiscOS and the Newton OS.) > > Most microkernel OSes are this way. QNX for x86 does something similar. > The kernel is basically just a scheduler (a QNX kernel is less than 50K), > and all other services that would normally be in the kernel are in their > own address spaces, using strict IPC interfaces between modules. That's not quite what I meant. As far as I know, the Spin and JavaOS beasties get an extra performance bennefit from running both the kernel and all user processes in the _same_ address space, without any hardware protections. They can do that safely, because they push the protection and access issues into the language and the compiler, rather than guarding for errant programs at run-time. NewtonOS and RiscOS also put everything into the one address space, but use some hardware memory _protection_ to prevent user processes from reading or writing into kernel (or other user process) space, unless explicitly allowed, by calling a kernel routine. QNX is much more like Unix, in that all processes have a separate address space of their own. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 21:08:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21243 for freebsd-current-outgoing; Wed, 5 Aug 1998 21:08:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21238 for ; Wed, 5 Aug 1998 21:08:43 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from rigel (pm3-pt2.pcnet.net [206.105.29.76]) by pcnet1.pcnet.com (8.8.7/PCNet) with SMTP id AAA05129; Thu, 6 Aug 1998 00:09:04 -0400 (EDT) Message-ID: <35C8F3D4.167EB0E7@vigrid.com> Date: Wed, 05 Aug 1998 20:07:48 -0400 From: "Daniel M. Eischen" X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: shmit@kublai.com CC: current@FreeBSD.ORG Subject: Re: Pthreads woes Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having similar problems with the tasking runtime of the last customer release of GNAT (Ada). The GNAT runtime, when an application uses tasking services, creates a couple of threads (timer_server and interrupt_manager). Each Ada task is its own thread. Each task also has its own mutex and CV pair which are used for timed delays and event notification. The problem occurs when trying to do a timed delay. The sequence of events for a timed delay is very similar to what you show: lock thread_mutex wait for signal (cond_signal) unlock thread_mutex I'm in the process of debugging the problem, but it seems that a SIGBUS or SIGSEGV is being generated when the thread is signaled. The thread being awoken is receiving the (UNIX) signal, not the signaling (cond_signal) thread. Ada handles SIGBUS/SIGSEGV as Storage_Error exceptions, which is what the GNAT runtime is seeing. It could be a pointer out of whack in the threads library, perhaps in the process of queueing and dequeueing threads waiting on CVs and mutexes. The code looks correct though. I've added some _thread_sys_write statements to the mutex and CV routines, but haven't found the problem. I've modified uthread_cond_timedwait as follows: /* Unlock the condition variable structure: */ _SPINUNLOCK(&(*cond)->lock); sprintf (s, "pthread_cond_timedwait, waiting..."); _uthread_sys_write (2, s, strlen (s)); /* Schedule the next thread: */ _thread_kern_sched_state(PS_COND_WAIT, __FILE__, __LINE__); sprintf (s, "pthread_cond_timedwait, awoken"); _uthread_sys_write (2, s, strlen (s)); /* Lock the condition variable structure: */ _SPINLOCK(&(*cond)->lock); The thread (Ada task) calling this successfully goes to sleep - you can see the "waiting..." mesage. You can even see the mutex (as passed in to pthread_cond_timedwait()) being released and taken by another thread. But when the sleeping thread is signaled (via cond_signal), a SIGBUS or SIGSEGV is generated which gets sent to the sleeping thread. The "awoken" message is never displayed. I'm using 3.0-current as of 5 days ago. Using a libc_r from a -current before the April spinlock/signal changes works. I've tried creating a simple C program to duplicate the problems, but can't reproduce it. Normally, I'd spend some more time trying to debug the problem before reporting it, but as long as someone else is having problems also... > I'm working on a program that spawns a bunch of threads in a pool, each > of which sits on a condition variable. The main thread waits for > a RADIUS request on a socket, it signals the condition variable on one > of the threads in the pool. > > The sequence of events is: > > main > ---------------------- > spawn threads > loop { > lock thread mutex > wait for packet > unlock mutex > send signal to thread > } > > threads > ---------------------- > loop { > wait for signal > do RADIUS crap > } > > The mutex in question is the same one as used by pthread_cond_wait. > > The problem is that I have to wake up the same thread /twice/ before > it answers a request (IOW, pthread_cond_signal is called twice before > the thread wakes up and `does RADIUS crap'). > > I haven't been able to reproduce this in something that isn't so > complicated (but I can give the full source to anyone who's interested), > but I was hoping someone might be able to tell me off-the-bat if it's > a known problem in some instances (or that it's a problem at all). > > If not, I'll see what I can do to make the test simpler. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 21:09:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21320 for freebsd-current-outgoing; Wed, 5 Aug 1998 21:09:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21301 for ; Wed, 5 Aug 1998 21:09:04 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id AAA08507; Thu, 6 Aug 1998 00:08:48 -0400 (EDT) (envelope-from luoqi) Date: Thu, 6 Aug 1998 00:08:48 -0400 (EDT) From: Luoqi Chen Message-Id: <199808060408.AAA08507@lor.watermarkgroup.com> To: current@FreeBSD.ORG, kong@kong.spb.ru Subject: Re: Still having big problems with 'w' Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You must be using DEVFS. I had the same problem. Try the following patch, it's a little simplistic, but it stopped my girlfriend from complaining that I was trying to hide something from her :( -lq Index: devfs_vnops.c =================================================================== RCS file: /fun/cvs/src/sys/miscfs/devfs/devfs_vnops.c,v retrieving revision 1.58 diff -u -r1.58 devfs_vnops.c --- devfs_vnops.c 1998/07/30 17:40:44 1.58 +++ devfs_vnops.c 1998/08/04 14:26:37 @@ -1403,6 +1403,8 @@ if (uio->uio_resid == 0) return (0); + getnanotime(&(dnp->atime)); + switch (vp->v_type) { case VCHR: @@ -1495,6 +1497,8 @@ if (uio->uio_segflg == UIO_USERSPACE && uio->uio_procp != curproc) panic("devfs_write proc"); #endif + + getnanotime(&(dnp->mtime)); switch (vp->v_type) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 21:25:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA23157 for freebsd-current-outgoing; Wed, 5 Aug 1998 21:25:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from wpaul@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA23145; Wed, 5 Aug 1998 21:25:15 -0700 (PDT) (envelope-from wpaul) From: Bill Paul Message-Id: <199808060425.VAA23145@hub.freebsd.org> Subject: Re: Etherlink XL driver In-Reply-To: from Alfred Perlstein at "Aug 5, 98 10:04:27 am" To: bright@hotjobs.com (Alfred Perlstein) Date: Wed, 5 Aug 1998 21:25:15 -0700 (PDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > using the first version of the driver posted on 100mb segement seemed to > have not great performance. The admin here said he was able to get > ~8megs/sec over the segment using Linux and 11megs/sec via Solaris, the > FreeBSD driver was never over 4.5megs and averaged around 3-3.5. This is > ftp transfers. It seems to grab a LOT of data, then "stall" then grab, > stall over and over. Can you describe the system in which the card is installed? What kind of processor and how fast is it? > I know this is an older driver, i'll compile him a new kernel with the > latest snapshot to see if there is an improvement. Just thought to let > you know. > > This is on a -current box with a PCI card 905b on 100/TX. The driver was > acting in full duplex mode, perhaps it should have been set to half-duplex > and it was tripping on itself? The depends. Both sides of the link must match. If the hub (or switch; you don't say which you're using) is in half-duplex mode, then the card should also be in half-duplex mode. What happens is that the PHY (in this case, the built-in autoneg logic on the 3Com chip) may negotiate a full-duplex link with the link partner, but then the driver has to look at the state of the link and set the 'fullduplex' bit in the MacControl register to match. If the physical layer negotiates a full-duplex connection but the controller chip stays in half-duplex, you get 'stuttery' performance, especially with TCP. Make absolutely sure the 3Com and the hub/switch are operating in the same mode. Use 'ifconfig xl0 media 100baseTX mediaopt full-duplex' to force a full-duplex link, or 'mediaopt half-duplex to force a half-duplex link. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 21:34:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA23928 for freebsd-current-outgoing; Wed, 5 Aug 1998 21:34:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA23923 for ; Wed, 5 Aug 1998 21:34:14 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id VAA22007; Wed, 5 Aug 1998 21:33:55 -0700 (PDT) (envelope-from jdp) Message-Id: <199808060433.VAA22007@austin.polstra.com> To: garnett@bogus.cs.colorado.edu Subject: Re: Heads up on LFS In-Reply-To: <199808051941.NAA10755@bogus.cs.colorado.edu> References: <199808051941.NAA10755@bogus.cs.colorado.edu> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Wed, 05 Aug 1998 21:33:55 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > According to the Spin SMP page, the FreeBSD code used is from 2.1.7 > > They plan to update to 3.0 to get SMP running though. > > It's not clear how alive SPIN really is anymore; it would be surprising if > they actually did this. In the OS research community the word is that it > is "Spun Down" or anything along similiar lines; work could be tailing off > on it, although you'd have to ask Brian Bershad to be sure. That's the impression I've gotten too. At one point, they wanted me to do some SPIN-related work for them, "definitely." We scheduled it to begin about 3 months in the future, because of prior commitments I had. When the 3 months were up, I contacted them and said I was ready to start. Their reply was, oh ... hmmm ... well ... we're not doing too much in that area any more, and we don't need it after all. (That kind of thing is incredibly common in the consulting biz, by the way.) -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 22:00:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26945 for freebsd-current-outgoing; Wed, 5 Aug 1998 22:00:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA26917 for ; Wed, 5 Aug 1998 22:00:32 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z4I9c-0006JA-00; Wed, 5 Aug 1998 21:59:56 -0700 Date: Wed, 5 Aug 1998 21:59:52 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Andrew Reilly cc: current@FreeBSD.ORG Subject: Re: Heads up on LFS In-Reply-To: <19980806033631.5013.qmail@gurney.reilly.home> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Aug 1998, Andrew Reilly wrote: > Tom said: > > > > On Thu, 6 Aug 1998, Andrew Reilly wrote: > > > > ... > >> Now if you were prepared to rely on hardware memory /protection/ > >> without using the hardware memory /mapping/, you could probably > >> do the same thing in C or C++ (or assembly language). I believe > >> that this has been tried in some of the Acorn ARM based OS's > >> (RiscOS and the Newton OS.) > > > > Most microkernel OSes are this way. QNX for x86 does something similar. > > The kernel is basically just a scheduler (a QNX kernel is less than 50K), > > and all other services that would normally be in the kernel are in their > > own address spaces, using strict IPC interfaces between modules. > > That's not quite what I meant. As far as I know, the Spin and JavaOS > beasties get an extra performance bennefit from running both the kernel > and all user processes in the _same_ address space, without any > hardware protections. They can do that safely, because they push the > protection and access issues into the language and the compiler, rather > than guarding for errant programs at run-time. > > NewtonOS and RiscOS also put everything into the one address space, but > use some hardware memory _protection_ to prevent user processes from > reading or writing into kernel (or other user process) space, unless > explicitly allowed, by calling a kernel routine. Hardware memory protection is hardware memory protection, whether you get a separate address space or not. Just like x86 stuff that generates protection faults. > QNX is much more like Unix, in that all processes have a separate > address space of their own. Not quite. Even the network staff, and file system run in separate spaces. As far as I know, even device drivers have their own address space. That level of segregation is not available on any Unix I know of. > -- > Andrew > > > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 23:06:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05915 for freebsd-current-outgoing; Wed, 5 Aug 1998 23:06:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA05907 for ; Wed, 5 Aug 1998 23:06:42 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id XAA21869; Wed, 5 Aug 1998 23:06:27 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpd021836; Wed Aug 5 23:06:22 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id XAA22855; Wed, 5 Aug 1998 23:06:17 -0700 (MST) From: Terry Lambert Message-Id: <199808060606.XAA22855@usr09.primenet.com> Subject: Re: Heads up on LFS To: reilly@zeta.org.au (Andrew Reilly) Date: Thu, 6 Aug 1998 06:06:17 +0000 (GMT) Cc: tlambert@primenet.com, tom@uniserve.com, current@FreeBSD.ORG In-Reply-To: <19980806112955.A4299@reilly.home> from "Andrew Reilly" at Aug 6, 98 11:29:55 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It's written in > > Modula 3 (of all things) and incorporates nullfs and lfs from FreeBSD, > > as well as CAM. > > I don't think that "of all things" is particularly fair: their > reasoning for the entire viability of the project is that they rely > on the strict typing and garbage collection of Modula-3 to prevent > user-written kernel extensions from breaking other kernel bits. To each his own; the need for a garbage collector for things that the language should know were out of scope and therefore not need to garbage collect is an agrument against such languages, in my book. > You couldn't really do it in C or even C++. The same logic is used > by the Sun JavaOS folks (Java being Modula-3 in C clothes, that's > hardly surprising.) The argument is interesting, but a bit too > restrictive to be useful in a general purpose sense, I think. The same argument about no explicit object destruction is a good anti-JAVA argument, as well. As far as C++: I've implemented a large portion of the java and javax classes in C++, including the Exception and Throwable classes, as part of a project unrelated to JAVA (I just figured that I might as well not reinvent a model Sun spent millions of dollars inventing, and the model was based on these classes). So you can indeed write JAVA in C++; you just need to do the right thing as regards deletion when something goes out of scope. The Vector, Enumerator, and Iterator classes are particularly tricky... > Now if you were prepared to rely on hardware memory /protection/ > without using the hardware memory /mapping/, you could probably > do the same thing in C or C++ (or assembly language). I believe > that this has been tried in some of the Acorn ARM based OS's > (RiscOS and the Newton OS.) It's possible in C++, if you are willing to explicitly destruct objects when you know they are going out of scope but the compiler doesn't, especially if you are using them as pointers instead of references. JAVA has a nasty tendency to leak like a sieve until the GC hits a steady state. As does Modula 3. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 5 23:38:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10127 for freebsd-current-outgoing; Wed, 5 Aug 1998 23:38:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10111; Wed, 5 Aug 1998 23:38:28 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id IAA25976; Thu, 6 Aug 1998 08:37:13 +0200 (CEST) (envelope-from sos) Message-Id: <199808060637.IAA25976@sos.freebsd.dk> Subject: Re: Patch for Bt848 driver to detect new Hauppauge 404 Cards In-Reply-To: <35C89370.A1EB29F8@cs.strath.ac.uk> from Roger Hardiman at "Aug 5, 98 06:16:32 pm" To: roger@cs.strath.ac.uk (Roger Hardiman) Date: Thu, 6 Aug 1998 08:37:12 +0200 (CEST) Cc: current@FreeBSD.ORG, roger@cs.strath.ac.uk, multimedia@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Roger Hardiman who wrote: > Hi, > Please can someone commit this patch for the bt848 driver. > It allows the new Hauppauge WinCastTV 404 card with NTSC tuner to be > detected. > It also tidies up some of my earlier initialisation code Amancio > commited for me. I'll try it out here and if nobody beats me to it commit your changes... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 01:09:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21909 for freebsd-current-outgoing; Thu, 6 Aug 1998 01:09:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from esmeralda.xaa.iae.nl (esmeralda.xaa.iae.nl [194.151.75.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21894 for ; Thu, 6 Aug 1998 01:09:36 -0700 (PDT) (envelope-from freebsd@xaa.iae.nl) Received: from ariel.xaa.iae.nl (ariel.xaa.iae.nl [194.151.75.10]) by esmeralda.xaa.iae.nl (8.8.8/8.8.7) with ESMTP id KAA11000 for ; Thu, 6 Aug 1998 10:09:00 +0200 (MET DST) (envelope-from freebsd@xaa.iae.nl) Received: by ariel.xaa.iae.nl (VMailer, from userid 1008) id A6C5E4556; Thu, 6 Aug 1998 10:08:59 +0200 (CEST) Message-ID: <19980806100859.A312@xaa.iae.nl> Date: Thu, 6 Aug 1998 10:08:59 +0200 From: Mark Huizer To: freebsd-current@FreeBSD.ORG Subject: memory leaks in libc Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, a nice user of ours pointed me to the fact that various functions like setenv, putenv etc leak memory like crazy. To mention a very simple example: main(){while(1){setenv("A","AA",1);setenv("A","A",1);}} while consume all memory within short periods of time (see setenv.c for the reason). Is this wellknown? I think it is bad, and would like to fix it Mark -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 01:36:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24719 for freebsd-current-outgoing; Thu, 6 Aug 1998 01:36:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles231.castles.com [208.214.165.231]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24708 for ; Thu, 6 Aug 1998 01:36:15 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id BAA01491; Thu, 6 Aug 1998 01:35:04 -0700 (PDT) Message-Id: <199808060835.BAA01491@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mark Huizer cc: freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-reply-to: Your message of "Thu, 06 Aug 1998 10:08:59 +0200." <19980806100859.A312@xaa.iae.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Aug 1998 01:35:04 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, a nice user of ours pointed me to the fact that various functions > like setenv, putenv etc leak memory like crazy. To mention a very > simple example: > > main(){while(1){setenv("A","AA",1);setenv("A","A",1);}} > > while consume all memory within short periods of time (see setenv.c for > the reason). > > Is this wellknown? I think it is bad, and would like to fix it Not sure, agreed, and please do. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 01:58:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28072 for freebsd-current-outgoing; Thu, 6 Aug 1998 01:58:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28066 for ; Thu, 6 Aug 1998 01:58:13 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id JAA12636; Thu, 6 Aug 1998 09:57:54 +0100 (BST) Message-ID: <35C9702B.87B3ED7D@tdx.co.uk> Date: Thu, 06 Aug 1998 09:58:19 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.5b1 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Mark Huizer CC: freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc References: <19980806100859.A312@xaa.iae.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I think I've seen this conversation before... It came up a while ago... I think it is well know, and apparently very hard to fix... Somone did offer to fix it, but then declined once it was pointed out exactly how hard it would be to do... ;-) I think it has something to do with shared memory allocation between shell's - i.e. exported environment strings or something... No doubt someone who knows what there talking about will explain it in all it's gory details why it's not so easy to fix... ;-) Regards, Karl Mark Huizer wrote: > > Hi, a nice user of ours pointed me to the fact that various functions > like setenv, putenv etc leak memory like crazy. To mention a very > simple example: > > main(){while(1){setenv("A","AA",1);setenv("A","A",1);}} > > while consume all memory within short periods of time (see setenv.c for > the reason). > > Is this wellknown? I think it is bad, and would like to fix it > > Mark > -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 02:13:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29851 for freebsd-current-outgoing; Thu, 6 Aug 1998 02:13:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com ([208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA29837 for ; Thu, 6 Aug 1998 02:12:53 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-39.camalott.com [208.229.74.39]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id EAA06960; Thu, 6 Aug 1998 04:12:33 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id CAA13740; Thu, 6 Aug 1998 02:54:33 -0500 (CDT) (envelope-from joelh) Date: Thu, 6 Aug 1998 02:54:33 -0500 (CDT) Message-Id: <199808060754.CAA13740@detlev.UUCP> To: ben@rosengart.com CC: dacole@netcom.ca, current@FreeBSD.ORG In-reply-to: (message from Snob Art Genre on Tue, 4 Aug 1998 13:41:05 -0400 (EDT)) Subject: Re: booting with verbosity by default? From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I would like to force my systems to always boot with '-v'.. Is there >> any way to do this without operator intervention? > Take a look at what boot(8) has to say about /boot.config. It says that -v doesn't make the cut for boot.config. The fix is trivial, but I haven't yet rolled a pr. This suggestion hasn't been carefully considered or tested, but if you want to fix it yourself, then in /sys/i386/boot/biosboot/boot.c, move the bit about "loadflags &= (RB_DUAL | RB_SERIAL);" to right around "readfile("boot.config", ...);" about 40 lines up. (The key is that it should be before "getbootdev(boot_config, &loadflags);".) This will effectively allow any boot flags in. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 02:52:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05613 for freebsd-current-outgoing; Thu, 6 Aug 1998 02:52:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05608 for ; Thu, 6 Aug 1998 02:52:21 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id CAA26488; Thu, 6 Aug 1998 02:48:58 -0700 (PDT) Message-Id: <199808060948.CAA26488@implode.root.com> To: Mark Huizer cc: freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-reply-to: Your message of "Thu, 06 Aug 1998 10:08:59 +0200." <19980806100859.A312@xaa.iae.nl> From: David Greenman Reply-To: dg@root.com Date: Thu, 06 Aug 1998 02:48:58 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hi, a nice user of ours pointed me to the fact that various functions >like setenv, putenv etc leak memory like crazy. To mention a very >simple example: > >main(){while(1){setenv("A","AA",1);setenv("A","A",1);}} > >while consume all memory within short periods of time (see setenv.c for >the reason). > >Is this wellknown? I think it is bad, and would like to fix it The problem with fixing setenv() is that you don't know if a pointer was malloced, allocated from the env area above the stack, points to read-only text, points to a static data buffer, etc. There really is no way to know for sure, so you can't free the memory. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 04:10:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA16835 for freebsd-current-outgoing; Thu, 6 Aug 1998 04:10:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA16826 for ; Thu, 6 Aug 1998 04:10:40 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA13616; Thu, 6 Aug 1998 21:10:20 +1000 Date: Thu, 6 Aug 1998 21:10:20 +1000 From: Bruce Evans Message-Id: <199808061110.VAA13616@godzilla.zeta.org.au> To: dg@root.com, freebsd@xaa.iae.nl Subject: Re: memory leaks in libc Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem with fixing setenv() is that you don't know if a pointer was >malloced, allocated from the env area above the stack, points to read-only >text, points to a static data buffer, etc. There really is no way to know >for sure, so you can't free the memory. Yo can know if you malloced it in a previous call to putenv() or setenv(). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 04:31:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19297 for freebsd-current-outgoing; Thu, 6 Aug 1998 04:31:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vortex.starix.net (vortex.starix.net [208.219.83.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19288 for ; Thu, 6 Aug 1998 04:31:17 -0700 (PDT) (envelope-from syko@sykotik.org) Received: from localhost (syko@localhost) by vortex.starix.net (8.7.6/8.7.3) with SMTP id HAA07398; Thu, 6 Aug 1998 07:28:46 -0400 X-Authentication-Warning: vortex.starix.net: syko owned process doing -bs Date: Thu, 6 Aug 1998 07:28:46 -0400 (EDT) From: Dusk Auriel Sykotik X-Sender: syko@vortex.starix.net To: Hostas Red cc: current@FreeBSD.ORG Subject: Re: Still having big problems with 'w' In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id EAA19293 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Odd, one time on a 2.2.6 system I had who performing oddly in a similar manner with the ansi chars. It also sometimes showed "invalid hostname" as the user's hostname from which they were logged in. That seems to have corrected itself by no doing of mine however, and I didn't really have time to look into it myself. I don't know whether `w` was broken, since I never use it. /* * Matt Harris +++ Syko * BPSOFH, BIOFH, C, SQL, PERL +++ http://starix.technonet.net/~syko/ */ On Thu, 6 Aug 1998, Hostas Red wrote: > Hi! > > Still having problems with idletimes, and not only them. It seems, that > 'w/who/finger' is completely broken: > > kong@kong:~> w > w: /dev//kong: No such file or directory > 7:11 up 2:35, 3 users, load averages: 0.15, 0.07, 0.08 > USER TTY FROM LOGIN@ IDLE WHAT > kong v7 - 4:36 2:35 xinit /home/kong/.xini > ttyp3 :0.0 7:09 2:34 - > kong p4 - 01ÑÎ×70 2:35 -bash (bash) Best look at the source for those bins and see where its getting that information from. > > kong@kong:~> who > kong ttyv7 6 Á×Ç 04:36 > kong ttyp4 1 ÑÎ× 03:00 > :0.0 kong 1 ÑÎ× 03:00 (ë#É5ttyp6) > > And such kind if things. It shows only 1-2-3 open sessions, but at present > time i have at least 8 pty's open and 1 vty (this is correct). > > It seems that there is big problems with utmp/wtmp stuff. > > Any ideas? > > Adios, > /KONG > > PS: I do not have 'noatime' mounts. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 04:40:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA20229 for freebsd-current-outgoing; Thu, 6 Aug 1998 04:40:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Guard.PolyNet.Lviv.UA (Guard.PolyNet.Lviv.UA [194.44.138.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA20072 for ; Thu, 6 Aug 1998 04:39:54 -0700 (PDT) (envelope-from pam@polynet.lviv.ua) From: pam@polynet.lviv.ua Received: (qmail 4745 invoked by alias); 6 Aug 1998 11:39:32 -0000 Received: (qmail 4740 invoked from network); 6 Aug 1998 11:39:32 -0000 Received: from postoffice.polynet.lviv.ua (194.44.138.1) by guard.polynet.lviv.ua with SMTP; 6 Aug 1998 11:39:32 -0000 Received: (qmail 20522 invoked by uid 1001); 6 Aug 1998 11:39:31 -0000 Date: 6 Aug 1998 14:39:31 +0300 Message-ID: <19980806143931.A19551@LP.Lviv.UA> Date: Thu, 6 Aug 1998 14:39:31 +0300 To: current@FreeBSD.ORG Subject: Q: DEVFS/SLICE real life usage example Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi everybody! Can somebody post a real life example of FreeBSD configuration with DEVFS/SLICE? Can it be used to totally eliminate /dev (I mean to have empty /dev on root filesystem)? What does mean? (what is its purpose?): devfs 16 16 0 100% dummy_mount Thanks in advance, -- Adrian Pavlykevych email: System Administrator phone/fax: +380 (322) 742041 State University "Lvivska Polytechnica" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 05:26:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26429 for freebsd-current-outgoing; Thu, 6 Aug 1998 05:26:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA26424 for ; Thu, 6 Aug 1998 05:26:20 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id PAA24176; Thu, 6 Aug 1998 15:24:08 +0300 (EEST) Date: Thu, 6 Aug 1998 15:24:08 +0300 (EEST) From: Narvi To: Bruce Evans cc: dg@root.com, freebsd@xaa.iae.nl, freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-Reply-To: <199808061110.VAA13616@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Aug 1998, Bruce Evans wrote: > > The problem with fixing setenv() is that you don't know if a pointer was > >malloced, allocated from the env area above the stack, points to read-only > >text, points to a static data buffer, etc. There really is no way to know > >for sure, so you can't free the memory. > > Yo can know if you malloced it in a previous call to putenv() or setenv(). > > Bruce So we could: a) allocate a bit more memory than needed b) set the environment string c) end it with zero d) append a certain token after the end of the string saying "ok to free() me" to anyone knowing what to look at? But couldn't a string end at the end of allocated area so that by peeking behind the final zero we will sometimes cause a SIGSEV? Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 05:44:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29580 for freebsd-current-outgoing; Thu, 6 Aug 1998 05:44:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29544 for ; Thu, 6 Aug 1998 05:43:54 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id FAA28204; Thu, 6 Aug 1998 05:38:48 -0700 (PDT) Message-Id: <199808061238.FAA28204@implode.root.com> To: Narvi cc: Bruce Evans , freebsd@xaa.iae.nl, freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-reply-to: Your message of "Thu, 06 Aug 1998 15:24:08 +0300." From: David Greenman Reply-To: dg@root.com Date: Thu, 06 Aug 1998 05:38:48 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > The problem with fixing setenv() is that you don't know if a pointer was >> >malloced, allocated from the env area above the stack, points to read-only >> >text, points to a static data buffer, etc. There really is no way to know >> >for sure, so you can't free the memory. >> >> Yo can know if you malloced it in a previous call to putenv() or setenv(). >> >> Bruce > >So we could: > > a) allocate a bit more memory than needed > b) set the environment string > c) end it with zero > d) append a certain token after the end of the string saying "ok > to free() me" to anyone knowing what to look at? > >But couldn't a string end at the end of allocated area so that by peeking >behind the final zero we will sometimes cause a SIGSEV? Perhaps Bruce is suggesting that a seperate array be allocated to keep track of whether or not an env pointer was malloced? This would be very costly and, IMO, not worth it considering how rarely memory is lost by not freeing previously malloced strings. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 06:36:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06685 for freebsd-current-outgoing; Thu, 6 Aug 1998 06:36:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA06666 for ; Thu, 6 Aug 1998 06:36:12 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA23389; Thu, 6 Aug 1998 23:35:45 +1000 Date: Thu, 6 Aug 1998 23:35:45 +1000 From: Bruce Evans Message-Id: <199808061335.XAA23389@godzilla.zeta.org.au> To: dg@root.com, narvi@haldjas.folklore.ee Subject: Re: memory leaks in libc Cc: bde@zeta.org.au, freebsd-current@FreeBSD.ORG, freebsd@xaa.iae.nl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Perhaps Bruce is suggesting that a seperate array be allocated to keep >track of whether or not an env pointer was malloced? This would be very >costly and, IMO, not worth it considering how rarely memory is lost by >not freeing previously malloced strings. Erm, this would be quite cheap, considering how rarely the environment is updated except by programs that want to demonstrate leaks in it. Most programs don't even reference putenv() or getenv(). Shells shouldn't use them because they might be too slow. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 07:21:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11364 for freebsd-current-outgoing; Thu, 6 Aug 1998 07:21:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.98.150]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11357 for ; Thu, 6 Aug 1998 07:20:57 -0700 (PDT) (envelope-from root@myhakas.matti.ee) Received: (from root@localhost) by myhakas.matti.ee (8.8.8/8.8.5) id RAA00576; Thu, 6 Aug 1998 17:20:33 +0300 (EEST) Message-ID: <19980806172033.46098@matti.ee> Date: Thu, 6 Aug 1998 17:20:33 +0300 From: Vallo Kallaste To: freebsd-current@FreeBSD.ORG Subject: Crash: Fatal trap 12 Reply-To: vallo@matti.ee Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello ! Today I got two crashes sequentially, after that machine is very unstable Background: I'm working under X3.3.2, some rxvt's and Netscape running, make buildworld also. At some moment my machine hangs completely, nothing responds, I can't get out of X or access machine remotely, it even doesn't respond to ping. I compiled kernel yesterday with new XL driver in memory mapped mode (commented out one #define in if_xl.c ). My machine hasn't crashed for a month until now. My sources are dated 1 August. So, I rebooted machine and it goes up normally, fsck's disks and corrects something, but just before initial prompt it crashes: Fatal trap 12: page fault while in kernel mode fault virtual address: = 0xeffd6004 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01e2207 stack pointer = 0x10:0xf577bc24 frame pointer = 0x10:0xf577bc44 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = Idle interrupt mask = net tty bio cam kernel: type 12 trap, code=0 Stopped at _pmap_enter+0x97: movl 0(%ecx),%ecx db> trace _pmap_enter(f023f188,f5801000,780e00,7,0,f577bcac,0) at _pmap_enter+0x97 _vm_fault(f023514c,f5801000,1,0,0) at _vm_fault+0x837 _trap_pfault(f577abd78,0,7b2d000,6,2000) at _trap_pfault+0x10b _trap(10,10,2000,6,f577bde4) at _trap+0x35f calltrap() at calltrap+0x15 --- trap 0xc, eip = 0xf01e42a0, esp = 0xf577bdb4, ebp = 0xf577bde4 --- swtch_com(80000000,f577bf84,f576a9c0,f3270110,100) at swtch_com+0x25 _tsleep(f0245a10,118,f01239bb,1f5,f576a9c0) at _tsleep+0x121 _poll(f576a9c0,f577bf84) at _poll+0x24c _syscall(27,27,1388,efbfaa68,efbfabf4) at _syscall+0x10f _Xsyscall() at _Xsyscall+0x35 --- syscall 0xd1, eip = 0x2005d6b1, esp = 0xefbfa958, ebp = 0xefbfabf4 --- db> show registers cs 0x8 ds 0x10 es 0x10 ss 0x10 eax 0xeffd6004 ecx 0xeffd6004 edx 0xefc00000 _PTmap ebx 0xf5801000 esp 0xf577bc24 ebp 0xf577bc44 esi 0x780e000 edi 0xf023f188 _kernel_pmap_store eip 0xf01e2207 _pmap_enter+0x97 efl 0x10082 _pmap_enter+0x97: movl 0(%ecx),%ecx db> This is a first crash traceback, copied by hand. Please remember, I never haven't done that and I don't have any background knowledge about debugging. Now, I rebooted machine and all repeats exactly, only crash is different. My machine crashes again just before initial prompt: mode = 0100644, inum = 266, fs = / panic: ffs_valloc: deep alloc Debugger("panic") stopped at _Debugger+0x35: movb $0,_in_Debugger.98 db> trace _Debugger(f011a7d4) at _Debugger+0x35 _panic(f01b056b,f01b054a,81a4,10a,f094e0d4) at _panic+0x5a _ffs_valloc(f57648e0,8180,f0910b00,f577fcbc,f577fe20) at _ffs_valloc+0xf6 _ufs_makeinode(8180,f57648e0,f577ff04,f577ff18) at _ufs_makeinode+0x57 _ufs_create(f577fe20,f577fe94,f0142b76,f577fe20,0) at _ufs_create+0x26 _ufs_vnoperate(f577fe20) at _ufs_vnoperate+0x15 _vn_open(f577fef4,a03,180,f576a880,f021c348) at _vn_open+0x116 _open(f576a880,f577ff84) at _open+0xad _syscall(27,27,e052,efbfde9b,efbfde18) at _syscall+0x10f _Xsyscall() at _Xsyscall+0x35 --- syscall 0x5, eip = 0x3a35, esp = 0xefbfdaf8, ebp = 0xefbfde18 db> show registers cs 0x8 ds 0x10 es 0x10 ss 0x10 eax 0x12 ecx 0xf01d9ad3 _db_write_bytes+0x147 edx 0 ebx 0x100 esp 0xf577fc40 ebp 0xf577fc48 esi 0xf01b056b _ffs_reallocblks+0x2b edi 0xf577fcbc eip 0xf01d9b09 _Debugger+0x35 efl 0x246 _Debugger+0x35: movb $0,_in_Debugger.98 db> This is a second crash and traceback. I used command "panic" at db> prompt, but unfortunately I don't have savecore enabled, so I don't have crashdump. After second crash my machine reboots itself and I used -s switch to get to single user. I fsck'ed filesystems by hand and lost one (not important because I have backup ). This is not a system partition, for remark. So far so good. After reboot my machine goes up normally, but are unstable, console hangs sometimes and Alt+F2 etc. don't work. Dmesg: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Wed Aug 5 18:23:57 EEST 1998 root@myhakas.matti.ee:/opt/src/sys/compile/Myhakas Timecounter "i8254" frequency 1193233 Hz cost 2638 ns Timecounter "TSC" frequency 199440070 Hz cost 137 ns CPU: Pentium/P54C (199.44-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 134217728 (131072K bytes) avail memory = 127967232 (124968K bytes) Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip2: rev 0x01 int d irq 10 on pci0.7.2 chip3: rev 0x01 on pci0.7.3 ahc0: rev 0x00 int a irq 9 on pci0.9.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 ahc0:A:0: refuses WIDE negotiation. Using 8bit transfers cd0 at scbus0 target 0 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM can't get the size st0 at scbus0 target 1 lun 0 st0: type 1 removable SCSI 2 st0: Sequential-Access density code 0x45, drive empty xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x24 int a irq 5 on pci0.10.0 xl0: Ethernet address: 00:a0:24:4e:3e:57 vga0: rev 0x9a on pci0.11.0 Probing for PnP devices: CSN 1 Vendor ID: GRV0001 [0x0100561e] Serial 0x00000484 mss_attach 1 at 0x328 irq 11 dma 7:5 flags 0x15 pcm1 (GusPnP sn 0x00000484) at 0x328-0x32f irq 11 drq 7 flags 0x15 on isa Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pcm0 not found wdc0 at 0x1f0-0x1f7 irq 14 flags 0xb008b008 on isa wdc0: unit 0 (wd0): , LBA, 32-bit, multi-block-8 wd0: 814MB (1667232 sectors), 827 cyls, 32 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , LBA, DMA, 32-bit, multi-block-8 wd1: 1151MB (2358720 sectors), 585 cyls, 64 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xb008b008 on isa wdc1: unit 0 (wd2): , LBA, DMA, 32-bit, multi-block-8 wd2: 2014MB (4124736 sectors), 1023 cyls, 64 heads, 63 S/T, 512 B/S wdc1: unit 1 (wd3): , LBA, DMA, 32-bit, multi-block-8 wd3: 2014MB (4124736 sectors), 1023 cyls, 64 heads, 63 S/T, 512 B/S fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset in EPP mode (EPP 1.9) Intel Pentium F00F detected, installing workaround changing root device to wd0s1a WARNING: / was not properly dismounted. xl0: autoneg complete, link status good (half-duplex, 10Mbps) ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated Kernel config: # Myhakas # machine "i386" ident Myhakas maxusers 12 config kernel root on wd0 options PQ_LARGECACHE # color for 512k/16k cache cpu "I586_CPU" # aka Pentium(tm) #cpu "I686_CPU" # aka Pentium Pro(tm) options "CPU_FASTER_5X86_FPU" #options "NO_F00F_HACK" options "COMPAT_43" options SYSVSHM options SYSVSEM options SYSVMSG options "MD5" options "VM86" options DDB #options DDB_UNATTENDED #options KTRACE #kernel tracing options PERFMON options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device tun 1 #Tunnel driver (user process ppp(8)) #pseudo-device sl 1 #Serial Line IP #pseudo-device ppp 1 #Point-to-point protocol #options PPP_BSDCOMP #PPP BSD-compress support #options PPP_DEFLATE #PPP zlib/deflate/gzip support #options PPP_FILTER #enable bpf filtering (needs bpfilter) options FFS #Fast filesystem options NFS #Network File System # options NFS_NOSERVER #Disable the NFS-server code. options "CD9660" #ISO 9660 filesystem #options KERNFS #Kernel filesystem options MFS #Memory File System options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options FFS_ROOT #FFS usable as root device options SOFTUPDATES controller scbus0 #base SCSI code device sd0 #SCSI disks device st0 #SCSI tapes device cd0 #SCSI CD-ROMs options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" pseudo-device pty 16 #Pseudo ttys - can go as high as 256 pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. #pseudo-device ccd 4 #Concatenated disk driver #pseudo-device su #scsi user #pseudo-device ssc #super scsi controller isa0 #options "AUTO_EOI_1" #options "AUTO_EOI_2" #options BOUNCE_BUFFERS controller pnp0 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options MAXCONS=16 # number of virtual consoles #options SLOW_VGA # do byte-wide i/o's to TS and G DC regs #options "STD8X16FONT" # Compile font in #makeoptions "STD8X16FONT"="cp850" options SC_HISTORY_SIZE=600 # number of history buffer lines options SC_DISABLE_REBOOT # disable reboot key sequence device npx0 at isa? port "IO_NPX" iosiz 0x0 flags 0x0 irq 13 vector npxintr controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xb008b008 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xb008b008 vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus #options ATAPI_STATIC #Don't do it as an LKM device wcd0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 #device lpt0 at isa? port? tty irq 7 vector lptintr #device lpt1 at isa? port "IO_LPT3" tty irq 5 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmint r device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device pcm0 at isa? port ? tty irq ? drq ? vector pcmintr controller ahc0 options AHC_TAGENABLE options AHC_SCBPAGING_ENABLE options AHC_ALLOW_MEMIO controller pci0 device de0 device xl0 controller ppbus0 controller vpo0 at ppbus? controller ppc0 at isa? port ? irq 7 vector ppcintr options CLK_CALIBRATION_LOOP options "CLK_USE_I8254_CALIBRATION" options CLK_USE_TSC_CALIBRATION options COMPAT_LINUX options PANIC_REBOOT_WAIT_TIME=30 options SCSI_DELAY=5 # Be pessimistic about Joe SCSI device options SHMMAXPGS=1025 I have one comment, I worked one whole day with new XL driver enabled without a hitch, but this was on the 10Mbit half duplex network. Half hour before first crash I switched over to 100Mbit full-duplex segment on our 3Com SuperStack II 1100 switch. Currently my network connection is 10Mbit half-duplex, I switched back because seems 100Mbit connection causes my machine unstability. Thanks Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 07:38:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA14127 for freebsd-current-outgoing; Thu, 6 Aug 1998 07:38:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA14113 for ; Thu, 6 Aug 1998 07:38:53 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id IAA11525; Thu, 6 Aug 1998 08:38:31 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id IAA12182; Thu, 6 Aug 1998 08:38:27 -0600 Date: Thu, 6 Aug 1998 08:38:27 -0600 Message-Id: <199808061438.IAA12182@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Terry Lambert Cc: reilly@zeta.org.au (Andrew Reilly), tom@uniserve.com, current@FreeBSD.ORG Subject: Re: Heads up on LFS In-Reply-To: <199808060606.XAA22855@usr09.primenet.com> References: <19980806112955.A4299@reilly.home> <199808060606.XAA22855@usr09.primenet.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > JAVA has a nasty tendency to leak like a sieve until the GC hits a > steady state. As does Modula 3. You've *got* to be kidding, right? Do you have any idea how often the GC collection pass is run? It would be *very* difficult in real world programs to leak any signficicant (~1MB) of memory before the GC phase kicked in. I know, I've tried and have benchmarks to prove it. Using 100% of the CPU for minutes at a time, I still get the GC kicking in using Sun's JVM implementation. (The M$ implementation is notorious for doing bad things since it uses a different reaping technology, so it's much less useful for programs that make heavy use of 'new'.) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 07:48:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15332 for freebsd-current-outgoing; Thu, 6 Aug 1998 07:48:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15325 for ; Thu, 6 Aug 1998 07:48:52 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id IAA11587; Thu, 6 Aug 1998 08:47:49 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id IAA12240; Thu, 6 Aug 1998 08:47:45 -0600 Date: Thu, 6 Aug 1998 08:47:45 -0600 Message-Id: <199808061447.IAA12240@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: dg@root.com Cc: Narvi , Bruce Evans , freebsd@xaa.iae.nl, freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-Reply-To: <199808061238.FAA28204@implode.root.com> References: <199808061238.FAA28204@implode.root.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David wrote: > The problem with fixing setenv() is that you don't know if a pointer > was malloced, allocated from the env area above the stack, points to > read-only text, points to a static data buffer, etc. There really is > no way to know for sure, so you can't free the memory. Bruce responded: > You can know if you malloced it in a previous call to putenv() or setenv(). David replied: > Perhaps Bruce is suggesting that a seperate array be allocated to keep > track of whether or not an env pointer was malloced? This would be very > costly and, IMO, not worth it considering how rarely memory is lost by > not freeing previously malloced strings. Very costly? Could you do almost all of it in the userland libraries, and would be pretty cost-free, especially considering it would only have much effect if the user did lots of environment allocations? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 08:30:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22014 for freebsd-current-outgoing; Thu, 6 Aug 1998 08:30:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA21928 for ; Thu, 6 Aug 1998 08:30:10 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z4RzG-0000Qg-00; Thu, 6 Aug 1998 09:29:54 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id JAA15132; Thu, 6 Aug 1998 09:30:13 -0600 (MDT) Message-Id: <199808061530.JAA15132@harmony.village.org> To: Philippe Regnauld Subject: Re: -current & pccard Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 05 Aug 1998 15:28:05 +0200." <19980805152805.30244@deepo.prosa.dk> References: <19980805152805.30244@deepo.prosa.dk> Date: Thu, 06 Aug 1998 09:30:13 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980805152805.30244@deepo.prosa.dk> Philippe Regnauld writes: : Also, there is no option to spindown the disk in the Libretto's BIOS -- : do we have an IOCTL for that ? No. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 08:45:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24903 for freebsd-current-outgoing; Thu, 6 Aug 1998 08:45:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles218.castles.com [208.214.165.218]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24883 for ; Thu, 6 Aug 1998 08:45:41 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA03196; Thu, 6 Aug 1998 08:44:08 -0700 (PDT) Message-Id: <199808061544.IAA03196@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: joelh@gnu.org cc: ben@rosengart.com, dacole@netcom.ca, current@FreeBSD.ORG Subject: New bootstrap config file(s) (Re: booting with verbosity by default? ) In-reply-to: Your message of "Thu, 06 Aug 1998 02:54:33 CDT." <199808060754.CAA13740@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Aug 1998 08:44:07 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> I would like to force my systems to always boot with '-v'.. Is there > >> any way to do this without operator intervention? > > Take a look at what boot(8) has to say about /boot.config. > > It says that -v doesn't make the cut for boot.config. The fix is > trivial, but I haven't yet rolled a pr. > > This suggestion hasn't been carefully considered or tested, but if you > want to fix it yourself, then in /sys/i386/boot/biosboot/boot.c, move > the bit about "loadflags &= (RB_DUAL | RB_SERIAL);" to right around > "readfile("boot.config", ...);" about 40 lines up. (The key is that > it should be before "getbootdev(boot_config, &loadflags);".) This > will effectively allow any boot flags in. It will become either "-v" in /boot.config or "set bootverbose" in the new bootstrap config, which I haven't named. And this is a handy topic to raise it under; the new bootstrap will (optionally) need access to quite a few files, and we may not really want these cluttering up the root directory. How do people feel about a /boot directory these days? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 08:49:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25690 for freebsd-current-outgoing; Thu, 6 Aug 1998 08:49:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coleridge.kublai.com (coleridge.kublai.com [207.96.1.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25682 for ; Thu, 6 Aug 1998 08:49:42 -0700 (PDT) (envelope-from shmit@coleridge.kublai.com) Received: (from shmit@localhost) by coleridge.kublai.com (8.8.8/8.8.8) id LAA10010; Thu, 6 Aug 1998 11:49:02 -0400 (EDT) (envelope-from shmit) Message-ID: <19980806114859.65354@kublai.com> Date: Thu, 6 Aug 1998 11:48:59 -0400 From: Brian Cully To: John Birrell Cc: current@FreeBSD.ORG Subject: Re: Pthreads woes Reply-To: shmit@kublai.com References: <19980805180913.10635@kublai.com> <199808052302.JAA28909@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199808052302.JAA28909@cimlogic.com.au>; from John Birrell on Thu, Aug 06, 1998 at 09:02:19AM +1000 X-Sender: If your mailer pays attention to this, it's broken. X-PGP-Info: finger shmit@kublai.com for my public key. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 06, 1998 at 09:02:19AM +1000, John Birrell wrote: > > The sequence of events is: > > > > main > > ---------------------- > > spawn threads > > loop { > > lock thread mutex > > wait for packet > > unlock mutex > > You keep the mutex locked while you wait? Yes, that way I don't have to waste time (even though it's a small amount) in mutex_lock after I get a packet (I want to /very/ quick response time). > > send signal to thread > > Signal a condition or a kill() signal? Sorry, I signal a condition with pthread_cond_signal(). > > If not, I'll see what I can do to make the test simpler. > > Does the code build cleanly (gcc -Wall) on -current, without using a GNU > configure script, and is it C code (not C++)? If yes, yes and yes, I'll > look at it. It builds -Wall and -Werror on -current from a couple of days ago, without using GNU configure (truly, configure is an abomination before the Lord), and it is entirely written in C; IOW, yes, yes, and yes. I'll send it to you privately, but don't fry your brain trying to find the problem, at this point I'm inclined to believe it's my fault. -bjc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 09:03:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28619 for freebsd-current-outgoing; Thu, 6 Aug 1998 09:03:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA28614 for ; Thu, 6 Aug 1998 09:03:23 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id JAA26197; Thu, 6 Aug 1998 09:03:07 -0700 (PDT) (envelope-from jdp) Message-Id: <199808061603.JAA26197@austin.polstra.com> To: tlambert@primenet.com Subject: Re: Heads up on LFS In-Reply-To: <199808060606.XAA22855@usr09.primenet.com> References: <199808060606.XAA22855@usr09.primenet.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 06 Aug 1998 09:03:07 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199808060606.XAA22855@usr09.primenet.com>, Terry Lambert wrote: > JAVA has a nasty tendency to leak like a sieve until the GC hits a > steady state. As does Modula 3. ^^^^^^^^^^^^^^^^ I don't know what you base that statement on. I have a lot of experience writing and using Modula-3 programs, and I've never observed the behavior you describe. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 09:10:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29647 for freebsd-current-outgoing; Thu, 6 Aug 1998 09:10:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vortex.starix.net (vortex.starix.net [208.219.83.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29573 for ; Thu, 6 Aug 1998 09:09:59 -0700 (PDT) (envelope-from syko@sykotik.org) Received: from localhost (syko@localhost) by vortex.starix.net (8.7.6/8.7.3) with SMTP id MAA08630; Thu, 6 Aug 1998 12:07:04 -0400 X-Authentication-Warning: vortex.starix.net: syko owned process doing -bs Date: Thu, 6 Aug 1998 12:07:04 -0400 (EDT) From: Dusk Auriel Sykotik X-Sender: syko@vortex.starix.net To: Bruce Evans cc: dg@root.com, narvi@haldjas.folklore.ee, freebsd-current@FreeBSD.ORG, freebsd@xaa.iae.nl Subject: Re: memory leaks in libc In-Reply-To: <199808061335.XAA23389@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apache uses them quite frequently. And this could make it very costly on large webservers. Where I work, we have hundreds of connections to some of our webservers per minute. We also use cgi scripts very frequently, and these use *env* functions quite frequently as well. /* * Matt Harris +++ Syko * BPSOFH, BIOFH, C, SQL, PERL +++ http://starix.technonet.net/~syko/ * FreeBSD SysAdmin +++ apocalypse.sykotik.org */ On Thu, 6 Aug 1998, Bruce Evans wrote: > > Perhaps Bruce is suggesting that a seperate array be allocated to keep > >track of whether or not an env pointer was malloced? This would be very > >costly and, IMO, not worth it considering how rarely memory is lost by > >not freeing previously malloced strings. > > Erm, this would be quite cheap, considering how rarely the environment is > updated except by programs that want to demonstrate leaks in it. Most > programs don't even reference putenv() or getenv(). Shells shouldn't > use them because they might be too slow. > > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 09:12:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00136 for freebsd-current-outgoing; Thu, 6 Aug 1998 09:12:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from esmeralda.xaa.iae.nl (esmeralda.xaa.iae.nl [194.151.75.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29997 for ; Thu, 6 Aug 1998 09:12:37 -0700 (PDT) (envelope-from freebsd@xaa.iae.nl) Received: from ariel.xaa.iae.nl (ariel.xaa.iae.nl [194.151.75.10]) by esmeralda.xaa.iae.nl (8.8.8/8.8.7) with ESMTP id SAA21281; Thu, 6 Aug 1998 18:12:16 +0200 (MET DST) (envelope-from freebsd@xaa.iae.nl) Received: by ariel.xaa.iae.nl (VMailer, from userid 1008) id AADEC456F; Thu, 6 Aug 1998 18:12:15 +0200 (CEST) Message-ID: <19980806181215.A7652@xaa.iae.nl> Date: Thu, 6 Aug 1998 18:12:15 +0200 From: Mark Huizer To: Dusk Auriel Sykotik , Bruce Evans Cc: dg@root.com, narvi@haldjas.folklore.ee, freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc References: <199808061335.XAA23389@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Dusk Auriel Sykotik on Thu, Aug 06, 1998 at 12:07:04PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 06, 1998 at 12:07:04PM -0400, Dusk Auriel Sykotik wrote: > Apache uses them quite frequently. And this could make it very costly on > large webservers. Where I work, we have hundreds of connections to some > of our webservers per minute. We also use cgi scripts very frequently, > and these use *env* functions quite frequently as well. > > /* > * Matt Harris +++ Syko > * BPSOFH, BIOFH, C, SQL, PERL +++ http://starix.technonet.net/~syko/ > * FreeBSD SysAdmin +++ apocalypse.sykotik.org > */ Hmm... then we should write a nice DoS attack for apache, would that be a reason for solving it? Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 09:35:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02860 for freebsd-current-outgoing; Thu, 6 Aug 1998 09:35:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02838 for ; Thu, 6 Aug 1998 09:35:00 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id MAA14269; Thu, 6 Aug 1998 12:34:31 -0400 (EDT) (envelope-from wollman) Date: Thu, 6 Aug 1998 12:34:31 -0400 (EDT) From: Garrett Wollman Message-Id: <199808061634.MAA14269@khavrinen.lcs.mit.edu> To: Bruce Evans Cc: dg@root.com, freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-Reply-To: <199808061335.XAA23389@godzilla.zeta.org.au> References: <199808061335.XAA23389@godzilla.zeta.org.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> Perhaps Bruce is suggesting that a seperate array be allocated to keep >> track of whether or not an env pointer was malloced? This would be very >> costly and, IMO, not worth it considering how rarely memory is lost by >> not freeing previously malloced strings. > Erm, this would be quite cheap, considering how rarely the environment is > updated except by programs that want to demonstrate leaks in it. So you both agree, then, that there is no point in wasting any more time on this? -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 09:35:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02878 for freebsd-current-outgoing; Thu, 6 Aug 1998 09:35:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles218.castles.com [208.214.165.218]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02862 for ; Thu, 6 Aug 1998 09:35:07 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA03421; Thu, 6 Aug 1998 09:33:15 -0700 (PDT) Message-Id: <199808061633.JAA03421@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: pam@polynet.lviv.ua cc: current@FreeBSD.ORG Subject: Re: Q: DEVFS/SLICE real life usage example In-reply-to: Your message of "Thu, 06 Aug 1998 14:39:31 +0300." <19980806143931.A19551@LP.Lviv.UA> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Aug 1998 09:33:15 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi everybody! > > Can somebody post a real life example of FreeBSD configuration with > DEVFS/SLICE? options SLICE options DEVFS > Can it be used to totally eliminate /dev (I mean to have empty /dev on root > filesystem)? Yes. > What does mean? (what is its purpose?): > devfs 16 16 0 100% dummy_mount DEVFS keeps an internal "master copy" of /dev, so that even if you delete nodes from /dev, they still exist (and thus could be reconstituted). It needs to mount it somewhere very early on so that the root filesystem can be mounted from it, but it doesn't want to be anyhere visible. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 09:37:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03194 for freebsd-current-outgoing; Thu, 6 Aug 1998 09:37:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03154 for ; Thu, 6 Aug 1998 09:37:09 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id CAA00012; Fri, 7 Aug 1998 02:36:07 +1000 Date: Fri, 7 Aug 1998 02:36:07 +1000 From: Bruce Evans Message-Id: <199808061636.CAA00012@godzilla.zeta.org.au> To: bde@zeta.org.au, syko@sykotik.org Subject: Re: memory leaks in libc Cc: dg@root.com, freebsd-current@FreeBSD.ORG, freebsd@xaa.iae.nl, narvi@haldjas.folklore.ee Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Apache uses them quite frequently. And this could make it very costly on >large webservers. Where I work, we have hundreds of connections to some >of our webservers per minute. We also use cgi scripts very frequently, >and these use *env* functions quite frequently as well. The env functions are already costly. They use dumb linear searches and malloc(), and don't alloc a little more than necessary so that the environment can grow a little without reallocation. Garbage collection need not be equally pessimal. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 09:38:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03304 for freebsd-current-outgoing; Thu, 6 Aug 1998 09:38:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA03254 for ; Thu, 6 Aug 1998 09:37:56 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z4T13-0004Kq-00; Thu, 6 Aug 1998 09:35:49 -0700 Date: Thu, 6 Aug 1998 09:35:47 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Mark Huizer cc: Dusk Auriel Sykotik , Bruce Evans , dg@root.com, narvi@haldjas.folklore.ee, freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-Reply-To: <19980806181215.A7652@xaa.iae.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Aug 1998, Mark Huizer wrote: > On Thu, Aug 06, 1998 at 12:07:04PM -0400, Dusk Auriel Sykotik wrote: > > Apache uses them quite frequently. And this could make it very costly on > > large webservers. Where I work, we have hundreds of connections to some > > of our webservers per minute. We also use cgi scripts very frequently, > > and these use *env* functions quite frequently as well. > > > > /* > > * Matt Harris +++ Syko > > * BPSOFH, BIOFH, C, SQL, PERL +++ http://starix.technonet.net/~syko/ > > * FreeBSD SysAdmin +++ apocalypse.sykotik.org > > */ > > Hmm... then we should write a nice DoS attack for apache, would that be a > reason for solving it? Couldn't be done. CGI scripts are so short lived, that that memory gets cleaned up on its own anyhow. Perhaps specific a DoS attack could be tailored to a specific CGI script, but I would argue that the CGI script is broken. CGI is used less and less anyhow, as peole use better and faster methods of server side scripting. > Mark Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 09:38:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03288 for freebsd-current-outgoing; Thu, 6 Aug 1998 09:38:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03240 for ; Thu, 6 Aug 1998 09:37:52 -0700 (PDT) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with SMTP id MAA21946; Thu, 6 Aug 1998 12:37:11 -0400 (EDT) Date: Thu, 6 Aug 1998 12:37:11 -0400 (EDT) From: Brian Feldman To: Vallo Kallaste cc: freebsd-current@FreeBSD.ORG Subject: Re: Crash: Fatal trap 12 In-Reply-To: <19980806172033.46098@matti.ee> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This seems quite a bit like my current problems, I've noticed only very recently, and with no real regularity. My uptime just won't exceed 1 or 2 days, usually, beacuse I'll get a lockup. It happenes doing different things. This morning, it locked up after switching from vty0 to X, solid, no panic or trap... It crashed ~2 days ago when grepping stuff in /tmp. I have no idea what it was, but I've completely gone over all speed settings for RAM, CPU, to make sure everything's right. Another weird thing is swap was at 122 mb being used, after the 80 mb of system RAM, when there was nothing to be taking up anywhere near as much swap as that, and starting new stuff dived more into swap, while there was still nothing actually USING the swap at all... it just didn't seem to be "going free". Oh, and Sendmail seemed to be SIGSEGVing quite a bit, but a new sendmail.cf and a reboot fixed that. But here's any possibly pertinent info: 100 mb MFS /tmp (I actaully thing that was what was causing the leak of memory, since a program had filled it up to the top and then my swap was really high, removing stuff didn't help, even when I brought it down to 1mb in size SoftUpdates on all FSen CURRENT as of 8/3/98, world of 8/5/98 80 mb ram, K6 200, no special drivers, all EIDE I'd start working on the mfs code, looking for leaks and improper memory freeing, except I have a BSD book to buy and read :) Cheers, Brian Feldman On Thu, 6 Aug 1998, Vallo Kallaste wrote: > Hello ! > > Today I got two crashes sequentially, after that machine is very unstable > > Background: > > I'm working under X3.3.2, some rxvt's and Netscape running, make > buildworld also. At some moment my machine hangs completely, nothing > responds, I can't get out of X or access machine remotely, it even doesn't > respond to ping. I compiled kernel yesterday with new XL driver in memory > mapped mode (commented out one #define in if_xl.c ). My machine hasn't > crashed for a month until now. My sources are dated 1 August. So, I > rebooted machine and it goes up normally, fsck's disks and corrects > something, but just before initial prompt it crashes: > > Fatal trap 12: page fault while in kernel mode > fault virtual address: = 0xeffd6004 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf01e2207 > stack pointer = 0x10:0xf577bc24 > frame pointer = 0x10:0xf577bc44 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = Idle > interrupt mask = net tty bio cam > kernel: type 12 trap, code=0 > Stopped at _pmap_enter+0x97: movl 0(%ecx),%ecx > db> trace > _pmap_enter(f023f188,f5801000,780e00,7,0,f577bcac,0) at _pmap_enter+0x97 > _vm_fault(f023514c,f5801000,1,0,0) at _vm_fault+0x837 > _trap_pfault(f577abd78,0,7b2d000,6,2000) at _trap_pfault+0x10b > _trap(10,10,2000,6,f577bde4) at _trap+0x35f > calltrap() at calltrap+0x15 > --- trap 0xc, eip = 0xf01e42a0, esp = 0xf577bdb4, ebp = 0xf577bde4 --- > swtch_com(80000000,f577bf84,f576a9c0,f3270110,100) at swtch_com+0x25 > _tsleep(f0245a10,118,f01239bb,1f5,f576a9c0) at _tsleep+0x121 > _poll(f576a9c0,f577bf84) at _poll+0x24c > _syscall(27,27,1388,efbfaa68,efbfabf4) at _syscall+0x10f > _Xsyscall() at _Xsyscall+0x35 > --- syscall 0xd1, eip = 0x2005d6b1, esp = 0xefbfa958, ebp = 0xefbfabf4 --- > db> show registers > cs 0x8 > ds 0x10 > es 0x10 > ss 0x10 > eax 0xeffd6004 > ecx 0xeffd6004 > edx 0xefc00000 _PTmap > ebx 0xf5801000 > esp 0xf577bc24 > ebp 0xf577bc44 > esi 0x780e000 > edi 0xf023f188 _kernel_pmap_store > eip 0xf01e2207 _pmap_enter+0x97 > efl 0x10082 > _pmap_enter+0x97: movl 0(%ecx),%ecx > db> > > This is a first crash traceback, copied by hand. Please remember, I > never haven't done that and I don't have any background knowledge about > debugging. > Now, I rebooted machine and all repeats exactly, only crash is different. > My machine crashes again just before initial prompt: > > mode = 0100644, inum = 266, fs = / > panic: ffs_valloc: deep alloc > Debugger("panic") > stopped at _Debugger+0x35: movb $0,_in_Debugger.98 > db> trace > _Debugger(f011a7d4) at _Debugger+0x35 > _panic(f01b056b,f01b054a,81a4,10a,f094e0d4) at _panic+0x5a > _ffs_valloc(f57648e0,8180,f0910b00,f577fcbc,f577fe20) at _ffs_valloc+0xf6 > _ufs_makeinode(8180,f57648e0,f577ff04,f577ff18) at _ufs_makeinode+0x57 > _ufs_create(f577fe20,f577fe94,f0142b76,f577fe20,0) at _ufs_create+0x26 > _ufs_vnoperate(f577fe20) at _ufs_vnoperate+0x15 > _vn_open(f577fef4,a03,180,f576a880,f021c348) at _vn_open+0x116 > _open(f576a880,f577ff84) at _open+0xad > _syscall(27,27,e052,efbfde9b,efbfde18) at _syscall+0x10f > _Xsyscall() at _Xsyscall+0x35 > --- syscall 0x5, eip = 0x3a35, esp = 0xefbfdaf8, ebp = 0xefbfde18 > db> show registers > cs 0x8 > ds 0x10 > es 0x10 > ss 0x10 > eax 0x12 > ecx 0xf01d9ad3 _db_write_bytes+0x147 > edx 0 > ebx 0x100 > esp 0xf577fc40 > ebp 0xf577fc48 > esi 0xf01b056b _ffs_reallocblks+0x2b > edi 0xf577fcbc > eip 0xf01d9b09 _Debugger+0x35 > efl 0x246 > _Debugger+0x35: movb $0,_in_Debugger.98 > db> > > This is a second crash and traceback. I used command "panic" at db> > prompt, but unfortunately I don't have savecore enabled, so I don't have > crashdump. > After second crash my machine reboots itself and I used -s switch to get > to single user. I fsck'ed filesystems by hand and lost one (not > important because I have backup ). This is not a system partition, for > remark. So far so good. After reboot my machine goes up normally, but are > unstable, console hangs sometimes and Alt+F2 etc. don't work. > > Dmesg: > > Copyright (c) 1992-1998 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.0-CURRENT #0: Wed Aug 5 18:23:57 EEST 1998 > root@myhakas.matti.ee:/opt/src/sys/compile/Myhakas > Timecounter "i8254" frequency 1193233 Hz cost 2638 ns > Timecounter "TSC" frequency 199440070 Hz cost 137 ns > CPU: Pentium/P54C (199.44-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x52c Stepping=12 > Features=0x1bf > real memory = 134217728 (131072K bytes) > avail memory = 127967232 (124968K bytes) > Probing for devices on PCI bus 0: > chip0: rev 0x01 on pci0.0.0 > chip1: rev 0x01 on pci0.7.0 > ide_pci0: rev 0x01 on pci0.7.1 > chip2: rev 0x01 int d irq 10 on pci0.7.2 > chip3: rev 0x01 on pci0.7.3 > ahc0: rev 0x00 int a irq 9 on pci0.9.0 > ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs > ahc0: waiting for scsi devices to settle > scbus0 at ahc0 bus 0 > ahc0:A:0: refuses WIDE negotiation. Using 8bit transfers > cd0 at scbus0 target 0 lun 0 > cd0: type 5 removable SCSI 2 > cd0: CD-ROM can't get the size > st0 at scbus0 target 1 lun 0 > st0: type 1 removable SCSI 2 > st0: Sequential-Access density code 0x45, drive empty > xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x24 int a irq 5 on > pci0.10.0 > xl0: Ethernet address: 00:a0:24:4e:3e:57 > vga0: rev 0x9a on pci0.11.0 > Probing for PnP devices: > CSN 1 Vendor ID: GRV0001 [0x0100561e] Serial 0x00000484 > mss_attach 1 at 0x328 irq 11 dma 7:5 flags 0x15 > pcm1 (GusPnP sn 0x00000484) at 0x328-0x32f irq 11 drq 7 flags 0x15 on > isa > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > psm0 at 0x60-0x64 irq 12 on motherboard > psm0: model Generic PS/2 mouse, device ID 0 > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > pcm0 not found > wdc0 at 0x1f0-0x1f7 irq 14 flags 0xb008b008 on isa > wdc0: unit 0 (wd0): , LBA, 32-bit, multi-block-8 > wd0: 814MB (1667232 sectors), 827 cyls, 32 heads, 63 S/T, 512 B/S > wdc0: unit 1 (wd1): , LBA, DMA, 32-bit, > multi-block-8 > wd1: 1151MB (2358720 sectors), 585 cyls, 64 heads, 63 S/T, 512 B/S > wdc1 at 0x170-0x177 irq 15 flags 0xb008b008 on isa > wdc1: unit 0 (wd2): , LBA, DMA, 32-bit, multi-block-8 > wd2: 2014MB (4124736 sectors), 1023 cyls, 64 heads, 63 S/T, 512 B/S > wdc1: unit 1 (wd3): , LBA, DMA, 32-bit, multi-block-8 > wd3: 2014MB (4124736 sectors), 1023 cyls, 64 heads, 63 S/T, 512 B/S > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > npx0 on motherboard > npx0: INT 16 interface > ppc0 at 0x378 irq 7 on isa > ppc0: Generic chipset in EPP mode (EPP 1.9) > Intel Pentium F00F detected, installing workaround > changing root device to wd0s1a > WARNING: / was not properly dismounted. > xl0: autoneg complete, link status good (half-duplex, 10Mbps) > ffs_mountfs: superblock updated > ffs_mountfs: superblock updated > ffs_mountfs: superblock updated > ffs_mountfs: superblock updated > ffs_mountfs: superblock updated > ffs_mountfs: superblock updated > > Kernel config: > > # Myhakas > # > > machine "i386" > ident Myhakas > maxusers 12 > > config kernel root on wd0 > > options PQ_LARGECACHE # color for 512k/16k cache > > cpu "I586_CPU" # aka Pentium(tm) > #cpu "I686_CPU" # aka Pentium Pro(tm) > > options "CPU_FASTER_5X86_FPU" > #options "NO_F00F_HACK" > > options "COMPAT_43" > options SYSVSHM > options SYSVSEM > options SYSVMSG > options "MD5" > options "VM86" > options DDB > #options DDB_UNATTENDED > #options KTRACE #kernel tracing > options PERFMON > > options INET #Internet communications protocols > > pseudo-device ether #Generic Ethernet > pseudo-device loop #Network loopback device > pseudo-device bpfilter 4 #Berkeley packet filter > pseudo-device tun 1 #Tunnel driver (user process ppp(8)) > #pseudo-device sl 1 #Serial Line IP > #pseudo-device ppp 1 #Point-to-point protocol > #options PPP_BSDCOMP #PPP BSD-compress support > #options PPP_DEFLATE #PPP zlib/deflate/gzip support > #options PPP_FILTER #enable bpf filtering (needs bpfilter) > > options FFS #Fast filesystem > options NFS #Network File System > # options NFS_NOSERVER #Disable the NFS-server code. > options "CD9660" #ISO 9660 filesystem > #options KERNFS #Kernel filesystem > options MFS #Memory File System > options MSDOSFS #MS DOS File System > options PROCFS #Process filesystem > options FFS_ROOT #FFS usable as root device > > options SOFTUPDATES > > controller scbus0 #base SCSI code > device sd0 #SCSI disks > device st0 #SCSI tapes > device cd0 #SCSI CD-ROMs > > options "P1003_1B" > options "_KPOSIX_PRIORITY_SCHEDULING" > options "_KPOSIX_VERSION=199309L" > > pseudo-device pty 16 #Pseudo ttys - can go as high as 256 > pseudo-device gzip #Exec gzipped a.out's > pseudo-device vn #Vnode driver (turns a file into a device) > pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. > #pseudo-device ccd 4 #Concatenated disk driver > #pseudo-device su #scsi user > #pseudo-device ssc #super scsi > > controller isa0 > > #options "AUTO_EOI_1" > #options "AUTO_EOI_2" > #options BOUNCE_BUFFERS > > controller pnp0 > > device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr > options MAXCONS=16 # number of virtual consoles > #options SLOW_VGA # do byte-wide i/o's to TS and > G > DC regs > #options "STD8X16FONT" # Compile font in > #makeoptions "STD8X16FONT"="cp850" > options SC_HISTORY_SIZE=600 # number of history buffer lines > options SC_DISABLE_REBOOT # disable reboot key sequence > > device npx0 at isa? port "IO_NPX" iosiz 0x0 flags 0x0 irq 13 > vector > npxintr > > controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xb008b008 > vector > wdintr > disk wd0 at wdc0 drive 0 > disk wd1 at wdc0 drive 1 > controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xb008b008 > vector > wdintr > disk wd2 at wdc1 drive 0 > disk wd3 at wdc1 drive 1 > > options ATAPI #Enable ATAPI support for IDE bus > #options ATAPI_STATIC #Don't do it as an LKM > device wcd0 > > controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr > disk fd0 at fdc0 drive 0 > #disk fd1 at fdc0 drive 1 > > #device lpt0 at isa? port? tty irq 7 vector lptintr > #device lpt1 at isa? port "IO_LPT3" tty irq 5 vector lptintr > device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector > psmint > r > device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr > device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr > > device pcm0 at isa? port ? tty irq ? drq ? vector pcmintr > > controller ahc0 > options AHC_TAGENABLE > options AHC_SCBPAGING_ENABLE > options AHC_ALLOW_MEMIO > > controller pci0 > device de0 > device xl0 > > controller ppbus0 > controller vpo0 at ppbus? > controller ppc0 at isa? port ? irq 7 vector ppcintr > > options CLK_CALIBRATION_LOOP > options "CLK_USE_I8254_CALIBRATION" > options CLK_USE_TSC_CALIBRATION > options COMPAT_LINUX > options PANIC_REBOOT_WAIT_TIME=30 > options SCSI_DELAY=5 # Be pessimistic about Joe SCSI device > options SHMMAXPGS=1025 > > > I have one comment, I worked one whole day with new XL driver enabled without > a hitch, but this was on the 10Mbit half duplex network. Half hour before first > crash I switched over to 100Mbit full-duplex segment on our 3Com SuperStack II > 1100 switch. Currently my network connection is 10Mbit half-duplex, I switched > back because seems 100Mbit connection causes my machine unstability. > > Thanks > > > Vallo Kallaste > vallo@matti.ee > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 09:40:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03834 for freebsd-current-outgoing; Thu, 6 Aug 1998 09:40:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03695 for ; Thu, 6 Aug 1998 09:39:58 -0700 (PDT) (envelope-from pb@hsc.fr) Received: from mars.hsc.fr (mars.hsc.fr [192.70.106.44]) by itesec.hsc.fr (8.8.8/8.8.5/itesec-1.12-nospam) with ESMTP id SAA20130; Thu, 6 Aug 1998 18:39:32 +0200 (MET DST) Received: (from pb@localhost) by mars.hsc.fr (8.8.8/8.8.8/pb-19980526) id SAA05292; Thu, 6 Aug 1998 18:39:31 +0200 (CEST) (envelope-from pb) Message-ID: <19980806183931.A5235@mars.hsc.fr> Date: Thu, 6 Aug 1998 18:39:31 +0200 From: Pierre Beyssac To: Dusk Auriel Sykotik , Bruce Evans Cc: dg@root.com, narvi@haldjas.folklore.ee, freebsd-current@FreeBSD.ORG, freebsd@xaa.iae.nl Subject: Re: memory leaks in libc References: <199808061335.XAA23389@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: ; from Dusk Auriel Sykotik on Thu, Aug 06, 1998 at 12:07:04PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 06, 1998 at 12:07:04PM -0400, Dusk Auriel Sykotik wrote: > Apache uses them quite frequently. And this could make it very costly on > large webservers. Where I work, we have hundreds of connections to some Apparently, from a very quick glance at Apache code, it looks like Apache handles environment stuff by itself (without setenv) before handling it to external programs. > of our webservers per minute. We also use cgi scripts very frequently, > and these use *env* functions quite frequently as well. cgi scripts are short lived, so memory leaks here are short lived too and much less of a problem. -- Pierre.Beyssac@hsc.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 09:52:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06187 for freebsd-current-outgoing; Thu, 6 Aug 1998 09:52:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fleming.cs.strath.ac.uk (bell.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06080; Thu, 6 Aug 1998 09:52:05 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from cs.strath.ac.uk (posh.dmem.strath.ac.uk [130.159.202.3]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id RAA20736 Thu, 6 Aug 1998 17:51:45 +0100 (BST) Message-ID: <35C9DF20.462DF047@cs.strath.ac.uk> Date: Thu, 06 Aug 1998 17:51:44 +0100 From: Roger Hardiman Organization: Strathclyde Uni X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-980520-SNAP i386) MIME-Version: 1.0 To: current@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: brooktree848 driver for 2.2.8 and -stable Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Recently a few users have complained about card detection of their bt848 based TV cards which were solved by using the -current driver. (Mainly Hauppauge users and Hauppauge 404 cards with 878 chips) As the -current driver has proved trustworthy, I think we should merge it into the -stable tree for inclusion in 2.2.8. What do you think to this? Bye Roger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 09:57:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07000 for freebsd-current-outgoing; Thu, 6 Aug 1998 09:57:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06954 for ; Thu, 6 Aug 1998 09:56:38 -0700 (PDT) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.9.1/kong/0.01) with SMTP id UAA00367; Thu, 6 Aug 1998 20:55:44 +0400 (MSD) (envelope-from kong@kong.dorms.spbu.ru) Date: Thu, 6 Aug 1998 20:55:43 +0400 (MSD) From: Hostas Red To: Luoqi Chen cc: current@FreeBSD.ORG Subject: Re: Still having big problems with 'w' In-Reply-To: <199808060408.AAA08507@lor.watermarkgroup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! On Thu, 6 Aug 1998, Luoqi Chen wrote: > You must be using DEVFS. I had the same problem. Try the following patch, > it's a little simplistic, but it stopped my girlfriend from complaining > that I was trying to hide something from her :( Thanks, this helps. :) In console. :) When i'm starting X everything starts again :(. But this is not a problem in DEVFS, it is problems in xterm, i think. I'm using 3.3.2 (binaries from 2.2.7R). Maybe i need to recompile xterm or something? Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 10:01:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08158 for freebsd-current-outgoing; Thu, 6 Aug 1998 10:01:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coleridge.kublai.com (coleridge.kublai.com [207.96.1.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08153 for ; Thu, 6 Aug 1998 10:01:40 -0700 (PDT) (envelope-from shmit@natasya.kublai.com) Received: from natasya.kublai.com (natasya.kublai.com [207.172.25.236]) by coleridge.kublai.com (8.8.8/8.8.8) with ESMTP id NAA10576 for ; Thu, 6 Aug 1998 13:01:23 -0400 (EDT) (envelope-from shmit@natasya.kublai.com) Received: (from shmit@localhost) by natasya.kublai.com (8.8.8/8.8.8) id NAA14193; Thu, 6 Aug 1998 13:01:22 -0400 (EDT) Message-ID: <19980806130122.38511@kublai.com> Date: Thu, 6 Aug 1998 13:01:22 -0400 From: Brian Cully To: current@FreeBSD.ORG Subject: Pthreads woes revisited. Reply-To: shmit@kublai.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=FyWQ0h3ruR435lwh X-Mailer: Mutt 0.89i X-Sender: If your mailer pays attention to this, it's broken. X-PGP-Info: finger shmit@kublai.com for my public key. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --FyWQ0h3ruR435lwh Content-Type: text/plain; charset=us-ascii I've put together a small C program that demonstrates the problems I described in my last message. You can find the program attached to this message. Note the location of the `sleep(1)' call, it's important. If it moves outside of the mutex lock/unlock bits, everything functions normally, but if it gets called after the lock, but before the unlock, the first signal is missed. Looks like broken signal handling of some variety. -- Brian Cully ``And when one of our comrades was taken prisoner, blindfolded, hung upside-down, shot, and burned, we thought to ourselves, `These are the best experiences of our lives''' -Pathology (Joe Frank, Somewhere Out There) --FyWQ0h3ruR435lwh Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="ptest2.c" #include #include #include pthread_cond_t wakeup; pthread_mutex_t busy; void * thr_routine(void *arg) { int rc; for (;;) { printf("%d: Waiting for signal.\n", pthread_self); rc = pthread_cond_wait(&wakeup, &busy); if (rc) { fprintf(stderr, "ERROR: couldn't wait for condition: %s.\n", strerror(rc)); return NULL; } printf("%d: Got signal.\n", pthread_self); } return NULL; } int main(int argc, char *argv[]) { int rc; pthread_t thread_id; rc = pthread_cond_init(&wakeup, NULL); if (rc) { fprintf(stderr, "ERROR: couldn't create condition variable: %s.\n", strerror(rc)); return 1; } rc = pthread_mutex_init(&busy, NULL); if (rc) { fprintf(stderr, "ERROR: couldn't create mutex: %s.\n", strerror(rc)); return 1; } rc = pthread_create(&thread_id, NULL, thr_routine, NULL); if (rc) { fprintf(stderr, "ERROR: couldn't create thread: %s.\n", strerror(rc)); return 1; } for (;;) { printf("MASTER: Acquiring lock.\n"); rc = pthread_mutex_lock(&busy); if (rc) { fprintf(stderr, "ERROR: couldn't lock mutex: %s.\n", strerror(rc)); return 1; } sleep(1); printf("MASTER: Releasing lock.\n"); rc = pthread_mutex_unlock(&busy); if (rc) { fprintf(stderr, "ERROR: couldn't unlock mutex: %s.\n", strerror(rc)); return 1; } printf("MASTER: Sending signal.\n"); rc = pthread_cond_signal(&wakeup); if (rc) { fprintf(stderr, "ERROR: couldn't signal thread: %s.\n", strerror(rc)); return 1; } } return 0; } --FyWQ0h3ruR435lwh-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 10:16:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11418 for freebsd-current-outgoing; Thu, 6 Aug 1998 10:16:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11368 for ; Thu, 6 Aug 1998 10:16:46 -0700 (PDT) (envelope-from nrahlstr@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id MAA03285; Thu, 6 Aug 1998 12:16:11 -0500 (CDT) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma003251; Thu, 6 Aug 98 12:16:06 -0500 Received: from localhost (nrahlstr@localhost) by tundra.winternet.com (8.8.7/8.8.4) with SMTP id MAA06021; Thu, 6 Aug 1998 12:16:05 -0500 (CDT) X-Authentication-Warning: tundra.winternet.com: nrahlstr owned process doing -bs Date: Thu, 6 Aug 1998 12:16:05 -0500 (CDT) From: Nathan Ahlstrom Reply-To: Nathan Ahlstrom To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: New bootstrap config file(s) (Re: booting with verbosity by default? ) In-Reply-To: <199808061544.IAA03196@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > want these cluttering up the root directory. How do people feel about > a /boot directory these days? A /boot directory would be very nice to keep down / clutter. This probably should be configurable somehow? if possible? Nathan Ahlstrom nrahlstr@winternet.com Run FreeBSD: http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 10:23:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12698 for freebsd-current-outgoing; Thu, 6 Aug 1998 10:23:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay1.aha.ru (relay1.aha.ru [195.2.83.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12676 for ; Thu, 6 Aug 1998 10:23:04 -0700 (PDT) (envelope-from osa@serv.etrust.ru) Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112]) by relay1.aha.ru (8.9.1/aha-r/0.04B) with ESMTP id VAA10697 for ; Thu, 6 Aug 1998 21:22:47 +0400 (MSD) Received: by sunny.aha.ru id VAA10176; (8.8.8/vak/1.9) Thu, 6 Aug 1998 21:22:23 +0400 (MSD) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma010137; Thu Aug 6 21:22:18 1998 Received: by serv.etrust.ru id VAA21670; (8.9.1/vak/1.9) Thu, 6 Aug 1998 21:25:17 +0400 (MSD) Date: Thu, 6 Aug 1998 21:25:17 +0400 (MSD) From: osa@serv.etrust.ru (Sergey A. Osokin) Message-Id: <199808061725.VAA21670@serv.etrust.ru> To: freebsd-current@FreeBSD.ORG Subject: make package in /usr/ports/lang/perl5 ( perl-5.00501 ) can't work? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Today I cvsuped FreeBSD-current sources & ports. I deinstall perl-5.00404 & then: # cd /usr/ports/lang/perl5 # make package ............ ........... Creating gzip'd tar ball in 'usr/ports/lang/perl5/perl-5.00501.tgz' tar: can't add file lib/perl5/site_perl/5.005/i386-freebsd/forms.ph : No such file or directory tar: can't add file lib/perl5/site_perl/5.005/i386-freebsd/machine/qcam.ph : No such file or directory *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. What can i do? Rgdz, oZZ, osa@etrust.ru RUSENIX - RUSsian USE UNIX! http://www.etrust.ru/osa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 10:24:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12961 for freebsd-current-outgoing; Thu, 6 Aug 1998 10:24:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12863 for ; Thu, 6 Aug 1998 10:24:05 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA02057; Fri, 7 Aug 1998 03:23:29 +1000 Date: Fri, 7 Aug 1998 03:23:29 +1000 From: Bruce Evans Message-Id: <199808061723.DAA02057@godzilla.zeta.org.au> To: bde@zeta.org.au, wollman@khavrinen.lcs.mit.edu Subject: Re: memory leaks in libc Cc: dg@root.com, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >So you both agree, then, that there is no point in wasting any more >time on this? Not quite. It should be fixed someday. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 10:26:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13636 for freebsd-current-outgoing; Thu, 6 Aug 1998 10:26:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA13610 for ; Thu, 6 Aug 1998 10:26:20 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 17168 invoked by uid 1001); 6 Aug 1998 17:26:00 +0000 (GMT) To: mike@smith.net.au Cc: current@FreeBSD.ORG Subject: Re: New bootstrap config file(s) (Re: booting with verbosity by default? ) In-Reply-To: Your message of "Thu, 06 Aug 1998 08:44:07 -0700" References: <199808061544.IAA03196@antipodes.cdrom.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 06 Aug 1998 19:26:00 +0200 Message-ID: <17166.902424360@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And this is a handy topic to raise it under; the new bootstrap will > (optionally) need access to quite a few files, and we may not really > want these cluttering up the root directory. How do people feel about > a /boot directory these days? Yes, please. Reducing clutter in / is a good thing. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 10:35:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15583 for freebsd-current-outgoing; Thu, 6 Aug 1998 10:35:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from account.abs.net (account.abs.net [207.114.0.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15573 for ; Thu, 6 Aug 1998 10:35:24 -0700 (PDT) (envelope-from howardl@account.abs.net) Received: (from howardl@localhost) by account.abs.net (8.9.0/8.9.0) id NAA14189; Thu, 6 Aug 1998 13:35:03 -0400 (EDT) From: Howard Leadmon Message-Id: <199808061735.NAA14189@account.abs.net> Subject: 3.0-19980720-SNAP & de full-duplex trouble? To: freebsd-current@FreeBSD.ORG Date: Thu, 6 Aug 1998 13:35:03 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I loaded up the 3.0 SNAP the other day and things seemed to be going well, and then I decided to try and put the DEC-21140 based board I had into full-duplex mode. Needless to say I also set the EtherSwitch it was connected to into full-duplex mode (I know the switch handles this well as I have a bunch of Solaris boxes running full-duplex on the same switch). My throughput came to a screeching halt, I could barely even FTP any files across. Also even though the machine claimed it was in full-duplex mode, it's still showing collisions even after a fresh reboot. Here is what I get from ifconfig: $ ifconfig -a de0: flags=8843 mtu 1500 inet 207.114.0.144 netmask 0xffffff00 broadcast 207.114.0.255 inet 207.114.0.241 netmask 0xffffff00 broadcast 207.114.0.255 inet 207.114.0.242 netmask 0xffffff00 broadcast 207.114.0.255 ether 00:c0:f0:30:0d:ad media: 10baseT/UTP (10baseT/UTP) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP Also looking at dmesg from the reboot, it appears to be in full-duplex: de0: rev 0x22 int a irq 11 on pci0.20.0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:f0:30:0d:ad de0: enabling 10baseT port de0: enabling Full Duplex 10baseT port Now the way I did this, was to just set the following in my rc.conf file on the machine: ifconfig_de0="inet 207.114.0.144 netmask 255.255.255.0 media 10baseT/UTP mediao pt full-duplex" So with all the above set, still a netstat -i shows: $ netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll de0 1500 00.c0.f0.30.0d.ad 238593178 11 237898092 5096726 4662492 de0 1500 207.114 u2 238593178 11 237898092 5096726 4662492 So it is seeing collisions, and I can only assume it's runing in half-duplex mode, even though everything seems to point to full-duplex. So does anyone have any ideas? Is the full-duplex option broken in 3.0 current? As this machine is being used for an IRC server, it's seeing a lot of small packets, so running full-duplex would sure cut out a lot of collisions. --- Howard Leadmon - howardl@abs.net - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 10:37:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15904 for freebsd-current-outgoing; Thu, 6 Aug 1998 10:37:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15889; Thu, 6 Aug 1998 10:37:30 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id NAA27893; Thu, 6 Aug 1998 13:37:59 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Thu, 6 Aug 1998 13:37:58 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: Bill Paul cc: current@FreeBSD.ORG Subject: Re: Etherlink XL driver In-Reply-To: <199808060425.VAA23145@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > using the first version of the driver posted on 100mb segement seemed to > > have not great performance. The admin here said he was able to get > > ~8megs/sec over the segment using Linux and 11megs/sec via Solaris, the > > FreeBSD driver was never over 4.5megs and averaged around 3-3.5. This is > > ftp transfers. It seems to grab a LOT of data, then "stall" then grab, > > stall over and over. > > Can you describe the system in which the card is installed? What kind > of processor and how fast is it? Well it's a PII-300, 128megs of RAM. > Make absolutely sure the 3Com and the hub/switch are operating in the > same mode. Use 'ifconfig xl0 media 100baseTX mediaopt full-duplex' > to force a full-duplex link, or 'mediaopt half-duplex to force a > half-duplex link. will do later, it's kinda busy here at the moment. thank you, Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 10:53:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18122 for freebsd-current-outgoing; Thu, 6 Aug 1998 10:53:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18107 for ; Thu, 6 Aug 1998 10:53:10 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id NAA97020; Thu, 6 Aug 1998 13:52:41 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <199808060948.CAA26488@implode.root.com> References: Your message of "Thu, 06 Aug 1998 10:08:59 +0200." <19980806100859.A312@xaa.iae.nl> Date: Thu, 6 Aug 1998 13:56:40 -0400 To: dg@root.com, Mark Huizer From: Garance A Drosihn Subject: Re: memory leaks in libc Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> To mention a very simple example: >> >> main(){while(1){setenv("A","AA",1);setenv("A","A",1);}} >> >> will consume all memory within short periods of time (see setenv.c >> for the reason). >> >> Is this wellknown? I think it is bad, and would like to fix it > > The problem with fixing setenv() is that you don't know if a pointer > was malloced, allocated from the env area above the stack, points to > read-only text, points to a static data buffer, etc. There really is > no way to know for sure, so you can't free the memory. setenv could keep track of memory that *it* mallocs for environment variables. That would at least solve the example case, even if it doesn't solve everything. This implies it'd have some memory- management smarts of it's own, and I don't know if a partial fix is really worth that much effort, but I would think it is doable. (seeing that it's mostly dealing with short strings, I'd have it malloc 1 Kbytes at a time, and then carve that up for environment variables. Then it wouldn't be too expensive to check if a given variable is part of setenv's own memory). --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 10:55:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18633 for freebsd-current-outgoing; Thu, 6 Aug 1998 10:55:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from plunger.gdeb.com (plunger.gdeb.com [153.11.11.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18608 for ; Thu, 6 Aug 1998 10:55:38 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from clcrtr.clc.gdeb.com ([153.11.109.11]) by plunger.gdeb.com with ESMTP (1.37.109.16/CSC-E_1.8) id AA142626082; Thu, 6 Aug 1998 13:54:42 -0400 Received: from clcrtr.clc.gdeb.com (clcrtr [153.11.109.129]) by clcrtr.clc.gdeb.com (8.8.8/8.7.3) with SMTP id NAA09576; Thu, 6 Aug 1998 13:51:57 -0400 (EDT) Message-Id: <35C9ED3D.41C67EA6@vigrid.com> Date: Thu, 06 Aug 1998 13:51:57 -0400 From: "Daniel M. Eischen" X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.6-STABLE i386) Mime-Version: 1.0 To: shmit@kublai.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Pthreads woes revisited. Content-Type: multipart/mixed; boundary="------------446B9B3D2781E494167EB0E7" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------446B9B3D2781E494167EB0E7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > I've put together a small C program that demonstrates the problems > I described in my last message. You can find the program attached > to this message. > > Note the location of the `sleep(1)' call, it's important. If it moves > outside of the mutex lock/unlock bits, everything functions normally, > but if it gets called after the lock, but before the unlock, the first > signal is missed. > But your not yielding the CPU after the pthread_cond_signal(). The waiter thread (thr_wait) should also take the mutex lock (busy) before the pthread_cond_wait(). See the comments in the revised copy of your code. Dan Eischen eischen@vigrid.com --------------446B9B3D2781E494167EB0E7 Content-Type: text/plain; charset=us-ascii; name="thr_test.c" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="thr_test.c" #include #include #include #include pthread_cond_t wakeup; pthread_mutex_t busy; void * thr_routine(void *arg) { int rc; /* * The mutex should be taken before the condition wait. * The condition wait will atomically release the mutex and * retake it when awoken. */ pthread_mutex_lock (&busy); for (;;) { printf("%d: Waiting for signal.\n", (int) pthread_self ()); rc = pthread_cond_wait(&wakeup, &busy); if (rc) { fprintf(stderr, "ERROR: couldn't wait for condition: %s.\n", strerror(rc)); return NULL; } printf("%d: Got signal.\n", (int) pthread_self ()); } return NULL; } int main(int argc, char *argv[]) { int rc; pthread_t thread_id; rc = pthread_cond_init(&wakeup, NULL); if (rc) { fprintf(stderr, "ERROR: couldn't create condition variable: %s.\n", strerror(rc)); return 1; } rc = pthread_mutex_init(&busy, NULL); if (rc) { fprintf(stderr, "ERROR: couldn't create mutex: %s.\n", strerror(rc)); return 1; } rc = pthread_create(&thread_id, NULL, thr_routine, NULL); if (rc) { fprintf(stderr, "ERROR: couldn't create thread: %s.\n", strerror(rc)); return 1; } for (;;) { printf("MASTER: Acquiring lock.\n"); rc = pthread_mutex_lock(&busy); if (rc) { fprintf(stderr, "ERROR: couldn't lock mutex: %s.\n", strerror(rc)); return 1; } sleep(1); printf("MASTER: Releasing lock.\n"); rc = pthread_mutex_unlock(&busy); if (rc) { fprintf(stderr, "ERROR: couldn't unlock mutex: %s.\n", strerror(rc)); return 1; } printf("MASTER: Sending signal.\n"); rc = pthread_cond_signal(&wakeup); if (rc) { fprintf(stderr, "ERROR: couldn't signal thread: %s.\n", strerror(rc)); return 1; } /* Allow the other thread to run. */ pthread_yield (); } return 0; } --------------446B9B3D2781E494167EB0E7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 11:07:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20528 for freebsd-current-outgoing; Thu, 6 Aug 1998 11:07:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20510 for ; Thu, 6 Aug 1998 11:07:47 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with ESMTP id LAA02309; Thu, 6 Aug 1998 11:07:21 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 6 Aug 1998 11:07:20 -0700 (PDT) From: Doug White To: =?X-UNKNOWN?B?t3Ok9Lprs1iryA==?= cc: freebsd-current@FreeBSD.ORG Subject: Re: About VCD (raw data reading) In-Reply-To: <199808051915.DAA05098@SungSung.Dorm10.NCTU.edu.tw> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Aug 1998, ·s¤ôºk³X«È wrote: > > I'd got http://www.mahoroba.ne.jp/~naoya/archives/vcdr.tar.gz > and patched, but it seems not working.... > > [AlanSung@ttyp1(SungSung)][/usr/tmp] >./vcdr /dev/cd0c 2 > Can't read RAW data.  > > Is there any new patch for 3.0-CURRENT? > my cdrom is TEAC 532S What raw data are you trying to read? The page is in Japanese so I can't figure out how this functionality is different from tosha/cdd. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 11:16:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22090 for freebsd-current-outgoing; Thu, 6 Aug 1998 11:16:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21994 for ; Thu, 6 Aug 1998 11:15:57 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id VAA28889; Thu, 6 Aug 1998 21:13:30 +0300 (EEST) Date: Thu, 6 Aug 1998 21:13:30 +0300 (EEST) From: Narvi To: Bruce Evans cc: syko@sykotik.org, dg@root.com, freebsd-current@FreeBSD.ORG, freebsd@xaa.iae.nl Subject: Re: memory leaks in libc In-Reply-To: <199808061636.CAA00012@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998, Bruce Evans wrote: > >Apache uses them quite frequently. And this could make it very costly on > >large webservers. Where I work, we have hundreds of connections to some > >of our webservers per minute. We also use cgi scripts very frequently, > >and these use *env* functions quite frequently as well. > > The env functions are already costly. They use dumb linear searches > and malloc(), and don't alloc a little more than necessary so that the > environment can grow a little without reallocation. Garbage collection > need not be equally pessimal. > > Bruce > Ok, I did make a dumb suggestion already. What follows is just my cursory reading of the code and thoughts on it: As we cannot disallow user r/w access to the environment that by-passes *env functions in the libc, we cannot have a perfect world. In a way, it is similar to allowing the user do go and muck freely with the malloc internal structures. But it should be possible to have a schema under wich: a) there exists a hash of all pointers returned by malloc to us. Using it we can know which strings are safe to be reallocated/freed b) a hash of all setenved strings. For use by get/setenv. Fragmentation: use one malloced area per a name, value pair. Keep an additional adaptive anmount of memory for the case it is going to get expanded yet again. Which adds the problem: the environment would need to be captured at startup time, before any user code runs, that would set up the inital hashes (init_environ). BUGS: Can be made to leak both memory and spam it's internal pointer hash, if the user a) setenvs a variable, b) manually changes the pointer value in the array c) repeats a) and b) a lot. Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 11:35:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25761 for freebsd-current-outgoing; Thu, 6 Aug 1998 11:35:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25744 for ; Thu, 6 Aug 1998 11:35:20 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.9.1/8.9.1) with SMTP id TAA26189 for ; Thu, 6 Aug 1998 19:35:03 +0100 (BST) Date: Thu, 6 Aug 1998 19:35:03 +0100 (BST) From: Karl Pielorz To: current@FreeBSD.ORG Subject: Building 2.2.7 on a 3.0-CURRENT system? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I have a fast 3.0-CURRENT system, and I need to build a 2.2.7-RELEASE, in order to muck around with the boot & fixit floppies... Can I get away doing this by copying the whole 2.2.7-RELEASE (/usr/src) source tree to a volume on the fast machine, e.g. /usr2/2.2.7-RELEASE And then running: cd /usr2/2.2.7-RELEASE make buildworld Are there any hardcoded paths in there that are going to screw up? - or is it generally 'not a good idea' to try building 2.2.X sources on 3.0 systems? (I'm worried about it finding / using 3.0 libs etc?) Any info greatly appreciated, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 11:36:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25933 for freebsd-current-outgoing; Thu, 6 Aug 1998 11:36:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25883 for ; Thu, 6 Aug 1998 11:36:26 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id SAA15799; Thu, 6 Aug 1998 18:36:00 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id UAA27330; Thu, 6 Aug 1998 20:35:59 +0200 (MET DST) Message-ID: <19980806203555.56458@follo.net> Date: Thu, 6 Aug 1998 20:35:55 +0200 From: Eivind Eklund To: Tom , Andrew Reilly Cc: current@FreeBSD.ORG Subject: Re: Heads up on LFS References: <19980806112955.A4299@reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Tom on Wed, Aug 05, 1998 at 08:26:32PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 05, 1998 at 08:26:32PM -0700, Tom wrote: > Most microkernel OSes are this way. QNX for x86 does something similar. > The kernel is basically just a scheduler (a QNX kernel is less than 50K), 7k, IIRC. > and all other services that would normally be in the kernel are in their > own address spaces, using strict IPC interfaces between modules. Being able to develop device drivers without expecting your macine to hang is actually very neat :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 11:40:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26484 for freebsd-current-outgoing; Thu, 6 Aug 1998 11:40:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.spel.com (elevator.cablenet-va.com [208.206.84.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26343; Thu, 6 Aug 1998 11:39:18 -0700 (PDT) (envelope-from mturpin@shadow.spel.com) Received: from localhost (mturpin@localhost) by shadow.spel.com (8.8.5/8.8.5) with SMTP id OAA20881; Thu, 6 Aug 1998 14:40:45 -0400 (EDT) Date: Thu, 6 Aug 1998 14:40:45 -0400 (EDT) From: Mark turpin To: FreeBSD Current , FreeBSD hackers Subject: Kernel compile problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I try to compile a GENERIC (-current as of 2:00PM (EDT) Aug 6,1998) kernel I get the following error. Am I doing something wrong? Thanks Mark Turpin cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h ../../scsi/cd.c In file included from ../../scsi/cd.c:48: ioconf.h:11: conflicting types for `fdintr' ../../i386/isa/isa_device.h:155: previous declaration of `fdintr' ioconf.h:11: warning: redundant redeclaration of `fdintr' in same scope ../../i386/isa/isa_device.h:155: warning: previous declaration of `fdintr' ioconf.h:12: conflicting types for `wdintr' ../../i386/isa/isa_device.h:186: previous declaration of `wdintr' ioconf.h:12: warning: redundant redeclaration of `wdintr' in same scope ../../i386/isa/isa_device.h:186: warning: previous declaration of `wdintr' ioconf.h:13: conflicting types for `bt_isa_intr' ../../i386/isa/isa_device.h:146: previous declaration of `bt_isa_intr' ioconf.h:13: warning: redundant redeclaration of `bt_isa_intr' in same scope ../../i386/isa/isa_device.h:146: warning: previous declaration of `bt_isa_intr' ioconf.h:14: conflicting types for `uhaintr' ../../i386/isa/isa_device.h:185: previous declaration of `uhaintr' ioconf.h:14: warning: redundant redeclaration of `uhaintr' in same scope ../../i386/isa/isa_device.h:185: warning: previous declaration of `uhaintr' ioconf.h:15: conflicting types for `ahaintr' ../../i386/isa/isa_device.h:138: previous declaration of `ahaintr' ioconf.h:15: warning: redundant redeclaration of `ahaintr' in same scope ../../i386/isa/isa_device.h:138: warning: previous declaration of `ahaintr' ioconf.h:16: conflicting types for `aicintr' ../../i386/isa/isa_device.h:139: previous declaration of `aicintr' ioconf.h:16: warning: redundant redeclaration of `aicintr' in same scope ../../i386/isa/isa_device.h:139: warning: previous declaration of `aicintr' ioconf.h:17: conflicting types for `ncaintr' ../../i386/isa/isa_device.h:167: previous declaration of `ncaintr' ioconf.h:17: warning: redundant redeclaration of `ncaintr' in same scope ../../i386/isa/isa_device.h:167: warning: previous declaration of `ncaintr' ioconf.h:18: conflicting types for `seaintr' ../../i386/isa/isa_device.h:177: previous declaration of `seaintr' ioconf.h:18: warning: redundant redeclaration of `seaintr' in same scope ../../i386/isa/isa_device.h:177: warning: previous declaration of `seaintr' ioconf.h:19: conflicting types for `wtintr' ../../i386/isa/isa_device.h:189: previous declaration of `wtintr' ioconf.h:19: warning: redundant redeclaration of `wtintr' in same scope ../../i386/isa/isa_device.h:189: warning: previous declaration of `wtintr' ioconf.h:20: conflicting types for `mcdintr' ../../i386/isa/isa_device.h:165: previous declaration of `mcdintr' ioconf.h:20: warning: redundant redeclaration of `mcdintr' in same scope ../../i386/isa/isa_device.h:165: warning: previous declaration of `mcdintr' ioconf.h:23: conflicting types for `scintr' ../../i386/isa/isa_device.h:176: previous declaration of `scintr' ioconf.h:23: warning: redundant redeclaration of `scintr' in same scope ../../i386/isa/isa_device.h:176: warning: previous declaration of `scintr' ioconf.h:24: conflicting types for `npxintr' ../../i386/isa/isa_device.h:168: previous declaration of `npxintr' ioconf.h:24: warning: redundant redeclaration of `npxintr' in same scope ../../i386/isa/isa_device.h:168: warning: previous declaration of `npxintr' ioconf.h:26: conflicting types for `siointr' ../../i386/isa/isa_device.h:178: previous declaration of `siointr' ioconf.h:26: warning: redundant redeclaration of `siointr' in same scope ../../i386/isa/isa_device.h:178: warning: previous declaration of `siointr' ioconf.h:27: conflicting types for `lptintr' ../../i386/isa/isa_device.h:163: previous declaration of `lptintr' ioconf.h:27: warning: redundant redeclaration of `lptintr' in same scope ../../i386/isa/isa_device.h:163: warning: previous declaration of `lptintr' ioconf.h:28: conflicting types for `mseintr' ../../i386/isa/isa_device.h:166: previous declaration of `mseintr' ioconf.h:28: warning: redundant redeclaration of `mseintr' in same scope ../../i386/isa/isa_device.h:166: warning: previous declaration of `mseintr' ioconf.h:29: conflicting types for `psmintr' ../../i386/isa/isa_device.h:173: previous declaration of `psmintr' ioconf.h:29: warning: redundant redeclaration of `psmintr' in same scope ../../i386/isa/isa_device.h:173: warning: previous declaration of `psmintr' ioconf.h:30: conflicting types for `edintr' ../../i386/isa/isa_device.h:150: previous declaration of `edintr' ioconf.h:30: warning: redundant redeclaration of `edintr' in same scope ../../i386/isa/isa_device.h:150: warning: previous declaration of `edintr' ioconf.h:31: conflicting types for `ieintr' ../../i386/isa/isa_device.h:158: previous declaration of `ieintr' ioconf.h:31: warning: redundant redeclaration of `ieintr' in same scope ../../i386/isa/isa_device.h:158: warning: previous declaration of `ieintr' ioconf.h:32: conflicting types for `epintr' ../../i386/isa/isa_device.h:153: previous declaration of `epintr' ioconf.h:32: warning: redundant redeclaration of `epintr' in same scope ../../i386/isa/isa_device.h:153: warning: previous declaration of `epintr' ioconf.h:33: conflicting types for `exintr' ../../i386/isa/isa_device.h:154: previous declaration of `exintr' ioconf.h:33: warning: redundant redeclaration of `exintr' in same scope ../../i386/isa/isa_device.h:154: warning: previous declaration of `exintr' ioconf.h:34: conflicting types for `feintr' ../../i386/isa/isa_device.h:156: previous declaration of `feintr' ioconf.h:34: warning: redundant redeclaration of `feintr' in same scope ../../i386/isa/isa_device.h:156: warning: previous declaration of `feintr' ioconf.h:35: conflicting types for `le_intr' ../../i386/isa/isa_device.h:160: previous declaration of `le_intr' ioconf.h:35: warning: redundant redeclaration of `le_intr' in same scope ../../i386/isa/isa_device.h:160: warning: previous declaration of `le_intr' ioconf.h:36: conflicting types for `lncintr' ../../i386/isa/isa_device.h:161: previous declaration of `lncintr' ioconf.h:36: warning: redundant redeclaration of `lncintr' in same scope ../../i386/isa/isa_device.h:161: warning: previous declaration of `lncintr' ioconf.h:37: conflicting types for `zeintr' ../../i386/isa/isa_device.h:190: previous declaration of `zeintr' ioconf.h:37: warning: redundant redeclaration of `zeintr' in same scope ../../i386/isa/isa_device.h:190: warning: previous declaration of `zeintr' ioconf.h:38: conflicting types for `zpintr' ../../i386/isa/isa_device.h:191: previous declaration of `zpintr' ioconf.h:38: warning: redundant redeclaration of `zpintr' in same scope ../../i386/isa/isa_device.h:191: warning: previous declaration of `zpintr' ioconf.h:39: conflicting types for `csintr' ../../i386/isa/isa_device.h:147: previous declaration of `csintr' ioconf.h:39: warning: redundant redeclaration of `csintr' in same scope ../../i386/isa/isa_device.h:147: warning: previous declaration of `csintr' *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 11:44:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27494 for freebsd-current-outgoing; Thu, 6 Aug 1998 11:44:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27395 for ; Thu, 6 Aug 1998 11:44:29 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (A27Z40emivdhsD7pKkZ6uXTHKwaJ6EA6@localhost [127.0.0.1]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id UAA16782; Thu, 6 Aug 1998 20:41:19 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199808061841.UAA16782@gratis.grondar.za> To: "Jordan K. Hubbard" cc: freebsd@magnet.geophysik.tu-freiberg.de, freebsd-current@FreeBSD.ORG Subject: Re: No More CTM Deltas on ftp.freebsd.org ? Date: Thu, 06 Aug 1998 20:41:16 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > CTM is currently and orphan and looking for a new home. I think Mark > Murray was going to take it over, but I haven't heard anything about > it. Ulf was also running it for awhile but that appears to have > stopped - he might have more to say about it. I am running it ATM - in my copious free time I get to fix that-which-is-broken. I will soon have it where I want it; please be patient. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 11:47:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28352 for freebsd-current-outgoing; Thu, 6 Aug 1998 11:47:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28300 for ; Thu, 6 Aug 1998 11:47:36 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id OAA28205; Thu, 6 Aug 1998 14:48:09 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Thu, 6 Aug 1998 14:48:09 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: Narvi cc: freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG why not build up a list of which pointers were malloc'd instead of that icky hack? -Alfred Perlstein -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- http://www.freebsd.org/ On Thu, 6 Aug 1998, Narvi wrote: > > On Thu, 6 Aug 1998, Bruce Evans wrote: > > > > The problem with fixing setenv() is that you don't know if a pointer was > > >malloced, allocated from the env area above the stack, points to read-only > > >text, points to a static data buffer, etc. There really is no way to know > > >for sure, so you can't free the memory. > > > > Yo can know if you malloced it in a previous call to putenv() or setenv(). > > > > Bruce > > So we could: > > a) allocate a bit more memory than needed > b) set the environment string > c) end it with zero > d) append a certain token after the end of the string saying "ok > to free() me" to anyone knowing what to look at? > > But couldn't a string end at the end of allocated area so that by peeking > behind the final zero we will sometimes cause a SIGSEV? > > Sander > > There is no love, no good, no happiness and no future - > all these are just illusions. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 11:50:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29121 for freebsd-current-outgoing; Thu, 6 Aug 1998 11:50:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28994; Thu, 6 Aug 1998 11:49:50 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (xMZ150oQLtojJutqDgGvaE0JW7skFwDE@localhost [127.0.0.1]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id UAA16918; Thu, 6 Aug 1998 20:47:48 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199808061847.UAA16918@gratis.grondar.za> To: John Hay cc: imp@village.org (Warner Losh), freebsd-ctm@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: CTM checksum errors? Date: Thu, 06 Aug 1998 20:47:47 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Hay wrote: > I don't think it really is an orphan. I think Mark Murray is just > still recovering from his overseas trip and that is probably why > he haven't chipped in yet. At the moment I'm still getting the > output of every ctm generation and there is no problems on that > machine as far as I can see. ...the way it should be! :-) > What I think happened is that we lost the mailing lists again > when hub died. I had to resubscribe to a lot of lists afterwards. That would explain why wcarchive has no CTM's - its entries in the CTM mailing lists got lost? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 11:59:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01516 for freebsd-current-outgoing; Thu, 6 Aug 1998 11:59:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from majestix.kph.uni-mainz.de (majestix.kph.uni-mainz.de [134.93.132.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01434 for ; Thu, 6 Aug 1998 11:59:12 -0700 (PDT) (envelope-from krygier@kph.uni-mainz.de) Received: from localhost (krygier@localhost) by majestix.kph.uni-mainz.de (8.8.8/8.8.8) with ESMTP id UAA13697; Thu, 6 Aug 1998 20:58:34 +0200 (CEST) (envelope-from krygier@kph.uni-mainz.de) X-Authentication-Warning: majestix.kph.uni-mainz.de: krygier owned process doing -bs Date: Thu, 6 Aug 1998 20:58:34 +0200 (CEST) From: Klaus Werner Krygier To: Philippe Regnauld cc: freebsd-current@FreeBSD.ORG Subject: Re: system lock-up (SMP, AHC_TAGENABLE, softupdates) In-Reply-To: <19980802172204.50682@deepo.prosa.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 2 Aug 1998, Philippe Regnauld wrote: > System: GigaByte 586-DX, 2xP5-133, 48MB, on-board 7880 SCSI, > 4GB IBM DCAS-34330W. > Current as of CTM src-cur 3477 (< 48 hours). > > Softupdates enabled on _all_ filesystems: no problem, did > two make buildworlds/installworld in a row, as long > as AHC_TAGENABLE is off. > > If I enable AHC_TAGENABLE, and push the system a bit (lots > of FS activity) -> freeze. Last time it happened was with X, > so I'd have to do it again in text mode to write down the AHC > TAG messages... I have a very similar hardware setup on several machines (Gigabyte 586-DX, 2 x P5-200, 64 MB, on-board 7880 SCSI, several different disks (2GB, 4GB, 9GB)) and I have the same problems: If I do a lot of disk activity my computers freeze. Sometimes a SCSI bus reset seems to be initiated (which I can recogize on the loading activity of my CD changer). This problem occurs on standard 3.0-SNAP kernels without softupdates and almost SMP-GENERIC configuration. I tried several SNAPs, but the problem remained - I have the impression it has become worse with newe versions :-(. At last I damaged one of my disks. My last hope was CAM. Here (3.0CAM-19980712-SNAP) the system does not freeze completely but becomes very slow on disk access and is also not usable. One positive aspect: I get kernel messages. Every few seconds the following message is printed out for ever: Timedout SCB handled by another timeout Timedout SCB handled by another timeout last message repeated 4 times last message repeated 13 times last message repeated 30 times Timedout SCB handled by another timeout Timedout SCB handled by another timeout etc. With older 3.0-SNAPs (e.g. May 97) a SMP system was very stable on my first board and did not show such effects for almost a year. Because of other problems and to use new features and improvements I had to upgrade and have now very instable systems. Klaus Werner Krygier +-----------------------------------------------------------------------+ | Dr. Klaus Werner Krygier | Email: krygier@kph.uni-mainz.de | | Institut für Kernphysik | | | Johannes Gutenberg-Universität | Tel: +49-6131-39-2960 | | J.J.Becher-Weg 45 | +49-6131-39-5868 | | D-55099 Mainz | Fax: +49-6131-39-2964 | +-----------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 12:05:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02834 for freebsd-current-outgoing; Thu, 6 Aug 1998 12:05:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA02723 for ; Thu, 6 Aug 1998 12:05:21 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z4VKj-0002RD-00; Thu, 6 Aug 1998 12:04:17 -0700 Date: Thu, 6 Aug 1998 12:04:15 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Eivind Eklund cc: Andrew Reilly , current@FreeBSD.ORG Subject: Re: Heads up on LFS In-Reply-To: <19980806203555.56458@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Aug 1998, Eivind Eklund wrote: > > and all other services that would normally be in the kernel are in their > > own address spaces, using strict IPC interfaces between modules. > > Being able to develop device drivers without expecting your macine to hang > is actually very neat :-) Yep, and apparently you can load, unload, and replace drivers on the fly too. It would be great to be able to upgrade the TCP/IP stack without rebooting, for example. > Eivind. > > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 13:01:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15239 for freebsd-current-outgoing; Thu, 6 Aug 1998 13:01:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15202 for ; Thu, 6 Aug 1998 13:01:05 -0700 (PDT) (envelope-from reilly@zeta.org.au) Received: from zeta.org.au (d4.syd2.zeta.org.au [203.26.11.4]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id GAA08612 for ; Fri, 7 Aug 1998 06:00:42 +1000 Received: (qmail 6681 invoked by uid 1000); 6 Aug 1998 09:09:48 -0000 Message-ID: <19980806090948.6680.qmail@gurney.reilly.home> From: "Andrew Reilly" Date: Thu, 6 Aug 1998 19:09:48 +1000 (EST) Subject: Spin-type OS issues, was: Re: Heads up on LFS To: tlambert@primenet.com cc: tom@uniserve.com, current@FreeBSD.ORG In-Reply-To: <199808060606.XAA22855@usr09.primenet.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My apologies for starting a language discussion. That was not my intention. I just thought that I would point out that I thought the interesting thing about Spin was not that it was written in Modula-3, but rather that the designers were trying to avoid the overhead of process-to-kernel virtual address translation by keeping both the kernel, the extensions, and the user processes in the one address space. (Yes, just like MacOS and Win3.1...) It seemed to me that they were trying to do this _safely_ by pushing the checks that prevent processes from diddling with data that didn't belong to them into the system compiler, resolved at compile time, rather than using the more traditional approach of physically segregating the address spaces. Obviously, forcing the use of a particular compiler for an otherwise niche language is going to limit the practical usefulness: no-one is likely to re-write perl or vi in Modula-3, for example.[1] My point was that some other attempts to use a uniform virtual address space have been attempted, with some hardware support in the form of read-only or no-access regions of the memory map. This still requires that you change protection maps on user/kernel boundary transitions, but a) you still avoid the need to walk tables to convert pointer arguments from one domain to the other. b) The hardware memory protection can be designed to make this more efficient, by associating process IDs (or a mapped working subset of same) with the protection mappings. I believe that the ARM MMU in the Newton was something like this, and that the memory hardware in AS400 systems has much the same effect. (Don't SPARC MMUs have a process ID in the context too?) None of that is particularly relevant to FreeBSD (at least until we try a port to "odd" platforms like those), but it is interesting to see how other folk are approaching OS design. [1] I suppose you could write a "safe C" compiler that nominally did range checking on all pointer references, and prevented access to regions that weren't explicitly passed to you by the operating system. That means that the compiler would have to have intimate knowledge of sbrk and mmap, and would have to work very hard to optimise away most of those checks. Does anyone know if such a compiler has been built? How about the "C on JVM" efforts? -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 13:16:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18632 for freebsd-current-outgoing; Thu, 6 Aug 1998 13:16:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coleridge.kublai.com (coleridge.kublai.com [207.96.1.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18574 for ; Thu, 6 Aug 1998 13:16:20 -0700 (PDT) (envelope-from shmit@coleridge.kublai.com) Received: (from shmit@localhost) by coleridge.kublai.com (8.8.8/8.8.8) id QAA12266; Thu, 6 Aug 1998 16:15:56 -0400 (EDT) (envelope-from shmit) Message-ID: <19980806161553.44240@kublai.com> Date: Thu, 6 Aug 1998 16:15:53 -0400 From: Brian Cully To: "Daniel M. Eischen" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Pthreads woes revisited. Reply-To: shmit@kublai.com Mail-Followup-To: "Daniel M. Eischen" , freebsd-current@FreeBSD.ORG References: <35C9ED3D.41C67EA6@vigrid.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <35C9ED3D.41C67EA6@vigrid.com>; from Daniel M. Eischen on Thu, Aug 06, 1998 at 01:51:57PM -0400 X-Sender: If your mailer pays attention to this, it's broken. X-PGP-Info: finger shmit@kublai.com for my public key. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 06, 1998 at 01:51:57PM -0400, Daniel M. Eischen wrote: > But your not yielding the CPU after the pthread_cond_signal(). > The waiter thread (thr_wait) should also take the mutex lock (busy) > before the pthread_cond_wait(). See the comments in the revised > copy of your code. >From what I can tell by looking at uthread_mutex.c:pthread_mutex_unlock() and uthread_cond.c:pthread_cond_wait(), I don't have to lock the mutex before calling pthread_cond_wait(). Regardless, I tried adding the extra pthread_mutex_lock() call, and things still fail in the same manner. Moreover, the fact that the location of the sleep() call makes a difference points to something more sinister. -bjc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 14:13:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04562 for freebsd-current-outgoing; Thu, 6 Aug 1998 14:13:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04456 for ; Thu, 6 Aug 1998 14:12:42 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id RAA18177; Thu, 6 Aug 1998 17:13:02 -0400 (EDT) Date: Thu, 6 Aug 1998 17:13:02 -0400 (EDT) From: Daniel Eischen Message-Id: <199808062113.RAA18177@pcnet1.pcnet.com> To: eischen@vigrid.com, shmit@kublai.com Subject: Re: Pthreads woes revisited. Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Aug 06, 1998 at 01:51:57PM -0400, Daniel M. Eischen wrote: > > But your not yielding the CPU after the pthread_cond_signal(). > > The waiter thread (thr_wait) should also take the mutex lock (busy) > > before the pthread_cond_wait(). See the comments in the revised > > copy of your code. > > From what I can tell by looking at uthread_mutex.c:pthread_mutex_unlock() > and uthread_cond.c:pthread_cond_wait(), I don't have to lock the mutex > before calling pthread_cond_wait(). True, the source for pthread_cond_wait ignores any error code returned by pthread_mutex_lock(). I don't know if this behaviour is defined in the POSIX spec (for whatever rev we're currently supporting), but the intended use is to acquire the mutex before the cond_wait/cond_timedwait. You're not adding the pthread_yield() call that I added after the pthread_cond_signal(). Your program is bogus because there is no guarantee that the main thread will release the CPU in order for the other task to run. You need to perform some sort of blocking operation after the pthread_cond_signal. I chose to use pthread_yield, although sleep would work just as well. Furthermore, thr_routine() will never return from the pthread_cond_wait() unless the busy mutex is available. You're main thread is taking the mutex before the sleep and releasing it after the sleep. There is no way that thr_routine can wakeup because it needs to acquire the busy mutex in order to return from the pthread_cond_wait(). Look: (from thr_routine) printf("%d: Waiting for signal.\n", (int) pthread_self ()); rc = pthread_cond_wait(&wakeup, &busy); if (rc) { fprintf(stderr, "ERROR: couldn't wait for condition: %s.\n", strerror(rc)); return NULL; } (from main) printf("MASTER: Acquiring lock.\n"); rc = pthread_mutex_lock(&busy); if (rc) { fprintf(stderr, "ERROR: couldn't lock mutex: %s.\n", strerror(rc)); return 1; } sleep(1); printf("MASTER: Releasing lock.\n"); rc = pthread_mutex_unlock(&busy); Sleeping while holding the mutex will obviously not allow the other thread to run. When the main thread returns from the sleep, it will run until its time quantum expires, preempted, or blocks (perhaps signals can affect it too?). I ran the same test on Solaris and the main thread *never* yielded the processor to the other thread until I placed a pthread_yield (sched_yield) after the pthread_cond_signal. Please try adding some sort of blocking operation after the pthread_cond_signal in the main thread. If you do not want to use pthread_yield(), then use sleep, select, or anything that will block the main thread. I suspect that you want the thread to run while the main thread is sleeping. If that is the case, then you must use another mutex in the main thread. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 14:18:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06153 for freebsd-current-outgoing; Thu, 6 Aug 1998 14:18:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05990 for ; Thu, 6 Aug 1998 14:17:50 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id XAA02604; Thu, 6 Aug 1998 23:15:07 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.1/8.9.1) id WAA20825; Thu, 6 Aug 1998 22:21:43 +0200 (CEST) (envelope-from andreas) Message-ID: <19980806222143.A17976@klemm.gtn.com> Date: Thu, 6 Aug 1998 22:21:43 +0200 From: Andreas Klemm To: Terry Lambert , Tom Cc: ken@plutotech.com, current@FreeBSD.ORG Subject: Re: Heads up on LFS References: <199808050801.BAA21512@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808050801.BAA21512@usr02.primenet.com>; from Terry Lambert on Wed, Aug 05, 1998 at 08:01:50AM +0000 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 05, 1998 at 08:01:50AM +0000, Terry Lambert wrote: > The device driver layer of x86-SPIN utilizes code from the > FreeBSD Operating System. For this reason SPIN has to be > booted on a machine that has a FreeBSD file system. We get ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > this by doing a minimal install of FreeBSD on the x86 machines > where SPIN will be run. In addition we have a boot loader > program (salboot.com) that runs either from a dos partition > on the disk or from a floppy. > > For historic reasons x86-SPIN needs to be built on a Linux ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > machine. It may be possible to build x86-SPIN in a different > posix environment but we have not attempted this and couldn't > provide help if you ran into problems. In order to build the > FreeBSD portions of SPIN on Linux, some cross development ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > tools are required. Sources for these tools are available as > a single file (bsdtools.tar.gz) here at our site. Sounds a bit sick ;-) We should make a FreeBSD port ;-)) -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 15:02:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12066 for freebsd-current-outgoing; Thu, 6 Aug 1998 14:37:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11857 for ; Thu, 6 Aug 1998 14:36:32 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id OAA06591; Thu, 6 Aug 1998 14:36:09 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd006564; Thu Aug 6 14:36:04 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id OAA24396; Thu, 6 Aug 1998 14:36:00 -0700 (MST) From: Terry Lambert Message-Id: <199808062136.OAA24396@usr07.primenet.com> Subject: Re: Spin-type OS issues, was: Re: Heads up on LFS To: reilly@zeta.org.au (Andrew Reilly) Date: Thu, 6 Aug 1998 21:36:00 +0000 (GMT) Cc: tlambert@primenet.com, tom@uniserve.com, current@FreeBSD.ORG In-Reply-To: <19980806090948.6680.qmail@gurney.reilly.home> from "Andrew Reilly" at Aug 6, 98 07:09:48 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just thought that I would point out that I thought the > interesting thing about Spin was not that it was written in Modula-3, > but rather that the designers were trying to avoid the overhead of > process-to-kernel virtual address translation by keeping both the > kernel, the extensions, and the user processes in the one address > space. (Yes, just like MacOS and Win3.1...) > > It seemed to me that they were trying to do this _safely_ by pushing > the checks that prevent processes from diddling with data that didn't > belong to them into the system compiler, resolved at compile time, > rather than using the more traditional approach of physically > segregating the address spaces. A more clever approach than this is the Chorus approach, which tends to limit protection domain crossing. Another clever approach that is becoming less useful as time goes on, and which is insufficient for security reasons is statistical protection in a very large address space. This works by making it a 1 in 2^32 chance (for a 32 bit allocation space within a 64 bit address space) for you to get a valid page at random. Thus there is no need to cross protection domains. This approach fails in the case of intentional acts of sabotage (ie: a determined attack, which is not a possible failure mode in normal operation). Another approach that is rather clever, but which requires protection domains is encapsulation, either via Capabilites (as in EROS) or via process encapsulation (as in Flux). 8-). I rather like the statistical protection model. You could pretty much represent all of the RAM on the Internet today as a 96 bit address, with a minimally 1 in 32 bit chance of a protection violation. This is a rather nifty idea... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 15:14:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19418 for freebsd-current-outgoing; Thu, 6 Aug 1998 15:14:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from plunger.gdeb.com (plunger.gdeb.com [153.11.11.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19408 for ; Thu, 6 Aug 1998 15:14:31 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from clcrtr.clc.gdeb.com ([153.11.109.11]) by plunger.gdeb.com with ESMTP (1.37.109.16/CSC-E_1.8) id AA194171626; Thu, 6 Aug 1998 18:13:46 -0400 Received: from clcrtr.clc.gdeb.com (clcrtr [153.11.109.129]) by clcrtr.clc.gdeb.com (8.8.8/8.7.3) with SMTP id SAA09802; Thu, 6 Aug 1998 18:11:01 -0400 (EDT) Message-Id: <35CA29F5.41C67EA6@vigrid.com> Date: Thu, 06 Aug 1998 18:11:01 -0400 From: "Daniel M. Eischen" X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.6-STABLE i386) Mime-Version: 1.0 To: eischen@vigrid.com, shmit@kublai.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Pthreads woes revisited. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I (Daniel Eischen) wrote: > > (from main) > printf("MASTER: Acquiring lock.\n"); > rc = pthread_mutex_lock(&busy); > if (rc) { > fprintf(stderr, "ERROR: couldn't lock mutex: %s.\n", > strerror(rc)); > return 1; > } > > sleep(1); > > printf("MASTER: Releasing lock.\n"); > rc = pthread_mutex_unlock(&busy); > > Sleeping while holding the mutex will obviously not allow the > other thread to run. When the main thread returns from the sleep, > it will run until its time quantum expires, preempted, or blocks > (perhaps signals can affect it too?). I ran the same test on > Solaris and the main thread *never* yielded the processor to the > other thread until I placed a pthread_yield (sched_yield) after > the pthread_cond_signal. > > Please try adding some sort of blocking operation after the > pthread_cond_signal in the main thread. If you do not want to > use pthread_yield(), then use sleep, select, or anything that > will block the main thread. > > I suspect that you want the thread to run while the main thread > is sleeping. If that is the case, then you must use another mutex > in the main thread. Instead of using sleep, use pthread_cond_timedwait with a timeout of 1 sec. This will release the busy mutex and let the other thread run: int main(int argc, char *argv[]) { int rc; pthread_t thread_id; pthread_cond_t sleep_cv; struct timespec ts; rc = pthread_cond_init(&wakeup, NULL); if (rc == 0) rc = pthread_cond_init(&sleep_cv, NULL); if (rc) { fprintf(stderr, "ERROR: couldn't create condition variables: %s.\n", strerror(rc)); return 1; } rc = pthread_mutex_init(&busy, NULL); if (rc) { fprintf(stderr, "ERROR: couldn't create mutex: %s.\n", strerror(rc)); return 1; } rc = pthread_create(&thread_id, NULL, thr_routine, NULL); if (rc) { fprintf(stderr, "ERROR: couldn't create thread: %s.\n", strerror(rc)); return 1; } for (;;) { printf("MASTER: Acquiring lock.\n"); rc = pthread_mutex_lock(&busy); if (rc) { fprintf(stderr, "ERROR: couldn't lock mutex: %s.\n", strerror(rc)); return 1; } clock_gettime (CLOCK_REALTIME, &ts); ts.tv_sec++; rc = pthread_cond_timedwait (&sleep_cv, &busy, &ts); if (rc != 0 && rc != ETIMEDOUT) { fprintf(stderr, "ERROR: pthread_cond_wait failed: %s.\n", strerror(rc)); return 1; } printf("MASTER: Releasing lock.\n"); rc = pthread_mutex_unlock(&busy); if (rc) { fprintf(stderr, "ERROR: couldn't unlock mutex: %s.\n", strerror(rc)); return 1; } printf("MASTER: Sending signal.\n"); rc = pthread_cond_signal(&wakeup); if (rc) { fprintf(stderr, "ERROR: couldn't signal thread: %s.\n", strerror(rc)); return 1; } } return 0; } Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 15:39:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24025 for freebsd-current-outgoing; Thu, 6 Aug 1998 15:39:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24006 for ; Thu, 6 Aug 1998 15:39:02 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id IAA02167; Fri, 7 Aug 1998 08:44:09 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808062244.IAA02167@cimlogic.com.au> Subject: Re: Pthreads woes revisited. In-Reply-To: <19980806130122.38511@kublai.com> from Brian Cully at "Aug 6, 98 01:01:22 pm" To: shmit@kublai.com Date: Fri, 7 Aug 1998 08:44:08 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Cully wrote: > I've put together a small C program that demonstrates the problems > I described in my last message. You can find the program attached > to this message. > > Note the location of the `sleep(1)' call, it's important. If it moves > outside of the mutex lock/unlock bits, everything functions normally, > but if it gets called after the lock, but before the unlock, the first > signal is missed. Mutexes can be implemented with spinlocks so that a thread that is blocked trying to lock a mutex will burn CPU and only when it exceeds it's time slice will it be interrupted to allow another thread to run. For this reason, mutexes should only be used to gain exclusive access to something and a condition variable should be used to wait. The mutex associated with the condition variable _must_ be locked prior to calling the cond_wait function. The cond_wait function will queue the calling thread and unlock the mutex. When the condition variable is signalled, a waiting thread is granted access by locking the mutex just before the cond_wait function returns. The woken thread should do what it needs to do quickly, then unlock the mutex or wait again (causing the mutex to be unlocked). More than one thread may be woken, but only one will get access to the mutex - all the rest will burn CPU, so each thread must unlock the mutex as quickly as possible. Signalling a condition variable only serves to wake any thread that might be waiting. If a thread hasn't called a cond_wait function, it won't be in a position to be woken by the signal. The thread should not be coded to use the occurrence of a signal as the driving event. Instead there should be a variable that is protected by the mutex that is changed to be used as the event data. The thread that is being driven by this data then locks the mutex, checks the variable and if there is no event data there, it calls the cond_wait. If there _is_ data already there (as the result of another thread getting there before it), no wait is necessary and the thread just unlocks the mutex and goes about it's business. If you need to buffer more than one event, then the event variable needs to be an array or a list. Whatever the variable is, it must only be accessed (both read and write) with the mutex locked. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 16:09:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29209 for freebsd-current-outgoing; Thu, 6 Aug 1998 16:09:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcpsj.pfcs.com (harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29200 for ; Thu, 6 Aug 1998 16:09:13 -0700 (PDT) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Thu, 6 Aug 1998 19:08:36 -0400 (EDT) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Thu, 6 Aug 1998 16:08:34 -0700 (PDT) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Thu, 6 Aug 1998 19:08:34 -0400 (EDT) X-Mailer: exmh version 2.0.2 2/24/98 To: Nathan Ahlstrom cc: Mike Smith , current@FreeBSD.ORG Subject: Re: New bootstrap config file(s) (Re: booting with verbosity by default? ) In-Reply-To: Nathan Ahlstrom's (nrahlstr@winternet.com) message dated Thu, 06 Aug 1998 12:16:05. X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Aug 1998 19:08:33 -0400 Message-ID: <583.902444913@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Possible Stupid Question Alert: What's with /stand, and why not use it instead of /boot? H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 16:12:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29930 for freebsd-current-outgoing; Thu, 6 Aug 1998 16:12:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29849 for ; Thu, 6 Aug 1998 16:12:14 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA00813; Thu, 6 Aug 1998 16:09:37 -0700 (PDT) Message-Id: <199808062309.QAA00813@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Harlan Stenn cc: Nathan Ahlstrom , Mike Smith , current@FreeBSD.ORG Subject: Re: New bootstrap config file(s) (Re: booting with verbosity by default? ) In-reply-to: Your message of "Thu, 06 Aug 1998 19:08:33 EDT." <583.902444913@brown.pfcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Aug 1998 16:09:37 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Possible Stupid Question Alert: > > What's with /stand, and why not use it instead of /boot? /stand typically contains leftovers from the installation. There's nothing inherently wrong with putting bootstrap stuff in there except that it's already cluttered. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 16:20:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01454 for freebsd-current-outgoing; Thu, 6 Aug 1998 16:20:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01381 for ; Thu, 6 Aug 1998 16:19:34 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-129.camalott.com [208.229.74.129]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id SAA19917; Thu, 6 Aug 1998 18:20:19 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id SAA01218; Thu, 6 Aug 1998 18:18:56 -0500 (CDT) (envelope-from joelh) Date: Thu, 6 Aug 1998 18:18:56 -0500 (CDT) Message-Id: <199808062318.SAA01218@detlev.UUCP> To: mike@smith.net.au CC: ben@rosengart.com, dacole@netcom.ca, current@FreeBSD.ORG In-reply-to: <199808061544.IAA03196@antipodes.cdrom.com> (message from Mike Smith on Thu, 06 Aug 1998 08:44:07 -0700) Subject: Re: New bootstrap config file(s) (Re: booting with verbosity by default? ) From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808061544.IAA03196@antipodes.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>> I would like to force my systems to always boot with '-v'.. Is there >>>> any way to do this without operator intervention? >>> Take a look at what boot(8) has to say about /boot.config. >> It says that -v doesn't make the cut for boot.config. The fix is >> trivial, but I haven't yet rolled a pr. > It will become either "-v" in /boot.config or "set bootverbose" in > the new bootstrap config, which I haven't named. Sorry, hadn't heard about it. Haven't been keeping up too closely these last few weeks. > And this is a handy topic to raise it under; the new bootstrap will > (optionally) need access to quite a few files, and we may not really > want these cluttering up the root directory. How do people feel > about a /boot directory these days? Aye. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 16:23:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02127 for freebsd-current-outgoing; Thu, 6 Aug 1998 16:23:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02002 for ; Thu, 6 Aug 1998 16:22:47 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-129.camalott.com [208.229.74.129]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id SAA20099; Thu, 6 Aug 1998 18:23:19 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id SAA01224; Thu, 6 Aug 1998 18:21:56 -0500 (CDT) (envelope-from joelh) Date: Thu, 6 Aug 1998 18:21:56 -0500 (CDT) Message-Id: <199808062321.SAA01224@detlev.UUCP> To: nate@mt.sri.com CC: tlambert@primenet.com, reilly@zeta.org.au, tom@uniserve.com, current@FreeBSD.ORG In-reply-to: <199808061438.IAA12182@mt.sri.com> (message from Nate Williams on Thu, 6 Aug 1998 08:38:27 -0600) Subject: Re: Heads up on LFS From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <19980806112955.A4299@reilly.home> <199808060606.XAA22855@usr09.primenet.com> <199808061438.IAA12182@mt.sri.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I know, I've tried and have benchmarks to prove it. Using 100% of > the CPU for minutes at a time, I still get the GC kicking in using > Sun's JVM implementation. (The M$ implementation is notorious for > doing bad things since it uses a different reaping technology, so > it's much less useful for programs that make heavy use of 'new'.) Is there some sort of irony in M$ not working well with memory-hungry programs? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 18:02:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20086 for freebsd-current-outgoing; Thu, 6 Aug 1998 18:02:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ixion.honeywell.com (ixion.honeywell.com [129.30.4.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20081; Thu, 6 Aug 1998 18:02:15 -0700 (PDT) (envelope-from sleas@ixion.honeywell.com) Received: from localhost by ixion.honeywell.com with SMTP (1.40.112.8/16.2) id AA237921702; Thu, 6 Aug 1998 20:01:42 -0500 Date: Thu, 6 Aug 1998 20:01:42 -0500 (CDT) From: Shawn Leas To: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: I unsubed, but I'm still getting msgs! Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will someone take me off? I have already unsubbed, and authed, AND gotten confirmation, but CONTINUE to get messages. -Shawn <=========== America Held Hostage ===========> Day 2024 for the poor and the middle class. Day 2043 for the rich and the dead. 898 days remaining in the Raw Deal. <============================================> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 18:23:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22713 for freebsd-current-outgoing; Thu, 6 Aug 1998 18:23:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22708 for ; Thu, 6 Aug 1998 18:23:58 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id SAA27698; Thu, 6 Aug 1998 18:23:39 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma027692; Thu Aug 6 18:23:27 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id SAA26723; Thu, 6 Aug 1998 18:23:27 -0700 (PDT) From: Archie Cobbs Message-Id: <199808070123.SAA26723@bubba.whistle.com> Subject: Re: memory leaks in libc In-Reply-To: <199808061723.DAA02057@godzilla.zeta.org.au> from Bruce Evans at "Aug 7, 98 03:23:29 am" To: bde@zeta.org.au (Bruce Evans) Date: Thu, 6 Aug 1998 18:23:27 -0700 (PDT) Cc: bde@zeta.org.au, wollman@khavrinen.lcs.mit.edu, dg@root.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > >So you both agree, then, that there is no point in wasting any more > >time on this? > > Not quite. It should be fixed someday. As the person who originally brought up this bug about 6 months ago, I agree with Bruce.. it should be fixed. I'm a little puzzeled as to why Garrett keeps wanting to sweep it under the rug. The idea of keeping a hash table of pointers that were gotten via malloc() is simple enough. It would solve the problem for programs than need it (a real world example of which exists at Whistle). For programs that don't do a lot of putenv()/setenv(), which is most programs, there would be no difference. In fact, we can optimize for this common case, which is NO calls to putenv()/setenv(), by not creating the hash table at all. Now all we need is some enterprising soul to come up with the patch... -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 18:34:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24501 for freebsd-current-outgoing; Thu, 6 Aug 1998 18:34:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24460 for ; Thu, 6 Aug 1998 18:34:09 -0700 (PDT) (envelope-from reilly@zeta.org.au) Received: from zeta.org.au (d18.syd2.zeta.org.au [203.26.11.18]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id LAA30518 for ; Fri, 7 Aug 1998 11:33:47 +1000 Received: (qmail 9802 invoked by uid 1000); 7 Aug 1998 01:02:43 -0000 From: "Andrew Reilly" Message-ID: <19980807110243.A9734@reilly.home> Date: Fri, 7 Aug 1998 11:02:43 +1000 To: Bruce Evans , wollman@khavrinen.lcs.mit.edu Cc: dg@root.com, freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc References: <199808061723.DAA02057@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808061723.DAA02057@godzilla.zeta.org.au>; from Bruce Evans on Fri, Aug 07, 1998 at 03:23:29AM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 07, 1998 at 03:23:29AM +1000, Bruce Evans wrote: > >So you both agree, then, that there is no point in wasting any more > >time on this? > > Not quite. It should be fixed someday. I always thought it odd that there were no implimentations of free() that were able to identify whether the pointer that they were passed was something that malloc had handed out previously. Surely malloc's data structures must have something to say about it. If free() could know this, then things like setenv could just go ahead and call free(), and if the previous object had not been malloc'ed then nothing would happen. What _does_ happen now if you do free("foo") ? Answering my own question with a small experiment: the free routine prints this message to stderr: foo in free(): warning: junk pointer, too low to make sense. Is there any way to turn the message off, and rely on the benign behaviour? -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 18:43:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26293 for freebsd-current-outgoing; Thu, 6 Aug 1998 18:43:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shidahara1.planet.kobe-u.ac.jp (shidahara1.planet.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26253 for ; Thu, 6 Aug 1998 18:43:18 -0700 (PDT) (envelope-from takawata@shidahara1.planet.kobe-u.ac.jp) From: takawata@shidahara1.planet.kobe-u.ac.jp Received: from libr.scitec.kobe-u.ac.jp (cs22209.ppp.infoweb.or.jp [202.219.171.25]) by shidahara1.planet.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id JAA11535 for ; Fri, 7 Aug 1998 09:37:39 +0900 (JST) Received: from libr (localhost [127.0.0.1]) by libr.scitec.kobe-u.ac.jp (8.8.4/3.5Wpl7) with ESMTP id JAA04285 for ; Fri, 7 Aug 1998 09:43:18 +0900 (JST) Message-Id: <199808070043.JAA04285@libr.scitec.kobe-u.ac.jp> To: freebsd-current@FreeBSD.ORG Subject: Re: About VCD (raw data reading) In-reply-to: Your message of "Thu, 06 Aug 1998 11:07:20 MST." Date: Fri, 07 Aug 1998 09:43:17 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Thu, 6 Aug 1998, s$B$t(B k X$B+H(B wrote: > >> >> I'd got http://www.mahoroba.ne.jp/~naoya/archives/vcdr.tar.gz >> and patched, but it seems not working.... >> >> [AlanSung@ttyp1(SungSung)][/usr/tmp] >./vcdr /dev/cd0c 2 >> Can't read RAW data.  It seems that the patch only works on *ATAPI*. And on SCSI, the way to read RAW data is VARIOUS. >> Is there any new patch for 3.0-CURRENT? >> my cdrom is TEAC 532S > >What raw data are you trying to read? The page is in Japanese so I can't >figure out how this functionality is different from tosha/cdd. The different is that it reads RAW sector , not CDDA ,and check each sector whether the sector is VideoCD sector or not,as 'xreadvcd' does. Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 18:46:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27055 for freebsd-current-outgoing; Thu, 6 Aug 1998 18:46:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27000 for ; Thu, 6 Aug 1998 18:46:02 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA10235; Thu, 6 Aug 1998 18:42:30 -0700 (PDT) Message-Id: <199808070142.SAA10235@implode.root.com> To: "Andrew Reilly" cc: Bruce Evans , wollman@khavrinen.lcs.mit.edu, freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-reply-to: Your message of "Fri, 07 Aug 1998 11:02:43 +1000." <19980807110243.A9734@reilly.home> From: David Greenman Reply-To: dg@root.com Date: Thu, 06 Aug 1998 18:42:30 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Fri, Aug 07, 1998 at 03:23:29AM +1000, Bruce Evans wrote: >> >So you both agree, then, that there is no point in wasting any more >> >time on this? >> >> Not quite. It should be fixed someday. > >I always thought it odd that there were no implimentations of >free() that were able to identify whether the pointer that they >were passed was something that malloc had handed out previously. >Surely malloc's data structures must have something to say about >it. > >If free() could know this, then things like setenv could just go >ahead and call free(), and if the previous object had not been >malloc'ed then nothing would happen. If the string were malloced by the program (as opposed to the library), then it won't be expecting setenv() to do a hidden free(). This could lead to random memory corruption if the process modifies the freed memory. In all of this dicussion, I can't stop thinking that the cure sounds far worse than the disease. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 18:46:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27309 for freebsd-current-outgoing; Thu, 6 Aug 1998 18:46:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27277 for ; Thu, 6 Aug 1998 18:46:43 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id SAA08445; Thu, 6 Aug 1998 18:46:25 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp03.primenet.com, id smtpd008412; Thu Aug 6 18:46:19 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id SAA25783; Thu, 6 Aug 1998 18:46:10 -0700 (MST) From: Terry Lambert Message-Id: <199808070146.SAA25783@usr06.primenet.com> Subject: Re: memory leaks in libc To: nate@mt.sri.com (Nate Williams) Date: Fri, 7 Aug 1998 01:46:10 +0000 (GMT) Cc: dg@root.com, narvi@haldjas.folklore.ee, bde@zeta.org.au, freebsd@xaa.iae.nl, freebsd-current@FreeBSD.ORG In-Reply-To: <199808061447.IAA12240@mt.sri.com> from "Nate Williams" at Aug 6, 98 08:47:45 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The problem with fixing setenv() is that you don't know if a pointer > > was malloced, allocated from the env area above the stack, points to > > read-only text, points to a static data buffer, etc. There really is > > no way to know for sure, so you can't free the memory. [ ... ] > > You can know if you malloced it in a previous call to putenv() or setenv(). [ ... ] > > Perhaps Bruce is suggesting that a seperate array be allocated to keep > > track of whether or not an env pointer was malloced? This would be very > > costly and, IMO, not worth it considering how rarely memory is lost by > > not freeing previously malloced strings. > > Very costly? Could you do almost all of it in the userland libraries, > and would be pretty cost-free, especially considering it would only have > much effect if the user did lots of environment allocations? The easiest thing to do would be to, in crt0.o, set another envp (__envp?) to point to the the original envp. If they are not equal, then you realloc the space. Frankly, I'd rather just hang the think of the proc struct. It's the non-opaque accesses and the execve(2) insistance on an envp in a non-opaque format that screw you. You can still implement it, but you have to tread a fine line to do it. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 18:49:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27995 for freebsd-current-outgoing; Thu, 6 Aug 1998 18:49:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27963 for ; Thu, 6 Aug 1998 18:49:15 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id SAA16836; Thu, 6 Aug 1998 18:48:58 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp02.primenet.com, id smtpd016759; Thu Aug 6 18:48:51 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id SAA25886; Thu, 6 Aug 1998 18:48:46 -0700 (MST) From: Terry Lambert Message-Id: <199808070148.SAA25886@usr06.primenet.com> Subject: Re: Heads up on LFS To: nate@mt.sri.com (Nate Williams) Date: Fri, 7 Aug 1998 01:48:46 +0000 (GMT) Cc: tlambert@primenet.com, reilly@zeta.org.au, tom@uniserve.com, current@FreeBSD.ORG In-Reply-To: <199808061438.IAA12182@mt.sri.com> from "Nate Williams" at Aug 6, 98 08:38:27 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > JAVA has a nasty tendency to leak like a sieve until the GC hits a > > steady state. As does Modula 3. > > You've *got* to be kidding, right? Do you have any idea how often the > GC collection pass is run? It would be *very* difficult in real world > programs to leak any signficicant (~1MB) of memory before the GC phase > kicked in. Your and my definitions of significant differ. For an embedded use, 1M is way, way too large. Most Palm pilots simply don't have that much memory to be abole to afford to leak that much. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 18:52:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28914 for freebsd-current-outgoing; Thu, 6 Aug 1998 18:52:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28851 for ; Thu, 6 Aug 1998 18:52:31 -0700 (PDT) (envelope-from reilly@zeta.org.au) Received: from zeta.org.au (d18.syd2.zeta.org.au [203.26.11.18]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id LAA32046 for ; Fri, 7 Aug 1998 11:52:08 +1000 Received: (qmail 10204 invoked by uid 1000); 7 Aug 1998 01:51:15 -0000 Message-ID: <19980807015115.10203.qmail@gurney.reilly.home> From: "Andrew Reilly" Date: Fri, 7 Aug 1998 11:51:15 +1000 (EST) Subject: Re: memory leaks in libc To: dg@root.com cc: bde@zeta.org.au, wollman@khavrinen.lcs.mit.edu, freebsd-current@FreeBSD.ORG In-Reply-To: <199808070142.SAA10235@implode.root.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman said: >>I always thought it odd that there were no implimentations of >>free() that were able to identify whether the pointer that they >>were passed was something that malloc had handed out previously. >>Surely malloc's data structures must have something to say about >>it. >> >>If free() could know this, then things like setenv could just go >>ahead and call free(), and if the previous object had not been >>malloc'ed then nothing would happen. > > If the string were malloced by the program (as opposed to the library), > then it won't be expecting setenv() to do a hidden free(). This could lead > to random memory corruption if the process modifies the freed memory. > In all of this dicussion, I can't stop thinking that the cure sounds far > worse than the disease. And yet it is a problem that I've never read a really good solution for. I read a comment on comp.lang.eiffel recently, about BeOS. Apparently they (the BeOS designers) have devised a protocol that goes by the name "wean/adopt", that is presumably about passing "ownership" of dynamically allocated objects around. Anyone know any details? Is it something that can be adopted here? -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 18:55:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29520 for freebsd-current-outgoing; Thu, 6 Aug 1998 18:55:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29464 for ; Thu, 6 Aug 1998 18:54:56 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA23758; Fri, 7 Aug 1998 11:24:12 +0930 (CST) Message-Id: <199808070154.LAA23758@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: joelh@gnu.org, ben@rosengart.com, dacole@netcom.ca, current@FreeBSD.ORG Subject: Re: New bootstrap config file(s) (Re: booting with verbosity by default? ) In-reply-to: Your message of "Thu, 06 Aug 1998 08:44:07 MST." <199808061544.IAA03196@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Aug 1998 11:24:11 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And this is a handy topic to raise it under; the new bootstrap will > (optionally) need access to quite a few files, and we may not really > want these cluttering up the root directory. How do people feel about > a /boot directory these days? Sounds good :) --------------------------------------------------------------------- |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 | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 18:58:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00257 for freebsd-current-outgoing; Thu, 6 Aug 1998 18:58:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00234 for ; Thu, 6 Aug 1998 18:57:56 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA16152; Thu, 6 Aug 1998 18:57:41 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpd016133; Thu Aug 6 18:57:40 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id SAA26484; Thu, 6 Aug 1998 18:57:38 -0700 (MST) From: Terry Lambert Message-Id: <199808070157.SAA26484@usr06.primenet.com> Subject: Re: Heads up on LFS To: jdp@polstra.com (John Polstra) Date: Fri, 7 Aug 1998 01:57:37 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199808061603.JAA26197@austin.polstra.com> from "John Polstra" at Aug 6, 98 09:03:07 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > JAVA has a nasty tendency to leak like a sieve until the GC hits a > > steady state. As does Modula 3. > ^^^^^^^^^^^^^^^^ > > I don't know what you base that statement on. I have a lot of > experience writing and using Modula-3 programs, and I've never > observed the behavior you describe. Q1: Is there more than 0 bytes difference between memory allocated and in use? Q2: If so, how large can this number be under the worst possible conditions? Q3: Is this more memory than is typically found in a typical embedded ssytem, such as the one found in a Microwave oven? Q4: What is the typical target platform for an RT OS, and what is one of the major target platforms for JAVA? Q5: How provable is a system that depends on garbage collection? My opinion is that RT OS's and portable devices need to run in (compared to most VAX programs) tiny memory footprints for them to be useful. The launch costs alone on the extra memory on its way to Mars are very, very large. Feel free to disagree with me (I'm sure you already do... 8-)). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 19:10:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02713 for freebsd-current-outgoing; Thu, 6 Aug 1998 19:10:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02696 for ; Thu, 6 Aug 1998 19:10:46 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id TAA28124; Thu, 6 Aug 1998 19:09:10 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma028122; Thu Aug 6 19:08:49 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id TAA26936; Thu, 6 Aug 1998 19:08:48 -0700 (PDT) From: Archie Cobbs Message-Id: <199808070208.TAA26936@bubba.whistle.com> Subject: Re: memory leaks in libc In-Reply-To: <199808070123.SAA26723@bubba.whistle.com> from Archie Cobbs at "Aug 6, 98 06:23:27 pm" To: freebsd-current@FreeBSD.ORG Date: Thu, 6 Aug 1998 19:08:48 -0700 (PDT) Cc: bde@zeta.org.au, wollman@khavrinen.lcs.mit.edu, dg@root.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > The idea of keeping a hash table of pointers that were gotten via > malloc() is simple enough. It would solve the problem for programs > than need it (a real world example of which exists at Whistle). > > For programs that don't do a lot of putenv()/setenv(), which is > most programs, there would be no difference. In fact, we can optimize > for this common case, which is NO calls to putenv()/setenv(), by > not creating the hash table at all. > > Now all we need is some enterprising soul to come up with the patch... OK, just to prove I'm not lazy... try this. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com Index: setenv.c =================================================================== RCS file: /cvs/freebsd/src/lib/libc/stdlib/setenv.c,v retrieving revision 1.3 diff -c -u -r1.3 setenv.c --- setenv.c 1996/07/12 18:55:21 1.3 +++ setenv.c 1998/08/07 02:05:15 @@ -41,6 +41,20 @@ char *__findenv __P((const char *, int *)); +/* We keep track of pointers gotten via malloc() using a hash table */ +#define NUMBUCKETS 64 +#define HASH(p) ((((int)(p) >> 24) ^ ((int)(p) >> 16) ^ \ + ((int)(p) >> 8) ^ ((int)(p))) % NUMBUCKETS) + +struct hashp { + void *ptr; + struct hashp *next; +}; +static struct hashp **table; + +static void addhash(void *ptr); +static void rmhash(void *ptr); + /* * setenv -- * Set the value of the environmental variable "name" to be @@ -55,6 +69,7 @@ extern char **environ; static int alloced; /* if allocated space before */ register char *c; + char *newptr; int l_value, offset; if (*value == '=') /* no `=' in value */ @@ -90,10 +105,13 @@ offset = cnt; } for (c = (char *)name; *c && *c != '='; ++c); /* no `=' in name */ - if (!(environ[offset] = /* name + `=' + value */ + if (!(newptr = /* name + `=' + value */ malloc((size_t)((int)(c - name) + l_value + 2)))) return (-1); - for (c = environ[offset]; (*c = *name++) && *c != '='; ++c); + rmhash(environ[offset]); /* free old value if malloc'd */ + environ[offset] = newptr; /* replace with new region */ + addhash(newptr); /* remember we malloc'd it */ + for (c = newptr; (*c = *name++) && *c != '='; ++c); for (*c++ = '='; (*c++ = *value++); ); return (0); } @@ -110,8 +128,63 @@ register char **p; int offset; - while (__findenv(name, &offset)) /* if set multiple times */ + while (__findenv(name, &offset)) { /* if set multiple times */ + rmhash(environ[offset]); /* free memory if malloc'd */ for (p = &environ[offset];; ++p) if (!(*p = *(p + 1))) break; + } } + +/* + * addhash(ptr) + * + * Add a pointer that we obtained via malloc() to our secret internal + * hash table, so when this variable is deleted or changed, we know to + * free the memory. + */ +static void +addhash(void *ptr) +{ + struct hashp *s; + int bucket; + + /* Create hash table if it doesn't already exist */ + if (table == NULL) { + if ((table = malloc(NUMBUCKETS * sizeof(*table))) == NULL) + return; + memset(table, 0, NUMBUCKETS * sizeof(*table)); + } + + /* Create new struct holding pointer and add it to the hash bucket */ + if ((s = malloc(sizeof(*s))) == NULL) + return; + s->ptr = ptr; + bucket = HASH(ptr); + s->next = table[bucket]; + table[bucket] = s; +} + +/* + * rmhash(ptr) + * + * Remove a pointer from the hash table and free() it. If the pointer + * was not obtained via malloc(), then it won't be found and we do nothing. + */ +static void +rmhash(void *ptr) +{ + struct hashp **sp, *s; + + if (table == NULL) + return; + for (sp = &table[HASH(ptr)]; (s = *sp) != NULL; sp = &s->next) { + if (s->ptr == ptr) { + *sp = s->next; + free(ptr); + free(s); + return; + } + } +} + To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 19:42:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA07241 for freebsd-current-outgoing; Thu, 6 Aug 1998 19:42:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA07221 for ; Thu, 6 Aug 1998 19:42:11 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id MAA03023; Fri, 7 Aug 1998 12:47:23 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808070247.MAA03023@cimlogic.com.au> Subject: Re: memory leaks in libc In-Reply-To: <199808070208.TAA26936@bubba.whistle.com> from Archie Cobbs at "Aug 6, 98 07:08:48 pm" To: archie@whistle.com (Archie Cobbs) Date: Fri, 7 Aug 1998 12:47:23 +1000 (EST) Cc: freebsd-current@FreeBSD.ORG, bde@zeta.org.au, wollman@khavrinen.lcs.mit.edu, dg@root.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs wrote: > OK, just to prove I'm not lazy... try this. And a thread safe version? -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 20:23:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12793 for freebsd-current-outgoing; Thu, 6 Aug 1998 20:23:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12777 for ; Thu, 6 Aug 1998 20:23:16 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id UAA29152; Thu, 6 Aug 1998 20:22:26 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808070322.UAA29152@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: shmit@kublai.com, current@FreeBSD.ORG Subject: Re: Pthreads woes revisited. In-reply-to: Your message of "Fri, 07 Aug 1998 08:44:08 +1000." <199808062244.IAA02167@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Aug 1998 20:22:26 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Curious, whats missing from the kernel for us to have kernel threads? Perhaps John Dyson can help us out over here ... Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 20:31:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13874 for freebsd-current-outgoing; Thu, 6 Aug 1998 20:31:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13866 for ; Thu, 6 Aug 1998 20:31:29 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id NAA03174; Fri, 7 Aug 1998 13:36:31 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808070336.NAA03174@cimlogic.com.au> Subject: Re: Pthreads woes revisited. In-Reply-To: <199808070322.UAA29152@rah.star-gate.com> from Amancio Hasty at "Aug 6, 98 08:22:26 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Fri, 7 Aug 1998 13:36:31 +1000 (EST) Cc: jb@cimlogic.com.au, shmit@kublai.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > Curious, whats missing from the kernel for us to have kernel threads? > > Perhaps John Dyson can help us out over here ... The last problem I was having was with the user_ldt being restored on context switches. AFAIK John never built in the patches I sent him. He was always preoccupied with the "next greatest improvement". I ended up side-lining the work in favour of doing work on the Alpha port. I'd suggest that it is too close to the release of 3.0 to try to get that stuff in, except possibly for the syscalls. It is better to get 3.0 to a stable state to limit the flak from people who don't (won't) understand why 2.2.8 will come out after 3.0. The release of 3.0 is due in about 9 weeks IIRC. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 20:33:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14115 for freebsd-current-outgoing; Thu, 6 Aug 1998 20:33:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14108 for ; Thu, 6 Aug 1998 20:33:01 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id XAA17093; Thu, 6 Aug 1998 23:32:21 -0400 (EDT) (envelope-from wollman) Date: Thu, 6 Aug 1998 23:32:21 -0400 (EDT) From: Garrett Wollman Message-Id: <199808070332.XAA17093@khavrinen.lcs.mit.edu> To: Archie Cobbs Cc: freebsd-current@FreeBSD.ORG, bde@zeta.org.au, wollman@khavrinen.lcs.mit.edu, dg@root.com Subject: Re: memory leaks in libc In-Reply-To: <199808070208.TAA26936@bubba.whistle.com> References: <199808070123.SAA26723@bubba.whistle.com> <199808070208.TAA26936@bubba.whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> malloc() is simple enough. It would solve the problem for programs >> than need it (a real world example of which exists at Whistle). > OK, just to prove I'm not lazy... try this. Now having gone to that effort, you can just add it to your program that needs it, and we don't have to bear the kluge in the C library. I believe that any program which suffers serious harm from the memory leak probably needs to use a different environment-access model. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 21:02:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17380 for freebsd-current-outgoing; Thu, 6 Aug 1998 21:02:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17352 for ; Thu, 6 Aug 1998 21:02:11 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id VAA29890; Thu, 6 Aug 1998 21:01:54 -0700 (PDT) (envelope-from jdp) Message-Id: <199808070401.VAA29890@austin.polstra.com> To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: Heads up on LFS In-reply-to: Your message of "Fri, 07 Aug 1998 01:57:37 -0000." <199808070157.SAA26484@usr06.primenet.com> Date: Thu, 06 Aug 1998 21:01:54 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > JAVA has a nasty tendency to leak like a sieve until the GC hits a > > > steady state. As does Modula 3. > > ^^^^^^^^^^^^^^^^ > > > > I don't know what you base that statement on. I have a lot of > > experience writing and using Modula-3 programs, and I've never > > observed the behavior you describe. > > Q1: Is there more than 0 bytes difference between memory > allocated and in use? > > Q2: If so, how large can this number be under the worst > possible conditions? > > Q3: Is this more memory than is typically found in a > typical embedded ssytem, such as the one found in a > Microwave oven? > > Q4: What is the typical target platform for an RT OS, and what > is one of the major target platforms for JAVA? > > Q5: How provable is a system that depends on garbage collection? > > My opinion is that RT OS's and portable devices need to run in > (compared to most VAX programs) tiny memory footprints for them > to be useful. The launch costs alone on the extra memory on its > way to Mars are very, very large. We were talking about SPIN and Modula-3. When did the subject change to real-time OSs and portable devices? And there is a vast gulf between "more than 0 bytes difference between memory allocated and in use" and "leaks like a sieve." You still haven't provided any support for the latter statement in reference to Modula-3's garbage collector. > Feel free to disagree with me (I'm sure you already do... 8-)). There's nothing there to agree or disagree with. You made a claim which goes against my experience, which happens to be extensive in this area. I challenged your claim. You changed the subject. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 21:03:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17440 for freebsd-current-outgoing; Thu, 6 Aug 1998 21:03:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from daphne.bogus (dialup1.black-hole.com [206.145.13.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17426 for ; Thu, 6 Aug 1998 21:03:25 -0700 (PDT) (envelope-from hank@black-hole.com) Received: from localhost (hank@localhost) by daphne.bogus (8.8.8/8.8.8) with SMTP id AAA00610 for ; Fri, 7 Aug 1998 00:04:02 -0500 (CDT) (envelope-from hank@black-hole.com) X-Authentication-Warning: daphne.bogus: hank owned process doing -bs Date: Fri, 7 Aug 1998 00:04:02 -0500 (CDT) From: Henry Miller X-Sender: hank@daphne.bogus cc: freebsd-current@FreeBSD.ORG Subject: Re: Crash: Fatal trap 12 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Aug 1998, Brian Feldman wrote: > This seems quite a bit like my current problems, I've noticed only very > recently, and with no real regularity. My uptime just won't exceed 1 or 2 > days, usually, beacuse I'll get a lockup. It happenes doing different > things. This morning, it locked up after switching from vty0 to X, solid, > no panic or trap... It crashed ~2 days ago when grepping stuff in /tmp. I Same thing just happened to me. I've just gone to SMP, (new computer, so I don't have much previous expirence) My brother went down, loged in, and started x (by login script) and the monitor cam up with sync out of range. >From a seperate comptuer I was unable to ping it, and nfs mounted file systems couldn't be read. num-lock on the keyboard didn't light up. After a hard power up, nothing was in /var/log that I could find. I'm not willing to say this is the same problem, though I'm hoping I can repeat it somehow and give more info. Until now I only send it to alert that there probably are problems serious enough to warent delaying the release of 3.0 (assuming that current becomes 3.0, but I'm new to freebsd so I don't know how that all works) oh, and I have an on motherboard Adaptec scsi contoroller that I boot from. (since it seems scsi disks are in common, but this could easially be a concidence) PS, your welcome to contact me if you want me to give more info, My day job was alpha test, so I am used to trying to repeat the unrepeatable over and over again. -- http://blugill.home.ml.org/ hank@black-hole.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 21:46:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22929 for freebsd-current-outgoing; Thu, 6 Aug 1998 21:46:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22924 for ; Thu, 6 Aug 1998 21:46:30 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA17379; Thu, 6 Aug 1998 22:46:05 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id WAA16195; Thu, 6 Aug 1998 22:46:01 -0600 Date: Thu, 6 Aug 1998 22:46:01 -0600 Message-Id: <199808070446.WAA16195@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Terry Lambert Cc: nate@mt.sri.com (Nate Williams), reilly@zeta.org.au, tom@uniserve.com, current@FreeBSD.ORG Subject: Re: Heads up on LFS In-Reply-To: <199808070148.SAA25886@usr06.primenet.com> References: <199808061438.IAA12182@mt.sri.com> <199808070148.SAA25886@usr06.primenet.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > JAVA has a nasty tendency to leak like a sieve until the GC hits a > > > steady state. As does Modula 3. > > > > You've *got* to be kidding, right? Do you have any idea how often the > > GC collection pass is run? It would be *very* difficult in real world > > programs to leak any signficicant (~1MB) of memory before the GC phase > > kicked in. > > Your and my definitions of significant differ. For an embedded use, > 1M is way, way too large. Most Palm pilots simply don't have that > much memory to be abole to afford to leak that much. On the palm pilot, you couldn't allocate 1M of stuff in that short of time. :) (The stuff I'm allocating is about 500-1MB/object, so your point is truly moot. Especially considering the footprint of my entire program is around 60-70MB.) Don't ask like an expert on something you have no idea on. Nate ps. There is no *real* Java on a pilot, and as such they're GC scheme could be much different than the current scheme, though I doubt it would make much difference. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 21:49:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA23403 for freebsd-current-outgoing; Thu, 6 Aug 1998 21:49:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA23389 for ; Thu, 6 Aug 1998 21:49:46 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id WAA15719; Thu, 6 Aug 1998 22:43:51 -0600 (MDT) Date: Thu, 6 Aug 1998 22:43:51 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199808070443.WAA15719@narnia.plutotech.com> To: Klaus Werner Krygier cc: current@FreeBSD.ORG Subject: Re: system lock-up (SMP, AHC_TAGENABLE, softupdates) Newsgroups: pluto.freebsd.current In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My last hope was CAM. Here (3.0CAM-19980712-SNAP) the system does not > freeze completely but becomes very slow on disk access and is also not > usable. One positive aspect: I get kernel messages. Every few seconds > the following message is printed out for ever: > > Timedout SCB handled by another timeout > Timedout SCB handled by another timeout > last message repeated 4 times > last message repeated 13 times > last message repeated 30 times > Timedout SCB handled by another timeout > Timedout SCB handled by another timeout > > etc. You are not the only person to report this problem, but I'm at a loss (at least hardware wise) to reproduce it. Mark Murry has also been able to make this happen but it only if he is running SMP. This makes me believe that there is a problem in our clock/timeout code that fails under SMP. Unfortunately I don't have any SMP hardware. Essentially what the messages are saying is that the timeouts scheduled for SCSI I/O are not canceled by the I/O completing. The timeout handler notices this and complains. This simply shouldn't happen. If you are interested in helping debug this problem, the strategy I would take is to turn the printf for the above message into a panic, and then go grovel around in the timeout data structures looking for corruption. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 22:49:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29867 for freebsd-current-outgoing; Thu, 6 Aug 1998 22:49:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29862 for ; Thu, 6 Aug 1998 22:49:42 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id HAA01678; Fri, 7 Aug 1998 07:46:18 +0200 (CEST) To: "Andrew Reilly" cc: Bruce Evans , wollman@khavrinen.lcs.mit.edu, dg@root.com, freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-reply-to: Your message of "Fri, 07 Aug 1998 11:02:43 +1000." <19980807110243.A9734@reilly.home> Date: Fri, 07 Aug 1998 07:46:18 +0200 Message-ID: <1676.902468778@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980807110243.A9734@reilly.home>, "Andrew Reilly" writes: >On Fri, Aug 07, 1998 at 03:23:29AM +1000, Bruce Evans wrote: >> >So you both agree, then, that there is no point in wasting any more >> >time on this? >> >> Not quite. It should be fixed someday. > >I always thought it odd that there were no implimentations of >free() that were able to identify whether the pointer that they >were passed was something that malloc had handed out previously. >Surely malloc's data structures must have something to say about >it. > >If free() could know this, then things like setenv could just go >ahead and call free(), and if the previous object had not been >malloc'ed then nothing would happen. Depends on your malloc(), phkmalloc can do this, and will issue a warning if you do something stupid. >Answering my own question with a small experiment: the free >routine prints this message to stderr: > >foo in free(): warning: junk pointer, too low to make sense. > >Is there any way to turn the message off, and rely on the benign >behaviour? no. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 22:55:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA00695 for freebsd-current-outgoing; Thu, 6 Aug 1998 22:55:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00689 for ; Thu, 6 Aug 1998 22:55:19 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id BAA20563; Fri, 7 Aug 1998 01:53:24 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Dusk Auriel Sykotik cc: Bruce Evans , dg@root.com, narvi@haldjas.folklore.ee, freebsd-current@FreeBSD.ORG, freebsd@xaa.iae.nl From: "Gary Palmer" Subject: Re: memory leaks in libc In-reply-to: Your message of "Thu, 06 Aug 1998 12:07:04 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Aug 1998 01:53:23 -0400 Message-ID: <20559.902469203@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dusk Auriel Sykotik wrote in message ID : > Apache uses them quite frequently. And this could make it very costly on > large webservers. Where I work, we have hundreds of connections to some > of our webservers per minute. We also use cgi scripts very frequently, > and these use *env* functions quite frequently as well. I would hope that apache does the setenv's in the child just before it does the exec, or even uses the exect() fn. I doubt very much that it is done *before* the fork. This means there is no leak (or rather, no long term leak), as the child dies rather promptly. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 23:09:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02195 for freebsd-current-outgoing; Thu, 6 Aug 1998 23:09:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02168 for ; Thu, 6 Aug 1998 23:09:41 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id CAA20731; Fri, 7 Aug 1998 02:05:45 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Harlan Stenn cc: Nathan Ahlstrom , Mike Smith , current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: New bootstrap config file(s) (Re: booting with verbosity by default? ) In-reply-to: Your message of "Thu, 06 Aug 1998 19:08:33 EDT." <583.902444913@brown.pfcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Aug 1998 02:05:45 -0400 Message-ID: <20727.902469945@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Harlan Stenn wrote in message ID <583.902444913@brown.pfcs.com>: > Possible Stupid Question Alert: > > What's with /stand, and why not use it instead of /boot? Since /stand has the installation tools, a lot of ppl blow it away after the install to get more free space on /. Putting the files in there would be bad(TM) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 23:22:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04365 for freebsd-current-outgoing; Thu, 6 Aug 1998 23:22:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04344 for ; Thu, 6 Aug 1998 23:22:08 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (UShoiM1li04o8ygL5cAVrmWy3rTtBuXe@localhost [127.0.0.1]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id IAA19287; Fri, 7 Aug 1998 08:21:22 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199808070621.IAA19287@gratis.grondar.za> To: "Justin T. Gibbs" cc: Klaus Werner Krygier , current@FreeBSD.ORG Subject: Re: system lock-up (SMP, AHC_TAGENABLE, softupdates) Date: Fri, 07 Aug 1998 08:21:21 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Justin T. Gibbs" wrote: > > Timedout SCB handled by another timeout > > > > etc. > > You are not the only person to report this problem, but I'm at a loss > (at least hardware wise) to reproduce it. Mark Murry has also been > able to make this happen but it only if he is running SMP. This makes > me believe that there is a problem in our clock/timeout code that fails > under SMP. Unfortunately I don't have any SMP hardware. Hi Justin Are you still keen to come into my box with a serial-port debugger to investigate this? I can make it happen at will. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 6 23:58:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09684 for freebsd-current-outgoing; Thu, 6 Aug 1998 23:58:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from USC-FW.utimaco.co.at (mail-gw.utimaco.co.at [195.96.28.162]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09678 for ; Thu, 6 Aug 1998 23:58:39 -0700 (PDT) (envelope-from Michael.Schuster@utimaco.co.at) Received: (from uucp@localhost) by USC-FW.utimaco.co.at (8.8.8/8.8.8) id IAA01459; Fri, 7 Aug 1998 08:57:18 +0200 (CEST) (envelope-from Michael.Schuster@utimaco.co.at) Received: from ns1.int.utimaco.co.at(10.1.0.254) by USC-FW.utimaco.co.at via smap (V2.0) id xma001457; Fri, 7 Aug 98 08:56:58 +0200 Received: from utimaco.co.at (ultra1.int.utimaco.co.at [10.1.0.32]) by safeconcept.int.utimaco.co.at (8.8.5/8.8.5) with ESMTP id IAA16388; Fri, 7 Aug 1998 08:56:56 +0200 (CEST) Message-ID: <35CAA537.BEE345B8@utimaco.co.at> Date: Fri, 07 Aug 1998 08:56:55 +0200 From: Michael Schuster Organization: Utimaco Safe Concept GmbH. Linz Austria X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.5.1 sun4u) MIME-Version: 1.0 To: "current@FreeBSD.ORG" , Narvi Subject: Re: memory leaks in libc Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apart from what everybody else has already said arguing for or against doing something about this, I do have a comment: Narvi wrote: > On Thu, 6 Aug 1998, Bruce Evans wrote: > > > > The problem with fixing setenv() is that you don't know if a pointer was > > >malloced, allocated from the env area above the stack, points to read-only ... > > a) allocate a bit more memory than needed > b) set the environment string > c) end it with zero > d) append a certain token after the end of the string saying "ok > to free() me" to anyone knowing what to look at? > > But couldn't a string end at the end of allocated area so that by peeking > behind the final zero we will sometimes cause a SIGSEV? Why not put the token into the beginning of the malloc'd memory and increase the value of the returned pointer by a constant number? This saves you the variable search effort for the terminating zero and also guards better against accidental overwrites. something like: /* define TOKEN to be an 8-byte unique pattern */ char *x; x = (char *) malloc (size); memcpy (x, TOKEN, sizeof (TOKEN)); x += sizeof (TOKEN); /* do env string copy into x; return x */ I did a small test program that seems to indicate that malloc always returns values 16-byte aligned (is that correct linguistically?). IFF we can rely on this behaviour, we could increment our (char) pointer by 8 (or 24 if 8 is not enough) bytes and check for this 8-byte displacement in setenv, even before having to check for the token. > > There is no love, no good, no happiness and no future - > all these are just illusions. maybe, but we live for them :-) Archie Cobbs wrote: >OK, just to prove I'm not lazy... try this. >+static void addhash(void *ptr); >+static void rmhash(void *ptr); (lots of stuff not quoted) I think that although my approach my be a bit less flexible, it certainly saves the second malloc (in the hash functions), and therefore would perform better. -- Michael Schuster To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 00:14:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12328 for freebsd-current-outgoing; Fri, 7 Aug 1998 00:14:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pobox.com (port25.prairietech.net [208.141.230.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12243 for ; Fri, 7 Aug 1998 00:14:17 -0700 (PDT) (envelope-from alk@pobox.com) Received: (from alk@localhost) by pobox.com (8.8.8/8.7.3) id CAA18096; Fri, 7 Aug 1998 02:15:48 -0500 (CDT) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 7 Aug 1998 02:15:47 -0500 (CDT) X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Reply-To: alk@pobox.com To: current@FreeBSD.ORG Subject: Re: Pthreads woes revisited. X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13770.43121.617719.400946@compound.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : From: John Birrell : Amancio Hasty wrote: : > Curious, whats missing from the kernel for us to have kernel threads? : The last problem I was having was with the user_ldt being restored : on context switches. ...patches I sent... : I'd suggest that it is too close to the release of 3.0 to try to get : that stuff in, except possibly for the syscalls. Ouch! Like some (many?) others, in my world the whole value of 3.0 is wrapt in SMP and kernel threads. Nothing else counts, comparatively speaking. : It is better to get : 3.0 to a stable state to limit the flak from people who don't (won't) : understand why 2.2.8 will come out after 3.0. How about delaying the release long enough to include the significant added value, thereby reducing the gap between 2.2.8 and 3.0, thereby reducing the flak from the quarter you posit, as well as the flak from my own kindred spirits? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 00:16:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12563 for freebsd-current-outgoing; Fri, 7 Aug 1998 00:16:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12506 for ; Fri, 7 Aug 1998 00:15:55 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id JAA12648; Fri, 7 Aug 1998 09:20:13 +0200 (CEST) (envelope-from regnauld@deepo.prosa.dk) Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id JAA07169; Fri, 7 Aug 1998 09:21:33 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id JAA13039; Fri, 7 Aug 1998 09:19:13 +0200 (CEST) Message-ID: <19980807091913.22769@deepo.prosa.dk> Date: Fri, 7 Aug 1998 09:19:13 +0200 From: Philippe Regnauld To: Klaus Werner Krygier Cc: freebsd-current@FreeBSD.ORG Subject: Re: system lock-up (SMP, AHC_TAGENABLE, softupdates) References: <19980802172204.50682@deepo.prosa.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from Klaus Werner Krygier on Thu, Aug 06, 1998 at 08:58:34PM +0200 X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Klaus Werner Krygier writes: > > I have a very similar hardware setup on several machines (Gigabyte > 586-DX, 2 x P5-200, 64 MB, on-board 7880 SCSI, several different disks > (2GB, 4GB, 9GB)) and I have the same problems: > > If I do a lot of disk activity my computers freeze. Sometimes a SCSI > bus reset seems to be initiated (which I can recogize on the loading [...] > With older 3.0-SNAPs (e.g. May 97) a SMP system was very stable on my > first board and did not show such effects for almost a year. Because of > other problems and to use new features and improvements I had to upgrade > and have now very instable systems. I haven't tried CAM, but I have the exact same symptoms -- and I didn't experience problems either last year... -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 00:24:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14605 for freebsd-current-outgoing; Fri, 7 Aug 1998 00:24:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14579 for ; Fri, 7 Aug 1998 00:23:48 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id AAA27067; Fri, 7 Aug 1998 00:23:32 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd027033; Fri Aug 7 00:23:25 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id AAA22404; Fri, 7 Aug 1998 00:23:21 -0700 (MST) From: Terry Lambert Message-Id: <199808070723.AAA22404@usr08.primenet.com> Subject: Re: Heads up on LFS To: jdp@polstra.com (John Polstra) Date: Fri, 7 Aug 1998 07:23:21 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199808070401.VAA29890@austin.polstra.com> from "John Polstra" at Aug 6, 98 09:01:54 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We were talking about SPIN and Modula-3. When did the subject change > to real-time OSs and portable devices? And there is a vast gulf > between "more than 0 bytes difference between memory allocated and in > use" and "leaks like a sieve." You still haven't provided any support > for the latter statement in reference to Modula-3's garbage collector. SPIN purports (on their www pages) to be RT. Perhaps "leaks" is a bad word, since it implies "unreferenced allocations". Languages that rely on GC'ing allocations reference the allocations in the allocator. They are only unreferenced as far as the program is concerned. >From the perspective of a program that believes it is running in its own virtual machine, however, there is very little difference between memory referenced by an allocator but not by me and memory that has leaked. In either case, until the GC runs, there is a program-observable leak. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 00:52:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20159 for freebsd-current-outgoing; Fri, 7 Aug 1998 00:52:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20115 for ; Fri, 7 Aug 1998 00:51:53 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id AAA03441; Fri, 7 Aug 1998 00:51:16 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd003395; Fri Aug 7 00:51:11 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id AAA23867; Fri, 7 Aug 1998 00:51:05 -0700 (MST) From: Terry Lambert Message-Id: <199808070751.AAA23867@usr08.primenet.com> Subject: Re: memory leaks in libc To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Fri, 7 Aug 1998 07:51:05 +0000 (GMT) Cc: archie@whistle.com, freebsd-current@FreeBSD.ORG, bde@zeta.org.au, wollman@khavrinen.lcs.mit.edu, dg@root.com In-Reply-To: <199808070332.XAA17093@khavrinen.lcs.mit.edu> from "Garrett Wollman" at Aug 6, 98 11:32:21 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > OK, just to prove I'm not lazy... try this. > > Now having gone to that effort, you can just add it to your program > that needs it, and we don't have to bear the kluge in the C library. > > I believe that any program which suffers serious harm from the memory > leak probably needs to use a different environment-access model. Isn't a C library that leaks in its standard function implemetnations already kludged? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 00:55:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20943 for freebsd-current-outgoing; Fri, 7 Aug 1998 00:55:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20908 for ; Fri, 7 Aug 1998 00:55:07 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id AAA05437; Fri, 7 Aug 1998 00:54:51 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd005373; Fri Aug 7 00:54:42 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id AAA24074; Fri, 7 Aug 1998 00:54:37 -0700 (MST) From: Terry Lambert Message-Id: <199808070754.AAA24074@usr08.primenet.com> Subject: Re: Heads up on LFS To: nate@mt.sri.com (Nate Williams) Date: Fri, 7 Aug 1998 07:54:37 +0000 (GMT) Cc: tlambert@primenet.com, nate@mt.sri.com, reilly@zeta.org.au, tom@uniserve.com, current@FreeBSD.ORG In-Reply-To: <199808070446.WAA16195@mt.sri.com> from "Nate Williams" at Aug 6, 98 10:46:01 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On the palm pilot, you couldn't allocate 1M of stuff in that short of > time. :) > > (The stuff I'm allocating is about 500-1MB/object, so your point is > truly moot. Especially considering the footprint of my entire program > is around 60-70MB.) > > Don't ask like an expert on something you have no idea on. You shouldn't either -- 60-70M footprint code won't run on a pilot, so the point about the size of your code is rather moot as well. > ps. There is no *real* Java on a pilot, and as such they're GC scheme > could be much different than the current scheme, though I doubt it would > make much difference. Tim Wilkerson's Kaffe code will run on a DOS machine in less memory than is available on a Palm pilot. In addition, the unslotted RAM on an unexpanded Pilot is sufficient for a JVM implementation in an EEPROM, since the pinout is equal to that of amny EEPROM parts. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 00:58:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21447 for freebsd-current-outgoing; Fri, 7 Aug 1998 00:58:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from terminator.informatik.ba-stuttgart.de (terminator.informatik.ba-stuttgart.de [141.31.111.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21407 for ; Fri, 7 Aug 1998 00:58:35 -0700 (PDT) (envelope-from henry@MX.BA-Stuttgart.De) Received: from marylin.goethestr12-net.marbach-neckar (marylin.informatik.ba-stuttgart.de [141.31.112.1]) by terminator.informatik.ba-stuttgart.de (8.8.8/8.8.8) with ESMTP id JAA21441 for ; Fri, 7 Aug 1998 09:42:26 +0200 (CEST) (envelope-from henry@MX.BA-Stuttgart.De) Received: (from henry@localhost) by marylin.goethestr12-net.marbach-neckar (8.9.1/8.8.8) id JAA01006 for freebsd-current@freebsd.org; Fri, 7 Aug 1998 09:40:24 +0200 (CEST) (envelope-from henry) From: Henry Vogt Message-Id: <199808070740.JAA01006@marylin.goethestr12-net.marbach-neckar> Subject: CAM/Kernel compile problem in -current To: freebsd-current@FreeBSD.ORG Date: Fri, 7 Aug 1998 09:40:23 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, After successfully upgrading my SMP box with CAM using the 3.0CAM-19980716-SNAP.diffs on a ccd(2 Disks - partly striped, partly mirrored) all was fine:-) After checking out newer sources (from around 2 days ago) trying to compile -current kernel leads to the following error: ----------------------------- C U T ----------------------------- cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h ../../cam/scsi/scsi_da.c ../../cam/scsi/scsi_da.c: In function `daopen': ../../cam/scsi/scsi_da.c:316: warning: passing arg 4 of `dsopen' makes integer from pointer without a cast ../../cam/scsi/scsi_da.c:316: warning: passing arg 5 of `dsopen' from incompatible pointer type ../../cam/scsi/scsi_da.c:316: warning: passing arg 6 of `dsopen' from incompatible pointer type ../../cam/scsi/scsi_da.c:316: warning: passing arg 7 of `dsopen' from incompatible pointer type ../../cam/scsi/scsi_da.c:316: warning: passing arg 8 of `dsopen' from incompatible pointer type ../../cam/scsi/scsi_da.c:316: too few arguments to function `dsopen' *** Error code 1 Stop. ----------------------------- C U T ----------------------------- Obvoiusly the dsopen routine expects now more arguments.. Needs the CAM-Snapshot to be updated ? Or am I doing something wrong? This leads me to a more general question: Whats the supposed way to have CAM a n d to follow the -current sources ? Do i have to re-check out a new source-tree and re-applied CAM, everytime ? Of course I would prefer just to check out the sources as usual.. Sorry, if this is a silly question or something obvious, which I'm not aware of. Regards Henry -- // // Do you suffer from long term memory loss ? I don't remember:-( // // Henry Vogt (henry@BA-Stuttgart.De) // Goethestr. 12, 71672 Marbach (Neckar), Tel. 07144/841653 // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 01:29:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26827 for freebsd-current-outgoing; Fri, 7 Aug 1998 01:29:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26813 for ; Fri, 7 Aug 1998 01:28:55 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id KAA16359; Fri, 7 Aug 1998 10:33:08 +0200 (CEST) (envelope-from regnauld@deepo.prosa.dk) Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id KAA07304; Fri, 7 Aug 1998 10:34:29 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id KAA13441; Fri, 7 Aug 1998 10:32:09 +0200 (CEST) Message-ID: <19980807103209.62498@deepo.prosa.dk> Date: Fri, 7 Aug 1998 10:32:09 +0200 From: Philippe Regnauld To: Mark Murray Cc: "Justin T. Gibbs" , current@FreeBSD.ORG Subject: Re: system lock-up (SMP, AHC_TAGENABLE, softupdates) References: <199808070621.IAA19287@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199808070621.IAA19287@gratis.grondar.za>; from Mark Murray on Fri, Aug 07, 1998 at 08:21:21AM +0200 X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray writes: > Hi Justin > > Are you still keen to come into my box with a serial-port debugger to > investigate this? I can make it happen at will. I was going to suggest the same (provided I bring my box to the office :-) -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 01:31:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27284 for freebsd-current-outgoing; Fri, 7 Aug 1998 01:31:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27268 for ; Fri, 7 Aug 1998 01:31:43 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id KAA02016 for current@freebsd.org; Fri, 7 Aug 1998 10:30:31 +0200 (CEST) (envelope-from sos) Message-Id: <199808070830.KAA02016@sos.freebsd.dk> Subject: Netstat broken .... To: current@FreeBSD.ORG (FreeBSD current) Date: Fri, 7 Aug 1998 10:30:31 +0200 (CEST) From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After a make world netstat seems to be broken or the kernel part that delivers the data: sos> netstat -rn Routing tables rt_tables: symbol not in namelist -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 01:44:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28626 for freebsd-current-outgoing; Fri, 7 Aug 1998 01:44:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28606 for ; Fri, 7 Aug 1998 01:44:39 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id SAA04153; Fri, 7 Aug 1998 18:49:56 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808070849.SAA04153@cimlogic.com.au> Subject: Re: Pthreads woes revisited. In-Reply-To: <13770.43121.617719.400946@compound.east> from Tony Kimball at "Aug 7, 98 02:15:47 am" To: alk@pobox.com Date: Fri, 7 Aug 1998 18:49:55 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tony Kimball wrote: > Ouch! Like some (many?) others, in my world the whole value > of 3.0 is wrapt in SMP and kernel threads. Nothing else counts, > comparatively speaking. These "many others" don't seem to contribute to making these things happen. > : It is better to get > : 3.0 to a stable state to limit the flak from people who don't (won't) > : understand why 2.2.8 will come out after 3.0. > > How about delaying the release long enough to include the significant > added value, thereby reducing the gap between 2.2.8 and 3.0, thereby > reducing the flak from the quarter you posit, as well as the flak from > my own kindred spirits? I doubt that introducing further delays would create a flurry of activity aimed at providing added value. All that would happen is that the same value would be delivered later. [ Anybody reading this who wants to prove me wrong was 9 weeks to submit a PR and nag a committer to get it worked on. The PR should contain patches relative to -current, though. ] -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 01:46:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28962 for freebsd-current-outgoing; Fri, 7 Aug 1998 01:46:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28848 for ; Fri, 7 Aug 1998 01:45:59 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id KAA03003; Fri, 7 Aug 1998 10:42:49 +0200 (CEST) To: alk@pobox.com cc: current@FreeBSD.ORG Subject: Re: Pthreads woes revisited. In-reply-to: Your message of "Fri, 07 Aug 1998 02:15:47 CDT." <13770.43121.617719.400946@compound.east> Date: Fri, 07 Aug 1998 10:42:49 +0200 Message-ID: <3001.902479369@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <13770.43121.617719.400946@compound.east>, Tony Kimball writes: >How about delaying the release long enough to include the significant >added value, thereby reducing the gap between 2.2.8 and 3.0, thereby >reducing the flak from the quarter you posit, as well as the flak from >my own kindred spirits? 3.0 goes out on september 15th, come hell or high water. If it doesn't contain what you want, well, sorry, can't really do much there... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 01:53:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00434 for freebsd-current-outgoing; Fri, 7 Aug 1998 01:53:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00425 for ; Fri, 7 Aug 1998 01:53:41 -0700 (PDT) (envelope-from reilly@zeta.org.au) Received: from zeta.org.au (d67.syd2.zeta.org.au [203.26.11.67]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id SAA30226 for ; Fri, 7 Aug 1998 18:53:21 +1000 Received: (qmail 339 invoked by uid 1000); 7 Aug 1998 08:42:56 -0000 From: "Andrew Reilly" Message-ID: <19980807184256.A27680@reilly.home> Date: Fri, 7 Aug 1998 18:42:56 +1000 To: Terry Lambert , John Polstra Cc: current@FreeBSD.ORG Subject: GC, was Re: Heads up on LFS References: <199808061603.JAA26197@austin.polstra.com> <199808070157.SAA26484@usr06.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808070157.SAA26484@usr06.primenet.com>; from Terry Lambert on Fri, Aug 07, 1998 at 01:57:37AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 07, 1998 at 01:57:37AM +0000, Terry Lambert wrote: > > > JAVA has a nasty tendency to leak like a sieve until the GC hits a > > > steady state. As does Modula 3. > > ^^^^^^^^^^^^^^^^ > > > > I don't know what you base that statement on. I have a lot of > > experience writing and using Modula-3 programs, and I've never > > observed the behaviour you describe. Terry goes on to ask a number of rhetorical questions, presumably intended to paint GC in a grim light, in the context of embedded systems. Knowing a thing or two about embedded systems, and having recently become very interested in dynamic memory allocation in general, and garbage collection systems in particular, I thought I'd have a blast. First, though: let's examine biases: Terry has used C++ and C as examples of systems to be preferred, on the grounds of predictability or efficiency. > Q1: Is there more than 0 bytes difference between memory > allocated and in use? This is not the right question. The right question is: can future demands for memory be met? Embedded systems generally don't have the luxury of being able to be re-booted. For a long time, my answer to this question was always: of course: I allocate everything I need at compile time, so there will be NO future demands for memory. Dynamic memory has no place in embedded, real-time systems, I thought. Since then, I have built some more complicated systems, that (because of flexibility requirements) did use dynamic memory of a sort. I still could not afford even the possibility of fragmentation, because the peak memory use was close to the total memory available. So I used a "strictly LIFO" stack-based heap. You see: even if your code has no memory leaks, and the difference between "allocated" and "in use" is zero bytes, and there is (barely) enough memory free to satisfy your future requirements, a straight C or C++ application is almost certainly going to crash with an out-of-memory exception caused by fragmentation at some point. You can't generally move things around to coalesce free space, because you have pointers that may or may not contain valid addresses everywhere. > Q2: If so, how large can this number be under the worst > possible conditions? As long as the running configuration fits into the available memory, what does it matter? If you run out, then you'd better run the collector again, and make a note that you'd better run it more often in future. > Q3: Is this more memory than is typically found in a > typical embedded system, such as the one found in a > Microwave oven? If you can find a microwave oven that feels the need to use dynamic memory allocation, then it may well be better off using GC. > Q4: What is the typical target platform for an RT OS, and what > is one of the major target platforms for JAVA? Not microwave ovens, that's for sure. What's your point here? (Perspective: one can now buy a 66 MHz, 32-bit processor with 2M _bytes_ of DRAM on a single chip: the Mitsubishi M32000D4AFP. You probably don't need one in your microwave oven, but your launch costs line [below] looks a bit spurious.) > Q5: How provable is a system that depends on garbage collection? How provable is one that depends on dynamic memory allocation at all? Not very (if time is a constraint). At least, if you know you've catered for the total, worst case requirement, then a GC system might be able to guarantee that you can always get to the bits that you need. You can't say that about a manual system unless you're prepared to stop and move things around yourself. > My opinion is that RT OS's and portable devices need to run in > (compared to most VAX programs) tiny memory footprints for them > to be useful. The launch costs alone on the extra memory on its > way to Mars are very, very large. The compute costs for memory allocation and reclamation can be just as large and unpredictable for C++ new and delete as they are for a GC system. How do you know that that tree node you're deleting now is a leaf, or something that is going to trigger an enormous cascade of subsequent deletions? In reality, whether you're using GC or manual reclamation, you simply DO NOT ALLOCATE OR FREE ANYTHING while you are running the real-time part of the code. (If you're game to try it though, at least the GC systems generally allow you to run the collector in a separate, non-real-time thread, whereas a manual system does it's work in the one-and-only thread.) > Feel free to disagree with me (I'm sure you already do... 8-)). I have copies of a GC-faq by an author too modest even to put an e-mail address into it, and an excellent survey article "Dynamic Storage Allocation: A Survey and Critical Review" by Paul Wilson, Mark Johnstone, Michael Neely and David Boles, somewhere on the Web, but I regret that I've lost the original URLs. If anyone can supply these I would be very grateful. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 01:59:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01219 for freebsd-current-outgoing; Fri, 7 Aug 1998 01:59:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wit393107.student.utwente.nl (wit393107.student.utwente.nl [130.89.235.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01206 for ; Fri, 7 Aug 1998 01:59:19 -0700 (PDT) (envelope-from gelderen@mediaport.org) Received: from wit395301.student.utwente.nl ([130.89.235.121]:34820 "HELO deskfix" ident: "NO-IDENT-SERVICE") by wit393107.student.utwente.nl with SMTP id <4117-24330>; Fri, 7 Aug 1998 10:58:53 +0200 Message-ID: <004d01bdc1e1$990cd7c0$1400000a@deskfix.local> From: "Jeroen C. van Gelderen" To: "Andrew Reilly" , Cc: , , Subject: Re: memory leaks in libc Date: Fri, 7 Aug 1998 10:58:50 +0200 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 4.72.3115.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Andrew Reilly |And yet it is a problem that I've never read a really good solution |for. I read a comment on comp.lang.eiffel recently, about BeOS. |Apparently they (the BeOS designers) have devised a protocol that goes |by the name "wean/adopt", that is presumably about passing "ownership" |of dynamically allocated objects around. See: URL:http://www.be.com/documentation/be_book_old/Intro/intro.html Cheers, Jeroen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 02:29:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06020 for freebsd-current-outgoing; Fri, 7 Aug 1998 02:29:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05874 for ; Fri, 7 Aug 1998 02:28:06 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id TAA04362; Fri, 7 Aug 1998 19:30:08 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808070930.TAA04362@cimlogic.com.au> Subject: Re: Pthreads woes revisited. In-Reply-To: <3001.902479369@critter.freebsd.dk> from Poul-Henning Kamp at "Aug 7, 98 10:42:49 am" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Fri, 7 Aug 1998 19:30:08 +1000 (EST) Cc: alk@pobox.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > 3.0 goes out on september 15th, come hell or high water. Jordan said October 15th in his mail on Tue, 28 Jul 1998 05:13:15 -0700. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 02:50:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09677 for freebsd-current-outgoing; Fri, 7 Aug 1998 02:50:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA09622 for ; Fri, 7 Aug 1998 02:50:22 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id LAA03251; Fri, 7 Aug 1998 11:47:03 +0200 (CEST) To: John Birrell cc: alk@pobox.com, current@FreeBSD.ORG Subject: Re: Pthreads woes revisited. In-reply-to: Your message of "Fri, 07 Aug 1998 19:30:08 +1000." <199808070930.TAA04362@cimlogic.com.au> Date: Fri, 07 Aug 1998 11:47:03 +0200 Message-ID: <3249.902483223@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808070930.TAA04362@cimlogic.com.au>, John Birrell writes: >Poul-Henning Kamp wrote: >> 3.0 goes out on september 15th, come hell or high water. > >Jordan said October 15th in his mail on Tue, 28 Jul 1998 05:13:15 -0700. Sorry, my memory must have slipped there then... At least I got the 15 right :-) But the vital thing is that we will not delay it from that date. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 03:03:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA11680 for freebsd-current-outgoing; Fri, 7 Aug 1998 03:03:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA11560; Fri, 7 Aug 1998 03:02:27 -0700 (PDT) (envelope-from croot@btp1da.phy.uni-bayreuth.de) Received: (from root@localhost) by btp1da.phy.uni-bayreuth.de (8.8.8/8.7.3) id MAA02173; Fri, 7 Aug 1998 12:02:05 +0200 (MEST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199808070830.KAA02016@sos.freebsd.dk> Date: Fri, 07 Aug 1998 12:02:05 +0200 (MEST) Organization: university of bayreuth From: Werner Griessl To: "S\xren Schmidt" Subject: RE: Netstat broken .... Cc: (FreeBSD current) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Aug-98 S\xren Schmidt wrote: > > After a make world netstat seems to be broken or the kernel part > that delivers the data: > > sos> netstat -rn > Routing tables > rt_tables: symbol not in namelist > > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end? > .. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- E-Mail: Werner Griessl Date: 07-Aug-98 Time: 12:01:18 This message was sent by XFMail ---------------------------------- Same here with sources from today. Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 03:11:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA12947 for freebsd-current-outgoing; Fri, 7 Aug 1998 03:11:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA12924; Fri, 7 Aug 1998 03:11:32 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id MAA03399; Fri, 7 Aug 1998 12:08:24 +0200 (CEST) To: sos@FreeBSD.ORG cc: current@FreeBSD.ORG (FreeBSD current) Subject: Re: Netstat broken .... In-reply-to: Your message of "Fri, 07 Aug 1998 10:30:31 +0200." <199808070830.KAA02016@sos.freebsd.dk> Date: Fri, 07 Aug 1998 12:08:23 +0200 Message-ID: <3397.902484503@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808070830.KAA02016@sos.freebsd.dk>, Søren Schmidt writes: > >After a make world netstat seems to be broken or the kernel part >that delivers the data: > >sos> netstat -rn >Routing tables >rt_tables: symbol not in namelist My fault, I'll fix it asap. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 03:43:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16441 for freebsd-current-outgoing; Fri, 7 Aug 1998 03:43:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16433 for ; Fri, 7 Aug 1998 03:43:33 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id MAA29821 for freebsd-current@FreeBSD.ORG; Fri, 7 Aug 1998 12:43:14 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 210B01527; Fri, 7 Aug 1998 12:33:42 +0200 (CEST) Message-ID: <19980807123342.A4133@keltia.freenix.fr> Date: Fri, 7 Aug 1998 12:33:42 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: CAM/Kernel compile problem in -current Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199808070740.JAA01006@marylin.goethestr12-net.marbach-neckar> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199808070740.JAA01006@marylin.goethestr12-net.marbach-neckar>; from Henry Vogt on Fri, Aug 07, 1998 at 09:40:23AM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4527 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Henry Vogt: > After checking out newer sources (from around 2 days ago) > trying to compile -current kernel leads to the following error: Interface for dsopen has changed since 7/16. Add a parameter to the dsopen() call, like this: /* Initialize slice tables. */ error = dsopen("da", dev, fmt, 0, &softc->dk_slices, &label, dastrategy, (ds_setgeom_t *)NULL, &da_cdevsw, &da_cdevsw); -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #62: Mon Jul 27 20:47:08 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 05:54:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA00471 for freebsd-current-outgoing; Fri, 7 Aug 1998 05:54:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay1.aha.ru (relay1.aha.ru [195.2.83.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA00466 for ; Fri, 7 Aug 1998 05:54:22 -0700 (PDT) (envelope-from osa@serv.etrust.ru) Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112]) by relay1.aha.ru (8.9.1/aha-r/0.04B) with ESMTP id QAA13158 for ; Fri, 7 Aug 1998 16:54:02 +0400 (MSD) Received: by sunny.aha.ru id QAA08192; (8.8.8/vak/1.9) Fri, 7 Aug 1998 16:53:48 +0400 (MSD) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma008094; Fri Aug 7 16:53:37 1998 Received: from papa by serv.etrust.ru with SMTP id QAA04882; (8.9.1/vak/1.9) Fri, 7 Aug 1998 16:56:30 +0400 (MSD) From: "oZZ!!" To: Subject: about vi in -current & file, containes 200000 strings ( squid.logs ) Date: Fri, 7 Aug 1998 16:53:27 +0400 Message-ID: <003801bdc202$5f613090$071ea8c0@papa.etrust.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by hub.freebsd.org id FAA00467 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Found a bug in 3.0-CURRENT ??? vi can't delete 100.000 strings from squid's access.log file It says : Cannot allocate memory Hmmm... Rgdz, oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 06:14:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02339 for freebsd-current-outgoing; Fri, 7 Aug 1998 06:14:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02331 for ; Fri, 7 Aug 1998 06:14:25 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (mCaXldqORvrNnYsnCZdp09DraUeXLA89@localhost [127.0.0.1]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id PAA22164; Fri, 7 Aug 1998 15:10:36 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199808071310.PAA22164@gratis.grondar.za> To: Henry Vogt cc: freebsd-current@FreeBSD.ORG Subject: Re: CAM/Kernel compile problem in -current Date: Fri, 07 Aug 1998 15:10:36 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Henry Vogt wrote: > cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prot otypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h ../../cam/scsi/scsi_da.c > ../../cam/scsi/scsi_da.c: In function `daopen': > ../../cam/scsi/scsi_da.c:316: warning: passing arg 4 of `dsopen' makes integer from pointer w ithout a cast > ../../cam/scsi/scsi_da.c:316: warning: passing arg 5 of `dsopen' from incompatible pointer ty pe > ../../cam/scsi/scsi_da.c:316: warning: passing arg 6 of `dsopen' from incompatible pointer ty pe > ../../cam/scsi/scsi_da.c:316: warning: passing arg 7 of `dsopen' from incompatible pointer ty pe > ../../cam/scsi/scsi_da.c:316: warning: passing arg 8 of `dsopen' from incompatible pointer ty pe > ../../cam/scsi/scsi_da.c:316: too few arguments to function `dsopen' > *** Error code 1 Add a new third argument of zero - so add a ", 0" (without the quotes) in position 3. (It may be position four - check for other calls to dsopen). > Needs the CAM-Snapshot to be updated ? Yes, frequently - but the guys working on it also need time to do the necessary development. > Or am I doing something wrong? Yes - not hacking on it yourself :-) > This leads me to a more general question: > Whats the supposed way to have CAM a n d to follow the -current sources ? Hack a lot. :-) > Do i have to re-check out a new source-tree and re-applied CAM, everytime ? Whenever a new CAM snapshot is released is a good idea, if you have the time and energy. > Of course I would prefer just to check out the sources as usual.. > Sorry, if this is a silly question or something obvious, which I'm not aware of. As with normal CURRENT, you are pretty much your own support guy - the authors are there to help with bugs, rather than implementation. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 06:23:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03835 for freebsd-current-outgoing; Fri, 7 Aug 1998 06:23:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03802 for ; Fri, 7 Aug 1998 06:23:33 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id PAA12932; Fri, 7 Aug 1998 15:23:13 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 7 Aug 1998 15:23:12 +0200 (MET DST) Mime-Version: 1.0 To: "oZZ!!" Cc: Subject: Re: about vi in -current & file, containes 200000 strings ( squid.logs ) References: <003801bdc202$5f613090$071ea8c0@papa.etrust.ru> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 07 Aug 1998 15:23:12 +0200 In-Reply-To: "oZZ!!"'s message of "Fri, 7 Aug 1998 16:53:27 +0400" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id GAA03822 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "oZZ!!" writes: > vi can't delete 100.000 strings from squid's access.log file > It says : Cannot allocate memory You hit your resource limits. 'man login.conf'. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 06:47:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06845 for freebsd-current-outgoing; Fri, 7 Aug 1998 06:47:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from esmeralda.xaa.iae.nl (esmeralda.xaa.iae.nl [194.151.75.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA06840 for ; Fri, 7 Aug 1998 06:47:41 -0700 (PDT) (envelope-from freebsd@xaa.iae.nl) Received: from ariel.xaa.iae.nl (ariel.xaa.iae.nl [194.151.75.10]) by esmeralda.xaa.iae.nl (8.8.8/8.8.7) with ESMTP id PAA10230; Fri, 7 Aug 1998 15:47:22 +0200 (MET DST) (envelope-from freebsd@xaa.iae.nl) Received: by ariel.xaa.iae.nl (VMailer, from userid 1008) id E61F24568; Fri, 7 Aug 1998 15:47:21 +0200 (CEST) Message-ID: <19980807154721.A865@xaa.iae.nl> Date: Fri, 7 Aug 1998 15:47:21 +0200 From: Mark Huizer To: Tom Cc: Dusk Auriel Sykotik , Bruce Evans , dg@root.com, narvi@haldjas.folklore.ee, freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc References: <19980806181215.A7652@xaa.iae.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Tom on Thu, Aug 06, 1998 at 09:35:47AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hmm... then we should write a nice DoS attack for apache, would that be a > > reason for solving it? > > Couldn't be done. CGI scripts are so short lived, that that memory gets > cleaned up on its own anyhow. Perhaps specific a DoS attack could be > tailored to a specific CGI script, but I would argue that the CGI script > is broken. CGI is used less and less anyhow, as peole use better and > faster methods of server side scripting. > OK, how come a poor little apache server doesn't like this: GET / HTTP/1.0 User-Agent: a User-Agent: aaaaaaaaaaaaaaaaaaaaaa (repeat last 2 lines 20000 times) (empty line) apache on a Linux machine here is still thinking about wheterh or not to return 100M, time to test it on my home FreeBSD server :-) Mark -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 07:07:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09182 for freebsd-current-outgoing; Fri, 7 Aug 1998 07:07:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coleridge.kublai.com (coleridge.kublai.com [207.96.1.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09171 for ; Fri, 7 Aug 1998 07:07:06 -0700 (PDT) (envelope-from shmit@coleridge.kublai.com) Received: (from shmit@localhost) by coleridge.kublai.com (8.8.8/8.8.8) id KAA20626; Fri, 7 Aug 1998 10:06:45 -0400 (EDT) (envelope-from shmit) Message-ID: <19980807100643.33286@kublai.com> Date: Fri, 7 Aug 1998 10:06:43 -0400 From: Brian Cully To: Daniel Eischen Cc: freebsd-current@FreeBSD.ORG Subject: Re: Pthreads woes revisited. Reply-To: shmit@kublai.com Mail-Followup-To: Daniel Eischen , freebsd-current@FreeBSD.ORG References: <199808062113.RAA18177@pcnet1.pcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199808062113.RAA18177@pcnet1.pcnet.com>; from Daniel Eischen on Thu, Aug 06, 1998 at 05:13:02PM -0400 X-Sender: If your mailer pays attention to this, it's broken. X-PGP-Info: finger shmit@kublai.com for my public key. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 06, 1998 at 05:13:02PM -0400, Daniel Eischen wrote: > You're not adding the pthread_yield() call that I added after > the pthread_cond_signal(). Your program is bogus because there > is no guarantee that the main thread will release the CPU in > order for the other task to run. You need to perform some > sort of blocking operation after the pthread_cond_signal. I > chose to use pthread_yield, although sleep would work just as > well. Do'h! I missed that. That did make the sample program work, so it looks like the error was mine all along, sorry for troubling everybody. -bjc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 07:10:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09986 for freebsd-current-outgoing; Fri, 7 Aug 1998 07:10:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09979 for ; Fri, 7 Aug 1998 07:10:52 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id QAA17530; Fri, 7 Aug 1998 16:06:10 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 7 Aug 1998 16:06:10 +0200 (MET DST) Mime-Version: 1.0 To: Mark Huizer Cc: Tom , Dusk Auriel Sykotik , Bruce Evans , dg@root.com, narvi@haldjas.folklore.ee, freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc References: <19980806181215.A7652@xaa.iae.nl> <19980807154721.A865@xaa.iae.nl> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 07 Aug 1998 16:06:09 +0200 In-Reply-To: Mark Huizer's message of "Fri, 7 Aug 1998 15:47:21 +0200" Message-ID: Lines: 24 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id HAA09980 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Huizer writes: > OK, how come a poor little apache server doesn't like this: > > GET / HTTP/1.0 > User-Agent: a > User-Agent: aaaaaaaaaaaaaaaaaaaaaa > (repeat last 2 lines 20000 times) > (empty line) > > apache on a Linux machine here is still thinking about wheterh or not to > return 100M, time to test it on my home FreeBSD server :-) So maybe it's time to switch to thttpd. Seriously, Apache should not rely on getenv() / setenv(). It should instead build an array of environment variables which it then passes to execvt(). Self-starting dynamically sized arrays (and strings) are easy enouugh to write, and if you use an exponential growth function the performance impact is negligible (in fact, I wouldn't be surprised if it turned out to be a lot faster than getenv() / setenv()) DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 07:16:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11043 for freebsd-current-outgoing; Fri, 7 Aug 1998 07:16:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11033 for ; Fri, 7 Aug 1998 07:16:51 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id QAA01227; Fri, 7 Aug 1998 16:06:56 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id MAA03715; Fri, 7 Aug 1998 12:11:01 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808071011.MAA03715@semyam.dinoco.de> To: Bruce Evans cc: syko@sykotik.org, dg@root.com, freebsd-current@FreeBSD.ORG, freebsd@xaa.iae.nl, narvi@haldjas.folklore.ee, seggers@semyam.dinoco.de Subject: Re: memory leaks in libc In-reply-to: Your message of "Fri, 07 Aug 1998 02:36:07 +1000." <199808061636.CAA00012@godzilla.zeta.org.au> Date: Fri, 07 Aug 1998 12:11:01 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > The env functions are already costly. They use dumb linear searches > and malloc(), and don't alloc a little more than necessary so that the > environment can grow a little without reallocation. Garbage collection Maybe the ideal solution would be to put the variables one encounters on a linear search into a more convenient data structure like a tree for later references and on subsequent getenv's one first checks in the tree for the variable and if it is not there starts from the point where the last linear search ended. If we brought over all variables we only consult the tree. Settings by setenv get put into the tree right away. To get the memory leak fixed each node entry contains a boolean which indicates the origin of the string, i.e. false for those we got from the list and true for those we malloced. For convenient subprocess creation where one needs an array of poin- ters to the environment variable settings one could have a parallel array of pointers and put an index into this array in the nodes. Then one can easily update this array while one manipulates the node. Does that sound reasonable? It would make frequent requests for the same variable fast and fixes the memory leak. The disadvantage is the time penalty for a variable lookup where the variable is not already in the tree and that we need a little bit more memory for the nodes. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 07:23:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12236 for freebsd-current-outgoing; Fri, 7 Aug 1998 07:23:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12213; Fri, 7 Aug 1998 07:23:25 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id AAA16799; Sat, 8 Aug 1998 00:23:04 +1000 Date: Sat, 8 Aug 1998 00:23:04 +1000 From: Bruce Evans Message-Id: <199808071423.AAA16799@godzilla.zeta.org.au> To: current@FreeBSD.ORG, hackers@FreeBSD.ORG, mturpin@shadow.spel.com Subject: Re: Kernel compile problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >When I try to compile a GENERIC (-current as of 2:00PM (EDT) Aug 6,1998) >kernel I get the following error. Am I doing something wrong? >cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit >-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith >-Winline -Wuninitialized -ansi -nostdinc -I- -I. -I../.. -I../../../include >-DKERNEL -include opt_global.h ../../scsi/cd.c > >In file included from ../../scsi/cd.c:48: >ioconf.h:11: conflicting types for `fdintr' >../../i386/isa/isa_device.h:155: previous declaration of `fdintr' >ioconf.h:11: warning: redundant redeclaration of `fdintr' in same scope >../../i386/isa/isa_device.h:155: warning: previous declaration of `fdintr' >... Rebuild, reinstall and rerun config. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 08:04:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18807 for freebsd-current-outgoing; Fri, 7 Aug 1998 08:04:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18793 for ; Fri, 7 Aug 1998 08:04:19 -0700 (PDT) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.8.8/8.8.7) with SMTP id KAA14839; Fri, 7 Aug 1998 10:03:43 -0500 (CDT) Message-Id: <199808071503.KAA14839@ns.tar.com> From: "Richard Seaman, Jr." To: "John Birrell" Cc: "current@freebsd.org" Date: Fri, 07 Aug 98 10:03:43 -0500 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Pthreads woes revisited. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998 13:36:31 +1000 (EST), John Birrell wrote: >Amancio Hasty wrote: >> Curious, whats missing from the kernel for us to have kernel threads? >> >> Perhaps John Dyson can help us out over here ... > >The last problem I was having was with the user_ldt being restored >on context switches. AFAIK John never built in the patches I sent him. Is there a description of what needs to be done, though? Are your patches available anywhere? If someone is really going to look at this, I assume they don't want to duplicate work already started, and I assume they don't want to go in some direction the core team doesn't support? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 08:50:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25794 for freebsd-current-outgoing; Fri, 7 Aug 1998 08:50:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from canonware.com (canonware.com [206.184.206.112]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA25787 for ; Fri, 7 Aug 1998 08:50:52 -0700 (PDT) (envelope-from jasone@canonware.com) Received: (qmail 1627 invoked by uid 1001); 7 Aug 1998 15:47:23 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Aug 1998 15:47:23 -0000 Date: Fri, 7 Aug 1998 08:47:23 -0700 (PDT) From: Jason Evans To: John Birrell cc: alk@pobox.com, current@FreeBSD.ORG Subject: Re: Pthreads woes revisited. In-Reply-To: <199808070849.SAA04153@cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998, John Birrell wrote: > Tony Kimball wrote: > > Ouch! Like some (many?) others, in my world the whole value > > of 3.0 is wrapt in SMP and kernel threads. Nothing else counts, > > comparatively speaking. SMP is rather pointless for me as well if kernel threads don't come with it. > I doubt that introducing further delays would create a flurry of activity > aimed at providing added value. All that would happen is that the same > value would be delivered later. > > [ Anybody reading this who wants to prove me wrong was 9 weeks to submit > a PR and nag a committer to get it worked on. The PR should contain > patches relative to -current, though. ] Can you summarize what needs done, how much effort you expect it is, and give a pointer or two on where to look in the source? If it's within my technical abilities, I'm willing to help make kernel threads work sooner rather than later. Jason Jason Evans Email: [jasone@canonware.com] Web: [http://www.canonware.com/~jasone] Home phone: [(650) 856-8204] Work phone: [(408) 774-8007] Quote: ["Invention is 1% inspiration and 99% perspiration" - Thomas Edison] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 09:09:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27972 for freebsd-current-outgoing; Fri, 7 Aug 1998 09:09:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27955 for ; Fri, 7 Aug 1998 09:09:25 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id MAA22564; Fri, 7 Aug 1998 12:09:03 -0400 (EDT) (envelope-from luoqi) Date: Fri, 7 Aug 1998 12:09:03 -0400 (EDT) From: Luoqi Chen Message-Id: <199808071609.MAA22564@lor.watermarkgroup.com> To: julian@whistle.com, kkennawa@physics.adelaide.edu.au Subject: Re: Softupdates panic Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, here's the problem simplified: > > cd /tmp (assuming mounted soft-updates) > mkdir d1 > mkdir d1/d2 > mkdir d2 > mv d2 d1 > rmdir d1/d2 > rmdir d1 > [system will panic in 15 seconds at 'sync' of that data.] > > fix to follow. (and checked in I guess) > > julian > I looked at the problem and figured out what went wrong. During the rename step (mv d2 d1), the target directory d1/d2 is deleted and a dirrem dependency is generated. Normally, a dirrem dependency would decrease the parent's link count by 1 and subdirectory's link count by 2. But for this particular dirrem, we don't want to decrement the parent's link count, otherwise we would the panic above. The solution would be mark this dirrem as such, and don't decrement the parent's link count when it's handled. Attached is a fix. -lq Index: ffs_softdep.c =================================================================== RCS file: /fun/cvs/src/contrib/sys/softupdates/ffs_softdep.c,v retrieving revision 1.12 diff -u -r1.12 ffs_softdep.c --- ffs_softdep.c 1998/06/12 21:21:26 1.12 +++ ffs_softdep.c 1998/08/07 15:37:57 @@ -2436,6 +2436,7 @@ * Allocate a new dirrem and ACQUIRE_LOCK. */ dirrem = newdirrem(bp, dp, ip, isrmdir); + dirrem->dm_state |= DIRCHG; pagedep = dirrem->dm_pagedep; /* @@ -2546,6 +2547,15 @@ ip->i_flag |= IN_CHANGE; if ((error = UFS_TRUNCATE(vp, (off_t)0, 0, p->p_ucred, p)) != 0) softdep_error("handle_workitem_remove: truncate", error); + /* + * Target directory deletion during a directory rename. The + * parent directory's link count doesn't need to be decremented. + */ + if (dirrem->dm_state & DIRCHG) { + vput(vp); + WORKITEM_FREE(dirrem, D_DIRREM); + return; + } ACQUIRE_LOCK(&lk); (void) inodedep_lookup(ip->i_fs, dirrem->dm_oldinum, DEPALLOC, &inodedep); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 09:18:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29293 for freebsd-current-outgoing; Fri, 7 Aug 1998 09:18:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA29215 for ; Fri, 7 Aug 1998 09:17:49 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z4pCe-0002v7-00; Fri, 7 Aug 1998 09:17:16 -0700 Date: Fri, 7 Aug 1998 09:17:14 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Mark Huizer cc: freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-Reply-To: <19980807154721.A865@xaa.iae.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998, Mark Huizer wrote: > > > Hmm... then we should write a nice DoS attack for apache, would that be a > > > reason for solving it? > > > > Couldn't be done. CGI scripts are so short lived, that that memory gets > > cleaned up on its own anyhow. Perhaps specific a DoS attack could be > > tailored to a specific CGI script, but I would argue that the CGI script > > is broken. CGI is used less and less anyhow, as peole use better and > > faster methods of server side scripting. > > > OK, how come a poor little apache server doesn't like this: > > GET / HTTP/1.0 > User-Agent: a > User-Agent: aaaaaaaaaaaaaaaaaaaaaa > (repeat last 2 lines 20000 times) > (empty line) > > apache on a Linux machine here is still thinking about wheterh or not to > return 100M, time to test it on my home FreeBSD server :-) Really nothing to do with setenv/putenv (which Apache doesn't even use). > Mark > -- > Nice testing in little China... Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 09:24:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01056 for freebsd-current-outgoing; Fri, 7 Aug 1998 09:24:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA01035 for ; Fri, 7 Aug 1998 09:24:08 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z4pIy-0003Xy-00; Fri, 7 Aug 1998 09:23:48 -0700 Date: Fri, 7 Aug 1998 09:23:47 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= cc: freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > apache on a Linux machine here is still thinking about wheterh or not to > > return 100M, time to test it on my home FreeBSD server :-) > > So maybe it's time to switch to thttpd. > > Seriously, Apache should not rely on getenv() / setenv(). It should It doesn't. Whatever is being exploited, it isn't that. Besides there are tons of such overload DoS attacks for web servers. How about just open connection and do nothing? That works on every web server. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 10:05:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08068 for freebsd-current-outgoing; Fri, 7 Aug 1998 10:05:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08013 for ; Fri, 7 Aug 1998 10:05:19 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id KAA05529; Fri, 7 Aug 1998 10:03:43 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma005525; Fri Aug 7 10:03:22 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id KAA29656; Fri, 7 Aug 1998 10:03:20 -0700 (PDT) From: Archie Cobbs Message-Id: <199808071703.KAA29656@bubba.whistle.com> Subject: Re: memory leaks in libc In-Reply-To: <199808070247.MAA03023@cimlogic.com.au> from John Birrell at "Aug 7, 98 12:47:23 pm" To: jb@cimlogic.com.au (John Birrell) Date: Fri, 7 Aug 1998 10:03:20 -0700 (PDT) Cc: archie@whistle.com, freebsd-current@FreeBSD.ORG, bde@zeta.org.au, wollman@khavrinen.lcs.mit.edu, dg@root.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Birrell writes: > Archie Cobbs wrote: > > OK, just to prove I'm not lazy... try this. > > And a thread safe version? Well, setenv() and unsetenv() are not thread safe as they currently exist. How does this look? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com Index: getenv.c =================================================================== RCS file: /cvs/freebsd/src/lib/libc/stdlib/getenv.c,v retrieving revision 1.2 diff -c -u -r1.2 getenv.c --- getenv.c 1995/10/17 21:37:41 1.2 +++ getenv.c 1998/08/07 17:03:04 @@ -39,6 +39,12 @@ #include #include +#include "libc_private.h" +#include "spinlock.h" +static spinlock_t thread_lock = _SPINLOCK_INITIALIZER; +#define THREAD_LOCK() if (__isthreaded) _SPINLOCK(&thread_lock); +#define THREAD_UNLOCK() if (__isthreaded) _SPINUNLOCK(&thread_lock); + inline char *__findenv __P((const char *, int *)); /* @@ -78,6 +84,28 @@ } /* + * __env_lock() + * + * Obtain mutex lock on the environment. Should be static. + */ +void +__env_lock(void) +{ + THREAD_LOCK(); +} + +/* + * __env_unlock() + * + * Release mutex lock on the environment. Should be static. + */ +void +__env_unlock(void) +{ + THREAD_UNLOCK(); +} + +/* * getenv -- * Returns ptr to value associated with name, if any, else NULL. */ @@ -86,6 +114,11 @@ const char *name; { int offset; + char *rtn; - return (__findenv(name, &offset)); + __env_lock(); + rtn = __findenv(name, &offset); + __env_unlock(); + return rtn; } + Index: setenv.c =================================================================== RCS file: /cvs/freebsd/src/lib/libc/stdlib/setenv.c,v retrieving revision 1.3 diff -c -u -r1.3 setenv.c --- setenv.c 1996/07/12 18:55:21 1.3 +++ setenv.c 1998/08/07 17:03:04 @@ -40,7 +40,23 @@ #include char *__findenv __P((const char *, int *)); +void __env_lock __P((void)); +void __env_unlock __P((void)); +/* We keep track of pointers gotten via malloc() using a hash table */ +#define NUMBUCKETS 64 +#define HASH(p) ((((int)(p) >> 24) ^ ((int)(p) >> 16) ^ \ + ((int)(p) >> 8) ^ ((int)(p))) % NUMBUCKETS) + +struct hashp { + void *ptr; + struct hashp *next; +}; +static struct hashp **table; + +static void addhash(void *ptr); +static void rmhash(void *ptr); + /* * setenv -- * Set the value of the environmental variable "name" to be @@ -55,16 +71,21 @@ extern char **environ; static int alloced; /* if allocated space before */ register char *c; + char *newptr; int l_value, offset; if (*value == '=') /* no `=' in value */ ++value; l_value = strlen(value); + __env_lock(); if ((c = __findenv(name, &offset))) { /* find if already exists */ - if (!rewrite) + if (!rewrite) { + __env_unlock(); return (0); + } if (strlen(c) >= l_value) { /* old larger; copy over */ while ( (*c++ = *value++) ); + __env_unlock(); return (0); } } else { /* create new slot */ @@ -75,14 +96,18 @@ if (alloced) { /* just increase size */ environ = (char **)realloc((char *)environ, (size_t)(sizeof(char *) * (cnt + 2))); - if (!environ) + if (!environ) { + __env_unlock(); return (-1); + } } else { /* get new space */ alloced = 1; /* copy old entries into it */ p = malloc((size_t)(sizeof(char *) * (cnt + 2))); - if (!p) + if (!p) { + __env_unlock(); return (-1); + } bcopy(environ, p, cnt * sizeof(char *)); environ = p; } @@ -90,11 +115,17 @@ offset = cnt; } for (c = (char *)name; *c && *c != '='; ++c); /* no `=' in name */ - if (!(environ[offset] = /* name + `=' + value */ - malloc((size_t)((int)(c - name) + l_value + 2)))) + if (!(newptr = /* name + `=' + value */ + malloc((size_t)((int)(c - name) + l_value + 2)))) { + __env_unlock(); return (-1); - for (c = environ[offset]; (*c = *name++) && *c != '='; ++c); + } + rmhash(environ[offset]); /* free old value if malloc'd */ + environ[offset] = newptr; /* replace with new region */ + addhash(newptr); /* remember we malloc'd it */ + for (c = newptr; (*c = *name++) && *c != '='; ++c); for (*c++ = '='; (*c++ = *value++); ); + __env_unlock(); return (0); } @@ -110,8 +141,64 @@ register char **p; int offset; - while (__findenv(name, &offset)) /* if set multiple times */ + __env_lock(); + while (__findenv(name, &offset)) { /* if set multiple times */ + rmhash(environ[offset]); /* free memory if malloc'd */ for (p = &environ[offset];; ++p) if (!(*p = *(p + 1))) break; + } + __env_unlock(); +} + +/* + * addhash(ptr) + * + * Add a pointer that we obtained via malloc() to our secret internal + * hash table, so when this variable is deleted or changed, we know to + * free the memory. + */ +static void +addhash(void *ptr) +{ + struct hashp *s; + int bucket; + + /* Create hash table if it doesn't already exist */ + if (table == NULL) { + if ((table = malloc(NUMBUCKETS * sizeof(*table))) == NULL) + return; + } + + /* Create new struct holding pointer and add it to the hash bucket */ + if ((s = malloc(sizeof(*s))) != NULL) + return; + s->ptr = ptr; + bucket = HASH(ptr); + s->next = table[bucket]; + table[bucket] = s; } + +/* + * rmhash(ptr) + * + * Remove a pointer from the hash table and free() it. If the pointer + * was not obtained via malloc(), then it won't be found and we do nothing. + */ +static void +rmhash(void *ptr) +{ + struct hashp **sp, *s; + + if (table == NULL) /* race condition here is ok */ + return; + for (sp = &table[HASH(ptr)]; (s = *sp) != NULL; sp = &s->next) { + if (s->ptr == ptr) { + *sp = s->next; + free(ptr); + free(s); + break; + } + } +} + To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 10:08:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08654 for freebsd-current-outgoing; Fri, 7 Aug 1998 10:08:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA08564 for ; Fri, 7 Aug 1998 10:08:07 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z4pza-0001EO-00; Fri, 7 Aug 1998 11:07:50 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id LAA26324; Fri, 7 Aug 1998 11:08:22 -0600 (MDT) Message-Id: <199808071708.LAA26324@harmony.village.org> To: Poul-Henning Kamp Subject: Re: Pthreads woes revisited. Cc: alk@pobox.com, current@FreeBSD.ORG In-reply-to: Your message of "Fri, 07 Aug 1998 10:42:49 +0200." <3001.902479369@critter.freebsd.dk> References: <3001.902479369@critter.freebsd.dk> Date: Fri, 07 Aug 1998 11:08:22 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3001.902479369@critter.freebsd.dk> Poul-Henning Kamp writes: : 3.0 goes out on september 15th, come hell or high water. Is this a typo, or has the release been moved up a month? Jordan has been saying October 15 for a long time. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 10:14:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10111 for freebsd-current-outgoing; Fri, 7 Aug 1998 10:14:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10068 for ; Fri, 7 Aug 1998 10:14:21 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id KAA05649; Fri, 7 Aug 1998 10:13:14 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma005645; Fri Aug 7 10:12:48 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id KAA29716; Fri, 7 Aug 1998 10:12:48 -0700 (PDT) From: Archie Cobbs Message-Id: <199808071712.KAA29716@bubba.whistle.com> Subject: Re: memory leaks in libc In-Reply-To: <199808070332.XAA17093@khavrinen.lcs.mit.edu> from Garrett Wollman at "Aug 6, 98 11:32:21 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Fri, 7 Aug 1998 10:12:48 -0700 (PDT) Cc: archie@whistle.com, freebsd-current@FreeBSD.ORG, bde@zeta.org.au, wollman@khavrinen.lcs.mit.edu, dg@root.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman writes: > >> malloc() is simple enough. It would solve the problem for programs > >> than need it (a real world example of which exists at Whistle). > > > OK, just to prove I'm not lazy... try this. > > Now having gone to that effort, you can just add it to your program > that needs it, and we don't have to bear the kluge in the C library. I just don't understand where you're coming from. There is a clear bug in the standard library, we agree on this right? You are saying that it's not worth fixing, because... - The cost is too high? I disagree, it's easy to fix and I've done it for you. The space increase is negligible, and the time increase is negligible, unless your program does a lot of environment operations, in which case you already have a bigger problem: a built-in memory leak! - Because no program you've ever written suffers from the bug? Others have encountered it in real programs. - It's a kludge? The kludge nature of this whole problem is already inherited from the "environ" variable semantics. There's nothing kludgey about the bug fix, other than that it takes one kludge to undo the negative effects (memory leak) of an existing kludge. > I believe that any program which suffers serious harm from the memory > leak probably needs to use a different environment-access model. Yes, until we fix the bug. Then they don't anymore, that's the whole point. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 10:22:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12224 for freebsd-current-outgoing; Fri, 7 Aug 1998 10:22:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12056 for ; Fri, 7 Aug 1998 10:22:00 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id NAA20680; Fri, 7 Aug 1998 13:21:21 -0400 (EDT) (envelope-from wollman) Date: Fri, 7 Aug 1998 13:21:21 -0400 (EDT) From: Garrett Wollman Message-Id: <199808071721.NAA20680@khavrinen.lcs.mit.edu> To: Archie Cobbs Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), freebsd-current@FreeBSD.ORG, bde@zeta.org.au, dg@root.com Subject: Re: memory leaks in libc In-Reply-To: <199808071712.KAA29716@bubba.whistle.com> References: <199808070332.XAA17093@khavrinen.lcs.mit.edu> <199808071712.KAA29716@bubba.whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> I believe that any program which suffers serious harm from the memory >> leak probably needs to use a different environment-access model. > Yes, until we fix the bug. Then they don't anymore, that's the whole point. No, you've missed the point entirely. *Any program which does enough playing around with the environment to be harmed by this memory leak is using a totally inappropriate interface.* -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 10:39:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14875 for freebsd-current-outgoing; Fri, 7 Aug 1998 10:39:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14842 for ; Fri, 7 Aug 1998 10:38:58 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id KAA05889; Fri, 7 Aug 1998 10:37:44 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma005887; Fri Aug 7 10:37:26 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id KAA29957; Fri, 7 Aug 1998 10:37:26 -0700 (PDT) From: Archie Cobbs Message-Id: <199808071737.KAA29957@bubba.whistle.com> Subject: Re: memory leaks in libc In-Reply-To: <199808071721.NAA20680@khavrinen.lcs.mit.edu> from Garrett Wollman at "Aug 7, 98 01:21:21 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Fri, 7 Aug 1998 10:37:26 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG, bde@zeta.org.au, dg@root.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman writes: > No, you've missed the point entirely. *Any program which does enough > playing around with the environment to be harmed by this memory leak > is using a totally inappropriate interface.* I disagree with that statement! And I base my disagreement not on conjecture but on experience. Here's a REAL example.. suppose you have a program which runs as a daemon, and it's job is to display the time on some display. The display of the time is generated via strftime(3). The device this daemon is running on allows the timezone to be configured. In order to display the time in the correct timezone, every so often (every 30 seconds or so) this deamon must make sure that strftime() knows about the *currently set* timezone, not the timezone that was set when the daemon started (which could be arbitrarily long ago in the past). How can it possibly do this? The only way to get strftime() to acknowledge a change in timezone is to do something like this: unsetenv("TZ"); tzset(); setenv("TZ", "/etc/localtime", 1); tzset(); (if you don't believe me then read the source for tzset() et. al.) Guess what? Every 30 seconds this deamon is malloc()'ing a new malloc block. Your supposedly reliable device will crash in a matter of days when it exhausts all available memory because of the memory leak. There's nothing "totally inappropriate" about what the daemon is doing -- in fact, using setenv() is the only way to do what it wants to do, ie., get libc to acknowledge a timezone change. My point? I agree with you that a program that implements a relational database using setenv()/getenv() as a backend would be "totally inappropriate". What I'm saying is that not every program which suffers from the setenv() memory leak is doing something "totally inappropriate". -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 12:05:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28618 for freebsd-current-outgoing; Fri, 7 Aug 1998 12:05:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28609 for ; Fri, 7 Aug 1998 12:05:35 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id VAA03226; Fri, 7 Aug 1998 21:01:52 +0200 (CEST) To: Archie Cobbs cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), freebsd-current@FreeBSD.ORG, bde@zeta.org.au, dg@root.com Subject: Re: memory leaks in libc In-reply-to: Your message of "Fri, 07 Aug 1998 10:12:48 PDT." <199808071712.KAA29716@bubba.whistle.com> Date: Fri, 07 Aug 1998 21:01:52 +0200 Message-ID: <3224.902516512@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808071712.KAA29716@bubba.whistle.com>, Archie Cobbs writes: >Garrett Wollman writes: >> >> malloc() is simple enough. It would solve the problem for programs >> >> than need it (a real world example of which exists at Whistle). >> >> > OK, just to prove I'm not lazy... try this. >> >> Now having gone to that effort, you can just add it to your program >> that needs it, and we don't have to bear the kluge in the C library. > >I just don't understand where you're coming from. There is a clear >bug in the standard library, we agree on this right? You are saying >that it's not worth fixing, because... I think there is agreement that a bogus API was defined long time ago, and since getting rid of that API not worth even discussing, this entire thread is a waste of time. Summary: Yes, there is a memoryleak associated with use of this API, if that is unacceptable for your application then don't use this API. Would this thread please DROP DEAD preferably RIGHT NOW! THANKYOU! -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 12:13:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29889 for freebsd-current-outgoing; Fri, 7 Aug 1998 12:13:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29866 for ; Fri, 7 Aug 1998 12:13:02 -0700 (PDT) (envelope-from wosch@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id VAA11811 for freebsd-current@freebsd.org; Fri, 7 Aug 1998 21:12:46 +0200 (CEST) (envelope-from wosch@panke.de.freebsd.org) Received: (from wosch@localhost) by campa.panke.de (8.8.8/8.8.8) id UAA20965; Fri, 7 Aug 1998 20:54:21 +0200 (MET DST) (envelope-from wosch) Date: Fri, 7 Aug 1998 20:54:21 +0200 (MET DST) Message-Id: <199808071854.UAA20965@campa.panke.de> From: Wolfram Schneider To: freebsd-current@FreeBSD.ORG Subject: removing -batch option from adduser command MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want remove the adduser(8) option `-batch'. Adduser was written as an *interactive* command for newbies. The pw(8) does now a much better job for adding users from command line. Also, the -batch option is not well tested, buggy and unsupported. -- Wolfram Schneider http://www.freebsd.org/~w/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 12:24:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02447 for freebsd-current-outgoing; Fri, 7 Aug 1998 12:24:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02404 for ; Fri, 7 Aug 1998 12:24:35 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA23168; Fri, 7 Aug 1998 13:24:03 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA20307; Fri, 7 Aug 1998 13:24:00 -0600 Date: Fri, 7 Aug 1998 13:24:00 -0600 Message-Id: <199808071924.NAA20307@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Garrett Wollman Cc: Archie Cobbs , freebsd-current@FreeBSD.ORG, bde@zeta.org.au, dg@root.com Subject: Re: memory leaks in libc In-Reply-To: <199808071721.NAA20680@khavrinen.lcs.mit.edu> References: <199808070332.XAA17093@khavrinen.lcs.mit.edu> <199808071712.KAA29716@bubba.whistle.com> <199808071721.NAA20680@khavrinen.lcs.mit.edu> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> I believe that any program which suffers serious harm from the memory > >> leak probably needs to use a different environment-access model. > > > Yes, until we fix the bug. Then they don't anymore, that's the whole point. > > No, you've missed the point entirely. *Any program which does enough > playing around with the environment to be harmed by this memory leak > is using a totally inappropriate interface.* That's not for you to decide, or even make judgements on. If you provide an interface, it should be bug-free. If there where bugs in our Q macros, and people were using them for inappropriate reasons, it doesn't justify the bugs. They may be the most *appropriate* and *portable* inteface available to programs, even if you don't like it personally. I'm in agreement with Archie here. We're not here to change the world to a different model than anyone else uses, we're here to provide a bug-free stable OS. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 12:25:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02527 for freebsd-current-outgoing; Fri, 7 Aug 1998 12:25:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02509 for ; Fri, 7 Aug 1998 12:25:09 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id MAA27403; Fri, 7 Aug 1998 12:17:49 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Poul-Henning Kamp cc: alk@pobox.com, current@FreeBSD.ORG Subject: Re: Pthreads woes revisited. In-reply-to: Your message of "Fri, 07 Aug 1998 10:42:49 +0200." <3001.902479369@critter.freebsd.dk> Date: Fri, 07 Aug 1998 12:17:49 -0700 Message-ID: <27399.902517469@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 3.0 goes out on september 15th, come hell or high water. Erm... October. October 15th. See the Really Quick Newsletter on the support page for the proposed schedule. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 12:33:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04119 for freebsd-current-outgoing; Fri, 7 Aug 1998 12:33:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04109 for ; Fri, 7 Aug 1998 12:33:20 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id VAA17410; Fri, 7 Aug 1998 21:32:33 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 7 Aug 1998 21:32:32 +0200 (MET DST) Mime-Version: 1.0 To: Archie Cobbs Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), freebsd-current@FreeBSD.ORG, bde@zeta.org.au, dg@root.com Subject: Re: memory leaks in libc References: <199808071737.KAA29957@bubba.whistle.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 07 Aug 1998 21:32:31 +0200 In-Reply-To: Archie Cobbs's message of "Fri, 7 Aug 1998 10:37:26 -0700 (PDT)" Message-ID: Lines: 38 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id MAA04113 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs writes: > Garrett Wollman writes: > > No, you've missed the point entirely. *Any program which does enough > > playing around with the environment to be harmed by this memory leak > > is using a totally inappropriate interface.* > I disagree with that statement! And I base my disagreement not on > conjecture but on experience. There is only one situation in which you need to change the environment: fork-and-exec, in which case it is trivial to construct a fresh environment for your child process in a safe manner. If you're not fork-and-execing, use program variables instead (which you initialize with getenv()). If you're writing a shell and need to keep track of lots of environment variables and pass them to your children, you're in both situations at once; use a hash table for quick lookup (you'll need it for variable substitution in command lines) and pass execve() a list of pointers to the contents of your hash table. > How can it possibly do this? The only way to get strftime() to > acknowledge a change in timezone is to do something like this: > > unsetenv("TZ"); > tzset(); > setenv("TZ", "/etc/localtime", 1); > tzset(); Then strftime() should be taken out and shot. Arguably, so should setenv(), but fixing setenv() will only hide the symptoms of bad programming practice. That said, I don't really see any reason *not* to commit your setenv() replacement, if it works properly. It's just that there aren't really any arguments *for* the commit, either. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 12:50:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06997 for freebsd-current-outgoing; Fri, 7 Aug 1998 12:50:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06988 for ; Fri, 7 Aug 1998 12:50:41 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id VAA18905; Fri, 7 Aug 1998 21:50:14 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 7 Aug 1998 21:50:13 +0200 (MET DST) Mime-Version: 1.0 To: Wolfram Schneider Cc: freebsd-current@FreeBSD.ORG Subject: Re: removing -batch option from adduser command References: <199808071854.UAA20965@campa.panke.de> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 07 Aug 1998 21:50:13 +0200 In-Reply-To: Wolfram Schneider's message of "Fri, 7 Aug 1998 20:54:21 +0200 (MET DST)" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id MAA06991 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wolfram Schneider writes: > I want remove the adduser(8) option `-batch'. Adduser was written as > an *interactive* command for newbies. The pw(8) does now a much better > job for adding users from command line. Also, the -batch option is > not well tested, buggy and unsupported. The crowd breaks out in spontaneous applause. Well, OK, maybe it doesn't, but I do :) DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 12:52:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07267 for freebsd-current-outgoing; Fri, 7 Aug 1998 12:52:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07262 for ; Fri, 7 Aug 1998 12:52:26 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA07644; Fri, 7 Aug 1998 12:51:23 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma007642; Fri Aug 7 12:51:04 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id MAA04454; Fri, 7 Aug 1998 12:51:04 -0700 (PDT) From: Archie Cobbs Message-Id: <199808071951.MAA04454@bubba.whistle.com> Subject: Re: memory leaks in libc In-Reply-To: <3224.902516512@critter.freebsd.dk> from Poul-Henning Kamp at "Aug 7, 98 09:01:52 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Fri, 7 Aug 1998 12:51:04 -0700 (PDT) Cc: wollman@khavrinen.lcs.mit.edu, freebsd-current@FreeBSD.ORG, bde@zeta.org.au, dg@root.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > >I just don't understand where you're coming from. There is a clear > >bug in the standard library, we agree on this right? You are saying > >that it's not worth fixing, because... > > I think there is agreement that a bogus API was defined long time ago, > and since getting rid of that API not worth even discussing, this > entire thread is a waste of time. ? Who's talking about changing the API? I think you're misunderstanding the issue. The issue is simply: there's a memory leak in libc, should we or should we not fix it? It's a standard bug-fix cost/benefit question. > Yes, there is a memoryleak associated with use of this API, > if that is unacceptable for your application then don't use this API. The attitude reflected in this statement is the exact opposite of mine, which is: Yes, there is a memoryleak associated with use of this API, let's fix the stupid bug and get on with it! Am I crazy for thinking that? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 13:00:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08599 for freebsd-current-outgoing; Fri, 7 Aug 1998 13:00:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08530 for ; Fri, 7 Aug 1998 13:00:01 -0700 (PDT) (envelope-from lile@stdio.com) Received: (from lile@localhost) by heathers.stdio.com (8.8.8/8.8.8) id PAA15000; Fri, 7 Aug 1998 15:56:11 -0400 (EDT) Date: Fri, 7 Aug 1998 15:56:10 -0400 (EDT) From: "Larry S. Lile" To: Bruce Evans cc: current@FreeBSD.ORG Subject: Re: Kernel compile problem In-Reply-To: <199808071423.AAA16799@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 8 Aug 1998, Bruce Evans wrote: > >When I try to compile a GENERIC (-current as of 2:00PM (EDT) Aug 6,1998) > >kernel I get the following error. Am I doing something wrong? > > >cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit > >-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > >-Winline -Wuninitialized -ansi -nostdinc -I- -I. -I../.. -I../../../include > >-DKERNEL -include opt_global.h ../../scsi/cd.c > > > >In file included from ../../scsi/cd.c:48: > >ioconf.h:11: conflicting types for `fdintr' > >../../i386/isa/isa_device.h:155: previous declaration of `fdintr' > >ioconf.h:11: warning: redundant redeclaration of `fdintr' in same scope > >../../i386/isa/isa_device.h:155: warning: previous declaration of `fdintr' > >... > > Rebuild, reinstall and rerun config. > > Bruce Speaking of this, what is the new magic with *intr routines. I am still working on my token ring driver and have cvsup'd to the latest level only to find out that my driver now panics when calling routines outside my tokintr like tok_tx_intr. Is it now neccesary to make these static? or inline? And is there some better fix for declaring your *intr routine or must you specify it in isa_device.h? Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 13:03:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09211 for freebsd-current-outgoing; Fri, 7 Aug 1998 13:03:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from redfish.go2net.com (redfish.go2net.com [207.178.55.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA09197 for ; Fri, 7 Aug 1998 13:03:14 -0700 (PDT) (envelope-from marcs@go2net.com) Received: from marcs by redfish.go2net.com with smtp (Exim 1.82 #2) id 0z4sfG-0000em-00; Fri, 7 Aug 1998 12:59:02 -0700 Date: Fri, 7 Aug 1998 12:59:02 -0700 (PDT) From: Marc Slemko X-Sender: marcs@redfish To: Dusk Auriel Sykotik cc: freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Aug 1998, Dusk Auriel Sykotik wrote: > Apache uses them quite frequently. And this could make it very costly on > large webservers. Where I work, we have hundreds of connections to some > of our webservers per minute. We also use cgi scripts very frequently, > and these use *env* functions quite frequently as well. Where exactly is Apache using getenv() and setenv() frequently? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 13:06:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09889 for freebsd-current-outgoing; Fri, 7 Aug 1998 13:06:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09866 for ; Fri, 7 Aug 1998 13:06:25 -0700 (PDT) (envelope-from kargl@troutmask.apl.washington.edu) Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.8.8/8.8.8) id NAA00348 for freebsd-current@freebsd.org; Fri, 7 Aug 1998 13:09:59 -0700 (PDT) (envelope-from kargl) From: "Steven G. Kargl" Message-Id: <199808072009.NAA00348@troutmask.apl.washington.edu> Subject: vm panic To: freebsd-current@FreeBSD.ORG Date: Fri, 7 Aug 1998 13:09:59 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ladies and Gents, I cvsup'd on Aug 7 at 12:02 pst. make world survives. Build a new kernel, and reboot gives (transcribed by hand) Fatal trap 12: page fault while in kernel mode fault virtual address = 0xeffd300c fault code = supervisor read, page not present instruction pointer = 0x8:0xf01d3187 stack pointer = 0x10:0xf4bfeae8 frame pointer = 0x10:0xf4bfeb08 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = idle interrupt mask = net tty bio cam kernel: type 12 trap, code = 0 Stopped at _pmap_enter+0x97; movl 0(%ecx), %ecx The initial part of a trace at the DDB> prompt gives _pmap_enter _vm_fault _trap_pfault _trap _calltrap Sources cvssup'd from Aug 5 at 09:35 pst do not exhibit this problem. Dmesg output follow sig. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #7: Fri Jul 31 13:24:39 PDT 1998 root@troutmask.apl.washington.edu:/usr/src/sys/compile/TROUTMASK Timecounter "i8254" frequency 1193182 Hz cost 2854 ns Timecounter "TSC" frequency 119752513 Hz cost 225 ns CPU: Pentium/P54C (119.75-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 100663296 (98304K bytes) avail memory = 95412224 (93176K bytes) DEVFS: ready for devices Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.7.0 vga0: rev 0x00 int a irq 12 on pci0.10.0 ahc0: rev 0x03 int a irq 11 on pci0.12.0 ahc0: aic7870 Single Channel, SCSI Id=7, 16/255 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 ahc0: target 0 Tagged Queuing Device sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 4341MB (8890760 512 byte sectors) ahc0: target 1 Tagged Queuing Device sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 1029MB (2109376 512 byte sectors) sd2 at scbus0 target 2 lun 0 sd2: type 0 fixed SCSI 2 sd2: Direct-Access 699MB (1431760 512 byte sectors) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <8 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface gp0 at 0x2c0 irq 5 on isa gp0: type AT-GPIB/TNT fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/utp/bnc[*UTP*] address 00:20:af:28:08:03 npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround DEVFS: ready to run changing root device to sd0s1a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 13:23:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13797 for freebsd-current-outgoing; Fri, 7 Aug 1998 13:23:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13772 for ; Fri, 7 Aug 1998 13:23:22 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id WAA03585; Fri, 7 Aug 1998 22:19:58 +0200 (CEST) To: Archie Cobbs cc: wollman@khavrinen.lcs.mit.edu, freebsd-current@FreeBSD.ORG, bde@zeta.org.au, dg@root.com Subject: Re: memory leaks in libc In-reply-to: Your message of "Fri, 07 Aug 1998 12:51:04 PDT." <199808071951.MAA04454@bubba.whistle.com> Date: Fri, 07 Aug 1998 22:19:57 +0200 Message-ID: <3583.902521197@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808071951.MAA04454@bubba.whistle.com>, Archie Cobbs writes: >> Yes, there is a memoryleak associated with use of this API, >> if that is unacceptable for your application then don't use this API. > >The attitude reflected in this statement is the exact opposite of mine, >which is: Yes, there is a memoryleak associated with use of this API, >let's fix the stupid bug and get on with it! Am I crazy for thinking >that? Yes, because as has been so elonquently pointed out to you by now, you cannot fix that leak without breaking a few conventions here and there and most likely some running code, for a very little actual benefit. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 13:31:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15681 for freebsd-current-outgoing; Fri, 7 Aug 1998 13:31:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15641 for ; Fri, 7 Aug 1998 13:31:03 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA24590; Fri, 7 Aug 1998 13:22:12 -0700 (PDT) Message-Id: <199808072022.NAA24590@implode.root.com> To: Archie Cobbs cc: phk@critter.freebsd.dk (Poul-Henning Kamp), wollman@khavrinen.lcs.mit.edu, freebsd-current@FreeBSD.ORG, bde@zeta.org.au Subject: Re: memory leaks in libc In-reply-to: Your message of "Fri, 07 Aug 1998 12:51:04 PDT." <199808071951.MAA04454@bubba.whistle.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 07 Aug 1998 13:22:11 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The attitude reflected in this statement is the exact opposite of mine, >which is: Yes, there is a memoryleak associated with use of this API, >let's fix the stupid bug and get on with it! Am I crazy for thinking >that? I wouldn't say you're crazy by thinking that, but I'm still concerned about programs that do a mix of setenv and private frobbing of the env. It seems to me that by "fixing" this memory leak, you're quite likely adding new bugs to existing programs. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 13:36:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16898 for freebsd-current-outgoing; Fri, 7 Aug 1998 13:36:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16762 for ; Fri, 7 Aug 1998 13:36:00 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id QAA165042; Fri, 7 Aug 1998 16:35:39 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <199808071712.KAA29716@bubba.whistle.com> References: <199808070332.XAA17093@khavrinen.lcs.mit.edu> from Garrett Wollman at "Aug 6, 98 11:32:21 pm" Date: Fri, 7 Aug 1998 16:39:37 -0400 To: Archie Cobbs , wollman@khavrinen.lcs.mit.edu (Garrett Wollman) From: Garance A Drosihn Subject: Re: memory leaks in libc Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:12 AM -0700 8/7/98, Archie Cobbs wrote: >Garrett Wollman writes: >> Now having gone to that effort, you can just add it to your program >> that needs it, and we don't have to bear the kluge in the C library. > > I just don't understand where you're coming from. There is a clear > bug in the standard library, we agree on this right? You are saying > that it's not worth fixing, because... I don't know where Garrett is coming from, but I must admit I would be leary of making changes to getenv/setenv. The main reason is that the environment mechanism was poorly thought out and defined to begin with, and thus any changes you make are likely to break something somewhere. By "poorly defined", I mean that there are not good, consistent definitions of what one can and can not expect from a call to getenv/putenv, and thus you can be sure that some code uses those routines in ways you won't forsee. Consider that getenv returns a pointer to the environment variable. It does not malloc any space, it just returns a pointer to the actual value it finds in the current environment. Now consider the following sequence: setenv("NAME","VAL1"); -> does a malloc to store NAME keep = getenv("NAME"); -> returns a pointer to the middle of that malloc'ed area setenv("NAME","VAL2"); -> replaces the value of NAME as is kept in the environment if ( ! strcmp(keep, "VAL1") ) { do_stuff(); } -> Here is the problem. In the above sequence, you -> "know" that setenv malloc'ed the space, and thus -> you would expect that the second setenv should -> free it. However, the program has stored away -> a pointer into that area which it got from getenv, -> and it has every right to believe (due to years of -> precedent) that that pointer will remain valid. -> if you free and reuse that space, you may introduce -> some pretty obscure bugs. And *that* is in the "well-understood" case, were we know that the only things playing with the environment have been setenv and getenv. However, there are plenty of programs which manipulate the environment via other means, and would make life even more complicated. If the question is: Can you design a safe *alternative* to setenv/getenv which would not have this memory-leak side-effect? the answer is definitely yes. However, for the specific routines of getenv/setenv/putenv, the horses left the barn a long time ago. There's no sense trying to lock the door now. I think that the risks of *replacing* getenv/setenv/putenv with a "smarter" version are far greater than the benefits of fixing this memory leak. If you wanted to define some "getenv2/setenv2", which worked on a vector called **environ2 (and *not* the standard, "well-known" environment vector), then there's all kinds of good things you can do. However, in my opinion replacing getenv/setenv is much too risky to be worth it. If you find some stupid program which really does have a serious memory leak due to setenv calls, then fix that one program. The memory leak would be easy enough to find and to fix in a program, as opposed to introducing very non-obvious bugs to a hole slew of programs which are currently working just fine as they are (even if they do occasionally "leak" 64 bytes of memory somewhere, nothing is the worse for that). So, I think Garrett's position is sensible and corrrect, even if his presentation could be somewhat more pleasent or informative. --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 13:41:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17965 for freebsd-current-outgoing; Fri, 7 Aug 1998 13:41:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17937; Fri, 7 Aug 1998 13:40:55 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id NAA11078; Fri, 7 Aug 1998 13:40:29 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 7 Aug 1998 13:40:29 -0700 (PDT) From: Doug White To: Shawn Leas cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: I unsubed, but I'm still getting msgs! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Aug 1998, Shawn Leas wrote: > > Will someone take me off? I have already unsubbed, and authed, AND gotten > confirmation, but CONTINUE to get messages. You followed these instructions exactly? > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ It sounds like you *subscribed* yourself if you had to authorize it. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 13:54:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20603 for freebsd-current-outgoing; Fri, 7 Aug 1998 13:54:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20453 for ; Fri, 7 Aug 1998 13:53:50 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA08584; Fri, 7 Aug 1998 13:53:24 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma008578; Fri Aug 7 13:52:59 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id NAA05035; Fri, 7 Aug 1998 13:52:59 -0700 (PDT) From: Archie Cobbs Message-Id: <199808072052.NAA05035@bubba.whistle.com> Subject: Re: memory leaks in libc In-Reply-To: <199808072022.NAA24590@implode.root.com> from David Greenman at "Aug 7, 98 01:22:11 pm" To: dg@root.com Date: Fri, 7 Aug 1998 13:52:59 -0700 (PDT) Cc: archie@whistle.com, phk@critter.freebsd.dk, wollman@khavrinen.lcs.mit.edu, freebsd-current@FreeBSD.ORG, bde@zeta.org.au X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman writes: > >The attitude reflected in this statement is the exact opposite of mine, > >which is: Yes, there is a memoryleak associated with use of this API, > >let's fix the stupid bug and get on with it! Am I crazy for thinking > >that? > > I wouldn't say you're crazy by thinking that, but I'm still concerned > about programs that do a mix of setenv and private frobbing of the env. > It seems to me that by "fixing" this memory leak, you're quite likely adding > new bugs to existing programs. Fair enough, that's a concern I can understand... I thought about this for a while before when I thought about trying to fix the problem. Here's the logic that I eventually came up with: Algorithm --------- 1. setenv() keeps a private list of all pointers it has obtained from calls to malloc() (these are pointers to individual strings only, not the entire environ[] array which is already kept track of). 2. Whenver any one of these pointers is no longer to be used (either because the variable was overwritten or unsetenv() was called), we call free() to free the pointer. Why any non-broken program will still work ------------------------------------------ Any program is free to play with the environ[] array all it wants to, changing pointers, moving the array, reassigning 'environ", or whatever. At worst, the program will leak some memory each time it does this (nothing new). Example: program says x = malloc(), then says environ[12] = x. We never could free x because it wasn't malloc()'d from within the setenv() code. The only thing that changes is if a program does this: s = getenv("FOO"); putenv("FOO=new-and-longer-value"); /* at this point, new putenv() will free(s), old putenv() won't */ ... /* program references old value of FOO */ printf("Old value of FOO was: %s\n", s); /* this is a bug */ In the last line, "s" is dereferenced. With the existing code, this will not segfault, whereas with the new code it might (if the malloc() library unmaps the page, for example). However, in BOTH cases the results of dereferencing "s" are indeterminate. Even with the old code, *s is not guaranteed to have its old value, because putenv() may overwrite the old value with the new value. Any program which is trying to have determinate behavior and does this contains a bug (in my judgement). So it's sortof like the question about installing phkmalloc(), which caused some buggy programs to start core dumping... do you accomodate the old bugs or fix them? If you can't tolerate this change in the meaning of "indeterminate" then you won't like the fix. My intuition suggests that it's unlikely that any program relies on this bug, since that program is already broken. Morever, I'm closer to the "fix old bugs" approach than the "accomodate old bugs" approach. Anyway, that's the way I see it.. if I missed anything please comment. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 14:14:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25286 for freebsd-current-outgoing; Fri, 7 Aug 1998 14:14:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25111 for ; Fri, 7 Aug 1998 14:13:20 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id QAA13383; Fri, 7 Aug 1998 16:12:13 -0500 (EST) (envelope-from toor) Message-Id: <199808072112.QAA13383@dyson.iquest.net> Subject: Re: Pthreads woes revisited. In-Reply-To: <199808070336.NAA03174@cimlogic.com.au> from John Birrell at "Aug 7, 98 01:36:31 pm" To: jb@cimlogic.com.au (John Birrell) Date: Fri, 7 Aug 1998 16:12:13 -0500 (EST) Cc: hasty@rah.star-gate.com, jb@cimlogic.com.au, shmit@kublai.com, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Birrell said: > Amancio Hasty wrote: > > Curious, whats missing from the kernel for us to have kernel threads? > > > > Perhaps John Dyson can help us out over here ... > > The last problem I was having was with the user_ldt being restored > on context switches. AFAIK John never built in the patches I sent him. > He was always preoccupied with the "next greatest improvement". > I ended up side-lining the work in favour of doing work on the Alpha > port. > I am working on Pthreads for work. However, I did get tied up trying to improve the SMP so that Pthreads work properly there. If someone distills the SMP patches that I had distributed and remove some of the buggy stuff, then the Pthreads should be closer to working, and when they do work, they'll work super-well. It wasn't so much the "next greatest improvement" but making the code work correctly on SMP (the problems weren't with JB's stuff, but with the structure that it was trying to work in.) So, given the goals of "good SMP" and "threads", and working within the existant kernel framework, it was a significant effort. Out of my patches, it would be a really good idea to grab the following: 1) prv_CMAP4,prv_CPAGE4, and the better prezero code. (Prezeros should be done on a private per-cpu mapping.) (vm_machdep, mp_machdep, pmap.) 2) The pmap (and tlb shootdown) improvements. (mp_machdep, apic_*, pmap.) 3) CPU affinity. (swtch.s) 4) Passing the vm_page_t into pmap instead of pa. (By doing so, it short circuits some really nasty code in pmap.) (vm_page, vm_object, vm_map, pmap, ...) 5) The improvements in vm_object and vm_map handling. (vm_map, vm_object.) 6) TLB update improvements for multi-threaded processes. (swtch.s) New things that MUST be done for reliable SMP on X86 (PPro's especially), and things NOT in my patches: 1) The TLB shootdown MUST be made synchronous!!! (I had experimental versions of that code.) Any non-synchronous TLB shootdowns on PPros is a non-starter. Some of the problems can be worked around by pre-setting the PG_A and PG_M bits, but that doesn't solve everything. Synchronous TLB shootdowns are a little bit tricky, due to the potential for deadlocks. However, the issues aren't impossible to solve, one just needs to be "aware." This starts pushing the code into being more correct regarding locking. 2) Correct the locking issues in vm_object -- it is horrendous (not just for fine-grained SMP.) Suggestions: 1) Make VM86 non-optional. 2) Make USER_LDT non-optional. I do have a tree of JB's work. I suspect that a significant percentage of SMP reliability problems are the TLB shootdown issue. I have known about these issues and more, and have only now had reason to explain what is going on -- since someone needs to pick-up some of these items. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 14:30:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00323 for freebsd-current-outgoing; Fri, 7 Aug 1998 14:30:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00251 for ; Fri, 7 Aug 1998 14:30:02 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id HAA10923; Sat, 8 Aug 1998 07:35:32 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808072135.HAA10923@cimlogic.com.au> Subject: Re: memory leaks in libc In-Reply-To: <199808071703.KAA29656@bubba.whistle.com> from Archie Cobbs at "Aug 7, 98 10:03:20 am" To: archie@whistle.com (Archie Cobbs) Date: Sat, 8 Aug 1998 07:35:32 +1000 (EST) Cc: jb@cimlogic.com.au, archie@whistle.com, freebsd-current@FreeBSD.ORG, bde@zeta.org.au, wollman@khavrinen.lcs.mit.edu, dg@root.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs wrote: > Well, setenv() and unsetenv() are not thread safe as they > currently exist. How does this look? FWIW, I think that any proposed changes to libc should be _required_ to be thread-safe from now on so that libc has a better chance of working with kernel threads. > +void > +__env_lock(void) > +{ > + THREAD_LOCK(); > +} > + > +/* > + * __env_unlock() > + * > + * Release mutex lock on the environment. Should be static. > + */ > +void > +__env_unlock(void) > +{ > + THREAD_UNLOCK(); > +} Why add these functions? Since kernel threads require the standard libc to be thread safe, don't expect that the calls will be optimized out. The idea is to make the non-threaded runtime impact just a test on the __is_threaded variable. Using the THREAD_LOCK() and THREAD_UNLOCK() macros directly will achieve this. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 14:53:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02893 for freebsd-current-outgoing; Fri, 7 Aug 1998 14:53:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02884 for ; Fri, 7 Aug 1998 14:53:41 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id HAA11063; Sat, 8 Aug 1998 07:59:06 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808072159.HAA11063@cimlogic.com.au> Subject: Kernel threads (Was Re: Pthreads woes revisited.) In-Reply-To: <199808071503.KAA14839@ns.tar.com> from "Richard Seaman, Jr." at "Aug 7, 98 10:03:43 am" To: lists@tar.com Date: Sat, 8 Aug 1998 07:59:06 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Seaman, Jr. wrote: > Is there a description of what needs to be done, though? Are your > patches available anywhere? If someone is really going to look at > this, I assume they don't want to duplicate work already started, > and I assume they don't want to go in some direction the core team > doesn't support? There are a number of existing syscalls which need to be redesigned to allow a POSIX thread API. AFAIK, these syscalls were (are?) used by NCI and were added by John for them. They aren't built into the FreeBSD libc so I doubt that anyone else uses them. I haven't asked for opinions about cleaning this up (until now 8-). I think there are two stages to this work. The first is to get the syscall API in and working in a uni-processor environment. The second stage is to work on the SMP side, but as you'll note from messages posted by John, there is a significant amount of work there for someone with John's ability and level of understanding of the VM. I guess it is possible to complete the first stage now, but I doubt that the second stage will happen within 6 months. I'd also say that trying to do the second stage now would destabilize 3.0 and this is something I don't want to see happen. I know that this is not what people want to hear. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 14:56:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03259 for freebsd-current-outgoing; Fri, 7 Aug 1998 14:56:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03197 for ; Fri, 7 Aug 1998 14:55:44 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA09380; Fri, 7 Aug 1998 14:55:24 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma009378; Fri Aug 7 14:55:13 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id OAA05409; Fri, 7 Aug 1998 14:55:13 -0700 (PDT) From: Archie Cobbs Message-Id: <199808072155.OAA05409@bubba.whistle.com> Subject: Re: memory leaks in libc In-Reply-To: from Garance A Drosihn at "Aug 7, 98 04:39:37 pm" To: drosih@rpi.edu (Garance A Drosihn) Date: Fri, 7 Aug 1998 14:55:12 -0700 (PDT) Cc: wollman@khavrinen.lcs.mit.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garance A Drosihn writes: > setenv("NAME","VAL1"); -> does a malloc to store NAME > keep = getenv("NAME"); -> returns a pointer to the middle > of that malloc'ed area > setenv("NAME","VAL2"); -> replaces the value of NAME as > is kept in the environment > if ( ! strcmp(keep, "VAL1") ) { do_stuff(); } Yes, I think we can boil it down to this. If you call this a perfectly valid program, then we should not fix the memory leak. If you call this a bug not worth accomodating, then we should fix the memory leak. NB: with today's libc, keep will be equal to "VAL2" on the last line! Isn't there a POSIX spec for getenv()/putenv()... what does it say? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 15:03:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04501 for freebsd-current-outgoing; Fri, 7 Aug 1998 15:03:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04483 for ; Fri, 7 Aug 1998 15:03:21 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id IAA11118; Sat, 8 Aug 1998 08:08:51 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808072208.IAA11118@cimlogic.com.au> Subject: SMP and kernel threads (Was: Re: Pthreads woes revisited.) In-Reply-To: from Jason Evans at "Aug 7, 98 08:47:23 am" To: jasone@canonware.com (Jason Evans) Date: Sat, 8 Aug 1998 08:08:51 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Evans wrote: > Can you summarize what needs done, how much effort you expect it is, and > give a pointer or two on where to look in the source? If it's within my > technical abilities, I'm willing to help make kernel threads work sooner > rather than later. I suggest that you look at the message John Dyson posted and try applying his patches to your local SMP system. If you can debug this and are willing to write regression testing code to prove that it works, then we can talk more. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 15:08:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05274 for freebsd-current-outgoing; Fri, 7 Aug 1998 15:08:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05235 for ; Fri, 7 Aug 1998 15:08:26 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id SAA22144; Fri, 7 Aug 1998 18:08:20 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <199808071951.MAA04454@bubba.whistle.com> References: <3224.902516512@critter.freebsd.dk> from Poul-Henning Kamp at "Aug 7, 98 09:01:52 pm" Date: Fri, 7 Aug 1998 18:12:18 -0400 To: Archie Cobbs From: Garance A Drosihn Subject: Re: memory leaks in libc Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:51 PM -0700 8/7/98, Archie Cobbs wrote: >Poul-Henning Kamp writes: >> >I just don't understand where you're coming from. There is a clear >> >bug in the standard library, we agree on this right? You are saying >> >that it's not worth fixing, because... >> >> I think there is agreement that a bogus API was defined long time ago, >> and since getting rid of that API not worth even discussing, this >> entire thread is a waste of time. > > ? Who's talking about changing the API? I think you're misunderstanding > the issue. The issue is simply: there's a memory leak in libc, should we > or should we not fix it? It's a standard bug-fix cost/benefit question. The memory leak is not due to a bug in libc, it's due to a bug in the definition of the API. The only way to reliably fix this problem is to create different, well-defined routines which provide a similar benefit. In this case, the API should have included important information on what programs could expect from the pointer returned from "getenv" (such as, whether they can just save that pointer and expect it to remain valid for the life of the program, even if some later call to setenv will change the value pointed at by **environ). It should have also hidden away **environ, so programs can't directly manipulate that global variable without setenv/getenv/putenv knowing about it. --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 15:23:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07469 for freebsd-current-outgoing; Fri, 7 Aug 1998 15:23:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07442 for ; Fri, 7 Aug 1998 15:23:42 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA11268; Fri, 7 Aug 1998 15:15:17 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdj11263; Fri Aug 7 22:15:10 1998 Date: Fri, 7 Aug 1998 15:15:07 -0700 (PDT) From: Julian Elischer To: Luoqi Chen cc: kkennawa@physics.adelaide.edu.au, current@FreeBSD.ORG Subject: Re: Softupdates panic In-Reply-To: <199808071609.MAA22564@lor.watermarkgroup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998, Luoqi Chen wrote: > > Well, here's the problem simplified: > > > > cd /tmp (assuming mounted soft-updates) > > mkdir d1 > > mkdir d1/d2 > > mkdir d2 > > mv d2 d1 > > rmdir d1/d2 > > rmdir d1 > > [system will panic in 15 seconds at 'sync' of that data.] > > > > fix to follow. (and checked in I guess) > > > > julian > > > I looked at the problem and figured out what went wrong. During the rename > step (mv d2 d1), the target directory d1/d2 is deleted and a dirrem > dependency is generated. Normally, a dirrem dependency would decrease > the parent's link count by 1 and subdirectory's link count by 2. But for > this particular dirrem, we don't want to decrement the parent's link count, > otherwise we would the panic above. The solution would be mark this dirrem > as such, and don't decrement the parent's link count when it's handled. > Attached is a fix. > Kirk pointed out that this is correct for some cases but not all. The correct fix it this fix, but conditional upon whether the new_parent flag is set in the rename system call. there are two cases... the move is happenning all within one directory the move is happenning across different directories.. they must be handled differently. And he is working on that part, but he will use your fix as part of it.. He says you're on the right track... thanks.. julian > -lq > > Index: ffs_softdep.c > =================================================================== > RCS file: /fun/cvs/src/contrib/sys/softupdates/ffs_softdep.c,v > retrieving revision 1.12 > diff -u -r1.12 ffs_softdep.c > --- ffs_softdep.c 1998/06/12 21:21:26 1.12 > +++ ffs_softdep.c 1998/08/07 15:37:57 > @@ -2436,6 +2436,7 @@ > * Allocate a new dirrem and ACQUIRE_LOCK. > */ > dirrem = newdirrem(bp, dp, ip, isrmdir); > + dirrem->dm_state |= DIRCHG; > pagedep = dirrem->dm_pagedep; > > /* > @@ -2546,6 +2547,15 @@ > ip->i_flag |= IN_CHANGE; > if ((error = UFS_TRUNCATE(vp, (off_t)0, 0, p->p_ucred, p)) != 0) > softdep_error("handle_workitem_remove: truncate", error); > + /* > + * Target directory deletion during a directory rename. The > + * parent directory's link count doesn't need to be decremented. > + */ > + if (dirrem->dm_state & DIRCHG) { > + vput(vp); > + WORKITEM_FREE(dirrem, D_DIRREM); > + return; > + } > ACQUIRE_LOCK(&lk); > (void) inodedep_lookup(ip->i_fs, dirrem->dm_oldinum, DEPALLOC, > &inodedep); > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 15:29:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08527 for freebsd-current-outgoing; Fri, 7 Aug 1998 15:29:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from canonware.com (canonware.com [206.184.206.112]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA08516 for ; Fri, 7 Aug 1998 15:29:31 -0700 (PDT) (envelope-from jasone@canonware.com) Received: (qmail 9194 invoked by uid 1001); 7 Aug 1998 22:25:52 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Aug 1998 22:25:52 -0000 Date: Fri, 7 Aug 1998 15:25:52 -0700 (PDT) From: Jason Evans To: John Birrell cc: current@FreeBSD.ORG Subject: Re: SMP and kernel threads (Was: Re: Pthreads woes revisited.) In-Reply-To: <199808072208.IAA11118@cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 8 Aug 1998, John Birrell wrote: > > I suggest that you look at the message John Dyson posted and try applying > his patches to your local SMP system. If you can debug this and are willing > to write regression testing code to prove that it works, then we can > talk more. Okay, ummm... Your message begs some additional questions and a comment. 1) Which message from John Dyson are you referring to? I don't recall a technically detailed message from him on this subject for 2+ months. 2) Where are John Dyson's patches currently available? 3) I thought that John Dyson's patches had been committed long ago. Were they not committed because of stability problems, performance problems, lack of a warm body to do it, etc.? You request that I "write regression testing code to prove that it works". Regression testing does nothing more than prevent old bugs from reappearing. It proves nothing other than that old bugs haven't reappeared, and that assumes that the regression tests are written correctly to test for the bugs rather than their symptoms. Don't get me wrong; I'm a proponent of regression testing, but it won't achieve what you're asking for. Are you just asking for stability testing of the patches, or something else in addition? Thanks, Jason Jason Evans Email: [jasone@canonware.com] Web: [http://www.canonware.com/~jasone] Home phone: [(650) 856-8204] Work phone: [(408) 774-8007] Quote: ["Invention is 1% inspiration and 99% perspiration" - Thomas Edison] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 15:52:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12603 for freebsd-current-outgoing; Fri, 7 Aug 1998 15:52:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12598 for ; Fri, 7 Aug 1998 15:52:39 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id IAA11353; Sat, 8 Aug 1998 08:57:59 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808072257.IAA11353@cimlogic.com.au> Subject: Re: SMP and kernel threads (Was: Re: Pthreads woes revisited.) In-Reply-To: from Jason Evans at "Aug 7, 98 03:25:52 pm" To: jasone@canonware.com (Jason Evans) Date: Sat, 8 Aug 1998 08:57:58 +1000 (EST) Cc: jb@cimlogic.com.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Evans wrote: > 1) Which message from John Dyson are you referring to? I don't recall a > technically detailed message from him on this subject for 2+ months. The message I am referring to was dated Fri, 7 Aug 1998 16:12:13 -0500 (EST) and sent as part of the original thread. I can forward you a copy if necessary. > 2) Where are John Dyson's patches currently available? Send email to John. > 3) I thought that John Dyson's patches had been committed long ago. Were > they not committed because of stability problems, performance problems, > lack of a warm body to do it, etc.? AFAIK, they were his work in progress. He wasn't ready to commit them because he hadn't completed what he wanted to achieve. > You request that I "write regression testing code to prove that it works". > Regression testing does nothing more than prevent old bugs from > reappearing. It proves nothing other than that old bugs haven't > reappeared, and that assumes that the regression tests are written > correctly to test for the bugs rather than their symptoms. > > Don't get me wrong; I'm a proponent of regression testing, but it won't > achieve what you're asking for. Are you just asking for stability testing > of the patches, or something else in addition? OK maybe "regression" is the wrong word. I'm asking for code that proves the threads work - code that can be used to ensure that the functionality hasn't been broken and code that can have additional tests added when people report bugs. This sort of code is needed so that regression tests can be performed when the bugs are fixed. One of the problems I have with FreeBSD is that developer testing is performed privately and test code if it exists at all is not contributed. In this case, I want to be able to look at the test code too. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 15:57:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13630 for freebsd-current-outgoing; Fri, 7 Aug 1998 15:57:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vortex.starix.net (vortex.starix.net [208.219.83.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13564; Fri, 7 Aug 1998 15:57:07 -0700 (PDT) (envelope-from syko@sykotik.org) Received: from localhost (syko@localhost) by vortex.starix.net (8.7.6/8.7.3) with SMTP id SAA16288; Fri, 7 Aug 1998 18:54:35 -0400 X-Authentication-Warning: vortex.starix.net: syko owned process doing -bs Date: Fri, 7 Aug 1998 18:54:35 -0400 (EDT) From: Dusk Auriel Sykotik X-Sender: syko@vortex.starix.net To: Doug White cc: Shawn Leas , freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: I unsubed, but I'm still getting msgs! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why is this crossposting between current and questions? /* * Matt Harris +++ Syko * BPSOFH, BIOFH, C, SQL, PERL +++ http://starix.technonet.net/~syko/ * FreeBSD SysAdmin +++ apocalypse.sykotik.org */ On Fri, 7 Aug 1998, Doug White wrote: > > On Thu, 6 Aug 1998, Shawn Leas wrote: > > > > > Will someone take me off? I have already unsubbed, and authed, AND gotten > > confirmation, but CONTINUE to get messages. > > You followed these instructions exactly? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > It sounds like you *subscribed* yourself if you had to authorize it. > > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 16:02:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15017 for freebsd-current-outgoing; Fri, 7 Aug 1998 16:02:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14626; Fri, 7 Aug 1998 16:01:33 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id BAA15558; Sat, 8 Aug 1998 01:01:00 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id BAA02087; Sat, 8 Aug 1998 01:01:23 +0200 (CEST) X-Face: " Date: Sat, 8 Aug 1998 01:01:22 +0200 From: Stefan Esser To: "Steven G. Kargl" , freebsd-current@FreeBSD.ORG Cc: Stefan Esser Subject: Re: vm panic Mail-Followup-To: "Steven G. Kargl" , freebsd-current@FreeBSD.ORG References: <199808072009.NAA00348@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808072009.NAA00348@troutmask.apl.washington.edu>; from Steven G. Kargl on Fri, Aug 07, 1998 at 01:09:59PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-08-07 13:09 -0700, "Steven G. Kargl" wrote: > Build a new kernel, and reboot gives (transcribed by hand) > > Fatal trap 12: page fault while in kernel mode Something changed in the kernel and requires user-land tools to be recompiled. I did not bother to find out what changed, but just built a new world, and the problem is gone ;-) Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 16:32:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19710 for freebsd-current-outgoing; Fri, 7 Aug 1998 16:32:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dll.abs.net (cc698686-a.whmh1.md.home.com [24.3.58.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19689; Fri, 7 Aug 1998 16:31:55 -0700 (PDT) (envelope-from hdl@abs.net) Received: from hdl (hdl@hdl.abs.net [207.114.24.1]) by dll.abs.net (8.9.0/8.8.5) with SMTP id TAA01389; Fri, 7 Aug 1998 19:31:38 -0400 (EDT) Message-Id: <199808072331.TAA01389@dll.abs.net> X-Sender: hdl@pop.abs.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.37 (Beta) Date: Fri, 07 Aug 1998 19:31:36 -0400 To: freebsd-current@FreeBSD.ORG From: Howard Leadmon Subject: select() -vs- poll() in 3.0-CURRENT??? Cc: freebsd-questions@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I have started working with FreeBSD 3.0-CURRENT to run an Undernet IRC Server. As this monolithic program allows thousands of clients to connect to it, I had to allow thousands of FD's to be open, which has been done and works fine. The big question is that the 3.0 release now supports poll() as well as select() to service the FD's. The Undernet IRCD allows me to use either method by selecting it at compile time. So any of you hardcore C programmers out their know what is better for this environment? The the configure program uses poll() by default if it finds it available, but I suspect that is from SysV, so wondered if this is still the correct action for FBSD. For now I am running with poll() enabled, but thought I would see what others feelings were on this.. --- Howard Leadmon - hdl@abs.net - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 16:33:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20002 for freebsd-current-outgoing; Fri, 7 Aug 1998 16:33:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19986 for ; Fri, 7 Aug 1998 16:33:13 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id QAA05872; Fri, 7 Aug 1998 16:32:42 -0700 (PDT) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA020262761; Fri, 7 Aug 1998 16:32:41 -0700 Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_14041)/8.7.3 TIS 5.0) id QAA24857; Fri, 7 Aug 1998 16:32:40 -0700 (PDT) Message-Id: <199808072332.QAA24857@mina.sr.hp.com> To: "Andrew Reilly" Cc: freebsd-current@FreeBSD.ORG Subject: Re: GC, was Re: Heads up on LFS Reply-To: darrylo@sr.hp.com In-Reply-To: Your message of "Fri, 07 Aug 1998 18:42:56 +1000." Mime-Version: 1.0 (generated by tm-edit 1.1.1.1) Content-Type: text/plain; charset=US-ASCII Date: Fri, 07 Aug 1998 16:32:40 -0700 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrew Reilly" wrote: > I have copies of a GC-faq by an author too modest even to put an > e-mail address into it, and an excellent survey article "Dynamic > Storage Allocation: A Survey and Critical Review" by Paul Wilson, > Mark Johnstone, Michael Neely and David Boles, somewhere on the > Web, but I regret that I've lost the original URLs. If anyone can > supply these I would be very grateful. Search engines are your friend. ;-) A general memory management reference is: http://www.harlequin.com/mm/reference/bib/misc.html which points to: http://www.harlequin.com/mm/reference/bib/full.html#wil95 which is: ------------------------------------------------------------------------------- Dynamic Storage Allocation: A Survey and Critical Review"; Paul R. Wilson, Mark S. Johnstone, Michael Neely, David Boles; University of Texas at Austin; 1995-07; . Dynamic memory allocation has been a fundamental part of most computer systems since roughly 1960, and memory allocation is widely considered to be either a solved problem or an insoluble one. In this survey, we describe a variety of memory allocator designs and point out issues relevant to their design and evaluation. We then chronologically survey most of the literature on allocators between 1961 and 1995. (Scores of papers are discussed, in varying detail, and over 150 references are given.) We argue that allocator designs have been unduly restricted by an emphasis on mechanism, rather than policy, while the latter is more important; higher-level strategic issues are still more important, but have not been given much attention. Most theoretical analyses and empirical allocator evaluations to date have relied on very strong assumptions of randomness and independence, but real program behavior exhibits important regularities that must be exploited if allocators are to perform well in practice. ------------------------------------------------------------------------------- The ftp URL is still valid. -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 17:08:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25215 for freebsd-current-outgoing; Fri, 7 Aug 1998 17:08:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net (oldnews.quick.net [207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25155 for ; Fri, 7 Aug 1998 17:08:04 -0700 (PDT) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id RAA16718; Fri, 7 Aug 1998 17:07:46 -0700 (PDT) Date: Fri, 7 Aug 1998 17:07:46 -0700 (PDT) From: "Steven P. Donegan" To: freebsd-current@FreeBSD.ORG Subject: Hauppage WinTV Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just tried the new kernel with my card - before it incorrectly identified the card as a PAL tuner. Now it reports the card as NONE tuner :-) To add insult to injury the car works just fine in Linux and Win95/NT boxes. I'd really like to be able to use this in my FreeBSD toy :-) Thanks for any assist... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 17:15:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26296 for freebsd-current-outgoing; Fri, 7 Aug 1998 17:15:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ixion.honeywell.com (ixion.honeywell.com [129.30.4.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26288; Fri, 7 Aug 1998 17:15:52 -0700 (PDT) (envelope-from sleas@ixion.honeywell.com) Received: from localhost by ixion.honeywell.com with SMTP (1.40.112.8/16.2) id AA041825301; Fri, 7 Aug 1998 19:15:01 -0500 Date: Fri, 7 Aug 1998 19:15:01 -0500 (CDT) From: Shawn Leas To: Doug White Cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: I unsubed, but I'm still getting msgs! In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998, Doug White wrote: > > On Thu, 6 Aug 1998, Shawn Leas wrote: > > > > > Will someone take me off? I have already unsubbed, and authed, AND gotten > > confirmation, but CONTINUE to get messages. > > You followed these instructions exactly? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > It sounds like you *subscribed* yourself if you had to authorize it. Well, after a day they finally seemed to stop. I resent the same message twice, then got replys saying I wasn't subbed and that the unsub failed. Don't know why it kept going soooooo long. -Shawn <=========== America Held Hostage ===========> Day 2025 for the poor and the middle class. Day 2044 for the rich and the dead. 897 days remaining in the Raw Deal. <============================================> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 18:08:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04490 for freebsd-current-outgoing; Fri, 7 Aug 1998 18:08:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vortex.starix.net (vortex.starix.net [208.219.83.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04288 for ; Fri, 7 Aug 1998 18:08:08 -0700 (PDT) (envelope-from syko@sykotik.org) Received: from localhost (syko@localhost) by vortex.starix.net (8.7.6/8.7.3) with SMTP id VAA16871; Fri, 7 Aug 1998 21:05:45 -0400 X-Authentication-Warning: vortex.starix.net: syko owned process doing -bs Date: Fri, 7 Aug 1998 21:05:45 -0400 (EDT) From: Dusk Auriel Sykotik X-Sender: syko@vortex.starix.net To: "Steven P. Donegan" cc: freebsd-current@FreeBSD.ORG Subject: Re: Hauppage WinTV In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't think FreeBSD support automobiles yet. If your referring to some kind of ethernet card or something please be more specific as to model numbers and such. When I first installed FreeBSD on one of my machine (with a terribly old ethernet card) it didn't detect it and I had to get my friend to gimme a new card to use instead. /* * Matt Harris +++ Syko * BPSOFH, BIOFH, C, SQL, PERL +++ http://starix.technonet.net/~syko/ * FreeBSD SysAdmin +++ apocalypse.sykotik.org * IRC TechnoNet +++ irc.technonet.net * IRC Cabalnet +++ dark-temple.cabalnet.org */ On Fri, 7 Aug 1998, Steven P. Donegan wrote: > Just tried the new kernel with my card - before it incorrectly identified > the card as a PAL tuner. Now it reports the card as NONE tuner :-) > > To add insult to injury the car works just fine in Linux and Win95/NT > boxes. I'd really like to be able to use this in my FreeBSD toy :-) > > Thanks for any assist... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 18:59:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10718 for freebsd-current-outgoing; Fri, 7 Aug 1998 18:59:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10713 for ; Fri, 7 Aug 1998 18:59:36 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id SAA29339; Fri, 7 Aug 1998 18:59:21 -0700 (PDT) Message-ID: <19980807185921.D18733@Alameda.net> Date: Fri, 7 Aug 1998 18:59:21 -0700 From: Ulf Zimmermann To: "Steven P. Donegan" , freebsd-current@FreeBSD.ORG Subject: Re: Hauppage WinTV Reply-To: ulf@Alameda.net References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Steven P. Donegan on Fri, Aug 07, 1998 at 05:07:46PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 07, 1998 at 05:07:46PM -0700, Steven P. Donegan wrote: > Just tried the new kernel with my card - before it incorrectly identified > the card as a PAL tuner. Now it reports the card as NONE tuner :-) > > To add insult to injury the car works just fine in Linux and Win95/NT > boxes. I'd really like to be able to use this in my FreeBSD toy :-) > > Thanks for any assist... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message I applied the patch from Roger Hardiman, which got me my tuner back. In a snap version from april it seemed to work, then I went to a snap from 7-19 and no tuner was detected. Applied the patch and it works fine again now. Has even better quality then the Hauppauge WinShit software. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 19:04:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11479 for freebsd-current-outgoing; Fri, 7 Aug 1998 19:04:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net (oldnews.quick.net [207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11392 for ; Fri, 7 Aug 1998 19:03:56 -0700 (PDT) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id TAA16929; Fri, 7 Aug 1998 19:02:24 -0700 (PDT) Date: Fri, 7 Aug 1998 19:02:24 -0700 (PDT) From: "Steven P. Donegan" To: Dusk Auriel Sykotik cc: freebsd-current@FreeBSD.ORG Subject: Re: Hauppage WinTV In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998, Dusk Auriel Sykotik wrote: Jeez, I mispell one word and you reply with this? > I don't think FreeBSD support automobiles yet. If your referring to some > kind of ethernet card or something please be more specific as to model > numbers and such. When I first installed FreeBSD on one of my machine > (with a terribly old ethernet card) it didn't detect it and I had to get > my friend to gimme a new card to use instead. > > /* > * Matt Harris +++ Syko > * BPSOFH, BIOFH, C, SQL, PERL +++ http://starix.technonet.net/~syko/ > * FreeBSD SysAdmin +++ apocalypse.sykotik.org > * IRC TechnoNet +++ irc.technonet.net > * IRC Cabalnet +++ dark-temple.cabalnet.org > */ > > > On Fri, 7 Aug 1998, Steven P. Donegan wrote: > > > Just tried the new kernel with my card - before it incorrectly identified > > the card as a PAL tuner. Now it reports the card as NONE tuner :-) > > > > To add insult to injury the car works just fine in Linux and Win95/NT --------------------------------^ card for crying out loud :-) > > boxes. I'd really like to be able to use this in my FreeBSD toy :-) > > > > Thanks for any assist... > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Any substantive assist would be appreciated :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 19:05:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11745 for freebsd-current-outgoing; Fri, 7 Aug 1998 19:05:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net (oldnews.quick.net [207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11716 for ; Fri, 7 Aug 1998 19:05:38 -0700 (PDT) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id TAA16939; Fri, 7 Aug 1998 19:05:18 -0700 (PDT) Date: Fri, 7 Aug 1998 19:05:18 -0700 (PDT) From: "Steven P. Donegan" To: Ulf Zimmermann cc: freebsd-current@FreeBSD.ORG Subject: Re: Hauppage WinTV In-Reply-To: <19980807185921.D18733@Alameda.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998, Ulf Zimmermann wrote: > On Fri, Aug 07, 1998 at 05:07:46PM -0700, Steven P. Donegan wrote: > > Just tried the new kernel with my card - before it incorrectly identified > > the card as a PAL tuner. Now it reports the card as NONE tuner :-) > > > > To add insult to injury the car works just fine in Linux and Win95/NT > > boxes. I'd really like to be able to use this in my FreeBSD toy :-) > > > > Thanks for any assist... > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > I applied the patch from Roger Hardiman, which got me my tuner back. > In a snap version from april it seemed to work, then I went to a snap > from 7-19 and no tuner was detected. Applied the patch and it works > fine again now. Has even better quality then the Hauppauge WinShit > software. > > > -- > Regards, Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > Where might I find this patch? I'd really like to get this working both for fun and to video conference. The audio/video setup is the Huappage card, a video camera, the tuner runs to my rooftop antenna, sound blaster etc. The video capture part used to work but at present even that doesn't work. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 19:09:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12525 for freebsd-current-outgoing; Fri, 7 Aug 1998 19:09:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12506 for ; Fri, 7 Aug 1998 19:09:23 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id TAA22235; Fri, 7 Aug 1998 19:08:41 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp04.primenet.com, id smtpd022177; Fri Aug 7 19:08:35 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id TAA20796; Fri, 7 Aug 1998 19:08:23 -0700 (MST) From: Terry Lambert Message-Id: <199808080208.TAA20796@usr01.primenet.com> Subject: Re: memory leaks in libc To: jb@cimlogic.com.au (John Birrell) Date: Sat, 8 Aug 1998 02:08:23 +0000 (GMT) Cc: archie@whistle.com, jb@cimlogic.com.au, freebsd-current@FreeBSD.ORG, bde@zeta.org.au, wollman@khavrinen.lcs.mit.edu, dg@root.com In-Reply-To: <199808072135.HAA10923@cimlogic.com.au> from "John Birrell" at Aug 8, 98 07:35:32 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > FWIW, I think that any proposed changes to libc should be _required_ to > be thread-safe from now on so that libc has a better chance of working > with kernel threads. I have sent copies of excerpts of the CAE and SUS specifications to the most interested (vocal) parties. Here are the salient points, and then can we let this die like Poul suggested? According to the standards: 1) People are permitted to muck about in environ. 2) putenv( "foo=fee"); followed by putenv("foo=xyz") is REQUIRED to free the allocations; in other words, not leak. 3) getenv() is permitted to use a local static buffer. Thus depending on getting a pointer to the real variable is not a valid thing to do. 4) Conforming POSIX threading programs are required to implement synchronization between threads accessing getenv/putenv and/or using environ to much things around. 5) Neither getenv() or putenv() are required to be reentrant. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 19:19:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14250 for freebsd-current-outgoing; Fri, 7 Aug 1998 19:19:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14238 for ; Fri, 7 Aug 1998 19:19:53 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id TAA00341; Fri, 7 Aug 1998 19:19:33 -0700 (PDT) Message-ID: <19980807191933.E18733@Alameda.net> Date: Fri, 7 Aug 1998 19:19:33 -0700 From: Ulf Zimmermann To: "Steven P. Donegan" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Hauppage WinTV Reply-To: ulf@Alameda.net References: <19980807185921.D18733@Alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Steven P. Donegan on Fri, Aug 07, 1998 at 07:05:18PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Search for: > Subject: Patch for Bt848 driver to detect new Hauppauge 404 Cards on -curent. On Fri, Aug 07, 1998 at 07:05:18PM -0700, Steven P. Donegan wrote: > On Fri, 7 Aug 1998, Ulf Zimmermann wrote: > > > On Fri, Aug 07, 1998 at 05:07:46PM -0700, Steven P. Donegan wrote: > > > Just tried the new kernel with my card - before it incorrectly identified > > > the card as a PAL tuner. Now it reports the card as NONE tuner :-) > > > > > > To add insult to injury the car works just fine in Linux and Win95/NT > > > boxes. I'd really like to be able to use this in my FreeBSD toy :-) > > > > > > Thanks for any assist... > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > I applied the patch from Roger Hardiman, which got me my tuner back. > > In a snap version from april it seemed to work, then I went to a snap > > from 7-19 and no tuner was detected. Applied the patch and it works > > fine again now. Has even better quality then the Hauppauge WinShit > > software. > > > > > > -- > > Regards, Ulf. > > > > --------------------------------------------------------------------- > > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > > Where might I find this patch? I'd really like to get this working both > for fun and to video conference. > > The audio/video setup is the Huappage card, a video camera, the tuner > runs to my rooftop antenna, sound blaster etc. The video capture part > used to work but at present even that doesn't work. > > Thanks! > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 20:03:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19762 for freebsd-current-outgoing; Fri, 7 Aug 1998 20:03:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19751 for ; Fri, 7 Aug 1998 20:03:10 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id VAA04348; Fri, 7 Aug 1998 21:58:06 -0400 (EDT) Date: Fri, 7 Aug 1998 21:58:06 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Dusk Auriel Sykotik cc: "Steven P. Donegan" , freebsd-current@FreeBSD.ORG Subject: Re: Hauppage WinTV In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998, Dusk Auriel Sykotik wrote: > I don't think FreeBSD support automobiles yet. If your referring to some > kind of ethernet card or something please be more specific as to model > numbers and such. When I first installed FreeBSD on one of my machine > (with a terribly old ethernet card) it didn't detect it and I had to get > my friend to gimme a new card to use instead. I don't understand Dusk's comments at all, since you clearly said you were talking about the Hauppage WinTV card (read the subject line, Dusk, I haven't modified the original one) ... maybe, since you should have posted to FreeBSD-multimedia (instead of current) he didn't understand it. Dusk maybe should lighten up on the sarcasm, and Steven should ask again on the right list. > > /* > * Matt Harris +++ Syko > * BPSOFH, BIOFH, C, SQL, PERL +++ http://starix.technonet.net/~syko/ > * FreeBSD SysAdmin +++ apocalypse.sykotik.org > * IRC TechnoNet +++ irc.technonet.net > * IRC Cabalnet +++ dark-temple.cabalnet.org > */ > > > On Fri, 7 Aug 1998, Steven P. Donegan wrote: > > > Just tried the new kernel with my card - before it incorrectly identified > > the card as a PAL tuner. Now it reports the card as NONE tuner :-) > > > > To add insult to injury the car works just fine in Linux and Win95/NT > > boxes. I'd really like to be able to use this in my FreeBSD toy :-) > > > > Thanks for any assist... > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 20:07:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20260 for freebsd-current-outgoing; Fri, 7 Aug 1998 20:07:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net (oldnews.quick.net [207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20249 for ; Fri, 7 Aug 1998 20:07:09 -0700 (PDT) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id UAA17061; Fri, 7 Aug 1998 20:06:49 -0700 (PDT) Date: Fri, 7 Aug 1998 20:06:49 -0700 (PDT) From: "Steven P. Donegan" To: Chuck Robey cc: Dusk Auriel Sykotik , freebsd-current@FreeBSD.ORG Subject: Re: Hauppage WinTV In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998, Chuck Robey wrote: > > I don't understand Dusk's comments at all, since you clearly said you > were talking about the Hauppage WinTV card (read the subject line, > Dusk, I haven't modified the original one) ... maybe, since you should > have posted to FreeBSD-multimedia (instead of current) he didn't > understand it. Dusk maybe should lighten up on the sarcasm, and Steven > should ask again on the right list. > No problem - he was just joking, and my reply was supposed to note that :-) Didn't even know there was a list specific to multimedia - I just subscribe to -current and -smp (the box in question runs both). Supposedly there is a patch out there (discussed recently in -current) that fixes this problem but I have no pointers to it yet. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 7 22:50:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04010 for freebsd-current-outgoing; Fri, 7 Aug 1998 22:50:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04005 for ; Fri, 7 Aug 1998 22:50:28 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id BAA165048; Sat, 8 Aug 1998 01:50:21 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <199808072155.OAA05409@bubba.whistle.com> References: from Garance A Drosihn at "Aug 7, 98 04:39:37 pm" Date: Sat, 8 Aug 1998 01:54:19 -0400 To: Archie Cobbs From: Garance A Drosihn Subject: Re: memory leaks in libc Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:55 PM -0700 8/7/98, Archie Cobbs wrote: >Garance A Drosihn writes: >> setenv("NAME","VAL1"); -> does a malloc to store NAME >> keep = getenv("NAME"); -> returns a pointer to the middle >> of that malloc'ed area >> setenv("NAME","VAL2"); -> replaces the value of NAME as >> is kept in the environment >> if ( ! strcmp(keep, "VAL1") ) { do_stuff(); } > > Yes, I think we can boil it down to this. If you call this a > perfectly valid program, then we should not fix the memory leak. > > If you call this a bug not worth accomodating, then we should > fix the memory leak. No. I'm saying that it's not worth stirring up potential trouble for every program which calls setenv(), in order to solve a memory leak problem which is not significant for 99.9% of those programs. Changing setenv() will only help programs which: 1) use setenv for manipulating the environment (as opposed to using putenv, or just going in and mucking with **environ by themselves). 2) make a *lot* of calls to setenv, such that the memory leak will amount to more space than the memory overhead you are going to add to setenv by tracking malloc's. 3) is making a lot of setenv calls to set the *same* variable, to different values of different length, because if each call is setting a different variable then there is no space you can free. > Isn't there a POSIX spec for getenv()/putenv()... what does > it say? Not in any of the references I have (which isn't saying much, I only have a few...). Most of the unix references that I have don't even list *any* of these routines in their index. (reminder: I only have a few...) Basically, I can't help but thing that if you add up all the memory on all the programs running on my machine right now, it's going to amount to maybe 4 kilobytes. I'd rather stay with that known leak-factor, then rewrite the API's for setenv and see what unknown side-effects that will have. But if someone really thinks this causes a serious memory leak, a leak that uses up significantly more memory than your improved implementation will use up in tracking these malloc'ed pointers, that's fine with me to. I'm just saying that if it were me, there's a long list of other projects that I'd worry about first. --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 00:25:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12771 for freebsd-current-outgoing; Sat, 8 Aug 1998 00:25:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12766 for ; Sat, 8 Aug 1998 00:25:06 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id DAA85998; Sat, 8 Aug 1998 03:24:59 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: References: <199808072155.OAA05409@bubba.whistle.com> from Garance A Drosihn at "Aug 7, 98 04:39:37 pm" Date: Sat, 8 Aug 1998 03:28:57 -0400 To: Archie Cobbs From: Garance A Drosihn Subject: Re: memory leaks in libc Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:54 AM -0400 8/8/98, Garance A Drosihn wrote: > Basically, I can't help but thing that if you add up all the > memory on all the programs running on my machine right now, > it's going to amount to maybe 4 kilobytes. Well, after getting off the floor laughing at this statement, let me rephrase it: If you add up all the memory *leaked* by this setenv bug --------------------------- on all the programs running on my machine right now, it's going to amount to maybe 4 kilobytes. I'm reasonably happy with how efficent freebsd is, but I'm not really running in 4 kilobytes of memory... --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 00:43:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14631 for freebsd-current-outgoing; Sat, 8 Aug 1998 00:43:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14623 for ; Sat, 8 Aug 1998 00:43:28 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id KAA17559; Sat, 8 Aug 1998 10:43:00 +0300 (EEST) Date: Sat, 8 Aug 1998 10:42:59 +0300 (EEST) From: Narvi To: Garance A Drosihn cc: Archie Cobbs , Garrett Wollman , freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998, Garance A Drosihn wrote: > At 10:12 AM -0700 8/7/98, Archie Cobbs wrote: > >Garrett Wollman writes: > >> Now having gone to that effort, you can just add it to your program > >> that needs it, and we don't have to bear the kluge in the C library. > > > > I just don't understand where you're coming from. There is a clear > > bug in the standard library, we agree on this right? You are saying > > that it's not worth fixing, because... > > I don't know where Garrett is coming from, but I must admit I would > be leary of making changes to getenv/setenv. The main reason is > that the environment mechanism was poorly thought out and defined > to begin with, and thus any changes you make are likely to break > something somewhere. By "poorly defined", I mean that there are > not good, consistent definitions of what one can and can not expect > from a call to getenv/putenv, and thus you can be sure that some > code uses those routines in ways you won't forsee. > > Consider that getenv returns a pointer to the environment variable. > It does not malloc any space, it just returns a pointer to the > actual value it finds in the current environment. Now consider > the following sequence: > setenv("NAME","VAL1"); -> does a malloc to store NAME > keep = getenv("NAME"); -> returns a pointer to the middle > of that malloc'ed area > setenv("NAME","VAL2"); -> replaces the value of NAME as > is kept in the environment > if ( ! strcmp(keep, "VAL1") ) { do_stuff(); } > > -> Here is the problem. In the above sequence, you > -> "know" that setenv malloc'ed the space, and thus > -> you would expect that the second setenv should > -> free it. However, the program has stored away > -> a pointer into that area which it got from getenv, > -> and it has every right to believe (due to years of > -> precedent) that that pointer will remain valid. > -> if you free and reuse that space, you may introduce > -> some pretty obscure bugs. > Actually, *if* strlen(VAL2) > strlen(VAL1) even the current code uses realloc, which might relocate the array. And the proposed replacement to the current code would not change this. Neither would it break this case you brought up, if reallocation does not take place. > And *that* is in the "well-understood" case, were we know that > the only things playing with the environment have been setenv > and getenv. However, there are plenty of programs which > manipulate the environment via other means, and would make > life even more complicated. > Every program that references potencially freed storage is broken. > If the question is: > Can you design a safe *alternative* to setenv/getenv which > would not have this memory-leak side-effect? The answer is yes. See above. > the answer is definitely yes. However, for the specific routines > of getenv/setenv/putenv, the horses left the barn a long time ago. > There's no sense trying to lock the door now. I think that the > risks of *replacing* getenv/setenv/putenv with a "smarter" version > are far greater than the benefits of fixing this memory leak. > At the worst, we could have a variable like in the case of phkmalloc... The right way, of course, is fixing the real bogus programs. > If you wanted to define some "getenv2/setenv2", which worked on a > vector called **environ2 (and *not* the standard, "well-known" > environment vector), then there's all kinds of good things you > can do. However, in my opinion replacing getenv/setenv is much There's another good idea. > too risky to be worth it. If you find some stupid program which > really does have a serious memory leak due to setenv calls, then > fix that one program. The memory leak would be easy enough to > find and to fix in a program, as opposed to introducing very > non-obvious bugs to a hole slew of programs which are currently > working just fine as they are (even if they do occasionally "leak" > 64 bytes of memory somewhere, nothing is the worse for that). > > So, I think Garrett's position is sensible and corrrect, even if > his presentation could be somewhat more pleasent or informative. > > --- > Garance Alistair Drosehn = gad@eclipse.its.rpi.edu > Senior Systems Programmer or drosih@rpi.edu > Rensselaer Polytechnic Institute > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 01:33:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA18069 for freebsd-current-outgoing; Sat, 8 Aug 1998 01:33:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from omnix.net (omnix.net [194.183.217.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18062 for ; Sat, 8 Aug 1998 01:33:39 -0700 (PDT) (envelope-from didier@omnix.net) Received: from localhost (didier@localhost) by omnix.net (8.8.7/8.8.7) with SMTP id IAA09998; Sat, 8 Aug 1998 08:33:12 GMT (envelope-from didier@omnix.net) Date: Sat, 8 Aug 1998 10:33:12 +0200 (CEST) From: Didier Derny To: "Steven P. Donegan" cc: freebsd-current@FreeBSD.ORG Subject: Re: Hauppage WinTV In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998, Steven P. Donegan wrote: > > Just tried the new kernel with my card - before it incorrectly identified > the card as a PAL tuner. Now it reports the card as NONE tuner :-) > > To add insult to injury the car works just fine in Linux and Win95/NT > boxes. I'd really like to be able to use this in my FreeBSD toy :-) > > Thanks for any assist... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > check in /usr/src/sys/pci/brooktree848.c there is a possibility to override the card/tuner It seems to be working with my card (I have probably a secam problem) but the pal version probably work. my card was recogniszed but not the tuner -- Didier Derny didier@omnix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 04:34:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06269 for freebsd-current-outgoing; Sat, 8 Aug 1998 04:34:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06262 for ; Sat, 8 Aug 1998 04:34:33 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA17235; Sat, 8 Aug 1998 21:34:14 +1000 Date: Sat, 8 Aug 1998 21:34:14 +1000 From: Bruce Evans Message-Id: <199808081134.VAA17235@godzilla.zeta.org.au> To: bde@zeta.org.au, lile@stdio.com Subject: Re: Kernel compile problem Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Speaking of this, what is the new magic with *intr routines. I am still The magic went away :-). >working on my token ring driver and have cvsup'd to the latest level only >to find out that my driver now panics when calling routines outside my >tokintr like tok_tx_intr. That would happen if you leave the interrupt specification out of the config file (so that ioconf.c compiles) without making any other changes. This gives a NULL interrupt handler. Unfortunately, config_isadev_c() registers interrupt handlers if (isdp->id_irq != 0) without looking at isdp->id_intr. >Is it now neccesary to make these static? or >inline? And is there some better fix for declaring your *intr routine >or must you specify it in isa_device.h? isa_device.h should not be changed for new drivers. Just initialize the isa_device struct member for the interrupt handler explicitly. Here is a suitable (slightly kludgy) initialization for sio: --- diff -c2 sio.c~ sio.c *** sio.c~ Wed Jul 15 22:18:14 1998 --- sio.c Sat Aug 8 20:36:47 1998 *************** *** 891,894 **** --- 891,895 ---- int unit; + isdp->id_intr = siointr; isdp->id_ri_flags |= RI_FAST; iobase = isdp->id_iobase; --- The compiler will warn about a type mismatch here. Avoiding this takes more code and isn't worth doing yet. The interrupt handler shuld take a `void *' arg. The declarations in isa_device.h prevent this for old drivers (until the declarations go away), but there is no problem for new drivers. However, if the driver takes a `void *' arg, then it isn't possible to correctly specify that arg in isdp->id_unit where config_isadev_c() expects it to be, so there is no correct way for drivers to depend on existing interrupt initialization (the current way is incorrect but the kludges are localised). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 07:59:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20916 for freebsd-current-outgoing; Sat, 8 Aug 1998 07:59:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tbsdbox.dyn.ml.org (pm3will3-28.csrlink.net [209.173.92.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20911 for ; Sat, 8 Aug 1998 07:58:58 -0700 (PDT) (envelope-from root@tbsdbox.dyn.ml.org) Received: (from root@localhost) by admin.techyman.net (8.8.8/8.8.8) id UAA05303 for current@freebsd.org; Wed, 5 Aug 1998 20:50:52 -0400 (EDT) (envelope-from root) Date: Wed, 5 Aug 1998 20:50:52 -0400 (EDT) From: Charlie Root Message-Id: <199808060050.UAA05303@admin.techyman.net> To: current@FreeBSD.ORG Subject: A CRAZY idea Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just an idea that would make Linus Torvalds quit making linux kernels: take the Linux kernel, Add it to the FreeBSD Kernel (i dont know what im talking about), so all Linux binaries run, then convert every single lib :P I know it sounds like A WHOLE LOT OF FUN! But, if i knew C (reccomend me to a good web page, i got tons of paper to print:P) I'd start such a humongus project like that :P P.S. Before i kill myself and do make world, in FreeBSD-19980801-SNAP, do i have to do anything and/or watch for something? my reply address is grumpyoldman0@yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 09:26:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28289 for freebsd-current-outgoing; Sat, 8 Aug 1998 09:26:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from red.juniper.net (red.juniper.net [208.197.169.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA28184 for ; Sat, 8 Aug 1998 09:26:00 -0700 (PDT) (envelope-from pst@juniper.net) Received: from pst (red.juniper.net [208.197.169.254]) by red.juniper.net (8.8.5/8.8.5) with SMTP id JAA13838 for ; Sat, 8 Aug 1998 09:25:39 -0700 (PDT) Reply-To: "Paul Traina" From: "Paul Traina" To: Subject: Fw: JunOS Whitepaper Date: Sat, 8 Aug 1998 09:25:47 -0700 Message-ID: <000001bdc2e9$33457380$28d176cc@pst.shockwave.com> 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 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD makes a pretty good platform for doing the non-realtime portions of a complex system. ObPlug: Juniper has funded and continues to fund development projects for FreeBSD (e.g. the kernel debugger, sysinstall, PAM integration, ...). We're happy to be a part of the FreeBSD family. ObAdd: By the way, I'm looking to hire a software tools person and a UNIX apps jack-of-all-trades person. Both must be insanely strong software developers who play nice with BSD (understand the Zen) but prefer to see their favorite bits of BSD rewritten to be efficient, maintainable, and robust. Paul Louis A. Mamakos wrote in message <199807041412.KAA22805@whizzo.transsys.com>... > > Yeah, it's pretty cool stuff. We've been testing it since late last year, > and it works pretty good. > > > Juniper Networks has a cool whitepaper on their FreeBSD derived > > technology. > > > > http://www.juniper.net/leadingedge/whitepapers/optimizing-routing-sw.fm.html > > Of course the cool stuff is the quality of the routing protocol > implementation they have. Nothing else like it on the planet. Not > just warmed-over gated. > > louie > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 09:30:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29112 for freebsd-current-outgoing; Sat, 8 Aug 1998 09:30:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net (oldnews.quick.net [207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29107 for ; Sat, 8 Aug 1998 09:30:19 -0700 (PDT) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id JAA21293; Sat, 8 Aug 1998 09:30:01 -0700 (PDT) Date: Sat, 8 Aug 1998 09:30:01 -0700 (PDT) From: "Steven P. Donegan" To: freebsd-current@FreeBSD.ORG Subject: Multimedia/WINTV Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The patches to the brooktree driver allowed my WinTV card to be recognised. Yea!!! Now, I need to know where to find the correct application software to allow me to do video and TV under X. After I pass that hurdle I'll be looking for 'standards compliant' video conferencing software. Any pointers would be welcome. BTW this is a 'current' topic - the system in question is an SMP/current (today's kernel) system. TIA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 10:41:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05102 for freebsd-current-outgoing; Sat, 8 Aug 1998 10:41:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05096 for ; Sat, 8 Aug 1998 10:41:03 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id KAA10642; Sat, 8 Aug 1998 10:40:40 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808081740.KAA10642@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Steven P. Donegan" cc: freebsd-current@FreeBSD.ORG Subject: Re: Multimedia/WINTV In-reply-to: Your message of "Sat, 08 Aug 1998 09:30:01 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 Aug 1998 10:40:40 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Traditionally, the multimedia components are separate from this mailing list in fact the multimedia mailing list started on my system rah. Development and support for FreeBSD multimedia components, drivers, applications, etc, has been carried out on the -multimedia mailing list . Usually, the multimedia folks post on this list for issues which the kernel affects the multimedia components . Amancio > The patches to the brooktree driver allowed my WinTV card to be > recognised. Yea!!! Now, I need to know where to find the correct > application software to allow me to do video and TV under X. After I pass > that hurdle I'll be looking for 'standards compliant' video conferencing > software. Any pointers would be welcome. BTW this is a 'current' topic - > the system in question is an SMP/current (today's kernel) system. > > TIA > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 11:42:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11033 for freebsd-current-outgoing; Sat, 8 Aug 1998 11:42:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vortex.starix.net (vortex.starix.net [208.219.83.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11021 for ; Sat, 8 Aug 1998 11:42:26 -0700 (PDT) (envelope-from syko@sykotik.org) Received: from localhost (syko@localhost) by vortex.starix.net (8.7.6/8.7.3) with SMTP id OAA21061; Sat, 8 Aug 1998 14:39:48 -0400 X-Authentication-Warning: vortex.starix.net: syko owned process doing -bs Date: Sat, 8 Aug 1998 14:39:48 -0400 (EDT) From: Dusk Auriel Sykotik X-Sender: syko@vortex.starix.net To: Charlie Root cc: current@FreeBSD.ORG Subject: Re: A CRAZY idea In-Reply-To: <199808060050.UAA05303@admin.techyman.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG lol. A quick question... Why would we need linux binaries to run? Just get the source and compile it yourself on FreeBSD. Anything that won't compile... well, thats why so many people learn to code :) As for a good place to learn C, I suggest you just read other people's source and start figuring out how things work. I'm probly going to put up an archive of all my code (cept a few things I choose not to distribute) and I'll point you to it once I have it setup. If you still have questions go buy a nice little reference book. I personally do no kernel coding, I honestly don't think I could deal with many of the things involved in it, and I have about one year of C coding experience. Experience is of course key, and the more ya got the better ya are. /* ** Matt Harris Syko ** BPSOFH, BIOFH, C, SQL, PERL http://www.sykotik.org/~syko/ ** FreeBSD SysAdmin sykotik.org ** IRC TechnoNet - dark.technonet.net Cabalnet - dark-temple.cabalnet.org */ On Wed, 5 Aug 1998, Charlie Root wrote: > Just an idea that would make Linus Torvalds quit making linux kernels: > take the Linux kernel, Add it to the FreeBSD Kernel (i dont know what im talking about), so all Linux binaries run, then convert every single lib :P > I know it sounds like A WHOLE LOT OF FUN! But, if i knew C (reccomend me to a good web page, i got tons of paper to print:P) I'd start such a humongus project like that :P > > P.S. Before i kill myself and do make world, in FreeBSD-19980801-SNAP, do i have to do anything and/or watch for something? my reply address is grumpyoldman0@yahoo.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 12:09:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14146 for freebsd-current-outgoing; Sat, 8 Aug 1998 12:09:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flamingo.McKusick.COM (flamingo.mckusick.com [209.31.233.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14128 for ; Sat, 8 Aug 1998 12:09:21 -0700 (PDT) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (mckusick@localhost [127.0.0.1]) by flamingo.McKusick.COM (8.8.5/8.8.5) with ESMTP id LAA06087; Sat, 8 Aug 1998 11:52:34 -0700 (PDT) Message-Id: <199808081852.LAA06087@flamingo.McKusick.COM> To: Julian Elischer Subject: Softupdates panic (fwd) cc: Luoqi Chen , kkennawa@physics.adelaide.edu.au, dg@root.com, current@FreeBSD.ORG Date: Sat, 08 Aug 1998 11:52:23 -0700 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem occured when renaming a directory to a new parent, but not when renaming a directory within the same parent (write a one line C program that does ``rename("d1", "d2");''). Luoqi Chen's fix (forwarded message below) for the broken case, breaks the same directory rename case. Thus, the soft update code needs to be aware of which case it is handling. I now pass this information through and do the right thing for both cases. Affected files are /sys/ufs/ufs/ufs_vnops.c and /sys/ufs/ffs/ffs_softdep.c. Note there is a related one line fix if ffs_softdep.c which sometimes caused the rename to fail with an EINVAL error (compounding the difficulty of trying to track down this bug). The diffs follow. Kirk McKusick Index: ffs_softdep.c =================================================================== RCS file: /master/sys/ufs/ffs/ffs_softdep.c,v retrieving revision 2.21 diff -c -r2.21 ffs_softdep.c *** ffs_softdep.c 1998/06/12 17:54:33 2.21 --- ffs_softdep.c 1998/08/08 18:32:36 *************** *** 52,58 **** * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * ! * @(#)ffs_softdep.c 9.27 (McKusick) 6/12/98 */ /* --- 52,58 ---- * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * ! * @(#)ffs_softdep.c 9.28 (McKusick) 8/8/98 */ /* *************** *** 2205,2210 **** --- 2205,2211 ---- } else { dirrem = dap->da_previous; pagedep = dirrem->dm_pagedep; + dirrem->dm_dirinum = pagedep->pd_ino; add_to_worklist(&dirrem->dm_list); } if (inodedep_lookup(VFSTOUFS(pagedep->pd_mnt)->um_fs, dap->da_newinum, *************** *** 2384,2389 **** --- 2385,2404 ---- */ dirrem = newdirrem(bp, dp, ip, isrmdir); pagedep = dirrem->dm_pagedep; + /* + * The possible values for isrmdir: + * 0 - non-directory file rename + * 1 - directory rename within same directory + * inum - directory rename to new directory of given inode number + * When renaming to a new directory, we are both deleting and + * creating a new directory entry, so the link count on the new + * directory should not change. Thus we do not need the followup + * dirrem which is usually done in handle_workitem_remove. We set + * the DIRCHG flag to tell handle_workitem_remove to skip the + * followup dirrem. + */ + if (isrmdir > 1) + dirrem->dm_state |= DIRCHG; /* * Whiteouts have no additional dependencies, *************** *** 2493,2498 **** --- 2508,2523 ---- ip->i_flag |= IN_CHANGE; if ((error = VOP_TRUNCATE(vp, (off_t)0, 0, p->p_ucred, p)) != 0) softdep_error("handle_workitem_remove: truncate", error); + /* + * Rename a directory to a new parent. Since, we are both deleting + * and creating a new directory entry, the link count on the new + * directory should not change. Thus we skip the followup dirrem. + */ + if (dirrem->dm_state & DIRCHG) { + vput(vp); + WORKITEM_FREE(dirrem, D_DIRREM); + return; + } ACQUIRE_LOCK(&lk); (void) inodedep_lookup(ip->i_fs, dirrem->dm_oldinum, DEPALLOC, &inodedep); Index: ufs_vnops.c =================================================================== RCS file: /master/sys/ufs/ufs/ufs_vnops.c,v retrieving revision 2.29 diff -c -r2.29 ufs_vnops.c *** ufs_vnops.c 1998/06/08 18:52:11 2.29 --- ufs_vnops.c 1998/08/08 18:20:28 *************** *** 930,936 **** } ip->i_flag |= IN_RENAME; oldparent = dp->i_number; ! doingdirectory++; } /* --- 930,936 ---- } ip->i_flag |= IN_RENAME; oldparent = dp->i_number; ! doingdirectory = 1; } /* *************** *** 1073,1079 **** goto bad; } if ((error = ufs_dirrewrite(dp, xp, ip->i_number, ! IFTODT(ip->i_mode), doingdirectory)) != 0) goto bad; if (doingdirectory) { if (!newparent) { --- 1073,1080 ---- goto bad; } if ((error = ufs_dirrewrite(dp, xp, ip->i_number, ! IFTODT(ip->i_mode), ! newparent ? newparent : doingdirectory)) != 0) goto bad; if (doingdirectory) { if (!newparent) { ---------- Forwarded message ---------- Date: Fri, 7 Aug 1998 12:09:03 -0400 (EDT) From: Luoqi Chen To: julian@whistle.com, kkennawa@physics.adelaide.edu.au Cc: current@FreeBSD.ORG Subject: Re: Softupdates panic > Well, here's the problem simplified: > > cd /tmp (assuming mounted soft-updates) > mkdir d1 > mkdir d1/d2 > mkdir d2 > mv d2 d1 > rmdir d1/d2 > rmdir d1 > [system will panic in 15 seconds at 'sync' of that data.] > > fix to follow. (and checked in I guess) > > julian > I looked at the problem and figured out what went wrong. During the rename step (mv d2 d1), the target directory d1/d2 is deleted and a dirrem dependency is generated. Normally, a dirrem dependency would decrease the parent's link count by 1 and subdirectory's link count by 2. But for this particular dirrem, we don't want to decrement the parent's link count, otherwise we would the panic above. The solution would be mark this dirrem as such, and don't decrement the parent's link count when it's handled. Attached is a fix. -lq Index: ffs_softdep.c =================================================================== RCS file: /fun/cvs/src/contrib/sys/softupdates/ffs_softdep.c,v retrieving revision 1.12 diff -u -r1.12 ffs_softdep.c --- ffs_softdep.c 1998/06/12 21:21:26 1.12 +++ ffs_softdep.c 1998/08/07 15:37:57 @@ -2436,6 +2436,7 @@ * Allocate a new dirrem and ACQUIRE_LOCK. */ dirrem = newdirrem(bp, dp, ip, isrmdir); + dirrem->dm_state |= DIRCHG; pagedep = dirrem->dm_pagedep; /* @@ -2546,6 +2547,15 @@ ip->i_flag |= IN_CHANGE; if ((error = UFS_TRUNCATE(vp, (off_t)0, 0, p->p_ucred, p)) != 0) softdep_error("handle_workitem_remove: truncate", error); + /* + * Target directory deletion during a directory rename. The + * parent directory's link count doesn't need to be decremented. + */ + if (dirrem->dm_state & DIRCHG) { + vput(vp); + WORKITEM_FREE(dirrem, D_DIRREM); + return; + } ACQUIRE_LOCK(&lk); (void) inodedep_lookup(ip->i_fs, dirrem->dm_oldinum, DEPALLOC, &inodedep); -------- End Forwarded message -------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 12:20:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15753 for freebsd-current-outgoing; Sat, 8 Aug 1998 12:20:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15680 for ; Sat, 8 Aug 1998 12:20:24 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.8.8/8.8.8) id OAA26364; Sat, 8 Aug 1998 14:19:58 -0500 (CDT) (envelope-from dan) Message-ID: <19980808141958.A26340@emsphone.com> Date: Sat, 8 Aug 1998 14:19:58 -0500 From: Dan Nelson To: Charlie Root , current@FreeBSD.ORG Subject: Re: A CRAZY idea References: <199808060050.UAA05303@admin.techyman.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.2i In-Reply-To: <199808060050.UAA05303@admin.techyman.net>; from "Charlie Root" on Wed Aug 5 20:50:52 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Aug 05), Charlie Root said: > Just an idea that would make Linus Torvalds quit making linux > kernels: take the Linux kernel, Add it to the FreeBSD Kernel (i dont > know what im talking about), so all Linux binaries run, then convert > every single lib :P I know it sounds like A WHOLE LOT OF FUN! But, if > i knew C (reccomend me to a good web page, i got tons of paper to > print:P) I'd start such a humongus project like that :P cd /usr/ports/emulators/linux_lib/ ; make all install vi /etc/rc.conf, set linux_enable="YES" # Linux emulation loaded at startup (or NO). shutdown -r now There, I've saved you all that work. :) -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 14:10:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25233 for freebsd-current-outgoing; Sat, 8 Aug 1998 14:10:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from homer.supersex.com (homer.supersex.com [209.5.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25219 for ; Sat, 8 Aug 1998 14:10:10 -0700 (PDT) (envelope-from leo@homer.supersex.com) Received: (from leo@localhost) by homer.supersex.com (8.8.8/8.8.5) id RAA12866; Sat, 8 Aug 1998 17:11:03 -0400 (EDT) Message-ID: <19980808171103.09374@supersex.com> Date: Sat, 8 Aug 1998 17:11:03 -0400 From: Leo Papandreou To: current@FreeBSD.ORG Subject: Re: A CRAZY idea References: <199808060050.UAA05303@admin.techyman.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199808060050.UAA05303@admin.techyman.net>; from Charlie Root on Wed, Aug 05, 1998 at 08:50:52PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 05, 1998 at 08:50:52PM -0400, Charlie Root wrote: > Just an idea that would make Linus Torvalds quit making linux kernels: > take the Linux kernel, Add it to the FreeBSD Kernel (i dont know what > im talking about), so all Linux binaries run, then convert every single > lib :P Cool. GPL tweaks distributed under BSD. The immediate consequences are Stallman blowing whatever remains of his MacArthur Grant on (a) cheap booze, country music and lots of hankies, or (b) AK-47s. That would certainly fly if it werent for the fact that BSD doesn't need an X widget war. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 14:14:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25877 for freebsd-current-outgoing; Sat, 8 Aug 1998 14:14:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25871 for ; Sat, 8 Aug 1998 14:14:45 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id OAA04436 for ; Sat, 8 Aug 1998 14:12:47 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: current@FreeBSD.ORG Subject: Bootstrapping problem with -current now. Date: Sat, 08 Aug 1998 14:12:46 -0700 Message-ID: <4432.902610766@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [during a ``make world''] ===> gnu/usr.bin/binutils/addr2line install -c -s -o bin -g bin -m 555 addr2line /usr/libexec/elf install -c -o bin -g bin -m 444 addr2line.1.gz /usr/share/man/man1 ===> gnu/usr.bin/binutils/ar install -c -s -o bin -g bin -m 555 ar /usr/libexec/elf install: /usr/libexec/elf/ar: Bad address *** Error code 71 Stop. Given the success of the previous target, this one is rather inexplicable, but I can reproduce it on demand from a clean /usr/obj too. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 14:41:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28234 for freebsd-current-outgoing; Sat, 8 Aug 1998 14:41:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28229 for ; Sat, 8 Aug 1998 14:41:45 -0700 (PDT) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with SMTP id RAA17732; Sat, 8 Aug 1998 17:40:46 -0400 (EDT) Date: Sat, 8 Aug 1998 17:40:45 -0400 (EDT) From: Brian Feldman To: Dan Nelson cc: Charlie Root , current@FreeBSD.ORG Subject: Re: A CRAZY idea In-Reply-To: <19980808141958.A26340@emsphone.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No offense, but instead of shutdown -r now, a bit of a better idea is to try modload /lkm/linux_mod.o *grin. Cheers, Brian green@unixhelp.org On Sat, 8 Aug 1998, Dan Nelson wrote: > In the last episode (Aug 05), Charlie Root said: > > Just an idea that would make Linus Torvalds quit making linux > > kernels: take the Linux kernel, Add it to the FreeBSD Kernel (i dont > > know what im talking about), so all Linux binaries run, then convert > > every single lib :P I know it sounds like A WHOLE LOT OF FUN! But, if > > i knew C (reccomend me to a good web page, i got tons of paper to > > print:P) I'd start such a humongus project like that :P > > > cd /usr/ports/emulators/linux_lib/ ; make all install > vi /etc/rc.conf, set > > linux_enable="YES" # Linux emulation loaded at startup (or NO). > > shutdown -r now > > There, I've saved you all that work. :) > > -Dan Nelson > dnelson@emsphone.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 15:02:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29654 for freebsd-current-outgoing; Sat, 8 Aug 1998 15:02:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29649 for ; Sat, 8 Aug 1998 15:02:08 -0700 (PDT) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with SMTP id SAA17895; Sat, 8 Aug 1998 18:01:00 -0400 (EDT) Date: Sat, 8 Aug 1998 18:01:00 -0400 (EDT) From: Brian Feldman To: Kirk McKusick cc: Julian Elischer , Luoqi Chen , kkennawa@physics.adelaide.edu.au, dg@root.com, current@FreeBSD.ORG Subject: Re: Softupdates panic (fwd) In-Reply-To: <199808081852.LAA06087@flamingo.McKusick.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the current ufs_vnops.c I have, the correct line 1146 is: IFTODT(ip->i_mode), newparent ? newparent : doingdirectory); My version is $Id: ufs_vnops.c,v 1.97 1998/07/27 15:37:00 bde Exp $, I guess we've got a non-committed version on our hands. Cheers, Brian Feldman green@unixhelp.org On Sat, 8 Aug 1998, Kirk McKusick wrote: > The problem occured when renaming a directory to a new parent, but > not when renaming a directory within the same parent (write a one > line C program that does ``rename("d1", "d2");''). Luoqi Chen's > fix (forwarded message below) for the broken case, breaks the same > directory rename case. Thus, the soft update code needs to be aware of > which case it is handling. I now pass this information through and do the > right thing for both cases. Affected files are /sys/ufs/ufs/ufs_vnops.c > and /sys/ufs/ffs/ffs_softdep.c. Note there is a related one line fix > if ffs_softdep.c which sometimes caused the rename to fail with an > EINVAL error (compounding the difficulty of trying to track down this > bug). The diffs follow. > > Kirk McKusick > > Index: ffs_softdep.c > =================================================================== > RCS file: /master/sys/ufs/ffs/ffs_softdep.c,v > retrieving revision 2.21 > diff -c -r2.21 ffs_softdep.c > *** ffs_softdep.c 1998/06/12 17:54:33 2.21 > --- ffs_softdep.c 1998/08/08 18:32:36 > *************** > *** 52,58 **** > * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF > * SUCH DAMAGE. > * > ! * @(#)ffs_softdep.c 9.27 (McKusick) 6/12/98 > */ > > /* > --- 52,58 ---- > * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF > * SUCH DAMAGE. > * > ! * @(#)ffs_softdep.c 9.28 (McKusick) 8/8/98 > */ > > /* > *************** > *** 2205,2210 **** > --- 2205,2211 ---- > } else { > dirrem = dap->da_previous; > pagedep = dirrem->dm_pagedep; > + dirrem->dm_dirinum = pagedep->pd_ino; > add_to_worklist(&dirrem->dm_list); > } > if (inodedep_lookup(VFSTOUFS(pagedep->pd_mnt)->um_fs, dap->da_newinum, > *************** > *** 2384,2389 **** > --- 2385,2404 ---- > */ > dirrem = newdirrem(bp, dp, ip, isrmdir); > pagedep = dirrem->dm_pagedep; > + /* > + * The possible values for isrmdir: > + * 0 - non-directory file rename > + * 1 - directory rename within same directory > + * inum - directory rename to new directory of given inode number > + * When renaming to a new directory, we are both deleting and > + * creating a new directory entry, so the link count on the new > + * directory should not change. Thus we do not need the followup > + * dirrem which is usually done in handle_workitem_remove. We set > + * the DIRCHG flag to tell handle_workitem_remove to skip the > + * followup dirrem. > + */ > + if (isrmdir > 1) > + dirrem->dm_state |= DIRCHG; > > /* > * Whiteouts have no additional dependencies, > *************** > *** 2493,2498 **** > --- 2508,2523 ---- > ip->i_flag |= IN_CHANGE; > if ((error = VOP_TRUNCATE(vp, (off_t)0, 0, p->p_ucred, p)) != 0) > softdep_error("handle_workitem_remove: truncate", error); > + /* > + * Rename a directory to a new parent. Since, we are both deleting > + * and creating a new directory entry, the link count on the new > + * directory should not change. Thus we skip the followup dirrem. > + */ > + if (dirrem->dm_state & DIRCHG) { > + vput(vp); > + WORKITEM_FREE(dirrem, D_DIRREM); > + return; > + } > ACQUIRE_LOCK(&lk); > (void) inodedep_lookup(ip->i_fs, dirrem->dm_oldinum, DEPALLOC, > &inodedep); > Index: ufs_vnops.c > =================================================================== > RCS file: /master/sys/ufs/ufs/ufs_vnops.c,v > retrieving revision 2.29 > diff -c -r2.29 ufs_vnops.c > *** ufs_vnops.c 1998/06/08 18:52:11 2.29 > --- ufs_vnops.c 1998/08/08 18:20:28 > *************** > *** 930,936 **** > } > ip->i_flag |= IN_RENAME; > oldparent = dp->i_number; > ! doingdirectory++; > } > > /* > --- 930,936 ---- > } > ip->i_flag |= IN_RENAME; > oldparent = dp->i_number; > ! doingdirectory = 1; > } > > /* > *************** > *** 1073,1079 **** > goto bad; > } > if ((error = ufs_dirrewrite(dp, xp, ip->i_number, > ! IFTODT(ip->i_mode), doingdirectory)) != 0) > goto bad; > if (doingdirectory) { > if (!newparent) { > --- 1073,1080 ---- > goto bad; > } > if ((error = ufs_dirrewrite(dp, xp, ip->i_number, > ! IFTODT(ip->i_mode), > ! newparent ? newparent : doingdirectory)) != 0) > goto bad; > if (doingdirectory) { > if (!newparent) { > > ---------- Forwarded message ---------- > Date: Fri, 7 Aug 1998 12:09:03 -0400 (EDT) > From: Luoqi Chen > To: julian@whistle.com, kkennawa@physics.adelaide.edu.au > Cc: current@FreeBSD.ORG > Subject: Re: Softupdates panic > > > Well, here's the problem simplified: > > > > cd /tmp (assuming mounted soft-updates) > > mkdir d1 > > mkdir d1/d2 > > mkdir d2 > > mv d2 d1 > > rmdir d1/d2 > > rmdir d1 > > [system will panic in 15 seconds at 'sync' of that data.] > > > > fix to follow. (and checked in I guess) > > > > julian > > > I looked at the problem and figured out what went wrong. During the rename > step (mv d2 d1), the target directory d1/d2 is deleted and a dirrem > dependency is generated. Normally, a dirrem dependency would decrease > the parent's link count by 1 and subdirectory's link count by 2. But for > this particular dirrem, we don't want to decrement the parent's link count, > otherwise we would the panic above. The solution would be mark this dirrem > as such, and don't decrement the parent's link count when it's handled. > Attached is a fix. > > -lq > > Index: ffs_softdep.c > =================================================================== > RCS file: /fun/cvs/src/contrib/sys/softupdates/ffs_softdep.c,v > retrieving revision 1.12 > diff -u -r1.12 ffs_softdep.c > --- ffs_softdep.c 1998/06/12 21:21:26 1.12 > +++ ffs_softdep.c 1998/08/07 15:37:57 > @@ -2436,6 +2436,7 @@ > * Allocate a new dirrem and ACQUIRE_LOCK. > */ > dirrem = newdirrem(bp, dp, ip, isrmdir); > + dirrem->dm_state |= DIRCHG; > pagedep = dirrem->dm_pagedep; > > /* > @@ -2546,6 +2547,15 @@ > ip->i_flag |= IN_CHANGE; > if ((error = UFS_TRUNCATE(vp, (off_t)0, 0, p->p_ucred, p)) != 0) > softdep_error("handle_workitem_remove: truncate", error); > + /* > + * Target directory deletion during a directory rename. The > + * parent directory's link count doesn't need to be decremented. > + */ > + if (dirrem->dm_state & DIRCHG) { > + vput(vp); > + WORKITEM_FREE(dirrem, D_DIRREM); > + return; > + } > ACQUIRE_LOCK(&lk); > (void) inodedep_lookup(ip->i_fs, dirrem->dm_oldinum, DEPALLOC, > &inodedep); > -------- End Forwarded message -------- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 15:12:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00575 for freebsd-current-outgoing; Sat, 8 Aug 1998 15:12:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from yip.org (yip.org [142.154.6.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00570 for ; Sat, 8 Aug 1998 15:12:17 -0700 (PDT) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by yip.org (8.8.8/8.8.8) with SMTP id SAA11830; Sat, 8 Aug 1998 18:11:46 -0400 (EDT) (envelope-from melange@yip.org) Date: Sat, 8 Aug 1998 18:11:44 -0400 (EDT) From: Bob K To: Brian Feldman cc: Dan Nelson , Charlie Root , current@FreeBSD.ORG Subject: Re: A CRAZY idea In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Umm... Won't linux(8) do the same thing? On Sat, 8 Aug 1998, Brian Feldman wrote: > No offense, but instead of shutdown -r now, a bit of a better idea is to > try modload /lkm/linux_mod.o *grin. > > Cheers, > Brian > green@unixhelp.org > > On Sat, 8 Aug 1998, Dan Nelson wrote: > > > In the last episode (Aug 05), Charlie Root said: > > > Just an idea that would make Linus Torvalds quit making linux > > > kernels: take the Linux kernel, Add it to the FreeBSD Kernel (i dont > > > know what im talking about), so all Linux binaries run, then convert > > > every single lib :P I know it sounds like A WHOLE LOT OF FUN! But, if > > > i knew C (reccomend me to a good web page, i got tons of paper to > > > print:P) I'd start such a humongus project like that :P > > > > > > cd /usr/ports/emulators/linux_lib/ ; make all install > > vi /etc/rc.conf, set > > > > linux_enable="YES" # Linux emulation loaded at startup (or NO). > > > > shutdown -r now > > > > There, I've saved you all that work. :) > > > > -Dan Nelson > > dnelson@emsphone.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > melange@yip.org - "Slightly tacky but completely entertaining" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 15:35:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02552 for freebsd-current-outgoing; Sat, 8 Aug 1998 15:35:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02547 for ; Sat, 8 Aug 1998 15:35:29 -0700 (PDT) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with SMTP id SAA18096; Sat, 8 Aug 1998 18:34:22 -0400 (EDT) Date: Sat, 8 Aug 1998 18:34:22 -0400 (EDT) From: Brian Feldman To: Kirk McKusick cc: Julian Elischer , Luoqi Chen , kkennawa@physics.adelaide.edu.au, dg@root.com, current@FreeBSD.ORG Subject: Re2: Softupdates panic (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whoops, sorry, what I _meant_ was the diff was probably for a different OS, maybe OpenBSD, and that would be the correct line on FreeBSD. Cheers, Brian Feldman green@unixhelp.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 15:40:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03094 for freebsd-current-outgoing; Sat, 8 Aug 1998 15:40:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tbsdbox.dyn.ml.org (pm3will2-17.csrlink.net [209.173.92.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02996 for ; Sat, 8 Aug 1998 15:39:57 -0700 (PDT) (envelope-from root@tbsdbox.dyn.ml.org) Received: (from root@localhost) by tbsdbox.dyn.ml.org (8.9.1/8.8.8) id SAA00677 for current@freebsd.org; Sat, 8 Aug 1998 18:39:35 -0400 (EDT) (envelope-from root) Date: Sat, 8 Aug 1998 18:39:35 -0400 (EDT) From: Charlie Root Message-Id: <199808082239.SAA00677@tbsdbox.dyn.ml.org> To: current@FreeBSD.ORG Subject: hehe... just an extension om my lkast email Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was talking mainly SQuake and SVGALib :P I dont like XWin, and xquake dont work :P -TeChY To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 16:36:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08308 for freebsd-current-outgoing; Sat, 8 Aug 1998 16:36:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08303 for ; Sat, 8 Aug 1998 16:36:31 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id TAA04875; Sat, 8 Aug 1998 19:36:01 -0400 (EDT) Date: Sat, 8 Aug 1998 19:36:01 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Brian Feldman cc: Dan Nelson , Charlie Root , current@FreeBSD.ORG Subject: Re: A CRAZY idea In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 8 Aug 1998, Brian Feldman wrote: > No offense, but instead of shutdown -r now, a bit of a better idea is to > try modload /lkm/linux_mod.o *grin. How about just /usr/bin/linux? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 17:09:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12158 for freebsd-current-outgoing; Sat, 8 Aug 1998 17:09:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12153 for ; Sat, 8 Aug 1998 17:09:07 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id RAA04402; Sat, 8 Aug 1998 17:08:38 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808090008.RAA04402@rah.star-gate.com> To: Charlie Root cc: current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: hehe... just an extension om my lkast email In-reply-to: Your message of "Sat, 08 Aug 1998 18:39:35 EDT." <199808082239.SAA00677@tbsdbox.dyn.ml.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4399.902621318.1@rah.star-gate.com> Date: Sat, 08 Aug 1998 17:08:38 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG SQuake works on FreeBSD . Try posting to : multimedia@freebsd.org Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 18:33:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21805 for freebsd-current-outgoing; Sat, 8 Aug 1998 18:33:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21799 for ; Sat, 8 Aug 1998 18:33:31 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.8.8/8.8.8) id UAA02451; Sat, 8 Aug 1998 20:25:40 -0500 (CDT) (envelope-from dan) Message-ID: <19980808202540.A2378@emsphone.com> Date: Sat, 8 Aug 1998 20:25:40 -0500 From: Dan Nelson To: Brian Feldman , Bob K , ben@rosengart.com Cc: Charlie Root , current@FreeBSD.ORG Subject: Re: A CRAZY idea References: <19980808141958.A26340@emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.2i In-Reply-To: ; from "Brian Feldman" on Sat Aug 8 17:40:45 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Aug 08), Bob K said: > Umm... Won't linux(8) do the same thing? In the last episode (Aug 08), Snob Art Genre said: > On Sat, 8 Aug 1998, Brian Feldman wrote: > > No offense, but instead of shutdown -r now, a bit of a better idea > > is to try modload /lkm/linux_mod.o *grin. > > How about just /usr/bin/linux? Yes, that will enable Linux emulation, but only until Mr C. Root shuts down. And whenever you edit /etc/rc.conf, it's a good idea to shutdown and reboot, if only to verify that you didn't make a typo :) -Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 20:00:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00247 for freebsd-current-outgoing; Sat, 8 Aug 1998 20:00:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00209; Sat, 8 Aug 1998 20:00:43 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199808090300.UAA00209@hub.freebsd.org> Subject: Re: I unsubed, but I'm still getting msgs! In-Reply-To: from Shawn Leas at "Aug 7, 98 07:15:01 pm" To: sleas@ixion.honeywell.com (Shawn Leas) Date: Sat, 8 Aug 1998 20:00:42 -0700 (PDT) Cc: dwhite@resnet.uoregon.edu, freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Shawn Leas wrote: > Well, after a day they finally seemed to stop. I resent the same message > twice, then got replys saying I wasn't subbed and that the unsub failed. > > Don't know why it kept going soooooo long. because it takes mail soooooo long to reach you once it has been sent. when you unsubscribe, we dont recall mail that has been sent out. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 20:10:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02121 for freebsd-current-outgoing; Sat, 8 Aug 1998 20:10:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com ([208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02097 for ; Sat, 8 Aug 1998 20:10:17 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-97.camalott.com [208.229.74.97]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id WAA29296; Sat, 8 Aug 1998 22:11:19 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id NAA18156; Sat, 8 Aug 1998 13:08:33 -0500 (CDT) (envelope-from joelh) Date: Sat, 8 Aug 1998 13:08:33 -0500 (CDT) Message-Id: <199808081808.NAA18156@detlev.UUCP> To: wosch@panke.de.freebsd.org CC: freebsd-current@FreeBSD.ORG In-reply-to: <199808071854.UAA20965@campa.panke.de> (message from Wolfram Schneider on Fri, 7 Aug 1998 20:54:21 +0200 (MET DST)) Subject: Re: removing -batch option from adduser command From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808071854.UAA20965@campa.panke.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I want remove the adduser(8) option `-batch'. Adduser was written as > an *interactive* command for newbies. The pw(8) does now a much better > job for adding users from command line. Also, the -batch option is > not well tested, buggy and unsupported. While you're at it, kindly add pw(8) to the SEE ALSO section of the adduser(8) manpage. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 20:26:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03742 for freebsd-current-outgoing; Sat, 8 Aug 1998 20:26:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03733 for ; Sat, 8 Aug 1998 20:26:38 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id DAA07438; Sun, 9 Aug 1998 03:26:18 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id FAA08228; Sun, 9 Aug 1998 05:26:16 +0200 (MET DST) Message-ID: <19980809052615.37763@follo.net> Date: Sun, 9 Aug 1998 05:26:15 +0200 From: Eivind Eklund To: John Birrell , Jason Evans Cc: current@FreeBSD.ORG Subject: Re: SMP and kernel threads (Was: Re: Pthreads woes revisited.) References: <199808072257.IAA11353@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199808072257.IAA11353@cimlogic.com.au>; from John Birrell on Sat, Aug 08, 1998 at 08:57:58AM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Aug 08, 1998 at 08:57:58AM +1000, John Birrell wrote: > Jason Evans wrote: > > 1) Which message from John Dyson are you referring to? I don't recall a > > technically detailed message from him on this subject for 2+ months. > > The message I am referring to was dated Fri, 7 Aug 1998 16:12:13 -0500 (EST) > and sent as part of the original thread. I can forward you a copy > if necessary. > > > 2) Where are John Dyson's patches currently available? > > Send email to John. He'll probably refer to http://www.freebsd.org/~eivind/ where I stored a copy of his latest distributed patches, though :-) IIRC, the code there (sysjun-07b.diff.gz) should match what John (Dyson) is talking about. These are the patches John was testing just before he left. The other patches there (vput-proc.diff) is to make vput() take a process argument, and thus avoid some race conditions under SMP. These need testing with NFS; I'm waiting on somebody (you know who you are) who promised to do this a long while ago, but have not heard back (even after repeated nagging). If somebody else has a suitable test environment, feel free to yell. The patches have been running on my machine for three months or so with no ill effects. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 21:09:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07716 for freebsd-current-outgoing; Sat, 8 Aug 1998 21:09:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07707 for ; Sat, 8 Aug 1998 21:09:19 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id XAA00446 for current@freebsd.org; Sat, 8 Aug 1998 23:08:58 -0500 (EST) (envelope-from toor) Message-Id: <199808090408.XAA00446@dyson.iquest.net> Subject: Just FYI about FreeBSD and 16.8GB drives To: current@FreeBSD.ORG Date: Sat, 8 Aug 1998 23:08:52 -0500 (EST) From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just bought one, and it (16.8GB IBM) works fine on the current that I use (about 2-3mos old.) It gets about 9-12MBytes/sec real throughput through the filesystem. Also, it co-exists my WD drives, as a master, and the WD drive as a slave. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 8 22:25:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12422 for freebsd-current-outgoing; Sat, 8 Aug 1998 22:25:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA12399 for ; Sat, 8 Aug 1998 22:24:19 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id WAA05274; Sat, 8 Aug 1998 22:22:50 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808090522.WAA05274@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: jasone@canonware.com (Jason Evans), current@FreeBSD.ORG Subject: Re: SMP and kernel threads (Was: Re: Pthreads woes revisited.) In-reply-to: Your message of "Sat, 08 Aug 1998 08:57:58 +1000." <199808072257.IAA11353@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 Aug 1998 22:22:50 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Perhaps someone should gather all the necessary pieces and provide a kernel , or patches so that support for kernel threads can proceed forward as opposed to waiting two months to then start the 6 month estimated time to complete the task. For the benefit of those who missed John Dyson's recent posting here it is again: ---------------------------------------------------------------------------- dyson@iquest.net: I am working on Pthreads for work. However, I did get tied up trying to improve the SMP so that Pthreads work properly there. If someone distills the SMP patches that I had distributed and remove some of the buggy stuff, then the Pthreads should be closer to working, and when they do work, they'll work super-well. It wasn't so much the "next greatest improvement" but making the code work correctly on SMP (the problems weren't with JB's stuff, but with the structure that it was trying to work in.) So, given the goals of "good SMP" and "threads", and working within the existant kernel framework, it was a significant effort. Out of my patches, it would be a really good idea to grab the following: 1) prv_CMAP4,prv_CPAGE4, and the better prezero code. (Prezeros should be done on a private per-cpu mapping.) (vm_machdep, mp_machdep, pmap.) 2) The pmap (and tlb shootdown) improvements. (mp_machdep, apic_*, pmap.) 3) CPU affinity. (swtch.s) 4) Passing the vm_page_t into pmap instead of pa. (By doing so, it short circuits some really nasty code in pmap.) (vm_page, vm_object, vm_map, pmap, ...) 5) The improvements in vm_object and vm_map handling. (vm_map, vm_object.) 6) TLB update improvements for multi-threaded processes. (swtch.s) New things that MUST be done for reliable SMP on X86 (PPro's especially), and things NOT in my patches: 1) The TLB shootdown MUST be made synchronous!!! (I had experimental versions of that code.) Any non-synchronous TLB shootdowns on PPros is a non-starter. Some of the problems can be worked around by pre-setting the PG_A and PG_M bits, but that doesn't solve everything. Synchronous TLB shootdowns are a little bit tricky, due to the potential for deadlocks. However, the issues aren't impossible to solve, one just needs to be "aware." This starts pushing the code into being more correct regarding locking. 2) Correct the locking issues in vm_object -- it is horrendous (not just for fine-grained SMP.) Suggestions: 1) Make VM86 non-optional. 2) Make USER_LDT non-optional. I do have a tree of JB's work. I suspect that a significant percentage of SMP reliability problems are the TLB shootdown issue. I have known about these issues and more, and have only now had reason to explain what is going on -- since someone needs to pick-up some of these items. ---------------------------------------------------------------------------- Enjoy, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message