From owner-freebsd-current Sun Feb 17 0: 4:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 8CCDF37B416; Sun, 17 Feb 2002 00:04:50 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id TAA19581; Sun, 17 Feb 2002 19:01:25 +1100 Date: Sun, 17 Feb 2002 19:04:38 +1100 (EST) From: Bruce Evans X-X-Sender: To: Terry Lambert Cc: Paul van der Zwan , Riccardo Torrini , Brian Fundakowski Feldman , Subject: Re: USB detach crashes possibly fixed In-Reply-To: <3C6F037D.A490C091@mindspring.com> Message-ID: <20020217190322.J934-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 16 Feb 2002, Terry Lambert wrote: > PHK was threatening to murder /dev/speaker to work > around some clock issues that would be hard to nail > down the right way. I think you mean /dev/pcaudio. I use /dev/pcaudio to expose the brokenness of clock code that is not nailed down in the right way. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 0:53:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.com [194.25.134.81]) by hub.freebsd.org (Postfix) with ESMTP id BB56737B405 for ; Sun, 17 Feb 2002 00:53:54 -0800 (PST) Received: from fwd09.sul.t-online.de by mailout03.sul.t-online.com with smtp id 16cN4I-0004bq-07; Sun, 17 Feb 2002 09:53:10 +0100 Received: from pc-micha.mc.hp.com (320021761316-0001@[80.131.82.66]) by fmrl09.sul.t-online.com with esmtp id 16cN4E-0ZFYiOC; Sun, 17 Feb 2002 09:53:06 +0100 Received: from gmx.net (michaelc@localhost [127.0.0.1]) by pc-micha.mc.hp.com (8.11.6/8.11.0) with ESMTP id g1H8rQ900404; Sun, 17 Feb 2002 09:53:26 +0100 (MET) (envelope-from michael_class@gmx.net) Message-ID: <3C6F6F85.4050300@gmx.net> Date: Sun, 17 Feb 2002 09:53:25 +0100 From: Michael Class User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.8) Gecko/20020206 X-Accept-Language: en-us MIME-Version: 1.0 To: current@freebsd.org Subject: Recent USB problems Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Sender: 320021761316-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, after the following patch: joe 2002/02/15 16:51:26 PST Modified files: sys/dev/usb ohci.c uhci.c usb.h usb_subr.c usbdivar.h Log: Merge from NetBSD: Pave the way for USB2, by replacing 'lowspeed' with 'speed', so that it can take the values USB_SPEED_LOW, USB_SPEED_FULL or in time USB_SPEED_HIGH. my USB-mouse quits working. Normal dmesg output looks like this: uhci0: port 0xcc00-0xcc1f irq 12 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: KYE Genius USB Wheel Mouse, rev 1.00/0.00, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. uhci1: port 0xd800-0xd81f irq 12 at device 7.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered Now the system pauses for approx. 15 second during boot and the output looks like this: uhci0: port 0xcc00-0xcc1f irq 12 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered << here pause >> usbd_new_device: addr=2, getting first desc failed uhub0: device problem, disabling port 1 uhci1: port 0xd800-0xd81f irq 12 at device 7.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered The system is a dual PIII Gigabyte system with VIA-Chipset. Any hints? Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 2:49:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 3DC8737B400; Sun, 17 Feb 2002 02:49:47 -0800 (PST) Received: from pool0048.cvx21-bradley.dialup.earthlink.net ([209.179.192.48] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16cOsU-0000fx-00; Sun, 17 Feb 2002 02:49:06 -0800 Message-ID: <3C6F8A98.2D9EA4AF@mindspring.com> Date: Sun, 17 Feb 2002 02:48:56 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Evans Cc: Paul van der Zwan , Riccardo Torrini , Brian Fundakowski Feldman , current@FreeBSD.ORG Subject: Re: USB detach crashes possibly fixed References: <20020217190322.J934-100000@gamplex.bde.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bruce Evans wrote: > On Sat, 16 Feb 2002, Terry Lambert wrote: > > PHK was threatening to murder /dev/speaker to work > > around some clock issues that would be hard to nail > > down the right way. > > I think you mean /dev/pcaudio. Yes; I confused the two, since I rarely do audio stuff at all (I think implementing the ALSA kernel and lib stuff for FreeBSD would not be a bad project for a junior person). So the problem can't be related to the timer changes that Poul was contemplating; therefore it *must* be related to the USB stuff. Maybe it's stomping on an interrupt or I/O address or something. 8-(. > I use /dev/pcaudio to expose the > brokenness of clock code that is not nailed down in the right way. Humor. Ar ar ar. To the original poster: So to fix the original problem, you should disable everything you can (and still boot) except the audio stuff, and then add things back in until it fails; this will identify the problem area, and we can go from there. Uh, it occurs to me that you might be loading your driver as a kernel module; if so, you remembered to recompile it when you recompiled your kernel, right? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 3: 3: 6 2002 Delivered-To: freebsd-current@freebsd.org Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138]) by hub.freebsd.org (Postfix) with ESMTP id BB26037B404; Sun, 17 Feb 2002 03:02:56 -0800 (PST) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtpzilla2.xs4all.nl (8.12.0/8.12.0) with ESMTP id g1HB2mUH026936; Sun, 17 Feb 2002 12:02:49 +0100 (CET) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.11.6/8.11.6) with ESMTP id g1HB2m146727; Sun, 17 Feb 2002 12:02:48 +0100 (MET) (envelope-from paulz@trantor.xs4all.nl) Message-Id: <200202171102.g1HB2m146727@trantor.xs4all.nl> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: "Brian F. Feldman" Subject: Re: USB detach crashes possibly fixed In-reply-to: Your message of "Sat, 16 Feb 2002 20:28:13 EST." <200202170128.g1H1SDY03195@green.bikeshed.org> Cc: Riccardo Torrini , current@FreeBSD.ORG Date: Sun, 17 Feb 2002 12:02:48 +0100 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Fcc: outbox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii -------- > > > > > > and I got a small tune on attach but nothing on detach. > > > Now I am unable to play notes on /dev/speaker. Any hint? > > As Terry notes, shouldn't possibly be related. > > > I have no crashes but the detach action is never executed when I switch off > > my Sony camera ( it has never worked as far as I know) > > Attach actions are executed fine.. > > Have you tried compiling in all available USB debugging support or seeing if > anyone else is using one like yours? No, but if I run usbd in the foreground and with some -v flags it never reports seeing a detach event even though the device driver reports it. It looks like usbd just doesn't get it... This is what the kernel logs when switching the camera on and off. Feb 17 11:57:44 trantor kernel: umass0: Sony Sony DSC, rev 1.00/2.10, addr 2 Feb 17 11:57:44 trantor kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Feb 17 11:57:44 trantor kernel: da0: Removable Direct Access SCSI-0 device Feb 17 11:57:44 trantor kernel: da0: 150KB/s transfers Feb 17 11:57:44 trantor kernel: da0: 61MB (126848 512 byte sectors: 0H 0S/T 0C) Feb 17 11:58:04 trantor kernel: umass0: at uhub0 port 1 (addr 2) disconnected Feb 17 11:58:04 trantor kernel: (da0:umass-sim0:0:0:0): lost device Feb 17 11:58:04 trantor kernel: umass0: detached Looks OK to me. And this is what usbd prints $ sudo usbd -d -v -v -v -v usbd: opened /dev/usb0 usbd: opened /dev/usb1 usbd: opened /dev/usb2 usbd: reading configuration file /etc/usbd.conf usbd: action 1: Sony DSC S70 Camera vndr=0x054c prdct=0x0010 attach='sleep 5 ;mount /sony' detach='umount -f /sony' usbd: action 2: USB device usbd: 2 actions usbd: opened /dev/usb usbd: device-attach event at 1013898654.505840000, Sony DSC, Sony: vndr=0x054c prdct=0x0010 rlse=0x0210 clss=0x0000 subclss=0x0000 prtcl=0x0000 device names: umass0 usbd: Found action 'Sony DSC S70 Camera' for Sony DSC, Sony at umass0 usbd: action 0: Sony DSC S70 Camera vndr=0x054c prdct=0x0010 attach='sleep 5 ;mount /sony' detach='umount -f /sony' usbd: Setting DEVNAME='umass0' usbd: Executing 'sleep 5 ;mount /sony' msdosfs: /dev/da0s1: No such file or directory usbd: 'sleep 5 ;mount /sony' returned 71 usbd: doing timeout discovery on /dev/usb0 usbd: doing timeout discovery on /dev/usb1 usbd: doing timeout discovery on /dev/usb2 usbd: processing event queue due to timeout on /dev/usb usbd: doing timeout discovery on /dev/usb0 usbd: doing timeout discovery on /dev/usb1 usbd: doing timeout discovery on /dev/usb2 usbd: processing event queue due to timeout on /dev/usb usbd: processing event queue on /dev/usb usbd: device-attach event at 1013943463.949946000, Sony DSC, Sony: vndr=0x054c prdct=0x0010 rlse=0x0210 clss=0x0000 subclss=0x0000 prtcl=0x0000 device names: umass0 usbd: Found action 'Sony DSC S70 Camera' for Sony DSC, Sony at umass0 usbd: action 0: Sony DSC S70 Camera vndr=0x054c prdct=0x0010 attach='sleep 5 ;mount /sony' detach='umount -f /sony' usbd: Setting DEVNAME='umass0' usbd: Executing 'sleep 5 ;mount /sony' usbd: 'sleep 5 ;mount /sony' is ok usbd: doing timeout discovery on /dev/usb0 usbd: doing timeout discovery on /dev/usb1 usbd: doing timeout discovery on /dev/usb2 usbd: processing event queue due to timeout on /dev/usb usbd: doing timeout discovery on /dev/usb0 usbd: doing timeout discovery on /dev/usb1 usbd: doing timeout discovery on /dev/usb2 usbd: processing event queue due to timeout on /dev/usb usbd: doing timeout discovery on /dev/usb0 usbd: doing timeout discovery on /dev/usb1 usbd: doing timeout discovery on /dev/usb2 usbd: processing event queue due to timeout on /dev/usb ^C It looks like the driver works fine as far as I can tell, but usbd just doesn't see the detach event. -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 3:47:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from vbook.express.ru (asplinux.ru [195.133.213.194]) by hub.freebsd.org (Postfix) with ESMTP id 9A6EA37B404 for ; Sun, 17 Feb 2002 03:47:54 -0800 (PST) Received: from localhost ([127.0.0.1]) by vbook.express.ru with esmtp (Exim 3.33 #1) id 16cPm5-00008F-00; Sun, 17 Feb 2002 14:46:33 +0300 Subject: Re: USB detach crashes possibly fixed From: "Vladimir B. " Grebenschikov To: Paul van der Zwan Cc: current@freebsd.org In-Reply-To: <200202162149.g1GLnK100609@trantor.xs4all.nl> References: <200202162149.g1GLnK100609@trantor.xs4all.nl> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution/1.0.2 Date: 17 Feb 2002 14:46:33 +0300 Message-Id: <1013946393.417.9.camel@vbook.express.ru> Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 2002-02-17 at 00:49, Paul van der Zwan wrote: > I have no crashes but the detach action is never executed when I switch o= ff > my Sony camera ( it has never worked as far as I know) > Attach actions are executed fine.. I have not see crashas any more too, BUT now I can't see my usb keyboard and mice at all: On today's current: uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.10/1.10, addr 2 uhub1: 4 ports with 4 removable, bus powered uhub1: device problem, disabling port 2 uhub1: device problem, disabling port 4 Same kernel with usb modules build on Feb 13 sources (previous): uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.10/1.10, addr 2 uhub1: 4 ports with 4 removable, bus powered ukbd0: Behavior Tech. Computer Keyboard with mouse port, rev 1.00/1.00, addr 3, iclass 3/1 kbd1 at ukbd0 ums0: Behavior Tech. Computer Keyboard with mouse port, rev 1.00/1.00, addr 3, iclass 3/1 ums0: 3 buttons ums1: Microsoft Microsoft IntelliMouse=AE Explorer, rev 1.10/1.14, addr 4, iclass 3/1 ums1: 5 buttons and Z dir. Output of usbdevs -v: Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 addr 2: power 100 mA, config 1, UT-USB41 hub(0x1446), Texas Instruments(0x0451), rev 1.10 port 1 powered port 2 addr 3: low speed, power 100 mA, config 1, Keyboard with mouse port(0x6782), Behavior Tech. Computer(0x046e), rev 1.00 port 3 powered port 4 addr 4: low speed, power 100 mA, config 1, Microsoft IntelliMouse=AE Explorer(0x001e), Microsoft(0x045e), rev 1.14 port 2 powered And usbd still not detect detaches (not execute detach scripts) People what is going on with USB code ??? > Paul --=20 TSB "Russian Express", Moscow Vladimir B. Grebenschikov, vova@express.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 5:56:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 1A2FF37B402; Sun, 17 Feb 2002 05:56:50 -0800 (PST) Received: from pool0100.cvx22-bradley.dialup.earthlink.net ([209.179.198.100] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16cRng-0002J4-00; Sun, 17 Feb 2002 05:56:20 -0800 Message-ID: <3C6FB679.3B505586@mindspring.com> Date: Sun, 17 Feb 2002 05:56:09 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Paul van der Zwan Cc: "Brian F. Feldman" , Riccardo Torrini , current@FreeBSD.ORG Subject: Re: USB detach crashes possibly fixed References: <200202171102.g1HB2m146727@trantor.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Paul van der Zwan wrote: > No, but if I run usbd in the foreground and with some -v flags it never > reports seeing a detach event even though the device driver reports it. > It looks like usbd just doesn't get it... [ ... ] > It looks like the driver works fine as far as I can tell, but usbd just > doesn't see the detach event. Does the daemon use kqueue? It looks like there's a bug in kqueue for FIN processing, and another bug in another area. It appears to all be FreeBSD 4.5/current specific (4.4 doesn't have the lost event problem). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 6:16:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from barry.mail.mindspring.net (barry.mail.mindspring.net [207.69.200.25]) by hub.freebsd.org (Postfix) with ESMTP id 7F5A137B426 for ; Sun, 17 Feb 2002 06:16:38 -0800 (PST) Received: from user-1120bmq.dsl.mindspring.com ([66.32.46.218] helo=europa2) by barry.mail.mindspring.net with smtp (Exim 3.33 #1) id 16cS7E-000272-00; Sun, 17 Feb 2002 09:16:32 -0500 Message-Id: <3.0.6.32.20020217091453.00da57b8@imatowns.com> X-Sender: ggombert@imatowns.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 17 Feb 2002 09:14:53 -0500 To: Bruce Evans , Matthew Dillon From: Glenn Gombert Subject: Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? Cc: In-Reply-To: <20020217184436.M934-100000@gamplex.bde.org> References: <200202170028.g1H0SQZ41827@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I also see these messages on my Dell 410 Workstation at work and a Dual PIII Box I use at home to do builds with...they just seem to 'come and go' with no particular pattern to them...I have just been ignoring them for the most part...they don't really seem to cause any problems...... At 06:54 PM 2/17/2002 +1100, Bruce Evans wrote: >On Sat, 16 Feb 2002, Matthew Dillon wrote: > >> Testing with a 'make -j 10 buildworld' on a -current box I am getting >> regular: >> >> microuptime() went backwards (146.826785 -> 146.156715) >> microuptime() went backwards (146.826782 -> 146.228636) >> ... >> microuptime() went backwards (8945.938288 -> 8945.251603) >> microuptime() went backwards (8945.938306 -> 8945.347173) >> microuptime() went backwards (9142.847550 -> 9142.847546) >> >> This occurs both with and without the gettimeofday Giant-removal patch, so >> I am fairly sure it has nothing to do with any of my current work. This is >> running -current on a DELL2550 (2xCPUs), compiled with the SMP option. > >The fact that the timecounter usually goes backwards by about 0.68 seconds >is probably significant, but I can't quite explain it. > >> Timecounter "i8254" frequency 1193182 Hz >> ... >> Timecounter "ACPI" frequency 3579545 Hz >> acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 >> acpi_cpu0: on acpi0 >> acpi_cpu1: on acpi0 >> acpi_pcib0: on acpi0 >> ... >> >> Question: How can this be occuring at all? Isn't the ACPI counter a >> 32 bit counter that does not have the rollover problems that the 8254 timer >> has? > >Timecounters go backwards when the timecounter update or reference code is >called insufficiently often to prevent overflow. The rollover problems of >the i8254 timecounter actually reduce this problem. If an i8254 rollover >is missed, then it causes the the i8254 timecounter to go forward less >than it should. > >I just wrote the following fix for some of the overflow problems. > >%%% >Index: kern_tc.c >=================================================================== >RCS file: /home/ncvs/src/sys/kern/kern_tc.c,v >retrieving revision 1.113 >diff -c -2 -r1.113 kern_tc.c >*** kern_tc.c 7 Feb 2002 21:21:55 -0000 1.113 >--- kern_tc.c 17 Feb 2002 06:25:14 -0000 >*************** >*** 108,114 **** > struct timecounter *tc; > >! tc = timecounter; >! *bt = tc->tc_offset; >! bintime_addx(bt, tc->tc_scale * tco_delta(tc)); > } > >--- 95,129 ---- > struct timecounter *tc; > >! /* >! * The loop is to handle changes of timecounter underneath us. >! * Such changes may even become normal for preemptive kernels. >! * It is quite reasonable for idle priority processes to not >! * run for many seconds, and if they are not running after >! * being preempted here, the timecounter may cycle many times >! * underneath them. An NTIMECOUNTER of > 2 is neither necessary >! * or sufficient for fixing this problem, unless NTIMECOUNTER is >! * preposterously large. NTIMECOUNTER == 2 suffices for most >! * cases, and something more is required to fix the general case. >! * >! * I hope this also fixes problems with overflow of the >! * multiplication. We depend on tc not becoming stale by more >! * than 1 second. We will now normally see such staleness >! * because it will cause the timecounter to change many times >! * underneath us. There will only be problems if hardclock() >! * doesn't run for many seconds, but hardclock() is a very >! * high priority interrupt, so such problems "can't happen". >! * >! * XXX should use a generation count. >! * >! * XXX problems with hardclock() can happen, e.g., at boot time >! * if you have fixed hardclock() to not be a broken fast interrupt >! * handler, or if you sit at the ddb prompt for several seconds. >! * Should do something to make them harmless. >! */ >! do { >! tc = timecounter; >! *bt = tc->tc_offset; >! bintime_addx(bt, tc->tc_scale * tco_delta(tc)); >! } while (tc != timecounter); > } > >%%% > >Bruce > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > Glenn Gombert ggombert@imatowns.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 6:57:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 878DA37B402; Sun, 17 Feb 2002 06:57:05 -0800 (PST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.6/8.11.6) with ESMTP id g1HEvHh16098; Sun, 17 Feb 2002 15:57:17 +0100 (CET) Date: Sun, 17 Feb 2002 15:57:59 +0100 (CET) From: Martin Blapp To: Cc: , , , Subject: FreeBSD unfinished NIS+ implementation in Linux ? Message-ID: <20020217155122.J17787-100000@levais.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all, While looking at nis-utils-1.4.1 from linux, I found that that whole package is based on Bill's work. Intersting that everything there is GNU labled. What happened to the BSD copyright ? Or has it been GPL'd from the beginning ? http://freshmeat.net/projects/nis-utils The author even forgot to remove one part of a manpage: nis-utils-1.4.1$ more man/nis_db.3 .Em The TI-RPCSRC 2.3 source code distribution. .Sh HISTORY This implementation of the .Nm nis_db library was written for and is scheduled to appear in a future release of FreeBSD 2.x as part of a complete, freely available NIS+ client and server package. This library was written entirely from scratch: no Sun code other than the publically available NIS+ header files was referenced. Strange thing. Bill, did you ever allowed them to make it GPL only ? Looking at the code it should be possible to import some things and make a NIS+ client available. But only if it's not GPL'd. Martin Martin Blapp, ------------------------------------------------------------------ ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E ------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 7:24:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 8BBAD37B402; Sun, 17 Feb 2002 07:24:15 -0800 (PST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.6/8.11.6) with ESMTP id g1HFOQh18153; Sun, 17 Feb 2002 16:24:27 +0100 (CET) Date: Sun, 17 Feb 2002 16:25:09 +0100 (CET) From: Martin Blapp To: , Subject: Re: FreeBSD unfinished NIS+ implementation in Linux ? Message-ID: <20020217161648.W17787-100000@levais.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bills Work: http://people.freebsd.org/~wpaul/nis.tar.gz Suse Linux version: ftp://ftp.kernel.org/pub/linux/utils/net/NIS+/nis-utils-1.4.1.tar.bz2 An example from a file: File: db_add_entry.c Bills Copyright: /* * Copyright (c) 1996, 1997 * Bill Paul . All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. All advertising materials mentioning features or use of this software * must display the following acknowledgement: * This product includes software developed by Bill Paul. * 4. Neither the name of the author nor the names of any co-contributors * may be used to endorse or promote products derived from this software * without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * * $FreeBSD$ */ Suse's Copyright: /* Copyright (c) 1999 Thorsten Kukuk Author: Thorsten Kukuk This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */ Martin Martin Blapp, ------------------------------------------------------------------ ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E ------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 9:46:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id AF0A837B400 for ; Sun, 17 Feb 2002 09:46:07 -0800 (PST) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.1/8.12.1) with ESMTP id g1HHk4il009077; Sun, 17 Feb 2002 12:46:04 -0500 (EST) Date: Sun, 17 Feb 2002 12:46:04 -0500 (EST) From: Daniel Eischen To: Kevin Day Cc: current@FreeBSD.ORG Subject: Re: function name collision on "getcontext" with ports/editors/joe In-Reply-To: <200202100723.g1A7NtW54701@shell.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 10 Feb 2002, Kevin Day wrote: > > I'm the maintainer for ports/editors/joe, and just tried compiling it under > -CURRENT. > > includes which includes ucontext.h > > > cc -O -pipe -c umath.c > > In file included from b.h:6, > > from bw.h:23, > > from umath.c:5: > > rc.h:41: conflicting types for `getcontext' > > /usr/include/sys/ucontext.h:54: previous declaration of `getcontext' > > *** Error code 1 > > > > Stop in /usr/ports/editors/joe/work/joe. > > > I can rename getcontext in joe, but "getcontext" seems like a pretty common > function name, I know I've used it in projects before. Not including > signal.h isn't really an option either. The ucontext related namespace pollution should be fixed now. Let me know otherwise. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 10:15:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from beastie.jocose.org (beastie.jocose.org [199.199.226.71]) by hub.freebsd.org (Postfix) with SMTP id A8E8D37B47C for ; Sun, 17 Feb 2002 10:15:18 -0800 (PST) Received: (qmail 35493 invoked from network); 17 Feb 2002 19:15:08 -0000 Received: from unknown (HELO jocose.org) (10.0.0.100) by 0 with SMTP; 17 Feb 2002 19:15:08 -0000 Message-ID: <3C6FF3B7.3030901@jocose.org> Date: Sun, 17 Feb 2002 12:17:27 -0600 From: Peter Schultz Organization: jocose.org User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.8) Gecko/20020216 X-Accept-Language: en-us MIME-Version: 1.0 To: current@freebsd.org Subject: problem installing ports Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Two ports I've tried to install recently, open-motif-devel and AbiWord, have attempted to `mkdir /'. This fails with: "mkdir: /: Is a directory." Installing these ports works just fine under 4.5-STABLE. Pete... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 10:46:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C6EBC37B404 for ; Sun, 17 Feb 2002 10:46:14 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1HIkCQ71367; Sun, 17 Feb 2002 10:46:12 -0800 (PST) (envelope-from dillon) Date: Sun, 17 Feb 2002 10:46:12 -0800 (PST) From: Matthew Dillon Message-Id: <200202171846.g1HIkCQ71367@apollo.backplane.com> To: Bruce Evans Cc: Subject: Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? References: <20020217184436.M934-100000@gamplex.bde.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :I just wrote the following fix for some of the overflow problems. I don't understand how this code is supposed to handle overflows. You seem only to be checking to see if the master timecounter has changed to a different type. -Matt Matthew Dillon :%%% :Index: kern_tc.c :=================================================================== :RCS file: /home/ncvs/src/sys/kern/kern_tc.c,v :retrieving revision 1.113 :diff -c -2 -r1.113 kern_tc.c :*** kern_tc.c 7 Feb 2002 21:21:55 -0000 1.113 :--- kern_tc.c 17 Feb 2002 06:25:14 -0000 :*************** :*** 108,114 **** : struct timecounter *tc; : :! tc = timecounter; :! *bt = tc->tc_offset; :! bintime_addx(bt, tc->tc_scale * tco_delta(tc)); : } : :--- 95,129 ---- : struct timecounter *tc; : :! /* :! * The loop is to handle changes of timecounter underneath us. :! * Such changes may even become normal for preemptive kernels. :! * It is quite reasonable for idle priority processes to not :! * run for many seconds, and if they are not running after :! * being preempted here, the timecounter may cycle many times :! * underneath them. An NTIMECOUNTER of > 2 is neither necessary :! * or sufficient for fixing this problem, unless NTIMECOUNTER is :! * preposterously large. NTIMECOUNTER == 2 suffices for most :! * cases, and something more is required to fix the general case. :! * :! * I hope this also fixes problems with overflow of the :! * multiplication. We depend on tc not becoming stale by more :! * than 1 second. We will now normally see such staleness :! * because it will cause the timecounter to change many times :! * underneath us. There will only be problems if hardclock() :! * doesn't run for many seconds, but hardclock() is a very :! * high priority interrupt, so such problems "can't happen". :! * :! * XXX should use a generation count. :! * :! * XXX problems with hardclock() can happen, e.g., at boot time :! * if you have fixed hardclock() to not be a broken fast interrupt :! * handler, or if you sit at the ddb prompt for several seconds. :! * Should do something to make them harmless. :! */ :! do { :! tc = timecounter; :! *bt = tc->tc_offset; :! bintime_addx(bt, tc->tc_scale * tco_delta(tc)); :! } while (tc != timecounter); : } : :%%% : :Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 11:42:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from squall.waterspout.com (squall.waterspout.com [208.13.56.12]) by hub.freebsd.org (Postfix) with ESMTP id 3010237B422; Sun, 17 Feb 2002 11:42:14 -0800 (PST) Received: by squall.waterspout.com (Postfix, from userid 1050) id 58C379B19; Sun, 17 Feb 2002 14:41:19 -0500 (EST) Date: Sun, 17 Feb 2002 14:41:19 -0500 From: Will Andrews To: Martin Blapp Cc: wpaul@freebsd.org, current@freebsd.org Subject: Re: FreeBSD unfinished NIS+ implementation in Linux ? Message-ID: <20020217194119.GD58005@squall.waterspout.com> Mail-Followup-To: Martin Blapp , wpaul@freebsd.org, current@freebsd.org References: <20020217155122.J17787-100000@levais.imp.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020217155122.J17787-100000@levais.imp.ch> User-Agent: Mutt/1.3.26i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Feb 17, 2002 at 03:57:59PM +0100, Martin Blapp wrote: > Bill, did you ever allowed them to make it GPL only ? Looking at the code > it should be possible to import some things and make a NIS+ client > available. But only if it's not GPL'd. Interesting. I looked as nisgrep/nisgrep.c and noticed that the code structure was basically the same, but the variables were just slightly different... -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 12:10:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 8A3A537B416 for ; Sun, 17 Feb 2002 12:10:05 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id VAA02303 for freebsd-current@freebsd.org; Sun, 17 Feb 2002 21:10:04 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g1HK7Tl25937; Sun, 17 Feb 2002 21:07:29 +0100 (MET) (envelope-from j) Date: Sun, 17 Feb 2002 21:07:29 +0100 (MET) Message-Id: <200202172007.g1HK7Tl25937@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden 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 References: <20020217161648.W17787-100000@levais.imp.ch> From: j@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: FreeBSD unfinished NIS+ implementation in Linux ? X-Original-Newsgroups: local.freebsd.current To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Martin Blapp wrote: > Suse's Copyright: > > /* Copyright (c) 1999 Thorsten Kukuk > Author: Thorsten Kukuk That would at least be a copyright violation. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL 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 Sun Feb 17 12:21: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 6602337B433 for ; Sun, 17 Feb 2002 12:21:01 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g1HKHtN05682; Sun, 17 Feb 2002 21:17:56 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? In-Reply-To: Your message of "Sun, 17 Feb 2002 18:54:13 +1100." <20020217184436.M934-100000@gamplex.bde.org> Date: Sun, 17 Feb 2002 21:17:54 +0100 Message-ID: <5680.1013977074@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020217184436.M934-100000@gamplex.bde.org>, Bruce Evans writes: >> This occurs both with and without the gettimeofday Giant-removal patch, so >> I am fairly sure it has nothing to do with any of my current work. This is >> running -current on a DELL2550 (2xCPUs), compiled with the SMP option. The Gian removal doesn't come anywhere near this. >The fact that the timecounter usually goes backwards by about 0.68 seconds >is probably significant, but I can't quite explain it. >> acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 Well: 2^32 / 3579545 = 1199.86 seconds. 2^24 / 3579545 = 4.68 seconds. So even assuming that ACPI reported a wrong width, four seconds should still be enough to prevent a wraparound even though we cycle through the timecounter ring in one second. >I just wrote the following fix for some of the overflow problems. It is true that if a process is not running for arbitrary long time the timecounter may be modified underneat it, and bruce's patch is actually a pretty elegant solution for that case. By all means try it. I have had one other report of a similar problem, with the added information that changing to the TSC or i8254 instead of PIXX made it go away so I am not entirely convinced this is really what we are looking for in this case. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 12:25:17 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id C46D637B416 for ; Sun, 17 Feb 2002 12:25:12 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g1HKM7N05783; Sun, 17 Feb 2002 21:22:07 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? In-Reply-To: Your message of "Sun, 17 Feb 2002 10:46:12 PST." <200202171846.g1HIkCQ71367@apollo.backplane.com> Date: Sun, 17 Feb 2002 21:22:07 +0100 Message-ID: <5781.1013977327@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200202171846.g1HIkCQ71367@apollo.backplane.com>, Matthew Dillon wri tes: >:I just wrote the following fix for some of the overflow problems. > > I don't understand how this code is supposed to handle overflows. > You seem only to be checking to see if the master timecounter has > changed to a different type. Bruce's patch amounts to a retry if the current timecounter was updated while we were calculating time. It is a bit more defensive than it needs to be and generally pessimizes the timecounters elegant lockless design a fair bit, but it is still much better than slamming a mutex around the entire clock code. If this patch cures the PIIX problem, something I'm not at all convinced about, it should go in, if not only the comment should go in. Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 12:25:46 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9875337B405 for ; Sun, 17 Feb 2002 12:25:40 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1HKPc589840; Sun, 17 Feb 2002 12:25:38 -0800 (PST) (envelope-from dillon) Date: Sun, 17 Feb 2002 12:25:38 -0800 (PST) From: Matthew Dillon Message-Id: <200202172025.g1HKPc589840@apollo.backplane.com> To: Bruce Evans Cc: Subject: Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? References: <20020217184436.M934-100000@gamplex.bde.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ok, I've looked at the code more carefully and I understand how this works now. However, it is not enough in an SMP environment. You need a generation count in the timecounter structure and you also need a synchronization point when you switch time counters or a process running on a different cpu may wind up using a time counter that is being actively updated. I'm experimenting with your patch now. I'll send email when I have some test results. -Matt : :I just wrote the following fix for some of the overflow problems. : :%%% :Index: kern_tc.c :=================================================================== :RCS file: /home/ncvs/src/sys/kern/kern_tc.c,v :retrieving revision 1.113 :diff -c -2 -r1.113 kern_tc.c :... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 12:38: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B0A5C37B41E for ; Sun, 17 Feb 2002 12:38:03 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1HKc1891121; Sun, 17 Feb 2002 12:38:01 -0800 (PST) (envelope-from dillon) Date: Sun, 17 Feb 2002 12:38:01 -0800 (PST) From: Matthew Dillon Message-Id: <200202172038.g1HKc1891121@apollo.backplane.com> To: Poul-Henning Kamp Cc: Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Success! Sorta! (was Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? ) References: <5781.1013977327@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Bruce's patch amounts to a retry if the current timecounter was updated :while we were calculating time. It is a bit more defensive than it :needs to be and generally pessimizes the timecounters elegant lockless :design a fair bit, but it is still much better than slamming a mutex :around the entire clock code. : :If this patch cures the PIIX problem, something I'm not at all convinced :about, it should go in, if not only the comment should go in. : :Poul-Henning : :-- :Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 Ok, I've tested Bruce's patch and it appeaars to mostly solve the problem. I no longer get 'microuptime ... backwards' errors on a -current SMP box. However, I think to be complete we need to make it even less elegant. The TC module is only flip-flopping between two time counters, which means that it can flip-flop twice and the test will not work. We need a generation count on the timecounter as well: do { tc = timecounter; gen = tc->tc_generation; *bt = tc->tc_offset; bintime_addx(bt, tc->tc_scale * tco_delta(tc)); } while (tc != timecounter || tc->tc_generation != gen); There is also an issue on non-i386 machines. The timecounter swapping code requires a memory synchronization point after updating the contents of the new timecounter but before setting the 'timecounter' global to the new timecounter. If this is not done, non-i386 machines running SMP may see the new timecounter structure but access pre-updated values from it. (i386 boxes do not have this problem because writes are ordered so the inherent synchronication point at the end of the timer interrupt is enough). Is there a memory synchronization point macro available? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 12:43: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 85AD737B402 for ; Sun, 17 Feb 2002 12:42:54 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1HKgs691210; Sun, 17 Feb 2002 12:42:54 -0800 (PST) (envelope-from dillon) Date: Sun, 17 Feb 2002 12:42:54 -0800 (PST) From: Matthew Dillon Message-Id: <200202172042.g1HKgs691210@apollo.backplane.com> To: Poul-Henning Kamp , Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: Success! Sorta! (was Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? ) References: <5781.1013977327@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Whoop! I take it back. I'm still getting the errors: microuptime() went backwards (458.168990 -> 458.168882) microuptime() went backwards (578.609995 -> 577.929801) microuptime() went backwards (748.912755 -> 748.237402) microuptime() went backwards (775.159625 -> 775.159612) I also think this retry loop has to be done everywhere where the timecounter structure is accessed directly. -Matt : Ok, I've tested Bruce's patch and it appeaars to mostly solve the problem. : I no longer get 'microuptime ... backwards' errors on a -current SMP : box. :... Index: kern/kern_tc.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_tc.c,v retrieving revision 1.113 diff -u -r1.113 kern_tc.c --- kern/kern_tc.c 7 Feb 2002 21:21:55 -0000 1.113 +++ kern/kern_tc.c 17 Feb 2002 20:41:47 -0000 @@ -107,9 +107,11 @@ { struct timecounter *tc; - tc = timecounter; - *bt = tc->tc_offset; - bintime_addx(bt, tc->tc_scale * tco_delta(tc)); + do { + tc = timecounter; + *bt = tc->tc_offset; + bintime_addx(bt, tc->tc_scale * tco_delta(tc)); + } while (tc != timecounter); } void @@ -126,8 +128,10 @@ struct timecounter *tc; ngetmicrotime++; - tc = timecounter; - *tvp = tc->tc_microtime; + do { + tc = timecounter; + *tvp = tc->tc_microtime; + } while (tc != timecounter); } void @@ -136,8 +140,10 @@ struct timecounter *tc; ngetnanotime++; - tc = timecounter; - *tsp = tc->tc_nanotime; + do { + tc = timecounter; + *tsp = tc->tc_nanotime; + } while (tc != timecounter); } void @@ -166,8 +172,10 @@ struct timecounter *tc; ngetmicrouptime++; - tc = timecounter; - bintime2timeval(&tc->tc_offset, tvp); + do { + tc = timecounter; + bintime2timeval(&tc->tc_offset, tvp); + } while (tc != timecounter); } void @@ -176,8 +184,10 @@ struct timecounter *tc; ngetnanouptime++; - tc = timecounter; - bintime2timespec(&tc->tc_offset, tsp); + do { + tc = timecounter; + bintime2timespec(&tc->tc_offset, tsp); + } while (tc != timecounter); } void To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 12:43:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id E7BBC37B41A for ; Sun, 17 Feb 2002 12:43:26 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g1HKeMN06317; Sun, 17 Feb 2002 21:40:22 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: Success! Sorta! (was Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? ) In-Reply-To: Your message of "Sun, 17 Feb 2002 12:38:01 PST." <200202172038.g1HKc1891121@apollo.backplane.com> Date: Sun, 17 Feb 2002 21:40:21 +0100 Message-ID: <6315.1013978421@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200202172038.g1HKc1891121@apollo.backplane.com>, Matthew Dillon wri tes: > However, I think to be complete we need to make it even less elegant. > The TC module is only flip-flopping between two time counters, which > means that it can flip-flop twice and the test will not work. We need > a generation count on the timecounter as well: > > do { > tc = timecounter; > gen = tc->tc_generation; > *bt = tc->tc_offset; > bintime_addx(bt, tc->tc_scale * tco_delta(tc)); > } while (tc != timecounter || tc->tc_generation != gen); No, more like: do { tc = timecounter; gen = tc->gen; ... } while (gen != tc->gen); -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 12:52: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 4272637B402 for ; Sun, 17 Feb 2002 12:51:56 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g1HKmqN06434; Sun, 17 Feb 2002 21:48:52 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: Success! Sorta! (was Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? ) In-Reply-To: Your message of "Sun, 17 Feb 2002 12:42:54 PST." <200202172042.g1HKgs691210@apollo.backplane.com> Date: Sun, 17 Feb 2002 21:48:52 +0100 Message-ID: <6432.1013978932@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200202172042.g1HKgs691210@apollo.backplane.com>, Matthew Dillon wri tes: > Whoop! I take it back. I'm still getting the errors: > >microuptime() went backwards (458.168990 -> 458.168882) >microuptime() went backwards (578.609995 -> 577.929801) >microuptime() went backwards (748.912755 -> 748.237402) >microuptime() went backwards (775.159625 -> 775.159612) > > I also think this retry loop has to be done everywhere where the > timecounter structure is accessed directly. No, only where the timecounter hardware is read and the math done. As far as I know, this is the only place. As I said, I am far from convinced this is the solution to the problem we are looking at with the PIIX timecounter. Msmith has some magic code in sys/dev/acpi/acpi_timer.c which tries to identify if the PIIX counter is broken or OK and I notice that the mask seems to always be set to 24 bits even if the hardware is 32 bits. I am not sure I read his code right, but he seems to default to the unsafe method, can you try this copy&pasted patch ? Index: acpi_timer.c =================================================================== RCS file: /home/ncvs/src/sys/dev/acpica/acpi_timer.c,v retrieving revision 1.11 diff -u -r1.11 acpi_timer.c --- acpi_timer.c 8 Jan 2002 06:45:56 -0000 1.11 +++ acpi_timer.c 17 Feb 2002 20:48:23 -0000 @@ -138,7 +138,7 @@ if (getenv("debug.acpi.timer_test") != NULL) acpi_timer_test(); - acpi_timer_timecounter.tc_get_timecount = acpi_timer_get_timecount; + acpi_timer_timecounter.tc_get_timecount = acpi_timer_get_timecount_safe; acpi_timer_timecounter.tc_frequency = acpi_timer_frequency; tc_init(&acpi_timer_timecounter); -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 12:59:14 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id CED2A37B41A for ; Sun, 17 Feb 2002 12:58:46 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g1HKtgN06618; Sun, 17 Feb 2002 21:55:42 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? In-Reply-To: Your message of "Sun, 17 Feb 2002 12:25:38 PST." <200202172025.g1HKPc589840@apollo.backplane.com> Date: Sun, 17 Feb 2002 21:55:42 +0100 Message-ID: <6616.1013979342@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matt, Easy now, there is more depth to it than that... I have promised myself to get the timecounter paper written and I'll probably present it at BSDcon-euro-2002 in Amsterdam if they want to listen to me. For now, lets concentrate on the PIIX hardware because that's where the problem seems to be... Poul-Henning In message <200202172025.g1HKPc589840@apollo.backplane.com>, Matthew Dillon wri tes: > Ok, I've looked at the code more carefully and I understand how this > works now. However, it is not enough in an SMP environment. You > need a generation count in the timecounter structure and you also need > a synchronization point when you switch time counters or a process > running on a different cpu may wind up using a time counter that is being > actively updated. > > I'm experimenting with your patch now. I'll send email when I have > some test results. > > -Matt > >: >:I just wrote the following fix for some of the overflow problems. >: >:%%% >:Index: kern_tc.c >:=================================================================== >:RCS file: /home/ncvs/src/sys/kern/kern_tc.c,v >:retrieving revision 1.113 >:diff -c -2 -r1.113 kern_tc.c >:... > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 13:54:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id C2E4737B402 for ; Sun, 17 Feb 2002 13:54:51 -0800 (PST) Received: from horsey.gshapiro.net (gshapiro@localhost [IPv6:::1]) by horsey.gshapiro.net (8.12.2/8.12.3.PreAlpha0) with ESMTP id g1HLspku026253 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 17 Feb 2002 13:54:51 -0800 (PST) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.12.2/8.12.2/Submit) id g1HLspPB026250; Sun, 17 Feb 2002 13:54:51 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15472.9898.868296.694584@horsey.gshapiro.net> Date: Sun, 17 Feb 2002 13:54:50 -0800 From: Gregory Neil Shapiro To: freebsd-current@freebsd.org Subject: HEADS UP: Expect buildworld instability X-Mailer: VM 7.00 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm about to begin the import of sendmail 8.12.2 into -CURRENT. While I am doing the important, it's likely that a buildworld will fail. I'll post again when I'm done (expected to take about 15 to 20 minutes). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 14:15:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by hub.freebsd.org (Postfix) with SMTP id 911FA37B41A for ; Sun, 17 Feb 2002 14:15:45 -0800 (PST) Received: (qmail 14911 invoked by uid 0); 17 Feb 2002 22:15:43 -0000 Received: from pd950a5a1.dip.t-dialin.net (HELO gmx.net) (217.80.165.161) by mail.gmx.net (mp008-rz3) with SMTP; 17 Feb 2002 22:15:43 -0000 Message-ID: <3C702B93.40601@gmx.net> Date: Sun, 17 Feb 2002 23:15:47 +0100 From: Michael Nottebrock User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.8) Gecko/20020204 X-Accept-Language: en-us MIME-Version: 1.0 To: whoever Cc: freebsd-current@FreeBSD.ORG Subject: Re: Witness and rpm References: <20020213112650.A3310@kashmir.etowns.net> <3C6AC2E5.9040203@gmx.net> <20020216192452.A6688@kashmir.etowns.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG whoever wrote: > Sorry work kept me from getting back to you immediately > following is the error i am getting .... > i cvsuped the src on February 7th > > > --------Version of my vfs_syscall > $FreeBSD: src/sys/kern/vfs_syscalls.c,v 1.220 2002/02/01 18:27:16 alfred Exp Are you sure you actually built and installed the world & kernel after you cvsup'd? -- Michael Nottebrock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 14:25:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (dhcp45-21.dis.org [216.240.45.21]) by hub.freebsd.org (Postfix) with ESMTP id 9B23637B41A for ; Sun, 17 Feb 2002 14:25:36 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.6) with ESMTP id g1HMPKA01422; Sun, 17 Feb 2002 14:25:20 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200202172225.g1HMPKA01422@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Poul-Henning Kamp Cc: Matthew Dillon , Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? In-reply-to: Your message of "Sun, 17 Feb 2002 21:22:07 +0100." <5781.1013977327@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Feb 2002 14:25:20 -0800 From: Michael Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > If this patch cures the PIIX problem, something I'm not at all convinced > about, it should go in, if not only the comment should go in. I would like to see "the PIIX problem" caught on camera, personally. We're aware of one errata for it already, and we work around it. If there's another problem, or ideally if someone has some relatively quick code to test it, that would be much better. -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 14:34:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id 64BEC37B416 for ; Sun, 17 Feb 2002 14:34:43 -0800 (PST) Received: from horsey.gshapiro.net (gshapiro@localhost [IPv6:::1]) by horsey.gshapiro.net (8.12.2/8.12.3.PreAlpha0) with ESMTP id g1HMYgku027058 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 17 Feb 2002 14:34:43 -0800 (PST) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.12.2/8.12.2/Submit) id g1HMYg9s027055; Sun, 17 Feb 2002 14:34:42 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15472.12290.384976.430745@horsey.gshapiro.net> Date: Sun, 17 Feb 2002 14:34:42 -0800 From: Gregory Neil Shapiro To: freebsd-current@FreeBSD.ORG Subject: Re: HEADS UP: Expect buildworld instability In-Reply-To: <15472.9898.868296.694584@horsey.gshapiro.net> References: <15472.9898.868296.694584@horsey.gshapiro.net> X-Mailer: VM 7.00 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG gshapiro> I'm about to begin the import of sendmail 8.12.2 into -CURRENT. gshapiro> While I am doing the important, it's likely that a buildworld gshapiro> will fail. I'll post again when I'm done (expected to take about gshapiro> 15 to 20 minutes). The import and infrastructure commits are complete. buildworld should be back to normal (I'm doing to a test run on a fresh checkout to be sure). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 14:39:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id CC6F437B405; Sun, 17 Feb 2002 14:39:02 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1HMd2r94356; Sun, 17 Feb 2002 14:39:02 -0800 (PST) (envelope-from dillon) Date: Sun, 17 Feb 2002 14:39:02 -0800 (PST) From: Matthew Dillon Message-Id: <200202172239.g1HMd2r94356@apollo.backplane.com> To: Michael Smith Cc: Poul-Henning Kamp , Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? References: <200202172225.g1HMPKA01422@mass.dis.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :I would like to see "the PIIX problem" caught on camera, personally. :We're aware of one errata for it already, and we work around it. If :there's another problem, or ideally if someone has some relatively quick :code to test it, that would be much better. If the _safe version works I'll reinstrument the code to catch and print the problem counter values. Is the ACPI on a 16 or 32 bit bus? Idiot chip designers have made 'non-atomic counter carry' bugs endemic in the PC world. The standard solution is to just read the counter twice and and loop if the top 17 bits have changed in order to avoid the carry problem entirely. Something like this: u_int32_t u1; u_int32_t u2; u1 = TIMER_READ; u2 = TIMER_READ; while ((u1 ^ u2) & 0xFFFF8000) { u1 = u2; u2 = TIMER_READ; } return(u2); The solution you have in there will theoretically work as long as the 16-bit carry itself is synchronized (which it probably is), but it should be possible to do it with only two timer reads in the best-case instead of three. I'll investigate further. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 15:18: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4ABDF37B404; Sun, 17 Feb 2002 15:18:01 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1HNI1I02804; Sun, 17 Feb 2002 15:18:01 -0800 (PST) (envelope-from dillon) Date: Sun, 17 Feb 2002 15:18:01 -0800 (PST) From: Matthew Dillon Message-Id: <200202172318.g1HNI1I02804@apollo.backplane.com> To: Michael Smith Cc: Poul-Henning Kamp , Bruce Evans , freebsd-current@FreeBSD.ORG Subject: ACPI timer is screwed... (was Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? ) References: <200202172225.g1HMPKA01422@mass.dis.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :I would like to see "the PIIX problem" caught on camera, personally. :We're aware of one errata for it already, and we work around it. If :there's another problem, or ideally if someone has some relatively quick :code to test it, that would be much better. Holy shit. We are screwed. It's a free-running counter with NO synchronization whatsoever. None. Zip. Zero. ACPI TIMER LSB MISREAD 128ababd 128abaa2 128abaa4 ACPI TIMER LSB MISREAD 128ea0cd 128ea0c9 128ea0cb ACPI TIMER LSB MISREAD 129427fd 129425ff 12942801 So, for example: ABD AA2 AA4 ABD 101010111101 ^ probably should be a 0 AA2 101010100010 AA2 101010100100 Another example: 0CD 0C9 0CB 0CD 000011001101 ^ probably should be a 0 0C9 000011001001 0CB 000011001011 It looks like the hardware is using an adder with fast carry (basically a forward looking carry calculation), which can result in a later bit being set before the earlier bits are updated. However, if this is the case then it is almost certain that you can catch the ripple as well, or even catch the counter while the bit states are changing. The only way to get a guarenteed accurate sample under these circumstances is something like this, where you calculate a mask that results in reasonable accurancy without causing the cpu to go into an infinite loop and then read the timer until you get two samples that are the same: u1 = TIMER_READ; u2 = TIMER_READ; while ((u1 ^ u2) & 0xFFFFFFF0) { <<<<<<<< mask must be chosen u1 = u2; u2 = TIMER_READ; } return(u2 & 0xFFFFFFF0) <<<<<<<< same mask here Here are some more from my debug output: ACPI TIMER LSB MISREAD 2cb0f97d 2cb0f961 2cb0f963 ACPI TIMER LSB MISREAD 2fad1ced 2fad1ce9 2fad1ceb ACPI TIMER LSB MISREAD 33ed26ff 33ed2681 33ed2683 ACPI TIMER LSB MISREAD 34184d1d 34184d19 34184d1c ACPI TIMER LSB MISREAD 344516ff 344516e1 344516e3 ACPI TIMER LSB MISREAD 392b2c6d 392b2c69 392b2c6b ACPI TIMER LSB MISREAD 39c9073d 39c90739 39c9073b ACPI TIMER LSB MISREAD 39f3161d 39f3161a 39f3161c ACPI TIMER LSB MISREAD 3ad04bbf 3ad04bb1 3ad04bb3 ACPI TIMER LSB MISREAD 39f3161d 39f3161a 39f3161c -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 15:28:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (dhcp45-21.dis.org [216.240.45.21]) by hub.freebsd.org (Postfix) with ESMTP id B264337B402; Sun, 17 Feb 2002 15:28:07 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.6) with ESMTP id g1HNRuA01838; Sun, 17 Feb 2002 15:27:56 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200202172327.g1HNRuA01838@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Matthew Dillon Cc: Michael Smith , Poul-Henning Kamp , Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: ACPI timer is screwed... (was Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? ) In-reply-to: Your message of "Sun, 17 Feb 2002 15:18:01 PST." <200202172318.g1HNI1I02804@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Feb 2002 15:27:56 -0800 From: Michael Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > :I would like to see "the PIIX problem" caught on camera, personally. > :We're aware of one errata for it already, and we work around it. If > :there's another problem, or ideally if someone has some relatively quick > :code to test it, that would be much better. > > Holy shit. We are screwed. It's a free-running counter with NO > synchronization whatsoever. None. Zip. Zero. Sounds like we need to smack whoever made your chipset as well. Intel learned their lesson (finally) with later revisions of the PIIX4. I'm guessing you're running this against a ServerWorks system. > It looks like the hardware is using an adder with fast carry > (basically a forward looking carry calculation), which can result in a > later bit being set before the earlier bits are updated. However, if > this is the case then it is almost certain that you can catch the ripple > as well, or even catch the counter while the bit states are changing. Lame. Incredibly lame. > The only way to get a guarenteed accurate sample under these circumstances > is something like this, where you calculate a mask that results in > reasonable accurancy without causing the cpu to go into an infinite > loop and then read the timer until you get two samples that are the same: > > u1 = TIMER_READ; > u2 = TIMER_READ; > while ((u1 ^ u2) & 0xFFFFFFF0) { <<<<<<<< mask must be chosen > u1 = u2; > u2 = TIMER_READ; > } > return(u2 & 0xFFFFFFF0) <<<<<<<< same mask here > > Here are some more from my debug output: Interesting. This would be reasonably robust in the ripple-counter case we have to deal with on the old PIIX4. Have you tried implementing the above yet, or measuring how much it costs? At any rate, please let me know for sure whether you're running on a ServerWorks board, and I'll see if I can't find a Big Stick to hit them with. Thanks, Mike -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 15:34: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id E3B2337B400; Sun, 17 Feb 2002 15:33:56 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1HNXuh07529; Sun, 17 Feb 2002 15:33:56 -0800 (PST) (envelope-from dillon) Date: Sun, 17 Feb 2002 15:33:56 -0800 (PST) From: Matthew Dillon Message-Id: <200202172333.g1HNXuh07529@apollo.backplane.com> To: Michael Smith Cc: Poul-Henning Kamp , Bruce Evans , freebsd-current@FreeBSD.ORG Subject: ACPI patch (was Re: 'microuptime() went backwards ...' using ACPI...) References: <200202172225.g1HMPKA01422@mass.dis.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ok, here is a patch that executes a brute-force solution to the asynchronous counter problem. Basically it figures out a mask and then the timer code loops until two masked reads yield the same value, guarenteeing that we haven't caught the timer during a carry. On my system, the mask I got was: 0xFFFFFFFC which means I lost only 2 bits of accuracy in order to be able to retrieve accurate counter values. This gives my particular box an approximately 1uS accuracy. I think this may be the only safe way to do it. It looks like it is possible to catch the ripple and/or fast-carry on *any* bit, with the statistical chance of it occuring on higher bits dropping by 2x per bit. My proposed (tested) patch is below. Mike? acpi_timer0: <32-bit timer at 3.579545MHz mask fffffffc> port 0x808-0x80b on acpi0 -Matt Index: acpi_timer.c =================================================================== RCS file: /home/ncvs/src/sys/dev/acpica/acpi_timer.c,v retrieving revision 1.11 diff -u -r1.11 acpi_timer.c --- acpi_timer.c 8 Jan 2002 06:45:56 -0000 1.11 +++ acpi_timer.c 17 Feb 2002 23:26:29 -0000 @@ -56,6 +56,7 @@ MODULE_NAME("TIMER") static device_t acpi_timer_dev; +static u_int32_t acpi_timer_mask; struct resource *acpi_timer_reg; #define TIMER_READ bus_space_read_4(rman_get_bustag(acpi_timer_reg), \ rman_get_bushandle(acpi_timer_reg), \ @@ -113,7 +114,7 @@ acpi_timer_identify(driver_t *driver, device_t parent) { device_t dev; - char desc[40]; + char desc[48]; int rid; FUNCTION_TRACE(__func__); @@ -138,14 +139,32 @@ if (getenv("debug.acpi.timer_test") != NULL) acpi_timer_test(); - acpi_timer_timecounter.tc_get_timecount = acpi_timer_get_timecount; + acpi_timer_timecounter.tc_get_timecount = acpi_timer_get_timecount_safe; acpi_timer_timecounter.tc_frequency = acpi_timer_frequency; tc_init(&acpi_timer_timecounter); - sprintf(desc, "%d-bit timer at 3.579545MHz", AcpiGbl_FADT->TmrValExt ? 32 : 24); + for (acpi_timer_mask = 0xFFFFFFFF; acpi_timer_mask; acpi_timer_mask <<= 1) { + u_int32_t u1; + u_int32_t u2; + int count = 10; + + u1 = TIMER_READ; + u2 = TIMER_READ; + while (count && ((u1 ^ u2) & acpi_timer_mask)) { + u1 = u2; + u2 = TIMER_READ; + --count; + } + if (count) + break; + } + acpi_timer_mask <<= 1; + + sprintf(desc, "%d-bit timer at 3.579545MHz mask %08x", + (AcpiGbl_FADT->TmrValExt ? 32 : 24), acpi_timer_mask); device_set_desc_copy(dev, desc); -#if 0 +#if 0 { u_int64_t first; @@ -192,16 +211,22 @@ static unsigned acpi_timer_get_timecount_safe(struct timecounter *tc) { - unsigned u1, u2, u3; + u_int32_t u1; + u_int32_t u2; + u1 = TIMER_READ; u2 = TIMER_READ; - u3 = TIMER_READ; - do { + while ((u1 ^ u2) & acpi_timer_mask) { u1 = u2; - u2 = u3; - u3 = TIMER_READ; - } while (u1 > u2 || u2 > u3); - return (u2); + u2 = TIMER_READ; + } +#if 0 /* DEBUGGING */ + if (u2 < u1) { + u_int32_t u3 = TIMER_READ; + printf("ACPI TIMER LSB MISREAD %08x %08x %08x\n", u1, u2, u3); + } +#endif + return(u2 & acpi_timer_mask); } /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 15:37:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3C5B137B47B; Sun, 17 Feb 2002 15:36:56 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1HNaup07553; Sun, 17 Feb 2002 15:36:56 -0800 (PST) (envelope-from dillon) Date: Sun, 17 Feb 2002 15:36:56 -0800 (PST) From: Matthew Dillon Message-Id: <200202172336.g1HNaup07553@apollo.backplane.com> To: Michael Smith Cc: Michael Smith , Poul-Henning Kamp , Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: ACPI timer is screwed... (was Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? ) References: <200202172327.g1HNRuA01838@mass.dis.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Sounds like we need to smack whoever made your chipset as well. Intel :learned their lesson (finally) with later revisions of the PIIX4. I'm :guessing you're running this against a ServerWorks system. atapci0: port 0x8b0-0x8bf at device 15.1 on pci0 Uh huh. It might be possible to detect the situation during init-time by explicitly looking for a reverse indexed time in a tight loop of maybe a thousand reads, but that would still leave us with a statistical chance of not guessing right. :Interesting. This would be reasonably robust in the ripple-counter case :we have to deal with on the old PIIX4. Have you tried implementing the :above yet, or measuring how much it costs? : :At any rate, please let me know for sure whether you're running on a :ServerWorks board, and I'll see if I can't find a Big Stick to hit them :with. : :Thanks, :Mike I haven't measured the cost (extra loops) but I expect it would stabilize in no more then one additional loop, which would be three counter reads total or roughly the same as your originaln _safe code in the worst case. I think we could default to the _safe version and then explicitly change it to use the fast version if we see specific chipsets which we know to be good. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 15:48:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 0B08D37B405; Sun, 17 Feb 2002 15:48:31 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g1HNjTN28246; Mon, 18 Feb 2002 00:45:29 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Michael Smith , Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: ACPI timer is screwed... (was Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? ) In-Reply-To: Your message of "Sun, 17 Feb 2002 15:18:01 PST." <200202172318.g1HNI1I02804@apollo.backplane.com> Date: Mon, 18 Feb 2002 00:45:29 +0100 Message-ID: <28244.1013989529@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200202172318.g1HNI1I02804@apollo.backplane.com>, Matthew Dillon wri tes: > >:I would like to see "the PIIX problem" caught on camera, personally. >:We're aware of one errata for it already, and we work around it. If >:there's another problem, or ideally if someone has some relatively quick >:code to test it, that would be much better. > > Holy shit. We are screwed. It's a free-running counter with NO > synchronization whatsoever. None. Zip. Zero. Yes, there is an errata for just that on early chipsets. Does the ..._slow patch I sent work for you ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 15:49:44 2002 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (dhcp45-21.dis.org [216.240.45.21]) by hub.freebsd.org (Postfix) with ESMTP id 1CA0937B400; Sun, 17 Feb 2002 15:49:42 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.6) with ESMTP id g1HNnWA01995; Sun, 17 Feb 2002 15:49:32 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200202172349.g1HNnWA01995@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Matthew Dillon Cc: Michael Smith , Poul-Henning Kamp , Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: ACPI patch (was Re: 'microuptime() went backwards ...' using ACPI...) In-reply-to: Your message of "Sun, 17 Feb 2002 15:33:56 PST." <200202172333.g1HNXuh07529@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Feb 2002 15:49:32 -0800 From: Michael Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Ok, here is a patch that executes a brute-force solution to the > asynchronous counter problem. > > Basically it figures out a mask and then the timer code loops until two > masked reads yield the same value, guarenteeing that we haven't caught > the timer during a carry. > > On my system, the mask I got was: 0xFFFFFFFC which means I lost only 2 > bits of accuracy in order to be able to retrieve accurate counter values. > This gives my particular box an approximately 1uS accuracy. > > I think this may be the only safe way to do it. It looks like it is > possible to catch the ripple and/or fast-carry on *any* bit, with the > statistical chance of it occuring on higher bits dropping by 2x per bit. > > My proposed (tested) patch is below. Mike? I have some reservations about this, because I'm not sure that 10 successive reads will catch the ripple-counter problem that the old PIIX4s have. I think that if this code detects a need for the mask technique, it should set the handler to a function that will deal with the mask. If it doesn't, it should assume that we need the 'safe' function as it currently exists (I'm not sure why it's not the default, unless there's a log message to explain it, it must have been a mistake on my part). I'd also like to see the description include the number of bits, rather than the mask, if we are using a mask. Thanks for taking the time to track this one down. -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 15:51:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id 2AB3F37B400 for ; Sun, 17 Feb 2002 15:51:35 -0800 (PST) Received: from horsey.gshapiro.net (gshapiro@localhost [IPv6:::1]) by horsey.gshapiro.net (8.12.2/8.12.3.PreAlpha0) with ESMTP id g1HNpYku028249 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 17 Feb 2002 15:51:34 -0800 (PST) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.12.2/8.12.2/Submit) id g1HNpY2d028246; Sun, 17 Feb 2002 15:51:34 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15472.16902.218983.970624@horsey.gshapiro.net> Date: Sun, 17 Feb 2002 15:51:34 -0800 From: Gregory Neil Shapiro To: freebsd-current@freebsd.org Subject: HEADS UP: sendmail 8.12.2 imported X-Mailer: VM 7.00 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG sendmail 8.12.2 has been imported into -CURRENT. sendmail 8.12 has been developed with two main topics in mind: enhanced security and better performance. sendmail is by default not set-user-ID root anymore which avoids potential local root exploits. See /etc/mail/README (after running mergemaster) for information about possible gotchas with this new version. For more information about the new functionality in 8.12, visit: http://www.sendmail.org/8.12.0.html /usr/src/contrib/sendmail/RELEASE_NOTES and /usr/src/contrib/sendmail/src/SECURITY may also be of interest. Finally, the default /etc/mail/sendmail.cf (based on /usr/src/etc/sendmail/freebsd.mc) no longer uses FEATURE(`relay_based_on_MX'). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 15:53:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (dhcp45-21.dis.org [216.240.45.21]) by hub.freebsd.org (Postfix) with ESMTP id 2C14737B416; Sun, 17 Feb 2002 15:53:14 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.6) with ESMTP id g1HNr3A02051; Sun, 17 Feb 2002 15:53:03 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200202172353.g1HNr3A02051@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Poul-Henning Kamp Cc: Matthew Dillon , Michael Smith , Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: ACPI timer is screwed... (was Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? ) In-reply-to: Your message of "Mon, 18 Feb 2002 00:45:29 +0100." <28244.1013989529@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Feb 2002 15:53:03 -0800 From: Michael Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > >:I would like to see "the PIIX problem" caught on camera, personally. > >:We're aware of one errata for it already, and we work around it. If > >:there's another problem, or ideally if someone has some relatively quick > >:code to test it, that would be much better. > > > > Holy shit. We are screwed. It's a free-running counter with NO > > synchronization whatsoever. None. Zip. Zero. > > Yes, there is an errata for just that on early chipsets. > > Does the ..._slow patch I sent work for you ? Matt's problem (look-ahead carry) will break the three-read algorithm because it can generate a sequence of three reads that appear to be in succession, but which are all wrong. We need three different algorithms; "works", "ripple" and "look-ahead". Of those, "works" should be based exclusively off a list of known-good chipsets, "look-ahead" seems to be easily enough detected (but we should probably have a blacklist anyway) and "ripple" is hard to detect and should be the default case. I really, really hate hardware. -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 15:54:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id E32ED37B400; Sun, 17 Feb 2002 15:54:06 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1HNs6407707; Sun, 17 Feb 2002 15:54:06 -0800 (PST) (envelope-from dillon) Date: Sun, 17 Feb 2002 15:54:06 -0800 (PST) From: Matthew Dillon Message-Id: <200202172354.g1HNs6407707@apollo.backplane.com> To: Michael Smith Cc: Poul-Henning Kamp , Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: ACPI patch (was Re: 'microuptime() went backwards ...' using ACPI...) References: <200202172349.g1HNnWA01995@mass.dis.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :I have some reservations about this, because I'm not sure that 10 :successive reads will catch the ripple-counter problem that the old PIIX4s :have. Just goes to show that I need to document my code :-) Those reads are not detecting the ripple-counter problem, they are figuring out the mask required to guarentee that two successive reads will return the same counter value so the counter read in the later code doesn't end up in an infinite loop. i.e. on a slow cpu the mask might have to remove more bits because the counter increments a number of times between reads. On a fast cpu, fewer bits would have to be chopped off. That's all. :I'd also like to see the description include the number of bits, rather :than the mask, if we are using a mask. : :Thanks for taking the time to track this one down. Well, I don't want to spend too much time on it because this was incidental to other work I'm doing on -current. If you think it's worth comitting I'll commit it, otherwise you can use it as a template for your own fix/commit. It would be nice if some sort of solution were comitted to the tree relatively soon. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 16:21: 3 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 1A69237B427 for ; Sun, 17 Feb 2002 16:20:25 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id LAA08787; Mon, 18 Feb 2002 11:20:17 +1100 Date: Mon, 18 Feb 2002 11:20:17 +1100 (EST) From: Bruce Evans X-X-Sender: To: Poul-Henning Kamp Cc: Matthew Dillon , Subject: Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? In-Reply-To: <5680.1013977074@critter.freebsd.dk> Message-ID: <20020218111106.V3970-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 17 Feb 2002, Poul-Henning Kamp wrote: > In message <20020217184436.M934-100000@gamplex.bde.org>, Bruce Evans writes: > > >> This occurs both with and without the gettimeofday Giant-removal patch, so > >> I am fairly sure it has nothing to do with any of my current work. This is > >> running -current on a DELL2550 (2xCPUs), compiled with the SMP option. > > The Gian removal doesn't come anywhere near this. Yes it did. There were Giants in the path for all syscalls. > >The fact that the timecounter usually goes backwards by about 0.68 seconds > >is probably significant, but I can't quite explain it. > > >> acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > > Well: > 2^32 / 3579545 = 1199.86 seconds. > 2^24 / 3579545 = 4.68 seconds. > > So even assuming that ACPI reported a wrong width, four seconds should > still be enough to prevent a wraparound even though we cycle through > the timecounter ring in one second. No, there is only one seconds worth of of wraparaond, because recent changes annulled the slightly less recent fixes for loss of nanoseconds above the first 10^9 of them. Previously, the multiplication corresponding to the one in binuptime() overflowed at 2^32 nsec. Now it overflows at 2^64 in units of 2^-64 seconds. > >I just wrote the following fix for some of the overflow problems. > > It is true that if a process is not running for arbitrary long time > the timecounter may be modified underneat it, and bruce's patch is > actually a pretty elegant solution for that case. By all means > try it. Thanks :-). In other mail you said "it pessimize the timecounters elegant lockless design a fair bit". Here the fair bit only applies to the elegance. The pessimization at runtime is tiny. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 16:27:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 11BB937B425 for ; Sun, 17 Feb 2002 16:26:59 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id LAA09636; Mon, 18 Feb 2002 11:26:55 +1100 Date: Mon, 18 Feb 2002 11:26:54 +1100 (EST) From: Bruce Evans X-X-Sender: To: Matthew Dillon Cc: Subject: Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? In-Reply-To: <200202172025.g1HKPc589840@apollo.backplane.com> Message-ID: <20020218112157.F3970-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 17 Feb 2002, Matthew Dillon wrote: > Ok, I've looked at the code more carefully and I understand how this > works now. However, it is not enough in an SMP environment. You > need a generation count in the timecounter structure and you also need > a synchronization point when you switch time counters or a process > running on a different cpu may wind up using a time counter that is being > actively updated. Er, the comment in patch says it needs a generation count. Unfortunately, we only have half a synchronization point now -- there is a sched_lock() in the update code but nothing in the code that reads the pointer. Maybe a large value of NTIMECOUNTER would help after all. We can afford to o miss a few timecounter changes if we have a lot of timecounter states. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 16:52:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 7B51437B400 for ; Sun, 17 Feb 2002 16:52:40 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id LAA12778; Mon, 18 Feb 2002 11:52:27 +1100 Date: Mon, 18 Feb 2002 11:52:26 +1100 (EST) From: Bruce Evans X-X-Sender: To: Matthew Dillon Cc: Poul-Henning Kamp , Subject: Re: Success! Sorta! (was Re: 'microuptime() went backwards ...' using ACPI timer. Shouldn't that be impossible? ) In-Reply-To: <200202172042.g1HKgs691210@apollo.backplane.com> Message-ID: <20020218114754.M4061-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 17 Feb 2002, Matthew Dillon wrote: > Whoop! I take it back. I'm still getting the errors: > > microuptime() went backwards (458.168990 -> 458.168882) > microuptime() went backwards (578.609995 -> 577.929801) > microuptime() went backwards (748.912755 -> 748.237402) > microuptime() went backwards (775.159625 -> 775.159612) > > I also think this retry loop has to be done everywhere where the > timecounter structure is accessed directly. Yes, since the reads of all the relevant timecounter variables are non-atomic. > Index: kern/kern_tc.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/kern_tc.c,v > retrieving revision 1.113 > diff -u -r1.113 kern_tc.c > --- kern/kern_tc.c 7 Feb 2002 21:21:55 -0000 1.113 > +++ kern/kern_tc.c 17 Feb 2002 20:41:47 -0000 > @@ -126,8 +128,10 @@ > struct timecounter *tc; > > ngetmicrotime++; > - tc = timecounter; > - *tvp = tc->tc_microtime; > + do { > + tc = timecounter; > + *tvp = tc->tc_microtime; > + } while (tc != timecounter); > } > > void E.g., tc_mictrotime here is a timeval. It doesn't matter getting a stale value (although getting a stale value increases the possible incoherency of the get*() functions from 1/HZ to NTIMECOUNTER/HZ), but getting a stale value that changed underneath the read would be bad. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 17:44: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from outboundx.mv.meer.net (outboundx.mv.meer.net [209.157.152.12]) by hub.freebsd.org (Postfix) with ESMTP id 0F16D37B404 for ; Sun, 17 Feb 2002 17:44:06 -0800 (PST) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by outboundx.mv.meer.net (8.11.6/8.11.6) with ESMTP id g1I1i2s96836 for ; Sun, 17 Feb 2002 17:44:02 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from neville-neil.com ([209.157.133.226]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id RAA266778 for ; Sun, 17 Feb 2002 17:43:55 -0800 (PST) Message-Id: <200202180143.RAA266778@meer.meer.net> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: freebsd-current@freebsd.org Subject: A quick, dumb, question... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Feb 2002 17:43:55 -0800 From: "George V. Neville-Neil" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is there a single document, or small set of documents, that describes getting started kernel hacking on FreeBSD? How about a set of URLs? I would like something that tells me about (in no particular order) 1) debugging over the serial line, and remote debugging in general 2) Building for 5.0 on 4.x (if possible though I suspect I should not do this) 3) Best practices for dealing with my own versions of files while also working with cvsup. Those are a good start for now. BTW If none exists I will try to write this up in the form of a tutorial and post it at some point. Thanks, George -- George V. Neville-Neil gnn@neville-neil.com NIC:GN82 "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 17:55:33 2002 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 9998037B404 for ; Sun, 17 Feb 2002 17:55:30 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id g1I1tUR59205; Sun, 17 Feb 2002 17:55:30 -0800 (PST) (envelope-from david) Date: Sun, 17 Feb 2002 17:55:30 -0800 (PST) From: David Wolfskill Message-Id: <200202180155.g1I1tUR59205@bunrab.catwhisker.org> To: gnn@neville-neil.com Subject: Re: A quick, dumb, question... Cc: current@freebsd.org In-Reply-To: <200202180143.RAA266778@meer.meer.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Date: Sun, 17 Feb 2002 17:43:55 -0800 >From: "George V. Neville-Neil" >Is there a single document, or small set of documents, that describes getting >started kernel hacking on FreeBSD? How about a set of URLs? >I would like something that tells me about (in no particular order) >1) debugging over the serial line, and remote debugging in general You might start with http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html. (Sorry about the line-wrapping.) >2) Building for 5.0 on 4.x (if possible though I suspect I should not do this) Sure: set up a 4.x system, clear /usr/src, populate /usr/src with the HEAD of the tree ("cvs co"), then follow the instructions in /usr/src/UPDATING. >3) Best practices for dealing with my own versions of files while also >working with cvsup. What I do is use CVSup to mirror the CVS repository (vs. a "working directory"), then use "cvs update" (well, after an initial "cvs co") to update the sources. I do this within "script", so I get a record of what was done, and I can grep the "typescript" file for various weirdnesses, such as conflicts to be resolved. (I also do the "make buildworld" & friends under script, so if something weird happens during the build, I don't need to record it: that's been done. Well, if it's a panic, that may not capture everything -- but a serial console can be helpful in that case.) (I've been tracking both -STABLE and -CURRENT daily, on each of a "build machine" and my laptop, for several months. I've also been testing patches for folks, so being able to revert patches or generate new ones is a definite advantage of having the CVS repository handy.) >Those are a good start for now. Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 18:48: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from theinternet.com.au (c20631.kelvn1.qld.optusnet.com.au [203.164.207.8]) by hub.freebsd.org (Postfix) with ESMTP id E47EB37B405 for ; Sun, 17 Feb 2002 18:48:03 -0800 (PST) Received: (from akm@localhost) by theinternet.com.au (8.11.6/8.11.4) id g1I2lJT12293; Mon, 18 Feb 2002 12:47:19 +1000 (EST) (envelope-from akm) Date: Mon, 18 Feb 2002 12:47:19 +1000 From: Andrew Kenneth Milton To: Joerg Wunsch Cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD unfinished NIS+ implementation in Linux ? Message-ID: <20020218124719.K90065@zeus.theinternet.com.au> References: <20020217161648.W17787-100000@levais.imp.ch> <200202172007.g1HK7Tl25937@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200202172007.g1HK7Tl25937@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Sun, Feb 17, 2002 at 09:07:29PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG +-------[ Joerg Wunsch ]---------------------- | Martin Blapp wrote: | | > Suse's Copyright: | > | > /* Copyright (c) 1999 Thorsten Kukuk | > Author: Thorsten Kukuk | | That would at least be a copyright violation. Not necessarily, some derived works are entitled to copyright protection in their own right, hard to prove you've changed it enough to get that though. Unauthorised relicensing of the invididual parts is a copyright violation, it's legal to contain BSDL code in a larger GPL'd work. The contained code still retains the original copyright and license. There is unfortunately a section of the GPL community who confuses this with the right to simply relicense BSDL code whenever you want, because it doesn't explicitly deny it. The FSF 'GPL compatible' licenses page makes this even more confusing (IMO). If you want to stop your BSDL code being used in GPL projects (not sure why you would want to), stick the advertising clause in, this then makes the BSDL GPL incompatible (according to the FSF). -- Totally Holistic Enterprises Internet| | Andrew Milton The Internet (Aust) Pty Ltd | | ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 18:49:55 2002 Delivered-To: freebsd-current@freebsd.org Received: from kashmir.etowns.net (dsl-65-184-96-65.telocity.com [65.184.96.65]) by hub.freebsd.org (Postfix) with ESMTP id E11A037B400 for ; Sun, 17 Feb 2002 18:49:52 -0800 (PST) Received: (from somebody@localhost) by kashmir.etowns.net (8.11.6/8.11.6) id g1I0o9800744; Sun, 17 Feb 2002 16:50:09 -0800 (PST) (envelope-from somebody) Date: Sun, 17 Feb 2002 16:50:09 -0800 From: whoever To: Michael Nottebrock Cc: freebsd-current@FreeBSD.ORG Subject: Re: Witness and rpm Message-ID: <20020217165009.A613@kashmir.etowns.net> References: <20020213112650.A3310@kashmir.etowns.net> <3C6AC2E5.9040203@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C6AC2E5.9040203@gmx.net>; from michaelnottebrock@gmx.net on Wed, Feb 13, 2002 at 08:47:49PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG |whoever wrote: | |> Sorry work kept me from getting back to you immediately |> following is the error i am getting .... |> i cvsuped the src on February 7th | > |> > --------Version of my vfs_syscall |> $FreeBSD: src/sys/kern/vfs_syscalls.c,v 1.220 2002/02/01 18:27:16 alfred Exp | |Are you sure you actually built and installed the world & kernel after |you cvsup'd? | |-- |Michael Nottebrock absolutely. I just checked again the kernel causing this trouble was built after cvsuping. And I am pretty sure I did the make world after cvsupping too. I dont know how to check for that though. Just out of curiosity should make world matter in this instance. is the said file used by some libraries also? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 20:17:44 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by hub.freebsd.org (Postfix) with SMTP id 400A137B404 for ; Sun, 17 Feb 2002 20:17:40 -0800 (PST) Received: (qmail 26741 invoked by uid 0); 18 Feb 2002 04:17:38 -0000 Received: from pd950a5a1.dip.t-dialin.net (HELO gmx.net) (217.80.165.161) by mail.gmx.net (mp013-rz3) with SMTP; 18 Feb 2002 04:17:38 -0000 Message-ID: <3C708068.8030507@gmx.net> Date: Mon, 18 Feb 2002 05:17:44 +0100 From: Michael Nottebrock User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.8) Gecko/20020204 X-Accept-Language: en-us MIME-Version: 1.0 To: whoever Cc: freebsd-current@FreeBSD.ORG Subject: Re: Witness and rpm References: <20020213112650.A3310@kashmir.etowns.net> <3C6AC2E5.9040203@gmx.net> <20020217165009.A613@kashmir.etowns.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG whoever wrote: > absolutely. > I just checked again the kernel causing this trouble was built after > cvsuping. And I am pretty sure I did the make world after > cvsupping too. I dont know how to check for that though. > Just out of curiosity should make world matter > in this instance. is the said file used by some libraries also? I just asked because I can't reproduce this anymore (I cvsup'd some six hours ago, rebuilt everything, with invariants and witness on, I even tried it with the port you reported, plus erasing and adding a few other random rpms). You might want to try cvsup'ing and updating everything again, make sure you are actually running the new kernel, and, if the problem persists, get a trace of the panic and report it to the mailing list. -- Michael Nottebrock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 22: 7:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 3437337B402; Sun, 17 Feb 2002 22:07:37 -0800 (PST) Received: from peter3.wemm.org ([12.232.27.13]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020218060736.SIAD2951.rwcrmhc53.attbi.com@peter3.wemm.org>; Mon, 18 Feb 2002 06:07:36 +0000 Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id g1I67Ys31455; Sun, 17 Feb 2002 22:07:34 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (Postfix) with ESMTP id 314FE3809; Sun, 17 Feb 2002 22:07:34 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: alpha@freebsd.org, current@freebsd.org Subject: OK, who broke alpha this time? :-/ Date: Sun, 17 Feb 2002 22:07:34 -0800 From: Peter Wemm Message-Id: <20020218060734.314FE3809@overcee.wemm.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ... sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A, console sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "i8254" frequency 1193182 Hz ata0-slave: timeout waiting for interrupt ata0-slave: ATAPI identify failed acd0: CDROM at ata0-master PIO4 Waiting 2 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) ^T load: 0.16 cmd: init 8 [inode] 0.00u 0.00s 0% 416k ^T load: 0.16 cmd: init 8 [inode] 0.00u 0.00s 0% 416k [forever] http://people.freebsd.org/~peter/alphadmesg.txt It seems that locking has been hosed somehow. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 22:36:58 2002 Delivered-To: freebsd-current@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id A512D37B402; Sun, 17 Feb 2002 22:36:52 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.6/8.11.6) with UUCP id g1I6aoZ15280; Mon, 18 Feb 2002 07:36:50 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g1I6aXeS026545; Mon, 18 Feb 2002 07:36:34 +0100 (CET)?g (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.6/8.11.6) id g1I6aXI45201; Mon, 18 Feb 2002 07:36:33 +0100 (CET) (envelope-from ticso) Date: Mon, 18 Feb 2002 07:36:33 +0100 From: Bernd Walter To: Peter Wemm Cc: alpha@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: OK, who broke alpha this time? :-/ Message-ID: <20020218063632.GA44861@cicely8.cicely.de> References: <20020218060734.314FE3809@overcee.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020218060734.314FE3809@overcee.wemm.org> User-Agent: Mutt/1.3.26i X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Feb 17, 2002 at 10:07:34PM -0800, Peter Wemm wrote: > ... > sio0 at port 0x3f8-0x3ff irq 4 on isa0 > sio0: type 16550A, console > sio0: interrupting at ISA irq 4 > sio1: reserved for low-level i/o > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounter "i8254" frequency 1193182 Hz > ata0-slave: timeout waiting for interrupt > ata0-slave: ATAPI identify failed > acd0: CDROM at ata0-master PIO4 > Waiting 2 seconds for SCSI devices to settle > Mounting root from ufs:/dev/da0a > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled > da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-3 device > da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled > da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) > ^T > load: 0.16 cmd: init 8 [inode] 0.00u 0.00s 0% 416k > ^T > load: 0.16 cmd: init 8 [inode] 0.00u 0.00s 0% 416k > [forever] > > http://people.freebsd.org/~peter/alphadmesg.txt > > It seems that locking has been hosed somehow. Just guessing: John Baldwin had enabled interrupt thread preemption some days ago. src/sys/alpha/alpha/interrupt.c rev 1.61 Maybe it also enabled some hidden bug. I hope to have one of my machines on -current later that day to compare. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 22:54:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 1F22737B43C for ; Sun, 17 Feb 2002 22:52:16 -0800 (PST) Received: from pool0305.cvx21-bradley.dialup.earthlink.net ([209.179.193.50] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16cheC-0004OK-00; Sun, 17 Feb 2002 22:51:36 -0800 Message-ID: <3C70A46D.41F05C21@mindspring.com> Date: Sun, 17 Feb 2002 22:51:25 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Kenneth Milton Cc: Joerg Wunsch , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD unfinished NIS+ implementation in Linux ? References: <20020217161648.W17787-100000@levais.imp.ch> <200202172007.g1HK7Tl25937@uriah.heep.sax.de> <20020218124719.K90065@zeus.theinternet.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Andrew Kenneth Milton wrote: > There is unfortunately a section of the GPL community who confuses this > with the right to simply relicense BSDL code whenever you want, because it > doesn't explicitly deny it. The FSF 'GPL compatible' licenses page makes > this even more confusing (IMO). > > If you want to stop your BSDL code being used in GPL projects (not sure > why you would want to), stick the advertising clause in, this then makes > the BSDL GPL incompatible (according to the FSF). The FSF is wrong on "compatible". No matter what license is on the code, relicensing it under a different license without the author's written permission is not legal. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 23: 8:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from theinternet.com.au (c20631.kelvn1.qld.optusnet.com.au [203.164.207.8]) by hub.freebsd.org (Postfix) with ESMTP id 91BC037B41A for ; Sun, 17 Feb 2002 23:08:30 -0800 (PST) Received: (from akm@localhost) by theinternet.com.au (8.11.6/8.11.4) id g1I787L13128; Mon, 18 Feb 2002 17:08:07 +1000 (EST) (envelope-from akm) Date: Mon, 18 Feb 2002 17:08:07 +1000 From: Andrew Kenneth Milton To: Terry Lambert Cc: Andrew Kenneth Milton , Joerg Wunsch , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD unfinished NIS+ implementation in Linux ? Message-ID: <20020218170806.M90065@zeus.theinternet.com.au> References: <20020217161648.W17787-100000@levais.imp.ch> <200202172007.g1HK7Tl25937@uriah.heep.sax.de> <20020218124719.K90065@zeus.theinternet.com.au> <3C70A46D.41F05C21@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3C70A46D.41F05C21@mindspring.com>; from tlambert2@mindspring.com on Sun, Feb 17, 2002 at 10:51:25PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG +-------[ Terry Lambert ]---------------------- | Andrew Kenneth Milton wrote: | > There is unfortunately a section of the GPL community who confuses this | > with the right to simply relicense BSDL code whenever you want, because it | > doesn't explicitly deny it. The FSF 'GPL compatible' licenses page makes | > this even more confusing (IMO). | > | > If you want to stop your BSDL code being used in GPL projects (not sure | > why you would want to), stick the advertising clause in, this then makes | > the BSDL GPL incompatible (according to the FSF). | | The FSF is wrong on "compatible". They're only right in one circumstance. Using whole slabs of BSDL code standalone as part of the GPL project, i.e. no mixing of code, the GPL forbids that (since you can't relicense other people's code). | No matter what license is on the code, relicensing it | under a different license without the author's written | permission is not legal. Relicensing isn't the same as incorporating into a larger work cf: Apple OSX is not BSDL, but contains code that is. This is the situation under which BSDL code is 'compatible' with the GPL (the license of the whole does not breech any conditions of the license of the parts). If you were to get your hands on the OSX code, you could safely and legally distribute the BSDL portions under the BSDL. Same with any GPL project using BSDL code. I don't think the GPL actually permits this either, but, the FSF are the ones who tell you what your interpretation of their license is to be. -- Totally Holistic Enterprises Internet| | Andrew Milton The Internet (Aust) Pty Ltd | | ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 17 23:36:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id ADB6137B422 for ; Sun, 17 Feb 2002 23:35:50 -0800 (PST) Received: from pool0305.cvx21-bradley.dialup.earthlink.net ([209.179.193.50] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ciKo-000795-00; Sun, 17 Feb 2002 23:35:38 -0800 Message-ID: <3C70AEC0.C56A3488@mindspring.com> Date: Sun, 17 Feb 2002 23:35:28 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Kenneth Milton Cc: Joerg Wunsch , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD unfinished NIS+ implementation in Linux ? References: <20020217161648.W17787-100000@levais.imp.ch> <200202172007.g1HK7Tl25937@uriah.heep.sax.de> <20020218124719.K90065@zeus.theinternet.com.au> <3C70A46D.41F05C21@mindspring.com> <20020218170806.M90065@zeus.theinternet.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Andrew Kenneth Milton wrote: > | The FSF is wrong on "compatible". > > They're only right in one circumstance. Using whole slabs of BSDL code > standalone as part of the GPL project, i.e. no mixing of code, the GPL > forbids that (since you can't relicense other people's code). Yes, this is actually where it's legal: to put an aggregate copyright on a set of code, rather than changing the license on an individual file or a portion thereof. This is because the license in that case is on the basis of a collection copyright, which is a different thing than a copyright on an individual work of authorship, or of a derivative work. > | No matter what license is on the code, relicensing it > | under a different license without the author's written > | permission is not legal. > > Relicensing isn't the same as incorporating into a larger work cf: Apple > OSX is not BSDL, but contains code that is. This is the situation under which > BSDL code is 'compatible' with the GPL (the license of the whole does not > breech any conditions of the license of the parts). Yes, a collection copyright. > If you were to get your hands on the OSX code, you could safely and legally > distribute the BSDL portions under the BSDL. Same with any GPL project using > BSDL code. Except in the NIS+ case, where the original license _was_ allegedly changed from BSDL to GPL. > I don't think the GPL actually permits this either, but, the FSF > are the ones who tell you what your interpretation of their license > is to be. Actually, not. It is the author who determines that... which is why the FSF requires you to execute an assignment of rights to contribute code to GCC and other FSF projects and have the code accepted, lest your interpretation of the GPL differ from theirs, and result in legal difficulties. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 3:35:46 2002 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (dhcp45-21.dis.org [216.240.45.21]) by hub.freebsd.org (Postfix) with ESMTP id BC9AF37B417 for ; Mon, 18 Feb 2002 03:35:41 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.6) with ESMTP id g1IBZXA06641; Mon, 18 Feb 2002 03:35:33 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200202181135.g1IBZXA06641@mass.dis.org> Date: Mon, 18 Feb 2002 03:35:32 -0800 From: Michael Smith Subject: 3ware 6xxx-series controllers and 6.9 firmware To: undisclosed-recipients:; Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ------- Blind-Carbon-Copy X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: stable@freebsd.org Subject: 3ware 6xxx-series controllers and 6.9 firmware Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Feb 2002 03:35:32 -0800 From: Michael Smith As several people have pointed out, the 6.9 firmware update from 3ware is causing problems with the 'twe' driver. I have a version of the driver working with the 6.9 firmware which folks encountering problems are encouraged to test. I've rolled most but not all of the changes from the Linux 6.9 drivers in; some will require more testing and/or may not be useful. Please try: http://people.freebsd.org/~msmith/RAID/3ware/twe.releng_4.diff http://people.freebsd.org/~msmith/RAID/3ware/twe.current.diff and let me know how you go. - -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt ------- End of Blind-Carbon-Copy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 3:48:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id 06A0137B402; Mon, 18 Feb 2002 03:48:33 -0800 (PST) Received: from peter3.wemm.org ([12.232.27.13]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020218114827.WMXP1214.rwcrmhc54.attbi.com@peter3.wemm.org>; Mon, 18 Feb 2002 11:48:27 +0000 Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id g1IBmQs32757; Mon, 18 Feb 2002 03:48:26 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (Postfix) with ESMTP id AAFF43A9A; Mon, 18 Feb 2002 03:48:26 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Bernd Walter Cc: alpha@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: OK, who broke alpha this time? :-/ In-Reply-To: <20020218063632.GA44861@cicely8.cicely.de> Date: Mon, 18 Feb 2002 03:48:26 -0800 From: Peter Wemm Message-Id: <20020218114826.AAFF43A9A@overcee.wemm.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bernd Walter wrote: > On Sun, Feb 17, 2002 at 10:07:34PM -0800, Peter Wemm wrote: > > ... > > sio0 at port 0x3f8-0x3ff irq 4 on isa0 > > sio0: type 16550A, console > > sio0: interrupting at ISA irq 4 > > sio1: reserved for low-level i/o > > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > > Timecounter "i8254" frequency 1193182 Hz > > ata0-slave: timeout waiting for interrupt > > ata0-slave: ATAPI identify failed > > acd0: CDROM at ata0-master PIO4 > > Waiting 2 seconds for SCSI devices to settle > > Mounting root from ufs:/dev/da0a > > da0 at ahc0 bus 0 target 0 lun 0 > > da0: Fixed Direct Access SCSI-3 device > > da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing En abled > > da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) > > da1 at ahc0 bus 0 target 1 lun 0 > > da1: Fixed Direct Access SCSI-3 device > > da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing En abled > > da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) > > ^T > load: 0.16 cmd: init 8 [inode] 0.00u 0.00s 0% 416k > > ^T > > load: 0.16 cmd: init 8 [inode] 0.00u 0.00s 0% 416k > > [forever] > > > > http://people.freebsd.org/~peter/alphadmesg.txt > > > > It seems that locking has been hosed somehow. > > Just guessing: > John Baldwin had enabled interrupt thread preemption some days ago. > src/sys/alpha/alpha/interrupt.c rev 1.61 > Maybe it also enabled some hidden bug. > > I hope to have one of my machines on -current later that day to > compare. Actually, it appears to be rev 1.131 of kern/vfs_vnops.c (suggested by phk, that revision panics his i386 diskless boots). Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 4:21: 6 2002 Delivered-To: freebsd-current@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id AF73237B404 for ; Mon, 18 Feb 2002 04:20:57 -0800 (PST) Received: from pool0015.cvx40-bradley.dialup.earthlink.net ([216.244.42.15] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16cmmu-0000N2-00; Mon, 18 Feb 2002 04:20:56 -0800 Message-ID: <3C70F19E.67BFCE35@mindspring.com> Date: Mon, 18 Feb 2002 04:20:46 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "George V. Neville-Neil" Cc: freebsd-current@freebsd.org Subject: Re: A quick, dumb, question... References: <200202180143.RAA266778@meer.meer.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "George V. Neville-Neil" wrote: > Is there a single document, or small set of documents, that describes getting > started kernel hacking on FreeBSD? How about a set of URLs? > > I would like something that tells me about (in no particular order) > > 1) debugging over the serial line, and remote debugging in general Use the handbook description. The only caveat is that you need to tell it to break to gdb before you start the GDB on the debugging system, or you'll get serial synchornization errors; this isn't documented in the handbook, but it is nevertheless true. > 2) Building for 5.0 on 4.x (if possible though I suspect I should not do this) Avoid doing this if you can. If you can't, then use a chroot'ed image of CDROM #2 to do the job. You should also copy in the ps, w, /kernel, etc. and other libkvm-using programs if you plan on using them, and make sure that you copy in /dev (in 5.0, there would be a devfs, and you don't have onw) and mount the procfs in the chroot environment. > 3) Best practices for dealing with my own versions of files while also > working with cvsup. Keep a seperate repository of your own stuff. Some people will tell you to trust the "magic" numbers for revision tags, which are poorly documented in a couple of places, but really, you want to maintain full revision history, and have a lesser problem merging, so you're better off importing the kernel (if you are hacking the kernel), and anything else you are hacking, into a private repository, by bringing it in on a vendor branch. See the CVS FAQ. If you also want to risk CVSup with the "magic" tags, look for the documentation that John Polstra has written (I think there is also a Daemon News article, FWIW). > Those are a good start for now. > > BTW If none exists I will try to write this up in the form of a tutorial > and post it at some point. If you want to write it up as something like "Building a FreeBSD derived System" or something like that, it would make a good Dameon News article. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 4:31:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 352E237B400; Mon, 18 Feb 2002 04:31:08 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id XAA15984; Mon, 18 Feb 2002 23:30:55 +1100 Date: Mon, 18 Feb 2002 23:34:13 +1100 (EST) From: Bruce Evans X-X-Sender: To: Peter Wemm Cc: Bernd Walter , , Subject: Re: OK, who broke alpha this time? :-/ In-Reply-To: <20020218114826.AAFF43A9A@overcee.wemm.org> Message-ID: <20020218233300.Q6160-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 18 Feb 2002, Peter Wemm wrote: > Actually, it appears to be rev 1.131 of kern/vfs_vnops.c (suggested by > phk, that revision panics his i386 diskless boots). I guess vrele() gets done twice. See the big comment in vn_close() about when VOP_CLOSE() does a vrele(). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 5:10:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 7631A37B404; Mon, 18 Feb 2002 05:10:06 -0800 (PST) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.1/8.12.1) with ESMTP id g1IDA2lF022192; Mon, 18 Feb 2002 08:10:04 -0500 (EST) Date: Mon, 18 Feb 2002 08:10:02 -0500 (EST) From: Daniel Eischen To: Peter Wemm Cc: Bernd Walter , alpha@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: OK, who broke alpha this time? :-/ In-Reply-To: <20020218114826.AAFF43A9A@overcee.wemm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG And when is alpha buildworld going to work again? It's been busted for well over a week. The following patch posted by drew gets around the problem for now. If we want people to test changes on on the alpha, then we should try and make sure that world isn't broken for too long on it. I know the fix below isn't correct, but it at least allows world to build. Index: usr.bin/binutils/gdb/alpha//kvm-fbsd.c =================================================================== RCS file: /home/ncvs/src/gnu/usr.bin/binutils/gdb/alpha/kvm-fbsd.c,v retrieving revision 1.6 diff -u -r1.6 kvm-fbsd.c --- usr.bin/binutils/gdb/alpha//kvm-fbsd.c 13 Oct 2001 04:38:46 -0000 1.6 +++ usr.bin/binutils/gdb/alpha//kvm-fbsd.c 17 Feb 2002 21:57:25 -0000 @@ -390,7 +390,7 @@ addr = (CORE_ADDR)parse_and_eval_address(arg); /* Read the PCB address in proc structure. */ - addr += (int) &((struct proc *)0)->p_thread.td_pcb; + addr += (int) &((struct proc *)0)->p_xxthread.td_pcb; if (kvread(addr, &val)) error("cannot read pcb ptr"); -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 5:56:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id AEF5C37B417; Mon, 18 Feb 2002 05:56:18 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id IAA29885; Mon, 18 Feb 2002 08:56:13 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g1IDth531825; Mon, 18 Feb 2002 08:55:43 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15473.2014.937310.949425@grasshopper.cs.duke.edu> Date: Mon, 18 Feb 2002 08:55:42 -0500 (EST) To: Daniel Eischen Cc: Peter Wemm , Bernd Walter , alpha@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: OK, who broke alpha this time? :-/ In-Reply-To: References: <20020218114826.AAFF43A9A@overcee.wemm.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Daniel Eischen writes: > > And when is alpha buildworld going to work again? It's been > busted for well over a week. The following patch posted by Crap. . I'd forgotten all about that. I have a fix locally that I'll commit as soon as I can power on the machine. Peter & I agreed not to fix this so as to break buildworld & prevent innocent bystanders from installing a bad rtld and hosing their systems. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 6: 2:10 2002 Delivered-To: freebsd-current@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id DE0A437B416; Mon, 18 Feb 2002 06:02:02 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.6/8.11.6) with UUCP id g1IE21A20801; Mon, 18 Feb 2002 15:02:01 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g1IE1jeS040425; Mon, 18 Feb 2002 15:01:45 +0100 (CET)?g (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.6/8.11.6) id g1IE1ih46284; Mon, 18 Feb 2002 15:01:44 +0100 (CET) (envelope-from ticso) Date: Mon, 18 Feb 2002 15:01:44 +0100 From: Bernd Walter To: Andrew Gallatin Cc: Daniel Eischen , Peter Wemm , alpha@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: OK, who broke alpha this time? :-/ Message-ID: <20020218140144.GI45770@cicely8.cicely.de> References: <20020218114826.AAFF43A9A@overcee.wemm.org> <15473.2014.937310.949425@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15473.2014.937310.949425@grasshopper.cs.duke.edu> User-Agent: Mutt/1.3.26i X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Feb 18, 2002 at 08:55:42AM -0500, Andrew Gallatin wrote: > > Daniel Eischen writes: > > > > And when is alpha buildworld going to work again? It's been > > busted for well over a week. The following patch posted by > > Crap. . I'd forgotten all about that. I have a fix locally that I'll > commit as soon as I can power on the machine. buildworld worked for me. installworld was failing claiming no gdb was there to install. > Peter & I agreed not to fix this so as to break buildworld & prevent > innocent bystanders from installing a bad rtld and hosing their > systems. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 6:10:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from cathbad.happygiraffe.net (choke.semantico.com [212.74.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 0B89837B416; Mon, 18 Feb 2002 06:09:38 -0800 (PST) Received: by cathbad.happygiraffe.net (Postfix, from userid 1001) id 180305D7C; Mon, 18 Feb 2002 14:04:58 +0000 (GMT) Date: Mon, 18 Feb 2002 14:04:57 +0000 To: Peter Wemm Cc: alpha@freebsd.org, current@freebsd.org Subject: Re: OK, who broke alpha this time? :-/ Message-ID: <20020218140457.A518@cathbad.happygiraffe.net> References: <20020218060734.314FE3809@overcee.wemm.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="x+6KMIRAuhnl3hBn" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020218060734.314FE3809@overcee.wemm.org>; from peter@wemm.org on Sun, Feb 17, 2002 at 10:07:34PM -0800 X-Warning: Incoming message from The Big Giant Head! X-OS: FreeBSD 5.0-CURRENT i386 X-Uptime: 1:59PM up 8 mins, 1 user, load averages: 0.00, 0.03, 0.01 From: dom@happygiraffe.net (Dominic Mitchell) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --x+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Feb 17, 2002 at 10:07:34PM -0800, Peter Wemm wrote: > ... > sio0 at port 0x3f8-0x3ff irq 4 on isa0 > sio0: type 16550A, console > sio0: interrupting at ISA irq 4 > sio1: reserved for low-level i/o > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounter "i8254" frequency 1193182 Hz > ata0-slave: timeout waiting for interrupt > ata0-slave: ATAPI identify failed > acd0: CDROM at ata0-master PIO4 > Waiting 2 seconds for SCSI devices to settle > Mounting root from ufs:/dev/da0a > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled > da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-3 device > da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled > da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) > ^T > load: 0.16 cmd: init 8 [inode] 0.00u 0.00s 0% 416k > ^T > load: 0.16 cmd: init 8 [inode] 0.00u 0.00s 0% 416k > [forever] > > http://people.freebsd.org/~peter/alphadmesg.txt > > It seems that locking has been hosed somehow. Just to confirm, I've just seen this on my i386 laptop (sony Z600TEK), too, which has a fresh cvsup and build from about 2.5 hours ago. Attached is a dmesg from my kernel.old which I've just manage to boot and a kernel config. -Dom --x+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="CATHBAD.dmesg" Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #32: Mon Feb 11 14:48:12 GMT 2002 root@cathbad.happygiraffe.net:/usr/obj/usr/src/sys/CATHBAD Preloaded elf kernel "/boot/kernel.old/kernel" at 0xc0370000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc03700ac. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 694834844 Hz CPU: Pentium III/Pentium III Xeon/Celeron (694.83-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 268369920 (262080K bytes) avail memory = 257699840 (251660K bytes) Pentium Pro MTRR support enabled Using $PIR table, 7 entries at 0xc00fdf50 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard Timecounter "ACPI" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_button0: on acpi0 acpi_pcib0: port 0xcf8-0xcff on acpi0 pci0: on acpi_pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) pci0: at device 8.0 (no driver attached) pci0: at device 9.0 (no driver attached) pci0: at device 10.0 (no driver attached) pci0: at device 11.0 (no driver attached) acpi_pcib0: device is routed to IRQ 9 pcic0: irq 9 at device 12.0 on pci0 pcic0: PCI Memory allocated: 0x44000000 pccard0: on pcic0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 acpi_ec0: port 0x66,0x62 on acpi0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A ppc0 port 0x778-0x77a,0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port acpi_cmbat0: on acpi0 acpi_acad0: on acpi0 ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it pcic: pcic0 already exists; skipping it ppc: ppc0 already exists; skipping it sc: sc0 already exists; skipping it sio: sio0 already exists; skipping it vga: vga0 already exists; skipping it orm0:
 3DImage1.gif
Monday, February = 18, 2002   Issue #1
=

 

3DImage2.gif
3 Day Baja Mexico Cruise from = Los Angeles
April 5-8, 2002 =

2 Nights of = Urban Comedy

 1 Night with a Special = Show


Speedy

Parties aboard = the Ecstasy

Excursions in = Ensenada


Shang


Luenell

=


Mike = Bonner


Rodney = Perry

Also = Starring:
=
Rip Da = Playa
Kirk = McHenry
=
Get ready for some serious partying and = hilarious urban comedy. The "Comedy on the High Seas II" = cruise is set. This year's cruise features two nights of "Off the = Chain" urban comedy and one night with a special surprise show. The = cruise is a three day party to Ensenada, Mexico from Los Angeles, = California.

The special Web = Site for the cruise is ComedyCruise.com. The site = features preview performances of the comedians for this year's cruise, a = complete schedule and description of all of the planned events, video = clips and photos from last year's cruise (including never before seen = ones), a preview of the Ecstasy, events and destinations in Ensenada, = and a complete on-line reservation system.

 =
Last = year's cruise sold out early. To avoid missing out on what everyone is = still talking about, make sure that you book early, only a minimal = deposit is required to hold your cabin.

 =
For = more information or to book the cruise, please call Comedy Access at = (510) 777-2952 or send an e-mail to info@comedycruise.com. Payment = options and payment plans are available.3DImage5.gif


This is a private event... Available exclusively through = ComedyAccess.

Please choose SHANG as reference during = registration

Please foward this email to as many people that you want = to go on this trip of a lifetime. =

= ------=_NextPart_000_8E88_01C1B81A.78094B20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 7:55:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 2850437B404; Mon, 18 Feb 2002 07:55:30 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g1IFtMD82364; Mon, 18 Feb 2002 10:55:22 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 18 Feb 2002 10:55:22 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Peter Wemm Cc: alpha@freebsd.org, current@freebsd.org Subject: Re: OK, who broke alpha this time? :-/ In-Reply-To: <20020218060734.314FE3809@overcee.wemm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Oops. Mis-merge. Thanks to Ian for fixing this. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Sun, 17 Feb 2002, Peter Wemm wrote: > ... > sio0 at port 0x3f8-0x3ff irq 4 on isa0 > sio0: type 16550A, console > sio0: interrupting at ISA irq 4 > sio1: reserved for low-level i/o > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounter "i8254" frequency 1193182 Hz > ata0-slave: timeout waiting for interrupt > ata0-slave: ATAPI identify failed > acd0: CDROM at ata0-master PIO4 > Waiting 2 seconds for SCSI devices to settle > Mounting root from ufs:/dev/da0a > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled > da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-3 device > da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled > da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) > ^T > load: 0.16 cmd: init 8 [inode] 0.00u 0.00s 0% 416k > ^T > load: 0.16 cmd: init 8 [inode] 0.00u 0.00s 0% 416k > [forever] > > http://people.freebsd.org/~peter/alphadmesg.txt > > It seems that locking has been hosed somehow. > > Cheers, > -Peter > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 10:53:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 4E52B37B400 for ; Mon, 18 Feb 2002 10:53:26 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id g1IIrQQ61800 for current@freebsd.org; Mon, 18 Feb 2002 10:53:26 -0800 (PST) (envelope-from david) Date: Mon, 18 Feb 2002 10:53:26 -0800 (PST) From: David Wolfskill Message-Id: <200202181853.g1IIrQQ61800@bunrab.catwhisker.org> To: current@freebsd.org Subject: Hangs with today's -CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Not entirely sure whether these hangs are related. First one (which I have been able to reproduce, and from which I invoked the debugger) is on my build machine, which is an SMP box: Mounting root from ufs:/dev/ad0s4a ad0s1: type 0xa5, start 63, end = 4192964, size 4192902 : OK ad0s2: type 0xa5, start 4192965, end = 8385929, size 4192965 : OK ad0s3: type 0xa5, start 8385930, end = 12578894, size 4192965 : OK ad0s4: type 0xa5, start 12578895, end = 80276804, size 67697910 : OK rMP: CPU1 apic_isntiatrita_liinziet(:) :t 0 i n g /lisnbti0n:/ i0nxi0t0 10700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff SMP: AP CPU #1 Launched! db> trace siointr1(c3f59c00,c0390280,0,c02f9b03,661) at siointr1+0xb1 siointr(c3f59c00) at siointr+0x23 Xfastintr4() at Xfastintr4+0x34 --- interrupt, eip = 0xc01a72f1, esp = 0xd683cd04, ebp = 0xd683cd0c --- runq_check(d682c600,d683cd34,c0195ca8,0,d683cd48) at runq_check+0x21 idle_proc(0,d683cd48,0,c0195e68,0) at idle_proc+0x2f fork_exit(c0195e68,0,d683cd48) at fork_exit+0x9c fork_trampoline() at fork_trampoline+0x8 db> show locks exclusive (spin mutex) sio (0xc0390280) locked @ /usr/src/sys/dev/sio/sio.c:1633 db> show pcpu 0 cpuid = 0 curthread = 0xd682c600: pid 11 "idle: cpu0" curpcb = 0xd683cda0 fpcurthread = none idlethread = 0xd682c600: pid 11 "idle: cpu0" currentldt = 0x28 spin locks held: exclusive (spin mutex) sio (0xc0390280) locked @ /usr/src/sys/dev/sio/sio.c:1633 db> show pcpu 1 cpuid = 1 curthread = 0xd682c900: pid 10 "idle: cpu1" curpcb = 0xd6838da0 fpcurthread = none idlethread = 0xd682c900: pid 10 "idle: cpu1" currentldt = 0x28 spin locks held: db> show lockedvnodes Locked vnodes panic: blockable sleep lock (sleep mutex) mountlist @ /usr/src/sys/kern/vfs_subr.c:2386 cpuid = 0; lapic.id = 00000000 Debugger("panic") Stopped at siointr1+0xb1: jmp siointr1+0x1b7 db> show map Task map 0xc02927f1: pmap=0x86ff00f7, nentries=1581315584, version=268435456 kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = 00000000 fault virtual address = 0x83f6890c fault code = supervisor read, page not present instruction pointer = 0x8:0xc0280898 stack pointer = 0x10:0xd683cb00 frame pointer = 0x10:0xd683cb0c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 11 (idle: cpu0) kernel: type 12 trap, code=0 Stopped at siointr1+0xb1: jmp siointr1+0x1b7 db> As noted, the machine is sitting, waiting for me to do more stuff to it, which I'm quite willing to do. The second is on my laptop. I don't have as extensive information on that, because I use the laptop to access the other machines, so having it non-responsive impairs my ability to do such things as send mail. :-) But after breaking to the debugger, a "show locks" on the laptop yielded: db> show locks exclusive (sleep mutex) Giant (0x0408460) locked @ /usr/src/sys/kern/kern_intr.c:532 db> Local CVS repository synced with cvsup14 (I think; I'd need to get the build machine running again to be sure, as it is also the local CVSup server) starting at 0347 hrs., ending around 0356 hrs. US/Pacific (8 hrs. west of GMT/UTC). Hints/clues/suggestions/...? Thanks, david -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 11:12:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8599337B400 for ; Mon, 18 Feb 2002 11:12:17 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1IJCGK32122; Mon, 18 Feb 2002 11:12:16 -0800 (PST) (envelope-from dillon) Date: Mon, 18 Feb 2002 11:12:16 -0800 (PST) From: Matthew Dillon Message-Id: <200202181912.g1IJCGK32122@apollo.backplane.com> To: current@freebsd.org Subject: Patch to improve mutex collision performance Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG While testing some Giant removal stuff I noticed that my current system sometimes got into an extremely non-optimal flip-flop situation between two processes contesting Giant on an SMP system which halved the syscall performance in the test. In my getuid test, for example, with Giant in place I was getting 683Kcalls/sec with one process and 427Kcalls/sec with two. Giant was being obtained in two places: in userret and in getuid(). When I turned off Giant in getuid() the syscall performance actually went DOWN, to 250Kcalls/sec with two processes. This was a totally unexpected result. It turns out that the two processes got into an extremely non-optimal contested/sleep/wakeup situation, even though they do not actually have to sleep on Giant in this situation. The solution is to allow _mtx_lock_sleep() to spin instead of sleep in the situation where: (1) there are no runnable processes other then the ones already running on a cpu, (2) interrupts are enabled, and (3) the mutex in question is not contested (to avoid starving the thread contesting the mutex). In this case we can spin. This will go in tonight if no problems arise. -Matt Index: kern/kern_mutex.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_mutex.c,v retrieving revision 1.80 diff -u -r1.80 kern_mutex.c --- kern/kern_mutex.c 18 Feb 2002 17:51:47 -0000 1.80 +++ kern/kern_mutex.c 18 Feb 2002 19:11:17 -0000 @@ -287,7 +287,9 @@ _mtx_lock_sleep(struct mtx *m, int opts, const char *file, int line) { struct thread *td = curthread; +#if 0 struct ksegrp *kg = td->td_ksegrp; +#endif if ((m->mtx_lock & MTX_FLAGMASK) == (uintptr_t)td) { m->mtx_recurse++; @@ -312,6 +314,22 @@ * the sched_lock. */ if ((v = m->mtx_lock) == MTX_UNOWNED) { mtx_unlock_spin(&sched_lock); continue; } + + /* + * Check to see if there are any runnable processes. If + * there aren't and nobody is contesting the mutex (to avoid + * starving a contester) and interrupts are enabled, then + * we can safely spin. + * + * This prevents a silly-sleep-flip-flop situation on SMP + * systems where two running processes need Giant (or any + * other sleep mutex). + */ + if (td->td_critnest == 0 && (v & MTX_CONTESTED) == 0 && + procrunnable() == 0) { + mtx_unlock_spin(&sched_lock); + continue; + } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 11:43:39 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 7148937B402 for ; Mon, 18 Feb 2002 11:43:35 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g1IJhQL99006; Mon, 18 Feb 2002 11:43:26 -0800 (PST) (envelope-from obrien) Date: Mon, 18 Feb 2002 11:43:26 -0800 From: "David O'Brien" To: Matthew Dillon Cc: current@freebsd.org Subject: Re: Patch to improve mutex collision performance Message-ID: <20020218114326.A98974@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200202181912.g1IJCGK32122@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202181912.g1IJCGK32122@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Feb 18, 2002 at 11:12:16AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Feb 18, 2002 at 11:12:16AM -0800, Matthew Dillon wrote: > While testing some Giant removal stuff I noticed that my current > system sometimes got into an extremely non-optimal flip-flop situation > between two processes contesting Giant on an SMP system which halved the > syscall performance in the test. ... > This will go in tonight if no problems arise. I request that you give say a 3 day review period for this. I know JHB still has limited email access (no DSL yet). This may be something he should review. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 11:51:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B5E4A37B400; Mon, 18 Feb 2002 11:51:44 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1IJpip33604; Mon, 18 Feb 2002 11:51:44 -0800 (PST) (envelope-from dillon) Date: Mon, 18 Feb 2002 11:51:44 -0800 (PST) From: Matthew Dillon Message-Id: <200202181951.g1IJpip33604@apollo.backplane.com> To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :I request that you give say a 3 day review period for this. :I know JHB still has limited email access (no DSL yet). :This may be something he should review. Sigh. Are you intending to ask me to have JHB review every single change I make to -current? Because if you are the answer is: "Are you out of your mind?". I'm fairly sure JHB does not have a patch to address this but, please, be my guest and check P4. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 12: 0:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id A9F8537B402 for ; Mon, 18 Feb 2002 12:00:38 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020218200038.GKFM1214.rwcrmhc54.attbi.com@InterJet.elischer.org>; Mon, 18 Feb 2002 20:00:38 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA52841; Mon, 18 Feb 2002 11:50:10 -0800 (PST) Date: Mon, 18 Feb 2002 11:50:09 -0800 (PST) From: Julian Elischer To: Matthew Dillon Cc: current@freebsd.org Subject: Re: Patch to improve mutex collision performance In-Reply-To: <200202181912.g1IJCGK32122@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 18 Feb 2002, Matthew Dillon wrote: [...] > > It turns out that the two processes got into an extremely non-optimal > contested/sleep/wakeup situation, even though they do not actually have > to sleep on Giant in this situation. > > The solution is to allow _mtx_lock_sleep() to spin instead of sleep in > the situation where: (1) there are no runnable processes other then > the ones already running on a cpu, (2) interrupts are enabled, and > (3) the mutex in question is not contested (to avoid starving the thread > contesting the mutex). In this case we can spin. it's possible John's preemption code may also handle this.. > > -Matt > > Index: kern/kern_mutex.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/kern_mutex.c,v > retrieving revision 1.80 > diff -u -r1.80 kern_mutex.c > --- kern/kern_mutex.c 18 Feb 2002 17:51:47 -0000 1.80 > +++ kern/kern_mutex.c 18 Feb 2002 19:11:17 -0000 > @@ -287,7 +287,9 @@ > _mtx_lock_sleep(struct mtx *m, int opts, const char *file, int line) > { > struct thread *td = curthread; > +#if 0 > struct ksegrp *kg = td->td_ksegrp; > +#endif > > if ((m->mtx_lock & MTX_FLAGMASK) == (uintptr_t)td) { > m->mtx_recurse++; > @@ -312,6 +314,22 @@ > * the sched_lock. > */ > if ((v = m->mtx_lock) == MTX_UNOWNED) { > mtx_unlock_spin(&sched_lock); > continue; > } > + > + /* > + * Check to see if there are any runnable processes. If > + * there aren't and nobody is contesting the mutex (to avoid > + * starving a contester) and interrupts are enabled, then > + * we can safely spin. > + * > + * This prevents a silly-sleep-flip-flop situation on SMP > + * systems where two running processes need Giant (or any > + * other sleep mutex). > + */ > + if (td->td_critnest == 0 && (v & MTX_CONTESTED) == 0 && > + procrunnable() == 0) { > + mtx_unlock_spin(&sched_lock); > + continue; > + } I can't see any major problem with this but I can't help thinking that there must be one.. on UP the question is: "who is going to release the lock if no-one is runnable?" can you detail in more clarity the flip-flopping you were seeing? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 12: 4:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from angelica.unixdaemons.com (angelica.unixdaemons.com [209.148.64.135]) by hub.freebsd.org (Postfix) with ESMTP id E869A37B41B; Mon, 18 Feb 2002 12:04:09 -0800 (PST) Received: from angelica.unixdaemons.com (bmilekic@localhost.unixdaemons.com [127.0.0.1]) by angelica.unixdaemons.com (8.12.2/8.12.1) with ESMTP id g1IK3t3c022451; Mon, 18 Feb 2002 15:03:55 -0500 (EST) Received: (from bmilekic@localhost) by angelica.unixdaemons.com (8.12.2/8.12.1/Submit) id g1IK3trd022450; Mon, 18 Feb 2002 15:03:55 -0500 (EST) (envelope-from bmilekic) Date: Mon, 18 Feb 2002 15:03:55 -0500 From: Bosko Milekic To: Matthew Dillon Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance Message-ID: <20020218150355.A21615@unixdaemons.com> References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200202181951.g1IJpip33604@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Feb 18, 2002 at 11:51:44AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Feb 18, 2002 at 11:51:44AM -0800, Matthew Dillon wrote: > > :I request that you give say a 3 day review period for this. > :I know JHB still has limited email access (no DSL yet). > :This may be something he should review. > > Sigh. Are you intending to ask me to have JHB review every single change > I make to -current? Because if you are the answer is: "Are you out of > your mind?". > > I'm fairly sure JHB does not have a patch to address this but, please, > be my guest and check P4. I've looked at it and I think it's OK. There are a few minor things I could think of, but they are only related to the context-borrowing interrupt stuff I'm working on in parallel (notably, when it goes in, I'll modify the "if ()" statement in there to add a check and only perform the lazy spin if we're not borrowing context). This only to say that I'm glad that you at least posted it for review, as it allowed me to make a quick note of this. The only other issue has to do with you getting pre-empted by, say, an interrupt after dropping sched_lock and then, should the lock you're trying to get become contested while the handler is running, have relatively weak priority on it after you iret and continue iterating. However, the odds of this happening are not only weak but this small loss of priority already exists in the locking code anyway (think of when we're trying to get a lock and get pre-empted right after failing to get it but before grabbing sched_lock and putting ourselves to sleep). So, in effect, it's a non-issue. > -Matt > Matthew Dillon > -- Bosko Milekic bmilekic@unixdaemons.com bmilekic@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 12: 9:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B405A37B417 for ; Mon, 18 Feb 2002 12:09:28 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1IK9Sh36025; Mon, 18 Feb 2002 12:09:28 -0800 (PST) (envelope-from dillon) Date: Mon, 18 Feb 2002 12:09:28 -0800 (PST) From: Matthew Dillon Message-Id: <200202182009.g1IK9Sh36025@apollo.backplane.com> To: current@freebsd.org Subject: Patch sets to date and timing tests with Giant out of userret. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Here are my giant related patches to date. These are NOT all commit candidates. Some are just hacks to test Giant removal. Julian is responsible for the td_ucred persistance stuff. The hack in userret() is just a hack to remove Giant when no signals are present in order to test performance. Note that Julian hasn't updated persistent support for other cpu's so this patch only operates on i386. userret() appears to be the last major Giant-contention point in the syscall management path. getuid() performance, calls per second. current, SMP build, 2xCPU, invariants (+ patches below). unpatched userret, kern.giant.ucred=1 (default) 1 process: 683K 2 processes: 427K per process unpatched userret, kern.giant.ucred=0 1 process: 770K 2 processes: 460K per process patched userret, kern.giant.ucred=1 (default) 1 process: 739K 2 processes: 480K per process patched userret, kern.giant.ucred=0 1 process: 855K 2 processes: 706K per process The 1 process vs 2 process numbers are getting a lot closer, but they are still not perfect. -Matt Index: i386/i386/trap.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/trap.c,v retrieving revision 1.212 diff -u -r1.212 trap.c --- i386/i386/trap.c 17 Feb 2002 01:09:54 -0000 1.212 +++ i386/i386/trap.c 18 Feb 2002 19:46:50 -0000 @@ -255,7 +255,9 @@ sticks = td->td_kse->ke_sticks; td->td_frame = &frame; +#if 0 KASSERT(td->td_ucred == NULL, ("already have a ucred")); +#endif if (td->td_ucred != p->p_ucred) cred_update_thread(td); @@ -643,7 +645,7 @@ userret(td, &frame, sticks); mtx_assert(&Giant, MA_NOTOWNED); userout: -#ifdef INVARIANTS +#if 0 mtx_lock(&Giant); crfree(td->td_ucred); mtx_unlock(&Giant); @@ -954,7 +956,9 @@ sticks = td->td_kse->ke_sticks; td->td_frame = &frame; +#if 0 KASSERT(td->td_ucred == NULL, ("already have a ucred")); +#endif if (td->td_ucred != p->p_ucred) cred_update_thread(td); params = (caddr_t)frame.tf_esp + sizeof(int); @@ -1099,7 +1103,7 @@ */ STOPEVENT(p, S_SCX, code); -#ifdef INVARIANTS +#if 0 mtx_lock(&Giant); crfree(td->td_ucred); mtx_unlock(&Giant); Index: kern/kern_fork.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_fork.c,v retrieving revision 1.131 diff -u -r1.131 kern_fork.c --- kern/kern_fork.c 17 Feb 2002 01:09:55 -0000 1.131 +++ kern/kern_fork.c 18 Feb 2002 19:46:51 -0000 @@ -799,7 +799,7 @@ kthread_exit(0); } PROC_UNLOCK(p); -#ifdef INVARIANTS +#if 0 mtx_lock(&Giant); crfree(td->td_ucred); mtx_unlock(&Giant); Index: kern/kern_mutex.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_mutex.c,v retrieving revision 1.80 diff -u -r1.80 kern_mutex.c --- kern/kern_mutex.c 18 Feb 2002 17:51:47 -0000 1.80 +++ kern/kern_mutex.c 18 Feb 2002 19:46:51 -0000 @@ -287,7 +287,9 @@ _mtx_lock_sleep(struct mtx *m, int opts, const char *file, int line) { struct thread *td = curthread; +#if 0 struct ksegrp *kg = td->td_ksegrp; +#endif if ((m->mtx_lock & MTX_FLAGMASK) == (uintptr_t)td) { m->mtx_recurse++; @@ -312,6 +314,22 @@ * the sched_lock. */ if ((v = m->mtx_lock) == MTX_UNOWNED) { + mtx_unlock_spin(&sched_lock); + continue; + } + + /* + * Check to see if there are any runnable processes. If + * there aren't and nobody is contesting the mutex (to avoid + * starving a contester) and interrupts are enabled, then + * we can safely spin. + * + * This prevents a silly-sleep-flip-flop situation on SMP + * systems where two running processes need Giant (or any + * other sleep mutex). + */ + if (td->td_critnest == 0 && (v & MTX_CONTESTED) == 0 && + procrunnable() == 0) { mtx_unlock_spin(&sched_lock); continue; } Index: kern/kern_prot.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_prot.c,v retrieving revision 1.135 diff -u -r1.135 kern_prot.c --- kern/kern_prot.c 17 Feb 2002 07:30:34 -0000 1.135 +++ kern/kern_prot.c 18 Feb 2002 19:46:51 -0000 @@ -228,14 +228,14 @@ struct thread *td; struct getuid_args *uap; { - struct proc *p = td->td_proc; + int s; - mtx_lock(&Giant); - td->td_retval[0] = p->p_ucred->cr_ruid; + s = mtx_lock_giant(kern_giant_ucred); + td->td_retval[0] = td->td_ucred->cr_ruid; #if defined(COMPAT_43) || defined(COMPAT_SUNOS) - td->td_retval[1] = p->p_ucred->cr_uid; + td->td_retval[1] = td->td_ucred->cr_uid; #endif - mtx_unlock(&Giant); + mtx_unlock_giant(s); return (0); } @@ -253,9 +253,11 @@ struct thread *td; struct geteuid_args *uap; { - mtx_lock(&Giant); - td->td_retval[0] = td->td_proc->p_ucred->cr_uid; - mtx_unlock(&Giant); + int s; + + s = mtx_lock_giant(kern_giant_ucred); + td->td_retval[0] = td->td_ucred->cr_uid; + mtx_unlock_giant(s); return (0); } @@ -273,14 +275,14 @@ struct thread *td; struct getgid_args *uap; { - struct proc *p = td->td_proc; + int s; - mtx_lock(&Giant); - td->td_retval[0] = p->p_ucred->cr_rgid; + s = mtx_lock_giant(kern_giant_ucred); + td->td_retval[0] = td->td_ucred->cr_rgid; #if defined(COMPAT_43) || defined(COMPAT_SUNOS) - td->td_retval[1] = p->p_ucred->cr_groups[0]; + td->td_retval[1] = td->td_ucred->cr_groups[0]; #endif - mtx_unlock(&Giant); + mtx_unlock_giant(s); return (0); } @@ -303,11 +305,11 @@ struct thread *td; struct getegid_args *uap; { - struct proc *p = td->td_proc; + int s; - mtx_lock(&Giant); - td->td_retval[0] = p->p_ucred->cr_groups[0]; - mtx_unlock(&Giant); + s = mtx_lock_giant(kern_giant_ucred); + td->td_retval[0] = td->td_ucred->cr_groups[0]; + mtx_unlock_giant(s); return (0); } @@ -326,13 +328,13 @@ register struct getgroups_args *uap; { struct ucred *cred; - struct proc *p = td->td_proc; u_int ngrp; int error; + int s; - mtx_lock(&Giant); + s = mtx_lock_giant(kern_giant_ucred); error = 0; - cred = p->p_ucred; + cred = td->td_ucred; if ((ngrp = uap->gidsetsize) == 0) { td->td_retval[0] = cred->cr_ngroups; goto done2; @@ -347,7 +349,7 @@ goto done2; td->td_retval[0] = ngrp; done2: - mtx_unlock(&Giant); + mtx_unlock_giant(s); return (error); } @@ -1057,11 +1059,11 @@ struct getresuid_args *uap; { struct ucred *cred; - struct proc *p = td->td_proc; int error1 = 0, error2 = 0, error3 = 0; + int s; - mtx_lock(&Giant); - cred = p->p_ucred; + s = mtx_lock_giant(kern_giant_ucred); + cred = td->td_ucred; if (uap->ruid) error1 = copyout((caddr_t)&cred->cr_ruid, (caddr_t)uap->ruid, sizeof(cred->cr_ruid)); @@ -1071,7 +1073,7 @@ if (uap->suid) error3 = copyout((caddr_t)&cred->cr_svuid, (caddr_t)uap->suid, sizeof(cred->cr_svuid)); - mtx_unlock(&Giant); + mtx_unlock_giant(s); return (error1 ? error1 : error2 ? error2 : error3); } @@ -1092,11 +1094,11 @@ struct getresgid_args *uap; { struct ucred *cred; - struct proc *p = td->td_proc; int error1 = 0, error2 = 0, error3 = 0; + int s; - mtx_lock(&Giant); - cred = p->p_ucred; + s = mtx_lock_giant(kern_giant_ucred); + cred = td->td_ucred; if (uap->rgid) error1 = copyout((caddr_t)&cred->cr_rgid, (caddr_t)uap->rgid, sizeof(cred->cr_rgid)); @@ -1106,7 +1108,7 @@ if (uap->sgid) error3 = copyout((caddr_t)&cred->cr_svgid, (caddr_t)uap->sgid, sizeof(cred->cr_svgid)); - mtx_unlock(&Giant); + mtx_unlock_giant(s); return (error1 ? error1 : error2 ? error2 : error3); } @@ -1172,6 +1174,8 @@ /* * Check if gid is a member of the group set. + * + * MPSAFE (cred must be held) */ int groupmember(gid, cred) @@ -1228,6 +1232,8 @@ /* * wrapper to use if you have the thread on hand but not the proc. + * + * MPSAFE (cred must be held) */ int suser_xxx_td(cred, td, flag) @@ -1269,6 +1275,8 @@ * existing securelevel checks that occurred without a process/credential * context. In the future this will be disallowed, so a kernel message * is displayed. + * + * MPSAFE */ int securelevel_gt(struct ucred *cr, int level) Index: kern/subr_trap.c =================================================================== RCS file: /home/ncvs/src/sys/kern/subr_trap.c,v retrieving revision 1.208 diff -u -r1.208 subr_trap.c --- kern/subr_trap.c 17 Feb 2002 01:09:55 -0000 1.208 +++ kern/subr_trap.c 18 Feb 2002 19:46:51 -0000 @@ -72,12 +72,18 @@ struct ksegrp *kg = td->td_ksegrp; int sig; - mtx_lock(&Giant); PROC_LOCK(p); - while ((sig = CURSIG(p)) != 0) - postsig(sig); - PROC_UNLOCK(p); - mtx_unlock(&Giant); + if (!SIGISEMPTY(p->p_siglist)) { + PROC_UNLOCK(p); + mtx_lock(&Giant); + PROC_LOCK(p); + while ((sig = CURSIG(p)) != 0) + postsig(sig); + PROC_UNLOCK(p); + mtx_unlock(&Giant); + } else { + PROC_UNLOCK(p); + } mtx_lock_spin(&sched_lock); td->td_priority = kg->kg_user_pri; @@ -131,7 +137,9 @@ #endif KASSERT(TRAPF_USERMODE(framep), ("ast in kernel mode")); +#if 0 KASSERT(td->td_ucred == NULL, ("leaked ucred")); +#endif #ifdef WITNESS if (witness_list(td)) panic("Returning to user mode with mutex(s) held"); @@ -187,7 +195,7 @@ } userret(td, framep, sticks); -#ifdef INVARIANTS +#if 0 mtx_lock(&Giant); crfree(td->td_ucred); mtx_unlock(&Giant); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 12:20:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from k6.locore.ca (k6.locore.ca [198.96.117.170]) by hub.freebsd.org (Postfix) with ESMTP id 0C67637B427; Mon, 18 Feb 2002 12:20:27 -0800 (PST) Received: (from jake@localhost) by k6.locore.ca (8.11.6/8.11.6) id g1IKc7j00373; Mon, 18 Feb 2002 15:38:07 -0500 (EST) (envelope-from jake) Date: Mon, 18 Feb 2002 15:38:07 -0500 From: Jake Burkholder To: Matthew Dillon Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance Message-ID: <20020218153807.E96115@locore.ca> References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202181951.g1IJpip33604@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Feb 18, 2002 at 11:51:44AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Apparently, On Mon, Feb 18, 2002 at 11:51:44AM -0800, Matthew Dillon said words to the effect of; > > :I request that you give say a 3 day review period for this. > :I know JHB still has limited email access (no DSL yet). > :This may be something he should review. I second this request. > > Sigh. Are you intending to ask me to have JHB review every single change > I make to -current? For changes to the mutex code, yes. > Because if you are the answer is: "Are you out of > your mind?". Sigh. > > I'm fairly sure JHB does not have a patch to address this but, please, > be my guest and check P4. Actually he does. Maybe you should have checked p4 first yourself. What John's patch does is spin while the lock owner is running on another cpu. Spinning while there are no other processes on the run queues as well makes sense but you'll also be doing a lot of acquires and releases of sched_lock. The only thing that jumped out at me looking at the patch is that critnest cannot be 0 here because the sched_lock is held; holding a spin lock implies being in a critical section. I need to think about this more and would like you to wait until John has a chance to look at it as well. Jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 12:22: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B095737B402 for ; Mon, 18 Feb 2002 12:22:00 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1IKLTM36110; Mon, 18 Feb 2002 12:21:29 -0800 (PST) (envelope-from dillon) Date: Mon, 18 Feb 2002 12:21:29 -0800 (PST) From: Matthew Dillon Message-Id: <200202182021.g1IKLTM36110@apollo.backplane.com> To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :I can't see any major problem with this but I can't help thinking that :there must be one.. on UP the question is: "who is going to :release the lock if no-one is runnable?" An interrupt, of course. Wakeups don't happen out of thin air! This is true of 1.x, 2.x, 3.x, 4.x, 5.x, UP, and SMP. Something needs to trigger the event that causes the wakeup to occur. :can you detail in more clarity the flip-flopping you were seeing? Basically what is happening is that switch/wakeup overhead is being imposed unnecessarily. There is no need to switch if there is nothing to switch to, and this also causes the other process to not have to wakeup anyone when it releases Giant because process #1 is spinning on it instead of sleeping on it. So you immediate remove four context switches from the critical path. The other problem I saw is actually a fairly typical problem. When you have multiple cpu's running the same program that is making a system call that obtains a mutex, and the mutex spins, the programs will tend to stabilize slightly out of sync of each other so the mutex-release in one occurs just before the mutex-acquire in another. The result is fairly optimal performance for this particular situation even though the mutexes are spinning. However, when the mutex sleeps instead of spins no such stabilization occurs. Sometimes I would run the two-process test and they would operate optimally... obviously they were out of sync enough so there was no mutex contention in the one remaining Giant mutex in userret. Sometimes they would operate non-optimally, showing half the performance. Even worse, this non-optimal performance appears to stabilize.. i.e., it can't break out of it once it gets into it. So what this code does is avoid both the sleep, the context switch, and the wakeup in situations where they are not needed and reduces syscall overhead by about 100% per cpu with 2 cpus. It almost certainly also avoids. - In regards to preemption code, I think this is a separate issue. This case occurs when there are no runnable processes waiting for cpu in the system (i.e. running processes are already on their cpus). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 12:33: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4869037B417; Mon, 18 Feb 2002 12:32:33 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1IKWVS36193; Mon, 18 Feb 2002 12:32:31 -0800 (PST) (envelope-from dillon) Date: Mon, 18 Feb 2002 12:32:31 -0800 (PST) From: Matthew Dillon Message-Id: <200202182032.g1IKWVS36193@apollo.backplane.com> To: Bosko Milekic Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218150355.A21615@unixdaemons.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : I've looked at it and I think it's OK. There are a few minor things I :could think of, but they are only related to the context-borrowing :interrupt stuff I'm working on in parallel (notably, when it goes in, :I'll modify the "if ()" statement in there to add a check and only :perform the lazy spin if we're not borrowing context). Yah, I saw the not-yet code just below it. At worst we would simply not optimize for the borrowing case, or move the optimization to just below it (or move the interrupt borrowing code to above it, i.e. before we mess with the CONTESTED bit stuff, which may be better). : This only to say that I'm glad that you at least posted it for review, :as it allowed me to make a quick note of this. : The only other issue has to do with you getting pre-empted by, say, an :interrupt after dropping sched_lock and then, should the lock you're :trying to get become contested while the handler is running, have :relatively weak priority on it after you iret and continue iterating. :However, the odds of this happening are not only weak but this small :loss of priority already exists in the locking code anyway (think of :when we're trying to get a lock and get pre-empted right after failing :to get it but before grabbing sched_lock and putting ourselves to :sleep). So, in effect, it's a non-issue. : :-- :Bosko Milekic The simple stuff I like to just commit... like instrumenting something like getuid() which makes no actual change to the way Giant operates in the system unless you play with the sysctl. The more complex stuff I throw up as a notice of intent or to support test results. The really complex stuff I get an actual review for. --- People like to bitch and moan about my commits but, frankly, there isn't much to really bitch and moan about if you actually look at the commits. None of this stuff is not rocket science. -current has been broken half a dozen times in the last month and not a single one of those breakages has been due to me, so people should bitch and moan and someone else. I suppose I am just a convenient punching bag. (And, as a side note to the bozos on IRC that complained about my kern.giant.ucred commit I will note that I was the person who CREATED the instrumented giant code in the first place. If code could be said to be owned by anyone that code could be said to be owned by me. That code exists precisely to allow incremental Giant pushdown commits to -current without blowing up other developers, which is precisely what I am doing). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 12:43:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0E6C437B400; Mon, 18 Feb 2002 12:43:20 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1IKhIc36298; Mon, 18 Feb 2002 12:43:18 -0800 (PST) (envelope-from dillon) Date: Mon, 18 Feb 2002 12:43:18 -0800 (PST) From: Matthew Dillon Message-Id: <200202182043.g1IKhIc36298@apollo.backplane.com> To: Jake Burkholder Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :What John's patch does is spin while the lock owner is running on another cpu. :Spinning while there are no other processes on the run queues as well makes sense :but you'll also be doing a lot of acquires and releases of sched_lock. : :The only thing that jumped out at me looking at the patch is that critnest cannot :be 0 here because the sched_lock is held; holding a spin lock implies being in a :critical section. I need to think about this more and would like you to wait until :John has a chance to look at it as well. : :Jake Sure thing. Ah, critnest... you are right. I should be checking for critnest > 1. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 12:47:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 21C9137B402 for ; Mon, 18 Feb 2002 12:47:27 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g1IKlNF99637; Mon, 18 Feb 2002 12:47:23 -0800 (PST) (envelope-from obrien) Date: Mon, 18 Feb 2002 12:47:23 -0800 From: "David O'Brien" To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance Message-ID: <20020218124723.C99108@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202181951.g1IJpip33604@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Feb 18, 2002 at 11:51:44AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Feb 18, 2002 at 11:51:44AM -0800, Matthew Dillon wrote: > :I request that you give say a 3 day review period for this. > :I know JHB still has limited email access (no DSL yet). > :This may be something he should review. > > Sigh. Are you intending to ask me to have JHB review every single change > I make to -current? Because if you are the answer is: "Are you out of > your mind?". No, I am not. Just from things I thought he was working on, I thought this was in the same area. A 1 day review is rather short. That is all. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 12:48:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 25F7B37B400 for ; Mon, 18 Feb 2002 12:48:49 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g1IKmTG99651; Mon, 18 Feb 2002 12:48:29 -0800 (PST) (envelope-from obrien) Date: Mon, 18 Feb 2002 12:48:29 -0800 From: "David O'Brien" To: Matthew Dillon Cc: Bosko Milekic , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance Message-ID: <20020218124829.D99108@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218150355.A21615@unixdaemons.com> <200202182032.g1IKWVS36193@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202182032.g1IKWVS36193@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Feb 18, 2002 at 12:32:31PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Feb 18, 2002 at 12:32:31PM -0800, Matthew Dillon wrote: > People like to bitch and moan about my commits but, frankly, there isn't > much to really bitch and moan about if you actually look at the commits. I really did not think I was bitching about your commit. I just thought that people should be given a little time to digest it. > -current has been broken half a dozen times in the last month and not > a single one of those breakages has been due to me, so people should bitch > and moan and someone else. I suppose I am just a convenient punching bag. I've never accused you of breaking the build. I am happy with the procedures and care you take. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 12:51:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from k6.locore.ca (k6.locore.ca [198.96.117.170]) by hub.freebsd.org (Postfix) with ESMTP id 06A6A37B43C; Mon, 18 Feb 2002 12:51:36 -0800 (PST) Received: (from jake@localhost) by k6.locore.ca (8.11.6/8.11.6) id g1IL98d00585; Mon, 18 Feb 2002 16:09:08 -0500 (EST) (envelope-from jake) Date: Mon, 18 Feb 2002 16:09:07 -0500 From: Jake Burkholder To: Matthew Dillon Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance Message-ID: <20020218160907.F96115@locore.ca> References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> <200202182043.g1IKhIc36298@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202182043.g1IKhIc36298@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Feb 18, 2002 at 12:43:18PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Apparently, On Mon, Feb 18, 2002 at 12:43:18PM -0800, Matthew Dillon said words to the effect of; > :What John's patch does is spin while the lock owner is running on another cpu. > :Spinning while there are no other processes on the run queues as well makes sense > :but you'll also be doing a lot of acquires and releases of sched_lock. > : > :The only thing that jumped out at me looking at the patch is that critnest cannot > :be 0 here because the sched_lock is held; holding a spin lock implies being in a > :critical section. I need to think about this more and would like you to wait until > :John has a chance to look at it as well. > : > :Jake > > Sure thing. Thanks. > Ah, critnest... you are right. I should be checking for > critnest > 1. I think you should just leave it alone, don't check critnest at all. critnest != 1 is illegal because you can't acquire a sleep lock while in an enclosing critical section. Jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 18 12:56:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by hub.freebsd.org (Postfix) with ESMTP id 07B5D37B402 for ; Mon, 18 Feb 2002 12:56:21 -0800 (PST) Received: from fwd01.sul.t-online.de by mailout06.sul.t-online.com with smtp id 16cupf-0004LC-05; Mon, 18 Feb 2002 21:56:19 +0100 Received: from dialin.t-online.de (340029380333-0001@[80.128.218.159]) by fmrl01.sul.t-online.com with esmtp id 16cupV-1CH83GC; Mon, 18 Feb 2002 21:56:09 +0100 Received: from t-online.de (server [172.23.7.1]) by dialin.t-online.de (8.11.6/8.11.6/Rock) with ESMTP id g1IKtpL20892 for ; Mon, 18 Feb 2002 21:55:51 +0100 (MET) Message-ID: <3C716A4D.A0D32693@t-online.de> Date: Mon, 18 Feb 2002 21:55:41 +0100 From: Daniel Rock X-Mailer: Mozilla 4.76 [de] (X11; U; SunOS 5.8 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: current@freebsd.org Subject: two panics with recent -CURRENT Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms859BFAD8838F87FA22C56DEB" X-Sender: 340029380333-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dies ist eine kryptographisch unterzeichnete Nachricht im MIME-Format. --------------ms859BFAD8838F87FA22C56DEB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, during a "make release" run I got two panics in -CURRENT (from Feb 16). Both panics occured during high I/O rates. The first one occured while mkisofs'ing the resulting release CD tree, The second one while "rm -rf RELEASEDIR". I am now running a kernel from Feb 08, which I believe is OK. I restarted a "make release" and will inform you if this kernel also panics. The relevant file system has soft updates enabled and was newfs'd with default argumengs (just the inode count was reduced). Background fsck is turned off, write cache is disabled. If you need more information, I can give additional detail. Thanks, Daniel ----- Kernel stacktrace from the first panic: IdlePTD at phsyical address 0x004c3000 initial pcb at physical address 0x003f3440 panicstr: allocbuf: buffer not busy panic messages: --- panic: softdep_disk_write_complete: lock is held syncing disks... panic: allocbuf: buffer not busy Uptime: 7h50m21s dumping to dev ad0b, offset 545184 [...] #0 0xc01e7cca in sysctl_kern_dumpdev (oidp=0xc0355c48, arg1=0x104, arg2=-1014061372, req=0x246) at ../../../kern/kern_shutdown.c:483 #1 0xc115754c in ?? () #2 0xc01e7a67 in boot (howto=260) at ../../../kern/kern_shutdown.c:333 #3 0xc01e7ef1 in panic (fmt=0xc0355c48 "allocbuf: buffer not busy") at ../../../kern/kern_shutdown.c:619 #4 0xc021c3ad in allocbuf (bp=0xc38ea6c4, size=16384) at ../../../kern/vfs_bio.c:2418 #5 0xc021c32d in getblk (vp=0xd8334ec0, blkno=11305088, size=16384, slpflag=0, slptimeo=0) at ../../../kern/vfs_bio.c:2361 #6 0xc0219fdc in breadn (vp=0xd8334ec0, blkno=11305088, size=16384, rablkno=0x0, rabsize=0x0, cnt=0, cred=0x0, bpp=0xd7faeb14) at ../../../kern/vfs_bio.c:601 #7 0xc0219fa9 in bread (vp=0xd8334ec0, blkno=11305088, size=16384, cred=0x0, bpp=0xd7faeb14) at ../../../kern/vfs_bio.c:585 #8 0xc02bacd4 in ffs_update (vp=0xd8846900, waitfor=0) at ../../../ufs/ffs/ffs_inode.c:101 #9 0xc02c814a in ffs_fsync (ap=0xd7faeb8c) at ../../../ufs/ffs/ffs_vnops.c:293 #10 0xc02c6712 in ffs_sync (mp=0xc113c400, waitfor=2, cred=0xc0b2ec00, td=0xc03b7780) at ../../../ufs/ffs/ffs_vfsops.c:1050 #11 0xc02272b1 in sync (td=0xc03b7780, uap=0x0) at ../../../kern/vfs_syscalls.c:669 #12 0xc01e767f in boot (howto=256) at ../../../kern/kern_shutdown.c:237 #13 0xc01e7ef1 in panic ( fmt=0xc036d440 "softdep_disk_write_complete: lock is held") at ../../../kern/kern_shutdown.c:619 #14 0xc02c2368 in softdep_disk_write_complete (bp=0xc38e29a4) at ../../../ufs/ffs/ffs_softdep.c:3466 #15 0xc021ca49 in bufdone (bp=0xc38e29a4) at ../../../kern/vfs_bio.c:2799 #16 0xc021f195 in cluster_callback (bp=0xc38d656c) at ../../../kern/vfs_cluster.c:551 #17 0xc021ca27 in bufdone (bp=0xc38d656c) at ../../../kern/vfs_bio.c:2789 #18 0xc021c982 in bufwait (bp=0xc38d656c) at ../../../kern/vfs_bio.c:2730 #19 0xc0173bdd in ad_interrupt (request=0xc187eb00) at ../../../sys/bio.h:106 #20 0xc0168fd2 in ata_intr (data=0xc10dd500) at ../../../dev/ata/ata-all.c:578 #21 0xc01d9ccf in ithread_loop (arg=0xc10e2900) at ../../../kern/kern_intr.c:529 #22 0xc01d8ec8 in fork_exit (callout=0xc01d9b34 , arg=0xc10e2900, frame=0xd7faed48) at ../../../kern/kern_fork.c:777 ----- the second panic: IdlePTD at phsyical address 0x004c3000 initial pcb at physical address 0x003f3440 panicstr: bwrite: buffer is not busy??? panic messages: --- panic: double fault syncing disks... panic: bwrite: buffer is not busy??? Uptime: 11h18m21s dumping to dev ad0b, offset 545184 [...] #0 0xc01e7cca in sysctl_kern_dumpdev (oidp=0xc0355918, arg1=0x104, arg2=537006244, req=0x4046) at ../../../kern/kern_shutdown.c:483 #1 0xc115754c in ?? () #2 0xc01e7a67 in boot (howto=260) at ../../../kern/kern_shutdown.c:333 #3 0xc01e7ef1 in panic (fmt=0xc0355918 "bwrite: buffer is not busy???") at ../../../kern/kern_shutdown.c:619 #4 0xc021a1f3 in bwrite (bp=0xc38da6d4) at ../../../sys/systm.h:241 #5 0xc021b476 in vfs_bio_awrite (bp=0xc38da6d4) at ../../../kern/vfs_bio.c:1535 #6 0xc01b3c1c in spec_fsync (ap=0xc040ce24) at ../../../fs/specfs/spec_vnops.c:351 #7 0xc01b3805 in pfs_write (va=0xc040ce24) at ../../../fs/pseudofs/pseudofs_vnops.c:777 #8 0xc02c6930 in ffs_sync (mp=0xc113c400, waitfor=2, cred=0xc0b2ec00, td=0xc03b7780) at ../../../ufs/ffs/ffs_vfsops.c:1086 #9 0xc02272b1 in sync (td=0xc03b7780, uap=0x0) at ../../../kern/vfs_syscalls.c:669 #10 0xc01e767f in boot (howto=256) at ../../../kern/kern_shutdown.c:237 #11 0xc01e7ef1 in panic (fmt=0xc0379343 "double fault") at ../../../kern/kern_shutdown.c:619 #12 0xc03106cb in dblfault_handler () at ../../../i386/i386/trap.c:871 ----- My dmesg output (from a kernel which i believe is OK): Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #624: Sat Feb 9 18:03:58 CET 2002 root@gate.rock.net:/usr/src/sys/i386/compile/ROCK Preloaded elf kernel "/boot/kernel/kernel" at 0xc04a3000. Calibrating clock(s) ... TSC clock: 300680590 Hz, i8254 clock: 1193178 Hz Timecounter "i8254" frequency 1193178 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 300681343 Hz CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 Features=0x8001bf AMD Features=0x80000800 Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 128M bytes Write Allocate 15-16M bytes: Enable Hardware Write Allocate Control: Disable real memory = 134152192 (131008K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x004ca000 - 0x07fe5fff, 129089536 bytes (31516 pages) avail memory = 125706240 (122760K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fb040 bios32: Entry = 0xfb4c0 (c00fb4c0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xb4f0 pnpbios: Found PnP BIOS data at 0xc00fc130 pnpbios: Entry = f0000:c158 Rev = 1.0 Other BIOS signatures found: random: mem: VESA: information block 56 45 53 41 00 02 0e 6f 00 c0 01 00 00 00 22 00 00 01 40 00 02 01 23 6f 00 c0 2a 6f 00 c0 38 6f 00 c0 00 01 01 01 02 01 03 01 05 01 07 01 08 01 09 01 0b 01 0c 01 10 01 11 01 12 01 13 01 14 01 VESA: 24 mode(s) found VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc0412402 (1000022) VESA: Matrox Graphics Inc. VESA: Matrox MILLENNIUM II 00 null: pci_open(1): mode 1 addr port (0x0cf8) is 0x80005800 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=154110b9) Using $PIR table, 8 entries at 0xc00fdef0 acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. acpi_cpu0: on acpi0 acpi_button0: on acpi0 acpi_pcib0: port 0x4d6,0x40b,0x480-0x48f,0x5000-0x501f,0x4000- 0x403f,0xcf8-0xcff on acpi0 pci0: physical bus=0 map[10]: type 1, range 32, base d0000000, size 28, enabled found-> vendor=0x10b9, dev=0x1541, revid=0x04 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 found-> vendor=0x10b9, dev=0x5243, revid=0x04 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 map[10]: type 1, range 32, base ee102000, size 12, enabled found-> vendor=0x10b9, dev=0x5237, revid=0x03 bus=0, slot=2, func=0 class=0c-03-10, hdrtype=0x00, mfdev=0 intpin=a, irq=11 found-> vendor=0x10b9, dev=0x1533, revid=0xc3 bus=0, slot=7, func=0 class=06-01-00, hdrtype=0x00, mfdev=0 map[10]: type 4, range 32, base 0000e000, size 8, enabled map[14]: type 1, range 32, base ee101000, size 8, enabled found-> vendor=0x1000, dev=0x0004, revid=0x04 bus=0, slot=8, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=10 map[10]: type 3, range 32, base ee100000, size 12, enabled map[14]: type 4, range 32, base 0000e400, size 5, enabled map[18]: type 1, range 32, base ee000000, size 20, enabled found-> vendor=0x8086, dev=0x1229, revid=0x05 bus=0, slot=9, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=12 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 0000e800, size 8, enabled map[14]: type 1, range 32, base ee103000, size 8, enabled found-> vendor=0x10ec, dev=0x8139, revid=0x10 bus=0, slot=10, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=9 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 3, range 32, base ea000000, size 24, enabled map[14]: type 1, range 32, base eb000000, size 14, enabled map[18]: type 1, range 32, base ec000000, size 23, enabled found-> vendor=0x102b, dev=0x051b, revid=0x00 bus=0, slot=11, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=9 map[20]: type 4, range 32, base 0000f000, size 4, enabled found-> vendor=0x10b9, dev=0x5229, revid=0xc1 bus=0, slot=15, func=0 class=01-01-fa, hdrtype=0x00, mfdev=0 intpin=a, irq=0 pci0: on acpi_pcib0 agp0: mem 0xd0000000-0xdfffffff at device 0.0 on pci0 agp0: allocating GATT for aperture of size 256M pcib1: at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xf000-0xfff pcib1: memory decode 0xfff00000-0xfffff pcib1: prefetched decode 0xfff00000-0xfffff pci1: physical bus=1 pci1: on pcib1 ohci0: mem 0xee102000-0xee102fff irq 11 at device 2.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered isab0: at device 7.0 on pci0 isa0: on isab0 sym0: <815> port 0xe000-0xe0ff mem 0xee101000-0xee1010ff irq 10 at device 8.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-10, SE, parity checking sym0: open drain IRQ line driver sym0: using NCR-generic firmware. sym0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 03/8a/80/00/00/00 sym0: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 03/ca/00/00/08/00 sym0: Delay (GEN=11): 281 msec, 31631 KHz sym0: Delay (GEN=11): 281 msec, 31631 KHz sym0: Delay (GEN=11): 281 msec, 31631 KHz fxp0: port 0xe400-0xe41f mem 0xee000000-0xee0f ffff,0xee100000-0xee100fff irq 12 at device 9.0 on pci0 fxp0: using memory space register mapping fxp0: Ethernet address 00:a0:c9:ef:69:8d fxp0: PCI IDs: 8086 1229 8086 0009 0005 fxp0: Dynamic Standby mode is disabled inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bpf: fxp0 attached rl0: port 0xe800-0xe8ff mem 0xee103000-0xee1030ff ir q 9 at device 10.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:e0:7d:75:fd:fb miibus1: on rl0 rlphy0: on miibus1 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bpf: rl0 attached pci0: at device 11.0 (no driver attached) atapci0: port 0xf000-0xf00f irq 0 at device 15.0 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000 ata0: mask=03 ostat0=50 ostat2=00 ata0-master: ATAPI 00 00 ata0-slave: ATAPI 00 00 ata0: mask=03 stat0=50 stat1=00 ata0-master: ATA 01 a5 ata0: devices=01 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xf008 ata1: mask=03 ostat0=50 ostat2=00 ata1-master: ATAPI 00 00 ata1-slave: ATAPI 00 00 ata1: mask=03 stat0=50 stat1=00 ata1-master: ATA 01 a5 ata1: devices=01 ata1: at 0x170 irq 15 on atapci0 fdc0: port 0x3f7,0x3f2-0 x3f5 irq 6 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: irq maps: 0x201 0x211 0x201 0x201 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A, console sio1: irq maps: 0x201 0x209 0x201 0x201 sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) ppc0: using extended I/O port range ppc0: ECP SPP ECP+EPP SPP ppc0 port 0x778-0x77b,0x378-0x37f irq 7 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/1 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 unknown: not probed (disabled) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 kbd0: atkbd0, generic (0), config:0x0, flags:0x1f0000 unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) npx0: on motherboard npx0: INT 16 interface sio: sio0 already exists; skipping it Trying Read_Port at 203 SAG0001: start dependent (1) SAG0001: adding io range 0x100-0x3f7, size=0x8, align=0x8 SAG0001: adding irq mask 0xbcb8 SAG0001: start dependent (1) SAG0001: adding io range 0x100-0x3f7, size=0x8, align=0x8 SAG0001: adding irq mask 0x20 SAG0001: start dependent (1) SAG0001: adding io range 0x100-0x3f7, size=0x8, align=0x8 SAG0001: adding irq mask 0x80 SAG0001: end dependent isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: Nouvelle page 2

Un ancien= repris de justice reçoit
d'un des 10 hommes les plus riches du mo= nde
l'ancien manuscrit secret des 7 pierres des Andes
qui ont plus de 6000 ans d'âge et
il devient milliardaire en dollars à son tour.

Pour en savoir d'avantage, à= propos de cette histoire hors du commun, il vous suffit simplement d'envoy= er un e-mail à l'adresse : 7pierres@wanadoo.fr=

Votre adresse fait partie d'une mailing-list à la suite de votre inscription ou de votre présence publique sur Internet. Nous nous eff= orçons de maintenir des listes de diffusion de qualité et d'éviter le S= pam. C’est pourquoi nous vous présentons nos excuses si ce mail vous a déra= ngé. Si ce mail vous a atteint par erreur et si vous souhaitez ne plus jamais recevoi= r de message de notre part et sortir immédiatement de nos listes, il vous = suffit simplement d'envoyer un mail en cliquant sur l’adresse : sortir-liste@wanadoo.fr=

Your address is listed because of your subscription to a list or becaus= e of your public presence on Internet. We are permanently monitoring the qua= lity of our mailing-lists to avoid Spam. We apologize for any disturbance. If this mail hits your inbox by error and/or if you do not wish to receive an= y other e-mail from us, you can unsubscribe from our lists by sending an ema= il to : sortir-liste@wanadoo.fr

 --5682426646345761-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 19 11:32:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 5403637B400 for ; Tue, 19 Feb 2002 11:32:16 -0800 (PST) Received: from [212.238.194.207] (helo=mailhost.raggedclown.net) by post.mail.nl.demon.net with esmtp (Exim 3.33 #1) id 16dFzp-00078S-00 for current@freebsd.org; Tue, 19 Feb 2002 19:32:13 +0000 Received: from angel.raggedclown.net (angel.raggedclown.intra [192.168.1.7]) by mailhost.raggedclown.net (Ragged Clown Mail Gateway [buffy]) with ESMTP id D27D413040 for ; Tue, 19 Feb 2002 20:32:11 +0100 (CET) Received: by angel.raggedclown.net (Ragged Clown Host [angel], from userid 6002) id B8ED022596; Tue, 19 Feb 2002 20:32:11 +0100 (CET) Date: Tue, 19 Feb 2002 20:32:11 +0100 From: Cliff Sarginson To: current@freebsd.org Subject: Re: more -current testers Message-ID: <20020219193211.GA1785@raggedclown.net> References: <20020219125011.A15871@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020219125011.A15871@blackhelicopters.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Feb 19, 2002 at 12:50:11PM -0500, Michael Lucas wrote: > I understand that we're getting to that stage where we need more > -current testers. > > We all agree that the optimal thing would be to have hordes of very > sophisticated users who can debug problems on their own and submit > patches to fix all their issues. I would guess that we all also agree > that that's not going to happen. > > It seems that the best we can hope for is to educate some of the > braver users who are ready to take the next step and are willing to > donate some time to us. > > I'm considering doing a series of articles on testing FreeBSD-current, > including: setting up for kernel dumps, what to type at the debugger > prompt after a crash, filing a decent bug report, what to expect from > -current, and so on. I would also make it clear when to not bother > filing a bug report (i.e., "You crashed, but had no WITNESS? Sorry, > enable WITNESS & try again."). This would be (I suspect) three > articles, running about a month and a half. > > The last time I checked, I get 12-15 thousand readers for each > article. One half of one percent uptake would (hopefully) be quite a > few bug reports. > > My question to the community is: is it too early to do this? If I > start now, the articles would probably appear April-May. I think this is an absolutely splendid idea :) I have enough resources to run a STABLE system for my day-to-day use and also have a -CURRENT system I am more than willing to spend some time on. I think some good pointers on what is required to provide useful feedback (as opposed to bug reports that are not adequately filled in) and some practical tips would really encourage people. My first question is who or what is WITNESS :) -- Regards Cliff Sarginson -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 19 12:40:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from msp-26-175-126.mn.rr.com (msp-26-175-126.mn.rr.com [24.26.175.126]) by hub.freebsd.org (Postfix) with ESMTP id 65B2C37B400 for ; Tue, 19 Feb 2002 12:40:38 -0800 (PST) Received: from ACHIWERE ([192.168.0.10]) by msp-26-175-126.mn.rr.com (8.11.6/8.11.6) with ESMTP id g1JKhDV04064 for ; Tue, 19 Feb 2002 14:43:13 -0600 (CST) (envelope-from smokeyser@msp-26-175-126.mn.rr.com) From: "Smokey DeWeed" To: Subject: RE: more -current testers Date: Tue, 19 Feb 2002 14:40:31 -0600 Message-ID: <001601c1b985$b27a6840$0a00a8c0@ACHIWERE> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <20020219193211.GA1785@raggedclown.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I run FreeBSD both at home and at work and I'd be happy to provide feedback on any bugs I come across. Your article on debugging and submitting a "proper" bug report would be helpful in making sure that any info I submit is useful. And I'm sure that there's a thousand others reading this and thinking the same thing. Keep up the good work. :) On Tue, Feb 19, 2002 at 12:50:11PM -0500, Michael Lucas wrote: > I understand that we're getting to that stage where we need more > -current testers. > > We all agree that the optimal thing would be to have hordes of very > sophisticated users who can debug problems on their own and submit > patches to fix all their issues. I would guess that we all also agree > that that's not going to happen. > > It seems that the best we can hope for is to educate some of the > braver users who are ready to take the next step and are willing to > donate some time to us. > > I'm considering doing a series of articles on testing FreeBSD-current, > including: setting up for kernel dumps, what to type at the debugger > prompt after a crash, filing a decent bug report, what to expect from > -current, and so on. I would also make it clear when to not bother > filing a bug report (i.e., "You crashed, but had no WITNESS? Sorry, > enable WITNESS & try again."). This would be (I suspect) three > articles, running about a month and a half. > > The last time I checked, I get 12-15 thousand readers for each > article. One half of one percent uptake would (hopefully) be quite a > few bug reports. > > My question to the community is: is it too early to do this? If I > start now, the articles would probably appear April-May. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 19 12:51:57 2002 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 7255A37B404 for ; Tue, 19 Feb 2002 12:51:52 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g1JKppi89896; Tue, 19 Feb 2002 13:51:51 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g1JKphL73687; Tue, 19 Feb 2002 13:51:44 -0700 (MST) (envelope-from imp@village.org) Date: Tue, 19 Feb 2002 13:51:31 -0700 (MST) Message-Id: <20020219.135131.83283562.imp@village.org> To: davidx@viasoft.com.cn Cc: julian@elischer.org, peter@wemm.org, current@FreeBSD.ORG Subject: Re: Patch sets to date and timing tests with Giant out of userret. From: "M. Warner Losh" In-Reply-To: <00cd01c1b926$82d35bb0$ef01a8c0@davidwnt> References: <20020219080019.8F1673A9A@overcee.wemm.org> <00cd01c1b926$82d35bb0$ef01a8c0@davidwnt> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <00cd01c1b926$82d35bb0$ef01a8c0@davidwnt> "David Xu" writes: : Sorry for a bit OT, is Perforce a free software? if it is not, why : do we need to use this property software? Because it is useful. And all the other alternative suck too bad to even try at this time. Bitkeeper enforces the linux devleopment model to a large extent, subversion and arch look promsing, but have growing pains and second system syndrome to battle. Perforce is available today for free for free software development. You can't get source, but it doesn't cost anything for the use to which we're putting it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 19 13:30:40 2002 Delivered-To: freebsd-current@freebsd.org Received: from mao.stokely.org (mao.stokely.org [65.84.64.228]) by hub.freebsd.org (Postfix) with ESMTP id 7148437B402; Tue, 19 Feb 2002 13:30:37 -0800 (PST) Received: by mao.stokely.org (Postfix, from userid 2074) id DDF414B65D; Tue, 19 Feb 2002 13:08:31 -0800 (PST) Date: Tue, 19 Feb 2002 13:08:31 -0800 From: Murray Stokely To: Jan Stocker Cc: Murray Stokely , current@FreeBSD.ORG Subject: Re: HEADS UP: DHCP 3.0.1RC6 imported Message-ID: <20020219210831.GB10706@freebsdmall.com> References: <20020219150724.GA10706@freebsdmall.com> <000e01c1b969$262d6b60$fe02010a@twoflower.liebende.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000e01c1b969$262d6b60$fe02010a@twoflower.liebende.de> User-Agent: Mutt/1.3.25i X-GPG-Key-ID: 1024D/0E451F7D X-GPG-Key-Fingerprint: E2CA 411D DD44 53FD BB4B 3CB5 B4D7 10A2 0E45 1F7D Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Feb 19, 2002 at 06:16:20PM +0100, Jan Stocker wrote: > I am using isc-dhcp3-3.0.r12 with DDNS on my FreeBSD 4.3 router a long time > and have no problem. Shall this msg mean the port is completly integrated in > freebsd 5? Only the client is built as part of the base system. I think that the new DHCP management shell, omshell, probably belongs in /usr/sbin, but as of right now you just get /sbin/dhclient as before. - Murray To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 19 14:26: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from neptune.deep-ocean.net (APastourelles-102-1-2-208.abo.wanadoo.fr [217.128.208.208]) by hub.freebsd.org (Postfix) with ESMTP id 8B8D537B404 for ; Tue, 19 Feb 2002 14:25:54 -0800 (PST) Received: by neptune.deep-ocean.net (Postfix, from userid 1000) id 266485EF05; Tue, 19 Feb 2002 23:25:53 +0100 (CET) Date: Tue, 19 Feb 2002 23:25:53 +0100 From: Olivier Cortes To: freebsd-current@freebsd.org Subject: Re: more -current testers Message-ID: <20020219232553.F21763@neptune.deep-ocean.local> Mail-Followup-To: Olivier Cortes , freebsd-current@freebsd.org References: <20020219125011.A15871@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020219125011.A15871@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Tue, Feb 19, 2002 at 12:50:11PM -0500 X-Operating-System: FreeBSD 4.5-STABLE i386 up 1 day, 6:27, 1 user, load averages: 0.04, 0.03, 0.02 Organization: Deep-Ocean Network X-URL: http://www.deep-ocean.org/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, i'm a freelance sys/net admin/architect who works with bsd (free/open) in France (Paris/Bordeaux). i'm reading your columns very regularly. Your writing are easy to understand and that's a good point ! I'm (for now) just following mailing lists (security, hackers, stable, current) and i want to help. I'm making progress slowly but surely. Soon i will be quite mature with bsd, and i will be able to report bugs, and later debug (at this time i'm playing with cvs and making worlds). if you write some docs, i will read them, and i will have time to report some bugs if you tell me how to do it right. I'm sticking with stable now (compiling once a day), but it's been times since i wanted to help the -current project; but i wouldn't have been efficient so i didn't do it. from my point of view, it is NOT too early. Go ahead !!! I think i'll be ready when your doc are finished. I understand that's it is only my point of view (and i can be considered as zero helper / poor joe user), but hey, it's one more potential tester :-) Even if i can't support what you (developpers) do the way you would like, i really appreciate the work you do on FreeBSD, and i try to show it by using and installing FreeBSD. Thanks ! Olivier (saturday i will buy a serial cable to start playing with ;-) ) On Tue, Feb 19, 2002 at 12:50:11PM -0500, Michael Lucas wrote: > I understand that we're getting to that stage where we need more > -current testers. > > We all agree that the optimal thing would be to have hordes of very > sophisticated users who can debug problems on their own and submit > patches to fix all their issues. I would guess that we all also agree > that that's not going to happen. > > It seems that the best we can hope for is to educate some of the > braver users who are ready to take the next step and are willing to > donate some time to us. > > I'm considering doing a series of articles on testing FreeBSD-current, > including: setting up for kernel dumps, what to type at the debugger > prompt after a crash, filing a decent bug report, what to expect from > -current, and so on. I would also make it clear when to not bother > filing a bug report (i.e., "You crashed, but had no WITNESS? Sorry, > enable WITNESS & try again."). This would be (I suspect) three > articles, running about a month and a half. > > The last time I checked, I get 12-15 thousand readers for each > article. One half of one percent uptake would (hopefully) be quite a > few bug reports. > > My question to the community is: is it too early to do this? If I > start now, the articles would probably appear April-May. > > Thanks, > Michael > > -- > Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org > my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons > > http://www.blackhelicopters.org/~mwlucas/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Olivier Cortes GPG 1024/46CE0A51 : 8DB6 A56C 00CA DA0F F77F 86EB E86A 803C 46CE 0A51 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 19 16: 6:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id BD06437B41F; Tue, 19 Feb 2002 16:06:26 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 58C445343; Wed, 20 Feb 2002 01:06:25 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Maxim Sobolev Cc: current@FreeBSD.org Subject: Re: Either PAM or login is broken References: <3C72944A.8C6EDF79@FreeBSD.org> <3C729655.27B995F2@FreeBSD.org> From: Dag-Erling Smorgrav Date: 20 Feb 2002 01:06:24 +0100 In-Reply-To: <3C729655.27B995F2@FreeBSD.org> Message-ID: Lines: 16 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-=-= Maxim Sobolev writes: > Ok, I've found the problem - it appears that my machine didn't have a > /var/log/lastlog file and so far pam_lastlog.so was quite happy with > this situation, while after a make world it doesn't tolerate it > anymore. I am not sure that such POLA change is good and IMO > pam_lastlog.so shouldn't refuse login just because there is no > /var/log/lastlog file or at least it should create the file by itself. See attached patch. Please commit it if it solves your problem. DES -- Dag-Erling Smorgrav - des@ofug.org --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=pam_lastlog.diff Index: pam_lastlog.c =================================================================== RCS file: /home/ncvs/src/lib/libpam/modules/pam_lastlog/pam_lastlog.c,v retrieving revision 1.6 diff -u -r1.6 pam_lastlog.c --- pam_lastlog.c 5 Feb 2002 06:08:25 -0000 1.6 +++ pam_lastlog.c 20 Feb 2002 00:04:20 -0000 @@ -149,7 +149,7 @@ if (tty == NULL) PAM_RETURN(PAM_SERVICE_ERR); - fd = open(_PATH_LASTLOG, O_RDWR, 0); + fd = open(_PATH_LASTLOG, O_RDWR|O_CREAT, 0644); if (fd == -1) { syslog(LOG_ERR, "cannot open %s: %m", _PATH_LASTLOG); PAM_RETURN(PAM_SERVICE_ERR); --=-=-=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 19 16:48: 3 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 1A0A937B400 for ; Tue, 19 Feb 2002 16:48:00 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g1K0kuS29788; Tue, 19 Feb 2002 16:46:56 -0800 (PST) (envelope-from obrien) Date: Tue, 19 Feb 2002 16:42:52 -0800 From: "David O'Brien" To: Dag-Erling Smorgrav Cc: Garrett Rooney , Julian Elischer , David Xu , Peter Wemm , current@FreeBSD.ORG Subject: Re: Patch sets to date and timing tests with Giant out of userret. Message-ID: <20020219164252.A29698@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20020219151845.GA13590@electricjellyfish.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Tue, Feb 19, 2002 at 04:30:43PM +0100 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Feb 19, 2002 at 04:30:43PM +0100, Dag-Erling Smorgrav wrote: > > it's problematic to do an apr port at this time because there is no > > stable release of apr, and subversion requires bleeding edge apr to > > function anyway. > > *shrug* so we need a port of a devel version of apr. It's what the > scientific community calls an "engineering problem" :) Please name it "apr-snapshot" or "apr-beta" rather than -devel if you do. One never is sure what "devel" is supose to mean -- something used in development, or an in-development version. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 19 16:48:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 94A0C37B41A for ; Tue, 19 Feb 2002 16:48:20 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g1K0mAQ29810; Tue, 19 Feb 2002 16:48:10 -0800 (PST) (envelope-from obrien) Date: Tue, 19 Feb 2002 16:44:06 -0800 From: "David O'Brien" To: "M. Warner Losh" Cc: current@FreeBSD.ORG Subject: Re: Patch sets to date and timing tests with Giant out of userret. Message-ID: <20020219164406.B29698@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20020219080019.8F1673A9A@overcee.wemm.org> <00cd01c1b926$82d35bb0$ef01a8c0@davidwnt> <20020219.135131.83283562.imp@village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020219.135131.83283562.imp@village.org>; from imp@village.org on Tue, Feb 19, 2002 at 01:51:31PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Feb 19, 2002 at 01:51:31PM -0700, M. Warner Losh wrote: > Bitkeeper enforces the linux devleopment model > to a large extent, In what way(s)? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 19 16:59:58 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 7D5FA37B404; Tue, 19 Feb 2002 16:59:54 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 93D3F5341; Wed, 20 Feb 2002 01:59:51 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: obrien@FreeBSD.ORG Cc: Garrett Rooney , Julian Elischer , David Xu , Peter Wemm , current@FreeBSD.ORG Subject: Re: Patch sets to date and timing tests with Giant out of userret. References: <20020219151845.GA13590@electricjellyfish.net> <20020219164252.A29698@dragon.nuxi.com> From: Dag-Erling Smorgrav Date: 20 Feb 2002 01:59:49 +0100 In-Reply-To: <20020219164252.A29698@dragon.nuxi.com> Message-ID: Lines: 14 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "David O'Brien" writes: > On Tue, Feb 19, 2002 at 04:30:43PM +0100, Dag-Erling Smorgrav wrote: > > *shrug* so we need a port of a devel version of apr. It's what the > > scientific community calls an "engineering problem" :) > Please name it "apr-snapshot" or "apr-beta" rather than -devel if you do. > One never is sure what "devel" is supose to mean -- something used in > development, or an in-development version. Actually, we figured out that we'd just link apr statically into the subversion binaries, so there is no need (yet) for an apr port. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 19 17:16:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from isris.pair.com (isris.pair.com [209.68.2.39]) by hub.freebsd.org (Postfix) with SMTP id BBC9437B402 for ; Tue, 19 Feb 2002 17:16:09 -0800 (PST) Received: (qmail 84628 invoked by uid 3130); 20 Feb 2002 01:16:08 -0000 Date: Tue, 19 Feb 2002 20:16:08 -0500 From: Garrett Rooney To: Dag-Erling Smorgrav Cc: obrien@FreeBSD.ORG, Julian Elischer , David Xu , Peter Wemm , current@FreeBSD.ORG Subject: Re: Patch sets to date and timing tests with Giant out of userret. Message-ID: <20020220011608.GA48161@electricjellyfish.net> References: <20020219151845.GA13590@electricjellyfish.net> <20020219164252.A29698@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.25i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Feb 20, 2002 at 01:59:49AM +0100, Dag-Erling Smorgrav wrote: > "David O'Brien" writes: > > On Tue, Feb 19, 2002 at 04:30:43PM +0100, Dag-Erling Smorgrav wrote: > > > *shrug* so we need a port of a devel version of apr. It's what the > > > scientific community calls an "engineering problem" :) > > Please name it "apr-snapshot" or "apr-beta" rather than -devel if you do. > > One never is sure what "devel" is supose to mean -- something used in > > development, or an in-development version. > > Actually, we figured out that we'd just link apr statically into the > subversion binaries, so there is no need (yet) for an apr port. I've got a version of the port that links statically, so if people think that's enough for now, we can go with that, but I've also got the apache people to put up a tarball of apr, so I'm putting together an apr-snapshot port as well, since subversion provides a bunch of C libraries that are less than useful without apr. -garrett -- garrett rooney Unix was not designed to stop you from rooneg@electricjellyfish.net doing stupid things, because that would http://electricjellyfish.net/ stop you from doing clever things. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 19 17:22:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 7868837B404; Tue, 19 Feb 2002 17:22:08 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id EBC9A5343; Wed, 20 Feb 2002 02:22:05 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Garrett Rooney Cc: obrien@FreeBSD.ORG, Julian Elischer , David Xu , Peter Wemm , current@FreeBSD.ORG Subject: Re: Patch sets to date and timing tests with Giant out of userret. References: <20020219151845.GA13590@electricjellyfish.net> <20020219164252.A29698@dragon.nuxi.com> <20020220011608.GA48161@electricjellyfish.net> From: Dag-Erling Smorgrav Date: 20 Feb 2002 02:22:05 +0100 In-Reply-To: <20020220011608.GA48161@electricjellyfish.net> Message-ID: Lines: 14 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Garrett Rooney writes: > I've got a version of the port that links statically, so if people > think that's enough for now, we can go with that, but I've also got > the apache people to put up a tarball of apr, so I'm putting together > an apr-snapshot port as well, since subversion provides a bunch of C > libraries that are less than useful without apr. Well, let's have the static version so we can play with it - you can always make it dynamic later when the apr-snapshot port is done. Mail me the diffs and I'll commit them. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 19 21: 8:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.sat.t.u-tokyo.ac.jp (nat.keisu.t.u-tokyo.ac.jp [133.11.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 3051A37B405 for ; Tue, 19 Feb 2002 21:08:43 -0800 (PST) Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [10.6.1.30]) by mail.sat.t.u-tokyo.ac.jp (Postfix) with ESMTP id E60DB2DABB; Wed, 20 Feb 2002 14:08:41 +0900 (JST) Date: Wed, 20 Feb 2002 14:08:41 +0900 Message-ID: From: Hidetoshi Shimokawa To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: module build process changed In-Reply-To: <20020110173500.A10785@hub.freebsd.org> References: <20020110173500.A10785@hub.freebsd.org> User-Agent: Wanderlust/2.4.1 (Stand By Me) REMI/1.14.3 (Matsudai) FLIM/1.13.2 (Kasanui) APEL/10.3 MULE XEmacs/21.2 (beta19) (Shinjuku) (i386-unknown-freebsd3.2) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7:#j7i14gu$ jgR\S*&C3R/pJX List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At Thu, 10 Jan 2002 17:35:00 -0800, Mike Smith wrote: > In order to deal with this problem, I have changed the module build > process so that symbols global to the module are converted to local > symbols when the module is linked into the .kld/,ko file. In order > to allow modules that intentionally export symbols to continue to do > so, a new module makefile variable 'EXPORT_SYMS' has been implemented. Hi Mike, I don' think EXPORT_SYMS works right. EXPORT_SYMS= fw_asybusy \ fw_asyreq \ fw_bindadd \ getcsrdata \ fw_xfer_alloc \ fw_xfer_free \ By this configuration, /sys/conf/kmod.mk generates space separated list to export_syms like this: fw_asybusy fw_asyreq fw_bindadd getcsrdata fw_xfer_alloc fw_xfer_free But /sys/conf/kmod_syms.awk expects 'line break' separated list. And we cannot export any symbols. For example, Remove ppbus/plip/lpt/ppi/ppc from you kernel config. Can you load ppbus and it's childen by kldload? Even if this problem is fixed, I suppose another problem there. Even if I set EXPORT_SYMS=YES, I cannot resolv module symbols. e.g. kldload module1 kldload module2 module2 cannnot resolv symbols in module1. -stable doesn't have this problem. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 19 21:41:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id 262C337B405 for ; Tue, 19 Feb 2002 21:41:12 -0800 (PST) Received: from peter3.wemm.org ([12.232.27.13]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020220054111.BHUT1214.rwcrmhc54.attbi.com@peter3.wemm.org> for ; Wed, 20 Feb 2002 05:41:11 +0000 Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id g1K5fBs39720 for ; Tue, 19 Feb 2002 21:41:11 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (Postfix) with ESMTP id 5648339F1; Tue, 19 Feb 2002 21:41:11 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Hidetoshi Shimokawa Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: HEADS UP: module build process changed In-Reply-To: Date: Tue, 19 Feb 2002 21:41:11 -0800 From: Peter Wemm Message-Id: <20020220054111.5648339F1@overcee.wemm.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hidetoshi Shimokawa wrote: > At Thu, 10 Jan 2002 17:35:00 -0800, > Mike Smith wrote: > > In order to deal with this problem, I have changed the module build > > process so that symbols global to the module are converted to local > > symbols when the module is linked into the .kld/,ko file. In order > > to allow modules that intentionally export symbols to continue to do > > so, a new module makefile variable 'EXPORT_SYMS' has been implemented. > > Hi Mike, > [... pass on this stuff ...] > Even if this problem is fixed, I suppose another problem there. > Even if I set EXPORT_SYMS=YES, I cannot resolv module symbols. > e.g. > > kldload module1 > kldload module2 > > module2 cannnot resolv symbols in module1. > > -stable doesn't have this problem. module2 cannot resolve symbols in module1 unless there is a declared dependency. This is intentional, otherwise there is no way to check that module1 is not unloaded while module2 is using it. Stable is lacking this enforcement. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 19 22: 1:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.sat.t.u-tokyo.ac.jp (nat.keisu.t.u-tokyo.ac.jp [133.11.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 404E537B446 for ; Tue, 19 Feb 2002 22:00:53 -0800 (PST) Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [10.6.1.30]) by mail.sat.t.u-tokyo.ac.jp (Postfix) with ESMTP id 2A25B2DABB; Wed, 20 Feb 2002 15:00:52 +0900 (JST) Date: Wed, 20 Feb 2002 15:00:52 +0900 Message-ID: From: Hidetoshi Shimokawa To: Peter Wemm Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: HEADS UP: module build process changed In-Reply-To: <20020220054111.5648339F1@overcee.wemm.org> References: <20020220054111.5648339F1@overcee.wemm.org> User-Agent: Wanderlust/2.4.1 (Stand By Me) REMI/1.14.3 (Matsudai) FLIM/1.13.2 (Kasanui) APEL/10.3 MULE XEmacs/21.2 (beta19) (Shinjuku) (i386-unknown-freebsd3.2) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7:#j7i14gu$ jgR\S*&C3R/pJX List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At Tue, 19 Feb 2002 21:41:11 -0800, Peter Wemm wrote: > > e.g. > > > > kldload module1 > > kldload module2 > > > > module2 cannnot resolv symbols in module1. > > > > -stable doesn't have this problem. > > module2 cannot resolve symbols in module1 unless there is a declared > dependency. This is intentional, otherwise there is no way to check that > module1 is not unloaded while module2 is using it. Stable is lacking this > enforcement. Thanks for the information. Could you point me an example code how to declare dependency? In my environment module1 is firewire bus drivier, module2 is sbp driver. module1: DRIVER_MODULE(firewire,fwohci,firewire_driver,firewire_devclass,0,0); module2: DRIVER_MODULE(sbp, firewire, sbp_driver, sbp_devclass, 0, 0); /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 0: 0:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 6E58A37B405 for ; Wed, 20 Feb 2002 00:00:14 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020220080014.EKOE2951.rwcrmhc53.attbi.com@InterJet.elischer.org>; Wed, 20 Feb 2002 08:00:14 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA61063; Tue, 19 Feb 2002 23:57:18 -0800 (PST) Date: Tue, 19 Feb 2002 23:57:16 -0800 (PST) From: Julian Elischer To: "George V. Neville-Neil" Cc: freebsd-current@freebsd.org Subject: Re: Kernel Debugging over the Ethernet? In-Reply-To: <200202200536.VAA258019@meer.meer.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 19 Feb 2002, George V. Neville-Neil wrote: > Hi Folks, > > Now that Luigi has put in polling support for some ethernet drivers > I was wondering how much work it would be to make the remote kernel debugging > run over the ethernet. I have worked on systems like this before (it's the > reason > I did polling network device drivers in Wind River's VxWorks) but it depends > on a debugging system that has the ability to have its back end swapped out. > > Who would I talk to about how kernel debugging works at the > lowest layers right now? Which source files should I look at first. the gdb debugging piggybacks onto the ddb debugger the file i386/i386/i386-gdbstub.c gives the basic interface for the serial connection. the serial part is in /sys/dev/sio/sio.c I don't know what gdb does on the ethernet but my guess is that it's already written there somewhere. I guess using udp packets with an address set by a sysctl would be sufficient, especially if we had our own udp handler (which I'm told can be done in a very small amount of code it we know what packets we are getting). > > Thanks, > George > > -- > George V. Neville-Neil gnn@neville-neil.com > NIC:GN82 > > "Those who would trade liberty for temporary security deserve neither" > - Benjamin Franklin > > > > 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 Feb 20 0:27:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from ix.rain.fr (ix.rain.fr [194.51.3.175]) by hub.freebsd.org (Postfix) with ESMTP id 93D9237B400 for ; Wed, 20 Feb 2002 00:27:07 -0800 (PST) Received: from rain.fr (localhost [127.0.0.1]) by ix.rain.fr (8.11.6/8.11.6) with ESMTP id g1K8Qiu63508 for ; Wed, 20 Feb 2002 09:26:59 +0100 (CET) (envelope-from tfischer@rain.fr) Message-ID: <3C735DC4.10805@rain.fr> Date: Wed, 20 Feb 2002 09:26:44 +0100 From: Tom Fischer Organization: Equant User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.8) Gecko/20020218 X-Accept-Language: en-us MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: more -current testers References: <20020219125011.A15871@blackhelicopters.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, These proposed articles can only help. I've been following this list for a few years, I'm ready to contribute in my own small way :-) tom tfischer@rain.fr Michael Lucas wrote: > I understand that we're getting to that stage where we need more > -current testers. > > We all agree that the optimal thing would be to have hordes of very > sophisticated users who can debug problems on their own and submit > patches to fix all their issues. I would guess that we all also agree > that that's not going to happen. > > It seems that the best we can hope for is to educate some of the > braver users who are ready to take the next step and are willing to > donate some time to us. > > I'm considering doing a series of articles on testing FreeBSD-current, > including: setting up for kernel dumps, what to type at the debugger > prompt after a crash, filing a decent bug report, what to expect from > -current, and so on. I would also make it clear when to not bother > filing a bug report (i.e., "You crashed, but had no WITNESS? Sorry, > enable WITNESS & try again."). This would be (I suspect) three > articles, running about a month and a half. > > The last time I checked, I get 12-15 thousand readers for each > article. One half of one percent uptake would (hopefully) be quite a > few bug reports. > > My question to the community is: is it too early to do this? If I > start now, the articles would probably appear April-May. > > Thanks, > Michael > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 0:56:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id 8130037B405 for ; Wed, 20 Feb 2002 00:56:26 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id KAA58782; Wed, 20 Feb 2002 10:56:08 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (h208.228.dialup.iptcom.net [212.9.228.208]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id KAA00554; Wed, 20 Feb 2002 10:56:05 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g1K8tXX02149; Wed, 20 Feb 2002 10:55:33 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3C7364A5.4600F8F5@FreeBSD.org> Date: Wed, 20 Feb 2002 10:56:05 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Michael Lucas Cc: current@FreeBSD.org Subject: Re: more -current testers References: <20020219125011.A15871@blackhelicopters.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Michael Lucas wrote: > > I understand that we're getting to that stage where we need more > -current testers. > > We all agree that the optimal thing would be to have hordes of very > sophisticated users who can debug problems on their own and submit > patches to fix all their issues. I would guess that we all also agree > that that's not going to happen. > > It seems that the best we can hope for is to educate some of the > braver users who are ready to take the next step and are willing to > donate some time to us. > > I'm considering doing a series of articles on testing FreeBSD-current, > including: setting up for kernel dumps, what to type at the debugger > prompt after a crash, filing a decent bug report, what to expect from > -current, and so on. I would also make it clear when to not bother > filing a bug report (i.e., "You crashed, but had no WITNESS? Sorry, > enable WITNESS & try again."). This would be (I suspect) three > articles, running about a month and a half. > > The last time I checked, I get 12-15 thousand readers for each > article. One half of one percent uptake would (hopefully) be quite a > few bug reports. Excellent idea IMO. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 1: 7:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id DF5DC37B405 for ; Wed, 20 Feb 2002 01:07:06 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA71129; Wed, 20 Feb 2002 11:06:31 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (h149.228.dialup.iptcom.net [212.9.228.149]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id LAA07472; Wed, 20 Feb 2002 11:06:27 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g1K95uX08065; Wed, 20 Feb 2002 11:05:56 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3C736713.B30E247B@FreeBSD.org> Date: Wed, 20 Feb 2002 11:06:27 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Julian Elischer Cc: "George V. Neville-Neil" , freebsd-current@FreeBSD.org, Jonathan Lemon Subject: Re: Kernel Debugging over the Ethernet? References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If my memory serves some time ago Jonathan Lemon was planning to add ability to remotely debug kernel via TCP/IP. Try to contact him and ask about the status of his work. -Maxim Julian Elischer wrote: > > On Tue, 19 Feb 2002, George V. Neville-Neil wrote: > > > Hi Folks, > > > > Now that Luigi has put in polling support for some ethernet drivers > > I was wondering how much work it would be to make the remote kernel debugging > > run over the ethernet. I have worked on systems like this before (it's the > > reason > > I did polling network device drivers in Wind River's VxWorks) but it depends > > on a debugging system that has the ability to have its back end swapped out. > > > > Who would I talk to about how kernel debugging works at the > > lowest layers right now? Which source files should I look at first. > > the gdb debugging piggybacks onto the ddb debugger > the file i386/i386/i386-gdbstub.c gives the basic > interface for the serial connection. > > the serial part is in /sys/dev/sio/sio.c > > I don't know what gdb does on the ethernet but my guess is that it's > already written there somewhere. > > I guess using udp packets with an address set by a sysctl > would be sufficient, > especially if we had our own udp handler (which I'm told can be done in a > very small amount of code it we know what packets we are getting). > > > > > Thanks, > > George > > > > -- > > George V. Neville-Neil gnn@neville-neil.com > > NIC:GN82 > > > > "Those who would trade liberty for temporary security deserve neither" > > - Benjamin Franklin > > > > > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 3:52:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by hub.freebsd.org (Postfix) with ESMTP id 861F837B400 for ; Wed, 20 Feb 2002 03:52:21 -0800 (PST) Received: from laptop.6bone.nl (penguin.ripe.net [193.0.1.232]) by birch.ripe.net (8.11.6/8.11.6) with SMTP id g1KBqFn06750; Wed, 20 Feb 2002 12:52:15 +0100 Received: (nullmailer pid 478 invoked by uid 1000); Wed, 20 Feb 2002 11:52:15 -0000 Date: Wed, 20 Feb 2002 12:52:14 +0100 From: Mark Santcroos To: Terry Lambert Cc: freebsd-current@FreeBSD.ORG, Alfred Perlstein Subject: Re: Ethernet tunnel device Message-ID: <20020220125214.A425@laptop.6bone.nl> References: <20020211032336.A2135@kashmir.etowns.net> <20020211170131.A79104@laptop.6bone.nl> <20020212074327.A3466@laptop.6bone.nl> <20020213111358.A3235@kashmir.etowns.net> <20020213111937.A10146@Odin.AC.HMC.Edu> <3C6B0BFD.F27F040F@mindspring.com> <20020216004146.A57907@laptop.6bone.nl> <3C6DD38B.BF38EC80@mindspring.com> <20020215214430.A7255@Odin.AC.HMC.Edu> <3C6E2011.65DDAD2A@mindspring.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C6E2011.65DDAD2A@mindspring.com>; from tlambert2@mindspring.com on Sat, Feb 16, 2002 at 01:02:09AM -0800 X-Handles: MS6-6BONE, MS18417-RIPE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Feb 16, 2002 at 01:02:09AM -0800, Terry Lambert wrote: > Pretty clearly, if it happens, and the process is truly > gone, then there is a resource track cleanup that's > missing (perhaps it's a reference that results from the > Linux mmap resource track cleanup not releasing it?). It was indeed a linux_compat specific resource cleanup issue. I managed to create a simple linux program that had the same problem. From there on it was easy... The problem was created by Alfred's locking commit of Jan 13. (No hard feelings, it helped me to understand the code alot better! ;) ) Can someone please commit the attached (trivial) patch? Mark ps. there might be more pieces of code like this maybe. -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="linux_ioctl.c.patch" --- linux_ioctl.c.orig Wed Feb 20 12:34:46 2002 +++ linux_ioctl.c Wed Feb 20 12:35:06 2002 @@ -2313,9 +2313,10 @@ TAILQ_FOREACH(he, &handlers, list) { if (cmd >= he->low && cmd <= he->high) { error = (*he->func)(td, args); - if (error != ENOIOCTL) + if (error != ENOIOCTL) { fdrop(fp, td); return (error); + } } } fdrop(fp, td); --pWyiEgJYm5f9v55/-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 4:12:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 28BBF37B402; Wed, 20 Feb 2002 04:12:08 -0800 (PST) Received: from 12-234-22-238.client.attbi.com ([12.234.22.238]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020220121207.FKQS1147.rwcrmhc52.attbi.com@12-234-22-238.client.attbi.com>; Wed, 20 Feb 2002 12:12:07 +0000 Received: from master.gorean.org (root@master.gorean.org [10.0.0.2]) by 12-234-22-238.client.attbi.com (8.11.6/8.11.6) with ESMTP id g1KCC6q24636; Wed, 20 Feb 2002 04:12:07 -0800 (PST) (envelope-from DougB@FreeBSD.org) Received: from localhost (doug@localhost) by master.gorean.org (8.11.6/8.11.6) with ESMTP id g1KCC5088625; Wed, 20 Feb 2002 04:12:05 -0800 (PST) (envelope-from DougB@FreeBSD.org) Date: Wed, 20 Feb 2002 04:12:05 -0800 (PST) From: Doug Barton X-X-Sender: doug@master.gorean.org To: John Baldwin Cc: mharnois@cpinternet.com, Subject: RE: mergemaster and /etc/pam.d In-Reply-To: Message-ID: <20020220041035.S87756-100000@master.gorean.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 4 Jan 2002, John Baldwin wrote: > > On 04-Jan-02 Michael D. Harnois wrote: > > mergemaster does not pick up changes to the /etc/pam.d directory. Is > > this a feature? > > I don't think pam.d is installed right now by default. Once it is turned on by > default I think mergemaster will DTRT. John's right. By design, mm only knows about things installed by /usr/src/etc/Makefile. That makes it flexible over time and much easier to keep up to date. Doug -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 4:26:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id E6A5137B404; Wed, 20 Feb 2002 04:26:31 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id F299F5341; Wed, 20 Feb 2002 13:26:26 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Doug Barton Cc: John Baldwin , mharnois@cpinternet.com, Subject: Re: mergemaster and /etc/pam.d References: <20020220041035.S87756-100000@master.gorean.org> From: Dag-Erling Smorgrav Date: 20 Feb 2002 13:26:25 +0100 In-Reply-To: <20020220041035.S87756-100000@master.gorean.org> Message-ID: Lines: 14 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Doug Barton writes: > On Fri, 4 Jan 2002, John Baldwin wrote: > > I don't think pam.d is installed right now by default. Once it is > > turned on by default I think mergemaster will DTRT. > John's right. By design, mm only knows about things installed by > /usr/src/etc/Makefile. That makes it flexible over time and much easier to > keep up to date. pam.d *is* listed in etc/Makefile, and mergemaster *does* pick up changes to it, as long as the RCS Id changed. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 5:54: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from encontacto.net (adsl-64-173-182-158.dsl.mtry01.pacbell.net [64.173.182.158]) by hub.freebsd.org (Postfix) with ESMTP id E9A1437B400 for ; Wed, 20 Feb 2002 05:53:59 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) (uid 0) by encontacto.net with local; Wed, 20 Feb 2002 05:53:59 -0800 Received: from 64.173.182.155 ( [64.173.182.155]) as user eculp@EnContacto.Net by Mail.MexComUSA.Net with HTTP; Wed, 20 Feb 2002 05:53:59 -0800 Message-ID: <1014213239.3c73aa7769178@Mail.MexComUSA.Net> Date: Wed, 20 Feb 2002 05:53:59 -0800 From: Edwin Culp To: current@FreeBSD.ORG Subject: Kernel compile error with today's cvsup. MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Originating-IP: 64.173.182.155 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On my daily build, my kernels are broken as per log: ===> wi cd /usr/obj/usr/src/sys/PIII850N; MAKESRCPATH=/usr/src/sys/dev/aic7xxx/aicasm make - f /usr/src/sys/dev/aic7xxx/aicasm/Makefile Warning: Object directory not changed from original /usr/obj/usr/src/sys/PIII850N cc -O -pipe -I/usr/include -I. -c aicasm_gram.c cc: installation problem, cannot exec `cpp0': No such file or directory cc: installation problem, cannot exec `cc1': No such file or directory *** Error code 1 Thanks, ed --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 7:49:26 2002 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 2926237B402 for ; Wed, 20 Feb 2002 07:49:20 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id g1KFnJe69025 for current@freebsd.org; Wed, 20 Feb 2002 07:49:19 -0800 (PST) (envelope-from david) Date: Wed, 20 Feb 2002 07:49:19 -0800 (PST) From: David Wolfskill Message-Id: <200202201549.g1KFnJe69025@bunrab.catwhisker.org> To: current@freebsd.org Subject: Panic with today's -CURRENT at runq_choose+0x83 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Just built & installed today's -CURRENT (CVSup around 0347 hrs. PST): Wed Feb 20 05:48:23 PST 2002 FreeBSD/i386 (freebeast.catwhisker.org) (cuaa0) login: Fboot() called on cpu#0 Waiting (max 60 seconds) for system process `vnlru' to stop...stopped lock order reversal 1st 0xc0337420 sched lock @ /usr/src/sys/kern/kern_idle.c:105 2nd 0xc0390840 sio @ /usr/src/sys/dev/sio/sio.c:3137 kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = 00000000 fault virtual address = 0xd6820001 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01a78cf stack pointer = 0x10:0xd683ccd0 frame pointer = 0x10:0xd683cce0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 11 (idle: cpu0) kernel: type 12 trap, code=0 timeout stopping cpus Stopped at runq_choose+0x83: movl 0(%edx),%eax db> trace runq_choose(c035a660,d683cd0c,c02b1b3e,c01a8d87,12e) at runq_choose+0x83 choosethread(c01a8d87,12e,c0196384,d682c500,1a09) at choosethread+0xd sw1(d682c600,d683cd34,c01961c4,0,d683cd48) at sw1+0x20 idle_proc(0,d683cd48,0,c0196384,0) at idle_proc+0x5c fork_exit(c0196384,0,d683cd48) at fork_exit+0x9c fork_trampoline() at fork_trampoline+0x8 db> show pcpu 0 cpuid = 0 curthread = 0xd682c600: pid 11 "idle: cpu0" curpcb = 0xd683cda0 fpcurthread = none idlethread = 0xd682c600: pid 11 "idle: cpu0" currentldt = 0x28 spin locks held: exclusive (spin mutex) sched lock (0xc0337420) locked @ /usr/src/sys/kern/kern_idle.c:105 db> show pcpu 1 cpuid = 1 curthread = 0xda408700: pid 90879 "reboot" curpcb = 0xda4b8da0 fpcurthread = none idlethread = 0xd682c900: pid 10 "idle: cpu1" currentldt = 0x28 spin locks held: exclusive (spin mutex) clk (0xc033ad00) locked @ /usr/src/sys/i386/isa/clock.c:415 db> show locks exclusive (spin mutex) sched lock (0xc0337420) locked @ /usr/src/sys/kern/kern_idle.c:105 db> I have some errands to run; should be back within about 1.5 hrs., but will be quite willing to poke & hack around to see what's up after that time. Cheers, david -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 9: 2:46 2002 Delivered-To: freebsd-current@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 75EAF37B402 for ; Wed, 20 Feb 2002 09:02:36 -0800 (PST) Received: from v-ger.we.lc.ehu.es (v-ger [158.227.6.51]) by polaris.we.lc.ehu.es (8.11.6/8.11.6) with ESMTP id g1KH2Vj23530 for ; Wed, 20 Feb 2002 18:02:32 +0100 (MET) Received: (from jose@localhost) by v-ger.we.lc.ehu.es (8.11.6/8.11.6) id g1KH2dU02753 for current@FreeBSD.org; Wed, 20 Feb 2002 18:02:39 +0100 (CET) (envelope-from jose) Date: Wed, 20 Feb 2002 18:02:38 +0100 From: "Jose M. Alcaide" To: current@FreeBSD.org Subject: cannot exec `cpp0': No such file or directory Message-ID: <20020220180238.J1170@v-ger.we.lc.ehu.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Operating-System: FreeBSD 4.5-RELEASE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, Just made world, and now cc(1) fails: $ cc p.c -o p cc: installation problem, cannot exec `cpp0': No such file or directory Using ktrace(1), I found that now cc searchs its subcomponents in /usr/libexec/elf. However, installworld puts them in /usr/libexec. Nothing is said about this problem in UPDATING. Could this problem be related to the recent changes to src/gnu/usr.bin/cc/cc_tools/freebsd-native.h (1.10, 1.11)? Cheers, JMA -- ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 9: 7: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 3437637B402 for ; Wed, 20 Feb 2002 09:07:00 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id CE5C6AE2C6; Wed, 20 Feb 2002 09:06:59 -0800 (PST) Date: Wed, 20 Feb 2002 09:06:59 -0800 From: Alfred Perlstein To: Mark Santcroos Cc: Terry Lambert , freebsd-current@FreeBSD.ORG Subject: Re: Ethernet tunnel device Message-ID: <20020220170659.GD12136@elvis.mu.org> References: <20020211170131.A79104@laptop.6bone.nl> <20020212074327.A3466@laptop.6bone.nl> <20020213111358.A3235@kashmir.etowns.net> <20020213111937.A10146@Odin.AC.HMC.Edu> <3C6B0BFD.F27F040F@mindspring.com> <20020216004146.A57907@laptop.6bone.nl> <3C6DD38B.BF38EC80@mindspring.com> <20020215214430.A7255@Odin.AC.HMC.Edu> <3C6E2011.65DDAD2A@mindspring.com> <20020220125214.A425@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020220125214.A425@laptop.6bone.nl> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Mark Santcroos [020220 03:52] wrote: > > It was indeed a linux_compat specific resource cleanup issue. > > I managed to create a simple linux program that had the same problem. From > there on it was easy... > > The problem was created by Alfred's locking commit of Jan 13. > (No hard feelings, it helped me to understand the code alot better! ;) ) > > Can someone please commit the attached (trivial) patch? Done. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 9:11:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 8E65037B400 for ; Wed, 20 Feb 2002 09:11:20 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.6/8.11.6) id g1KHAx405407; Wed, 20 Feb 2002 19:10:59 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200202201710.g1KHAx405407@zibbi.icomtek.csir.co.za> Subject: Re: Kernel compile error with today's cvsup. In-Reply-To: <1014213239.3c73aa7769178@Mail.MexComUSA.Net> from Edwin Culp at "Feb 20, 2002 05:53:59 am" To: eculp@encontacto.net (Edwin Culp) Date: Wed, 20 Feb 2002 19:10:59 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > On my daily build, my kernels are broken as per log: > > ===> wi > cd /usr/obj/usr/src/sys/PIII850N; MAKESRCPATH=/usr/src/sys/dev/aic7xxx/aicasm > make - > f /usr/src/sys/dev/aic7xxx/aicasm/Makefile > Warning: Object directory not changed from original /usr/obj/usr/src/sys/PIII850N > cc -O -pipe -I/usr/include -I. -c aicasm_gram.c > cc: installation problem, cannot exec `cpp0': No such file or directory > cc: installation problem, cannot exec `cc1': No such file or directory > *** Error code 1 > I don't think it is the kernel. My "make release" failed with the same type of error and that machine's kernel is from Jan 28. Maybe it is the search path that changed in gnu/usr.bin/cc/cc_tools/freebsd-native.h ... Just a guess. John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 9:21:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 4158937B405 for ; Wed, 20 Feb 2002 09:21:48 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g1KHLE006684; Wed, 20 Feb 2002 09:21:14 -0800 (PST) (envelope-from obrien) Date: Wed, 20 Feb 2002 09:21:14 -0800 From: "David O'Brien" To: "Jose M. Alcaide" Cc: current@FreeBSD.org Subject: Re: cannot exec `cpp0': No such file or directory Message-ID: <20020220092114.A4493@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <20020220180238.J1170@v-ger.we.lc.ehu.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020220180238.J1170@v-ger.we.lc.ehu.es>; from jose@we.lc.ehu.es on Wed, Feb 20, 2002 at 06:02:38PM +0100 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Feb 20, 2002 at 06:02:38PM +0100, Jose M. Alcaide wrote: > Using ktrace(1), I found that now cc searchs its subcomponents in > /usr/libexec/elf. However, installworld puts them in /usr/libexec. ... > Could this problem be related to the recent changes to > src/gnu/usr.bin/cc/cc_tools/freebsd-native.h (1.10, 1.11)? I need to see the output of ``/usr/bin/cc -print-search-dirs'' from the problematic compiler. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 9:22:44 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 4559437B405 for ; Wed, 20 Feb 2002 09:22:36 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g1KHMU506712; Wed, 20 Feb 2002 09:22:30 -0800 (PST) (envelope-from obrien) Date: Wed, 20 Feb 2002 09:22:30 -0800 From: "David O'Brien" To: Edwin Culp Cc: current@FreeBSD.ORG Subject: Re: Kernel compile error with today's cvsup. Message-ID: <20020220092230.B4493@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <1014213239.3c73aa7769178@Mail.MexComUSA.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1014213239.3c73aa7769178@Mail.MexComUSA.Net>; from eculp@encontacto.net on Wed, Feb 20, 2002 at 05:53:59AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Feb 20, 2002 at 05:53:59AM -0800, Edwin Culp wrote: > On my daily build, my kernels are broken as per log: > > ===> wi > cd /usr/obj/usr/src/sys/PIII850N; MAKESRCPATH=/usr/src/sys/dev/aic7xxx/aicasm > make - > f /usr/src/sys/dev/aic7xxx/aicasm/Makefile > Warning: Object directory not changed from original /usr/obj/usr/src/sys/PIII850N > cc -O -pipe -I/usr/include -I. -c aicasm_gram.c > cc: installation problem, cannot exec `cpp0': No such file or directory > cc: installation problem, cannot exec `cc1': No such file or directory > *** Error code 1 I need to see the output of ``/usr/bin/cc -print-search-dirs'' from the problematic compiler. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 9:32:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 5210437B416; Wed, 20 Feb 2002 09:32:44 -0800 (PST) Received: from v-ger.we.lc.ehu.es (v-ger [158.227.6.51]) by polaris.we.lc.ehu.es (8.11.6/8.11.6) with ESMTP id g1KHWfj23818; Wed, 20 Feb 2002 18:32:41 +0100 (MET) Received: (from jose@localhost) by v-ger.we.lc.ehu.es (8.11.6/8.11.6) id g1KHWjf02902; Wed, 20 Feb 2002 18:32:45 +0100 (CET) (envelope-from jose) Date: Wed, 20 Feb 2002 18:32:45 +0100 From: "Jose M. Alcaide" To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: cannot exec `cpp0': No such file or directory Message-ID: <20020220183245.K1170@v-ger.we.lc.ehu.es> References: <20020220180238.J1170@v-ger.we.lc.ehu.es> <20020220092114.A4493@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020220092114.A4493@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Wed, Feb 20, 2002 at 09:21:14AM -0800 X-Operating-System: FreeBSD 4.5-RELEASE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Feb 20, 2002 at 09:21:14AM -0800, David O'Brien wrote: > I need to see the output of ``/usr/bin/cc -print-search-dirs'' from the > problematic compiler. $ /usr/bin/cc -print-search-dirs install: /usr/libexec/(null) programs: /usr/libexec/elf/ libraries: /usr/lib/ -- ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 9:44:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id B270537B400 for ; Wed, 20 Feb 2002 09:44:19 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id g1KHiJ369377 for current@FreeBSD.ORG; Wed, 20 Feb 2002 09:44:19 -0800 (PST) (envelope-from david) Date: Wed, 20 Feb 2002 09:44:19 -0800 (PST) From: David Wolfskill Message-Id: <200202201744.g1KHiJ369377@bunrab.catwhisker.org> To: current@FreeBSD.ORG Subject: Sorry, false alarm (was: Panic with today's -CURRENT at runq_choose+0x83) In-Reply-To: <200202201549.g1KFnJe69025@bunrab.catwhisker.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Date: Wed, 20 Feb 2002 07:49:19 -0800 (PST) >From: David Wolfskill >Just built & installed today's -CURRENT (CVSup around 0347 hrs. PST): >... >Stopped at runq_choose+0x83: movl 0(%edx),%eax >db> trace >runq_choose(c035a660,d683cd0c,c02b1b3e,c01a8d87,12e) at runq_choose+0x83 >choosethread(c01a8d87,12e,c0196384,d682c500,1a09) at choosethread+0xd >sw1(d682c600,d683cd34,c01961c4,0,d683cd48) at sw1+0x20 >idle_proc(0,d683cd48,0,c0196384,0) at idle_proc+0x5c >fork_exit(c0196384,0,d683cd48) at fork_exit+0x9c >fork_trampoline() at fork_trampoline+0x8 Ahhh... that would seem to have been merely fallout from the upgrade process I used. A subsequent reboot worked fine: freebeast(5.0-C)[1] uname -a FreeBSD freebeast.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #84: Wed Feb 20 07:20:46 PST 2002 root@freebeast.catwhisker.org:/common/S4/obj/usr/src/sys/FREEBEAST i386 freebeast(5.0-C)[2] and I didn't even have the above-referenced panic at all on my laptop: g1-7(5.0-C)[1] uname -a FreeBSD g1-7.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #3: Wed Feb 20 09:13:13 PST 2002 root@g1-7.catwhisker.org:/common/S3/obj/usr/src/sys/LAPTOP_30W_NC i386 g1-7(5.0-C)[2] So... move along, folks; nothing to see here.... Sorry for the noise. Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 10:17:50 2002 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id 3E6B537B400; Wed, 20 Feb 2002 10:17:49 -0800 (PST) Date: Wed, 20 Feb 2002 10:17:49 -0800 From: David O'Brien To: "Jose M. Alcaide" Cc: current@FreeBSD.org Subject: Re: cannot exec `cpp0': No such file or directory Message-ID: <20020220101749.A52183@hub.freebsd.org> Reply-To: obrien@freebsd.org References: <20020220180238.J1170@v-ger.we.lc.ehu.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020220180238.J1170@v-ger.we.lc.ehu.es>; from jose@we.lc.ehu.es on Wed, Feb 20, 2002 at 06:02:38PM +0100 X-Operating-System: FreeBSD 4.4-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Feb 20, 2002 at 06:02:38PM +0100, Jose M. Alcaide wrote: > $ cc p.c -o p > cc: installation problem, cannot exec `cpp0': No such file or directory Fixed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 11:13:46 2002 Delivered-To: freebsd-current@freebsd.org Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id CFC7A37B417 for ; Wed, 20 Feb 2002 11:13:38 -0800 (PST) Received: from pool0120.cvx21-bradley.dialup.earthlink.net ([209.179.192.120] helo=mindspring.com) by hawk.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 16dcBN-00069N-00; Wed, 20 Feb 2002 11:13:37 -0800 Message-ID: <3C73F557.3646A148@mindspring.com> Date: Wed, 20 Feb 2002 11:13:27 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mark Santcroos Cc: freebsd-current@FreeBSD.ORG, Alfred Perlstein Subject: Re: Ethernet tunnel device References: <20020211032336.A2135@kashmir.etowns.net> <20020211170131.A79104@laptop.6bone.nl> <20020212074327.A3466@laptop.6bone.nl> <20020213111358.A3235@kashmir.etowns.net> <20020213111937.A10146@Odin.AC.HMC.Edu> <3C6B0BFD.F27F040F@mindspring.com> <20020216004146.A57907@laptop.6bone.nl> <3C6DD38B.BF38EC80@mindspring.com> <20020215214430.A7255@Odin.AC.HMC.Edu> <3C6E2011.65DDAD2A@mindspring.com> <20020220125214.A425@laptop.6bone.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mark Santcroos wrote: > On Sat, Feb 16, 2002 at 01:02:09AM -0800, Terry Lambert wrote: > > Pretty clearly, if it happens, and the process is truly > > gone, then there is a resource track cleanup that's > > missing (perhaps it's a reference that results from the > > Linux mmap resource track cleanup not releasing it?). > > It was indeed a linux_compat specific resource cleanup issue. Cool. No zebras. 8-). > I managed to create a simple linux program that had the same problem. From > there on it was easy... > > The problem was created by Alfred's locking commit of Jan 13. > (No hard feelings, it helped me to understand the code alot better! ;) ) > > Can someone please commit the attached (trivial) patch? Alfred... that would be for you? 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 11:20:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 5835E37B404 for ; Wed, 20 Feb 2002 11:19:57 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 135A9AE25C; Wed, 20 Feb 2002 11:19:57 -0800 (PST) Date: Wed, 20 Feb 2002 11:19:57 -0800 From: Alfred Perlstein To: Terry Lambert Cc: Mark Santcroos , freebsd-current@FreeBSD.ORG Subject: Re: Ethernet tunnel device Message-ID: <20020220191957.GG12136@elvis.mu.org> References: <20020212074327.A3466@laptop.6bone.nl> <20020213111358.A3235@kashmir.etowns.net> <20020213111937.A10146@Odin.AC.HMC.Edu> <3C6B0BFD.F27F040F@mindspring.com> <20020216004146.A57907@laptop.6bone.nl> <3C6DD38B.BF38EC80@mindspring.com> <20020215214430.A7255@Odin.AC.HMC.Edu> <3C6E2011.65DDAD2A@mindspring.com> <20020220125214.A425@laptop.6bone.nl> <3C73F557.3646A148@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C73F557.3646A148@mindspring.com> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Terry Lambert [020220 11:13] wrote: > Mark Santcroos wrote: > > > I managed to create a simple linux program that had the same problem. From > > there on it was easy... > > > > The problem was created by Alfred's locking commit of Jan 13. > > (No hard feelings, it helped me to understand the code alot better! ;) ) > > > > Can someone please commit the attached (trivial) patch? > > Alfred... that would be for you? 8-). All patches are trivial, it's the bugs that are a b*tch. Yes, the patch has been committed. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 11:52:17 2002 Delivered-To: freebsd-current@freebsd.org Received: from encontacto.net (adsl-64-173-182-158.dsl.mtry01.pacbell.net [64.173.182.158]) by hub.freebsd.org (Postfix) with ESMTP id DF24237B41A; Wed, 20 Feb 2002 11:52:11 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) (uid 0) by encontacto.net with local; Wed, 20 Feb 2002 11:52:10 -0800 Received: from 64.173.182.155 ( [64.173.182.155]) as user eculp@EnContacto.Net by Mail.MexComUSA.Net with HTTP; Wed, 20 Feb 2002 11:52:10 -0800 Message-ID: <1014234730.3c73fe6a5d619@Mail.MexComUSA.Net> Date: Wed, 20 Feb 2002 11:52:10 -0800 From: Edwin Culp To: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: Kernel compile error with today's cvsup. References: <1014213239.3c73aa7769178@Mail.MexComUSA.Net> <20020220092230.B4493@dragon.nuxi.com> In-Reply-To: <20020220092230.B4493@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Originating-IP: 64.173.182.155 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David, I see it's already fixed so I'll assume that you no longer need the compiler output. I'm sorry that I didn't answer before but I just checked my email and went to some meetings and am just getting back. Thanks for your help, ed Quoting David O'Brien : > On Wed, Feb 20, 2002 at 05:53:59AM -0800, Edwin Culp wrote: > > On my daily build, my kernels are broken as per log: > > > > ===> wi > > cd /usr/obj/usr/src/sys/PIII850N; > MAKESRCPATH=/usr/src/sys/dev/aic7xxx/aicasm > > make - > > f /usr/src/sys/dev/aic7xxx/aicasm/Makefile > > Warning: Object directory not changed from original > /usr/obj/usr/src/sys/PIII850N > > cc -O -pipe -I/usr/include -I. -c aicasm_gram.c > > cc: installation problem, cannot exec `cpp0': No such file or directory > > cc: installation problem, cannot exec `cc1': No such file or directory > > *** Error code 1 > > > I need to see the output of ``/usr/bin/cc -print-search-dirs'' from the > problematic compiler. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 14:28: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 46D6E37B42A for ; Wed, 20 Feb 2002 14:27:32 -0800 (PST) Received: (qmail 3773 invoked from network); 20 Feb 2002 22:27:30 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.90.117.57]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 20 Feb 2002 22:27:30 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200202190945.g1J9j9kg076110@rina.r.dl.itc.u-tokyo.ac.jp> Date: Wed, 20 Feb 2002 17:27:33 -0500 (EST) From: John Baldwin To: Seigo Tanimura Subject: RE: pgrp/session patch Cc: Alfred Perlstein , current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 19-Feb-02 Seigo Tanimura wrote: > Here is the most up-to-date version of pgrp/session lock (at Change 6700): > > http://people.FreeBSD.org/~tanimura/patches/pgrp10.diff.gz > > I would like to commit this on the next Sunday. Otherwise, my patch > would conflict with other patches, especially tty. I've looked over other versions of this patch and am happy with them, so I have no objections. :) -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 14:29:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail12.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with ESMTP id A9DC237B431 for ; Wed, 20 Feb 2002 14:27:43 -0800 (PST) Received: (qmail 11615 invoked from network); 20 Feb 2002 22:27:42 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.90.117.57]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 20 Feb 2002 22:27:42 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200202181912.g1IJCGK32122@apollo.backplane.com> Date: Wed, 20 Feb 2002 17:27:45 -0500 (EST) From: John Baldwin To: Matthew Dillon Subject: RE: Patch to improve mutex collision performance Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-Feb-02 Matthew Dillon wrote: > While testing some Giant removal stuff I noticed that my current > system sometimes got into an extremely non-optimal flip-flop situation > between two processes contesting Giant on an SMP system which halved the > syscall performance in the test. > > In my getuid test, for example, with Giant in place I was getting > 683Kcalls/sec with one process and 427Kcalls/sec with two. Giant > was being obtained in two places: in userret and in getuid(). > > When I turned off Giant in getuid() the syscall performance actually > went DOWN, to 250Kcalls/sec with two processes. This was a totally > unexpected result. > > It turns out that the two processes got into an extremely non-optimal > contested/sleep/wakeup situation, even though they do not actually have > to sleep on Giant in this situation. > > The solution is to allow _mtx_lock_sleep() to spin instead of sleep in > the situation where: (1) there are no runnable processes other then > the ones already running on a cpu, (2) interrupts are enabled, and > (3) the mutex in question is not contested (to avoid starving the thread > contesting the mutex). In this case we can spin. > > This will go in tonight if no problems arise. I would rather make the locks adaptive like so: (untested) --- //depot/projects/smpng/sys/conf/options 2002/02/08 13:19:07 +++ //depot/user/jhb/lock/conf/options 2002/02/08 13:50:54 @@ -56,6 +56,7 @@ # mapped I/O # Miscellaneous options. +ADAPTIVE_MUTEXES BLEED COMPAT_43 opt_compat.h COMPAT_SUNOS opt_compat.h --- //depot/projects/smpng/sys/i386/include/cpufunc.h 2001/12/18 13:07:32 +++ //depot/user/jhb/lock/i386/include/cpufunc.h 2001/12/20 15:54:32 @@ -550,6 +550,12 @@ __asm __volatile("movl %0,%%dr7" : : "r" (sel)); } +static __inline void +cpu_pause(void) +{ + __asm __volatile("pause"); +} + static __inline critical_t cpu_critical_enter(void) { --- //depot/projects/smpng/sys/kern/kern_mutex.c 2002/02/08 14:19:21 +++ //depot/user/jhb/lock/kern/kern_mutex.c 2002/02/08 13:50:54 @@ -34,6 +34,7 @@ * Machine independent bits of mutex implementation. */ +#include "opt_adaptive_mutexes.h" #include "opt_ddb.h" #include @@ -345,7 +354,22 @@ continue; } +#if defined(SMP) && defined(ADAPTIVE_MUTEXES) /* + * If the current owner of the lock is executing on another + * CPU, spin instead of blocking. + */ + if (((struct thread *)(v & MTX_FLAGMASK)->td_kse->kse_oncpu != + NOCPU) { + mtx_unlock_spin(&sched_lock); +#ifdef __i386__ + cpu_pause(); +#endif + continue; + } +#endif /* SMP && ADAPTIVE_MUTEXES */ + + /* * We deffinately must sleep for this lock. */ mtx_assert(m, MA_NOTOWNED); @@ -433,6 +457,9 @@ /* Give interrupts a chance while we spin. */ critical_exit(); while (m->mtx_lock != MTX_UNOWNED) { +#ifdef __i386__ + cpu_pause(); +#endif if (i++ < 10000000) continue; if (i++ < 60000000) This is more a specific problem with Giant and I don't think it will be a problem with other mutexes, so I'd prefer a solution not quite so tailored to this particular behavior of Giant. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 14:30:52 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id 9844F37B449 for ; Wed, 20 Feb 2002 14:27:47 -0800 (PST) Received: (qmail 5106 invoked from network); 20 Feb 2002 22:27:46 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.90.117.57]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 20 Feb 2002 22:27:46 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3C720859.C77590F0@mindspring.com> Date: Wed, 20 Feb 2002 17:27:48 -0500 (EST) From: John Baldwin To: Terry Lambert Subject: Re: Patch sets to date and timing tests with Giant out of userre Cc: current@FreeBSD.ORG, Peter Wemm , Matthew Dillon , Julian Elischer Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 19-Feb-02 Terry Lambert wrote: > Julian Elischer wrote: >> The fully safe version of this code is: >> td->td_retval[0] = td->td_ucred->cr_ruid; >> td->td_retval[1] = td->td_ucred->cr_uid; >> return (0); >> >> because td->td_ucred is read-only for it's whole existance. > > ??? > > Are you sure that td->td_ucred can't change in the middle, > to point to a different ucred, as a result of kernel > preemption? Yes. A thread's ucred pointer is constant teh entire time that it is in the kernel. If we get preempted who cares. We will still be teh same thread when we continue executing. :) -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 15: 5:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by hub.freebsd.org (Postfix) with ESMTP id 53BA037B402; Wed, 20 Feb 2002 15:05:42 -0800 (PST) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.11.6/8.11.4) id g1KN5VB57770; Thu, 21 Feb 2002 00:05:31 +0100 (CET) (envelope-from stijn) Date: Thu, 21 Feb 2002 00:05:31 +0100 From: Stijn Hoop To: "Alexander N. Kabaev" Cc: Bjoern Fischer , current@freebsd.org, freebsd-gnats-submit@freebsd.org, vova@sw.ru, "David O'Brien" Subject: Re: ports/34908: libpng port makes bad dynamic library on -CURRENT Message-ID: <20020221000531.A57633@pcwin002.win.tue.nl> References: <3C6D49E0.3000506@gte.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3C6D49E0.3000506@gte.com>; from ak03@gte.com on Fri, Feb 15, 2002 at 12:48:16PM -0500 X-Bright-Idea: Let's abolish HTML mail! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi -current, I ventured into this brave new world a few days ago and ran into this very problem. Alexander's patch (along with a make install in /usr/src/gnu/usr.bin/binutils) fixed it, as advertised. Maybe this can now be committed? --Stijn --=20 Help Wanted: Telepath. You know where to apply. --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8dCu7Y3r/tLQmfWcRAtx4AJ0QhKrMNLCREGXngXZTFP6BX+/71gCeJDjy X+dkuUlpBeY1mLpn13r+ug8= =yAOh -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 16:49:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 2365737B417; Wed, 20 Feb 2002 16:49:18 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 1A9B17830E; Thu, 21 Feb 2002 11:19:15 +1030 (CST) Date: Thu, 21 Feb 2002 11:19:15 +1030 From: Greg Lehey To: Jake Burkholder Cc: Matthew Dillon , David O'Brien , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance Message-ID: <20020221111915.N65817@wantadilla.lemis.com> References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020218153807.E96115@locore.ca> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday, 18 February 2002 at 15:38:07 -0500, Jake Burkholder wrote: > Apparently, On Mon, Feb 18, 2002 at 11:51:44AM -0800, > Matthew Dillon said words to the effect of; >> I'm fairly sure JHB does not have a patch to address this but, please, >> be my guest and check P4. > > Actually he does. Maybe you should have checked p4 first yourself. Well, maybe, like me, he doesn't know how. I only recently learnt of the existence of this repo, and I still don't know where it is. It certainly wasn't announced on the SMP mailing list. I've seen a few references to p4 there, but no indication of how to access the repo. > What John's patch does is spin while the lock owner is running on > another cpu. Spinning while there are no other processes on the run > queues as well makes sense but you'll also be doing a lot of > acquires and releases of sched_lock. I must be misinterpreting this statement. Under what circumstances do you spin? Yes, I read the "while the owner is running in another CPU", but the way I read that, it turns the blocking lock into a spin lock. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 17: 2:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id AC94337B405; Wed, 20 Feb 2002 17:02:22 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1L12MR91194; Wed, 20 Feb 2002 17:02:22 -0800 (PST) (envelope-from dillon) Date: Wed, 20 Feb 2002 17:02:22 -0800 (PST) From: Matthew Dillon Message-Id: <200202210102.g1L12MR91194@apollo.backplane.com> To: John Baldwin Cc: current@FreeBSD.org Subject: Re: RE: Patch to improve mutex collision performance References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This sounds better but why do we need a 'pause' at all? I don't think spinning in this case will have any effect on power consumption. -Matt Matthew Dillon :I would rather make the locks adaptive like so: (untested) : :--- //depot/projects/smpng/sys/conf/options 2002/02/08 13:19:07 :+++ //depot/user/jhb/lock/conf/options 2002/02/08 13:50:54 :@@ -56,6 +56,7 @@ : # mapped I/O : : # Miscellaneous options. :+ADAPTIVE_MUTEXES : BLEED : COMPAT_43 opt_compat.h : COMPAT_SUNOS opt_compat.h :--- //depot/projects/smpng/sys/i386/include/cpufunc.h 2001/12/18 13:07:32 :+++ //depot/user/jhb/lock/i386/include/cpufunc.h 2001/12/20 15:54:32 :@@ -550,6 +550,12 @@ : __asm __volatile("movl %0,%%dr7" : : "r" (sel)); : } : :+static __inline void :+cpu_pause(void) :+{ :+ __asm __volatile("pause"); :+} :+ : static __inline critical_t : cpu_critical_enter(void) : { :--- //depot/projects/smpng/sys/kern/kern_mutex.c 2002/02/08 14:19:21 :+++ //depot/user/jhb/lock/kern/kern_mutex.c 2002/02/08 13:50:54 :@@ -34,6 +34,7 @@ : * Machine independent bits of mutex implementation. : */ : :+#include "opt_adaptive_mutexes.h" : #include "opt_ddb.h" : : #include :@@ -345,7 +354,22 @@ : continue; : } : :+#if defined(SMP) && defined(ADAPTIVE_MUTEXES) : /* :+ * If the current owner of the lock is executing on another :+ * CPU, spin instead of blocking. :+ */ :+ if (((struct thread *)(v & MTX_FLAGMASK)->td_kse->kse_oncpu != :+ NOCPU) { :+ mtx_unlock_spin(&sched_lock); :+#ifdef __i386__ :+ cpu_pause(); :+#endif :+ continue; :+ } :+#endif /* SMP && ADAPTIVE_MUTEXES */ :+ :+ /* : * We deffinately must sleep for this lock. : */ : mtx_assert(m, MA_NOTOWNED); :@@ -433,6 +457,9 @@ : /* Give interrupts a chance while we spin. */ : critical_exit(); : while (m->mtx_lock != MTX_UNOWNED) { :+#ifdef __i386__ :+ cpu_pause(); :+#endif : if (i++ < 10000000) : continue; : if (i++ < 60000000) : :This is more a specific problem with Giant and I don't think it will be a :problem with other mutexes, so I'd prefer a solution not quite so tailored to :this particular behavior of Giant. : :-- : :John Baldwin <>< http://www.FreeBSD.org/~jhb/ :"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 17:46:56 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B3E4E37B400; Wed, 20 Feb 2002 17:46:52 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1L1kqg91511; Wed, 20 Feb 2002 17:46:52 -0800 (PST) (envelope-from dillon) Date: Wed, 20 Feb 2002 17:46:52 -0800 (PST) From: Matthew Dillon Message-Id: <200202210146.g1L1kqg91511@apollo.backplane.com> To: Greg Lehey Cc: Jake Burkholder , "David O'Brien" , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> <20020221111915.N65817@wantadilla.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :On Monday, 18 February 2002 at 15:38:07 -0500, Jake Burkholder wrote: :> Apparently, On Mon, Feb 18, 2002 at 11:51:44AM -0800, :> Matthew Dillon said words to the effect of; :>> I'm fairly sure JHB does not have a patch to address this but, please, :>> be my guest and check P4. :> :> Actually he does. Maybe you should have checked p4 first yourself. : :Well, maybe, like me, he doesn't know how. I only recently learnt of :the existence of this repo, and I still don't know where it is. It :certainly wasn't announced on the SMP mailing list. I've seen a few :references to p4 there, but no indication of how to access the repo. : :> What John's patch does is spin while the lock owner is running on :> another cpu. Spinning while there are no other processes on the run :> queues as well makes sense but you'll also be doing a lot of :> acquires and releases of sched_lock. : :I must be misinterpreting this statement. Under what circumstances do :you spin? Yes, I read the "while the owner is running in another :CPU", but the way I read that, it turns the blocking lock into a spin :lock. : :Greg I'm not interested in using P4. I think it's a mistake. That is, I think it is being severely overused. At the very least it is preventing me from comitting simple things to -current because as far as I can tell when you add up the junk sitting in P4 it touches almost every file in the kernel tree. Everything I've tried to work on has some hack sitting in P4 somewhere that somebody hasn't committed. Well, that sucks folks. I want to be able to work on -current. There are literally 20 or 30 procedures that I can document and/or instrument Giant in and commit to the main tree trivially, with almost no chance of breaking someone and I want to do that to get those routines out of the way. I have no interest in taking what should be a day's worth of work and stretching out into one or two weeks due to having to check P4 to see what hacks other people might have left sitting there for weeks or months (half of it stale now). It is a supreme waste of time. I would like to see John commit his ucred stuff with Giant instrumentation. If he doesn't want to do it then I would like him to give me permission to do it from my tree now. I see no reason why we should have to wait another X days or weeks to see this stuff in the main tree. It just makes no sense to me. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 18:13:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 1B02F37B416; Wed, 20 Feb 2002 18:13:28 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id BE6E97830E; Thu, 21 Feb 2002 12:43:25 +1030 (CST) Date: Thu, 21 Feb 2002 12:43:25 +1030 From: Greg Lehey To: David O'Brien Cc: "M. Warner Losh" , current@FreeBSD.ORG Subject: Version control software (was: Patch sets to date and timing tests with Giant out of userret.) Message-ID: <20020221124325.Y65817@wantadilla.lemis.com> References: <20020219080019.8F1673A9A@overcee.wemm.org> <00cd01c1b926$82d35bb0$ef01a8c0@davidwnt> <20020219.135131.83283562.imp@village.org> <20020219164406.B29698@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020219164406.B29698@dragon.nuxi.com> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday, 19 February 2002 at 16:44:06 -0800, David O'Brien wrote: > On Tue, Feb 19, 2002 at 01:51:31PM -0700, M. Warner Losh wrote: >> Bitkeeper enforces the linux devleopment model >> to a large extent, > > In what way(s)? I'd be interested in this too. I've been using Bitkeeper for, well, Linux development, but I don't see anything which locks it in to that direction. Of course, Bitkeeper isn't free either, so there's no particular reason to prefer it to p4. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 18:17:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 04A6137B404 for ; Wed, 20 Feb 2002 18:17:34 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id F321578306; Thu, 21 Feb 2002 12:47:31 +1030 (CST) Date: Thu, 21 Feb 2002 12:47:31 +1030 From: Greg Lehey To: Peter Wemm Cc: Julian Elischer , current@FreeBSD.ORG Subject: Perforce repo (was: Patch sets to date and timing tests with Giant out of userret.) Message-ID: <20020221124731.Z65817@wantadilla.lemis.com> References: <20020219080019.8F1673A9A@overcee.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020219080019.8F1673A9A@overcee.wemm.org> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday, 19 February 2002 at 0:00:19 -0800, Peter Wemm wrote: > Julian Elischer wrote: >> I'd prefer to be working on a branch of CVS if it weren't for the people >> that would scream whenever I moved my merged tag up. >> (eek eek cvsup bloat). >> That way i would have a dozen people helping me but with my code in P4 I >> have me and occasionally Peter. > > Everybody who can commit to cvs on freefall also has p4 access. Well, I certainly missed this. > The set of people who can help is exactly the same. In fact, we > even have a couple of non-comitters with access. As I posted > before, When? > the instructions are in > http://people.freebsd.org/~peter/p4cookbook.txt, and the 'p4newuser' > command on freefall is what is run to activate it. If we want a > majordomo p4-all@freebsd.org mailing list (or something like that, > as an analog to cvs-all@freebsd.org), I can have that set up as > well. Am I the only person who, despite careful scrutiny, missed this announcement? I would have thought that this would at least have been worth a HEADS UP and prior discussion in -core. I've just checked my -core archive, and though we discuss this repo from time to time, there was nothing there to suggest that it was publicly available. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 18:26:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 7955B37B400 for ; Wed, 20 Feb 2002 18:26:23 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 954D378306; Thu, 21 Feb 2002 12:56:18 +1030 (CST) Date: Thu, 21 Feb 2002 12:56:18 +1030 From: Greg Lehey To: Peter Wemm , Matthew Dillon Cc: current@FreeBSD.ORG Subject: FreeBSD Project management (was: Patch sets to date and timing tests with Giant out of userret.) Message-ID: <20020221125618.A65817@wantadilla.lemis.com> References: <200202190715.g1J7F0158985@apollo.backplane.com> <20020219072228.C27743A9A@overcee.wemm.org> <20020219070403.B151F3A9A@overcee.wemm.org> <200202190715.g1J7F0158985@apollo.backplane.com> <200202190646.g1J6kgE58769@apollo.backplane.com> <20020219070403.B151F3A9A@overcee.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020219072228.C27743A9A@overcee.wemm.org> <200202190715.g1J7F0158985@apollo.backplane.com> <20020219070403.B151F3A9A@overcee.wemm.org> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday, 18 February 2002 at 23:04:03 -0800, Peter Wemm wrote: > Matthew Dillon wrote: >>> What a waste.. John has already done all this stuff already (using >>> td_ucred instead of p_ucred) over the entire tree. >>> >>> Cheers, >>> -Peter >> >> He didn't instrument Giant, and if you actually believe that one >> massive commit is going to be more stable then the piecemeal safe-mode >> commits I am making then you are smoking something. Or are you >> expecting John to commit his patchset piecemeal as well and test >> inbetween? If that is so, then he just wasted a whole lot time >> managing all this junk in P4 because, frankly, it only took me a few >> minutes to instrument the easier system calls. I spend far more >> time testing. > > So, John's last few months of work is junk then, is it? On Monday, 18 February 2002 at 23:22:28 -0800, Peter Wemm wrote: > Matthew Dillon wrote: >>> >>> So, John's last few months of work is junk then, is it? >>> >>> Cheers, >>> -Peter >>> -- >>> Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au >> >> I'll tell you what is junk... patches for things like getuid() sitting >> in P4 (whether instrumented or not). That's junk. >> >> I'll tell what is NOT junk. What isn't junk are things like John's more >> complex patch to kern_descrip.c. There's real work involved there >> that can be salvaged, and which can be committed to the -current >> piecemeal if Giant is properly instrumented. >> >> The biggest problem is that all of this stuff is sitting in P4 and none >> of it belongs there. > > With all due respect, bullshit! The p4 tree exists only as an > alternative to people having large uncommitted diffs sitting in > checked out cvs trees. > > Mailing patches between people trying to work in parallel is a > bigger waste of time. That is inherently single threaded. While I don't agree with dillon's tone, I can understand his frustration. There is a lack of communication in the SMP project. I might have done more myself if I had been able to follow it without being on IRC 24 hours a day. I suspect that this applies to other people as well. Note that dillon has suffered because of this. He has gone and done what looks like being unnecessary work. When he tries to commit it, he finds that somebody else has been working on it, and despite a kernel summit only a couple of days ago, he didn't know about it. I'm not picking on jhb here. This is the project's fault, not any individual's. We need some kind of project management to coordinate this effort, or the results will be seriously suboptimal. I would certainly not like to see dillon go away because it's too difficult to work with the project. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 18:35:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id A4E5837B400; Wed, 20 Feb 2002 18:35:37 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 698D3AE2AB; Wed, 20 Feb 2002 18:35:37 -0800 (PST) Date: Wed, 20 Feb 2002 18:35:37 -0800 From: Alfred Perlstein To: Greg Lehey Cc: Peter Wemm , Matthew Dillon , current@FreeBSD.ORG Subject: Re: FreeBSD Project management (was: Patch sets to date and timing tests with Giant out of userret.) Message-ID: <20020221023537.GU12136@elvis.mu.org> References: <200202190715.g1J7F0158985@apollo.backplane.com> <20020219072228.C27743A9A@overcee.wemm.org> <20020219070403.B151F3A9A@overcee.wemm.org> <200202190715.g1J7F0158985@apollo.backplane.com> <200202190646.g1J6kgE58769@apollo.backplane.com> <20020219070403.B151F3A9A@overcee.wemm.org> <20020221125618.A65817@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020221125618.A65817@wantadilla.lemis.com> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Greg Lehey [020220 18:26] wrote: > > I'm not picking on jhb here. This is the project's fault, not any > individual's. We need some kind of project management to coordinate > this effort, or the results will be seriously suboptimal. I would > certainly not like to see dillon go away because it's too difficult to > work with the project. First with the code complete has it go in. Seems pretty simple enough doesn't it? I've had quite enough of people telling others to hold off because "i'll have the feature any day now", or "that fix is in my local tree". Like I care about your local tree, it's useless from my point of view when it's not working and in the repo. And what the hell has happened to the usb stack? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 18:36: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from outboundx.mv.meer.net (outboundx.mv.meer.net [209.157.152.12]) by hub.freebsd.org (Postfix) with ESMTP id 5696D37B400; Wed, 20 Feb 2002 18:36:05 -0800 (PST) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by outboundx.mv.meer.net (8.11.6/8.11.6) with ESMTP id g1L2a1s62106; Wed, 20 Feb 2002 18:36:01 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from neville-neil.com ([209.157.133.226]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id SAA415110; Wed, 20 Feb 2002 18:35:48 -0800 (PST) Message-Id: <200202210235.SAA415110@meer.meer.net> To: Greg Lehey Cc: Peter Wemm , Matthew Dillon , current@FreeBSD.ORG Subject: Re: FreeBSD Project management (was: Patch sets to date and timing tests with Giant out of userret.) In-Reply-To: Message from Greg Lehey of "Thu, 21 Feb 2002 12:56:18 +1030." <20020221125618.A65817@wantadilla.lemis.com> Date: Wed, 20 Feb 2002 18:35:47 -0800 From: "George V. Neville-Neil" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm not in the core of the SMP stuff (the closest I'll get is the networking stuff) but I wonder if there is: 1) A work list of things that need to be done. 2) If that list is easy to read/update. Has anyone considered a Wiki to do this kind of coordination? We used TWiki at my last employer to decent effect. Check out www.twiki.org. Later, George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 18:40:14 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id 657CC37B400; Wed, 20 Feb 2002 18:40:12 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020221024011.XDIQ2626.rwcrmhc51.attbi.com@InterJet.elischer.org>; Thu, 21 Feb 2002 02:40:11 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id SAA65536; Wed, 20 Feb 2002 18:31:14 -0800 (PST) Date: Wed, 20 Feb 2002 18:31:14 -0800 (PST) From: Julian Elischer To: Greg Lehey Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: Perforce repo (was: Patch sets to date and timing tests with Giant out of userret.) In-Reply-To: <20020221124731.Z65817@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 21 Feb 2002, Greg Lehey wrote: > On Tuesday, 19 February 2002 at 0:00:19 -0800, Peter Wemm wrote: > Am I the only person who, despite careful scrutiny, missed this > announcement? I would have thought that this would at least have been > worth a HEADS UP and prior discussion in -core. I've just checked my > -core archive, and though we discuss this repo from time to time, > there was nothing there to suggest that it was publicly available. Even better is that the stuff is exported to a CVS tree and CVSupped out so you can actually work on it. (of course the version numbers are wierd but that doesn't matter) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 18:43:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 4E6ED37B400; Wed, 20 Feb 2002 18:43:05 -0800 (PST) Received: from localhost (arr@localhost) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g1L2grD33635; Wed, 20 Feb 2002 21:42:53 -0500 (EST) (envelope-from arr@FreeBSD.org) X-Authentication-Warning: fledge.watson.org: arr owned process doing -bs Date: Wed, 20 Feb 2002 21:42:48 -0500 (EST) From: "Andrew R. Reiter" X-Sender: arr@fledge.watson.org To: "George V. Neville-Neil" Cc: Greg Lehey , Peter Wemm , Matthew Dillon , current@FreeBSD.org Subject: Re: FreeBSD Project management (was: Patch sets to date and timing tests with Giant out of userret.) In-Reply-To: <200202210235.SAA415110@meer.meer.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 20 Feb 2002, George V. Neville-Neil wrote: :I'm not in the core of the SMP stuff (the closest I'll get is the :networking stuff) but I wonder if there is: Doesn't this belong on smp@freebsd.org so that SMP people could answer? : :1) A work list of things that need to be done. : :2) If that list is easy to read/update. : :Has anyone considered a Wiki to do this kind of coordination? We used :TWiki at my last employer to decent effect. Check out www.twiki.org. : :Later, :George : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : -- Andrew R. Reiter arr@watson.org arr@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 18:46:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 7158537B400 for ; Wed, 20 Feb 2002 18:46:40 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 558AB78307; Thu, 21 Feb 2002 13:16:38 +1030 (CST) Date: Thu, 21 Feb 2002 13:16:38 +1030 From: Greg Lehey To: Alfred Perlstein Cc: Peter Wemm , Matthew Dillon , current@FreeBSD.ORG Subject: Re: FreeBSD Project management (was: Patch sets to date and timing tests with Giant out of userret.) Message-ID: <20020221131638.B65817@wantadilla.lemis.com> References: <200202190715.g1J7F0158985@apollo.backplane.com> <20020219072228.C27743A9A@overcee.wemm.org> <20020219070403.B151F3A9A@overcee.wemm.org> <200202190715.g1J7F0158985@apollo.backplane.com> <200202190646.g1J6kgE58769@apollo.backplane.com> <20020219070403.B151F3A9A@overcee.wemm.org> <20020221125618.A65817@wantadilla.lemis.com> <20020221023537.GU12136@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020221023537.GU12136@elvis.mu.org> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday, 20 February 2002 at 18:35:37 -0800, Alfred Perlstein wrote: > * Greg Lehey [020220 18:26] wrote: >> >> I'm not picking on jhb here. This is the project's fault, not any >> individual's. We need some kind of project management to coordinate >> this effort, or the results will be seriously suboptimal. I would >> certainly not like to see dillon go away because it's too difficult to >> work with the project. > > First with the code complete has it go in. Seems pretty simple > enough doesn't it? Too simple. It's not the "code complete", it's the correct code to implement a part of the overall goal. And we should be working together, not duplicating each other's efforts. > I've had quite enough of people telling others to hold off because > "i'll have the feature any day now", or "that fix is in my local > tree". That's a detail, though admittedly one that needs to be addressed. We have more serious issues. Last Friday I asked for an overall project plan, and I still haven't seen one. Yes, we had some useful discussions, but it's still not enough. If it took Sun 8 years of (relatively) careful project planning to get their SMP up to a reasonable standard, how can we hope to succeed if we don't even decide what we're trying to do? Two years ago I spoke with you on the phone about SMP, and said that I didn't think that the project could cope with such a pervasive change. That's why I was happy when BSD[Ii] dropped both the design and the code into our lap, and we had an SMP project manager (for all of 6 months). Looking back now, we're making the same old mistakes. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 18:49:57 2002 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 1F61637B416; Wed, 20 Feb 2002 18:49:45 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 2A14378307; Thu, 21 Feb 2002 13:19:43 +1030 (CST) Date: Thu, 21 Feb 2002 13:19:43 +1030 From: Greg Lehey To: "Andrew R. Reiter" Cc: "George V. Neville-Neil" , Peter Wemm , Matthew Dillon , current@FreeBSD.org, developers@FreeBSD.org Subject: Re: FreeBSD Project management (was: Patch sets to date and timing tests with Giant out of userret.) Message-ID: <20020221131943.C65817@wantadilla.lemis.com> References: <200202210235.SAA415110@meer.meer.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday, 20 February 2002 at 21:42:48 -0500, Andrew R. Reiter wrote: > On Wed, 20 Feb 2002, George V. Neville-Neil wrote: > >> I'm not in the core of the SMP stuff (the closest I'll get is the >> networking stuff) but I wonder if there is: > > Doesn't this belong on smp@freebsd.org so that SMP people could > answer? Only up to a point. My issues (and George's, for that matter) are the project management side of things. I'm copying -developers, but maybe we need a different list: I'm open to suggestions. Maybe it's a symptom of the problem that there's no project management list. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 19:50:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id AB9A437B402; Wed, 20 Feb 2002 19:50:18 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.6/8.11.6) with UUCP id g1L3oDk53477; Thu, 21 Feb 2002 04:50:13 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g1L3XoYd051254; Thu, 21 Feb 2002 04:33:50 +0100 (CET)?g (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.6/8.11.6) id g1L3XoG55176; Thu, 21 Feb 2002 04:33:50 +0100 (CET) (envelope-from ticso) Date: Thu, 21 Feb 2002 04:33:49 +0100 From: Bernd Walter To: Julian Elischer Cc: Greg Lehey , Peter Wemm , current@FreeBSD.ORG Subject: Re: Perforce repo (was: Patch sets to date and timing tests with Giant out of userret.) Message-ID: <20020221033349.GJ51784@cicely8.cicely.de> References: <20020221124731.Z65817@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.26i X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Feb 20, 2002 at 06:31:14PM -0800, Julian Elischer wrote: > > > > On Thu, 21 Feb 2002, Greg Lehey wrote: > > > On Tuesday, 19 February 2002 at 0:00:19 -0800, Peter Wemm wrote: > > > Am I the only person who, despite careful scrutiny, missed this > > announcement? I would have thought that this would at least have been > > worth a HEADS UP and prior discussion in -core. I've just checked my > > -core archive, and though we discuss this repo from time to time, > > there was nothing there to suggest that it was publicly available. > > Even better is that the stuff is exported to a CVS tree and CVSupped out > so you can actually work on it. > (of course the version numbers are wierd but that doesn't matter) There is still missing an overview over the p4 collections. No - I'm not going to cvsup p4-all - I already had an increasing of 1G overnight without a single warning. A p4-self collection is also missing. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 19:56: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 5BF2337B402; Wed, 20 Feb 2002 19:55:57 -0800 (PST) Received: from pool0050.cvx22-bradley.dialup.earthlink.net ([209.179.198.50] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16dkKp-00031G-00; Wed, 20 Feb 2002 19:55:56 -0800 Message-ID: <3C746FC1.897E759C@mindspring.com> Date: Wed, 20 Feb 2002 19:55:45 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: Greg Lehey , Jake Burkholder , David O'Brien , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> <20020221111915.N65817@wantadilla.lemis.com> <200202210146.g1L1kqg91511@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon wrote: > I'm not interested in using P4. I think it's a mistake. That is, I > think it is being severely overused. At the very least it is preventing > me from comitting simple things to -current because as far as I can tell > when you add up the junk sitting in P4 it touches almost every file > in the kernel tree. Everything I've tried to work on has some hack > sitting in P4 somewhere that somebody hasn't committed. By the same token, you have also stated: ] Well... try again. If something ought to be compatible in a piecemeal ] commit and isn't, then something unexpected happened and you need to ] find out what it was. Doing a full-on commit for something like the ] proc lock patch is far too dangerous. It's just too large a patch set ] and we know from experience (cam, softupdates, etc...) that having a ] small handful of people testing a large private patch is not going to ] find all the bugs. How do you reconcile these divergent points of view? > I would like to see John commit his ucred stuff with Giant > instrumentation. If he doesn't want to do it then I would like him > to give me permission to do it from my tree now. I see no reason why > we should have to wait another X days or weeks to see this stuff in > the main tree. It just makes no sense to me. What large scale changes are "OK", and what large scale changes are "too dangerous"? Do you have a set of rules, that would let us look at a patch set and instantly decide which of these two categories the code fell into? I'm not trying to be a jerk, but not everything can be broken down into 1 line commits, and not everything can be broken down into 8 line commits, or 64 line commits, or 512 line commits, etc. (if you'll forgive my proof by induction). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 20: 5:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id A167937B400; Wed, 20 Feb 2002 20:05:43 -0800 (PST) Received: from pool0050.cvx22-bradley.dialup.earthlink.net ([209.179.198.50] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16dkUI-0006FX-00; Wed, 20 Feb 2002 20:05:43 -0800 Message-ID: <3C74720C.CCC8AF1E@mindspring.com> Date: Wed, 20 Feb 2002 20:05:32 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: David O'Brien , "M. Warner Losh" , current@FreeBSD.ORG Subject: Re: Version control software (was: Patch sets to date and timing tests with Giant out of userret.) References: <20020219080019.8F1673A9A@overcee.wemm.org> <00cd01c1b926$82d35bb0$ef01a8c0@davidwnt> <20020219.135131.83283562.imp@village.org> <20020219164406.B29698@dragon.nuxi.com> <20020221124325.Y65817@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greg Lehey wrote: > On Tuesday, 19 February 2002 at 16:44:06 -0800, David O'Brien wrote: > > On Tue, Feb 19, 2002 at 01:51:31PM -0700, M. Warner Losh wrote: > >> Bitkeeper enforces the linux devleopment model > >> to a large extent, > > > > In what way(s)? > > I'd be interested in this too. I've been using Bitkeeper for, well, > Linux development, but I don't see anything which locks it in to that > direction. Of course, Bitkeeper isn't free either, so there's no > particular reason to prefer it to p4. Bitkeeper is free if you publish your repository; P4 is free if you are a free software project. Otherwise, they cost. Both are barriers to commercial utilization of free code, in the same way. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 20:25:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 3ABDE37B404; Wed, 20 Feb 2002 20:25:03 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.6/8.11.6) id g1L4P0126016; Thu, 21 Feb 2002 06:25:00 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200202210425.g1L4P0126016@zibbi.icomtek.csir.co.za> Subject: make release failure in kerberos To: nectar@freebsd.org Date: Thu, 21 Feb 2002 06:24:59 +0200 (SAT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Jacques, Make release fails here. Can it be your changes to kerberos? John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org ===> libexec/kdc ... cc -O -pipe -I/usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/include -I/usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc -I/usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/lib/krb5 -I/usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/lib/asn1 -I/usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/lib/hdb -I/usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/lib/roken -I/usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kuser -I/usr/obj/usr/src/kerberos5/libexec/kdc/../../lib/libasn1 -I/usr/obj/usr/src/kerberos5/libexec/kdc/../../lib/libhdb -I/usr/obj/usr/src/kerberos5/libexec/kdc -Wall -I/usr/src/kerberos5/libexec/kdc/../../include -I/usr/src/kerberos5/libexec/kdc/../../include -DHAVE_CONFIG_H -DINET6 -c /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c: In function `create_reply_ticket': /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:254: syntax error before `ticket' /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:268: warning: implicit declaration of function `krb_create_ticket' /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:268: `ticket' undeclared (first use in this function) /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:268: (Each undeclared identifier is reported only once /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:268: for each function it appears in.) /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:282: warning: implicit declaration of function `krb_life_to_time' /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c: In function `do_authenticate': /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:405: `v4_realm' undeclared (first use in this function) /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:407: warning: implicit declaration of function `db_fetch4' /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:435: warning: implicit declaration of function `get_des_key' /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:483: warning: implicit declaration of function `krb_time_to_life' /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c: In function `do_getticket': /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:587: `ANAME_SZ' undeclared (first use in this function) /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:588: `INST_SZ' undeclared (first use in this function) /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:589: `REALM_SZ' undeclared (first use in this function) /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:599: `v4_realm' undeclared (first use in this function) /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:646: syntax error before `ticket' /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:651: `SNAME_SZ' undeclared (first use in this function) /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:654: `ticket' undeclared (first use in this function) /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:666: warning: implicit declaration of function `decomp_ticket' /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:651: warning: unused variable `sinstance' /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:650: warning: unused variable `sname' /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:589: warning: unused variable `prealm' /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:588: warning: unused variable `pinst' /usr/src/kerberos5/libexec/kdc/../../../crypto/heimdal/kdc/kaserver.c:587: warning: unused variable `pname' *** Error code 1 Stop in /usr/src/kerberos5/libexec/kdc. *** Error code 1 Stop in /usr/src/kerberos5/libexec. *** Error code 1 Stop in /usr/src/kerberos5. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /home/src/release. End Thu Feb 21 01:27:59 SAST 2002 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 20:35: 8 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 69BD437B405; Wed, 20 Feb 2002 20:35:01 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1L4Z0H92642; Wed, 20 Feb 2002 20:35:00 -0800 (PST) (envelope-from dillon) Date: Wed, 20 Feb 2002 20:35:00 -0800 (PST) From: Matthew Dillon Message-Id: <200202210435.g1L4Z0H92642@apollo.backplane.com> To: Terry Lambert Cc: Greg Lehey , Jake Burkholder , "David O'Brien" , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> <20020221111915.N65817@wantadilla.lemis.com> <200202210146.g1L1kqg91511@apollo.backplane.com> <3C746FC1.897E759C@mindspring.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Matthew Dillon wrote: :> I'm not interested in using P4. I think it's a mistake. That is, I :> think it is being severely overused. At the very least it is preventing :> me from comitting simple things to -current because as far as I can tell :> when you add up the junk sitting in P4 it touches almost every file :> in the kernel tree. Everything I've tried to work on has some hack :> sitting in P4 somewhere that somebody hasn't committed. : :By the same token, you have also stated: : :] Well... try again. If something ought to be compatible in a piecemeal :] commit and isn't, then something unexpected happened and you need to :] find out what it was. Doing a full-on commit for something like the :] proc lock patch is far too dangerous. It's just too large a patch set :] and we know from experience (cam, softupdates, etc...) that having a :] small handful of people testing a large private patch is not going to :] find all the bugs. : :How do you reconcile these divergent points of view? These are not divergent points of view. I am saying quite clearly that the ucred code and proc-locking code can be committed in a piecemeal fashion. In fact, good chunk of the proc locking code already has been with no ill effect on the tree - it might not be completely operational due to Giant, but just comitting it tests a great deal of infrastructure including potential lock order reversals and mismatched locks. That's the whole point of doing things this way. :What large scale changes are "OK", and what large scale changes :are "too dangerous"? The best example I can think of is Julian's initial KSE commit, where he rearranged the proc structure. The rearrangement touched a huge number of files and the commit had to be made all at once, not file by file, due to the structural changes. :Do you have a set of rules, that would let us look at a patch :set and instantly decide which of these two categories the :code fell into? : :I'm not trying to be a jerk, but not everything can be broken :down into 1 line commits, and not everything can be broken down :into 8 line commits, or 64 line commits, or 512 line commits, :etc. (if you'll forgive my proof by induction). : :-- Terry This is getting a bit absurd. I am arguing a general principle here, you are not contributing anything by stretching it into an irrational statement. One line commits? Oh come on! I will say that the work *I* am doing on -current is mostly piecemeal in nature. I even expect the VM locking to wind up being piecemeal. Everything I have posted to date has been piecemeal. For example, the ucred patchset I posted does not patch all the ucred functions, it just patched the read-only functions. But as a side effect that gave me a basis to track down the other uses of Giant in the general syscall path. That was a good demarkation point for me. It is by no means the end... it is, as I have said, piecemeal. The result? I was able to immediately note the use of Giant in trap.c (the ucred clearing code) as well as its use in userret(), plus I could test a few of the ucred functions like getuid() and test the Giant instrumentation. So you see, a piecemeal commit can have a great ability to move the development process forward. When you spend weeks or months putting together an UBER-patch you do not get any of that... it's all delayed and when the patch finally goes in people wind up spending a lot of time testing the patch itself rather then working on the ramification of what the patch allows you to move on to. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 20:48:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id ACBD537B41F for ; Wed, 20 Feb 2002 20:48:18 -0800 (PST) Received: (qmail 23516 invoked from network); 21 Feb 2002 04:48:15 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.152.92]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 21 Feb 2002 04:48:15 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020221111915.N65817@wantadilla.lemis.com> Date: Wed, 20 Feb 2002 23:48:12 -0500 (EST) From: John Baldwin To: Greg Lehey Subject: Re: Patch to improve mutex collision performance Cc: current@FreeBSD.ORG, "David O'Brien" , Matthew Dillon , Jake Burkholder Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 21-Feb-02 Greg Lehey wrote: > On Monday, 18 February 2002 at 15:38:07 -0500, Jake Burkholder wrote: >> Apparently, On Mon, Feb 18, 2002 at 11:51:44AM -0800, >> Matthew Dillon said words to the effect of; >>> I'm fairly sure JHB does not have a patch to address this but, please, >>> be my guest and check P4. >> >> Actually he does. Maybe you should have checked p4 first yourself. > > Well, maybe, like me, he doesn't know how. I only recently learnt of > the existence of this repo, and I still don't know where it is. It > certainly wasn't announced on the SMP mailing list. I've seen a few > references to p4 there, but no indication of how to access the repo. > >> What John's patch does is spin while the lock owner is running on >> another cpu. Spinning while there are no other processes on the run >> queues as well makes sense but you'll also be doing a lot of >> acquires and releases of sched_lock. > > I must be misinterpreting this statement. Under what circumstances do > you spin? Yes, I read the "while the owner is running in another > CPU", but the way I read that, it turns the blocking lock into a spin > lock. Only in some cases. This is the classic way of implementing an adaptive mutex. You spin if the other thread is actually executing on another CPU (the idea being it will release the lock soon so you are better off avoiding the context switch) and block if it is not executing on another CPU (releasing the lock is already at least one context switch away, so we might as well switch). > Greg > -- > See complete headers for address and phone numbers > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 20:48:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id 9B65637B416 for ; Wed, 20 Feb 2002 20:48:07 -0800 (PST) Received: (qmail 1231 invoked from network); 21 Feb 2002 04:48:05 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.152.92]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 21 Feb 2002 04:48:05 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200202210102.g1L12MR91194@apollo.backplane.com> Date: Wed, 20 Feb 2002 23:47:58 -0500 (EST) From: John Baldwin To: Matthew Dillon Subject: Re: RE: Patch to improve mutex collision performance Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 21-Feb-02 Matthew Dillon wrote: > This sounds better but why do we need a 'pause' at all? I don't > think spinning in this case will have any effect on power > consumption. The pause is extra stuff mostly needed for the HyperThreading stuff on the Pentium4 and also it helps improve cache performance on the P4. Talk to Peter about it. It's really a separate deal but this was a quick cut 'n paste. The actual kernel preemption code will reduce the number of context switches back and forth on mutex release since it only preempts the kernel for real-time (i.e. interrupt) kernel threads. Currently we will preempt one non-RT kthread for another. When I talked to the guy who worked on Irix's ithread stuff at Usenix, he said that adaptive locks actually ended up hurting performance, so I would prefer to not put this in until after preemption is in and then do some testing to see if adaptive mutexes help or hurt more. > -Matt > Matthew Dillon > > >:I would rather make the locks adaptive like so: (untested) >: >:--- //depot/projects/smpng/sys/conf/options 2002/02/08 13:19:07 >:+++ //depot/user/jhb/lock/conf/options 2002/02/08 13:50:54 >:@@ -56,6 +56,7 @@ >: # mapped I/O >: >: # Miscellaneous options. >:+ADAPTIVE_MUTEXES >: BLEED >: COMPAT_43 opt_compat.h >: COMPAT_SUNOS opt_compat.h >:--- //depot/projects/smpng/sys/i386/include/cpufunc.h 2001/12/18 13:07:32 >:+++ //depot/user/jhb/lock/i386/include/cpufunc.h 2001/12/20 15:54:32 >:@@ -550,6 +550,12 @@ >: __asm __volatile("movl %0,%%dr7" : : "r" (sel)); >: } >: >:+static __inline void >:+cpu_pause(void) >:+{ >:+ __asm __volatile("pause"); >:+} >:+ >: static __inline critical_t >: cpu_critical_enter(void) >: { >:--- //depot/projects/smpng/sys/kern/kern_mutex.c 2002/02/08 14:19:21 >:+++ //depot/user/jhb/lock/kern/kern_mutex.c 2002/02/08 13:50:54 >:@@ -34,6 +34,7 @@ >: * Machine independent bits of mutex implementation. >: */ >: >:+#include "opt_adaptive_mutexes.h" >: #include "opt_ddb.h" >: >: #include >:@@ -345,7 +354,22 @@ >: continue; >: } >: >:+#if defined(SMP) && defined(ADAPTIVE_MUTEXES) >: /* >:+ * If the current owner of the lock is executing on another >:+ * CPU, spin instead of blocking. >:+ */ >:+ if (((struct thread *)(v & MTX_FLAGMASK)->td_kse->kse_oncpu >:!= >:+ NOCPU) { >:+ mtx_unlock_spin(&sched_lock); >:+#ifdef __i386__ >:+ cpu_pause(); >:+#endif >:+ continue; >:+ } >:+#endif /* SMP && ADAPTIVE_MUTEXES */ >:+ >:+ /* >: * We deffinately must sleep for this lock. >: */ >: mtx_assert(m, MA_NOTOWNED); >:@@ -433,6 +457,9 @@ >: /* Give interrupts a chance while we spin. */ >: critical_exit(); >: while (m->mtx_lock != MTX_UNOWNED) { >:+#ifdef __i386__ >:+ cpu_pause(); >:+#endif >: if (i++ < 10000000) >: continue; >: if (i++ < 60000000) >: >:This is more a specific problem with Giant and I don't think it will be a >:problem with other mutexes, so I'd prefer a solution not quite so tailored to >:this particular behavior of Giant. >: >:-- >: >:John Baldwin <>< http://www.FreeBSD.org/~jhb/ >:"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 20:48:52 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail12.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with ESMTP id EC4B637B425 for ; Wed, 20 Feb 2002 20:48:26 -0800 (PST) Received: (qmail 31798 invoked from network); 21 Feb 2002 04:48:24 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.152.92]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 21 Feb 2002 04:48:24 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200202210235.SAA415110@meer.meer.net> Date: Wed, 20 Feb 2002 23:48:24 -0500 (EST) From: John Baldwin To: "George V. Neville-Neil" Subject: Re: FreeBSD Project management (was: Patch sets to date and timi Cc: current@FreeBSD.ORG, Matthew Dillon , Peter Wemm , Greg Lehey Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 21-Feb-02 George V. Neville-Neil wrote: > I'm not in the core of the SMP stuff (the closest I'll get is the > networking stuff) but I wonder if there is: > > 1) A work list of things that need to be done. > > 2) If that list is easy to read/update. > > Has anyone considered a Wiki to do this kind of coordination? We used > TWiki at my last employer to decent effect. Check out www.twiki.org. There is http://www.freebsd.org/smp/ If someone wanted to convert this over to Twiki, go for it. New ideas to add to the list are welcome as well. > Later, > George > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 21:32:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id C4A8E37B405; Wed, 20 Feb 2002 21:32:15 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 34F047830E; Thu, 21 Feb 2002 16:02:12 +1030 (CST) Date: Thu, 21 Feb 2002 16:02:12 +1030 From: Greg Lehey To: John Baldwin Cc: current@FreeBSD.ORG, David O'Brien , Matthew Dillon , Jake Burkholder Subject: Re: Patch to improve mutex collision performance Message-ID: <20020221160212.H65817@wantadilla.lemis.com> References: <20020221111915.N65817@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday, 20 February 2002 at 23:48:12 -0500, John Baldwin wrote: > > On 21-Feb-02 Greg Lehey wrote: >> On Monday, 18 February 2002 at 15:38:07 -0500, Jake Burkholder wrote: >>> Apparently, On Mon, Feb 18, 2002 at 11:51:44AM -0800, >>> Matthew Dillon said words to the effect of; >>>> I'm fairly sure JHB does not have a patch to address this but, please, >>>> be my guest and check P4. >>> >>> Actually he does. Maybe you should have checked p4 first yourself. >> >> Well, maybe, like me, he doesn't know how. I only recently learnt of >> the existence of this repo, and I still don't know where it is. It >> certainly wasn't announced on the SMP mailing list. I've seen a few >> references to p4 there, but no indication of how to access the repo. >> >>> What John's patch does is spin while the lock owner is running on >>> another cpu. Spinning while there are no other processes on the run >>> queues as well makes sense but you'll also be doing a lot of >>> acquires and releases of sched_lock. >> >> I must be misinterpreting this statement. Under what circumstances do >> you spin? Yes, I read the "while the owner is running in another >> CPU", but the way I read that, it turns the blocking lock into a spin >> lock. > > Only in some cases. This is the classic way of implementing an adaptive mutex. Well, no, the classic way of implementing an adaptive lock is to spin a little bit and then block. Alternatives would be to learn what's going on and then decide whether to spin or block, or how long to spin before blocking. I've never heard it applied to a choice of CPU. Obviously any "spin lock" shouldn't spin if the lock holder is in the same CPU. > You spin if the other thread is actually executing on another CPU (the idea > being it will release the lock soon so you are better off avoiding the context > switch) and block if it is not executing on another CPU (releasing the lock is > already at least one context switch away, so we might as well > switch). If you're talking about Giant here, one of us is seriously misunderstanding something. The whole idea of Giant is that it should be a blocking lock, not a spin lock. Tell me I'm misunderstanding you. The very first project milestone at http://www.freebsd.org/smp/ read "Convert the giant lock from spinning to blocking". You might say "ah, but the average system call takes less time than a schedule". We can test that. I've run lmbench on zaphod and found: Scheduling overhead: 18 µs Null syscall (1 CPU): 9 µs Null syscall (2 CPUs): 57 µs So this doesn't stand up. Note also that if there are more than two CPUs, the loss of time is much more significant. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 20 23:26:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from outboundx.mv.meer.net (outboundx.mv.meer.net [209.157.152.12]) by hub.freebsd.org (Postfix) with ESMTP id BD40737B402; Wed, 20 Feb 2002 23:26:43 -0800 (PST) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by outboundx.mv.meer.net (8.11.6/8.11.6) with ESMTP id g1L7Qds65378; Wed, 20 Feb 2002 23:26:39 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from neville-neil.com ([209.157.133.226]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id XAA429886; Wed, 20 Feb 2002 23:24:17 -0800 (PST) Message-Id: <200202210724.XAA429886@meer.meer.net> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: John Baldwin Cc: current@FreeBSD.org, smp@FreeBSD.org Subject: Re: FreeBSD Project management (was: Patch sets to date and timi In-Reply-To: Message from John Baldwin of "Wed, 20 Feb 2002 23:48:24 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Feb 2002 23:24:15 -0800 From: "George V. Neville-Neil" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > There is http://www.freebsd.org/smp/ > > If someone wanted to convert this over to Twiki, go for it. New ideas to add > to the list are welcome as well. > I'll install TWiki on my home server tomorrow and publish when I'm ready, probably a day or so if all goes well. Then people can try it out and if people like it that will be fine. I'll write up a short email with pointers etc. so people will have an idea what to expect. If people hate it, well there is always rm :-) Later, George -- George V. Neville-Neil gnn@neville-neil.com NIC:GN82 "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 1:13: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from harrier.prod.itd.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by hub.freebsd.org (Postfix) with ESMTP id 3FA1F37B404; Thu, 21 Feb 2002 01:12:58 -0800 (PST) Received: from pool0063.cvx40-bradley.dialup.earthlink.net ([216.244.42.63] helo=mindspring.com) by harrier.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16dpHW-000786-00; Thu, 21 Feb 2002 01:12:53 -0800 Message-ID: <3C74B9EA.9692E27E@mindspring.com> Date: Thu, 21 Feb 2002 01:12:10 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: Greg Lehey , Jake Burkholder , David O'Brien , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> <20020221111915.N65817@wantadilla.lemis.com> <200202210146.g1L1kqg91511@apollo.backplane.com> <3C746FC1.897E759C@mindspring.com> <200202210435.g1L4Z0H92642@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon wrote: [ ... ] > :How do you reconcile these divergent points of view? > > These are not divergent points of view. I am saying quite clearly that > the ucred code and proc-locking code can be committed in a piecemeal > fashion. In fact, good chunk of the proc locking code already has been > with no ill effect on the tree - it might not be completely operational > due to Giant, but just comitting it tests a great deal of infrastructure > including potential lock order reversals and mismatched locks. That's > the whole point of doing things this way. If you'll notice, the post to which you are replying was posted before your last post on the same topic. > :Do you have a set of rules, that would let us look at a patch > :set and instantly decide which of these two categories the > :code fell into? > : > :I'm not trying to be a jerk, but not everything can be broken > :down into 1 line commits, and not everything can be broken down > :into 8 line commits, or 64 line commits, or 512 line commits, > :etc. (if you'll forgive my proof by induction). > > This is getting a bit absurd. I am arguing a general principle here, > you are not contributing anything by stretching it into an irrational > statement. One line commits? Oh come on! I'm asking because I've made changes like this which never got in, and the review cycle was such that unless they were reviewed immediately, the patches wouldn't cleanly apply. In other words, anything that makes an interface change is going to fall into the category os "too big". I've also done changes that were very large scale, and could be broken up, but when they were actually broken up, there was no obvious benefit to about 3/4's of them, so the broken up pieces were labelled as "gratuitous", when in fact they were necessary foundation work for the last 1/4 of the changes. Rarely, I've made sweeping changes, and they've been sheparded into the source tree by Julian's dogged (and appreciated) persistance, e.g. when I rewrote init_main.c and added the original SYSINIT() construct using linker sets, or reinvented later by someone else, e.g. my nameifree() changes to make it so that there was no longer a "caller allocate/callee free" interface for nameidata. Other people's code has dropped by the wayside completely, and been lost; the SACK/TSACK work Luigi did never got integrated and accepted by the project, and LRP code that Peter Druschel and Gaurav Banga did at Rice University, which was originally done against FreeBSD 2.2. For that matter, we've also lost out on integration of the IO-Lite code, also from Rice (both were a result of the ScalaServer project). Likewise, the CMU work on TCP Rate Halving (admittedly, it's based on NetBSD 1.3.2, but that's not that significantly different from FreeBSD to matter), as well as their FACK/SACK implementation. It just seems to me that FreeBSD is blocking integration of important research advances, and I don't see a clear criteria being used to make this decision... a "general principle". > I will say that the work *I* am doing on -current is mostly piecemeal > in nature. I even expect the VM locking to wind up being piecemeal. > Everything I have posted to date has been piecemeal. For example, > the ucred patchset I posted does not patch all the ucred functions, > it just patched the read-only functions. But as a side effect that > gave me a basis to track down the other uses of Giant in the general > syscall path. That was a good demarkation point for me. It is by > no means the end... it is, as I have said, piecemeal. Not "everything to date"; "everything recently", perhaps. It was not so long ago that you had your commit priviledges yanked for, in effect, producing code faster than it could be reviewed and vetted, so you checked in anyway. You've got them back, and have since got the "incremental changes" religion: there are none so zealous as a recent convert, it seems. Right now, you're trying to enforce this world-view, which was enforced on you, on others. All I'm asking is "where is the line in the sand?". I know that a lot of the people doing work in the P4 repository would just as soon be commiting to the main CVS repository, instead, but, frankly, they are not *permitted* to do this. So they do the work in P4, in order to build a consensus around the code, so that it can be jammed in over the "go slooooooooow" objections. > The result? I was able to immediately note the use of Giant in > trap.c (the ucred clearing code) as well as its use in userret(), > plus I could test a few of the ucred functions like getuid() and test > the Giant instrumentation. Look, I'm not faulting your work, or your choice of the "interesting problems" you choose to work on, but I do maintain that not everything can be done as incrementally as you seem to want it done these days. You as much as admitted this yourself in your previous postings, and then went on to say that committing the prime example of current work of this nature is "too dangerous". All I'm asking for is "where is ``dangerous, but not too dangerous'' so it can be targeted". > So you see, a piecemeal commit can have a great ability to move the > development process forward. When you spend weeks or months putting > together an UBER-patch you do not get any of that... it's all delayed > and when the patch finally goes in people wind up spending a lot of > time testing the patch itself rather then working on the ramification > of what the patch allows you to move on to. That works great for incremental changes, which can be brought in peicemeal. Interface changes to widely used interfaces don't fall into that category (CAM is the biggest recent example of this, IMO). Patches which are, for lack of a better metaphor, nothing but road-bed materials, could never get in over the hurdle of "gratuitous changes". It's amazingly ironic that major changes (e.g. newbus) are allowed in without usage documentation at all, whereas things like SACK or FACK, with dozens of research papers aren't. Again, not to be a jerk, but I'd like to see the "dangerous" code committed to the main source tree. Willing testers have not worked in the past, so unwilling testers (like those for CAM and the character device removal changes) should be used: people have had their chance so far, and if they have not availed themselves of it, well, we have the choice of incrementally making the changes only to find out right before 5.0 ships that there was some part of the problem space not mapped by the code, that wasn't seen because no one got there in time. It's best to fail fast and early, and so have room to try again, then to fail slow and late, and not have time to retry. This is basically the only way to reconcile your complaint about developement going forward in the P4 repository, and leaving the main CVS repository "out of sync". -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 1:49:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 1B45537B400 for ; Thu, 21 Feb 2002 01:49:18 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g1L9nDi13999 for current@FreeBSD.ORG; Thu, 21 Feb 2002 01:49:13 -0800 (PST) (envelope-from obrien) Date: Thu, 21 Feb 2002 01:49:09 -0800 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance Message-ID: <20020221014909.A13952@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> <20020221111915.N65817@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020221111915.N65817@wantadilla.lemis.com>; from grog@FreeBSD.org on Thu, Feb 21, 2002 at 11:19:15AM +1030 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >> I'm fairly sure JHB does not have a patch to address this but, please, >> be my guest and check P4. > > Actually he does. Maybe you should have checked p4 first yourself. Users of Perforce are starting to force the rest of us to learn and use it. That is totally not acceptable for the general FreeBSD population. Those that chose to use it because they feel the tool is useful for THEMSELVES are of course free to use it. HOWEVER, Perforce is NOT the CM system of the FreeBSD project. Thus users of Perforce are expected to share their bits via posting patches, not forcing everyone to pull them out of the Perforce depot. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 2: 4:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 0017137B400; Thu, 21 Feb 2002 02:04:10 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g1LA3gI14114; Thu, 21 Feb 2002 02:03:42 -0800 (PST) (envelope-from obrien) Date: Thu, 21 Feb 2002 02:03:41 -0800 From: "David O'Brien" To: Stijn Hoop Cc: "Alexander N. Kabaev" , Bjoern Fischer , current@freebsd.org, freebsd-gnats-submit@freebsd.org, vova@sw.ru Subject: Re: ports/34908: libpng port makes bad dynamic library on -CURRENT Message-ID: <20020221020341.C13952@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <3C6D49E0.3000506@gte.com> <20020221000531.A57633@pcwin002.win.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020221000531.A57633@pcwin002.win.tue.nl>; from stijn@win.tue.nl on Thu, Feb 21, 2002 at 12:05:31AM +0100 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 21, 2002 at 12:05:31AM +0100, Stijn Hoop wrote: > I ventured into this brave new world a few days ago and ran into > this very problem. Alexander's patch (along with a make install in > /usr/src/gnu/usr.bin/binutils) fixed it, as advertised. > > Maybe this can now be committed? NOT until I have sufficient feedback from the FSF Binutils developers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 5: 2:55 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 5EBA137B404; Thu, 21 Feb 2002 05:02:50 -0800 (PST) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.1/8.12.1) with ESMTP id g1LD2V4b024520; Thu, 21 Feb 2002 08:02:31 -0500 (EST) Date: Thu, 21 Feb 2002 08:02:31 -0500 (EST) From: Daniel Eischen To: Greg Lehey Cc: John Baldwin , current@FreeBSD.ORG, "David O'Brien" , Matthew Dillon , Jake Burkholder Subject: Re: Patch to improve mutex collision performance In-Reply-To: <20020221160212.H65817@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 21 Feb 2002, Greg Lehey wrote: > On Wednesday, 20 February 2002 at 23:48:12 -0500, John Baldwin wrote: > > > >>> What John's patch does is spin while the lock owner is running on > >>> another cpu. Spinning while there are no other processes on the run > >>> queues as well makes sense but you'll also be doing a lot of > >>> acquires and releases of sched_lock. > >> > >> I must be misinterpreting this statement. Under what circumstances do > >> you spin? Yes, I read the "while the owner is running in another > >> CPU", but the way I read that, it turns the blocking lock into a spin > >> lock. > > > > Only in some cases. This is the classic way of implementing an adaptiv= e mutex. >=20 > Well, no, the classic way of implementing an adaptive lock is to spin > a little bit and then block. Alternatives would be to learn what's > going on and then decide whether to spin or block, or how long to spin > before blocking. I've never heard it applied to a choice of CPU. > Obviously any "spin lock" shouldn't spin if the lock holder is in the > same CPU. The spin only if the owner is running on another CPU is an optimization. There's no sense in spinning unconditionally when you can see if the mutex' owner is running on another CPU. This is how adaptive mutexes in Solaris work also. > > You spin if the other thread is actually executing on another CPU (the = idea > > being it will release the lock soon so you are better off avoiding the = context > > switch) and block if it is not executing on another CPU (releasing the = lock is > > already at least one context switch away, so we might as well > > switch). >=20 > If you're talking about Giant here, one of us is seriously > misunderstanding something. The whole idea of Giant is that it should > be a blocking lock, not a spin lock. Tell me I'm misunderstanding > you. The very first project milestone at http://www.freebsd.org/smp/ > read "Convert the giant lock from spinning to blocking". The spin should be very short lived if the current owner is running on another CPU. There is a lot of overhead in blocking and switching contexts, plus don't you also have to take sched lock if you block? If you know the current owner of the mutex is running on another CPU, then you should acquire the mutex within a few cycles. You have to make the assumption that mutexes are held for very short periods of time, and that there are not a lot of highly contested adaptive mutexes. > You might say "ah, but the average system call takes less time than a > schedule". We can test that. I've run lmbench on zaphod and found: >=20 > Scheduling overhead:=0918 =B5s > Null syscall (1 CPU):=09 9 =B5s > Null syscall (2 CPUs):=0957 =B5s >=20 > So this doesn't stand up. Note also that if there are more than two > CPUs, the loss of time is much more significant. --=20 Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 5:13:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id B110037B402 for ; Thu, 21 Feb 2002 05:13:24 -0800 (PST) Received: from madman.nectar.cc (madman.nectar.cc [10.0.1.111]) by gw.nectar.cc (Postfix) with ESMTP id 177D03A; Thu, 21 Feb 2002 07:13:24 -0600 (CST) Received: (from nectar@localhost) by madman.nectar.cc (8.11.6/8.11.6) id g1LDDNw22784; Thu, 21 Feb 2002 07:13:23 -0600 (CST) (envelope-from nectar) Date: Thu, 21 Feb 2002 07:13:23 -0600 From: "Jacques A. Vidrine" To: John Hay Cc: current@freebsd.org Subject: Re: make release failure in kerberos Message-ID: <20020221131323.GA22765@madman.nectar.cc> References: <200202210425.g1L4P0126016@zibbi.icomtek.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200202210425.g1L4P0126016@zibbi.icomtek.csir.co.za> User-Agent: Mutt/1.3.27i X-Url: http://www.nectar.cc/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 21, 2002 at 06:24:59AM +0200, John Hay wrote: > Hi Jacques, > > Make release fails here. Can it be your changes to kerberos? Could be; I'll have a look. Thanks! -- Jacques A. Vidrine http://www.nectar.cc/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos jvidrine@verio.net . nectar@FreeBSD.org . nectar@kth.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 5:32:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 9130537B402 for ; Thu, 21 Feb 2002 05:32:45 -0800 (PST) Received: from blossom.cjclark.org ([12.234.91.48]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020221133245.IQVF2951.rwcrmhc53.attbi.com@blossom.cjclark.org> for ; Thu, 21 Feb 2002 13:32:45 +0000 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.6) id g1LDWim79845 for current@freebsd.org; Thu, 21 Feb 2002 05:32:44 -0800 (PST) (envelope-from cjc) Date: Thu, 21 Feb 2002 05:32:44 -0800 From: "Crist J. Clark" To: current@freebsd.org Subject: HEADS UP: Minor rc.firewall{,6} Change Message-ID: <20020221053244.S48401@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just made a few _minor_ changes to the rc.firewall{,6} scripts. The vast majority of users will not be affected. However, since a few may be, and this is a security issue with the potential to cause some subtle breakage, I felt a small HEADS UP was in order. (For the very security conscious and paranoid, note that this change can only "fail-safe" if people apply it blindly. You'll be "more secure," but it may break stuff.) If you do not use firewalling or rc.firewall{,6} at all (that is, you do not have 'firewall_enable="YES"' and/or 'ipv6_firewall_enable="YES"') or if you use custom rc.firewall{,6} scripts, you are not affected. Two groups of people who use the provided firewall scripts are affected: 1) Those who put a rules file in the 'firewall_type' variable, or 2) Those who put a non-existent type in the 'firewall_type' variable. In both cases, you will no longer get the rules, 100 pass all from any to any via lo0 200 deny all from any to 127.0.0.0/8 300 deny ip from 127.0.0.0/8 to any In rc.firewall, and, 100 pass all from any to any via lo0 200 pass ipv6-icmp from :: to ff02::/16 300 pass ipv6-icmp from fe80::/10 to fe80::/10 400 pass ipv6-icmp from fe80::/10 to ff02::/16 In rc.firewall6 added to your firewall by the system scripts. If you are in group (1), you should add whatever rules like these _you_ want for _your_ site into your rule file. If you are in group (2), use 'firewall_type="closed"' (which now works as advertised) will give you the same effect as your current configuration. The motivation for the change was mainly for the people in group (1). Up until now, those rules were added _unconditionally_ by the rc.network{,6} scripts. For people who want to define their own rulesets outside of the simple ones provided in the rc.firewall{,6} scripts, the system should make NO assumptions about your site's policy and be adding rules. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@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 Feb 21 5:33:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from mharnois.mdharnois.net (customer-mpls-23.cpinternet.com [209.240.253.23]) by hub.freebsd.org (Postfix) with ESMTP id CC62F37B405; Thu, 21 Feb 2002 05:33:29 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mharnois.mdharnois.net (Postfix) with ESMTP id 673A53C41; Thu, 21 Feb 2002 07:33:22 -0600 (CST) Subject: Re: ports/34908: libpng port makes bad dynamic library on -CURRENT From: "Michael D. Harnois" To: obrien@FreeBSD.ORG Cc: Stijn Hoop , "Alexander N. Kabaev" , Bjoern Fischer , current@FreeBSD.ORG, "freebsd-gnats-submit@FreeBSD. " Org , vova@sw.ru In-Reply-To: <20020221020341.C13952@dragon.nuxi.com> References: <3C6D49E0.3000506@gte.com> <20020221000531.A57633@pcwin002.win.tue.nl> <20020221020341.C13952@dragon.nuxi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 21 Feb 2002 07:33:22 -0600 Message-Id: <1014298402.526.33.camel@mharnois.mdharnois.net> Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2002-02-21 at 04:03, David O'Brien wrote: > On Thu, Feb 21, 2002 at 12:05:31AM +0100, Stijn Hoop wrote: > > > > Maybe this can now be committed? > > NOT until I have sufficient feedback from the FSF Binutils developers. OK, I'm confused. binutils has been broken for three weeks. We have a patch that we know fixes, at the very least, one of the known problems. However, it can't be committed without feedback from the developers. So having binutils broken indefinitely is better than applying a patch that *might* have to be backed out or altered later? -- Michael D. Harnois bilocational bivocational Pastor, Redeemer Lutheran Church Washburn, Iowa 1L, UST School of Law Minneapolis, Minnesota Creative thought means that you forgot where you read it. --Stanley Hauerwas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 5:41:55 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 8552C37B416; Thu, 21 Feb 2002 05:41:51 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g1LDfcD39674; Thu, 21 Feb 2002 08:41:38 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Thu, 21 Feb 2002 08:41:38 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: "George V. Neville-Neil" Cc: Greg Lehey , Peter Wemm , Matthew Dillon , current@FreeBSD.ORG Subject: Re: FreeBSD Project management (was: Patch sets to date and timing tests with Giant out of userret.) In-Reply-To: <200202210235.SAA415110@meer.meer.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG http://www.freebsd.org/smp/ Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Wed, 20 Feb 2002, George V. Neville-Neil wrote: > I'm not in the core of the SMP stuff (the closest I'll get is the > networking stuff) but I wonder if there is: > > 1) A work list of things that need to be done. > > 2) If that list is easy to read/update. > > Has anyone considered a Wiki to do this kind of coordination? We used > TWiki at my last employer to decent effect. Check out www.twiki.org. > > Later, > George > > 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 Feb 21 6:52:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id 54C2737B402 for ; Thu, 21 Feb 2002 06:52:43 -0800 (PST) Received: (qmail 14900 invoked from network); 21 Feb 2002 14:52:42 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.90.117.117]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 21 Feb 2002 14:52:42 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020221014909.A13952@dragon.nuxi.com> Date: Thu, 21 Feb 2002 09:52:44 -0500 (EST) From: John Baldwin To: "David O'Brien" Subject: Re: Patch to improve mutex collision performance Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 21-Feb-02 David O'Brien wrote: >>> I'm fairly sure JHB does not have a patch to address this but, please, >>> be my guest and check P4. >> >> Actually he does. Maybe you should have checked p4 first yourself. > > Users of Perforce are starting to force the rest of us to learn and use > it. That is totally not acceptable for the general FreeBSD population. > Those that chose to use it because they feel the tool is useful for > THEMSELVES are of course free to use it. HOWEVER, Perforce is NOT the CM > system of the FreeBSD project. Thus users of Perforce are expected to > share their bits via posting patches, not forcing everyone to pull them > out of the Perforce depot. They are shared now just as often as before. Actually, more so. Remember the days of my one big sys.patch where I'd have to spend a night trying to commit the bits piecemeal? Contrast that with the way the MI pcpu stuff went in, or the first round of changes to add td_ucred. I actually have cron jobs that can generate updated diffs of the important p4 trees every 15 min or so but don't have most of them on for fear of hurting freefall with the extra load. You are asking for people to do more than they have done before and blaming their not doing it on the tools they are using. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 9:48:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from encontacto.net (adsl-64-173-182-158.dsl.mtry01.pacbell.net [64.173.182.158]) by hub.freebsd.org (Postfix) with ESMTP id A69A137B400; Thu, 21 Feb 2002 09:48:10 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) (uid 0) by encontacto.net with local; Thu, 21 Feb 2002 09:48:10 -0800 Received: from 64.173.182.155 ( [64.173.182.155]) as user eculp@mail.mexcomusa.net by Mail.MexComUSA.Net with HTTP; Thu, 21 Feb 2002 09:48:10 -0800 Message-ID: <1014313690.3c7532da5a5d2@Mail.MexComUSA.Net> Date: Thu, 21 Feb 2002 09:48:10 -0800 From: eculp@mail.mexcomusa.net To: Edwin Culp Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: compile errors after yesterdays cvsup and makeworld. References: <1014213239.3c73aa7769178@Mail.MexComUSA.Net> <20020220092230.B4493@dragon.nuxi.com> <1014234730.3c73fe6a5d619@Mail.MexComUSA.Net> In-Reply-To: <1014234730.3c73fe6a5d619@Mail.MexComUSA.Net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Originating-IP: 64.173.182.155 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I sure missed something, I'm sorry. I still have the problem with buildworld. What should I do to fix it? # /usr/bin/cc -print-search-dirs install: /usr/libexec/(null) programs: /usr/libexec/elf/ libraries: /usr/lib/ Thanks, ed Quoting Edwin Culp : > David, > > I see it's already fixed so I'll assume that you no longer need the > compiler output. I'm sorry that I didn't answer before but I just > checked my email and went to some meetings and am just getting back. > > Thanks for your help, > > ed > > Quoting David O'Brien : > > > On Wed, Feb 20, 2002 at 05:53:59AM -0800, Edwin Culp wrote: > > > On my daily build, my kernels are broken as per log: > > > > > > ===> wi > > > cd /usr/obj/usr/src/sys/PIII850N; > > MAKESRCPATH=/usr/src/sys/dev/aic7xxx/aicasm > > > make - > > > f /usr/src/sys/dev/aic7xxx/aicasm/Makefile > > > Warning: Object directory not changed from original > > /usr/obj/usr/src/sys/PIII850N > > > cc -O -pipe -I/usr/include -I. -c aicasm_gram.c > > > cc: installation problem, cannot exec `cpp0': No such file or directory > > > cc: installation problem, cannot exec `cc1': No such file or directory > > > *** Error code 1 > > > > > > I need to see the output of ``/usr/bin/cc -print-search-dirs'' from the > > problematic compiler. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > -- > To announce that there must be no criticism of the president, > or that we are to stand by the president, right or wrong, is not > only unpatriotic and servile, but is morally treasonable to > the American public. - Theodore Roosevelt > > > > --- > ------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 9:55:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id BA30137B42B; Thu, 21 Feb 2002 09:55:20 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id g1LHtIm73084; Thu, 21 Feb 2002 09:55:18 -0800 (PST) (envelope-from david) Date: Thu, 21 Feb 2002 09:55:18 -0800 (PST) From: David Wolfskill Message-Id: <200202211755.g1LHtIm73084@bunrab.catwhisker.org> To: eculp@casa-205.mexcomusa.net, eculp@encontacto.net Subject: Re: compile errors after yesterdays cvsup and makeworld. Cc: current@FreeBSD.ORG, obrien@FreeBSD.ORG In-Reply-To: <1014313690.3c7532da5a5d2@Mail.MexComUSA.Net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Date: Thu, 21 Feb 2002 09:48:10 -0800 >From: eculp@casa-205.mexcomusa.net >I sure missed something, I'm sorry. I still have the problem with >buildworld. What should I do to fix it? ># /usr/bin/cc -print-search-dirs >install: /usr/libexec/(null) >programs: /usr/libexec/elf/ >libraries: /usr/lib/ Well, you need to do something so the installed cc actually works. What worked for me was to do the following just before starting the "make buildworld"": * cd /usr/libexec/elf * ln -s ../cc* ../cpp* . Then go through the usual "make buildworld" & friends. After the "make installworld" is done (I actually did this after "mergemaster"): * cd /usr/libexec/elf * rm cc* cpp* Following the reboot, I created a "hello.c" in /tmp, typed "make", and was mildly gratified to see that it not only compiled without complaint, it even ran properly. :-} Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 10:14: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from beastie.jocose.org (beastie.jocose.org [199.199.226.71]) by hub.freebsd.org (Postfix) with SMTP id 3BE7237B47D for ; Thu, 21 Feb 2002 10:13:43 -0800 (PST) Received: (qmail 46090 invoked from network); 21 Feb 2002 19:13:39 -0000 Received: from unknown (HELO jocose.org) (10.0.0.100) by 0 with SMTP; 21 Feb 2002 19:13:39 -0000 Message-ID: <3C75395A.7030001@jocose.org> Date: Thu, 21 Feb 2002 12:15:54 -0600 From: Peter Schultz Organization: jocose.org User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.8) Gecko/20020219 X-Accept-Language: en-us MIME-Version: 1.0 To: "Michael D. Harnois" Cc: obrien@FreeBSD.ORG, Stijn Hoop , "Alexander N. Kabaev" , Bjoern Fischer , current@FreeBSD.ORG, "freebsd-gnats-submit@FreeBSD. Org" , vova@sw.ru Subject: Re: ports/34908: libpng port makes bad dynamic library on -CURRENT References: <3C6D49E0.3000506@gte.com> <20020221000531.A57633@pcwin002.win.tue.nl> <20020221020341.C13952@dragon.nuxi.com> <1014298402.526.33.camel@mharnois.mdharnois.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Michael D. Harnois wrote: > On Thu, 2002-02-21 at 04:03, David O'Brien wrote: > > >>On Thu, Feb 21, 2002 at 12:05:31AM +0100, Stijn Hoop wrote: >> >>>Maybe this can now be committed? >>> >>NOT until I have sufficient feedback from the FSF Binutils developers. >> > > OK, I'm confused. binutils has been broken for three weeks. We have a > patch that we know fixes, at the very least, one of the known roblems. > However, it can't be committed without feedback from the developers. > > So having binutils broken indefinitely is better than applying a patch > that *might* have to be backed out or altered later? > I would like to wait and see what David comes up with. I've applied the patch and things work for the most part, but there are some problems I'm having with the vim, open-motif-devel and AbiWord ports that I did not see until this patch. So I guess the lesson is that if you want to run -CURRENT you just have to roll with the punches. Pete... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 10:29:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from encontacto.net (adsl-64-173-182-158.dsl.mtry01.pacbell.net [64.173.182.158]) by hub.freebsd.org (Postfix) with ESMTP id 06E9237B402; Thu, 21 Feb 2002 10:29:28 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) (uid 0) by encontacto.net with local; Thu, 21 Feb 2002 10:29:27 -0800 Received: from 64.173.182.155 ( [64.173.182.155]) as user eculp@mail.mexcomusa.net by Mail.MexComUSA.Net with HTTP; Thu, 21 Feb 2002 10:29:27 -0800 Message-ID: <1014316167.3c753c87667b9@Mail.MexComUSA.Net> Date: Thu, 21 Feb 2002 10:29:27 -0800 From: Edwin Culp To: David Wolfskill Cc: current@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: compile errors after yesterdays cvsup and makeworld. References: <200202211755.g1LHtIm73084@bunrab.catwhisker.org> In-Reply-To: <200202211755.g1LHtIm73084@bunrab.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Originating-IP: 64.173.182.155 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Quoting David Wolfskill : > >Date: Thu, 21 Feb 2002 09:48:10 -0800 > >From: eculp@casa-205.mexcomusa.net > > >I sure missed something, I'm sorry. I still have the problem with > >buildworld. What should I do to fix it? > > ># /usr/bin/cc -print-search-dirs > >install: /usr/libexec/(null) > >programs: /usr/libexec/elf/ > >libraries: /usr/lib/ > > Well, you need to do something so the installed cc actually works. > > What worked for me was to do the following just before starting the > "make buildworld"": > > * cd /usr/libexec/elf > * ln -s ../cc* ../cpp* . David, Of course, I paniced. Thanks for the help. It sure seems to be working. It sure makes me feel good to see something compiling :-) Your help, as always is invaluable. Thanks, ed > > Then go through the usual "make buildworld" & friends. > > After the "make installworld" is done (I actually did this after > "mergemaster"): > > * cd /usr/libexec/elf > * rm cc* cpp* > > Following the reboot, I created a "hello.c" in /tmp, typed "make", and > was mildly gratified to see that it not only compiled without complaint, > it even ran properly. :-} > > Cheers, > david (links to my resume at http://www.catwhisker.org/~david) > -- > David H. Wolfskill david@catwhisker.org > I believe it would be irresponsible (and thus, unethical) for me to advise, > recommend, or support the use of any product that is or depends on any > Microsoft product for any purpose other than personal amusement. > ------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 11:11:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 7822C37B400; Thu, 21 Feb 2002 11:11:56 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 1B3A55341; Thu, 21 Feb 2002 20:11:53 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Bernd Walter Cc: Julian Elischer , Greg Lehey , Peter Wemm , current@FreeBSD.ORG Subject: Re: Perforce repo (was: Patch sets to date and timing tests with Giant out of userret.) References: <20020221124731.Z65817@wantadilla.lemis.com> <20020221033349.GJ51784@cicely8.cicely.de> From: Dag-Erling Smorgrav Date: 21 Feb 2002 20:11:52 +0100 In-Reply-To: <20020221033349.GJ51784@cicely8.cicely.de> Message-ID: Lines: 14 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bernd Walter writes: > There is still missing an overview over the p4 collections. > No - I'm not going to cvsup p4-all - I already had an increasing of > 1G overnight without a single warning. > A p4-self collection is also missing. p4-all is not a good idea - Perforce makes branching very cheap, and the repo reflects that :) There are currently 52 branches, some of which are full copies of the FreeBSD source tree, and some of which only include the kernel sources. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 11:31: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 4430837B405; Thu, 21 Feb 2002 11:30:11 -0800 (PST) Received: from pool0500.cvx21-bradley.dialup.earthlink.net ([209.179.193.245] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16dyuj-0001QU-00; Thu, 21 Feb 2002 11:29:57 -0800 Message-ID: <3C754AAA.9117A19@mindspring.com> Date: Thu, 21 Feb 2002 11:29:46 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Michael D. Harnois" Cc: obrien@FreeBSD.ORG, Stijn Hoop , "Alexander N. Kabaev" , Bjoern Fischer , current@FreeBSD.ORG, "freebsd-gnats-submit@FreeBSD. Org" , vova@sw.ru Subject: Re: ports/34908: libpng port makes bad dynamic library on -CURRENT References: <3C6D49E0.3000506@gte.com> <20020221000531.A57633@pcwin002.win.tue.nl> <20020221020341.C13952@dragon.nuxi.com> <1014298402.526.33.camel@mharnois.mdharnois.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Michael D. Harnois" wrote: > On Thu, 2002-02-21 at 04:03, David O'Brien wrote: > > On Thu, Feb 21, 2002 at 12:05:31AM +0100, Stijn Hoop wrote: > > > > > > Maybe this can now be committed? > > > > NOT until I have sufficient feedback from the FSF Binutils developers. > > OK, I'm confused. binutils has been broken for three weeks. We have a > patch that we know fixes, at the very least, one of the known problems. > However, it can't be committed without feedback from the developers. > > So having binutils broken indefinitely is better than applying a patch > that *might* have to be backed out or altered later? I believe the intent is to ensure that the patches make it back into the FSF distributed code, so that in the future, there is less maintenance required for FreeBSD platforms. This offloading of maintenance is a good idea, considering the stated positions of those with the currently thankless job of beating FSF code into submission to make it run on FreeBSD platforms. Actually, there was a discussion at BSDCon as to whether or not to drop the a.out support in order to decrease the patch size necessary to make the FSF distributed code do what FreeBSD needed it to do (personally, I would prefer that the a.out code generation be integrated back into the FSF code base but this is unlikely for FSF political reasons with regard to the intent to get rid of the a.out standard entirely). Such changes to the FreeBSD toolchain are necessary, unless there is sufficient support for what the FSF views as being gratuitous differences (e.g. not replacing BSD make with GNU make like FreeBSD is "supposed to do", etc.). While I would incredibly dislike losing a.out, since most of the promised advantages of ELF have not materialized (some, such as linking a library against a library have... but only for shared libraries), I have to side with David O'Brien, since he is at least actively involved in maintaining the code in question. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 11:50:55 2002 Delivered-To: freebsd-current@freebsd.org Received: from espresso.q9media.com (espresso.q9media.com [216.254.138.122]) by hub.freebsd.org (Postfix) with ESMTP id 9238A37B400; Thu, 21 Feb 2002 11:50:52 -0800 (PST) Received: (from mike@localhost) by espresso.q9media.com (8.11.6/8.11.6) id g1LJkKs00510; Thu, 21 Feb 2002 14:46:20 -0500 (EST) (envelope-from mike) Date: Thu, 21 Feb 2002 14:46:20 -0500 From: Mike Barcroft To: Terry Lambert Cc: Matthew Dillon , Greg Lehey , Jake Burkholder , "David O'Brien" , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance Message-ID: <20020221144620.B68344@espresso.q9media.com> References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> <20020221111915.N65817@wantadilla.lemis.com> <200202210146.g1L1kqg91511@apollo.backplane.com> <3C746FC1.897E759C@mindspring.com> <200202210435.g1L4Z0H92642@apollo.backplane.com> <3C74B9EA.9692E27E@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C74B9EA.9692E27E@mindspring.com>; from tlambert2@mindspring.com on Thu, Feb 21, 2002 at 01:12:10AM -0800 Organization: The FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert writes: > Other people's code has dropped by the wayside completely, and > been lost; the SACK/TSACK work Luigi did never got integrated > and accepted by the project, and LRP code that Peter Druschel > and Gaurav Banga did at Rice University, which was originally > done against FreeBSD 2.2. For that matter, we've also lost > out on integration of the IO-Lite code, also from Rice (both > were a result of the ScalaServer project). Likewise, the CMU > work on TCP Rate Halving (admittedly, it's based on NetBSD 1.3.2, > but that's not that significantly different from FreeBSD to matter), > as well as their FACK/SACK implementation. I'm getting sick of reading this. Terry, if you want this code integrated into FreeBSD, here's what you do: 1) Find yourself a mentor, 2) Get a commit bit, 3) Update worthy patchsets to -current sources, 4) Have them reviewed, 5) Commit them. If you aren't interested in doing this, you are the sole person to be blamed for them not being integrated into FreeBSD. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 12:15: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id F1F6C37B400; Thu, 21 Feb 2002 12:14:57 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 045385341; Thu, 21 Feb 2002 21:14:55 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Matthew Dillon Cc: Greg Lehey , Jake Burkholder , "David O'Brien" , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> <20020221111915.N65817@wantadilla.lemis.com> <200202210146.g1L1kqg91511@apollo.backplane.com> From: Dag-Erling Smorgrav Date: 21 Feb 2002 21:14:54 +0100 In-Reply-To: <200202210146.g1L1kqg91511@apollo.backplane.com> Message-ID: Lines: 17 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon writes: > I'm not interested in using P4. I think it's a mistake. That is, I > think it is being severely overused. [...] Frankly, although I use Perforce myself for PAM work, I agree with Matt here. Most of what is going on in the Perforce should be happening on branches in our main repo, if only CVS didn't suck so bad at branching. I would like to suggest that we consider transitioning our main repo to Subversion. It's reasonably similar to cvs, and has all the features we need that cvs lack: metadata versioning, atomic commits, cheap branching... DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 12:20:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 9002D37B400; Thu, 21 Feb 2002 12:20:19 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.6/8.11.6) with UUCP id g1LKKGA64984; Thu, 21 Feb 2002 21:20:16 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g1LKHcYd058643; Thu, 21 Feb 2002 21:17:38 +0100 (CET)?g (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.6/8.11.6) id g1LKHc957363; Thu, 21 Feb 2002 21:17:38 +0100 (CET) (envelope-from ticso) Date: Thu, 21 Feb 2002 21:17:37 +0100 From: Bernd Walter To: Dag-Erling Smorgrav Cc: Julian Elischer , Greg Lehey , Peter Wemm , current@FreeBSD.ORG Subject: Re: Perforce repo (was: Patch sets to date and timing tests with Giant out of userret.) Message-ID: <20020221201736.GD56929@cicely8.cicely.de> References: <20020221124731.Z65817@wantadilla.lemis.com> <20020221033349.GJ51784@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.26i X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 21, 2002 at 08:11:52PM +0100, Dag-Erling Smorgrav wrote: > Bernd Walter writes: > > There is still missing an overview over the p4 collections. > > No - I'm not going to cvsup p4-all - I already had an increasing of > > 1G overnight without a single warning. > > A p4-self collection is also missing. > > p4-all is not a good idea - Perforce makes branching very cheap, and > the repo reflects that :) There are currently 52 branches, some of > which are full copies of the FreeBSD source tree, and some of which > only include the kernel sources. Depends on what you want to do. I had p4-all on cvsup.de.freebsd.org, but it growed massively without warnings and the collectios had to be created manualy. I stoped distributing p4* because of disk space limitations in december. If there is no overview to show which cvsup servers hold these special collections most people will fall back to cvsup10.freebsd.org, if they ever know them. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 12:21:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from isris.pair.com (isris.pair.com [209.68.2.39]) by hub.freebsd.org (Postfix) with SMTP id 8B11437B402 for ; Thu, 21 Feb 2002 12:21:44 -0800 (PST) Received: (qmail 41460 invoked by uid 3130); 21 Feb 2002 20:21:43 -0000 Date: Thu, 21 Feb 2002 15:21:43 -0500 From: Garrett Rooney To: Dag-Erling Smorgrav Cc: Matthew Dillon , Greg Lehey , Jake Burkholder , David O'Brien , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance Message-ID: <20020221202143.GA23502@electricjellyfish.net> References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> <20020221111915.N65817@wantadilla.lemis.com> <200202210146.g1L1kqg91511@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.25i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 21, 2002 at 09:14:54PM +0100, Dag-Erling Smorgrav wrote: > Matthew Dillon writes: > > I'm not interested in using P4. I think it's a mistake. That is, I > > think it is being severely overused. [...] > > Frankly, although I use Perforce myself for PAM work, I agree with > Matt here. Most of what is going on in the Perforce should be > happening on branches in our main repo, if only CVS didn't suck so bad > at branching. > > I would like to suggest that we consider transitioning our main repo > to Subversion. It's reasonably similar to cvs, and has all the > features we need that cvs lack: metadata versioning, atomic commits, > cheap branching... As a Subversion developer and a FreeBSD user, I'd love to see this happen some day. Subversion is designed for precisely this sort of thing, a version control system for a project that likes many things about CVS, but doesn't wish to deal with its many drawbacks. Unfortunately, at the moment, Suversion is far from mature enough for such a transition. Some day, perhaps even some day soon, but not quite yet. What I would suggest though, is that FreeBSD developers who are interested in the possibility of such a transition int he future should subscribe to the Subversion development list (see http://subversion.tigris.org/ for instructions on how to subscribe) and try to make sure that the features we're currently building into subversion will meet FreeBSD's needs in the future. There have already been some NetBSD and Apple developers on the lists, along with a few FreeBSD people giving us valuable feedback, and any additional FreeBSD people would be very welcome. -garrett -- garrett rooney Unix was not designed to stop you from rooneg@electricjellyfish.net doing stupid things, because that would http://electricjellyfish.net/ stop you from doing clever things. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 12:50:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from harrier.prod.itd.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by hub.freebsd.org (Postfix) with ESMTP id 9AD7037B404; Thu, 21 Feb 2002 12:50:07 -0800 (PST) Received: from pool0500.cvx21-bradley.dialup.earthlink.net ([209.179.193.245] helo=mindspring.com) by harrier.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16e0AC-0005nA-00; Thu, 21 Feb 2002 12:50:00 -0800 Message-ID: <3C755D6C.BE8F1776@mindspring.com> Date: Thu, 21 Feb 2002 12:49:48 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Barcroft Cc: Matthew Dillon , Greg Lehey , Jake Burkholder , David O'Brien , current@FreeBSD.ORG Subject: "Forking" FreeBSD: CVS vs. P4 References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> <20020221111915.N65817@wantadilla.lemis.com> <200202210146.g1L1kqg91511@apollo.backplane.com> <3C746FC1.897E759C@mindspring.com> <200202210435.g1L4Z0H92642@apollo.backplane.com> <3C74B9EA.9692E27E@mindspring.com> <20020221144620.B68344@espresso.q9media.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Barcroft wrote: > I'm getting sick of reading this. Terry, if you want this code > integrated into FreeBSD, here's what you do: 1) Find yourself a > mentor, 2) Get a commit bit, 3) Update worthy patchsets to -current > sources, 4) Have them reviewed, 5) Commit them. > > If you aren't interested in doing this, you are the sole person to be > blamed for them not being integrated into FreeBSD. And I'm getting sick of being dragged down into details in what should be a meta-discussion, thus effectively glossing over the major point in order to pick on one or two "objectionable" paragraphs out of an entire posting. Right now we have a situation where people are complaining about large scale changes being "dangerous", and at the same time complaining that they are taking place in the P4 repository instead of the CVS repository. One of these points of view has to give, so a uniform policy exists that people can comply with before they burn months of work for naught, or are unwilling to give up all that work -- just as the "386BSD 0.5 interim release" group was unwilling to give up their work, and "forked" 386BSD to create the first FreeBSD. Either it's OK to make large scale changes in the CVS repository, or it's OK to make them in a seperate (only currently P4) reposity, and integrate them later. Topologically, as far as the project is concerned, there's no difference between making changes locally or making them in the P4 tree. The alternative is to simply disallow the changes, which I'm sure would please some people. I prefer the dichotomy be resolved, rather than glossed over. I think it's valuable to look at why this "immune response" is suppressing, among other things, my list of examples... which was far from comprehensive, and which are not *my* examples, in particular, merely because I raised them. As was noted elsewhere, there are now 57 P4 branches, most of them active, in which work is taking place outside the umbrella of "the one true HEAD" of the CVS repository. There's no possible way this situation could have arisen in the first place, had not people found themselves beating their heads against _some_ obstacle that migrating to P4 based developement removed, and which removal was worth the cost of being yelled at for using P4 (among other costs). It seems to me that what people are getting upset about is the fact that the people using P4 are "routing around the damage" and are thus able to collaborate effectively towards goals that others won't believe in until they have a working example thrown in their face, and would prefer to not have that. We have to ask ourselves: what damage is being routed around that could be worth paying the "popularity penalty", when people yell "Hey! That's *my* barrier you're routing around!". The differences in the P4 vs. CVS environment are many, but the main ones which seem, sociologically, to favor P4 are: o Multiple lines of developement o Reduced politics o Reduced/removed review barrier o Better small project collaboration vs. patches and email I should think that people would be interested in *why* the situation has arisen, and not merely interested in bitching about the fact that it exists. Frankly, though I think having only "one true HEAD branch", as imposed by the use of CVS, has hurt FreeBSD's progress enormously (by creating a GlobalCop model game), I have to say that the middle two are probably primary in the minds of the people now using P4. In fact, I'll say it straight our: IMO, it's the review barrier. Matt's commit bit was yanked a long time ago, right after he reached the point where he could spend 12+ hours a day hacking on FreeBSD, and the reviewer resources simply could not keep up with his output. He effectively flood attacked the review process. The reaction of yanking the bit, and the subsequent backlash "corrected" this: not by increasing the review rate, but by decreasing the rate at which new code is submitted, and decreasing the maximum size that can make it through review. The problem is not the barrier itself, it's the rate at which the barrier processes, and the maximum load it can handle. Now we have a P4 repository, and there are at present 57 special interests who are routing around that barrier's inability to handle load. Perhaps it's time to follow the lead of Linux, and break the review barrier into multiple barriers, with seperately controlled review processes. People involved in review would then have to pick what they cared about most, and *trust* the rest of the people to make the right decisions. The overall ability to handle load would go up, just like adding machines to a web farm increases capacity. Doing this has certain drawbacks, as Linux has discovered (USL had a similar situation with similar drawbacks), the foremost being that cross-domain changes were inordinately hard to push through (cv. Linux's recent issues with their VM system "forking" between the RedHat/Alan Cox version, and the "official"/Linus version). I would argue that such changes are only "inordinately hard" in comparison to other changes, and that "inordinately hard" is no worse than what's there now. Small changes will still pass individual barriers as easily as they pass the big one today -- easier, in fact, with less people standing in line to rubber stamp the changes. Hopefully, over time, these drawbacks can be overcome, or a better approach will come along (e.g. the barriers being drawn on the lines of well documented and rigidly defined interfaces, agreed upon between the various guards at the various gates). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 13:11: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by hub.freebsd.org (Postfix) with ESMTP id 0AB5637B402; Thu, 21 Feb 2002 13:10:58 -0800 (PST) Received: by energyhq.homeip.net (Postfix, from userid 1001) id 970023FC26; Thu, 21 Feb 2002 22:10:05 +0100 (CET) Date: Thu, 21 Feb 2002 22:10:05 +0100 From: Miguel Mendez To: David O'Brien Cc: current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance Message-ID: <20020221221005.A78243@energyhq.homeip.net> References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> <20020221111915.N65817@wantadilla.lemis.com> <20020221014909.A13952@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="3MwIy2ne0vdjdPXF" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020221014909.A13952@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Thu, Feb 21, 2002 at 01:49:09AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 21, 2002 at 01:49:09AM -0800, David O'Brien wrote: I'm not a commiter, but here comes my very humble opinion... > Users of Perforce are starting to force the rest of us to learn and use > it. That is totally not acceptable for the general FreeBSD population. This argument is pretty weak, learning perforce takes 15-20 minutes. > Those that chose to use it because they feel the tool is useful for > THEMSELVES are of course free to use it. HOWEVER, Perforce is NOT the CM > system of the FreeBSD project. Thus users of Perforce are expected to > share their bits via posting patches, not forcing everyone to pull them > out of the Perforce depot. Well, if all developers started using p4, things would be easier and work better in the long term. p4 is lightyears ahead of cvs, and, from what I've read in this thread, developers are not exactly happy with cvs now, as it's limitations have become evident. So, why not give it a try? Just my 0.02 Eur Cheers, --=20 Miguel Mendez - flynn@energyhq.homeip.net GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! --3MwIy2ne0vdjdPXF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8dWIsnLctrNyFFPERAjCTAJ9nPXRh8rDDpiM1oH03IVrE90uTFwCfVE4E n3is7f7nk26i3JEjKywBD2E= =2UCW -----END PGP SIGNATURE----- --3MwIy2ne0vdjdPXF-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 13:29:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id C952F37B405; Thu, 21 Feb 2002 13:29:04 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g1LLSnD47499; Thu, 21 Feb 2002 16:28:50 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Thu, 21 Feb 2002 16:28:49 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Dag-Erling Smorgrav Cc: Matthew Dillon , Greg Lehey , Jake Burkholder , "David O'Brien" , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 21 Feb 2002, Dag-Erling Smorgrav wrote: > Matthew Dillon writes: > > I'm not interested in using P4. I think it's a mistake. That is, I > > think it is being severely overused. [...] > > Frankly, although I use Perforce myself for PAM work, I agree with Matt > here. Most of what is going on in the Perforce should be happening on > branches in our main repo, if only CVS didn't suck so bad at branching. > > I would like to suggest that we consider transitioning our main repo to > Subversion. It's reasonably similar to cvs, and has all the features we > need that cvs lack: metadata versioning, atomic commits, cheap > branching... The problem is CVS. The solution is unclear. In the mean time, people are using Perforce because it's an effective tool to do the job. Believe me, I'd rather *not* be using two (or two and a half) different version control and software source management schemes, but the practical reality is that CVS cannot provide what I need to do what I do. Once there's a reliable free version control system that can be the One True System, I'll be extremely pleased to use it. Until then, well... :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 13:36:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 1FF4B37B400; Thu, 21 Feb 2002 13:36:42 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id D353A5341; Thu, 21 Feb 2002 22:36:39 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Miguel Mendez Cc: David O'Brien , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> <20020221111915.N65817@wantadilla.lemis.com> <20020221014909.A13952@dragon.nuxi.com> <20020221221005.A78243@energyhq.homeip.net> From: Dag-Erling Smorgrav Date: 21 Feb 2002 22:36:39 +0100 In-Reply-To: <20020221221005.A78243@energyhq.homeip.net> Message-ID: Lines: 13 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Miguel Mendez writes: > Well, if all developers started using p4, things would be easier and work > better in the long term. p4 is lightyears ahead of cvs, and, from what > I've read in this thread, developers are not exactly happy with cvs now, > as it's limitations have become evident. Perforce also has limitations. It does a number of things better than CVS, and a number of things worse. Its main problem, IMHO, is that it tries to do too much, at the expense of basic functionality. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 13:39:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from mharnois.mdharnois.net (customer-mpls-23.cpinternet.com [209.240.253.23]) by hub.freebsd.org (Postfix) with ESMTP id AACA737B423; Thu, 21 Feb 2002 13:39:15 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mharnois.mdharnois.net (Postfix) with ESMTP id DEFAA3CB1; Thu, 21 Feb 2002 15:39:08 -0600 (CST) Subject: Re: ports/34908: libpng port makes bad dynamic library on -CURRENT From: "Michael D. Harnois" To: Terry Lambert Cc: obrien@FreeBSD.ORG, Stijn Hoop , "Alexander N. Kabaev" , Bjoern Fischer , current@FreeBSD.ORG, "freebsd-gnats-submit@FreeBSD. " Org , vova@sw.ru In-Reply-To: <3C754AAA.9117A19@mindspring.com> References: <3C6D49E0.3000506@gte.com> <20020221000531.A57633@pcwin002.win.tue.nl> <20020221020341.C13952@dragon.nuxi.com> <1014298402.526.33.camel@mharnois.mdharnois.net> <3C754AAA.9117A19@mindspring.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 21 Feb 2002 15:39:08 -0600 Message-Id: <1014327548.19351.0.camel@mharnois.mdharnois.net> Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2002-02-21 at 13:29, Terry Lambert wrote: > "Michael D. Harnois" wrote: > > On Thu, 2002-02-21 at 04:03, David O'Brien wrote: > > > On Thu, Feb 21, 2002 at 12:05:31AM +0100, Stijn Hoop wrote: > > > > > > > > Maybe this can now be committed? > > > > > > NOT until I have sufficient feedback from the FSF Binutils developers. > > > > OK, I'm confused. binutils has been broken for three weeks. We have a > > patch that we know fixes, at the very least, one of the known problems. > > However, it can't be committed without feedback from the developers. > > > > So having binutils broken indefinitely is better than applying a patch > > that *might* have to be backed out or altered later? > > I believe the intent is to ensure that the patches make it > back into the FSF distributed code, so that in the future, > there is less maintenance required for FreeBSD platforms. This is all wonderful. But then it seems to me that the entire new binutils should have been backed out until it worked. Just like XFree-4.2.0 was backed out. -- Michael D. Harnois bilocational bivocational Pastor, Redeemer Lutheran Church Washburn, Iowa 1L, UST School of Law Minneapolis, Minnesota EDUCATION, n. That which discloses to the wise and disguises from the foolish their lack of understanding. -- Ambrose Bierce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 13:46:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 00E1A37B419; Thu, 21 Feb 2002 13:46:19 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g1LLjgB37177; Thu, 21 Feb 2002 13:45:42 -0800 (PST) (envelope-from obrien) Date: Thu, 21 Feb 2002 13:45:42 -0800 From: "David O'Brien" To: "Michael D. Harnois" Cc: Terry Lambert , Stijn Hoop , "Alexander N. Kabaev" , Bjoern Fischer , current@FreeBSD.ORG, "freebsd-gnats-submit@FreeBSD. Org" , vova@sw.ru Subject: Re: ports/34908: libpng port makes bad dynamic library on -CURRENT Message-ID: <20020221134542.B23386@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <3C6D49E0.3000506@gte.com> <20020221000531.A57633@pcwin002.win.tue.nl> <20020221020341.C13952@dragon.nuxi.com> <1014298402.526.33.camel@mharnois.mdharnois.net> <3C754AAA.9117A19@mindspring.com> <1014327548.19351.0.camel@mharnois.mdharnois.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1014327548.19351.0.camel@mharnois.mdharnois.net>; from mharnois@cpinternet.com on Thu, Feb 21, 2002 at 03:39:08PM -0600 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 21, 2002 at 03:39:08PM -0600, Michael D. Harnois wrote: > On Thu, 2002-02-21 at 13:29, Terry Lambert wrote: > > "Michael D. Harnois" wrote: > > > On Thu, 2002-02-21 at 04:03, David O'Brien wrote: > > > > On Thu, Feb 21, 2002 at 12:05:31AM +0100, Stijn Hoop wrote: > > > > > > > > > > Maybe this can now be committed? > > > > > > > > NOT until I have sufficient feedback from the FSF Binutils developers. > > > > > > OK, I'm confused. binutils has been broken for three weeks. We have a > > > patch that we know fixes, at the very least, one of the known problems. > > > However, it can't be committed without feedback from the developers. > > > > > > So having binutils broken indefinitely is better than applying a patch > > > that *might* have to be backed out or altered later? > > > > I believe the intent is to ensure that the patches make it > > back into the FSF distributed code, so that in the future, > > there is less maintenance required for FreeBSD platforms. > > This is all wonderful. > > But then it seems to me that the entire new binutils should have been > backed out until it worked. Just like XFree-4.2.0 was backed out. It works in general for 'make world' and is suffient for FreeBSD developent -- the purpose of 5-CURRENT. It is also allowing us to find bugs that would otherwise go unfixed in Binutils 2.12.0 release. Or would you perfer we stick to 2.11.x forever -- BTW that would not give us support for IA-64 or x86-64. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 13:57:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 8811037B404; Thu, 21 Feb 2002 13:57:27 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g1LLvFh37381; Thu, 21 Feb 2002 13:57:15 -0800 (PST) (envelope-from obrien) Date: Thu, 21 Feb 2002 13:57:15 -0800 From: "David O'Brien" To: "Michael D. Harnois" Cc: Stijn Hoop , "Alexander N. Kabaev" , Bjoern Fischer , current@FreeBSD.ORG, "freebsd-gnats-submit@FreeBSD. Org" , vova@sw.ru Subject: Re: ports/34908: libpng port makes bad dynamic library on -CURRENT Message-ID: <20020221135715.F23386@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <3C6D49E0.3000506@gte.com> <20020221000531.A57633@pcwin002.win.tue.nl> <20020221020341.C13952@dragon.nuxi.com> <1014298402.526.33.camel@mharnois.mdharnois.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1014298402.526.33.camel@mharnois.mdharnois.net>; from mharnois@cpinternet.com on Thu, Feb 21, 2002 at 07:33:22AM -0600 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 21, 2002 at 07:33:22AM -0600, Michael D. Harnois wrote: > On Thu, 2002-02-21 at 04:03, David O'Brien wrote: > > > On Thu, Feb 21, 2002 at 12:05:31AM +0100, Stijn Hoop wrote: > > > > > > Maybe this can now be committed? > > > > NOT until I have sufficient feedback from the FSF Binutils developers. > > OK, I'm confused. binutils has been broken for three weeks. We have a > patch that we know fixes, at the very least, one of the known problems. I have also heard it caused a new problem. > However, it can't be committed without feedback from the developers. Yes, unless you can fully explain the problem and why the patch is the correct fix. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 13:58:58 2002 Delivered-To: freebsd-current@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id DE55A37B404; Thu, 21 Feb 2002 13:58:53 -0800 (PST) Received: from pool0500.cvx21-bradley.dialup.earthlink.net ([209.179.193.245] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16e1Ep-00056I-00; Thu, 21 Feb 2002 13:58:52 -0800 Message-ID: <3C756D8F.646CD494@mindspring.com> Date: Thu, 21 Feb 2002 13:58:39 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Michael D. Harnois" Cc: obrien@FreeBSD.ORG, Stijn Hoop , "Alexander N. Kabaev" , Bjoern Fischer , current@FreeBSD.ORG, "freebsd-gnats-submit@FreeBSD. Org" , vova@sw.ru Subject: Re: ports/34908: libpng port makes bad dynamic library on -CURRENT References: <3C6D49E0.3000506@gte.com> <20020221000531.A57633@pcwin002.win.tue.nl> <20020221020341.C13952@dragon.nuxi.com> <1014298402.526.33.camel@mharnois.mdharnois.net> <3C754AAA.9117A19@mindspring.com> <1014327548.19351.0.camel@mharnois.mdharnois.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Michael D. Harnois" wrote: > > I believe the intent is to ensure that the patches make it > > back into the FSF distributed code, so that in the future, > > there is less maintenance required for FreeBSD platforms. > > This is all wonderful. > > But then it seems to me that the entire new binutils should have been > backed out until it worked. Just like XFree-4.2.0 was backed out. Feel free to tilt at your windmills, all you want; I'm personally busy with other windmills; I was just pointing out what I thought was the rationale. FWIW: it *does* work on Intel, it's just Alpha that's in the dumps. The currently accepted fix is to use the older code until all the problems are out of there. -- Tery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 13:59:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id D777A37B41B; Thu, 21 Feb 2002 13:59:24 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g1LLxAk37395; Thu, 21 Feb 2002 13:59:10 -0800 (PST) (envelope-from obrien) Date: Thu, 21 Feb 2002 13:59:10 -0800 From: "David O'Brien" To: Terry Lambert Cc: "Michael D. Harnois" , Stijn Hoop , "Alexander N. Kabaev" , Bjoern Fischer , current@FreeBSD.ORG, "freebsd-gnats-submit@FreeBSD. Org" , vova@sw.ru Subject: Re: ports/34908: libpng port makes bad dynamic library on -CURRENT Message-ID: <20020221135910.G23386@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <3C6D49E0.3000506@gte.com> <20020221000531.A57633@pcwin002.win.tue.nl> <20020221020341.C13952@dragon.nuxi.com> <1014298402.526.33.camel@mharnois.mdharnois.net> <3C754AAA.9117A19@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C754AAA.9117A19@mindspring.com>; from tlambert2@mindspring.com on Thu, Feb 21, 2002 at 11:29:46AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 21, 2002 at 11:29:46AM -0800, Terry Lambert wrote: > Actually, there was a discussion at BSDCon as to whether or > not to drop the a.out support in order to decrease the patch > size necessary to make the FSF distributed code do what FreeBSD That is true for GCC. For contrib/binutils, the code only supports FreeBSD/ELF. The old a.out as & ld are elsewhere in the tree -- and have not been updated for years. > needed it to do (personally, I would prefer that the a.out > code generation be integrated back into the FSF code base but > this is unlikely for FSF political reasons with regard to the I have tried many times... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 14: 3: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id E5A4737B400; Thu, 21 Feb 2002 14:03:01 -0800 (PST) Received: from pool0500.cvx21-bradley.dialup.earthlink.net ([209.179.193.245] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16e1Ir-0003Ph-00; Thu, 21 Feb 2002 14:03:01 -0800 Message-ID: <3C756E88.669ED0EE@mindspring.com> Date: Thu, 21 Feb 2002 14:02:48 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: obrien@FreeBSD.ORG Cc: "Michael D. Harnois" , Stijn Hoop , "Alexander N. Kabaev" , Bjoern Fischer , current@FreeBSD.ORG, "freebsd-gnats-submit@FreeBSD. Org" , vova@sw.ru Subject: Re: ports/34908: libpng port makes bad dynamic library on -CURRENT References: <3C6D49E0.3000506@gte.com> <20020221000531.A57633@pcwin002.win.tue.nl> <20020221020341.C13952@dragon.nuxi.com> <1014298402.526.33.camel@mharnois.mdharnois.net> <3C754AAA.9117A19@mindspring.com> <1014327548.19351.0.camel@mharnois.mdharnois.net> <20020221134542.B23386@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David O'Brien wrote: > It works in general for 'make world' and is suffient for FreeBSD > developent -- the purpose of 5-CURRENT. It is also allowing us to find > bugs that would otherwise go unfixed in Binutils 2.12.0 release. Or > would you perfer we stick to 2.11.x forever -- BTW that would not give us > support for IA-64 or x86-64. Surprisingly, this did not occur to me until the Developer's Summit report on other architectures, so it's probably not obvious to most people. For the record, then: binutils 2.12.0 is *required* by IA64, and so it's required going forward. Personally, I've been quiet since my initial Alpha breakage complaints, except to try to help track things down once in a while, since I had since realized this was an issue. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 14:22:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from jochem.dyndns.org (cc40670-a.groni1.gr.nl.home.com [217.120.131.23]) by hub.freebsd.org (Postfix) with ESMTP id BE53237B402 for ; Thu, 21 Feb 2002 14:22:24 -0800 (PST) Received: (from jochem@localhost) by jochem.dyndns.org (8.11.6/8.11.6) id g1LMMI611409 for current@FreeBSD.ORG; Thu, 21 Feb 2002 23:22:18 +0100 (CET) (envelope-from jochem) Date: Thu, 21 Feb 2002 23:22:18 +0100 From: Jochem Kossen To: current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance Message-ID: <20020221222218.GA11359@jochem.dyndns.org> References: <200202181912.g1IJCGK32122@apollo.backplane.com> <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> <20020221111915.N65817@wantadilla.lemis.com> <20020221014909.A13952@dragon.nuxi.com> <20020221221005.A78243@energyhq.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 21, 2002 at 10:36:39PM +0100, Dag-Erling Smorgrav wrote: > Miguel Mendez writes: > > Well, if all developers started using p4, things would be easier and work > > better in the long term. p4 is lightyears ahead of cvs, and, from what > > I've read in this thread, developers are not exactly happy with cvs now, > > as it's limitations have become evident. > > Perforce also has limitations. It does a number of things better than > CVS, and a number of things worse. Its main problem, IMHO, is that it > tries to do too much, at the expense of basic functionality. As it seems people are forming a list of cvs alternatives, anyone ever took a look at arch? http://regexps.com/#arch A buddy of mine just mentioned it, and it seemed to fit in this discussion, i don't know it myself though. It's covered under the GPL. Jochem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 14:36: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from [209.49.190.34] (fireout.mbakercorp.com [209.49.190.34]) by hub.freebsd.org (Postfix) with SMTP id 0A1F937B405 for ; Thu, 21 Feb 2002 14:35:58 -0800 (PST) Received: from no.name.available by [209.49.190.34] via smtpd (for hub.FreeBSD.org [216.136.204.18]) with SMTP; 21 Feb 2002 22:35:58 UT Received: from mbakercorp.com (unverified) by mailsweeper.mbakercorp.com (Content Technologies SMTPRS 4.2.10) with ESMTP id for ; Thu, 21 Feb 2002 17:36:30 -0500 Received: from gatedom-MTA by mbakercorp.com with Novell_GroupWise; Thu, 21 Feb 2002 17:34:37 -0500 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.1 Date: Thu, 21 Feb 2002 17:34:25 -0500 From: "Joseph Wright" To: Subject: Building php mod and cgi Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is their a way to build the port mod_php4 as the module version for apache and the cgi for command line options. I currently have mod_php+apache13+mysql+gd working perfect but I now have the need to run php from the command prompt with mysql & gd. What is the best way to go about this. thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 15: 0:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from mta5.rcsntx.swbell.net (mta5.rcsntx.swbell.net [151.164.30.29]) by hub.freebsd.org (Postfix) with ESMTP id 19DDB37B416 for ; Thu, 21 Feb 2002 15:00:39 -0800 (PST) Received: from Eagle ([64.216.142.92]) by mta5.rcsntx.swbell.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GRW00K1VNX2YO@mta5.rcsntx.swbell.net> for current@FreeBSD.ORG; Thu, 21 Feb 2002 17:00:38 -0600 (CST) Date: Thu, 21 Feb 2002 17:00:37 -0600 From: robert garrett Subject: RE: Patch to improve mutex collision performance In-reply-to: <20020221222218.GA11359@jochem.dyndns.org> To: 'Jochem Kossen' , current@FreeBSD.ORG Message-id: <004401c1bb2b$936c7130$7228fea9@Eagle> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Mailer: Microsoft Outlook, Build 10.0.2616 Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Could someone tell me where documentation concerning the use of perforce and or, how to gain access to is located? Up until very recently I was not aware of it's existence. This would make it very difficult for someone new to the Project to contribute. It seems to my line of thinking that the existence of a repository That is undocumented, that is used for major development proccess's Breaks our development model. Further enhancing the "Elite" attitude that is so often proscribed To BSD* developers. Robert Garrett -----Original Message----- From: owner-freebsd-current@FreeBSD.ORG [mailto:owner-freebsd-current@FreeBSD.ORG] On Behalf Of Jochem Kossen Sent: Thursday, February 21, 2002 4:22 PM To: current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance On Thu, Feb 21, 2002 at 10:36:39PM +0100, Dag-Erling Smorgrav wrote: > Miguel Mendez writes: > > Well, if all developers started using p4, things would be easier and work > > better in the long term. p4 is lightyears ahead of cvs, and, from what > > I've read in this thread, developers are not exactly happy with cvs now, > > as it's limitations have become evident. > > Perforce also has limitations. It does a number of things better than > CVS, and a number of things worse. Its main problem, IMHO, is that it > tries to do too much, at the expense of basic functionality. As it seems people are forming a list of cvs alternatives, anyone ever took a look at arch? http://regexps.com/#arch A buddy of mine just mentioned it, and it seemed to fit in this discussion, i don't know it myself though. It's covered under the GPL. Jochem 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 Feb 21 15:14:57 2002 Delivered-To: freebsd-current@freebsd.org Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 8F4CE37B402; Thu, 21 Feb 2002 15:14:51 -0800 (PST) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g1LNEdZ54174; Thu, 21 Feb 2002 15:14:39 -0800 (PST) (envelope-from rizzo) Date: Thu, 21 Feb 2002 15:14:39 -0800 From: Luigi Rizzo To: Alfred Perlstein Cc: Bruce Evans , "M. Warner Losh" , current@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Proposed patch for "/bin/sh: Argument list too long" when compiling LINT ... Message-ID: <20020221151439.D53952@iguana.icir.org> References: <20020218.174959.96666779.imp@village.org> <20020219193515.Y1320-100000@gamplex.bde.org> <20020219004144.A25474@iguana.icir.org> <20020219085306.GL12136@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020219085306.GL12136@elvis.mu.org> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG So, in this thread a few days ago i reported that the list of arguments passed to mkdep can become quite large and exceed kern.argmax, especially if your sources are not in the default place and you are compiling a file with lots of options such as LINT. The place to fix (for -current) is sys/conf/kern.post.mk, and as Alfred suggested, a fix involves using xargs (mkdep is already invoked with -a). Unfortunately it is not entirely trivial because the variable containing the argument list is a Make variable, and any attempt to expand it in a command will result in the "Argument list too long" error. The best I could come up with is the following (modulo cut&paste conversion of tabs in spaces), i.e. use make's .for to copy the list of files into a file that we can then pass to xargs. Any better ideas ? cheers luigi Index: kern.post.mk =================================================================== RCS file: /home/ncvs/src/sys/conf/kern.post.mk,v retrieving revision 1.4 diff -u -r1.4 kern.post.mk --- kern.post.mk 2001/11/11 06:16:53 1.4 +++ kern.post.mk 2002/02/21 04:49:26 @@ -89,10 +89,28 @@ ${SYSTEM_SFILES} ${MFILES:T:S/.m$/.h/} if [ -f .olddep ]; then mv .olddep .depend; fi rm -f .newdep - env MKDEP_CPP="${CC} -E" CC="${CC}" \ - mkdep -a -f .newdep ${CFLAGS} ${CFILES} ${SYSTEM_CFILES} ${GEN_CFILE S} - env MKDEP_CPP="${CC} -E" \ - mkdep -a -f .newdep ${ASM_CFLAGS} ${SFILES} ${SYSTEM_SFILES} + # + # The argument list can be very long, and the only way we have to + # split it is within make because anything else will cause + # an exec error if the list is too long! + rm -f .args +.for I in ${CFILES} ${SYSTEM_CFILES} ${GEN_CFILES} + @echo -n "$I " >> .args +.endfor + echo "" >> .args + echo "args len is " ; wc .args + # argument list... + cat .args | xargs env MKDEP_CPP="${CC} -E" CC="${CC}" \ + mkdep -a -f .newdep ${CFLAGS} + rm -f .args +.for I in ${SFILES} ${SYSTEM_SFILES} + @echo -n "$I " >> .args +.endfor + echo "" >> .args + echo "args len is " ; wc .args + cat .args | xargs env MKDEP_CPP="${CC} -E" \ + mkdep -a -f .newdep ${ASM_CFLAGS} + rm -f .args rm -f .depend mv .newdep .depend To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 15:40: 6 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 60D4237B404 for ; Thu, 21 Feb 2002 15:40:03 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 2C0885341; Fri, 22 Feb 2002 00:40:00 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: robert garrett Cc: 'Jochem Kossen' , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance References: <004401c1bb2b$936c7130$7228fea9@Eagle> From: Dag-Erling Smorgrav Date: 22 Feb 2002 00:39:59 +0100 In-Reply-To: <004401c1bb2b$936c7130$7228fea9@Eagle> Message-ID: Lines: 9 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG robert garrett writes: > Further enhancing the "Elite" attitude that is so often proscribed > To BSD* developers. I hope you meant "ascribed" :) DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 15:41:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id D05DB37B404; Thu, 21 Feb 2002 15:41:46 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 7B9E2AE2AC; Thu, 21 Feb 2002 15:41:46 -0800 (PST) Date: Thu, 21 Feb 2002 15:41:46 -0800 From: Alfred Perlstein To: Luigi Rizzo Cc: Bruce Evans , "M. Warner Losh" , current@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Proposed patch for "/bin/sh: Argument list too long" when compiling LINT ... Message-ID: <20020221234146.GH12136@elvis.mu.org> References: <20020218.174959.96666779.imp@village.org> <20020219193515.Y1320-100000@gamplex.bde.org> <20020219004144.A25474@iguana.icir.org> <20020219085306.GL12136@elvis.mu.org> <20020221151439.D53952@iguana.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020221151439.D53952@iguana.icir.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Luigi Rizzo [020221 15:14] wrote: > So, in this thread a few days ago i reported that the > list of arguments passed to mkdep can become quite large > and exceed kern.argmax, especially if your sources are not in the > default place and you are compiling a file with lots of options > such as LINT. > > The place to fix (for -current) is sys/conf/kern.post.mk, and > as Alfred suggested, a fix involves using xargs (mkdep is already > invoked with -a). Unfortunately it is not entirely trivial because > the variable containing the argument list is a Make variable, and > any attempt to expand it in a command will result in the "Argument > list too long" error. > > The best I could come up with is the following (modulo cut&paste > conversion of tabs in spaces), i.e. use make's .for to > copy the list of files into a file that we can then pass > to xargs. > > Any better ideas ? Yes. :) $(MAKE) -V CFILES -V SYSTEM_CFILES -V |\ xargs env MKDEP_CPP="${CC} -E" CC="${CC}" mkdep -a -f .newdep ${CFLAGS} -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 15:42:14 2002 Delivered-To: freebsd-current@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 7DB6B37B404 for ; Thu, 21 Feb 2002 15:42:11 -0800 (PST) Received: from pool0385.cvx22-bradley.dialup.earthlink.net ([209.179.199.130] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16e2qj-0005pr-00; Thu, 21 Feb 2002 15:42:05 -0800 Message-ID: <3C7585C2.CD608466@mindspring.com> Date: Thu, 21 Feb 2002 15:41:54 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: robert garrett Cc: 'Jochem Kossen' , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance References: <004401c1bb2b$936c7130$7228fea9@Eagle> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG robert garrett wrote: > > Could someone tell me where documentation concerning the > use of perforce and or, how to gain access to is located? http://people.freebsd.org/~peter/p4cookbook.txt > Up until very recently I was not aware of it's existence. > This would make it very difficult for someone new to the > Project to contribute. To contribute to a seperate branch other than the main line branch, yes. You'd have to join the mailing list for the side project in question (e.g. SMP), and learn about it that way). Effectively, all it provides is a place for people to collaborate, and to gather in force in favor of a commit to the CVS repository. You could get the same effect from a small group working with a shared CVS repository, and having their code show up full blown, but this way, it at least happens under the umbrella, and therefore theoretically the oversight, of the project. It's also much easier to keep up to date, since CVSup pretty much hates local branches with merges to HEAD. > It seems to my line of thinking that the existence of a repository > That is undocumented, that is used for major development proccess's > Breaks our development model. > > Further enhancing the "Elite" attitude that is so often proscribed > To BSD* developers. Actually, the P4 repository has a lower barrier to entry than the CVS repository -- which is one of the main reasons people choose to use it. It overcomes an inherent weakness in the developement model. The real issues that need to be addressed are the underlying issues that cause people to move to P4 in the first place. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 15:47:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id D8F4837B402; Thu, 21 Feb 2002 15:47:47 -0800 (PST) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g1LNlhK54477; Thu, 21 Feb 2002 15:47:43 -0800 (PST) (envelope-from rizzo) Date: Thu, 21 Feb 2002 15:47:43 -0800 From: Luigi Rizzo To: Alfred Perlstein Cc: Bruce Evans , "M. Warner Losh" , current@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Proposed patch for "/bin/sh: Argument list too long" when compiling LINT ... Message-ID: <20020221154743.B54262@iguana.icir.org> References: <20020218.174959.96666779.imp@village.org> <20020219193515.Y1320-100000@gamplex.bde.org> <20020219004144.A25474@iguana.icir.org> <20020219085306.GL12136@elvis.mu.org> <20020221151439.D53952@iguana.icir.org> <20020221234146.GH12136@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020221234146.GH12136@elvis.mu.org> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 21, 2002 at 03:41:46PM -0800, Alfred Perlstein wrote: > * Luigi Rizzo [020221 15:14] wrote: > > So, in this thread a few days ago i reported that the > > list of arguments passed to mkdep can become quite large > > and exceed kern.argmax, especially if your sources are not in the ... > > Any better ideas ? > > Yes. :) > > $(MAKE) -V CFILES -V SYSTEM_CFILES -V |\ > xargs env MKDEP_CPP="${CC} -E" CC="${CC}" mkdep -a -f .newdep ${CFLAGS} Nice one, didn't know about the -V option. Would you like to commit this or should I do it ? Also, do you know where to look for the same problem in RELENG_4 ? cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 15:50:26 2002 Delivered-To: freebsd-current@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 8A9C437B405 for ; Thu, 21 Feb 2002 15:50:22 -0800 (PST) Received: from pool0385.cvx22-bradley.dialup.earthlink.net ([209.179.199.130] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16e2xu-0000cZ-00; Thu, 21 Feb 2002 15:49:30 -0800 Message-ID: <3C758780.67C24641@mindspring.com> Date: Thu, 21 Feb 2002 15:49:20 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: robert garrett , 'Jochem Kossen' , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance References: <004401c1bb2b$936c7130$7228fea9@Eagle> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > robert garrett writes: > > Further enhancing the "Elite" attitude that is so often proscribed > > To BSD* developers. > > I hope you meant "ascribed" :) I think he means FreeBSD developers are not allowed to have that attitude. 8-) 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 16: 0:58 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 9E8C737B404; Thu, 21 Feb 2002 16:00:54 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id DFB355343; Fri, 22 Feb 2002 01:00:52 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Luigi Rizzo Cc: Alfred Perlstein , Bruce Evans , "M. Warner Losh" , current@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Proposed patch for "/bin/sh: Argument list too long" when compiling LINT ... References: <20020218.174959.96666779.imp@village.org> <20020219193515.Y1320-100000@gamplex.bde.org> <20020219004144.A25474@iguana.icir.org> <20020219085306.GL12136@elvis.mu.org> <20020221151439.D53952@iguana.icir.org> From: Dag-Erling Smorgrav Date: 22 Feb 2002 01:00:52 +0100 In-Reply-To: <20020221151439.D53952@iguana.icir.org> Message-ID: Lines: 35 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Luigi Rizzo writes: > Any better ideas ? You could just chicken out and do Index: kern.post.mk =================================================================== RCS file: /home/ncvs/src/sys/conf/kern.post.mk,v retrieving revision 1.7 diff -u -r1.7 kern.post.mk --- kern.post.mk 10 Jan 2002 03:52:00 -0000 1.7 +++ kern.post.mk 21 Feb 2002 23:55:02 -0000 @@ -93,10 +93,15 @@ ${SYSTEM_SFILES} ${MFILES:T:S/.m$/.h/} if [ -f .olddep ]; then mv .olddep .depend; fi rm -f .newdep +# Do this one file at a time to avoid overly long command lines +.for file in ${CFILES} ${SYSTEM_CFILES} ${GEN_CFILES} env MKDEP_CPP="${CC} -E" CC="${CC}" \ - mkdep -a -f .newdep ${CFLAGS} ${CFILES} ${SYSTEM_CFILES} ${GEN_CFILES} + mkdep -a -f .newdep ${CFLAGS} ${file} +.endfor +.for file in ${SFILES} ${SYSTEM_SFILES} env MKDEP_CPP="${CC} -E" \ - mkdep -a -f .newdep ${ASM_CFLAGS} ${SFILES} ${SYSTEM_SFILES} + mkdep -a -f .newdep ${ASM_CFLAGS} ${file} +.endfor rm -f .depend mv .newdep .depend Not particularly efficient, but shorter, simpler and clearer. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 16: 4: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from espresso.q9media.com (espresso.q9media.com [216.254.138.122]) by hub.freebsd.org (Postfix) with ESMTP id 4C0B037B405; Thu, 21 Feb 2002 16:03:56 -0800 (PST) Received: (from mike@localhost) by espresso.q9media.com (8.11.6/8.11.6) id g1LNxZY11890; Thu, 21 Feb 2002 18:59:35 -0500 (EST) (envelope-from mike) Date: Thu, 21 Feb 2002 18:59:35 -0500 From: Mike Barcroft To: Terry Lambert Cc: Matthew Dillon , Greg Lehey , Jake Burkholder , "David O'Brien" , current@FreeBSD.ORG Subject: Re: "Forking" FreeBSD: CVS vs. P4 Message-ID: <20020221185935.C68344@espresso.q9media.com> References: <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> <20020221111915.N65817@wantadilla.lemis.com> <200202210146.g1L1kqg91511@apollo.backplane.com> <3C746FC1.897E759C@mindspring.com> <200202210435.g1L4Z0H92642@apollo.backplane.com> <3C74B9EA.9692E27E@mindspring.com> <20020221144620.B68344@espresso.q9media.com> <3C755D6C.BE8F1776@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C755D6C.BE8F1776@mindspring.com>; from tlambert2@mindspring.com on Thu, Feb 21, 2002 at 12:49:48PM -0800 Organization: The FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert writes: > Mike Barcroft wrote: > > I'm getting sick of reading this. Terry, if you want this code > > integrated into FreeBSD, here's what you do: 1) Find yourself a > > mentor, 2) Get a commit bit, 3) Update worthy patchsets to -current > > sources, 4) Have them reviewed, 5) Commit them. > > > > If you aren't interested in doing this, you are the sole person to be > > blamed for them not being integrated into FreeBSD. > > And I'm getting sick of being dragged down into details in what > should be a meta-discussion, thus effectively glossing over the > major point in order to pick on one or two "objectionable" > paragraphs out of an entire posting. [Discussion related to the root of the thread, rather than my message, removed.] I see you are not interested in doing this. -CURRENT READERS TAKE NOTE: No longer can Terry blame CVS, P4, Gnats, our two seperate branches of development, FreeBSD developers, or the color of the sky; Terry can be attributed to be the sole reason why these outside projects have never been integrated into FreeBSD. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 16:11:14 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 6B35E37B402; Thu, 21 Feb 2002 16:11:10 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 395C3AE2DD; Thu, 21 Feb 2002 16:11:10 -0800 (PST) Date: Thu, 21 Feb 2002 16:11:10 -0800 From: Alfred Perlstein To: Luigi Rizzo Cc: Bruce Evans , "M. Warner Losh" , current@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Proposed patch for "/bin/sh: Argument list too long" when compiling LINT ... Message-ID: <20020222001110.GI12136@elvis.mu.org> References: <20020218.174959.96666779.imp@village.org> <20020219193515.Y1320-100000@gamplex.bde.org> <20020219004144.A25474@iguana.icir.org> <20020219085306.GL12136@elvis.mu.org> <20020221151439.D53952@iguana.icir.org> <20020221234146.GH12136@elvis.mu.org> <20020221154743.B54262@iguana.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020221154743.B54262@iguana.icir.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Luigi Rizzo [020221 15:47] wrote: > On Thu, Feb 21, 2002 at 03:41:46PM -0800, Alfred Perlstein wrote: > > * Luigi Rizzo [020221 15:14] wrote: > > > So, in this thread a few days ago i reported that the > > > list of arguments passed to mkdep can become quite large > > > and exceed kern.argmax, especially if your sources are not in the > ... > > > Any better ideas ? > > > > Yes. :) > > > > $(MAKE) -V CFILES -V SYSTEM_CFILES -V |\ > > xargs env MKDEP_CPP="${CC} -E" CC="${CC}" mkdep -a -f .newdep ${CFLAGS} > > Nice one, didn't know about the -V option. > > Would you like to commit this or should I do it ? Go for it. > Also, do you know where to look for the same problem in RELENG_4 ? Not offhand, sorry. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 16:16:57 2002 Delivered-To: freebsd-current@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 255B737B402; Thu, 21 Feb 2002 16:16:54 -0800 (PST) Received: from pool0385.cvx22-bradley.dialup.earthlink.net ([209.179.199.130] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16e3OO-00043C-00; Thu, 21 Feb 2002 16:16:53 -0800 Message-ID: <3C758DEA.1DE260BE@mindspring.com> Date: Thu, 21 Feb 2002 16:16:42 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Barcroft Cc: Matthew Dillon , Greg Lehey , Jake Burkholder , David O'Brien , current@FreeBSD.ORG Subject: Re: "Forking" FreeBSD: CVS vs. P4 References: <20020218114326.A98974@dragon.nuxi.com> <200202181951.g1IJpip33604@apollo.backplane.com> <20020218153807.E96115@locore.ca> <20020221111915.N65817@wantadilla.lemis.com> <200202210146.g1L1kqg91511@apollo.backplane.com> <3C746FC1.897E759C@mindspring.com> <200202210435.g1L4Z0H92642@apollo.backplane.com> <3C74B9EA.9692E27E@mindspring.com> <20020221144620.B68344@espresso.q9media.com> <3C755D6C.BE8F1776@mindspring.com> <20020221185935.C68344@espresso.q9media.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Barcroft wrote: > [Discussion related to the root of the thread, rather than my message, > removed.] > > I see you are not interested in doing this. > > -CURRENT READERS TAKE NOTE: > No longer can Terry blame CVS, P4, Gnats, our two seperate branches of > development, FreeBSD developers, or the color of the sky; Terry can be > attributed to be the sole reason why these outside projects have never > been integrated into FreeBSD. Apparently, you weren't paying attention to the "too dangerous" part of the discussion, which would, by definition, keep my examples from getting committed. FWIW: I specifically chose my examples so that 3 out of the 4 of them were complex enough that they would hit the review wall. Also FWIW: Just because I came up with the examples does not mean they are my code. They are code that was current at the time the project was made aware of the patches, and the only thing missing from your 5 step process was the review and commit. Check the list archives for them, if you don't believe me. I'm amazed that I now suddenly own the integration of all forward looking projects into FreeBSD where the only steps necessary for their integration are "4) review, 5) commit". If that's the case, I hereby approve, after having reviewed it, John Baldwin's proc-locking patch. As my "mentor", I'm sure you'll commit it, now, right? If anyone else wants their code that's in P4, and not CVS, reviewed and committed to CVS, speak up, because Mike Barcroft is here to help you. PS: Grow up: you can't dismiss all my examples by waving an "it's Terry's problem" wand at them. There's a real process problem here that needs addressing. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 16:17: 8 2002 Delivered-To: freebsd-current@freebsd.org Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 38E8237B404; Thu, 21 Feb 2002 16:16:59 -0800 (PST) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g1M0Gp554682; Thu, 21 Feb 2002 16:16:51 -0800 (PST) (envelope-from rizzo) Date: Thu, 21 Feb 2002 16:16:51 -0800 From: Luigi Rizzo To: Dag-Erling Smorgrav Cc: Alfred Perlstein , Bruce Evans , "M. Warner Losh" , current@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Proposed patch for "/bin/sh: Argument list too long" when compiling LINT ... Message-ID: <20020221161651.E54262@iguana.icir.org> References: <20020218.174959.96666779.imp@village.org> <20020219193515.Y1320-100000@gamplex.bde.org> <20020219004144.A25474@iguana.icir.org> <20020219085306.GL12136@elvis.mu.org> <20020221151439.D53952@iguana.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Not particularly efficient... oh yes... i think Al's solution (make -V ... | xargs .. ) wins both in terms of simplicity and efficiency cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 16:19:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id CB6F737B400; Thu, 21 Feb 2002 16:19:47 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 0FEEC5343; Fri, 22 Feb 2002 01:19:46 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Luigi Rizzo Cc: Alfred Perlstein , Bruce Evans , "M. Warner Losh" , current@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Proposed patch for "/bin/sh: Argument list too long" when compiling LINT ... References: <20020218.174959.96666779.imp@village.org> <20020219193515.Y1320-100000@gamplex.bde.org> <20020219004144.A25474@iguana.icir.org> <20020219085306.GL12136@elvis.mu.org> <20020221151439.D53952@iguana.icir.org> <20020221161651.E54262@iguana.icir.org> From: Dag-Erling Smorgrav Date: 22 Feb 2002 01:19:45 +0100 In-Reply-To: <20020221161651.E54262@iguana.icir.org> Message-ID: Lines: 9 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Luigi Rizzo writes: > i think Al's solution (make -V ... | xargs .. ) > wins both in terms of simplicity and efficiency Ah, of course! now why didn't I think of that? :) DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 16:21: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from voi.aagh.net (pc1-hart4-0-cust168.mid.cable.ntl.com [62.254.84.168]) by hub.freebsd.org (Postfix) with ESMTP id A157737B400 for ; Thu, 21 Feb 2002 16:21:03 -0800 (PST) Received: from freaky by voi.aagh.net with local (Exim 3.35 #1) id 16e3SQ-000Cyq-00 for freebsd-current@FreeBSD.org; Fri, 22 Feb 2002 00:21:02 +0000 Date: Fri, 22 Feb 2002 00:21:02 +0000 From: Thomas Hurst To: freebsd-current@FreeBSD.org Subject: Re: Building php mod and cgi Message-ID: <20020222002102.GA49724@voi.aagh.net> Mail-Followup-To: freebsd-current@FreeBSD.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Organization: Not much. X-Operating-System: FreeBSD/4.5-PRERELEASE (i386) X-Uptime: 12:19AM up 63 days, 9:04, 4 users, load averages: 2.00, 2.00, 2.00 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Joseph Wright (JWRIGHT@mbakercorp.com) wrote: > Is their a way to build the port mod_php4 as the module version > for apache and the cgi for command line options. I currently have > mod_php+apache13+mysql+gd working perfect but I now have the need to > run php from the command prompt with mysql & gd. What is the best way > to go about this. Install lang/php4, it slaves off www/mod_php4 but produces a standalone executable instead. -- Thomas 'Freaky' Hurst - freaky@aagh.net - http://www.aagh.net/ - Documentation is the castor oil of programming. Managers know it must be good because the programmers hate it so much. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 16:28:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 6FC4F37B402; Thu, 21 Feb 2002 16:28:22 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 3D4F5AE2DA; Thu, 21 Feb 2002 16:28:22 -0800 (PST) Date: Thu, 21 Feb 2002 16:28:22 -0800 From: Alfred Perlstein To: Dag-Erling Smorgrav Cc: Luigi Rizzo , Bruce Evans , "M. Warner Losh" , current@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Proposed patch for "/bin/sh: Argument list too long" when compiling LINT ... Message-ID: <20020222002822.GJ12136@elvis.mu.org> References: <20020218.174959.96666779.imp@village.org> <20020219193515.Y1320-100000@gamplex.bde.org> <20020219004144.A25474@iguana.icir.org> <20020219085306.GL12136@elvis.mu.org> <20020221151439.D53952@iguana.icir.org> <20020221161651.E54262@iguana.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Dag-Erling Smorgrav [020221 16:19] wrote: > Luigi Rizzo writes: > > i think Al's solution (make -V ... | xargs .. ) > > wins both in terms of simplicity and efficiency > > Ah, of course! now why didn't I think of that? :) My first thought was: "If make(1) doesn't have that functionality I will beat it into it with a lead pipe..." Luckly I can across the option. :) -- -Alfred Perlstein [alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 16:29:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id A074E37B402; Thu, 21 Feb 2002 16:29:43 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id F160D5341; Fri, 22 Feb 2002 01:29:41 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Alfred Perlstein Cc: Luigi Rizzo , Bruce Evans , "M. Warner Losh" , current@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Proposed patch for "/bin/sh: Argument list too long" when compiling LINT ... References: <20020218.174959.96666779.imp@village.org> <20020219193515.Y1320-100000@gamplex.bde.org> <20020219004144.A25474@iguana.icir.org> <20020219085306.GL12136@elvis.mu.org> <20020221151439.D53952@iguana.icir.org> <20020221161651.E54262@iguana.icir.org> <20020222002822.GJ12136@elvis.mu.org> From: Dag-Erling Smorgrav Date: 22 Feb 2002 01:29:41 +0100 In-Reply-To: <20020222002822.GJ12136@elvis.mu.org> Message-ID: Lines: 15 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-=-= Alfred Perlstein writes: > * Dag-Erling Smorgrav [020221 16:19] wrote: > > Ah, of course! now why didn't I think of that? :) > My first thought was: > "If make(1) doesn't have that functionality I will beat it into it > with a lead pipe..." Heh :) Here's a patch, anyway. DES -- Dag-Erling Smorgrav - des@ofug.org --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=kern.post.mk.diff Index: kern.post.mk =================================================================== RCS file: /home/ncvs/src/sys/conf/kern.post.mk,v retrieving revision 1.7 diff -u -r1.7 kern.post.mk --- kern.post.mk 10 Jan 2002 03:52:00 -0000 1.7 +++ kern.post.mk 22 Feb 2002 00:22:39 -0000 @@ -93,10 +93,10 @@ ${SYSTEM_SFILES} ${MFILES:T:S/.m$/.h/} if [ -f .olddep ]; then mv .olddep .depend; fi rm -f .newdep - env MKDEP_CPP="${CC} -E" CC="${CC}" \ - mkdep -a -f .newdep ${CFLAGS} ${CFILES} ${SYSTEM_CFILES} ${GEN_CFILES} - env MKDEP_CPP="${CC} -E" \ - mkdep -a -f .newdep ${ASM_CFLAGS} ${SFILES} ${SYSTEM_SFILES} + ${MAKE} -VCFILES -VSYSTEM_CFILES -VGEN_CFILES | xargs\ + env MKDEP_CPP="${CC} -E" CC="${CC}" mkdep -a -f .newdep ${CFLAGS} + ${MAKE} -VSFILES -VSYSTEM_FILES | xargs\ + env MKDEP_CPP="${CC} -E" mkdep -a -f .newdep ${ASM_CFLAGS} rm -f .depend mv .newdep .depend --=-=-=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 18: 0:39 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 676C137B402 for ; Thu, 21 Feb 2002 18:00:35 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g1M20HJx134632; Thu, 21 Feb 2002 21:00:22 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20020219130836.B16105@blackhelicopters.org> References: <20020219125011.A15871@blackhelicopters.org> <20020219190142.A66679@energyhq.homeip.net> <20020219130836.B16105@blackhelicopters.org> Date: Thu, 21 Feb 2002 21:00:16 -0500 To: Michael Lucas From: Garance A Drosihn Subject: Re: more -current testers - are they WANTED yet? Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 1:08 PM -0500 2/19/02, Michael Lucas wrote: >In an ideal world, you're correct. > >The real question here should have been: do those people who >are actively committing rapidly to the tree want to see this >happen? They are the people who will realistically have to >deal with the PRs. This is the main question of course, and I can't say that I've seen any of the really active developers comment on it. I do think it is important to get more people on -current, so I'm trying to do more with -current myself. So, for instance, I've already come across two small errors in -current which should certainly be fixed before 5.0 "goes -stable". However, looking at the bigger issues being discussed in -current right now, I expect it would be annoying if I bugged anyone about little cosmetic issues. I think if Michael writes up anything, it will certainly encourage more people to use current, including people who might very well start commenting on the little nit-picking items. Do the developers of current want that yet, or will they find it irritating to have people pointing out minor issues when they (the developers) are still trying to sort out some of the more major issues? Current is fine for me (at the moment at least, and if we ignore the topic of vmware...), and I do hope to write a few patches to fix the cosmetic things I do come across. But are the developers ready for maybe a hundred more people playing around with current, and reporting on all kinds of things? I assume we'd still like 5.0 to "go -stable" in about 8-10 months, so at which point to we start encouraging more people to jump into it? -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 18:45: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id EB9D737B402 for ; Thu, 21 Feb 2002 18:44:54 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g1M2ihJx037958; Thu, 21 Feb 2002 21:44:43 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: <20020219125011.A15871@blackhelicopters.org> <20020219190142.A66679@energyhq.homeip.net> <20020219130836.B16105@blackhelicopters.org> Date: Thu, 21 Feb 2002 21:44:42 -0500 To: current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: more -current testers - are they WANTED yet? Cc: Michael Lucas Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 9:00 PM -0500 2/21/02, Garance A Drosihn wrote: >At 1:08 PM -0500 2/19/02, Michael Lucas wrote: >>In an ideal world, you're correct. >> >>The real question here should have been: do those people who >>are actively committing rapidly to the tree want to see this >>happen? They are the people who will realistically have to >>deal with the PRs. > >I assume we'd still like 5.0 to "go -stable" in about 8-10 months, >so at which point to we start encouraging more people to jump >into it? It occurs to me that the "yet" that I added to this subject is a little misleading. Michael wasn't talking about articles which would appear this weekend... From Michael's original message: The last time I checked, I get 12-15 thousand readers for each article. One half of one percent uptake would (hopefully) be quite a few bug reports. My question to the community is: is it too early to do this? If I start now, the articles would probably appear April-May. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 20: 0:55 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id A777937B404 for ; Thu, 21 Feb 2002 20:00:51 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g1M40pn78295 for current@freebsd.org; Thu, 21 Feb 2002 20:00:51 -0800 (PST) (envelope-from obrien) Date: Thu, 21 Feb 2002 20:00:51 -0800 From: "David O'Brien" To: current@freebsd.org Subject: changes to rc.diskless* Message-ID: <20020221200050.A78243@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The existing very bazaar and local policy in rc.diskless1 is Just Wrong; and looks like no other Unix diskless configuration I've ever seen. I plan on committing this patch to negate this. The use of an MFS /var should also be settable. Otherwise installing ports(packages) is just a total PITA. Index: rc.diskless1 =================================================================== RCS file: /home/ncvs/src/etc/rc.diskless1,v retrieving revision 1.13 diff -u -r1.13 rc.diskless1 --- rc.diskless1 17 Jan 2002 00:10:28 -0000 1.13 +++ rc.diskless1 22 Feb 2002 03:52:41 -0000 @@ -92,13 +92,14 @@ done echo "Interface ${bootp_ifc} IP-Address ${bootp_ipa} Broadcast ${bootp_ipbca}" +if [ -d /conf/default/etc ]; then + mount_md 4096 /etc 0 + chkerr $? "MFS mount on /etc" + /bin/chmod 755 /etc -mount_md 4096 /etc 0 -chkerr $? "MFS mount on /etc" -/bin/chmod 755 /etc - -/bin/cp -Rp /conf/default/etc/* /etc -chkerr $? "cp /conf/default/etc to /etc MFS" + /bin/cp -Rp /conf/default/etc/* /etc + chkerr $? "cp /conf/default/etc to /etc MFS" +fi # Allow for override files to replace files in /etc. Use /conf/*/etc to find # the override files. First choice is default files that # always override, @@ -113,6 +114,11 @@ cp -Rp /conf/${i}/etc/* /etc fi done + +# Since we are starting with a very fresh /etc on an MFS: +if [ -d /conf/default/etc ]; then + newaliases +if # Tell /etc/rc to run the specified script after it does its mounts but # before it does anything else. Index: rc.diskless2 =================================================================== RCS file: /home/ncvs/src/etc/rc.diskless2,v retrieving revision 1.15 diff -u -r1.15 rc.diskless2 --- rc.diskless2 26 Dec 2001 17:18:39 -0000 1.15 +++ rc.diskless2 22 Feb 2002 03:56:18 -0000 @@ -56,7 +56,7 @@ fi echo "+++ mount_md of /var" -mount_md ${varsize:=65536} /var 1 +mount_md ${varsize:=32m} /var 1 echo "+++ populate /var using /etc/mtree/BSD.var.dist" /usr/sbin/mtree -deU -f /etc/mtree/BSD.var.dist -p /var @@ -83,7 +83,7 @@ # so if /var/tmp == /tmp, then you don't get a vi.recover. # if [ ! -h /tmp ]; then - mount_md ${tmpsize:=20480} /tmp 2 + mount_md ${tmpsize:=64m} /tmp 2 chmod 01777 /tmp fi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 20:40:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id CD03C37B416 for ; Thu, 21 Feb 2002 20:40:43 -0800 (PST) Received: (qmail 12758 invoked from network); 22 Feb 2002 04:40:31 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.136.163]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 22 Feb 2002 04:40:31 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 21 Feb 2002 23:39:40 -0500 (EST) From: John Baldwin To: Robert Watson Subject: Re: Patch to improve mutex collision performance Cc: current@FreeBSD.ORG, "David O'Brien" , Jake Burkholder , Greg Lehey , Matthew Dillon , Dag-Erling Smorgrav Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 21-Feb-02 Robert Watson wrote: > > On 21 Feb 2002, Dag-Erling Smorgrav wrote: > >> Matthew Dillon writes: >> > I'm not interested in using P4. I think it's a mistake. That is, I >> > think it is being severely overused. [...] >> >> Frankly, although I use Perforce myself for PAM work, I agree with Matt >> here. Most of what is going on in the Perforce should be happening on >> branches in our main repo, if only CVS didn't suck so bad at branching. >> >> I would like to suggest that we consider transitioning our main repo to >> Subversion. It's reasonably similar to cvs, and has all the features we >> need that cvs lack: metadata versioning, atomic commits, cheap >> branching... > > The problem is CVS. The solution is unclear. In the mean time, people > are using Perforce because it's an effective tool to do the job. Believe > me, I'd rather *not* be using two (or two and a half) different version > control and software source management schemes, but the practical reality > is that CVS cannot provide what I need to do what I do. Once there's a > reliable free version control system that can be the One True System, I'll > be extremely pleased to use it. Until then, well... :-) Yep, if subversion ends up being a p4 + decent diffs + annotate + repository replication (p4's vcp looks uber leet) + offline mode, then I'm all for it. :) It would be much easier to not be having to use p4 for work branches since I and others could just reverse integrate our changes into HEAD from the side branches. As it is, we have to create diffs and then patch them into CVS. This is part of the reason I think that p4 doesn't have the greatest diffs btw: you don't need diffs to move code from a work branch into HEAD, you can just reverse integ and it DTRT for you. Plus, if others want to see what you are up to, they can just check out your branch rather than having to pass diffs around. Basically, I don't think p4 was designed for people passing diffs around, folks are supposed to instead be looking at each others branches. However, that's not the way FreeBSD works atm (esp. since CVS is our real SCM), so we end up using p4 in possibly one of the worst ways possible. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 21: 0:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 0279F37B402; Thu, 21 Feb 2002 21:00:28 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g1M50Pi04803; Thu, 21 Feb 2002 22:00:26 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g1M50OL92078; Thu, 21 Feb 2002 22:00:24 -0700 (MST) (envelope-from imp@village.org) Date: Thu, 21 Feb 2002 22:00:29 -0700 (MST) Message-Id: <20020221.220029.50852208.imp@village.org> To: rooneg@electricjellyfish.net Cc: des@ofug.org, dillon@apollo.backplane.com, grog@FreeBSD.ORG, jake@locore.ca, obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance From: "M. Warner Losh" In-Reply-To: <20020221202143.GA23502@electricjellyfish.net> References: <200202210146.g1L1kqg91511@apollo.backplane.com> <20020221202143.GA23502@electricjellyfish.net> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'd love to see subversion beefed up. It looks like the most promising of the replacements for cvs on the horizon. One thing that it doesn't appear to have, that would be useful to the BSD community, is the ability to cons up a tree from multiple repos easily. If we had that, then we wouldn't need 5 different versions of cat for {Free,Net,Open}BSD, Darwin and BSD/os. :-) That reminds me, I gotta go fix FreeBSD's patch to grok patches properly ... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 21: 9:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 52CAC37B404 for ; Thu, 21 Feb 2002 21:09:46 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g1M59V789027; Thu, 21 Feb 2002 21:09:31 -0800 (PST) (envelope-from obrien) Date: Thu, 21 Feb 2002 21:09:27 -0800 From: "David O'Brien" To: robert garrett Cc: current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance Message-ID: <20020221210927.A86370@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20020221222218.GA11359@jochem.dyndns.org> <004401c1bb2b$936c7130$7228fea9@Eagle> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <004401c1bb2b$936c7130$7228fea9@Eagle>; from robertgarrett@sbcglobal.net on Thu, Feb 21, 2002 at 05:00:37PM -0600 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 21, 2002 at 05:00:37PM -0600, robert garrett wrote: > Could someone tell me where documentation concerning the > use of perforce and or, how to gain access to is located? > > Up until very recently I was not aware of it's existence. > This would make it very difficult for someone new to the > Project to contribute. You have read too much into the use of Perforce. It is a useful tool to some, and there is nothing wrong with people wanting to use a tool that handles merges much better than CVS does. Have you ever had a local change in /usr/src and had ''cvs up'' make a TOTAL mess of it? Or maybe done a vendor import into /usr/src/contrib and then tried to do a ''cvs co -j -j'' and seen just how totally idiotically STUPID CVS's merging can be? This is the problem space that some are using Perforce for -- because it can handle merges (integrations) more sanely. Thus there is nothing wrong with the _personal_ use of Perforce by some committers. > It seems to my line of thinking that the existence of a repository > That is undocumented, that is used for major development proccess's > Breaks our development model. My various local copies of the FreeBSD CVS repo where I do major toolchain work in is also undocumented. Since I have been using them for the better part of 5 years, I really don't a local private repository breaks our development model. What is breaking it, is for users of Perforce to expect the rest of the development community to use this tool also. Perforce is really a side issue of communication and collaboration in our development. In this case it boils down to one developer being told not to work on something because another developer has a work-in-progress also in that area. However the first developer felt that the work-in-progress was taking too long and thus should not be an impediment to his development in the same area. > Further enhancing the "Elite" attitude that is so often proscribed > To BSD* developers. No it isn't! I don't give you access to my local hard disk. Does that make me "Elite"? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 21 23:30: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C2FDF37B402; Thu, 21 Feb 2002 23:29:59 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1M7TxP14486; Thu, 21 Feb 2002 23:29:59 -0800 (PST) (envelope-from dillon) Date: Thu, 21 Feb 2002 23:29:59 -0800 (PST) From: Matthew Dillon Message-Id: <200202220729.g1M7TxP14486@apollo.backplane.com> To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: changes to rc.diskless* References: <20020221200050.A78243@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :The existing very bazaar and local policy in rc.diskless1 is Just Wrong; :and looks like no other Unix diskless configuration I've ever seen. I :plan on committing this patch to negate this. : :The use of an MFS /var should also be settable. Otherwise installing :ports(packages) is just a total PITA. While you've got rc.diskless* broken open it would be great if you could implement an override rc variable that completely overrides the script. i.e. so someone can set 'rc_diskless_script' in /etc/rc.conf (on the server) and /etc/rc will run that instead of /etc/rc.diskless1 if the machine is booted diskless. The problem we face is that the rc.diskless* scripts are simply not flexible enough to cover everyone's needs (or even most people's needs) and we need to provide a mechanism to allow the sysad to write his own without forcing him to edit a 'system standard' script (i.e. /etc/rc.diskless1 itself). In anycase, if you don't have time to add this I'd appreciate a head's up after you are done-and-committed your diskless scripts and I will have a go at it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 2:17:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail12.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with ESMTP id 1813137B416 for ; Fri, 22 Feb 2002 02:17:07 -0800 (PST) Received: (qmail 30567 invoked from network); 22 Feb 2002 10:17:05 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.136.163]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 22 Feb 2002 10:17:05 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 22 Feb 2002 05:17:05 -0500 (EST) From: John Baldwin To: current@FreeBSD.org Subject: device figlet for the kernel Cc: msmith@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Those of you who waste large amounts of time on IRC, esp. on The Channel Which Shall Rename Nameless will appreciate this: figlet is this nifty little ASCII art tool that Alfred likes to use a lot. He has since gotten several other people hooked on using it, and a sort of running joke has been to get figlet into the kernel. (Imagine ASCII part panic messages for example.) Mike Smith ported the figlet program as a filter on the low-level console output by taking over v_putc a while ago but it had an annoying bug where it only printed one char out at a time. During some down time tonight during which my brain was vegging, I picked up the code, tracked down the bug and added some features: - Originally, once figlet was initialized, it was turned on until you rebooted. Now it defaults to being off, but you can change that via a loader tunable (kern.figlet_enable). Also, there is an escape character that you can use to send commands to the figlet filter. Right now the only commands are to turn on figlet output; adjust the justification of the outputted text as either left, center, or right aligned; or turn off figlet output and revert to normal output. When figlet is turned off, the justification is reset to the default of left. - figlet is not a psuedo device that can be conditionally compiled into the kernel by putting 'device figlet' in your kernel config file - a spin lock has been added to protect the state machine variables so that it is SMPng safe. - a new console API function cnsetputc() has been added so that v_putc can be changed at runtime. This isn't quite right as v_putc really needs a lock now. Currently figlet isn't a kernel module, but one could make it so without too much additional work. To play with this, first download and apply the patch at http://www.FreeBSD.org/~jhb/patches/figlet.patch Then compile a kernel with 'device figlet'. You will need to load a figlet font file in the loader when you boot. You can get font files from either the figlet or figlet-fonts ports. For example, if you copy /usr/local/share/figlet/standard.flf (the default font) to /boot, then you would need to either use 'load -t figlet_font /boot/standard.flf' prior to booting the kernel or add the following to /boot/loader.conf: font_load="YES" font_name="/boot/standard.flf" font_type="figlet_font" The patch includes a sample SYSINIT at the bottom of subr_figlet.c that demonstrates sending commands to the filter. So who's going to do subr_jive.c next? :) -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 2:26:14 2002 Delivered-To: freebsd-current@freebsd.org Received: from gate.uai.etel.ru (gate.uai.etel.ru [195.38.57.243]) by hub.freebsd.org (Postfix) with ESMTP id D4E3237B404 for ; Fri, 22 Feb 2002 02:26:06 -0800 (PST) Received: by sendmail of gate.uai.etel.ru id g1MAQ7O17427 for ; Fri, 22 Feb 2002 15:26:07 +0500 X-Authentication-Warning: gate.uai.etel.ru: smap set sender to using -f Received: from by gate.uai.etel.ru via smap (V2.1) id xma017317; Fri, 22 Feb 02 15:24:11 +0500 Received: by sendmail with ESMTP id g1MAOA0u006208 from vlad@telecom.ural.ru for ; Fri, 22 Feb 2002 15:24:10 +0500 Received: by sendmail id g1MAOA8G006207 for freebsd-current@FreeBSD.ORG.KAV; Fri, 22 Feb 2002 15:24:10 +0500 Received: by sendmail with ESMTP id g1MAO90u006190; Fri, 22 Feb 2002 15:24:09 +0500 Date: Fri, 22 Feb 2002 15:24:08 +0500 From: "Vladimir G. Drobyshevsky" X-Mailer: The Bat! (v1.54 Beta/8) Reply-To: "Vladimir G. Drobyshevsky" Organization: Computer saloons "TelescOp" X-Priority: 3 (Normal) Message-ID: <13314046938.20020222152408@telecom.ural.ru> To: freebsd-bugs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Is any patch to situation with bad linking library on -CURRENT? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Have a nice day! I'm sorry for possible beginning of flame, but is there exist real solution for bad linking library problem on -CURRENT? I was noticed about this problem about two or three weeks ago, and don't see nothing except discussions about new binutils. May be I was inattentive but can anybody tell me (may be, for us?) how to fix that problem? I haven't enough knowledge to solve this by my hand for my sorry and need assistance. I have AMD Duron, MB Epox 8KTA3+, IBM 60 Gb, Radeon 8500, and 5.0-CURRENT installed on that. The first problem was occured is coredumps any program compiled with imlib. It was come to light on gnomelibs building - on configure stage conftest program was exit with bus error message and coredumps. The second problem is mplayer exits with the same message (bus error) right after launch. Once again excuse me for anxiety and possible impoliteness. Sincerelly yours, Vladimir G. Drobyshevsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 2:43:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from theinternet.com.au (c20631.kelvn1.qld.optusnet.com.au [203.164.207.8]) by hub.freebsd.org (Postfix) with ESMTP id 343C937B400; Fri, 22 Feb 2002 02:43:09 -0800 (PST) Received: (from akm@localhost) by theinternet.com.au (8.11.6/8.11.4) id g1MAh3I33499; Fri, 22 Feb 2002 20:43:03 +1000 (EST) (envelope-from akm) Date: Fri, 22 Feb 2002 20:43:03 +1000 From: Andrew Kenneth Milton To: John Baldwin Cc: current@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: device figlet for the kernel Message-ID: <20020222204303.N90065@zeus.theinternet.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from jhb@FreeBSD.ORG on Fri, Feb 22, 2002 at 05:17:05AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG +-------[ John Baldwin ]---------------------- | Those of you who waste large amounts of time on IRC, esp. on The Channel Which | Shall Rename Nameless will appreciate this: [snip] So the truth finally comes out. Now we discover the real reason -current was delayed for 12 months d8) -- Totally Holistic Enterprises Internet| | Andrew Milton The Internet (Aust) Pty Ltd | | ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 3:12:10 2002 Delivered-To: freebsd-current@freebsd.org Received: from gateg.kw.bbc.co.uk (gateg.kw.bbc.co.uk [132.185.132.16]) by hub.freebsd.org (Postfix) with ESMTP id B39A837B405; Fri, 22 Feb 2002 03:12:06 -0800 (PST) Received: from sunf0.rd.bbc.co.uk (ddmailgate.rd.bbc.co.uk [132.185.128.104]) by gateg.kw.bbc.co.uk (8.11.2/8.11.2) with SMTP id g1MBC1w02924; Fri, 22 Feb 2002 11:12:03 GMT Received: from inet34.rd.bbc.co.uk by sunf0.rd.bbc.co.uk; Fri, 22 Feb 02 11:11:54 GMT Date: Fri, 22 Feb 2002 11:11:51 +0000 From: Jonathan Perkin To: John Baldwin Cc: current@FreeBSD.org Subject: Re: device figlet for the kernel Message-Id: <20020222111151.GW5885@inet34.rd.bbc.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri Feb 22, 2002 at 05:17:05AM -0500, John Baldwin wrote: > So who's going to do subr_jive.c next? :) subr_cowsay.c first :) -- Jonathan Perkin - BBC Internet Services - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 4: 9:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id B12A037B400; Fri, 22 Feb 2002 04:09:15 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.6/8.11.6) id g1MC8o229256; Fri, 22 Feb 2002 14:08:50 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200202221208.g1MC8o229256@zibbi.icomtek.csir.co.za> Subject: Re: Is any patch to situation with bad linking library on -CURRENT? In-Reply-To: <13314046938.20020222152408@telecom.ural.ru> from "Vladimir G. Drobyshevsky" at "Feb 22, 2002 03:24:08 pm" To: vlad@telecom.ural.ru (Vladimir G. Drobyshevsky) Date: Fri, 22 Feb 2002 14:08:50 +0200 (SAT) Cc: freebsd-bugs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > I'm sorry for possible beginning of flame, but is there exist real > solution for bad linking library problem on -CURRENT? I was noticed > about this problem about two or three weeks ago, and don't see nothing > except discussions about new binutils. It looks like the import for binutils today fixed it. At least my test case of libpng does not coredump anymore. I'll see how far a release gets. It will probably not finish because I think the dhcp stuff in the crunch files are still broken. John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 4:22: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from isris.pair.com (isris.pair.com [209.68.2.39]) by hub.freebsd.org (Postfix) with SMTP id 4D3A037B416 for ; Fri, 22 Feb 2002 04:21:51 -0800 (PST) Received: (qmail 84036 invoked by uid 3130); 22 Feb 2002 12:21:50 -0000 Date: Fri, 22 Feb 2002 07:21:50 -0500 From: Garrett Rooney To: "M. Warner Losh" Cc: des@ofug.org, dillon@apollo.backplane.com, grog@FreeBSD.ORG, jake@locore.ca, obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance Message-ID: <20020222122149.GA23702@electricjellyfish.net> References: <200202210146.g1L1kqg91511@apollo.backplane.com> <20020221202143.GA23502@electricjellyfish.net> <20020221.220029.50852208.imp@village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020221.220029.50852208.imp@village.org> User-Agent: Mutt/1.3.25i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 21, 2002 at 10:00:29PM -0700, M. Warner Losh wrote: > I'd love to see subversion beefed up. It looks like the most > promising of the replacements for cvs on the horizon. > > One thing that it doesn't appear to have, that would be useful to the > BSD community, is the ability to cons up a tree from multiple repos > easily. If we had that, then we wouldn't need 5 different versions of > cat for {Free,Net,Open}BSD, Darwin and BSD/os. :-) This is one of the features that has been requested several times, and is on the agenda for after we hit 1.0. Subversion is trying to limit it's first round of functionality to 'What CVS does, minus the worst problems'. After that, we'll get to work on the other cool features ;-) > That reminds me, I gotta go fix FreeBSD's patch to grok patches > properly ... Thank You!!! It is so annoying having to install the port of gpatch... If you could also remove the FreeBSD specific hacks to diff, it would be quite appreciated (see http://svn.collab.net/repos/svn/trunk/ac-helpers/gnu-diff.sh for the script we use to ensure we have a working version of diff). -garrett -- garrett rooney Unix was not designed to stop you from rooneg@electricjellyfish.net doing stupid things, because that would http://electricjellyfish.net/ stop you from doing clever things. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 5:34:52 2002 Delivered-To: freebsd-current@freebsd.org Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by hub.freebsd.org (Postfix) with ESMTP id 5764137B402 for ; Fri, 22 Feb 2002 05:34:46 -0800 (PST) Received: from pool-63.49.207.155.troy.grid.net ([63.49.207.155] helo=europa2) by granger.mail.mindspring.net with smtp (Exim 3.33 #1) id 16eFqU-0002cQ-00 for current@FreeBSD.ORG; Fri, 22 Feb 2002 08:34:43 -0500 Message-Id: <3.0.6.32.20020222083301.00d94c70@imatowns.com> X-Sender: ggombert@imatowns.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 22 Feb 2002 08:33:01 -0500 To: current@FreeBSD.ORG From: Glenn Gombert Subject: Install World fails in -Current Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have tried to re-cvsup and a clean rebuild the alst couple of days, and I keep getting this error when I try and do an 'installworld' ..after a clean build...does anyone know what might be causing this?? ... ........ mtree -deU -f /usr/src/etc/mtree/BSD.var -p /var mtree: line 67: unknown user smmsp Glenn Gombert ggombert@imatowns.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 5:38:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 3E90F37B400 for ; Fri, 22 Feb 2002 05:38:41 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id g1MDceE75453; Fri, 22 Feb 2002 05:38:40 -0800 (PST) (envelope-from david) Date: Fri, 22 Feb 2002 05:38:40 -0800 (PST) From: David Wolfskill Message-Id: <200202221338.g1MDceE75453@bunrab.catwhisker.org> To: current@FreeBSD.ORG, ggombert@imatowns.com Subject: Re: Install World fails in -Current In-Reply-To: <3.0.6.32.20020222083301.00d94c70@imatowns.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Date: Fri, 22 Feb 2002 08:33:01 -0500 >From: Glenn Gombert >I have tried to re-cvsup and a clean rebuild the alst couple of days, and I >keep getting this error when I try and do an 'installworld' ..after a clean >build...does anyone know what might be causing this?? >... >........ >mtree -deU -f /usr/src/etc/mtree/BSD.var -p /var >mtree: line 67: unknown user smmsp Sounds like a botched (or not run) "mergemaster" execution: freebeast(5.0-C)[2] grep smmsp /usr/src/etc/master.passwd smmsp:*:25:25::0:0:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin freebeast(5.0-C)[3] Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 6:49:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 8DA0A37B404 for ; Fri, 22 Feb 2002 06:49:23 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 16eH0k-0002uE-00; Fri, 22 Feb 2002 15:49:22 +0100 Message-Id: From: mailnull@mips.inka.de Date: Fri, 22 Feb 2002 15:49:22 +0100 To: undisclosed-recipients:; Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From mailnull@mips.inka.de Fri Feb 22 15:33:26 2002 Received: from kemoauc.mips.inka.de (localhost [127.0.0.1]) by kemoauc.mips.inka.de (8.12.2/8.12.2) with ESMTP id g1MEXQ0L002228 for ; Fri, 22 Feb 2002 15:33:26 +0100 (CET) (envelope-from mailnull@localhost.mips.inka.de) Received: (from mailnull@localhost) by kemoauc.mips.inka.de (8.12.2/8.12.2/Submit) id g1MEXQ2T002227 for freebsd-current@freebsd.org; Fri, 22 Feb 2002 15:33:26 +0100 (CET) (envelope-from mailnull) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: HEADS UP: sendmail 8.12.2 imported Date: Fri, 22 Feb 2002 14:33:26 +0000 (UTC) Message-ID: References: <15472.16902.218983.970624@horsey.gshapiro.net> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-current@freebsd.org Gregory Neil Shapiro wrote: > sendmail 8.12.2 has been imported into -CURRENT. Users of ports/mail/bsmtp beware, this breaks address rewriting in the bsmtp mailer, because it still references the rewriting rules by number. I'll update the port shortly. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 7:43:57 2002 Delivered-To: freebsd-current@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id B842337B417; Fri, 22 Feb 2002 07:43:45 -0800 (PST) Received: from pool0378.cvx22-bradley.dialup.earthlink.net ([209.179.199.123] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16eHr2-0007Dq-00; Fri, 22 Feb 2002 07:43:24 -0800 Message-ID: <3C766712.36698EC1@mindspring.com> Date: Fri, 22 Feb 2002 07:43:14 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Dag-Erling Smorgrav , Luigi Rizzo , Bruce Evans , "M. Warner Losh" , current@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Proposed patch for "/bin/sh: Argument list too long" when compiling LINT ... References: <20020218.174959.96666779.imp@village.org> <20020219193515.Y1320-100000@gamplex.bde.org> <20020219004144.A25474@iguana.icir.org> <20020219085306.GL12136@elvis.mu.org> <20020221151439.D53952@iguana.icir.org> <20020221161651.E54262@iguana.icir.org> <20020222002822.GJ12136@elvis.mu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > * Dag-Erling Smorgrav [020221 16:19] wrote: > > Luigi Rizzo writes: > > > i think Al's solution (make -V ... | xargs .. ) > > > wins both in terms of simplicity and efficiency > > > > Ah, of course! now why didn't I think of that? :) > > My first thought was: > "If make(1) doesn't have that functionality I will beat it into it > with a lead pipe..." > > Luckly I can across the option. :) Alfred, an hour later: "Wow, there's a lot of code in here that almost does exactly what I want!". 8-) 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 8:15:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 2151537B400; Fri, 22 Feb 2002 08:15:24 -0800 (PST) Received: from pool0378.cvx22-bradley.dialup.earthlink.net ([209.179.199.123] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16eILz-0004yR-00; Fri, 22 Feb 2002 08:15:23 -0800 Message-ID: <3C766E91.4637BE0E@mindspring.com> Date: Fri, 22 Feb 2002 08:15:13 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: obrien@FreeBSD.ORG Cc: robert garrett , current@FreeBSD.ORG Subject: Re: Patch to improve mutex collision performance References: <20020221222218.GA11359@jochem.dyndns.org> <004401c1bb2b$936c7130$7228fea9@Eagle> <20020221210927.A86370@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David O'Brien wrote: > No it isn't! I don't give you access to my local hard disk. Does that > make me "Elite"? Yes, you're "Elite". ;^). But not handing out keys to your local hard disk doesn;t make you "Elitest". 8-) 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 8:19:56 2002 Delivered-To: freebsd-current@freebsd.org Received: from beastie.jocose.org (beastie.jocose.org [199.199.226.71]) by hub.freebsd.org (Postfix) with SMTP id 432D237B405 for ; Fri, 22 Feb 2002 08:19:03 -0800 (PST) Received: (qmail 48492 invoked from network); 22 Feb 2002 17:18:54 -0000 Received: from unknown (HELO jocose.org) (10.0.0.100) by 0 with SMTP; 22 Feb 2002 17:18:54 -0000 Message-ID: <3C766FFD.3040800@jocose.org> Date: Fri, 22 Feb 2002 10:21:17 -0600 From: Peter Schultz Organization: jocose.org User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.8) Gecko/20020222 X-Accept-Language: en-us MIME-Version: 1.0 To: obrien@FreeBSD.org, gnome@FreeBSD.org, freebsd-current@FreeBSD.org Subject: ports problem: where to start Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just upgraded everything on my system and I'm still having trouble with vim, AbiWord, and open-motif-devel. The problem with vim is one I can fix by changing the install.sh script it comes with by forcing it to link against the X11 library. For some reason it does not pick up that it's required: $ gvim /usr/libexec/ld-elf.so.1: Shared object "libXThrStub.XmbResetIC" not found The other two are executing `mkdir /' at install time. This fails: ===> Installing for AbiWord-0.99.1_1 ===> AbiWord-0.99.1_1 depends on shared library: png.5 - found ===> AbiWord-0.99.1_1 depends on shared library: giconv.2 - found ===> AbiWord-0.99.1_1 depends on shared library: psiconv.7 - found ===> AbiWord-0.99.1_1 depends on shared library: X11.6 - found ===> AbiWord-0.99.1_1 depends on shared library: glib12.3 - found ===> AbiWord-0.99.1_1 depends on shared library: gtk12.2 - found Making install in src gmake[1]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src' Making install in tools gmake[2]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools' Making install in cdump gmake[3]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump' Making install in xp gmake[4]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump/xp' gmake[5]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump/xp' gmake[5]: Nothing to be done for `install-exec-am'. gmake[5]: Nothing to be done for `install-data-am'. gmake[5]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump/xp' gmake[4]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump/xp' gmake[4]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump' gmake[5]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump' gmake[5]: Nothing to be done for `install-exec-am'. gmake[5]: Nothing to be done for `install-data-am'. gmake[5]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump' gmake[4]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump' gmake[3]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/cdump' Making install in pfa2afm gmake[3]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm' Making install in unix gmake[4]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm/unix' gmake[5]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm/unix' gmake[5]: Nothing to be done for `install-exec-am'. gmake[5]: Nothing to be done for `install-data-am'. gmake[5]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm/unix' gmake[4]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm/unix' gmake[4]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm' gmake[5]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm' gmake[5]: Nothing to be done for `install-exec-am'. gmake[5]: Nothing to be done for `install-data-am'. gmake[5]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm' gmake[4]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm' gmake[3]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/pfa2afm' Making install in ttftool gmake[3]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/ttftool' Making install in unix gmake[4]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/ttftool/unix' gmake[5]: Entering directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/ttftool/unix' mkdir: /: Is a directory gmake[5]: *** [install-exec-local] Error 1 gmake[5]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/ttftool/unix' gmake[4]: *** [install-am] Error 2 gmake[4]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/ttftool/unix' gmake[3]: *** [install-recursive] Error 1 gmake[3]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools/ttftool' gmake[2]: *** [install-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src/tools' gmake[1]: *** [install-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/editors/AbiWord/work/abiword/abi/src' gmake: *** [install-recursive] Error 1 *** Error code 2 Stop in /usr/ports/editors/AbiWord. *** Error code 1 Stop in /usr/ports/editors/AbiWord. *** Error code 1 Stop in /usr/ports/editors/AbiWord. *** Error code 1 Stop in /usr/ports/editors/AbiWord. ===> Installing for open-motif-devel-2.1.30 ===> open-motif-devel-2.1.30 depends on shared library: X11.6 - found mkdir: /: Is a directory *** Error code 1 Stop in /usr/ports/x11-toolkits/open-motif-devel. *** Error code 1 Stop in /usr/ports/x11-toolkits/open-motif-devel. *** Error code 1 Stop in /usr/ports/x11-toolkits/open-motif-devel. Unfortunately I have no idea what I might have done to cause these failures. As far as I know I'm following all the suggested steps to build world and ports, i.e. there is nothing added to make.conf, etc. Sincerely, Pete... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 8:35:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id 9B08137B400 for ; Fri, 22 Feb 2002 08:35:48 -0800 (PST) Received: (qmail 16573 invoked from network); 22 Feb 2002 16:35:46 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.90.111.58]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 22 Feb 2002 16:35:46 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200202221338.g1MDceE75453@bunrab.catwhisker.org> Date: Fri, 22 Feb 2002 11:35:45 -0500 (EST) From: John Baldwin To: David Wolfskill Subject: Re: Install World fails in -Current Cc: ggombert@imatowns.com, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 22-Feb-02 David Wolfskill wrote: >>Date: Fri, 22 Feb 2002 08:33:01 -0500 >>From: Glenn Gombert > >>I have tried to re-cvsup and a clean rebuild the alst couple of days, and I >>keep getting this error when I try and do an 'installworld' ..after a clean >>build...does anyone know what might be causing this?? > >>... >>........ >>mtree -deU -f /usr/src/etc/mtree/BSD.var -p /var >>mtree: line 67: unknown user smmsp > > > Sounds like a botched (or not run) "mergemaster" execution: Sort of. The problem is we have added a new user that installworld depends on. Imagine a 4.x to 5.0 upgrade right now. 4.x doesn't have this user IIRC, and you are supposed to run installworld before mergemaster. Sounds like a nice catch 22 to me. :-/ -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 9: 9:40 2002 Delivered-To: freebsd-current@freebsd.org Received: from nebula.anchoragerescue.org (cable-115-7-237-24.anchorageak.net [24.237.7.115]) by hub.freebsd.org (Postfix) with ESMTP id 0AD8237B402 for ; Fri, 22 Feb 2002 09:09:35 -0800 (PST) Received: from there (galaxy.anchoragerescue.org [24.237.7.95]) by nebula.anchoragerescue.org (Postfix) with SMTP id 9D2EFAA for ; Fri, 22 Feb 2002 08:09:28 -0900 (AKST) Content-Type: text/plain; charset="iso-8859-1" From: Beech Rintoul To: freebsd-current@freebsd.org Subject: Build Failure (libkvm) Date: Fri, 22 Feb 2002 08:09:28 -0900 X-Mailer: KMail [version 1.3] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020222170928.9D2EFAA@nebula.anchoragerescue.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Last night's build for -current failed with the following: mkdep -f .depend -a -DLIBC_SCCS -I/usr/src/lib/libkvm /usr/src/lib/libkvm/kvm.c /usr/src/lib/libkvm/kvm_i386.c /usr/src/lib/libkvm/kvm_file.c /usr/src/lib/libkvm/kvm_getloadavg.c /usr/src/lib/libkvm/kvm_getswapinfo.c /usr/src/lib/libkvm/kvm_proc.c cd /usr/src/lib/libkvm; make _EXTRADEPEND cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm.c -o kvm.o cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm_i386.c -o kvm_i386.o cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm_file.c -o kvm_file.o cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm_getloadavg.c -o kvm_getloadavg.o cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm_getswapinfo.c -o kvm_getswapinfo.o cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm_proc.c -o kvm_proc.o /usr/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist': /usr/src/lib/libkvm/kvm_proc.c:316: incompatible types in assignment *** Error code 1 Stop in /usr/src/lib/libkvm. *** Error code 1 Tried all the usual, rm -R /usr/obj, fresh cvsup etc.... Beech -- ------------------------------------------------------------------- Beech Rintoul - IT Manager - Instructor - akbeech@anchoragerescue.org /"\ ASCII Ribbon Campaign | Anchorage Gospel Rescue Mission \ / - NO HTML/RTF in e-mail | P.O. Box 230510 X - NO Word docs in e-mail | Anchorage, AK 99523-0510 / \ ----------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 9:14:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 3103C37B405 for ; Fri, 22 Feb 2002 09:14:33 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id g1MHESZ76173; Fri, 22 Feb 2002 09:14:28 -0800 (PST) (envelope-from david) Date: Fri, 22 Feb 2002 09:14:28 -0800 (PST) From: David Wolfskill Message-Id: <200202221714.g1MHESZ76173@bunrab.catwhisker.org> To: akbeech@anchoragerescue.org Subject: Re: Build Failure (libkvm) Cc: current@freebsd.org In-Reply-To: <20020222170928.9D2EFAA@nebula.anchoragerescue.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >From: Beech Rintoul >Date: Fri, 22 Feb 2002 08:09:28 -0900 >Last night's build for -current failed with the following: I got -CURRENT built today without problem. Recent CVSup history: freebeast(5.0-C)[1] tail /var/log/cvsup-history.log CVSup begin from cvsup14.freebsd.org at Mon Feb 18 03:47:02 PST 2002 CVSup ended from cvsup14.freebsd.org at Mon Feb 18 03:54:22 PST 2002 CVSup begin from cvsup14.freebsd.org at Tue Feb 19 03:47:02 PST 2002 CVSup ended from cvsup14.freebsd.org at Tue Feb 19 03:53:36 PST 2002 CVSup begin from cvsup14.freebsd.org at Wed Feb 20 03:47:02 PST 2002 CVSup ended from cvsup14.freebsd.org at Wed Feb 20 04:00:08 PST 2002 CVSup begin from cvsup14.freebsd.org at Thu Feb 21 03:47:03 PST 2002 CVSup ended from cvsup14.freebsd.org at Thu Feb 21 03:53:29 PST 2002 CVSup begin from cvsup14.freebsd.org at Fri Feb 22 03:47:02 PST 2002 CVSup ended from cvsup14.freebsd.org at Fri Feb 22 03:54:26 PST 2002 freebeast(5.0-C)[2] uname -a FreeBSD freebeast.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #86: Fri Feb 22 07:07:23 PST 2002 root@freebeast.catwhisker.org:/common/S4/obj/usr/src/sys/FREEBEAST i386 freebeast(5.0-C)[3] Might try updating again.... Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 9:40:55 2002 Delivered-To: freebsd-current@freebsd.org Received: from nebula.anchoragerescue.org (cable-115-7-237-24.anchorageak.net [24.237.7.115]) by hub.freebsd.org (Postfix) with ESMTP id 22EA637B400 for ; Fri, 22 Feb 2002 09:40:44 -0800 (PST) Received: from there (galaxy.anchoragerescue.org [24.237.7.95]) by nebula.anchoragerescue.org (Postfix) with SMTP id E3CC9AA; Fri, 22 Feb 2002 08:40:42 -0900 (AKST) Content-Type: text/plain; charset="iso-8859-1" From: Beech Rintoul To: David Wolfskill Subject: Re: Build Failure (libkvm) Date: Fri, 22 Feb 2002 08:40:42 -0900 X-Mailer: KMail [version 1.3] Cc: freebsd-current@freebsd.org References: <200202221714.g1MHESZ76173@bunrab.catwhisker.org> In-Reply-To: <200202221714.g1MHESZ76173@bunrab.catwhisker.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020222174042.E3CC9AA@nebula.anchoragerescue.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Friday 22 February 2002 08:14 am, David Wolfskill wrote: > From: Beech Rintoul > > >Date: Fri, 22 Feb 2002 08:09:28 -0900 > > > >Last night's build for -current failed with the following: > > I got -CURRENT built today without problem. Recent CVSup history: > (snip history) > > Might try updating again.... Already did that. The update was about 15 minutes prior to that last build attempt. Interesting, the last change to that file was about 2 weeks ago and I have done several builds since then. I'm clueless as to why it picked today to fail rather than immediately following the commit. Beech -- ------------------------------------------------------------------- Beech Rintoul - IT Manager - Instructor - akbeech@anchoragerescue.org /"\ ASCII Ribbon Campaign | Anchorage Gospel Rescue Mission \ / - NO HTML/RTF in e-mail | P.O. Box 230510 X - NO Word docs in e-mail | Anchorage, AK 99523-0510 / \ ----------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 9:52:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 13F3837B405; Fri, 22 Feb 2002 09:52:26 -0800 (PST) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id g1MHqPF09731; Fri, 22 Feb 2002 09:52:25 -0800 Date: Fri, 22 Feb 2002 09:52:25 -0800 From: Brooks Davis To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: changes to rc.diskless* Message-ID: <20020222095225.A6604@Odin.AC.HMC.Edu> References: <20020221200050.A78243@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020221200050.A78243@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Thu, Feb 21, 2002 at 08:00:51PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 21, 2002 at 08:00:51PM -0800, David O'Brien wrote: > The use of an MFS /var should also be settable. Otherwise installing > ports(packages) is just a total PITA. I had issues with the MFS /var and /tmp[0] a couple days ago and changed the code to move the "mount -a" up before /var and /tmp creation and then actually test to be sure they are not writable before attempting to create MFS versions. The logic was basicly: if touch /var/_writable_test; then rm /var/_writable_test else #create MFS var fi -- Brooks [0] I've got a slightly strange configuration with network booting cluster nodes which have a disk for /tmp, /var, and swap. --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --2fHTh5uZTiUOsy+g Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8doVYXY6L6fI4GtQRAk8pAKCw4j/Tr4mThxxoi25mLag+PwQ+TwCgpFzP ROLGGWCPOo/mpTLeeYBcEHU= =30dv -----END PGP SIGNATURE----- --2fHTh5uZTiUOsy+g-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 10:14:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailgate.rz.uni-karlsruhe.de (mailgate.rz.uni-karlsruhe.de [129.13.64.97]) by hub.freebsd.org (Postfix) with ESMTP id 44BC137B416 for ; Fri, 22 Feb 2002 10:14:30 -0800 (PST) Received: from f113.hadiko.de (root@hadif113.hadiko.uni-karlsruhe.de [172.20.42.143]) by mailgate.rz.uni-karlsruhe.de with esmtp (Exim 3.33 #1) id 16eKDF-0000K2-00; Fri, 22 Feb 2002 19:14:29 +0100 Received: (from riggs@localhost) by f113.hadiko.de (8.11.6/8.11.6) id g1MIESb08879; Fri, 22 Feb 2002 19:14:28 +0100 (CET) (envelope-from riggs) Date: Fri, 22 Feb 2002 19:14:28 +0100 From: "Thomas E. Zander" To: Michael Class Cc: current@freebsd.org Subject: Re: Recent USB problems Message-ID: <20020222181428.GA8774@f113.hadiko.de> References: <3C6F6F85.4050300@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <3C6F6F85.4050300@gmx.net> Organization: RiggiServ - Ihr Partner =?iso-8859-15?Q?f?= =?iso-8859-15?Q?=FCr?= alles Delikate X-PGP-KeyID: 0xC85996CD X-PGP-Fingerprint: 4F59 75B4 4CE3 3B00 BC61 5400 8DD4 8929 C859 96CD X-Mailer: Riggisoft Ausguck Eggsbress (Build 1014400815) X-Operating-System: Riggiland BSD 4.5-RELEASE (To serve and protect.) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 17. Feb 2002, at 9:53 +0100, Michael Class wrote according to [Recent USB problems]: > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > > The system is a dual PIII Gigabyte system with VIA-Chipset. > > Any hints? Sorry, no hint by my side, but I can report exactly the same problem on an Athlon-C System equipped with a VIA-KT133A chipset. (actually it has the same USB controller, so it was expectable) Riggs -- - "[...] I talked to the computer at great length and -- explained my view of the Universe to it" said Marvin. --- And what happened?" pressed Ford. ---- "It committed suicide." said Marvin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 10:23:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 86E9937B404 for ; Fri, 22 Feb 2002 10:23:17 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.6/8.11.6) id g1MIMrW40266; Fri, 22 Feb 2002 20:22:53 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200202221822.g1MIMrW40266@zibbi.icomtek.csir.co.za> Subject: Re: Build Failure (libkvm) In-Reply-To: <20020222174042.E3CC9AA@nebula.anchoragerescue.org> from Beech Rintoul at "Feb 22, 2002 08:40:42 am" To: akbeech@anchoragerescue.org (Beech Rintoul) Date: Fri, 22 Feb 2002 20:22:53 +0200 (SAT) Cc: david@catwhisker.org (David Wolfskill), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > > >Date: Fri, 22 Feb 2002 08:09:28 -0900 > > > > > >Last night's build for -current failed with the following: > > > > I got -CURRENT built today without problem. Recent CVSup history: > > > (snip history) > > > > Might try updating again.... > > Already did that. The update was about 15 minutes prior to that last build > attempt. Interesting, the last change to that file was about 2 weeks ago and > I have done several builds since then. I'm clueless as to why it picked today > to fail rather than immediately following the commit. The type of p_runtime in sys/proc.h changed today, but ki_runtime in sys/user.h hasn't changed yet. Or maybe it shouldn't change and there should rather be a conversion? Who knows. :-) phk? John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 10:23:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 87C0E37B402; Fri, 22 Feb 2002 10:23:19 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g1MINCD61500; Fri, 22 Feb 2002 13:23:13 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 22 Feb 2002 13:23:12 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Brooks Davis Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: changes to rc.diskless* In-Reply-To: <20020222095225.A6604@Odin.AC.HMC.Edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 22 Feb 2002, Brooks Davis wrote: > On Thu, Feb 21, 2002 at 08:00:51PM -0800, David O'Brien wrote: > > The use of an MFS /var should also be settable. Otherwise installing > > ports(packages) is just a total PITA. > > I had issues with the MFS /var and /tmp[0] a couple days ago and changed > the code to move the "mount -a" up before /var and /tmp creation and > then actually test to be sure they are not writable before attempting to > create MFS versions. The logic was basicly: > > if touch /var/_writable_test; then > rm /var/_writable_test > else > #create MFS var > fi > > -- Brooks > > [0] I've got a slightly strange configuration with network booting > cluster nodes which have a disk for /tmp, /var, and swap. One of the problems I have with a similar configuration is that the file system checker never runs for local filesystems mounted on writable disks. I tend to mount everything nfs and mfs, except for a scratch drive and swap, which are from the local hard disk. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 10:35:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id A0EE237B402; Fri, 22 Feb 2002 10:35:28 -0800 (PST) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id g1MIZSm15348; Fri, 22 Feb 2002 10:35:28 -0800 Date: Fri, 22 Feb 2002 10:35:28 -0800 From: Brooks Davis To: Robert Watson Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: changes to rc.diskless* Message-ID: <20020222103528.A15071@Odin.AC.HMC.Edu> References: <20020222095225.A6604@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="+HP7ph2BbKc20aGI" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from rwatson@FreeBSD.ORG on Fri, Feb 22, 2002 at 01:23:12PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --+HP7ph2BbKc20aGI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 22, 2002 at 01:23:12PM -0500, Robert Watson wrote: >=20 > One of the problems I have with a similar configuration is that the file > system checker never runs for local filesystems mounted on writable disks= .=20 > I tend to mount everything nfs and mfs, except for a scratch drive and > swap, which are from the local hard disk. Hmm, that's odd. They are definatly getting fsck'd on my test machine. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --+HP7ph2BbKc20aGI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8do9vXY6L6fI4GtQRAtzgAJ48evy06gEhwkkJ9kCVVx9seGDTnACeOGCn ma3bB33oePqrstk5ayYIZSg= =ZjhL -----END PGP SIGNATURE----- --+HP7ph2BbKc20aGI-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 10:36:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from h132-197-179-27.gte.com (h132-197-179-27.gte.com [132.197.179.27]) by hub.freebsd.org (Postfix) with ESMTP id E3A2137B405 for ; Fri, 22 Feb 2002 10:36:30 -0800 (PST) Received: from kanpc.gte.com (localhost [127.0.0.1]) by h132-197-179-27.gte.com (8.12.2/8.12.2) with SMTP id g1MIaTJR006951; Fri, 22 Feb 2002 13:36:29 -0500 (EST) (envelope-from ak03@gte.com) Date: Fri, 22 Feb 2002 13:36:29 -0500 From: Alexander Kabaev To: "Thomas E. Zander" Cc: current@FreeBSD.ORG Subject: Re: Recent USB problems Message-Id: <20020222133629.15316a9f.ak03@gte.com> In-Reply-To: <20020222181428.GA8774@f113.hadiko.de> References: <3C6F6F85.4050300@gmx.net> <20020222181428.GA8774@f113.hadiko.de> Organization: Verizon Data Services X-Mailer: Sylpheed version 0.7.2claws1 (GTK+ 1.2.10; i386--freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Sorry, no hint by my side, but I can report exactly the same problem > on an Athlon-C System equipped with a VIA-KT133A chipset. > (actually it has the same USB controller, so it was expectable) > > Riggs I am seeing the same symptoms while using Microsoft USB mouse with KT133A-based computer. In my case, initial probe for ums, uhid and then ugen fails. This is not consistent, though. Sometimes, probe will report failing ums attach, sometimes it will not even detect device as mouse and will start probing uhid or even ugen instead. Later in the boot process, right after the "Waiting for SCSI messages to settle" message, ums gets probed again and this time it attaches and works flawlessly 100% of the time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 10:56:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com [194.25.134.18]) by hub.freebsd.org (Postfix) with ESMTP id D77EC37B404 for ; Fri, 22 Feb 2002 10:56:29 -0800 (PST) Received: from fwd06.sul.t-online.de by mailout04.sul.t-online.com with smtp id 16eKn4-0007IP-03; Fri, 22 Feb 2002 19:51:30 +0100 Received: from pc-micha.mc.hp.com (320021761316-0001@[80.131.76.181]) by fmrl06.sul.t-online.com with esmtp id 16eKmv-0UIg8OC; Fri, 22 Feb 2002 19:51:21 +0100 Received: from gmx.net (michaelc@localhost [127.0.0.1]) by pc-micha.mc.hp.com (8.11.6/8.11.0) with ESMTP id g1MIpLQ53097; Fri, 22 Feb 2002 19:51:21 +0100 (MET) (envelope-from michael_class@gmx.net) Message-ID: <3C769328.1090908@gmx.net> Date: Fri, 22 Feb 2002 19:51:20 +0100 From: Michael Class User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.8) Gecko/20020206 X-Accept-Language: en-us MIME-Version: 1.0 To: Alexander Kabaev Cc: current@freebsd.org Subject: Re: Recent USB problems References: <3C6F6F85.4050300@gmx.net> <20020222181428.GA8774@f113.hadiko.de> <20020222133629.15316a9f.ak03@gte.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Sender: 320021761316-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, with current of yesterday everything seems to be ok for me again. But I do not see any reason for this (code has not changed inbetween). Michael Alexander Kabaev wrote: >>Sorry, no hint by my side, but I can report exactly the same problem >>on an Athlon-C System equipped with a VIA-KT133A chipset. >>(actually it has the same USB controller, so it was expectable) >> >>Riggs >> > I am seeing the same symptoms while using Microsoft USB mouse with >KT133A-based computer. In my case, initial probe for ums, uhid and then >ugen fails. This is not consistent, though. Sometimes, probe will report >failing ums attach, sometimes it will not even detect device as mouse >and will start probing uhid or even ugen instead. Later in the boot >process, right after the "Waiting for SCSI messages to settle" message, >ums gets probed again and this time it attaches and works flawlessly >100% of the time. > >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 Feb 22 11:13: 8 2002 Delivered-To: freebsd-current@freebsd.org Received: from k6.locore.ca (k6.locore.ca [198.96.117.170]) by hub.freebsd.org (Postfix) with ESMTP id 85B1337B400; Fri, 22 Feb 2002 11:13:04 -0800 (PST) Received: (from jake@localhost) by k6.locore.ca (8.11.6/8.11.6) id g1MJDN227797; Fri, 22 Feb 2002 14:13:23 -0500 (EST) (envelope-from jake) Date: Fri, 22 Feb 2002 14:13:22 -0500 From: Jake Burkholder To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: changes to rc.diskless* Message-ID: <20020222141322.A27577@locore.ca> References: <20020221200050.A78243@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020221200050.A78243@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Thu, Feb 21, 2002 at 08:00:51PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Apparently, On Thu, Feb 21, 2002 at 08:00:51PM -0800, David O'Brien said words to the effect of; > The existing very bazaar and local policy in rc.diskless1 is Just Wrong; > and looks like no other Unix diskless configuration I've ever seen. I > plan on committing this patch to negate this. Yay! > > The use of an MFS /var should also be settable. Otherwise installing > ports(packages) is just a total PITA. > > > Index: rc.diskless2 > =================================================================== > RCS file: /home/ncvs/src/etc/rc.diskless2,v > retrieving revision 1.15 > diff -u -r1.15 rc.diskless2 > --- rc.diskless2 26 Dec 2001 17:18:39 -0000 1.15 > +++ rc.diskless2 22 Feb 2002 03:56:18 -0000 > @@ -56,7 +56,7 @@ > fi > > echo "+++ mount_md of /var" > -mount_md ${varsize:=65536} /var 1 > +mount_md ${varsize:=32m} /var 1 One problem with making the mds so big is that it uses type malloc which afaict uses malloc(9) to get the backing store. This was the point of the M_SHORTWAIT patch posted a while ago, if you ask for too much with M_WAITOK you might go to sleep and never be woken up. It might be better to use type vnode with file or swap based backing store. sparc64 machines tend to have more ram than older pcs that this might also be used on :) my $0.02. Jake > > echo "+++ populate /var using /etc/mtree/BSD.var.dist" > /usr/sbin/mtree -deU -f /etc/mtree/BSD.var.dist -p /var > @@ -83,7 +83,7 @@ > # so if /var/tmp == /tmp, then you don't get a vi.recover. > # > if [ ! -h /tmp ]; then > - mount_md ${tmpsize:=20480} /tmp 2 > + mount_md ${tmpsize:=64m} /tmp 2 > chmod 01777 /tmp > fi > > > 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 Feb 22 11:17:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from h132-197-179-27.gte.com (h132-197-179-27.gte.com [132.197.179.27]) by hub.freebsd.org (Postfix) with ESMTP id 7DF8037B421 for ; Fri, 22 Feb 2002 11:17:08 -0800 (PST) Received: from kanpc.gte.com (localhost [127.0.0.1]) by h132-197-179-27.gte.com (8.12.2/8.12.2) with SMTP id g1MJH6JR007357; Fri, 22 Feb 2002 14:17:06 -0500 (EST) (envelope-from ak03@gte.com) Date: Fri, 22 Feb 2002 14:17:06 -0500 From: Alexander Kabaev To: Michael Class Cc: current@freebsd.org Subject: Re: Recent USB problems Message-Id: <20020222141706.0dbbcda3.ak03@gte.com> In-Reply-To: <3C769328.1090908@gmx.net> References: <3C6F6F85.4050300@gmx.net> <20020222181428.GA8774@f113.hadiko.de> <20020222133629.15316a9f.ak03@gte.com> <3C769328.1090908@gmx.net> Organization: Verizon Data Services X-Mailer: Sylpheed version 0.7.2claws1 (GTK+ 1.2.10; i386--freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I had no problem with kernel from February 14, but failed ums probes are happening very consistently with kernel from Feb 18. Kernels from dates earlier than Feb 14 failed to attach USB mouse most of the time but sometimes misteriously managed to work. No configuration was changing between successfull and unsuccessful boots, and there was no pattern whatsoever to hint why was that happening. By the way, the problem is related to the ums driver only, apparently. While I am having problems with the mouse, my USB scanner works absolutely reliably. > with current of yesterday everything seems to be ok for me again. But > I do not see any reason for this (code has not changed inbetween). I > will upgrade today and To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 11:20:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 2BC3337B404 for ; Fri, 22 Feb 2002 11:20:10 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020222192009.BWDL1147.rwcrmhc52.attbi.com@InterJet.elischer.org>; Fri, 22 Feb 2002 19:20:09 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA74281; Fri, 22 Feb 2002 11:01:14 -0800 (PST) Date: Fri, 22 Feb 2002 11:01:13 -0800 (PST) From: Julian Elischer To: Beech Rintoul Cc: freebsd-current@freebsd.org Subject: Re: Build Failure (libkvm) In-Reply-To: <20020222170928.9D2EFAA@nebula.anchoragerescue.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG the probkem is that phk didn't test a buildworld before making the following change to proc.h: ---------------------------- revision 1.204 date: 2002/02/22 13:32:01; author: phk; state: Exp; lines: +1 -1 Convert p->p_runtime and PCPU(switchtime) to bintime format. ---------------------------- Any change to proc.h needs an appropriate change to /usr/src/lib/libkvm/kvm_proc.c to convert the new value to th old stable type. (we will continue to export the old type so that ps doesn't need to be recompiled all the time). Slightly humourous because this is EXACTLY the same breakage (same file , about 10 lines away) that he was ragging me about doing last week :-) On Fri, 22 Feb 2002, Beech Rintoul wrote: > Last night's build for -current failed with the following: > > mkdep -f .depend -a -DLIBC_SCCS -I/usr/src/lib/libkvm > /usr/src/lib/libkvm/kvm.c /usr/src/lib/libkvm/kvm_i386.c > /usr/src/lib/libkvm/kvm_file.c /usr/src/lib/libkvm/kvm_getloadavg.c > /usr/src/lib/libkvm/kvm_getswapinfo.c /usr/src/lib/libkvm/kvm_proc.c > cd /usr/src/lib/libkvm; make _EXTRADEPEND > cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm.c > -o kvm.o > cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c > /usr/src/lib/libkvm/kvm_i386.c -o kvm_i386.o > cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c > /usr/src/lib/libkvm/kvm_file.c -o kvm_file.o > cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c > /usr/src/lib/libkvm/kvm_getloadavg.c -o kvm_getloadavg.o > cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c > /usr/src/lib/libkvm/kvm_getswapinfo.c -o kvm_getswapinfo.o > cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c > /usr/src/lib/libkvm/kvm_proc.c -o kvm_proc.o > /usr/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist': > /usr/src/lib/libkvm/kvm_proc.c:316: incompatible types in assignment > *** Error code 1 > > Stop in /usr/src/lib/libkvm. > *** Error code 1 > > Tried all the usual, rm -R /usr/obj, fresh cvsup etc.... > > Beech > -- > ------------------------------------------------------------------- > Beech Rintoul - IT Manager - Instructor - akbeech@anchoragerescue.org > /"\ ASCII Ribbon Campaign | Anchorage Gospel Rescue Mission > \ / - NO HTML/RTF in e-mail | P.O. Box 230510 > X - NO Word docs in e-mail | Anchorage, AK 99523-0510 > / \ ----------------------------------------------------------------- > > > > > > > > > > > > > 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 Feb 22 11:20:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 447B737B405 for ; Fri, 22 Feb 2002 11:20:20 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020222192019.BWGN1147.rwcrmhc52.attbi.com@InterJet.elischer.org>; Fri, 22 Feb 2002 19:20:19 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA74297; Fri, 22 Feb 2002 11:05:39 -0800 (PST) Date: Fri, 22 Feb 2002 11:05:38 -0800 (PST) From: Julian Elischer To: John Hay Cc: Beech Rintoul , David Wolfskill , freebsd-current@FreeBSD.ORG Subject: Re: Build Failure (libkvm) In-Reply-To: <200202221822.g1MIMrW40266@zibbi.icomtek.csir.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 22 Feb 2002, John Hay wrote: > > > > > > >Date: Fri, 22 Feb 2002 08:09:28 -0900 > > > > > > > >Last night's build for -current failed with the following: > > > > > > I got -CURRENT built today without problem. Recent CVSup history: > > > > > (snip history) > > > > > > Might try updating again.... > > > > Already did that. The update was about 15 minutes prior to that last build > > attempt. Interesting, the last change to that file was about 2 weeks ago and > > I have done several builds since then. I'm clueless as to why it picked today > > to fail rather than immediately following the commit. > > The type of p_runtime in sys/proc.h changed today, but ki_runtime in > sys/user.h hasn't changed yet. Or maybe it shouldn't change and there > should rather be a conversion? Who knows. :-) phk? > it must not change in ki_runtime (unless it's binary compatible on all platforms). the aim of ki_runtime is to keep exporting a STABLE interface (i.e. one that doesn't change). a simple conversion in libkvm is enough. I'll be going through that file with a rototiller in a few months anyhow. > John > -- > John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 11:21:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from outboundx.mv.meer.net (outboundx.mv.meer.net [209.157.152.12]) by hub.freebsd.org (Postfix) with ESMTP id B896D37B400; Fri, 22 Feb 2002 11:21:07 -0800 (PST) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by outboundx.mv.meer.net (8.11.6/8.11.6) with ESMTP id g1MJL3s97593; Fri, 22 Feb 2002 11:21:03 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from neville-neil.com ([209.157.133.226]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id LAA704177; Fri, 22 Feb 2002 11:20:41 -0800 (PST) Message-Id: <200202221920.LAA704177@meer.meer.net> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: freebsd-smp@freebsd.org, freebsd-current@freebsd.org Subject: TWiki as promised... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 Feb 2002 11:20:40 -0800 From: "George V. Neville-Neil" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Folks, In an attempt to help out with coordination on projects I've put up a TWiki (see www.twiki.org for info on TWiki) site on my web server. As a guest you can read but not update, you have to register to update content. There is a Freebsd web and it has 1 topic which is the SMP project. I have put the entire page from http://www.freebsd.org/smp/ into TWiki. The local references on that page (i.e. the href:./foo.txt stuff) are now external references but we could fix that. A few notes might be helpful. 1) Why did you do this? TWiki (and Wiki's in general) allow people to easily update centralized web content without haveing to have real logins on the web serving computer. This makes keeping things like worklists trivial. The language used by TWiki is NOT HTML but a clever subset that requires a lot less work. For instance a table looks like this: | Task | Responsible | Date| | Task 1| GeorgeNevilleNeil| 2 March 2002 | This will get translated into a nice, simple HTML table by the TWiki stuff. 2) What do I have to do to use this? To read the stuff just go to: http://www.neville-neil.com/twiki/bin/view/Main/WebHome and click on the Freebsd label. To update you must register. Go to the main page and register yourself. The passwords are encrypted but I WOULD NOT use my system password here. Actually, I'd like it if you didn't use any important password there, I don't want to be responsible for y'all in that way. 3) How do I learn more about TWiki? Go to www.twiki.org In particular check out: http://TWiki.org/cgi-bin/view/Main/TWikiPresentation s to see why and how we should be using TWiki. ONE FINAL NOTE. TWiki uses WordsLikeThis to denote automatic links. This means that FreeBSD is an automatic link. If you MUST type FreeBSD then put a before it on the page. I'm working with the author to come up with a way to make it so that FreeBSD never gets converted within our TWiki Web. Later, George -- George V. Neville-Neil gnn@neville-neil.com NIC:GN82 "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 13:40:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id 9A03737B416; Fri, 22 Feb 2002 13:40:09 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020222214008.GCBK1214.rwcrmhc54.attbi.com@InterJet.elischer.org>; Fri, 22 Feb 2002 21:40:08 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA74908; Fri, 22 Feb 2002 13:23:33 -0800 (PST) Date: Fri, 22 Feb 2002 13:23:32 -0800 (PST) From: Julian Elischer To: "George V. Neville-Neil" Cc: freebsd-smp@freebsd.org, freebsd-current@freebsd.org Subject: Re: TWiki as promised... In-Reply-To: <200202221920.LAA704177@meer.meer.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hmm cute I added a comment as an experiment.. really quite easy to use after the first 5 minute learning curve. On Fri, 22 Feb 2002, George V. Neville-Neil wrote: > 2) What do I have to do to use this? > > To read the stuff just go to: > > http://www.neville-neil.com/twiki/bin/view/Main/WebHome > > and click on the Freebsd label. > > To update you must register. Go to the main page and register yourself. > The passwords are encrypted but I WOULD NOT use my system password > here. Actually, I'd like it if you didn't use any important password there, I > don't want to be responsible for y'all in that way. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 14: 2:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from outboundx.mv.meer.net (outboundx.mv.meer.net [209.157.152.12]) by hub.freebsd.org (Postfix) with ESMTP id A754537B416; Fri, 22 Feb 2002 14:02:09 -0800 (PST) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by outboundx.mv.meer.net (8.11.6/8.11.6) with ESMTP id g1MM25s01360; Fri, 22 Feb 2002 14:02:05 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from neville-neil.com ([209.157.133.226]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id OAA642995; Fri, 22 Feb 2002 14:01:30 -0800 (PST) Message-Id: <200202222201.OAA642995@meer.meer.net> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Julian Elischer Cc: freebsd-smp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: TWiki as promised... In-Reply-To: Message from Julian Elischer of "Fri, 22 Feb 2002 13:23:32 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 Feb 2002 14:01:30 -0800 From: "George V. Neville-Neil" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Hmm cute > > I added a comment as an experiment.. > really quite easy to use after the first 5 minute learning curve. > Well, you're the only one to use it thus far so let's see what others think as well. Thanks for checking it out though. Later, George -- George V. Neville-Neil gnn@neville-neil.com NIC:GN82 "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 14:25:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D9BD137B417; Fri, 22 Feb 2002 14:25:10 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 91B445343; Fri, 22 Feb 2002 23:25:08 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: arch@freebsd.org Subject: OpenPAM From: Dag-Erling Smorgrav Date: 22 Feb 2002 23:25:07 +0100 Message-ID: Lines: 15 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG OpenPAM Cantaloupe is now available at along with an integration patch for FreeBSD-CURRENT. Since the two previous releases have solicited absolutely no feedback other than to point out a broken link on the project's web page, I assume that everybody is happy with the code, and that nobody will object when I import it into CVS and ditch Linux-PAM later this weekend. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 14:28:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id A804837B43D; Fri, 22 Feb 2002 14:28:05 -0800 (PST) Received: from user-1120bjg.dsl.mindspring.com ([66.32.46.112] helo=europa2) by blount.mail.mindspring.net with smtp (Exim 3.33 #1) id 16eOAe-00023H-00; Fri, 22 Feb 2002 17:28:04 -0500 Message-Id: <3.0.6.32.20020222172614.00dabac0@imatowns.com> X-Sender: ggombert@imatowns.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 22 Feb 2002 17:26:14 -0500 To: John Baldwin , David Wolfskill From: Glenn Gombert Subject: Re: Install World fails in -Current Cc: current@FreeBSD.ORG In-Reply-To: References: <200202221338.g1MDceE75453@bunrab.catwhisker.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG All I did was to add a 'smmsp' user in via the sysisntall utility, ran 'installworld/mergemaster' again and things worked fine, adding a not to the Updating file might be a good idea for others thought :) At 11:35 AM 2/22/2002 -0500, John Baldwin wrote: > >On 22-Feb-02 David Wolfskill wrote: >>>Date: Fri, 22 Feb 2002 08:33:01 -0500 >>>From: Glenn Gombert >> >>>I have tried to re-cvsup and a clean rebuild the alst couple of days, and I >>>keep getting this error when I try and do an 'installworld' ..after a clean >>>build...does anyone know what might be causing this?? >> >>>... >>>........ >>>mtree -deU -f /usr/src/etc/mtree/BSD.var -p /var >>>mtree: line 67: unknown user smmsp >> >> >> Sounds like a botched (or not run) "mergemaster" execution: > >Sort of. The problem is we have added a new user that installworld depends on. >Imagine a 4.x to 5.0 upgrade right now. 4.x doesn't have this user IIRC, and >you are supposed to run installworld before mergemaster. Sounds like a nice >catch 22 to me. :-/ > >-- > >John Baldwin <>< http://www.FreeBSD.org/~jhb/ >"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > Glenn Gombert ggombert@imatowns.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 14:32:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id 2F9F937B400; Fri, 22 Feb 2002 14:32:24 -0800 (PST) Received: from user-1120bjg.dsl.mindspring.com ([66.32.46.112] helo=europa2) by blount.mail.mindspring.net with smtp (Exim 3.33 #1) id 16eOEp-0006FE-00; Fri, 22 Feb 2002 17:32:23 -0500 Message-Id: <3.0.6.32.20020222173051.00dabac0@imatowns.com> X-Sender: ggombert@imatowns.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 22 Feb 2002 17:30:51 -0500 To: obrien@freebsd.org, current@freebsd.org From: Glenn Gombert Subject: Re: changes to rc.diskless* In-Reply-To: <20020221200050.A78243@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The rc.diskless1/2 scripts *do* need some work, I finally got my diskless kernel booting (with help from Matt and Robert Watson) but it was a lot of 'trial and error' to do so"...but well worthwhile to boot diskless (test/experimental) kernels for developmental purposes ..... At 08:00 PM 2/21/2002 -0800, David O'Brien wrote: >The existing very bazaar and local policy in rc.diskless1 is Just Wrong; >and looks like no other Unix diskless configuration I've ever seen. I >plan on committing this patch to negate this. > >The use of an MFS /var should also be settable. Otherwise installing >ports(packages) is just a total PITA. > > >Index: rc.diskless1 >=================================================================== >RCS file: /home/ncvs/src/etc/rc.diskless1,v >retrieving revision 1.13 >diff -u -r1.13 rc.diskless1 >--- rc.diskless1 17 Jan 2002 00:10:28 -0000 1.13 >+++ rc.diskless1 22 Feb 2002 03:52:41 -0000 >@@ -92,13 +92,14 @@ > done > echo "Interface ${bootp_ifc} IP-Address ${bootp_ipa} Broadcast ${bootp_ipbca}" > >+if [ -d /conf/default/etc ]; then >+ mount_md 4096 /etc 0 >+ chkerr $? "MFS mount on /etc" >+ /bin/chmod 755 /etc > >-mount_md 4096 /etc 0 >-chkerr $? "MFS mount on /etc" >-/bin/chmod 755 /etc >- >-/bin/cp -Rp /conf/default/etc/* /etc >-chkerr $? "cp /conf/default/etc to /etc MFS" >+ /bin/cp -Rp /conf/default/etc/* /etc >+ chkerr $? "cp /conf/default/etc to /etc MFS" >+fi > > # Allow for override files to replace files in /etc. Use /conf/*/etc to find > # the override files. First choice is default files that # always override, >@@ -113,6 +114,11 @@ > cp -Rp /conf/${i}/etc/* /etc > fi > done >+ >+# Since we are starting with a very fresh /etc on an MFS: >+if [ -d /conf/default/etc ]; then >+ newaliases >+if > > # Tell /etc/rc to run the specified script after it does its mounts but > # before it does anything else. >Index: rc.diskless2 >=================================================================== >RCS file: /home/ncvs/src/etc/rc.diskless2,v >retrieving revision 1.15 >diff -u -r1.15 rc.diskless2 >--- rc.diskless2 26 Dec 2001 17:18:39 -0000 1.15 >+++ rc.diskless2 22 Feb 2002 03:56:18 -0000 >@@ -56,7 +56,7 @@ > fi > > echo "+++ mount_md of /var" >-mount_md ${varsize:=65536} /var 1 >+mount_md ${varsize:=32m} /var 1 > > echo "+++ populate /var using /etc/mtree/BSD.var.dist" > /usr/sbin/mtree -deU -f /etc/mtree/BSD.var.dist -p /var >@@ -83,7 +83,7 @@ > # so if /var/tmp == /tmp, then you don't get a vi.recover. > # > if [ ! -h /tmp ]; then >- mount_md ${tmpsize:=20480} /tmp 2 >+ mount_md ${tmpsize:=64m} /tmp 2 > chmod 01777 /tmp > fi > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > Glenn Gombert ggombert@imatowns.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 15:33:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from pump3.york.ac.uk (pump3.york.ac.uk [144.32.128.131]) by hub.freebsd.org (Postfix) with ESMTP id 1B7A237B400 for ; Fri, 22 Feb 2002 15:33:49 -0800 (PST) Received: from ury.york.ac.uk (ury.york.ac.uk [144.32.108.81]) by pump3.york.ac.uk (8.10.2/8.10.2) with ESMTP id g1MNXlN25799; Fri, 22 Feb 2002 23:33:47 GMT Received: from localhost (gavin@localhost) by ury.york.ac.uk (8.11.6/8.11.3) with ESMTP id g1MNXlI56146; Fri, 22 Feb 2002 23:33:47 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: ury.york.ac.uk: gavin owned process doing -bs Date: Fri, 22 Feb 2002 23:33:46 +0000 (GMT) From: Gavin Atkinson To: Glenn Gombert Cc: Subject: Re: Install World fails in -Current In-Reply-To: <3.0.6.32.20020222172614.00dabac0@imatowns.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 22 Feb 2002, Glenn Gombert wrote: > All I did was to add a 'smmsp' user in via the sysisntall utility, ran > 'installworld/mergemaster' again and things worked fine, adding a not to > the Updating file might be a good idea for others thought :) Section 19.4.3 of the FreeBSD handbook does mention this type of problem, however only suggests comparing /etc/group with the new file. "There have been occasions when the installation part of ``make world'' has expected certain usernames or groups to exist. When performing an upgrade it is likely that these groups did not exist. This caused problems when upgrading." It might be worth including explicit mention about checking changes in master.passwd as well. I'll submit a patch tomorrow if nobody beats me to it... Gavin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 15:38:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id DA4AE37B402 for ; Fri, 22 Feb 2002 15:38:48 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g1MNcZH73615; Fri, 22 Feb 2002 15:38:35 -0800 (PST) (envelope-from obrien) Date: Fri, 22 Feb 2002 15:38:34 -0800 From: "David O'Brien" To: Jake Burkholder Cc: current@FreeBSD.ORG Subject: Re: changes to rc.diskless* Message-ID: <20020222153834.A67327@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20020221200050.A78243@dragon.nuxi.com> <20020222141322.A27577@locore.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020222141322.A27577@locore.ca>; from jake@locore.ca on Fri, Feb 22, 2002 at 02:13:22PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Feb 22, 2002 at 02:13:22PM -0500, Jake Burkholder wrote: > > echo "+++ mount_md of /var" > > -mount_md ${varsize:=65536} /var 1 > > +mount_md ${varsize:=32m} /var 1 > > One problem with making the mds so big is that it uses type malloc > which afaict uses malloc(9) to get the backing store. I only changed the syntax for the size to something easier to read, but not the size itself. > much with M_WAITOK you might go to sleep and never be woken up. It > might be better to use type vnode with file or swap based backing > store. No opinion :-) > sparc64 machines tend to have more ram than older pcs that > this might also be used on :) one can set varsize=2m in /etc/rc.conf is they need to. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 17:39:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id A7BA837B402 for ; Fri, 22 Feb 2002 17:39:22 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 878A25341; Sat, 23 Feb 2002 02:39:19 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: David Wolfskill Cc: current@FreeBSD.ORG, ggombert@imatowns.com Subject: Re: Install World fails in -Current References: <200202221338.g1MDceE75453@bunrab.catwhisker.org> From: Dag-Erling Smorgrav Date: 23 Feb 2002 02:39:18 +0100 In-Reply-To: <200202221338.g1MDceE75453@bunrab.catwhisker.org> Message-ID: Lines: 10 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Wolfskill writes: > Sounds like a botched (or not run) "mergemaster" execution: No - mergemaster will croak because it runs mtree to build its temp directory, so if you're trying to update a pre-smmsp system you have to add the smmsp user and group manually. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 19:25: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id 225BB37B400 for ; Fri, 22 Feb 2002 19:25:06 -0800 (PST) Received: (qmail 19285 invoked from network); 23 Feb 2002 03:25:04 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.137.227]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 23 Feb 2002 03:25:04 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 22 Feb 2002 22:25:03 -0500 (EST) From: John Baldwin To: Dag-Erling Smorgrav Subject: Re: Install World fails in -Current Cc: ggombert@imatowns.com, current@FreeBSD.ORG, David Wolfskill Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 23-Feb-02 Dag-Erling Smorgrav wrote: > David Wolfskill writes: >> Sounds like a botched (or not run) "mergemaster" execution: > > No - mergemaster will croak because it runs mtree to build its temp > directory, so if you're trying to update a pre-smmsp system you have > to add the smmsp user and group manually. I think this is a bug but can't think of a clean way to work around it. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 20:38:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail12.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with ESMTP id 00DD637B405 for ; Fri, 22 Feb 2002 20:38:08 -0800 (PST) Received: (qmail 32203 invoked from network); 23 Feb 2002 04:38:07 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.137.227]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 23 Feb 2002 04:38:07 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 22 Feb 2002 23:38:07 -0500 (EST) From: John Baldwin To: dillon@FreeBSD.org Subject: First (easy) td_ucred patch Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm currently testing the following patch whcih is a subset of the td_ucred changes. It involves no API changes, but only contains 2 basic changes: 1) We still need Giant when doing the crhold() to set td_ucred in cred_update_thread(). This is an old bug that is my fault. I knew that PROC_LOCK was sufficient yet which was my reason for not using td_ucred. However, we could still be derferencing a stale p_ucred and doing very bad things, so this needs to be fixed until p_ucred is fully protected by the PROC_LOCK. This also means that td_ucred is now safe to use. As such: 2) All the "easy" p->p_ucred -> td->td_ucred changes that don't involve the changes to API's such as suser() and p_canfoo(). The next patch in this series will most likely be the suser() API change. http://www.FreeBSD.org/~jhb/patches/ucred.patch -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 20:50:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-10.dsl.lsan03.pacbell.net [64.169.107.10]) by hub.freebsd.org (Postfix) with ESMTP id 207FE37B400; Fri, 22 Feb 2002 20:50:17 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A7ED666C32; Fri, 22 Feb 2002 20:50:16 -0800 (PST) Date: Fri, 22 Feb 2002 20:50:16 -0800 From: Kris Kennaway To: John Baldwin Cc: current@FreeBSD.org, msmith@FreeBSD.org Subject: Re: device figlet for the kernel Message-ID: <20020222205016.A19371@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from jhb@FreeBSD.org on Fri, Feb 22, 2002 at 05:17:05AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 22, 2002 at 05:17:05AM -0500, John Baldwin wrote: > Currently figlet isn't a kernel module, but one could make it so without = too > much additional work. To play with this, first download and apply the pa= tch at >=20 > http://www.FreeBSD.org/~jhb/patches/figlet.patch I think this should be committed ASAP. Kris --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8dx+IWry0BWjoQKURAhAZAJ0e/W/fE+4dKr1fhhMOF/ZEt3lgxwCgiHYd Swsu4mlVlDc9m/D70LI2C7g= =q3IS -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 21: 0:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id CAB7137B405 for ; Fri, 22 Feb 2002 21:00:33 -0800 (PST) Received: (qmail 16545 invoked from network); 23 Feb 2002 05:00:32 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.137.227]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 23 Feb 2002 05:00:32 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020222205016.A19371@xor.obsecurity.org> Date: Sat, 23 Feb 2002 00:00:32 -0500 (EST) From: John Baldwin To: Kris Kennaway Subject: Re: device figlet for the kernel Cc: msmith@FreeBSD.org, current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 23-Feb-02 Kris Kennaway wrote: > On Fri, Feb 22, 2002 at 05:17:05AM -0500, John Baldwin wrote: > >> Currently figlet isn't a kernel module, but one could make it so without too >> much additional work. To play with this, first download and apply the patch >> at >> >> http://www.FreeBSD.org/~jhb/patches/figlet.patch > > I think this should be committed ASAP. Well, the supprot for kernel console filters needs to be fleshed out a bit more so that figlet could be a KLD before it would really be worth considering. Also, a better method of sending commands to a filter is needed. > Kris -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 21: 0:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id 923F737B41A for ; Fri, 22 Feb 2002 21:00:36 -0800 (PST) Received: (qmail 16847 invoked from network); 23 Feb 2002 05:00:35 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.137.227]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 23 Feb 2002 05:00:35 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 23 Feb 2002 00:00:35 -0500 (EST) From: John Baldwin To: John Baldwin Subject: RE: First (easy) td_ucred patch Cc: current@FreeBSD.org, dillon@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 23-Feb-02 John Baldwin wrote: > I'm currently testing the following patch whcih is a subset of the td_ucred > changes. It involves no API changes, but only contains 2 basic changes: > > 1) We still need Giant when doing the crhold() to set td_ucred in > cred_update_thread(). This is an old bug that is my fault. I knew that > PROC_LOCK was sufficient yet which was my reason for not using td_ucred. > However, we could still be derferencing a stale p_ucred and doing very bad > things, so this needs to be fixed until p_ucred is fully protected by the > PROC_LOCK. This also means that td_ucred is now safe to use. As such: > > 2) All the "easy" p->p_ucred -> td->td_ucred changes that don't involve the > changes to API's such as suser() and p_canfoo(). The next patch in this > series will most likely be the suser() API change. > > http://www.FreeBSD.org/~jhb/patches/ucred.patch To apply this patch, use -p6 like so: cd work/my/kernel/tree/sys patch -p6 < path/to/patch/file/ucred.patch -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 21:35: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id BAC0537B400; Fri, 22 Feb 2002 21:34:55 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1N5Ytr34236; Fri, 22 Feb 2002 21:34:55 -0800 (PST) (envelope-from dillon) Date: Fri, 22 Feb 2002 21:34:55 -0800 (PST) From: Matthew Dillon Message-Id: <200202230534.g1N5Ytr34236@apollo.backplane.com> To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: RE: First (easy) td_ucred patch References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :> I'm currently testing the following patch whcih is a subset of the td_ucred :> changes. It involves no API changes, but only contains 2 basic changes: :> :> 1) We still need Giant when doing the crhold() to set td_ucred in :> cred_update_thread(). This is an old bug that is my fault. I knew that :> PROC_LOCK was sufficient yet which was my reason for not using td_ucred. :> However, we could still be derferencing a stale p_ucred and doing very bad :> things, so this needs to be fixed until p_ucred is fully protected by the :> PROC_LOCK. This also means that td_ucred is now safe to use. As such: :> :> 2) All the "easy" p->p_ucred -> td->td_ucred changes that don't involve the :> changes to API's such as suser() and p_canfoo(). The next patch in this :> series will most likely be the suser() API change. :> :> http://www.FreeBSD.org/~jhb/patches/ucred.patch Well, I have some issues with this patch. It seems to include a number of structural changes ranging from the removal of braces (syntactical changes) to straightforward but major flow changes such as found in getgroups(). Some of these changes, for example return()ing in the middle of a procedure, are highly dependant on the removal of Giant. goto's are questionable but replacing them with return()s in the middle of a procedure isn't too hot an idea either. * I do not think it is a good idea to mix these changes with the ucred changes, even if they appear to be straightforward. You are making a large number of changes to the system all at once. The changes should focus only on what is absolutely necessary in this round. Leave syntactical (cleanup?) to a later round. * I strongly, *strongly* disagree with the removal of Giant at this time, even in 'read-only' functions. I would much rather see a methodology whereby Giant is replaced with an instrumented Giant such as found in the patches I was working on. If you are really worried about the 10ns of call overhead I believe Peter has been interested in making the instrumentation optionable at compile time (and I am not against that provided it is done correctly). The reason I am strongly opposed to the removal of Giant is several fold: - Giant serves to mark where we were essentially single threading the kernel before and this will be important in understanding and tracking down bugs we find in the future. And make no mistake, there will be many. - Giant is going to be pushed down into many subsystems in coming months. It is highly likely that many hard-to-find bugs are going to come out of the woodwork, no matter how conservative we are or how well we believe we understand the code. Without instrumentation tracking down the less obvious bugs is going to be difficult. - It's a bad idea to second-guess the code, even if a piece of code looks like Giant can simply be removed (i.e. due to being a read-only function like getuid()). The removal of Giant creates all sorts of side effects, from something as simple as a difference in performance to something more complex such as creating memory sync points and removing (pseudo giant-enforced) atomicy that was previously depended upon. We are almost certainly going to face hard-to-find races in the code as Giant is unwound, even if we are extremely conservative in our commits. It's going to happen. The code was never designed for MP operation. Instrumenting Giant unconditionally at this early stage will make our jobs a whole lot easier. If you are completely against doing Giant instrumentation in your own patch sets then I would like both a head's up (like you just did) of patch sets you intend to commit to the main tree, and also permission to add Giant instrumentation in a secondary commit after you make the initial commit (which also means I would request that you not make code flow changes if at all possible). I think it's *that* important. I would much prefer that you do it yourself but if you won't I feel strongly enough about the issue to want to do it myself. --- on cred_update_thread() -- I suggested this same thing to Julian so I agree with adding Giant back in. Again, I would instrument it instead of just adding back in, i.e.: s = mtx_lock_giant(kern_giant_proc); PROC_LOCK(p); td->td_ucred = crhold(p->p_ucred); PROC_UNLOCK(p); mtx_unlock_giant(s); Instead of: mtx_lock(&Giant); PROC_LOCK(p); td->td_ucred = crhold(p->p_ucred); PROC_UNLOCK(p); mtx_unlock(&Giant); In anycase, if you are willing to either instrument Giant or allow me to then I am willing to do full reviews of reasonably-chunked patch sets (the URL you just posted is quite reasonably chunked BTW). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 21:56:51 2002 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 654) id 05E4E37B404; Fri, 22 Feb 2002 21:56:48 -0800 (PST) Date: Fri, 22 Feb 2002 21:56:47 -0800 From: Mike Smith To: current@freebsd.org Subject: HEADS UP: ACPI CA updated Message-ID: <20020222215647.A54975@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've finally updated the ACPI CA codebase with Intel's 20020214 drop (yes, I tagged it 0217, my bad). This is the first drop that Intel haven't asked me not to commit since the 20011120 version, so there are a large number of changes and bugfixes. See Intel's logs at http://developer.intel.com/technology/iapc/acpi for more details. There aren't many changes in the FreeBSD-specific code, this is just catching up with major improvements in the interpreter. As usual, please report any problems or success to the list. Regards, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 22: 8:46 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id B2AC437B400 for ; Fri, 22 Feb 2002 22:08:41 -0800 (PST) Received: (qmail 32010 invoked from network); 23 Feb 2002 06:08:39 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.137.227]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 23 Feb 2002 06:08:39 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200202230534.g1N5Ytr34236@apollo.backplane.com> Date: Sat, 23 Feb 2002 01:08:39 -0500 (EST) From: John Baldwin To: Matthew Dillon Subject: Re: RE: First (easy) td_ucred patch Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 23-Feb-02 Matthew Dillon wrote: >:> I'm currently testing the following patch whcih is a subset of the td_ucred >:> changes. It involves no API changes, but only contains 2 basic changes: >:> >:> 1) We still need Giant when doing the crhold() to set td_ucred in >:> cred_update_thread(). This is an old bug that is my fault. I knew that >:> PROC_LOCK was sufficient yet which was my reason for not using td_ucred. >:> However, we could still be derferencing a stale p_ucred and doing very >:> bad >:> things, so this needs to be fixed until p_ucred is fully protected by >:> the >:> PROC_LOCK. This also means that td_ucred is now safe to use. As such: >:> >:> 2) All the "easy" p->p_ucred -> td->td_ucred changes that don't involve the >:> changes to API's such as suser() and p_canfoo(). The next patch in this >:> series will most likely be the suser() API change. >:> >:> http://www.FreeBSD.org/~jhb/patches/ucred.patch > > Well, I have some issues with this patch. It seems to include > a number of structural changes ranging from the removal of braces > (syntactical changes) to straightforward but major flow changes such > as found in getgroups(). Some of these changes, for example return()ing > in the middle of a procedure, are highly dependant on the removal of > Giant. goto's are questionable but replacing them with return()s in > the middle of a procedure isn't too hot an idea either. It's how the code is going to look as the final rendition. It also restores the code more to its 4.x flow making a diff to see what actual changes SMPng made easier to read. > * I do not think it is a good idea to mix these changes with the > ucred changes, even if they appear to be straightforward. > You are making a large number of changes to the system all at once. > The changes should focus only on what is absolutely necessary in > this round. Leave syntactical (cleanup?) to a later round. They weren't committed separately from adding Giant to the functions when they went in. :) > * I strongly, *strongly* disagree with the removal of Giant at this > time, even in 'read-only' functions. I would much rather see a > methodology whereby Giant is replaced with an instrumented Giant > such as found in the patches I was working on. If you are really > worried about the 10ns of call overhead I believe Peter has been > interested in making the instrumentation optionable at compile > time (and I am not against that provided it is done correctly). I don't care about whatever time it takes to do teh check. I don't make decisions about debugging code based on clock cycles. Here are my concerns: - kern.giant.proc as you would have it now is far too broad. Most of the proc locking currently in the tree and in my work tree is not safe yet. This is because certain fields are only locked in certain places. For a field to be safe outside of Giant, it needs to be locked everywhere. You include both code that contains partially locked fields and fully locked fields under the same sysctl. This means I can't actually turn the sysctl on to do the testing safely, so I might as well just leave Giant in there rahter than bother with a useless sysctl. One solution might be to split ths sysctl up. Well then, how many are we going to have, one sysctl for each field in proc? This won't scale in my opinion. It may be useful for covering fields that aren't fully locked, but for stuff that is done, I don't think you need it. - How many various locking systems do syscalls like read() going call into? Are we going to eventually need to check 8, 10, or 16 sysctl's? Trying to keep all that straight will be a major pain. This is another reason I don't think they scale well. - We eventually have to go and remove all this stuff anyways. - As another note specific to td_ucred: there is no other lock that you are "covering up" for. It is a private per-thread pointer to a read-only structure. I can see needing to turn Giant back on around a lock done wrong, but there is no lock in this instance. We need to people to test stuff as it comes out from under Giant so we can find the bugs sooner rather than later, the current way these things work is far too coarse grained and I think I'll be spending more time figuring out how to split them up to make them useful and then figure out where they need to be acquired. For example, assuming I used kern.giant.proc.ucred for just the td_ucred stuff, since I've changed just about every VOP in the system, I now need to add instrumentation around every single syscall that might call a VOP, or that might call any of the other functions I changed. Maybe if you want SMPng to take 5 times as long... -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 22:35:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id EEF0737B400; Fri, 22 Feb 2002 22:35:37 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1N6ZbZ34600; Fri, 22 Feb 2002 22:35:37 -0800 (PST) (envelope-from dillon) Date: Fri, 22 Feb 2002 22:35:37 -0800 (PST) From: Matthew Dillon Message-Id: <200202230635.g1N6ZbZ34600@apollo.backplane.com> To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: RE: First (easy) td_ucred patch References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :> as found in getgroups(). Some of these changes, for example return()ing :> in the middle of a procedure, are highly dependant on the removal of :> Giant. goto's are questionable but replacing them with return()s in :> the middle of a procedure isn't too hot an idea either. : :It's how the code is going to look as the final rendition. It also restores :the code more to its 4.x flow making a diff to see what actual changes SMPng :made easier to read. This makes no sense whatsoever. We aren't trying to make the code look like 4.x. We are trying to make it MP safe. :- kern.giant.proc as you would have it now is far too broad. Most of the proc : locking currently in the tree and in my work tree is not safe yet. This is : because certain fields are only locked in certain places. For a field to be : safe outside of Giant, it needs to be locked everywhere. You include both : code that contains partially locked fields and fully locked fields under the : same sysctl. This means I can't actually turn the sysctl on to do the : testing safely, so I might as well just leave Giant in there rahter than : bother with a useless sysctl. One solution might be to split ths sysctl up. : Well then, how many are we going to have, one sysctl for each field in proc? : This won't scale in my opinion. It may be useful for covering fields that : aren't fully locked, but for stuff that is done, I don't think you need it. :- How many various locking systems do syscalls like read() going call into? : Are we going to eventually need to check 8, 10, or 16 sysctl's? Trying to : keep all that straight will be a major pain. This is another reason I don't : think they scale well. :- We eventually have to go and remove all this stuff anyways. :- As another note specific to td_ucred: there is no other lock that you are : "covering up" for. It is a private per-thread pointer to a read-only : structure. I can see needing to turn Giant back on around a lock done : wrong, but there is no lock in this instance. I don't think you quite understand the purpose of instrumenting Giant. You are synthesizing problems where none exist, and you are making assumptions that are simply not true. You are exaggerating the issues to ridiculous extremes. You seem hell bent on taking parts of PROC out from under Giant. Well, where's the documentation? In your head? How the hell are other people supposed to be able to work on the system when the only person who knows what is safe and what is not is you? One of the things Giant instrumentation gives us is the ability to show people, very clearly in the code, what we believe to be safe and what we believe not to be safe, or in beta, simply by changing the giant globals in kern_mutex.c. It allows other developers to see, very clearly, *EXACTLY* where we are in the Giant pushdown work. The way you are doing it nobody will know what the hell is going on except you! :We need to people to test stuff as it comes out from under Giant so we can find The instrumented Giant does not in any way prevent this from occuring. It does not in any way prevent you from finding bugs. :Maybe if you want SMPng to take 5 times as long... : I think it's going to take 5 times as long if you make mass commits from P4 with no way to at least partially turn off the MP functionality you added and we wind up with dozens of impossible-to-find bugs a year down the line. I think it is going to take 5 times as long if there is no clear documentation or indication in the code showing developers what is safe, what is under test, and what is not safe. What I am doing is trying to prevent that from happening. You are treating each subsystem separately and assuming that bugs will be found on a per-subsystem basis, regardless of the complexity of the interactions between subsystems. Well, I know better. When you have a dozen subsystems interacting in an MP system and you have a race or MP-related bug, good fucking luck find it! How long do you want it to take to get a stable 5.x release? Because the way you are going it isn't going to happen until we hit 5.3 or so. -Matt Matthew Dillon :John Baldwin <>< http://www.FreeBSD.org/~jhb/ :"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 22:40:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 18C5537B404 for ; Fri, 22 Feb 2002 22:40:14 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id E420BAE344; Fri, 22 Feb 2002 22:40:13 -0800 (PST) Date: Fri, 22 Feb 2002 22:40:13 -0800 From: Alfred Perlstein To: Mike Smith Cc: current@freebsd.org Subject: Re: HEADS UP: ACPI CA updated Message-ID: <20020223064013.GB80761@elvis.mu.org> References: <20020222215647.A54975@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020222215647.A54975@hub.freebsd.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Mike Smith [020222 21:56] wrote: > > I've finally updated the ACPI CA codebase with Intel's 20020214 drop > (yes, I tagged it 0217, my bad). Woo! Go Mike! -- -Alfred Perlstein [alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 23:40:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id 29DD037B402; Fri, 22 Feb 2002 23:40:16 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020223074015.TFGL1214.rwcrmhc54.attbi.com@InterJet.elischer.org>; Sat, 23 Feb 2002 07:40:15 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA77182; Fri, 22 Feb 2002 23:27:10 -0800 (PST) Date: Fri, 22 Feb 2002 23:27:09 -0800 (PST) From: Julian Elischer To: John Baldwin Cc: dillon@FreeBSD.org, current@FreeBSD.org Subject: Re: First (easy) td_ucred patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG please feel free to commit. If you break something so be it. I've been watching your P4 commits, and have not seen any obvious problems I assume that your "easy" changes are those you;ve been doing on P4. On Fri, 22 Feb 2002, John Baldwin wrote: > I'm currently testing the following patch whcih is a subset of the td_ucred > changes. It involves no API changes, but only contains 2 basic changes: > > 1) We still need Giant when doing the crhold() to set td_ucred in > cred_update_thread(). This is an old bug that is my fault. I knew that > PROC_LOCK was sufficient yet which was my reason for not using td_ucred. > However, we could still be derferencing a stale p_ucred and doing very bad > things, so this needs to be fixed until p_ucred is fully protected by the > PROC_LOCK. This also means that td_ucred is now safe to use. As such: > > 2) All the "easy" p->p_ucred -> td->td_ucred changes that don't involve the > changes to API's such as suser() and p_canfoo(). The next patch in this > series will most likely be the suser() API change. > > http://www.FreeBSD.org/~jhb/patches/ucred.patch > > -- > > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 22 23:40:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id A86B437B417; Fri, 22 Feb 2002 23:40:17 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020223074017.TFGU1214.rwcrmhc54.attbi.com@InterJet.elischer.org>; Sat, 23 Feb 2002 07:40:17 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA77184; Fri, 22 Feb 2002 23:28:58 -0800 (PST) Date: Fri, 22 Feb 2002 23:28:58 -0800 (PST) From: Julian Elischer To: John Baldwin Cc: current@FreeBSD.org, dillon@FreeBSD.org Subject: RE: First (easy) td_ucred patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I can't look at it till tomorrow. But I've been watching. I'd be surprised if anything broke with what I've seen. I'll look at it then if you haven;t commited by then. On Sat, 23 Feb 2002, John Baldwin wrote: > > On 23-Feb-02 John Baldwin wrote: > > I'm currently testing the following patch whcih is a subset of the td_ucred > > changes. It involves no API changes, but only contains 2 basic changes: > > > > 1) We still need Giant when doing the crhold() to set td_ucred in > > cred_update_thread(). This is an old bug that is my fault. I knew that > > PROC_LOCK was sufficient yet which was my reason for not using td_ucred. > > However, we could still be derferencing a stale p_ucred and doing very bad > > things, so this needs to be fixed until p_ucred is fully protected by the > > PROC_LOCK. This also means that td_ucred is now safe to use. As such: > > > > 2) All the "easy" p->p_ucred -> td->td_ucred changes that don't involve the > > changes to API's such as suser() and p_canfoo(). The next patch in this > > series will most likely be the suser() API change. > > > > http://www.FreeBSD.org/~jhb/patches/ucred.patch > > To apply this patch, use -p6 like so: > > cd work/my/kernel/tree/sys > patch -p6 < path/to/patch/file/ucred.patch > > -- > > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 1:44:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from k6.locore.ca (k6.locore.ca [198.96.117.170]) by hub.freebsd.org (Postfix) with ESMTP id AA1E337B400; Sat, 23 Feb 2002 01:44:33 -0800 (PST) Received: (from jake@localhost) by k6.locore.ca (8.11.6/8.11.6) id g1N9j4R34410; Sat, 23 Feb 2002 04:45:04 -0500 (EST) (envelope-from jake) Date: Sat, 23 Feb 2002 04:45:03 -0500 From: Jake Burkholder To: John Baldwin Cc: dillon@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: First (easy) td_ucred patch Message-ID: <20020223044503.C27577@locore.ca> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.ORG on Fri, Feb 22, 2002 at 11:38:07PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Apparently, On Fri, Feb 22, 2002 at 11:38:07PM -0500, John Baldwin said words to the effect of; > I'm currently testing the following patch whcih is a subset of the td_ucred > changes. It involves no API changes, but only contains 2 basic changes: > > 1) We still need Giant when doing the crhold() to set td_ucred in > cred_update_thread(). This is an old bug that is my fault. I knew that > PROC_LOCK was sufficient yet which was my reason for not using td_ucred. > However, we could still be derferencing a stale p_ucred and doing very bad > things, so this needs to be fixed until p_ucred is fully protected by the > PROC_LOCK. This also means that td_ucred is now safe to use. As such: > > 2) All the "easy" p->p_ucred -> td->td_ucred changes that don't involve the > changes to API's such as suser() and p_canfoo(). The next patch in this > series will most likely be the suser() API change. > > http://www.FreeBSD.org/~jhb/patches/ucred.patch The UGAR changes in sysv_sem.c to not leak Giant are most unreleated and should probably be committed separately. I wonder who introduced the leaks in the first place. Other than that I don't see anything wrong with this. Commit it. Jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 3:27:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from lyris.bestnet.net (lyris.bestnet.net [216.15.129.82]) by hub.freebsd.org (Postfix) with SMTP id 0B6BD37B400 for ; Sat, 23 Feb 2002 03:27:17 -0800 (PST) X-Mailer: Lyris Web Interface Date: Sat, 23 Feb 2002 04:47:33 -0600 Subject: Three Free Psychology/Self-Improvement Software Downloads To: "mindmedia" From: "bruce@mindmedia.com" List-Unsubscribe: Reply-To: "mindmedia" Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG MIND MEDIA REVIEW No.43 Introductory Edition Edited by Mead Rose Copy Editor: Will Penna ****************************************************************** When you think about self-improvement, think Mind Media! To visit our site, tune your favorite web browser to: http://www.mindmedia.com ****************************************************************** IN THIS SPECIAL ISSUE! ++ WELCOME TO MIND MEDIA -- HOME OF PERSONAL DEVELOPMENT ON THE WEB by Bruce Ehrlich, Founder of the Mindware Catalog ++ THREE FREE SOFTWARE DOWNLOADS YOU THAT WILL CHANGE YOUR LIFE -- DOWNLOAD SITES BELOW ++ FIVE SOFTWARE DOWNLOAD WEB SITES WORTH HAVING ON YOUR HARD DRIVE by Bruce Eisner ++ FIVE MINDWARE ONLINE APPLICATIONS YOU CAN VISIT TODAY by Bruce Eisner ++ FIVE FAVORITE MIND MEDIA PRODUCTS by the Mind Media Staff +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+-+--+--+--+--+--+--+ WELCOME TO MIND MEDIA -- HOME OF PERSONAL DEVELOPMENT ON THE WEB by Bruce Ehrlich, Founder of the Mindware Catalog This is a special issue of the Mindware Review. The Mindware Review is one of the longest running Internet newsletters -- having sent out its first issue to subscribers in early 1995. The publication is written by the Mind Media staff and is sent to a subscriber list which has now grown to over 100,000. I am sending it to you because you visited Mind Media Life-Enhancment Network so I know you are interested in what I call Mindware. Please excuse me if I sent it to you in error, Mind Media Review is about "Mindware" -- a term I coined back in 1988 to describe software that I had been collecting while I was finishing my doctorate in P.M. Actually, just when I was going to write my dissertation, I decided to start a small "side-business" called the Mindware catalog. The 32 page color catalog grew from a circulation of 5000 for issue mailed out in the spring of '88 to 500,000 mailed in the summer of 1994 -- our last issue. In a strange twist, the first issue of the Mindware catalog was called The Mindware Review -- which was the hot idea of a marketing company I had hired to put out the first issue. When I found out I could print 50,000 catalogs for about twice as much as 5,000, I left that company and found a local designer named Scott Sandow who was a great layout artist but an also had been in business and marketing his entire life. As someone who had come from Grad School (I didn't know the difference between an invoice and a purchase order), I was glad to have him spend hours with me figuring out what this mindware thing was all about and who would be interested in using it. This is an excerpt from the "Letter from the President" from that second Mindware catalog. "Welcome to Mindware! An extra dimension has been added to your personal computer with the arrival of a new genre of software we call mind appliances. These mind appliances cover many areas but share a common purpose: the enhancement of human intelligence in all its aspects - - and so our name became,"Mindware." Mindware was conceived and created to be more than a business in the normal sense. We sincerely believe that anyone can benefit from this new relationship between computers and the mind! By the time we had grown to half a million catalogs, we were the first catalog to have sold a CD-ROM drive along with CD-ROMs to play in them and also the first to sell voice recognition software. In a sense, we were kind of a "Sharper Image" of computer software as well as a self- improvement catalog. One half-million catalogs costs a lot to mail. Our post office bill was so large, I thought we should be given red carpet treatment at the post office -- but we had to stand in line like everyone else. Our team at Mindware was always dreaming of starting something like America Online or even to be given a section of AOL or than equally prominent CompuServe in order to replace or at least supplement the catalog. My main assistant at the time,Thad Atkins had a couple of friends who were starting a company to do catalogs on something called the World Wide Web. When I ordered an ISDN line and started browsing, I was sure that this was where I wanted real estate. So as the web began to become more than just a place for scientists, we were one of the earliest online. Our first web site was at mindware.com but we decided to create a larger site called the Mind Media Life- Enhancement Network so that we could feature more than just the Mindware Catalog Online. In 1995, we stopped printing catalogs and went entirely online. The same year, I came out with the first email edition of the Mindware Review. At the time there were only about a hundred online newsletters and so were actually read and even enjoyed (I got a lot of email asking questions when I wrote something which is how I know). But by the end of the decade, the Internet revolution occurred -- which actually made it more difficult for us in many ways. All of the good programmers and web artists were suddenly working for large corporations that formerly only had stores and advertised on TV. Search engines were selling ranking -- and we didn't have the money to pay. From less than twenty online catalogs that were around when we started, now there were 200,000. Many of them started what became known as the "dot comers" -- people who had made money in other businesses and now were getting Venture Capital which allowed them to out spend us by huge factors. Perhaps the one of the strangest stories of my twelve years in the computer human potential business was an event that took place in the fall of 1999. It was right in the middle of the Internet boom -- when you drove through Silicon Valley and saw billboards from VC companies. A woman called me. She told me that she had an online art gallery but that her first love was personal development -- the kind of products and services that we provide. She then told me she represented someone in the "self-help" field whose name I would instantly recognize. He had acquired a publicly traded shell (a stock in which the company no longer exists but which is still listed on a stock exchange -- a fast way of raising public money is to buy one of these "shells" and put your company and a few others together into it.). She was looking for a few good personal development sites which you could join together under this self-improvement figure. At one point, she had me on the line with a gentleman who asked me what my gross sales were. He had seen my business plan, which is posted on our web site and mistakenly took our projections based on one million dollars investment as our current earnings. When he found out we weren't making the projected figure, he hurriedly got off the phone. Who was the mysterious man? A few months afterward, Anthony Robbins launched his high-profile web site -- Dreamlife.com. And here is an excerpt from a January 10, 2000 Newsweek Magazine (International Edition) -- http://www.rickross.com/reference/general/general162.html -- article: "This much is clear: if success is the goal, the gurus have found it. Anthony Robbins leads the pack. Of all the gurus, he's most focused on the Net. Last summer Robbins took control of a publicly traded shell company whose stock cost just pennies a share and announced plans to build a self- improvement Web site, Dreamlife.com. The site still isn't operational, but investors don't seem to mind. Last week its stock stood at $16 a share, putting Robbins's stake at more than $300 million." Well Robbins site was slick and "did everything right" -- from personalized membership to an online interactive tutorial which identified the parts of life that needed improvement, complete with Tony Robbins voice and picture to guide you. I joined the site and was bombarded with Newsletters on a daily basis. Now in one of the business plans I wrote, before the Internet became so fashionable -- I suggested that Mind Media approach individuals such a Robbins, Deepak Chopra Stephen Covey. In "The 7 Habits of Highly Effective People, and John Gray, the former Hindu monk from right here in Mind Media Country, Santa Cruz, California -- who wrote "Men Are From Mars, Women Are From Venus," with the idea of Mind Media using its expertise to give them a web presence. So when the VC money flowed like wine and all of the big guys jumped aboard, little Mind Media remained pretty much a slowly evolving web organism as it always had been. Well in mid-2001, a year after its launch, Dreamlife.com was dead. And Mind Media is still here.. Back in 1990, one of the software publishers I featured on in the Mindware Catalog, Bert Shaw, sent me this quotation which still hands on my bulletin board. "Nothing in this world can take the place of persistence. Talent will not; nothing is more common than unsuccessful men with talent. Genius will not; unrewarded genius is almost a proconservation alone will not; the world is full of educated derelicts." The saying had nobody it was attributed to, so I decided to look it up on the web as I was wring this, I found out it was said by good old "Silent" Calvin Coolidge himself, so I thought about taking it down since he doesn't have much of a reputation] as he had articulated an idea missed by many in the trendy self- improvement arena. So this special issue is dedicated to the future of what I called Mindware back in 1988. Its come a long way. In this issue, I'll start with three free programs we give away on our site. Then I'm going to take sections of two previous issues to introduce you to five great downloads on the Web (not on our site) and five of the best of the online applications And finally I'll put in a plug for five of my favorite Mind Media Products. So I'm still carrying the torch Mindware. My dream is to make our West into a portal dedicated to the use of computers as mind appliances -- for individual success and personal development and the enhancement of the diverse aspects of human intelligence. How is that for perseverance? +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+-+--+--+--+--+--+--+ THREE FREE SOFTWARE DOWNLOADS YOU THAT MAY CHANGE YOUR LIFE Here are three free software give-always from mind media They all can be found on our "Specials Page" http://www.mindmedia.com/specials.html. 1) The first is the ever-popular Mindviewer -- a very close follow up to the original Mind Prober which was published in the mid-1980's: MINDVIEWER GIVES YOU X-RAY VISION INTO ANYONE'S HIDDEN PERSONALITY AND PRIVATE FANTASIES "Gain the advantage in personal and business relationships Reveals the secrets of winning people's trust Developed by an eminent team of psychologists "I was impressed by the reports it produced. In fact, I thought it pegged me pretty darn close to how I perceive myself. After showing the reports to a couple of close (and I mean close) friends, they agreed with Mindviewer's analysis completely. Of course I clipped out the section "Top Secret Sex Fantasies." -- Ron Albright, Computer Shopper Uncover anyone's hidden personality with the best-selling self- improvement program of all time. After using Mindviewer, you will feel like you have x- ray vision into parts of people that normally they can keep hidden. People hide behind masks. With Mindviewer, you gain accurate insight into the true nature of your friends, family, employees, associates. Find out what makes them tick, what gets them angry-- even how to shape their behavior. Developed by Drs. James and Kathy Johnson, a renowned husband/wife psychologist team, the program is both entertaining and enlightening. And its analysis hits home in a big way. Using the program is simple, yet the complex psychometric equations taken from personality psychology make the program uncannily accurate. Mindviewer asks you a series of multiple- choice questions about yourself or someone you wish to know better. Then you get a detailed profile of your subject, which can be viewed on the screen or printed as a detailed 3-5 page report custom-generated from the results. Run Mindviewer on your best friends and see if you get some new angle on them. Run Mindviewer on your boss for advice on important matters like how to get that raise or next promotion. Or try the program on your spouse or lover to reveal some hidden fantasies that just might warm up your relationship. You'll have fun finding out what Mindviewer can do for you! A free download at download at http://www.mindmedia.com/mv.com 2) Another of our featured downloads is called Brainworks and it helps you determine which hemisphere of the brain you use --left or right or perhaps a bit of both. WHAT BRAIN HEMISPHERE DO YOU PREFER? ARE YOU MORE VISUAL OR AUDITORY? DISCOVER YOUR PERSONALITY STYLE Do you know whether you prefer your left hemisphere or your right hemisphere? When you think, do you think visually or in sounds? The answer to these two key questions can unlock important secrets to your personality. Secrets, which can give help you to become more successful and effective in everything that you do. Mind Media Life Enhancement Network is pleased to give you, for a limited time, Brain Works, a simple to use software program which answer the two questions we asked at the beginning, and then give you much more. You'll get a complete report which you can read on screen or print, how your unique preferences for right or left hemisphere and for visual or auditory thinking styles make up your unique personality style. But more important, you'll get guidance and important tips on how you can be more effective in your learning, in relating to others and in achieving your goals with maximum success. When you download Brain Works, you get a free subscription to Mind Media Review Newsletter with information on the cutting edge software, CD-ROMs and new technologies in computers and the mind. Back issues of this important publication are available on our site. The questionnaire is visual, short and fun. And you never get the same set of questions twice. The report invaluable! Print it out and keep it for future reverence. For a limited time only, Mind Media Life Enhancement Network presents Brain Work, a revealing mind revealing software program absolutely FREE! Download it now at http://www.mindmedia.com/brain.html The last is called IQ Smarts and it gives you four IQ scores instead of one and helps you build your IQ by several points -- up to 15 says the publishers. TURBOCHARGE YOUR BRAIN WITH IQ SMARTS MEASURE YOUR IQ - THEN RAISE IT DRAMATICALLY RAISE YOUR IQ BY 15 POINTS OR MORE Discover your hidden strengths At last, here is a computer program that can not only measures your IQ, and whether you are left or right brained-- it actually raises your IQ. And it will raise it not just a tiny amount but to a dimension that you never dreamed possible. From the psychological and programming genius of Dr. James Johnson -- founder of the pioneer Human Edge Software -- comes IQ SMARTS, dramatic new advance intelligence. The software is based on major breakthroughs in the brain sciences. You?ll get exercises specially designed to develop your brain the same way aerobics, Nautilus, and other fitness programs have given us the ability to develop our body. Until now, these exercises have been available only from professionals with programs costing many thousands of dollars. Now these life- changing exercises are available with IQ SMARTS. IQ SMARTS begins by measuring all aspects of your intelligence through a short test. In the multi-page report you print out, you are told: Your overall IQ score Your "common sense" intelligence IQ score Your "book smarts" intelligence IQ Your "thinking creativity" intelligence score After explaining exactly what these scores mean, the program tells you exactly where you are strongest and targets weaknesses for improvement. IQ SMARTS explains what these strengths and weaknesses mean for your everyday life. Then, you are given a personalized training program that includes exercises, skills and procedures that are specific to your unique makeup and that are guaranteed to improve your ability to think and be creative. The user interface friendly and easy to use and you?ll be building brain cells in minutes after running the program. With this remarkable program, you can actually raise your intelligence by 15 points or more in as little as three weeks. This increase can mean the difference between success and failure in many careers and can lead a better and richer life. Download Spot http://www.mindmedia.com/iqsmart.html +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+-+--+--+--+--+--+-- FIVE SOFTWARE DOWNLOAD WEB SITES WORTH HAVING ON YOUR HARD DRIVE If you're at all like me, you love to download and try new software. However as you might have discovered, you only really find a few programs that you continue using and want to keep on your hard drive. Today, I'm going to show some of the programs that I kept on my computer. In addition to being winners, I have tried to choose programs from a variety of different sub-categories of the genre that I call "mindware." They are all worth a download. 1. http://www.goalpro.com/index.cfm?ID=50571 The people who publish GoalPro 5.0 calls it "The most effective success- management application available" and the funny thing is -- they may be right! I've been working on a special feature article covering my personal search trying to find the perfect program or combination of programs to accomplish the increasingly difficult task of managing my personal information. And GoalPro software in tandem with Microsoft Outlook is the combo that I use. But you don't have to use GoalPro on a PC. The people at GoalPro have kept up with the state-of-the-art and are offering GoalPro with most of its features intact as an on-line application. So Macintosh and Linux users as well as anyone who has access to the web can begin using GoalPro right now. What does the program do? Well it's hard to describe all of what it does briefly and so next month this publication will have a feature length review of GoalPro. In summary, it guides you through the process of listing and clarifying your most important life objectives. You a set of concrete goals to reach each of these objectives and also create short term tasks for reaching the objectives and goals. The program not only helps you create your "success tree" of objectives, goals and tasks, it sets up a regular daily and separate weekend routine where you visit these lists and determine how you are doing. This is called Success Coach and it's pretty darn useful. There's even a past-due management system where people who set too many tasks or procrastinate -- - people such as myself -- can evaluate and reschedule missed deadlines. Download a free thirty-day trial -- you might want to keep using it. 2. http://www.store-mindjet.com/affiliate.cfm?aff=PEZEVOBFQNFJ A mind map is a visual representation of the relationship between related ideas. The typical map starts with a central idea, word or concept. Then, around the central word you draw five to ten main ideas that relate to that word. You then take each of those child words and again draw the five to ten main ideas that relate to each of those words until you have an excellent visual model of the idea you are trying to understand or express. MindManager 3.7 is perhaps the best tool for creating mind-maps that has yet been devised, Whether you're trying to solve a problem, prioritize your daily activities, organize multiple projects or make a simple to-do list, MindManager will help. Here's some of the wide range of uses for the program: you can prepare speeches and presentations quickly and easily, plan and track complex tasks and projects, share project information with others, via MindManager's unique Internet conferencing, create web sites and/or site maps using the web site export features, track progress on projects visually, to quickly see how far along you are, organize multiple projects at once, take notes efficiently and easily reorganize them and more. Download a free full-featured demo -- or a smaller version which downloads quicker and try it for 21 days. There are a wealth of resources on-line to help you learn the skill of mapping your mind. So if you want the big picture, he's a place to start drawing it. 3.http://www.brain.com Josh Reynolds's Brain.com focuses on mental performance enhancement with its premier thinkFast software. Now thinkFast is an on-line application and brain.com has become an on-line brain-enhancement community. In 1995,the Global Idea Bank listed my idea of the "mini- mind gym" http://www.globalideasbank.org/BOV/BV-488.HTML. The principle is that by using your brain, you can increase your mental fitness. Mind Media's IQ Builder and thinkFast software featured on brain.com work along these principles. They both give you a variety of mental tests which focus on a spectrum of mental abilities. By increasing the difficulty over trials, you "build mental muscle." Now thinkFast has become an on-line application and added features which take the idea of mental fitness workouts further. thinkFast is the perfect mind-mini gym and allows you to measure and save your improvements on-line. It "works you out" on a wide variety of mental skills. The program even includes your own Personal Tutor who coaches you to greater mental heights. 4. http://www.acal.com Stressmaster by Acel Self-Growth Software is about more than just stress. Modules contained within this ambitious Windows program include: Define Goals, Design Life, Overcome Additions, Change My State of Mind, Calm Anger, Cope with Daily Stress and several more. Some of the modules take you through interactive exercises that help you deal with various problem areas. Each of the modules written output is recorded in a master Self Discovery Journal. This is one of the best of the growing number of programs aimed toward self-therapy, StressMaster is available for a 30-day free trial. 5. http://brainstorming.org/ablemind/index.html ThinkWorld's Ablemind Streaming Idea Generator is the latest in the genre of brainstorming software and works in conjunction with the company's Brainstorming 101 seminar. You can download a demo version of the program, which contains a subset of the program's 87 million idea cards. The idea cards, which the program generates upon demand, consist of three words - a verb adjective and a noun. For example here are a few of the cards I drew: bevel postmodern shirts, lighten leather cans, vibrate instant televisions, These phrases might seem a bit meaningless but they are there to make you think. The company gives a few examples. Pump basketball shoes, they say, would have made people laugh twenty years ago. Now, after tens of millions of basketball shoes sold, people would think the idea pure genius. A few more examples among the millions possible from Able's software: project Celluloid images, navigate electronic documents. Well the arguments pretty convincing that this software can make me money. I'm going to file my patent for a vibrating instant television tomorrow. . +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+-+--+--+--+--+--+-- FIVE MINDWARE ONLINE APPLICATIONS YOU CAN VISIT TODAY by Bruce Eisner The Internet is always issuing new and trendy buzzwords and so you have probably started hearing that the next wave on the Web is online applications. In fact, online applications have arrived and will revolutionize the way that you will use the interactive self- improvement and personal-development tools which is the essence of the meaning of this new genre of Mindware tools. Since the beginning of personal computing, there have always been a number of competing operating systems which you can chose from to run your PC. In the past twenty years CPM, OS/2, the BeOS, the Macintosh, many flavors of UNIX along with several flavors of Windows. It has been a situation akin to the Biblical tower of Babel and so computer users for the most part chose Windows along those "who think different" picking the Mac. And the third most popular desktop operating system, Linux. Many people have chose Windows as an operating system because there are hundreds of times as many applications made for it than for the Mac or Linux or the others. Most computer users have dreamed of a day when it didn't matter what operating system you ran, you could use whatever application you wanted on any computer. Online applications are rapidly making this dream a reality. Online applications are built to work within a computer browser so that the application runs on the web server and any web-enabled computer can use them. In addition to their universality of use, these applications can also be upgraded by system administrator of the web server, virtually eliminating the need to constantly buy and install upgrades to every one of your software applications. Confined at first to a small group of mainstream software applications such as accounting software, utilities, online greeting card generators and the like, online applications are now becoming available for the kind of software that I like to write about. So here are five web online applications worth a visit. I've written about some of them before and their here again because they help broaden the range of possible scope of what you can look at today. Five Self-Improvement Online Applications worth a Visit 1.http://www.living-software.com The first personal development online application I'm going to review is by an Israeli team headed by C.E.O Doron Zzur. The link above is to a beta of the most sophisticated self-therapy tool created for the computer and it runs on any machine you care to try it on! After registering, the program prompts you with the question, "How Do You Feel Today." You answer by writing down what psychologists are fond of calling "your issues" and then you are introduced to four helpers in cartoon form. You can choose any of them and they will converse with you and help you clarify your problem and think about it in different terms. Each of the helpers is a different kind of personality and can give advices, which might even contradict the other very different personality. By then noting changes as they occur, you involve yourself in an ongoing process. This process can lead to improvements in attitude and mood as the brainstorming helps you become familiar with your "issue." And with familiarity comes relief by looking at something you here-to-fore avoided. This is a beta and has some rough edges but the good part is that it is free. Also information collected will help to make this site even better. Eventually Mr. Dzur hopes to turn this into a paid service. He was inspired to go into this line of work by a very significant personal crisis in his life, which occurred after his wife passed away with cancer several years ago. He founded this company to make available to the public ways of quickly responding to stressful life crises. His company has board of consulting psychologists and the site is worth a visit or several. 2. http://app.brain.com/member/join.cfm Josh Reynolds's Brain.com focuses on mental performance enhancement with its premier thinkFast software. Now thinkFast is an online application and brain.com has become an online brain-enhancement community. In 1995,the Global Idea Bank listed my idea of the "mini- mind gym" http://www.globalideasbank.org/BOV/BV-488.html was listed for voting.The basic principle is that by using your brain, you can increase your mental fitness by exersing it, just as you do physical muscles. Mind Media's IQ Builder and thinkFast software featured on brain.com work along these principles. They both give you a variety of mental tests, which focus on a spectrum of mental abilities. By increasing the difficulty over trials, you "build mental muscle." Now thinkFast has become an online application and added features, which take the idea of mental fitness workouts further. ThinkFast is the perfect mind-mini gym and allows you to measure and save your improvements online. It "works you out" on a wide variety of mental skills. The program even includes your own Personal Tutor who coaches you to greater mental heights. 3.http://www.goalpro.com/index.cfm?ID=50571 I've written a lot in June and July about GoalPro - which I consider one of the most helpful software programs I've used to help me organize for success. I'm featuring it here again because you've got to look around the site to find that in addition to the software version, there's an online version of GoalPro you can purchase as a subscription which allows anyone including Mac and Linux users to use this significant program. Here's what I wrote in June: The people who publish GoalPro 5.0 calls it "The most effective success management application available" and the funny thing is - - they may be right! GoalPro software in tandem with Microsoft Outlook is the combo that I use. But you don't have to use GoalPro on a PC. The people at GoalPro have kept up with the state-of-the- art and are offering GoalPro with most of its features intact as an online application. So Macintosh and Linux users as well as anyone who has access to the web can begin using GoalPro right now. What does the program do? Well it's hard to describe all of what it does briefly and so next month this publication will have a feature length review of GoalPro. In short, it guides you through the process of listing and clarifying your most important life objectives. You list a set of concrete goals to reach each of these objectives and also create short term tasks for reaching the objectives and goals. The program not only helps you create your "success tree" of objectives, goals and tasks, it sets up a regular daily and separate weekend routine where you visit these lists and determine how you are doing. This is called Success Coach and it's pretty darn useful. There's even a past-due management system where people who set too many tasks or procrastinate can evaluate and reschedule missed deadlines. Download a free thirty-day trial - - you might want to keep using it -- I did. 4. http://www.timecontrol.cc Panella Strategies: Success-Centered Time Management Power and Power Marketing Principles is not an exactly an online application but I put it here because it relies on the multimedia capabilities of the web to deliver an extensive library of time management principles developed by Vince Panella. During the past 18 years, his profit and time-building programs have influenced thousands of companies and tens of thousands of people in 25 countries around the world. The application- like section is called the Time Control Room and it has series of modules which take several days to learn (Panella finds that most people who take other time management courses don't learn anything because they are presented two quickly so they are forgotten just as quickly. Real Audio lectures by Vince Panella are supplemented by written materials available for download and the program together works very well. The cost is $20 per month but readers of this column can email mailto:psi@accelernet.net and get yearlong subscription for only $49.95 if you mention that Robert Galpren, Editor-In-Cheif from the Mind Media review sent you. 5.http://www.ansir.com -- Ashir.com is more than a web site, it is one premier example of Mindware online app. Ashir.com starts with a personality test which uses a unique system called the Ansir Style of Relating. You take the test after registering and are rated on 14 different personality attributes. Here is what they say about their test. "Discover your Self- truth and potential! It's free, challenging, and enlightening! But be warned, this serious test has 2,744 possible combinations and is ranked-by participants and Members alike-among the toughest and most accurate on the Web. Self-honesty is key. Read Profile Briefs first, then learn much, much more with Profiles In Depth absolutely free! Once you take the test, you are presented with a unique perspective on yourself and also become part of the Asir community. It is fun, fascinating and most of all - worth a visit. +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+-+--+--+--+--+--+-- FIVE FAVORITE MIND MEDIA PRODUCTS by the Mind Media Staff Here are the most popular Mind Media products of all time favorite from actual sales figures. 1) Most often on the order list -- our Top Twenty Software Programs from the Famous Mindware Catalog http://www.mindmedia.com/catalog/pub/bundles.html 2) For those of you who want the highest quality Mindware CD-ROM based mental tests -- Be Sure to Get the Superstar Suite! Five multimedia tests originally published] by Virtual Knowledge, Inc available at http://www.mindmedia.com/customer3.html 3) Always Popular -- Mind Prober 3.0 at http://wwww.mindmedia.com/probind.html came in third 4) The State-of-the-Art CD-ROM by Psychologist Sam Keen --Your Mythic Journey http://www.mindmedia.com/mythicj.html 5) Five Multimedia CD-ROMs for Personal and Professional Success -- Full Interactive Video Courses on a Disk! Titles: Manage Time, Organize For Success, Manage Stress, Attitude for Success and Communicate! http://www.mindmedia.com/catalog/pub/cdrom.html +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ Digital River -- the world's largest electronic download company has taken over administration of our electronic download catalog. This means that you get their 30 money back guarantee and their technical support staff is on call 24/7 to insure that if you pay for your download you get your download. Just go to http://www.digitalriver.com/dr/v2/ec_Main.Entry?SP=10007&SID=30169 &CID=0 We hope you enjoy the work our staff has done to enrich the product descriptions of the programs you can download there include Mind Prober 3.0 and our Top Ten Windows Best-Sellers -. . .-- ... --- ..-. - .... . .-- .. .-. . -.. Mind Media, Inc. 849 Almar Ave. Suite C-125 Santa Cruz, CA 95060 You can order securely on our web site or Call toll free during weekdays at 1-800-818-9445 Or Internationally:1+831+4260762 Or FAX 1+831+426-8519 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+ Thank you for reading and stay tuned for more! For comments or contributions, send e-mail to Mead Rose mailto:web@mindmedia.com Copyright 2002, Mind Media, Inc. -. . .-- ... --- ..-. - .... . .-- .. .-. . -.. --- You are currently subscribed to mindmedia as: current@freebsd.org To unsubscribe send a blank email to leave-mindmedia-462958O@lyris.bestnet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 5: 0: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 7444537B400 for ; Sat, 23 Feb 2002 05:00:06 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id E15255341; Sat, 23 Feb 2002 14:00:03 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Mike Smith Cc: current@freebsd.org Subject: Re: HEADS UP: ACPI CA updated References: <20020222215647.A54975@hub.freebsd.org> From: Dag-Erling Smorgrav Date: 23 Feb 2002 14:00:02 +0100 In-Reply-To: <20020222215647.A54975@hub.freebsd.org> Message-ID: Lines: 10 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Smith writes: > I've finally updated the ACPI CA codebase with Intel's 20020214 drop > (yes, I tagged it 0217, my bad). ...so just retag it. Add the correct tag on top of the incorrect one, then remove the incorrect tag. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 8:15:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id DDAB937B405; Sat, 23 Feb 2002 08:15:25 -0800 (PST) Received: from blossom.cjclark.org ([12.234.91.48]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020223161525.XWAS1147.rwcrmhc52.attbi.com@blossom.cjclark.org>; Sat, 23 Feb 2002 16:15:25 +0000 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.6) id g1NGFO322843; Sat, 23 Feb 2002 08:15:24 -0800 (PST) (envelope-from cjc) Date: Sat, 23 Feb 2002 08:15:24 -0800 From: "Crist J. Clark" To: John Baldwin Cc: Dag-Erling Smorgrav , ggombert@imatowns.com, current@FreeBSD.ORG, David Wolfskill Subject: Re: Install World fails in -Current Message-ID: <20020223081524.K16048@blossom.cjclark.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.ORG on Fri, Feb 22, 2002 at 10:25:03PM -0500 X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Feb 22, 2002 at 10:25:03PM -0500, John Baldwin wrote: > > On 23-Feb-02 Dag-Erling Smorgrav wrote: > > David Wolfskill writes: > >> Sounds like a botched (or not run) "mergemaster" execution: > > > > No - mergemaster will croak because it runs mtree to build its temp > > directory, so if you're trying to update a pre-smmsp system you have > > to add the smmsp user and group manually. > > I think this is a bug but can't think of a clean way to work around it. I can think of a two "clean" ways... but it ain't pretty. 1) Do not enter users in the BSD.*.dist files by 'uname,' but only by 'uid.' But this makes the files more difficult to maintain and generally icky. 2) Keep 'uname's in BSD.*.dist files, but use the distributed src/etc/master.passwd to process the BSD.*.dist files into a format with 'uid's on the fly during buildworld-installworld. These versions would only be built during buildworld and only used by the mtree(8) commands during installworld. The source BSD.*.dist files would be the ones actually installed of course. Obviously, one could do the same with groups. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 8:42:46 2002 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 63E6D37B405; Sat, 23 Feb 2002 08:42:40 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id g1NGgen81171; Sat, 23 Feb 2002 08:42:40 -0800 (PST) (envelope-from david) Date: Sat, 23 Feb 2002 08:42:40 -0800 (PST) From: David Wolfskill Message-Id: <200202231642.g1NGgen81171@bunrab.catwhisker.org> To: current@freebsd.org, tanimura@freebsd.org Subject: Problem with buildworld: what is "major" really supposed to be? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Trying to "make buildworld" for today's -CURRENT, I get: >>> stage 4: building libraries -------------------------------------------------------------- ... ===> doc cc -fpic -DPIC -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm_file.c -o kvm_file.So In file included from /usr/obj/usr/src/i386/usr/include/sys/file.h:40, from /usr/src/lib/libkvm/kvm_file.c:54: /usr/obj/usr/src/i386/usr/include/sys/systm.h:305: syntax error before `int' /usr/obj/usr/src/i386/usr/include/sys/systm.h:306: syntax error before `int' /usr/obj/usr/src/i386/usr/include/sys/systm.h:307: syntax error before `(' *** Error code 1 After enough tinkering with copies of the files to demonstrate to my satisfaction that my C skills are pretty rusty, I noticed that: * The lines in systm.h look like (starting at line 301): /* * Common `dev_t' stuff are declared here to avoid #include poisoning */ int major(dev_t x); int minor(dev_t x); dev_t makedev(int x, int y); udev_t dev2udev(dev_t x); dev_t udev2dev(udev_t x, int b); int uminor(udev_t dev); int umajor(udev_t dev); udev_t makeudev(int x, int y); so it looks as if we're declaring "major" as a function returning int. * But sys/sys/file.h, starting at line 49 reads: #ifdef _KERNEL #include #include #include #include which is OK, except that sys/sys/types.h, starting at line 113 reads: /* * minor() gives a cookie instead of an index since we don't want to * change the meanings of bits 0-15 or waste time and space shifting * bits 16-31 for devices that don't use them. */ #define major(x) ((int)(((u_int)(x) >> 8)&0xff)) /* major number */ #define minor(x) ((int)((x)&0xffff00ff)) /* minor number */ #define makedev(x,y) ((dev_t)(((x) << 8) | (y))) /* create dev_t */ and this appears to be a bit of a problem, because by the time the C compiler gets to the "int major(dev_t x);" line in sys/sys/systm.h, "major" has been replaced, so the line looks like: int ((int)(((u_int)( dev_t x ) >> 8)&0xff)) ; which is pretty non-ideal, any way you look at it. In case it's of interest/value, recent CVSup history is: freebeast(5.0-C)[44] tail /var/log/cvsup-history.log CVSup begin from cvsup14.freebsd.org at Tue Feb 19 03:47:02 PST 2002 CVSup ended from cvsup14.freebsd.org at Tue Feb 19 03:53:36 PST 2002 CVSup begin from cvsup14.freebsd.org at Wed Feb 20 03:47:02 PST 2002 CVSup ended from cvsup14.freebsd.org at Wed Feb 20 04:00:08 PST 2002 CVSup begin from cvsup14.freebsd.org at Thu Feb 21 03:47:03 PST 2002 CVSup ended from cvsup14.freebsd.org at Thu Feb 21 03:53:29 PST 2002 CVSup begin from cvsup14.freebsd.org at Fri Feb 22 03:47:02 PST 2002 CVSup ended from cvsup14.freebsd.org at Fri Feb 22 03:54:26 PST 2002 CVSup begin from cvsup14.freebsd.org at Sat Feb 23 04:35:13 PST 2002 CVSup ended from cvsup14.freebsd.org at Sat Feb 23 04:42:37 PST 2002 freebeast(5.0-C)[45] So: how should this be resolved? Or am I just confused (again)? Thanks, david -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 8:44:58 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 72F3B37B400; Sat, 23 Feb 2002 08:44:49 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g1NGidwC007127; Sat, 23 Feb 2002 17:44:40 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: David Wolfskill Cc: current@FreeBSD.ORG, tanimura@FreeBSD.ORG Subject: Re: Problem with buildworld: what is "major" really supposed to be? In-Reply-To: Your message of "Sat, 23 Feb 2002 08:42:40 PST." <200202231642.g1NGgen81171@bunrab.catwhisker.org> Date: Sat, 23 Feb 2002 17:44:39 +0100 Message-ID: <7126.1014482679@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yeah, I'm chasing that one right now. I'm not yet quite sure which commit has broken this, nor what the right fix is... Poul-Henning In message <200202231642.g1NGgen81171@bunrab.catwhisker.org>, David Wolfskill w rites: >Trying to "make buildworld" for today's -CURRENT, I get: > >>>> stage 4: building libraries >-------------------------------------------------------------- >... >===> doc >cc -fpic -DPIC -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm_file.c -o kvm_file.So >In file included from /usr/obj/usr/src/i386/usr/include/sys/file.h:40, > from /usr/src/lib/libkvm/kvm_file.c:54: >/usr/obj/usr/src/i386/usr/include/sys/systm.h:305: syntax error before `int' >/usr/obj/usr/src/i386/usr/include/sys/systm.h:306: syntax error before `int' >/usr/obj/usr/src/i386/usr/include/sys/systm.h:307: syntax error before `(' >*** Error code 1 > > >After enough tinkering with copies of the files to demonstrate to >my satisfaction that my C skills are pretty rusty, I noticed that: > >* The lines in systm.h look like (starting at line 301): > >/* > * Common `dev_t' stuff are declared here to avoid #include poisoning > */ > >int major(dev_t x); >int minor(dev_t x); >dev_t makedev(int x, int y); >udev_t dev2udev(dev_t x); >dev_t udev2dev(udev_t x, int b); >int uminor(udev_t dev); >int umajor(udev_t dev); >udev_t makeudev(int x, int y); > > > so it looks as if we're declaring "major" as a function returning int. > >* But sys/sys/file.h, starting at line 49 reads: > >#ifdef _KERNEL >#include >#include >#include >#include > > which is OK, except that sys/sys/types.h, starting at line 113 reads: > >/* > * minor() gives a cookie instead of an index since we don't want to > * change the meanings of bits 0-15 or waste time and space shifting > * bits 16-31 for devices that don't use them. > */ >#define major(x) ((int)(((u_int)(x) >> 8)&0xff)) /* major number */ >#define minor(x) ((int)((x)&0xffff00ff)) /* minor number */ >#define makedev(x,y) ((dev_t)(((x) << 8) | (y))) /* create dev_t */ > > > and this appears to be a bit of a problem, because by the time the C > compiler gets to the "int major(dev_t x);" line in sys/sys/systm.h, > "major" has been replaced, so the line looks like: > >int ((int)(((u_int)( dev_t x ) >> 8)&0xff)) ; > > which is pretty non-ideal, any way you look at it. > > >In case it's of interest/value, recent CVSup history is: >freebeast(5.0-C)[44] tail /var/log/cvsup-history.log >CVSup begin from cvsup14.freebsd.org at Tue Feb 19 03:47:02 PST 2002 >CVSup ended from cvsup14.freebsd.org at Tue Feb 19 03:53:36 PST 2002 >CVSup begin from cvsup14.freebsd.org at Wed Feb 20 03:47:02 PST 2002 >CVSup ended from cvsup14.freebsd.org at Wed Feb 20 04:00:08 PST 2002 >CVSup begin from cvsup14.freebsd.org at Thu Feb 21 03:47:03 PST 2002 >CVSup ended from cvsup14.freebsd.org at Thu Feb 21 03:53:29 PST 2002 >CVSup begin from cvsup14.freebsd.org at Fri Feb 22 03:47:02 PST 2002 >CVSup ended from cvsup14.freebsd.org at Fri Feb 22 03:54:26 PST 2002 >CVSup begin from cvsup14.freebsd.org at Sat Feb 23 04:35:13 PST 2002 >CVSup ended from cvsup14.freebsd.org at Sat Feb 23 04:42:37 PST 2002 >freebeast(5.0-C)[45] > > >So: how should this be resolved? Or am I just confused (again)? > > >Thanks, >david >-- >David H. Wolfskill david@catwhisker.org >I believe it would be irresponsible (and thus, unethical) for me to advise, >recommend, or support the use of any product that is or depends on any >Microsoft product for any purpose other than personal amusement. > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 8:48: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id 2B6C137B400 for ; Sat, 23 Feb 2002 08:47:59 -0800 (PST) Received: (qmail 11518 invoked from network); 23 Feb 2002 16:47:57 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.90.110.184]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 23 Feb 2002 16:47:57 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020223044503.C27577@locore.ca> Date: Sat, 23 Feb 2002 11:47:57 -0500 (EST) From: John Baldwin To: Jake Burkholder Subject: Re: First (easy) td_ucred patch Cc: current@FreeBSD.ORG, dillon@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 23-Feb-02 Jake Burkholder wrote: > Apparently, On Fri, Feb 22, 2002 at 11:38:07PM -0500, > John Baldwin said words to the effect of; > >> I'm currently testing the following patch whcih is a subset of the td_ucred >> changes. It involves no API changes, but only contains 2 basic changes: >> >> 1) We still need Giant when doing the crhold() to set td_ucred in >> cred_update_thread(). This is an old bug that is my fault. I knew that >> PROC_LOCK was sufficient yet which was my reason for not using td_ucred. >> However, we could still be derferencing a stale p_ucred and doing very >> bad >> things, so this needs to be fixed until p_ucred is fully protected by the >> PROC_LOCK. This also means that td_ucred is now safe to use. As such: >> >> 2) All the "easy" p->p_ucred -> td->td_ucred changes that don't involve the >> changes to API's such as suser() and p_canfoo(). The next patch in this >> series will most likely be the suser() API change. >> >> http://www.FreeBSD.org/~jhb/patches/ucred.patch > > The UGAR changes in sysv_sem.c to not leak Giant are most unreleated and > should probably be committed separately. I wonder who introduced the leaks > in the first place. Yes. The first change will also be a separate commit. > Other than that I don't see anything wrong with this. Commit it. > > Jake -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 8:54:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 7E1B037B404; Sat, 23 Feb 2002 08:54:36 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g1NGsXwC007262; Sat, 23 Feb 2002 17:54:33 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Cc: David Wolfskill , current@FreeBSD.ORG, tanimura@FreeBSD.ORG Subject: Re: Problem with buildworld: what is "major" really supposed to be? In-Reply-To: Your message of "Sat, 23 Feb 2002 17:44:39 +0100." <7126.1014482679@critter.freebsd.dk> Date: Sat, 23 Feb 2002 17:54:33 +0100 Message-ID: <7261.1014483273@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ok, found it: This is the culprit: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/sys/file.h.diff?r1=1.39&r2=1.40 In message <7126.1014482679@critter.freebsd.dk>, Poul-Henning Kamp writes: > >Yeah, I'm chasing that one right now. > >I'm not yet quite sure which commit has broken this, nor what the right >fix is... > >Poul-Henning > >In message <200202231642.g1NGgen81171@bunrab.catwhisker.org>, David Wolfskill w >rites: >>Trying to "make buildworld" for today's -CURRENT, I get: >> >>>>> stage 4: building libraries >>-------------------------------------------------------------- >>... >>===> doc >>cc -fpic -DPIC -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm_file.c -o kvm_file.So >>In file included from /usr/obj/usr/src/i386/usr/include/sys/file.h:40, >> from /usr/src/lib/libkvm/kvm_file.c:54: >>/usr/obj/usr/src/i386/usr/include/sys/systm.h:305: syntax error before `int' >>/usr/obj/usr/src/i386/usr/include/sys/systm.h:306: syntax error before `int' >>/usr/obj/usr/src/i386/usr/include/sys/systm.h:307: syntax error before `(' >>*** Error code 1 >> >> >>After enough tinkering with copies of the files to demonstrate to >>my satisfaction that my C skills are pretty rusty, I noticed that: >> >>* The lines in systm.h look like (starting at line 301): >> >>/* >> * Common `dev_t' stuff are declared here to avoid #include poisoning >> */ >> >>int major(dev_t x); >>int minor(dev_t x); >>dev_t makedev(int x, int y); >>udev_t dev2udev(dev_t x); >>dev_t udev2dev(udev_t x, int b); >>int uminor(udev_t dev); >>int umajor(udev_t dev); >>udev_t makeudev(int x, int y); >> >> >> so it looks as if we're declaring "major" as a function returning int. >> >>* But sys/sys/file.h, starting at line 49 reads: >> >>#ifdef _KERNEL >>#include >>#include >>#include >>#include >> >> which is OK, except that sys/sys/types.h, starting at line 113 reads: >> >>/* >> * minor() gives a cookie instead of an index since we don't want to >> * change the meanings of bits 0-15 or waste time and space shifting >> * bits 16-31 for devices that don't use them. >> */ >>#define major(x) ((int)(((u_int)(x) >> 8)&0xff)) /* major number */ >>#define minor(x) ((int)((x)&0xffff00ff)) /* minor number */ >>#define makedev(x,y) ((dev_t)(((x) << 8) | (y))) /* create dev_t */ >> >> >> and this appears to be a bit of a problem, because by the time the C >> compiler gets to the "int major(dev_t x);" line in sys/sys/systm.h, >> "major" has been replaced, so the line looks like: >> >>int ((int)(((u_int)( dev_t x ) >> 8)&0xff)) ; >> >> which is pretty non-ideal, any way you look at it. >> >> >>In case it's of interest/value, recent CVSup history is: >>freebeast(5.0-C)[44] tail /var/log/cvsup-history.log >>CVSup begin from cvsup14.freebsd.org at Tue Feb 19 03:47:02 PST 2002 >>CVSup ended from cvsup14.freebsd.org at Tue Feb 19 03:53:36 PST 2002 >>CVSup begin from cvsup14.freebsd.org at Wed Feb 20 03:47:02 PST 2002 >>CVSup ended from cvsup14.freebsd.org at Wed Feb 20 04:00:08 PST 2002 >>CVSup begin from cvsup14.freebsd.org at Thu Feb 21 03:47:03 PST 2002 >>CVSup ended from cvsup14.freebsd.org at Thu Feb 21 03:53:29 PST 2002 >>CVSup begin from cvsup14.freebsd.org at Fri Feb 22 03:47:02 PST 2002 >>CVSup ended from cvsup14.freebsd.org at Fri Feb 22 03:54:26 PST 2002 >>CVSup begin from cvsup14.freebsd.org at Sat Feb 23 04:35:13 PST 2002 >>CVSup ended from cvsup14.freebsd.org at Sat Feb 23 04:42:37 PST 2002 >>freebeast(5.0-C)[45] >> >> >>So: how should this be resolved? Or am I just confused (again)? >> >> >>Thanks, >>david >>-- >>David H. Wolfskill david@catwhisker.org >>I believe it would be irresponsible (and thus, unethical) for me to advise, >>recommend, or support the use of any product that is or depends on any >>Microsoft product for any purpose other than personal amusement. >> >>To Unsubscribe: send mail to majordomo@FreeBSD.org >>with "unsubscribe freebsd-current" in the body of the message >> > >-- >Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 >phk@FreeBSD.ORG | TCP/IP since RFC 956 >FreeBSD committer | BSD since 4.3-tahoe >Never attribute to malice what can adequately be explained by incompetence. > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 9:24:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 81E8337B400; Sat, 23 Feb 2002 09:24:42 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id B3DB75341; Sat, 23 Feb 2002 18:24:40 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: current@freebsd.org Subject: -CURRENT in pretty good shape, after all From: Dag-Erling Smorgrav Date: 23 Feb 2002 18:24:39 +0100 Message-ID: Lines: 9 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thumbs up and big cheers to all of you (well, us) guys working on -CURRENT. It's pretty stable and has been for a while now - and even on my poor old 350 MHz K6-2, it performs well enough to make a kickass desktop & development platform. Let's hope it'll only get better from here on out :) DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 9:35:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from angelica.unixdaemons.com (angelica.unixdaemons.com [209.148.64.135]) by hub.freebsd.org (Postfix) with ESMTP id E95FA37B404 for ; Sat, 23 Feb 2002 09:35:35 -0800 (PST) Received: from angelica.unixdaemons.com (bmilekic@localhost.unixdaemons.com [127.0.0.1]) by angelica.unixdaemons.com (8.12.2/8.12.1) with ESMTP id g1NHZOh4027533; Sat, 23 Feb 2002 12:35:24 -0500 (EST) Received: (from bmilekic@localhost) by angelica.unixdaemons.com (8.12.2/8.12.1/Submit) id g1NHZOFh027531; Sat, 23 Feb 2002 12:35:24 -0500 (EST) (envelope-from bmilekic) Date: Sat, 23 Feb 2002 12:35:24 -0500 From: Bosko Milekic To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: -CURRENT in pretty good shape, after all Message-ID: <20020223123524.A27146@unixdaemons.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from des@ofug.org on Sat, Feb 23, 2002 at 06:24:39PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Feb 23, 2002 at 06:24:39PM +0100, Dag-Erling Smorgrav wrote: > Thumbs up and big cheers to all of you (well, us) guys working on > -CURRENT. It's pretty stable and has been for a while now - and even > on my poor old 350 MHz K6-2, it performs well enough to make a kickass > desktop & development platform. Let's hope it'll only get better from > here on out :) Yep! Out of 3 FreeBSD machines I own, I now have 2 (the dual processor systems) running -CURRENT. I think it should finally be noted that -CURRENT effectively does meet its advertised form: "development bleeding edge version of FreeBSD" (as opposed to "[totally broke and bleeding] developer [for those who feel like it] version of FreeBSD."). > DES > -- > Dag-Erling Smorgrav - des@ofug.org -- Bosko Milekic bmilekic@unixdaemons.com bmilekic@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 10:40:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 96D0837B402 for ; Sat, 23 Feb 2002 10:40:07 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020223184007.USQM2951.rwcrmhc53.attbi.com@InterJet.elischer.org>; Sat, 23 Feb 2002 18:40:07 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA79320; Sat, 23 Feb 2002 10:35:45 -0800 (PST) Date: Sat, 23 Feb 2002 10:35:44 -0800 (PST) From: Julian Elischer To: Bosko Milekic Cc: Dag-Erling Smorgrav , current@FreeBSD.ORG Subject: Re: -CURRENT in pretty good shape, after all In-Reply-To: <20020223123524.A27146@unixdaemons.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG that could change real soon! On Sat, 23 Feb 2002, Bosko Milekic wrote: > > On Sat, Feb 23, 2002 at 06:24:39PM +0100, Dag-Erling Smorgrav wrote: > > Thumbs up and big cheers to all of you (well, us) guys working on > > -CURRENT. It's pretty stable and has been for a while now - and even > > on my poor old 350 MHz K6-2, it performs well enough to make a kickass > > desktop & development platform. Let's hope it'll only get better from > > here on out :) > > Yep! Out of 3 FreeBSD machines I own, I now have 2 (the dual processor > systems) running -CURRENT. I think it should finally be noted that > -CURRENT effectively does meet its advertised form: "development > bleeding edge version of FreeBSD" (as opposed to "[totally broke and > bleeding] developer [for those who feel like it] version of FreeBSD."). > > > DES > > -- > > Dag-Erling Smorgrav - des@ofug.org > > -- > Bosko Milekic > bmilekic@unixdaemons.com > bmilekic@FreeBSD.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 11: 6:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from angelica.unixdaemons.com (angelica.unixdaemons.com [209.148.64.135]) by hub.freebsd.org (Postfix) with ESMTP id 3A54937B404 for ; Sat, 23 Feb 2002 11:06:44 -0800 (PST) Received: from angelica.unixdaemons.com (bmilekic@localhost.unixdaemons.com [127.0.0.1]) by angelica.unixdaemons.com (8.12.2/8.12.1) with ESMTP id g1NJ6Vh4038815; Sat, 23 Feb 2002 14:06:31 -0500 (EST) Received: (from bmilekic@localhost) by angelica.unixdaemons.com (8.12.2/8.12.1/Submit) id g1NJ6V7J038814; Sat, 23 Feb 2002 14:06:31 -0500 (EST) (envelope-from bmilekic) Date: Sat, 23 Feb 2002 14:06:31 -0500 From: Bosko Milekic To: Julian Elischer Cc: Dag-Erling Smorgrav , current@FreeBSD.ORG Subject: Re: -CURRENT in pretty good shape, after all Message-ID: <20020223140631.A38036@unixdaemons.com> References: <20020223123524.A27146@unixdaemons.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from julian@elischer.org on Sat, Feb 23, 2002 at 10:35:44AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Feb 23, 2002 at 10:35:44AM -0800, Julian Elischer wrote: > that could change real soon! I certainly *hope* not. If you plan to break it, you plan to break it, but I hope you don't plan to render it unstable. There is a difference between breaking the build, breaking -CURRENT because of one thing you happened to have missed when you committed and breaking it for a prolonged period of time without actually knowing what broke it and then having to do `guess-work' and needless debugging because someone committed totally broken code. By -CURRENT's description, the former is acceptable, every once in a while, but the latter is not. The latter just leads to a lot of blood spillage and is evidence of a not-well-tested set of changes. So, it's acceptable to go: "Oh, I did this wrong and broke -CURRENT, let me fix it" every once in a while but it shouldn't be acceptable to go "euh, -CURRENT is broken and it's probably because of me but I have no friggin' clue how or why. I don't even know where to start looking." It's just common sense. > On Sat, 23 Feb 2002, Bosko Milekic wrote: > > > > > On Sat, Feb 23, 2002 at 06:24:39PM +0100, Dag-Erling Smorgrav wrote: > > > Thumbs up and big cheers to all of you (well, us) guys working on > > > -CURRENT. It's pretty stable and has been for a while now - and even > > > on my poor old 350 MHz K6-2, it performs well enough to make a kickass > > > desktop & development platform. Let's hope it'll only get better from > > > here on out :) > > > > Yep! Out of 3 FreeBSD machines I own, I now have 2 (the dual processor > > systems) running -CURRENT. I think it should finally be noted that > > -CURRENT effectively does meet its advertised form: "development > > bleeding edge version of FreeBSD" (as opposed to "[totally broke and > > bleeding] developer [for those who feel like it] version of FreeBSD."). > > > > > DES > > > -- > > > Dag-Erling Smorgrav - des@ofug.org > > > > -- > > Bosko Milekic > > bmilekic@unixdaemons.com > > bmilekic@FreeBSD.org -- Bosko Milekic bmilekic@unixdaemons.com bmilekic@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 11:20:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id 461DA37B400; Sat, 23 Feb 2002 11:20:09 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020223192008.UHUK2626.rwcrmhc51.attbi.com@InterJet.elischer.org>; Sat, 23 Feb 2002 19:20:08 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA79453; Sat, 23 Feb 2002 11:03:28 -0800 (PST) Date: Sat, 23 Feb 2002 11:03:27 -0800 (PST) From: Julian Elischer To: John Baldwin Cc: dillon@FreeBSD.org, current@FreeBSD.org Subject: Re: First (easy) td_ucred patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 22 Feb 2002, John Baldwin wrote: > http://www.FreeBSD.org/~jhb/patches/ucred.patch > The following diff removes the capacity to cope with the case when td is NULL. I presume it is there because it CAN be NULL. (Though I have not checked further.) --- //depot/vendor/freebsd/sys/fs/smbfs/smbfs_vnops.c 2001/12/20 08:43:46 +++ //depot/projects/smpng/sys/fs/smbfs/smbfs_vnops.c 2002/02/21 15:55:47 @@ -976,7 +976,6 @@ caddr_t id = (caddr_t)1 /* ap->a_id */; /* int flags = ap->a_flags;*/ struct thread *td = curthread; - struct proc *p = td ? td->td_proc : NULL; struct smb_cred scred; u_quad_t size; off_t start, end, oadd; @@ -1027,7 +1026,7 @@ return EOVERFLOW; end = start + oadd; } - smb_makescred(&scred, td, p ? p->p_ucred : NULL); + smb_makescred(&scred, td, td->td_ucred); switch (ap->a_op) { case F_SETLK: switch (fl->l_type) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 11:40:10 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id D0F1037B404 for ; Sat, 23 Feb 2002 11:40:08 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020223194008.VZOT2951.rwcrmhc53.attbi.com@InterJet.elischer.org>; Sat, 23 Feb 2002 19:40:08 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA79531; Sat, 23 Feb 2002 11:23:18 -0800 (PST) Date: Sat, 23 Feb 2002 11:23:17 -0800 (PST) From: Julian Elischer To: Bosko Milekic Cc: Dag-Erling Smorgrav , current@FreeBSD.ORG Subject: Re: -CURRENT in pretty good shape, after all In-Reply-To: <20020223140631.A38036@unixdaemons.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I forgot the :-) On Sat, 23 Feb 2002, Bosko Milekic wrote: > > On Sat, Feb 23, 2002 at 10:35:44AM -0800, Julian Elischer wrote: > > that could change real soon! > > I certainly *hope* not. If you plan to break it, you plan to break it, > but I hope you don't plan to render it unstable. There is a difference To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 11:40:19 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 69DD737B421; Sat, 23 Feb 2002 11:40:15 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020223194015.VZQH2951.rwcrmhc53.attbi.com@InterJet.elischer.org>; Sat, 23 Feb 2002 19:40:15 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA79529; Sat, 23 Feb 2002 11:21:25 -0800 (PST) Date: Sat, 23 Feb 2002 11:21:24 -0800 (PST) From: Julian Elischer To: John Baldwin Cc: dillon@FreeBSD.org, current@FreeBSD.org Subject: Re: First (easy) td_ucred patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 22 Feb 2002, John Baldwin wrote: > > http://www.FreeBSD.org/~jhb/patches/ucred.patch the structural rewriting in kern_proc.c should be done as a separate commit. (though I agree it should be done) the structural rewriting in kern/sysv_*.c could be done as a separate commit as well. (I agree it is worth doing) I'll let you get away with unp_listen() :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 12:21:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.dada.it (mail3.dada.it [195.110.96.70]) by hub.freebsd.org (Postfix) with SMTP id 0DB6437B400 for ; Sat, 23 Feb 2002 12:21:32 -0800 (PST) Received: (qmail 18796 invoked from network); 23 Feb 2002 20:21:21 -0000 Received: from unknown (HELO torrini.org) (195.110.114.101) by mail.dada.it with SMTP; 23 Feb 2002 20:21:21 -0000 Received: (from riccardo@localhost) by torrini.org (8.11.6/8.11.6) id g1NKLMj69289; Sat, 23 Feb 2002 21:21:22 +0100 (CET) (envelope-from riccardo) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 23 Feb 2002 21:21:22 +0100 (CET) From: Riccardo Torrini To: Julian Elischer Subject: Re: -CURRENT in pretty good shape, after all Cc: current@FreeBSD.ORG, Dag-Erling Smorgrav , Bosko Milekic Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 23-Feb-2002 (19:23:17/GMT) Julian Elischer wrote: > I forgot the :-) [...] >> On Sat, Feb 23, 2002 at 10:35:44AM -0800, Julian Elischer wrote: >> > that could change real soon! >> >> I certainly *hope* not. If you plan to break it, you plan to break it, >> but I hope you don't plan to render it unstable. There is a difference I'm -CURRENT from 3.0 and I can confirm that (if handled with care) is really usable. I have contributed only with bug report and not with lines of code or patches, but I think that bug report can help also. Anyway, any plan to fix build breakage? ---8<--- In file included from /usr/obj/usr/src/i386/usr/include/sys/file.h:40, from /usr/src/lib/libkvm/kvm_file.c:54: /usr/obj/usr/src/i386/usr/include/sys/systm.h:305: syntax error before `int' /usr/obj/usr/src/i386/usr/include/sys/systm.h:306: syntax error before `int' /usr/obj/usr/src/i386/usr/include/sys/systm.h:307: syntax error before `(' ---8<--- I really need build to (try to?) locate missing /dev/speaker :( Riccardo. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 12:51:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 43ABB37B417; Sat, 23 Feb 2002 12:51:21 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1NKpE741310; Sat, 23 Feb 2002 12:51:14 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Feb 2002 12:51:14 -0800 (PST) From: Matthew Dillon Message-Id: <200202232051.g1NKpE741310@apollo.backplane.com> To: Seigo Tanimura Cc: current@FreeBSD.ORG, John Baldwin , Alfred Perlstein Subject: Re: pgrp/session patch References: <200201051752.g05Hq3gG074525@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <200201241022.g0OAMISM093913@faber.r.dl.itc.u-tokyo.ac.jp> <20020124024534.V13686@elvis.mu.org> <200202131739.g1DHdZT5023794@rina.r.dl.itc.u-tokyo.ac.jp> <200202190945.g1J9j9kg076110@rina.r.dl.itc.u-tokyo.ac.jp> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Here is the most up-to-date version of pgrp/session lock (at Change 6700): : :http://people.FreeBSD.org/~tanimura/patches/pgrp10.diff.gz : :I would like to commit this on the next Sunday. Otherwise, my patch :would conflict with other patches, especially tty. : :-- :Seigo Tanimura Do you have any plans to get pgdelete() out from under Giant? That would allow leavepgrp(), doenterpgrp(), enterpgrp(), enterthispgrp(), setsid() (mostly) to be taken out from under Giant, and perhaps a few others. I was thinking of simply having a free list of sessions and process groups, locked by PGRPSESS_XLOCK(). pgdelete() would then not have to call FREE() and setsid() would almost always be able to pull a new structure of the appropriate free list and thus not have to obtain Giant for the MALLOC. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 13:12:17 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 31DCE37B404 for ; Sat, 23 Feb 2002 13:12:15 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id B09A95341; Sat, 23 Feb 2002 22:12:12 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Riccardo Torrini Cc: Julian Elischer , current@FreeBSD.ORG, Bosko Milekic Subject: Re: -CURRENT in pretty good shape, after all References: From: Dag-Erling Smorgrav Date: 23 Feb 2002 22:12:12 +0100 In-Reply-To: Message-ID: Lines: 39 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Riccardo Torrini writes: > Anyway, any plan to fix build breakage? Sure: Index: file.h =================================================================== RCS file: /home/ncvs/src/sys/sys/file.h,v retrieving revision 1.40 diff -u -r1.40 file.h --- file.h 23 Feb 2002 11:12:57 -0000 1.40 +++ file.h 23 Feb 2002 21:10:58 -0000 @@ -37,10 +37,6 @@ #ifndef _SYS_FILE_H_ #define _SYS_FILE_H_ -#include -#include -#include -#include #ifndef _KERNEL #include #include @@ -51,6 +47,7 @@ #include #include #include +#include struct stat; struct thread; > I really need build to (try to?) locate missing /dev/speaker :( # kldload atspeaker DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 13:15: 8 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 1789737B419; Sat, 23 Feb 2002 13:14:50 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id D70BDAE368; Sat, 23 Feb 2002 13:14:49 -0800 (PST) Date: Sat, 23 Feb 2002 13:14:49 -0800 From: Alfred Perlstein To: Matthew Dillon Cc: Seigo Tanimura , current@FreeBSD.ORG, John Baldwin Subject: How to fix malloc. Message-ID: <20020223211449.GJ80761@elvis.mu.org> References: <200201051752.g05Hq3gG074525@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <200201241022.g0OAMISM093913@faber.r.dl.itc.u-tokyo.ac.jp> <20020124024534.V13686@elvis.mu.org> <200202131739.g1DHdZT5023794@rina.r.dl.itc.u-tokyo.ac.jp> <200202190945.g1J9j9kg076110@rina.r.dl.itc.u-tokyo.ac.jp> <200202232051.g1NKpE741310@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200202232051.g1NKpE741310@apollo.backplane.com> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Matthew Dillon [020223 12:51] wrote: > > :Here is the most up-to-date version of pgrp/session lock (at Change 6700): > : > :http://people.FreeBSD.org/~tanimura/patches/pgrp10.diff.gz > : > :I would like to commit this on the next Sunday. Otherwise, my patch > :would conflict with other patches, especially tty. > : > :-- > :Seigo Tanimura > > Do you have any plans to get pgdelete() out from under Giant? That > would allow leavepgrp(), doenterpgrp(), enterpgrp(), enterthispgrp(), > setsid() (mostly) to be taken out from under Giant, and perhaps a few > others. > > I was thinking of simply having a free list of sessions and process > groups, locked by PGRPSESS_XLOCK(). pgdelete() would then not have > to call FREE() and setsid() would almost always be able to pull a new > structure of the appropriate free list and thus not have to obtain Giant > for the MALLOC. All these per-subsystem free-lists are making me nervous in both complexity and wasted code... Ok, instead of keeping all these per-subsystem free-lists here's what we do: In kern_malloc:free() right at the point of if (size > MAXALLOCSAVE) we check if we have Giant or not. if we do not then we simply queue the memory however, if we do then we call into kmem_free with all the queued memory. This ought to solve the issue without making us keep all these per-cpu caches. By the way, since "MAXALLOCSAVE" is some multiple of PAGE_SIZE, we really don't have to worry about it when freeing small structures although that puts evilness into malloc(9) consumers. Can you please consider that instead of continueing down this path of per-subsystem caches? thanks, -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 13:28:58 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 17A5537B402 for ; Sat, 23 Feb 2002 13:28:52 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g1NLSlD80813 for ; Sat, 23 Feb 2002 16:28:47 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sat, 23 Feb 2002 16:28:47 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Subject: Discussion of guidelines for additional version control mechanisms Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the past week, a number of comments have been made both for and against additional version control mechanisms being used to supplement the FreeBSD Project official CVS server. Proponents of additional mechanisms, such as Perforce, have pointed out that CVS doesn't provide the necessary tools to support several important development models, including those based on light-weight branching and three-way merges. Others have pointed out that while these technical benefits might be real, the resulting decentralization can be a problem for the project, and that requiring additional version control mechanisms in order to work with the project is simply not feasible. For the purpose of this discussion, please assume that additional version control facilities serve a useful purpose (by supporting collaboration, tree tracking, etc), but that no everyone will be able to use them, both based on preference, and for technical and material reasons. The purpose of this message is to initiate a serious discussion of what guidelines might be put in place to help facilitate the use of additional version control mechanisms (which are inevitable, even if it means only individual developers with local CVS repositories of their own), and how to specifically address the problems that have been posed, in particular relating to communication. The outcome of this conversation will probably not be a set of rules: there is sufficient variation in the nature of various sub-projects that it wouldn't make sense. However, it will result in a set of recommendations to maximize communication and acceptance by the broader community. I've mixed in some suggested things to think about as possible answers, but there are probably many more things to consider. Question 1: How should the presence of on-going work in an external repository be announced to the broader community? Suggestion: e-mail to -arch, -current, or a related mailing list Question 2: How should the status of on-going work be announced to the broader community? Suggestion: Bi-monthly developer status report Suggestion: Status web page for the project Suggestion: Regular status reports on work to relevant mailing lists Question 3: How should the results of the on-going work be made available to the broader community? Suggestion: cvsup10 export of the Perforce tree Suggestion: patchsets sent to appropriate mailing lists with status Suggestion: patchsets generated automatically and posted to the mailing list Question 4: How agressively should on-going work be pushed back into the base tree? (Note that the answer here depends a great deal on the nature of the work: both its rationale, its goals, etc). In particular note that currently Perforce is used to hold experimental changes, as well as ones destined for eventual production use. Suggestion: For work requiring large source tree sweeps, API changes, etc, only when the work is ready to commit. Suggestion: For more minor work, P4 might be used only for brief collaboration, or to assist in patch preparation. It's worth noting before getting into too much discussion that there's a spectrum of possibilities, and different answers may be appropriate for different circumstances. If P4 is not used as a collaboration tool, only for local version management for individual developers, it serves the same purpose as any local source tree. Likewise, at low levels of collaboration, it's no different from mailing patchsets. As the level of collaboration increases, the failed balancing point seems to be in providing access to non-P4 users. It might be useful to look at this discussion through a series of case examples, including projects such as KSE, SMPng, OpenPAM, TrustedBSD, architecture ports such as ia64, sparc64, etc. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 13:32:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.dada.it (mail4.dada.it [195.110.96.56]) by hub.freebsd.org (Postfix) with SMTP id 3483137B405 for ; Sat, 23 Feb 2002 13:32:31 -0800 (PST) Received: (qmail 2004 invoked from network); 23 Feb 2002 21:32:21 -0000 Received: from unknown (HELO torrini.org) (195.110.114.101) by mail.dada.it with SMTP; 23 Feb 2002 21:32:21 -0000 Received: (from riccardo@localhost) by torrini.org (8.11.6/8.11.6) id g1NLWQA79525; Sat, 23 Feb 2002 22:32:26 +0100 (CET) (envelope-from riccardo) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 23 Feb 2002 22:32:26 +0100 (CET) From: Riccardo Torrini To: Dag-Erling Smorgrav Subject: Re: -CURRENT in pretty good shape, after all Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 23-Feb-2002 (21:12:12/GMT) Dag-Erling Smorgrav wrote: > Riccardo Torrini writes: >> Anyway, any plan to fix build breakage? > Sure: [...] This works. Thanks. >> I really need build to (try to?) locate missing /dev/speaker :( ># kldload atspeaker This doesn't work. I'm missing something obvious? # kldstat Id Refs Address Size Name 1 3 0xc0100000 2c7b4c kernel 2 1 0xc1981000 3000 daemon_saver.ko # kldload atspeaker # kldstat Id Refs Address Size Name 1 4 0xc0100000 2c7b4c kernel 2 1 0xc1981000 3000 daemon_saver.ko 3 1 0xc27c6000 3000 atspeaker.ko # echo cde >/dev/speaker /dev/speaker: Operation not supported. # ls -ld /dev/*speaker* ls: No match. Riccardo. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 13:40:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 0F8E237B416; Sat, 23 Feb 2002 13:40:29 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g1NLeRwC013093; Sat, 23 Feb 2002 22:40:28 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Robert Watson Cc: current@FreeBSD.ORG Subject: Re: Discussion of guidelines for additional version control mechanisms In-Reply-To: Your message of "Sat, 23 Feb 2002 16:28:47 EST." Date: Sat, 23 Feb 2002 22:40:27 +0100 Message-ID: <13092.1014500427@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Robe rt Watson writes: >Question 1: How should the presence of on-going work in an external >repository be announced to the broader community? On the project.freebsd.org web-page and the regular status emails generated from the contents of that web-page. >Question 2: How should the status of on-going work be announced to the >broader community? > >Suggestion: Bi-monthly developer status report >Suggestion: Status web page for the project >Suggestion: Regular status reports on work to relevant mailing lists All of the above with a s/Regular/As warranted/ on the third line. >Question 3: How should the results of the on-going work be made available >to the broader community? > >Suggestion: cvsup10 export of the Perforce tree >Suggestion: patchsets sent to appropriate mailing lists with status >Suggestion: patchsets generated automatically and posted to the mailing > list Whichever fits the particular project but it would be wonderful if a patch file for all projects could be accessed via the web-page. >Question 4: How agressively should on-going work be pushed back into the >base tree? > >Suggestion: For work requiring large source tree sweeps, API changes, etc, > only when the work is ready to commit. Panic: recursion: "commit only when ready to commit" Doesn't this one hinge on the stability/compilability goal of current and only that ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 13:55:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 0A2BE37B405; Sat, 23 Feb 2002 13:55:12 -0800 (PST) Received: from pool0164.cvx40-bradley.dialup.earthlink.net ([216.244.42.164] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ek8J-0004FU-00; Sat, 23 Feb 2002 13:55:07 -0800 Message-ID: <3C780FAF.F95A23EF@mindspring.com> Date: Sat, 23 Feb 2002 13:54:55 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Matthew Dillon , Seigo Tanimura , current@FreeBSD.ORG, John Baldwin Subject: Re: How to fix malloc. References: <200201051752.g05Hq3gG074525@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <200201241022.g0OAMISM093913@faber.r.dl.itc.u-tokyo.ac.jp> <20020124024534.V13686@elvis.mu.org> <200202131739.g1DHdZT5023794@rina.r.dl.itc.u-tokyo.ac.jp> <200202190945.g1J9j9kg076110@rina.r.dl.itc.u-tokyo.ac.jp> <200202232051.g1NKpE741310@apollo.backplane.com> <20020223211449.GJ80761@elvis.mu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > All these per-subsystem free-lists are making me nervous in both > complexity and wasted code... Me too. > Ok, instead of keeping all these per-subsystem free-lists here's what > we do: > > In kern_malloc:free() right at the point of > if (size > MAXALLOCSAVE) we check if we have Giant or not. > if we do not then we simply queue the memory > however, if we do then we call into kmem_free with all the queued memory. > > This ought to solve the issue without making us keep all these > per-cpu caches. One modification: limit the number that are freed per invocation to some number small enough that there won't be a big latency. Once everything gets to this point, though, there will be nothing to trigger a free with giant held, and you'll just queue things up forever. Really, we need counted queues -- queues that know the number of elemenets on them. This is a requirement for RED-Queueing, and it will let us know when the queue gets deep... then you can grab giant, and flush down the queue if it hits a high watermark. Obviously, the correct way to handle this is per CPU memory pools that don't have any need for lock contention at all on the "real" frees. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 14: 4: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 48F6037B419 for ; Sat, 23 Feb 2002 14:03:59 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 53B125343; Sat, 23 Feb 2002 23:03:57 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Riccardo Torrini Cc: current@FreeBSD.ORG Subject: Re: -CURRENT in pretty good shape, after all References: From: Dag-Erling Smorgrav Date: 23 Feb 2002 23:03:56 +0100 In-Reply-To: Message-ID: Lines: 10 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Riccardo Torrini writes: > On 23-Feb-2002 (21:12:12/GMT) Dag-Erling Smorgrav wrote: > > # kldload atspeaker > This doesn't work. I'm missing something obvious? Not that I can see... works for me DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 14: 6:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D0A6F37B404; Sat, 23 Feb 2002 14:06:32 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 848C75341; Sat, 23 Feb 2002 23:06:31 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: cvs-committers@FreeBSD.org Cc: cvs-all@FreeBSD.org, current@FreeBSD.org Subject: Re: cvs commit: src/sys/sys file.h References: <200202232114.g1NLEh696459@freefall.freebsd.org> From: Dag-Erling Smorgrav Date: 23 Feb 2002 23:06:30 +0100 In-Reply-To: <200202232114.g1NLEh696459@freefall.freebsd.org> Message-ID: Lines: 17 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > des 2002/02/23 13:14:43 PST > > Modified files: > sys/sys file.h > Log: > Fix namespace pollution introduced in previous commit. > > Revision Changes Path > 1.41 +1 -4 src/sys/sys/file.h > This commit unbreaks world. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 14:10:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id CBB6937B402; Sat, 23 Feb 2002 14:10:36 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1NMAaB41797; Sat, 23 Feb 2002 14:10:36 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Feb 2002 14:10:36 -0800 (PST) From: Matthew Dillon Message-Id: <200202232210.g1NMAaB41797@apollo.backplane.com> To: Alfred Perlstein , Bosko Milekic Cc: Seigo Tanimura , current@FreeBSD.ORG, John Baldwin Subject: Re: How to fix malloc. References: <200201051752.g05Hq3gG074525@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <200201241022.g0OAMISM093913@faber.r.dl.itc.u-tokyo.ac.jp> <20020124024534.V13686@elvis.mu.org> <200202131739.g1DHdZT5023794@rina.r.dl.itc.u-tokyo.ac.jp> <200202190945.g1J9j9kg076110@rina.r.dl.itc.u-tokyo.ac.jp> <200202232051.g1NKpE741310@apollo.backplane.com> <20020223211449.GJ80761@elvis.mu.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :All these per-subsystem free-lists are making me nervous in both :complexity and wasted code... : :Ok, instead of keeping all these per-subsystem free-lists here's what :we do: : :In kern_malloc:free() right at the point of : if (size > MAXALLOCSAVE) we check if we have Giant or not. : if we do not then we simply queue the memory : however, if we do then we call into kmem_free with all the queued memory. : :This ought to solve the issue without making us keep all these :per-cpu caches. Hmm. I don't like generalizing it to that extent. What if we simply assert that Giant is held if size > MAXALLOCSAVE in free()? i.e. for the moment we require that any 'large allocations' use Giant. Then we can freely use free() to free smaller allocations without Giant. There are three other problems: (1) malloc() itself will call kmem_malloc() even if M_NOWAIT is passed, so we can't optimize malloc()-without-giant unless we add a new flag to deal with this situation. And, (2) we have a single mutex, malloc_mtx. This is Bosko's code so I am adding him to the To: list. Bosko, it looks like with a simple cleanup to the msleep() call we can use a pool lock instead of malloc_mtx, which would give us the ability to lock malloc() on a bucket-by-bucket basis. The addition of a another malloc flag will allow us to tell malloc() to return NULL if it can't do the operation with its own mutex. And, (3) we wind up getting and releasing two mutexes instead of one in the code I was originally refering to, because setsid() already gets an SX lock and I was just going to fold the free list into that. Still, I don't mind doing it via malloc(). What do people think? -Matt Matthew Dillon :By the way, since "MAXALLOCSAVE" is some multiple of PAGE_SIZE, we :really don't have to worry about it when freeing small structures :although that puts evilness into malloc(9) consumers. : :Can you please consider that instead of continueing down this path :of per-subsystem caches? : :thanks, :-- :-Alfred Perlstein [alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 14:43:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0443337B400; Sat, 23 Feb 2002 14:43:36 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1NMhZP49110; Sat, 23 Feb 2002 14:43:35 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Feb 2002 14:43:35 -0800 (PST) From: Matthew Dillon Message-Id: <200202232243.g1NMhZP49110@apollo.backplane.com> Cc: Alfred Perlstein , Bosko Milekic , Seigo Tanimura , current@FreeBSD.ORG, John Baldwin Subject: malloc_bucket() idea (was Re: How to fix malloc.) References: <200201051752.g05Hq3gG074525@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <200201241022.g0OAMISM093913@faber.r.dl.itc.u-tokyo.ac.jp> <20020124024534.V13686@elvis.mu.org> <200202131739.g1DHdZT5023794@rina.r.dl.itc.u-tokyo.ac.jp> <200202190945.g1J9j9kg076110@rina.r.dl.itc.u-tokyo.ac.jp> <200202232051.g1NKpE741310@apollo.backplane.com> <20020223211449.GJ80761@elvis.mu.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is approximately what I am thinking. Note that this gives us the flexibility to create a larger infrastructure around the bucket cache, such as implement per-cpu caches and so on and so forth. What I have here is the minimal implementation. -Matt Index: kern/kern_malloc.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_malloc.c,v retrieving revision 1.93 diff -u -r1.93 kern_malloc.c --- kern/kern_malloc.c 12 Sep 2001 08:37:44 -0000 1.93 +++ kern/kern_malloc.c 23 Feb 2002 22:41:56 -0000 @@ -116,6 +116,63 @@ #endif /* INVARIANTS */ /* + * init_malloc_bucket: + * + * Initialize a malloc bucket + */ +void +init_malloc_bucket(struct malloc_bucket *bucket, struct malloc_type *type, int size) +{ + bzero(bucket, sizeof(struct malloc_bucket)); + bucket->b_size = size; + bucket->b_type = type; + bucket->b_mtx = mtx_pool_find(bucket); +} + +/* + * malloc_bucket: + * + * Allocate a structure from the supplied low-latency cache. NULL is + * returned if the cache is empty. + */ +void * +malloc_bucket(struct malloc_bucket *bucket) +{ + void *ptr = NULL; + + if (bucket->b_next) { + mtx_lock(bucket->b_mtx); + if ((ptr = bucket->b_next) != NULL) { + bucket->b_next = *(caddr_t *)ptr; + KASSERT(bucket->b_count > 0, ("bucket count mismatch")); + --bucket->b_count; + *(caddr_t *)ptr = WEIRD_ADDR; + } else { + KASSERT(bucket->b_count == 0, ("bucket count mismatch")); + } + mtx_unlock(bucket->b_mtx); + } + return(ptr); +} + +/* + * free_bucket: + * + * Free a structure to the low latency cache. + * + */ +void +free_bucket(struct malloc_bucket *bucket, void *ptr) +{ + mtx_lock(bucket->b_mtx); + *(caddr_t *)ptr = bucket->b_next; + bucket->b_next = (caddr_t)ptr; + ++bucket->b_count; + mtx_unlock(bucket->b_mtx); + /* XXX if b_count > something, wakeup our cleaner? */ +} + +/* * malloc: * * Allocate a block of memory. Index: sys/malloc.h =================================================================== RCS file: /home/ncvs/src/sys/sys/malloc.h,v retrieving revision 1.54 diff -u -r1.54 malloc.h --- sys/malloc.h 10 Aug 2001 06:37:04 -0000 1.54 +++ sys/malloc.h 23 Feb 2002 22:36:09 -0000 @@ -109,6 +109,18 @@ long kb_couldfree; /* over high water mark and could free */ }; +/* + * malloc_bucket holder for fast low-latency malloc_bucket() and free_bucket() + * calls. + */ +struct malloc_bucket { + caddr_t b_next; + int b_count; + int b_size; + struct mtx *b_mtx; + struct malloc_type *b_type; +}; + #ifdef _KERNEL #define MINALLOCSIZE (1 << MINBUCKET) #define BUCKETINDX(size) \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 15: 5: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from harrier.prod.itd.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by hub.freebsd.org (Postfix) with ESMTP id 74CE937B402; Sat, 23 Feb 2002 15:05:01 -0800 (PST) Received: from pool0164.cvx40-bradley.dialup.earthlink.net ([216.244.42.164] helo=mindspring.com) by harrier.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16elDu-0006K4-00; Sat, 23 Feb 2002 15:04:58 -0800 Message-ID: <3C78200E.EC89C4E1@mindspring.com> Date: Sat, 23 Feb 2002 15:04:46 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: Alfred Perlstein , Bosko Milekic , Seigo Tanimura , current@FreeBSD.ORG, John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) References: <200201051752.g05Hq3gG074525@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <200201241022.g0OAMISM093913@faber.r.dl.itc.u-tokyo.ac.jp> <20020124024534.V13686@elvis.mu.org> <200202131739.g1DHdZT5023794@rina.r.dl.itc.u-tokyo.ac.jp> <200202190945.g1J9j9kg076110@rina.r.dl.itc.u-tokyo.ac.jp> <200202232051.g1NKpE741310@apollo.backplane.com> <20020223211449.GJ80761@elvis.mu.org> <200202232243.g1NMhZP49110@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon wrote: > This is approximately what I am thinking. Note that this gives us the > flexibility to create a larger infrastructure around the bucket cache, > such as implement per-cpu caches and so on and so forth. What I have > here is the minimal implementation. Uh, probably freeing the mutex of the new bucket after holding the one on the "next" list is probably not what you wanted to happen. 8-). I think you would nead a seperate "head", and then use the head containing structure mutex, instead. I understand what you were trying to do, though... I guess you are relying on the use of different buckets to spread the pain? Right now the pain is centered arouns one struct type anyway (the cred one that started this dicussion), so you are still going to contend the same resource for each (just "bucket hash mtx" instead of "giant", for the bucket type). Also, you probably want it to be a STAILQ. I'm not sure that this is actually a win?!? I guess if there are a bunch of these buckets, you would end up with different hash values for the mutexes... though relying on a hash seems wrong, since you can't really control collision domains that way; eventally, you will get people with widely different perofromance based on where the linker linked their bucket list head to, and that's probably not good. OTOH, A per CPU bucket list means no bucket mtx would be necessary; without that, it's just replacing one type of contention for another, I think, until you start making mutex selection indeterminate. 8^(. Really, this delayed freeing idea is starting to get uglier than just going to per CPU pools... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 15:12:56 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 17C2A37B416; Sat, 23 Feb 2002 15:12:37 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1NNCaH54765; Sat, 23 Feb 2002 15:12:36 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Feb 2002 15:12:36 -0800 (PST) From: Matthew Dillon Message-Id: <200202232312.g1NNCaH54765@apollo.backplane.com> To: Terry Lambert Cc: Alfred Perlstein , Bosko Milekic , Seigo Tanimura , current@FreeBSD.ORG, John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) References: <200201051752.g05Hq3gG074525@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <200201241022.g0OAMISM093913@faber.r.dl.itc.u-tokyo.ac.jp> <20020124024534.V13686@elvis.mu.org> <200202131739.g1DHdZT5023794@rina.r.dl.itc.u-tokyo.ac.jp> <200202190945.g1J9j9kg076110@rina.r.dl.itc.u-tokyo.ac.jp> <200202232051.g1NKpE741310@apollo.backplane.com> <20020223211449.GJ80761@elvis.mu.org> <200202232243.g1NMhZP49110@apollo.backplane.com> <3C78200E.EC89C4E1@mindspring.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :OTOH, A per CPU bucket list means no bucket mtx would be necessary; :without that, it's just replacing one type of contention for another, :I think, until you start making mutex selection indeterminate. 8^(. : :Really, this delayed freeing idea is starting to get uglier than :just going to per CPU pools... : :-- Terry Well, if we want to rewrite malloc() a per-cpu pool inside a critical section would not be that difficult. The 'bucket' array would simply be placed in the per-cpu area. However, with malloc() we still have a serious problem with the malloc_type structure statistics. There would have to be per-cpu information for those as well. critical_enter() isn't much better then a mutex. It can be optimized to get rid of the inline cli & sti however. Actually, it can be optimized trivially for i386, all we have to do is check the critical nesting count from the interrupt code and set the interrupts-disabled bit in the returned (supervisor mode) frame. critical_enter() and critical_exit() would then be nearly perfect. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 15:29:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from k6.locore.ca (k6.locore.ca [198.96.117.170]) by hub.freebsd.org (Postfix) with ESMTP id 45E8237B416; Sat, 23 Feb 2002 15:29:15 -0800 (PST) Received: (from jake@localhost) by k6.locore.ca (8.11.6/8.11.6) id g1NNTmm37564; Sat, 23 Feb 2002 18:29:48 -0500 (EST) (envelope-from jake) Date: Sat, 23 Feb 2002 18:29:47 -0500 From: Jake Burkholder To: Matthew Dillon Cc: Alfred Perlstein , Bosko Milekic , Seigo Tanimura , current@FreeBSD.ORG, John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) Message-ID: <20020223182947.A35990@locore.ca> References: <200201051752.g05Hq3gG074525@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <200201241022.g0OAMISM093913@faber.r.dl.itc.u-tokyo.ac.jp> <20020124024534.V13686@elvis.mu.org> <200202131739.g1DHdZT5023794@rina.r.dl.itc.u-tokyo.ac.jp> <200202190945.g1J9j9kg076110@rina.r.dl.itc.u-tokyo.ac.jp> <200202232051.g1NKpE741310@apollo.backplane.com> <20020223211449.GJ80761@elvis.mu.org> <200202232243.g1NMhZP49110@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202232243.g1NMhZP49110@apollo.backplane.com>; from dillon@apollo.backplane.com on Sat, Feb 23, 2002 at 02:43:35PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Apparently, On Sat, Feb 23, 2002 at 02:43:35PM -0800, Matthew Dillon said words to the effect of; > This is approximately what I am thinking. Note that this gives us the > flexibility to create a larger infrastructure around the bucket cache, > such as implement per-cpu caches and so on and so forth. What I have > here is the minimal implementation. > > -Matt Jeff Roberson (jeff@) has been working on a slab allocator that goes a long way to making malloc(), free() and the zone allocator not require giant. I've reviewed what he's got so far and it looks pretty damn good to me, I'll see about getting him to post it. He's working on adding the per-cpu queues now. Jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 15:55: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 0B8E337B402; Sat, 23 Feb 2002 15:54:59 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id KAA30541; Sun, 24 Feb 2002 10:54:51 +1100 Date: Sun, 24 Feb 2002 10:55:08 +1100 (EST) From: Bruce Evans X-X-Sender: To: Matthew Dillon Cc: Terry Lambert , Alfred Perlstein , Bosko Milekic , Seigo Tanimura , , John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) In-Reply-To: <200202232312.g1NNCaH54765@apollo.backplane.com> Message-ID: <20020224105118.L30818-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 23 Feb 2002, Matthew Dillon wrote: > critical_enter() isn't much better then a mutex. It can > be optimized to get rid of the inline cli & sti however. Actually, it > can be optimized trivially for i386, all we have to do is check the > critical nesting count from the interrupt code and set the > interrupts-disabled bit in the returned (supervisor mode) frame. > > critical_enter() and critical_exit() would then be nearly perfect. My version of it does less than this. I only use it to help implement spinlocks. Index: kern_switch.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_switch.c,v retrieving revision 1.20 diff -u -2 -r1.20 kern_switch.c --- kern_switch.c 11 Feb 2002 20:37:51 -0000 1.20 +++ kern_switch.c 13 Feb 2002 05:34:20 -0000 @@ -70,14 +70,21 @@ } -/* Critical sections that prevent preemption. */ +/*- + * Critical section handling. + * XXX doesn't belong here. + * + * Entering a critical section only blocks non-fast interrupts. + * critical_enter() is similar to splhigh() in a 2-level spl setup under + * old versions of FreeBSD. + * + * Exiting from all critical sections unblocks non-fast interrupts and runs + * the handlers of any that were blocked. critical_exit() is similar to + * spl(old_level) in a 2-level spl setup under old versions of FreeBSD. + */ void critical_enter(void) { - struct thread *td; - td = curthread; - if (td->td_critnest == 0) - td->td_savecrit = cpu_critical_enter(); - td->td_critnest++; + curthread->td_critnest++; } @@ -85,12 +92,7 @@ critical_exit(void) { - struct thread *td; - td = curthread; - if (td->td_critnest == 1) { - td->td_critnest = 0; - cpu_critical_exit(td->td_savecrit); - } else - td->td_critnest--; + if (--curthread->td_critnest == 0 && (ipending | spending) != 0) + unpend(); } Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 16: 3:14 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4CE9C37B400; Sat, 23 Feb 2002 16:03:09 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1O036164477; Sat, 23 Feb 2002 16:03:06 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Feb 2002 16:03:06 -0800 (PST) From: Matthew Dillon Message-Id: <200202240003.g1O036164477@apollo.backplane.com> To: Bruce Evans Cc: Terry Lambert , Alfred Perlstein , Bosko Milekic , Seigo Tanimura , , John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) References: <20020224105118.L30818-100000@gamplex.bde.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :My version of it does less than this. I only use it to help implement :spinlocks. You put together infrastructure to deal with pending pci interrupts? If so, then why not commit it (or at least commit a version #ifdef'd for the i386 architecture). -Matt Matthew Dillon :Index: kern_switch.c :=================================================================== :RCS file: /home/ncvs/src/sys/kern/kern_switch.c,v :retrieving revision 1.20 :diff -u -2 -r1.20 kern_switch.c :--- kern_switch.c 11 Feb 2002 20:37:51 -0000 1.20 :+++ kern_switch.c 13 Feb 2002 05:34:20 -0000 :@@ -70,14 +70,21 @@ : } : :-/* Critical sections that prevent preemption. */ :+/*- :+ * Critical section handling. :+ * XXX doesn't belong here. :+ * :+ * Entering a critical section only blocks non-fast interrupts. :+ * critical_enter() is similar to splhigh() in a 2-level spl setup under :+ * old versions of FreeBSD. :+ * :+ * Exiting from all critical sections unblocks non-fast interrupts and runs :+ * the handlers of any that were blocked. critical_exit() is similar to :+ * spl(old_level) in a 2-level spl setup under old versions of FreeBSD. :+ */ : void : critical_enter(void) : { :- struct thread *td; : :- td = curthread; :- if (td->td_critnest == 0) :- td->td_savecrit = cpu_critical_enter(); :- td->td_critnest++; :+ curthread->td_critnest++; : } : :@@ -85,12 +92,7 @@ : critical_exit(void) : { :- struct thread *td; : :- td = curthread; :- if (td->td_critnest == 1) { :- td->td_critnest = 0; :- cpu_critical_exit(td->td_savecrit); :- } else :- td->td_critnest--; :+ if (--curthread->td_critnest == 0 && (ipending | spending) != 0) :+ unpend(); : } : :Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 16: 8:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from coc-ias.coc-snt.com.br (200-206-240-101.dsl.telesp.net.br [200.206.240.101]) by hub.freebsd.org (Postfix) with ESMTP id 5055F37B405; Sat, 23 Feb 2002 16:08:22 -0800 (PST) Received: from portugalmail.com (1Cust46.tnt59.dfw5.da.uu.net [67.203.43.46]) by coc-ias.coc-snt.com.br (8.11.1/8.8.7) with SMTP id g1O19DT15262; Sat, 23 Feb 2002 22:09:16 -0300 Message-Id: <200202240109.g1O19DT15262@coc-ias.coc-snt.com.br> To: From: d7354@portugalmail.com Subject: Burn fat with no effort Date: Sat, 23 Feb 2002 19:00:51 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Tone your Abs, Thighs, Arms, and more with NO EFFORT ! Don't have time to workout? Tired of all those products that have you get down on the floor? Tired of backaches caused by sit-ups!? NO MORE... READ ON! *TRIM AND TONE YOUR TUMMY IN TIME FOR THE SUMMER! *WORKOUT WHILE WATCHING TV, AT THE COMPUTER, OR EVEN AT THE MALL! *TONE YOUR MUSCLES WHILE AT WORK, HOME, OR EVEN ON THE ROAD! *EAT WHAT YOU WANT THIS HOLIDAY SEASON THEN SHED THE EXTRA FAT! *LOOK AMAZING IN YOUR BEACH WEAR NEXT SUMMER! For complete information: http://www2.software4you2002.com/tv/ Bonus! Order by February 28, 2002 and receive your choice of one of the following "FREE Gifts". 1. Satellite System. $149.95 Value! 2. Digital Cellular Phone. $99.95 Value! +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ To opt-Out: http://www2.software4you2002.com/options To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 16:28:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 5DA2737B404; Sat, 23 Feb 2002 16:28:37 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id g1O0Sbb82131; Sat, 23 Feb 2002 16:28:37 -0800 (PST) (envelope-from david) Date: Sat, 23 Feb 2002 16:28:37 -0800 (PST) From: David Wolfskill Message-Id: <200202240028.g1O0Sbb82131@bunrab.catwhisker.org> To: current@FreeBSD.ORG, msmith@hub.freebsd.org Subject: Re: HEADS UP: ACPI CA updated In-Reply-To: <20020222215647.A54975@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Date: Fri, 22 Feb 2002 21:56:47 -0800 >From: Mike Smith >I've finally updated the ACPI CA codebase with Intel's 20020214 drop Yay...! >There aren't many changes in the FreeBSD-specific code, this is just >catching up with major improvements in the interpreter. >As usual, please report any problems or success to the list. Well, I see that the code is now able to distinguish between "battery 1 not present" vs. "battery 1 drained" (at least for my laptop) -- seems like progress! Thanks, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 16:37:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id DB65C37B402; Sat, 23 Feb 2002 16:37:39 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id A872EAE2D8; Sat, 23 Feb 2002 16:37:39 -0800 (PST) Date: Sat, 23 Feb 2002 16:37:39 -0800 From: Alfred Perlstein To: Matthew Dillon Cc: Bosko Milekic , Seigo Tanimura , current@FreeBSD.ORG, John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) Message-ID: <20020224003739.GL80761@elvis.mu.org> References: <200201051752.g05Hq3gG074525@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <200201241022.g0OAMISM093913@faber.r.dl.itc.u-tokyo.ac.jp> <20020124024534.V13686@elvis.mu.org> <200202131739.g1DHdZT5023794@rina.r.dl.itc.u-tokyo.ac.jp> <200202190945.g1J9j9kg076110@rina.r.dl.itc.u-tokyo.ac.jp> <200202232051.g1NKpE741310@apollo.backplane.com> <20020223211449.GJ80761@elvis.mu.org> <200202232243.g1NMhZP49110@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200202232243.g1NMhZP49110@apollo.backplane.com> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Matthew Dillon [020223 14:43] wrote: > This is approximately what I am thinking. Note that this gives us the > flexibility to create a larger infrastructure around the bucket cache, > such as implement per-cpu caches and so on and so forth. What I have > here is the minimal implementation. I strongly object to this implementation right now, please do not commit it. I already explained to you how to make the problem go away but instead you insist on some complex api that pins memory down like the damn zone allocator. It's not needed, so please don't do it. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 16:41:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9E90437B419; Sat, 23 Feb 2002 16:41:08 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1O0f8G86153; Sat, 23 Feb 2002 16:41:08 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Feb 2002 16:41:08 -0800 (PST) From: Matthew Dillon Message-Id: <200202240041.g1O0f8G86153@apollo.backplane.com> To: Alfred Perlstein Cc: Bosko Milekic , Seigo Tanimura , current@FreeBSD.ORG, John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) References: <200201051752.g05Hq3gG074525@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <200201241022.g0OAMISM093913@faber.r.dl.itc.u-tokyo.ac.jp> <20020124024534.V13686@elvis.mu.org> <200202131739.g1DHdZT5023794@rina.r.dl.itc.u-tokyo.ac.jp> <200202190945.g1J9j9kg076110@rina.r.dl.itc.u-tokyo.ac.jp> <200202232051.g1NKpE741310@apollo.backplane.com> <20020223211449.GJ80761@elvis.mu.org> <200202232243.g1NMhZP49110@apollo.backplane.com> <20020224003739.GL80761@elvis.mu.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :* Matthew Dillon [020223 14:43] wrote: :> This is approximately what I am thinking. Note that this gives us the :> flexibility to create a larger infrastructure around the bucket cache, :> such as implement per-cpu caches and so on and so forth. What I have :> here is the minimal implementation. : :I strongly object to this implementation right now, please do not :commit it. I already explained to you how to make the problem :go away but instead you insist on some complex api that pins :memory down like the damn zone allocator. It's not needed, so :please don't do it. : :-Alfred Woa! Timeout! I'm not planning on comitting any sort of malloc thingy. That was a 10 second thought experiment. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 16:43:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 67A9E37B404; Sat, 23 Feb 2002 16:43:47 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 27AF3AE2E0; Sat, 23 Feb 2002 16:43:47 -0800 (PST) Date: Sat, 23 Feb 2002 16:43:47 -0800 From: Alfred Perlstein To: Matthew Dillon Cc: Bosko Milekic , Seigo Tanimura , current@FreeBSD.ORG, John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) Message-ID: <20020224004347.GN80761@elvis.mu.org> References: <200201241022.g0OAMISM093913@faber.r.dl.itc.u-tokyo.ac.jp> <20020124024534.V13686@elvis.mu.org> <200202131739.g1DHdZT5023794@rina.r.dl.itc.u-tokyo.ac.jp> <200202190945.g1J9j9kg076110@rina.r.dl.itc.u-tokyo.ac.jp> <200202232051.g1NKpE741310@apollo.backplane.com> <20020223211449.GJ80761@elvis.mu.org> <200202232243.g1NMhZP49110@apollo.backplane.com> <20020224003739.GL80761@elvis.mu.org> <200202240041.g1O0f8G86153@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200202240041.g1O0f8G86153@apollo.backplane.com> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Matthew Dillon [020223 16:41] wrote: > > : > :* Matthew Dillon [020223 14:43] wrote: > :> This is approximately what I am thinking. Note that this gives us the > :> flexibility to create a larger infrastructure around the bucket cache, > :> such as implement per-cpu caches and so on and so forth. What I have > :> here is the minimal implementation. > : > :I strongly object to this implementation right now, please do not > :commit it. I already explained to you how to make the problem > :go away but instead you insist on some complex api that pins > :memory down like the damn zone allocator. It's not needed, so > :please don't do it. > : > :-Alfred > > Woa! Timeout! I'm not planning on comitting any sort of malloc thingy. > That was a 10 second thought experiment. Usually when I see diff(1) output from you I usually expect a commit within the next half hour or so, I just wanted to make myself clear on the issue. No worries. :) Yes, and hopefully JeffR's allocator will fix our problems, that is if it ever makes it out of p4. :) -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 16:49: 8 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 58DE437B400; Sat, 23 Feb 2002 16:49:02 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id LAA00511; Sun, 24 Feb 2002 11:48:55 +1100 Date: Sun, 24 Feb 2002 11:49:12 +1100 (EST) From: Bruce Evans X-X-Sender: To: Matthew Dillon Cc: Terry Lambert , Alfred Perlstein , Bosko Milekic , Seigo Tanimura , , John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) In-Reply-To: <200202240003.g1O036164477@apollo.backplane.com> Message-ID: <20020224111043.W30980-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 23 Feb 2002, Matthew Dillon wrote: > :My version of it does less than this. I only use it to help implement > :spinlocks. > > You put together infrastructure to deal with pending pci interrupts? > If so, then why not commit it (or at least commit a version #ifdef'd > for the i386 architecture). It's too messy and unfinished (doesn't work right for SMP or irqs >= 16), and dificult to untangle from my other patches. I posted these partial ones to attempt to inhibit() recomplication of the current critical* functions in directions that I don't want to go :-). > :Index: kern_switch.c > :=================================================================== > :RCS file: /home/ncvs/src/sys/kern/kern_switch.c,v > :retrieving revision 1.20 > :diff -u -2 -r1.20 kern_switch.c > :--- kern_switch.c 11 Feb 2002 20:37:51 -0000 1.20 > :+++ kern_switch.c 13 Feb 2002 05:34:20 -0000 > :@@ -70,14 +70,21 @@ > : } > : > :-/* Critical sections that prevent preemption. */ > :+/*- > :+ * Critical section handling. > :+ * XXX doesn't belong here. > :+ * > :+ * Entering a critical section only blocks non-fast interrupts. > :+ * critical_enter() is similar to splhigh() in a 2-level spl setup under > :+ * old versions of FreeBSD. > :+ * > :+ * Exiting from all critical sections unblocks non-fast interrupts and runs > :+ * the handlers of any that were blocked. critical_exit() is similar to > :+ * spl(old_level) in a 2-level spl setup under old versions of FreeBSD. > :+ */ > : void > : critical_enter(void) > : { > :- struct thread *td; > : > :- td = curthread; > :- if (td->td_critnest == 0) > :- td->td_savecrit = cpu_critical_enter(); > :- td->td_critnest++; > :+ curthread->td_critnest++; > : } > : > :@@ -85,12 +92,7 @@ > : critical_exit(void) > : { > :- struct thread *td; > : > :- td = curthread; > :- if (td->td_critnest == 1) { > :- td->td_critnest = 0; > :- cpu_critical_exit(td->td_savecrit); > :- } else > :- td->td_critnest--; > :+ if (--curthread->td_critnest == 0 && (ipending | spending) != 0) > :+ unpend(); > : } ipending here works much as in RELENG_4. It is ORed into by sched_ithd() if curthread->td_critnest != 0. Nothing special is needed for pci (the ICU masks pending interrupts). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 16:50:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 80BF937B402; Sat, 23 Feb 2002 16:49:50 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1O0noD15327; Sat, 23 Feb 2002 16:49:50 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Feb 2002 16:49:50 -0800 (PST) From: Matthew Dillon Message-Id: <200202240049.g1O0noD15327@apollo.backplane.com> To: Bruce Evans , Terry Lambert , Alfred Perlstein , Bosko Milekic , Seigo Tanimura , , John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) References: <20020224105118.L30818-100000@gamplex.bde.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bruce, I've looked at the vector assembly and it looks like cleaning up critical_enter() and critical_exit() for i386 ought to be simple. If you have a complete patch set I would like to see it posted for review or comitted, or if you don't want to deal with the commit I would love to have it so I can bang it into shape for commit. Having a sleek critical_enter()/critical_exit() would double sched_lock's performance. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 16:51: 6 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9F52237B405; Sat, 23 Feb 2002 16:51:04 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1O0p3E16932; Sat, 23 Feb 2002 16:51:03 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Feb 2002 16:51:03 -0800 (PST) From: Matthew Dillon Message-Id: <200202240051.g1O0p3E16932@apollo.backplane.com> To: Bruce Evans Cc: Terry Lambert , Alfred Perlstein , Bosko Milekic , Seigo Tanimura , , John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) References: <20020224111043.W30980-100000@gamplex.bde.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :On Sat, 23 Feb 2002, Matthew Dillon wrote: : :> :My version of it does less than this. I only use it to help implement :> :spinlocks. :> :> You put together infrastructure to deal with pending pci interrupts? :> If so, then why not commit it (or at least commit a version #ifdef'd :> for the i386 architecture). : :It's too messy and unfinished (doesn't work right for SMP or irqs >= 16), :and dificult to untangle from my other patches. I posted these partial :ones to attempt to inhibit() recomplication of the current critical* :functions in directions that I don't want to go :-). Oh, ok. Hmm. Well, do you mind if I throw together an interrupt-set-cli- in-return-frame patch set? I think it would wind up being just as fast. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 17:55: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C4CBE37B402; Sat, 23 Feb 2002 17:54:58 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1O1suv36741; Sat, 23 Feb 2002 17:54:56 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Feb 2002 17:54:56 -0800 (PST) From: Matthew Dillon Message-Id: <200202240154.g1O1suv36741@apollo.backplane.com> To: Bruce Evans Cc: Terry Lambert , Alfred Perlstein , Bosko Milekic , Seigo Tanimura , , John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) References: <20020224111043.W30980-100000@gamplex.bde.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :It's too messy and unfinished (doesn't work right for SMP or irqs >= 16), :and dificult to untangle from my other patches. I posted these partial :ones to attempt to inhibit() recomplication of the current critical* :functions in directions that I don't want to go :-). :... : :ipending here works much as in RELENG_4. It is ORed into by sched_ithd() :if curthread->td_critnest != 0. Nothing special is needed for pci :(the ICU masks pending interrupts). : :Bruce Ok, I have most of it coded up. Could you explain what 'spending' was for? I am doing it slightly different then you. To avoid having to use locked instructions I have placed ipending in the thread structure: void critical_enter(void) { struct thread *td = curthread; ++td->td_critnest; } void critical_exit(void) { struct thread *td = curthread; KASSERT(td->td_critnest > 0, ("bad td_critnest value!")); if (--td->td_critnest == 0) { if (td->td_ipending) unpend(); } } The apic and icu vector code will do a simple td_critnest test and OR the irq bit into td->td_ipending (it conveniently already has the struct thread in %ebx). And the vector code will also check and handle any non-zero td_ipending if critnest is 0, handling the 1->0 transition/preemption race. I'll post the patch when it gets a little further along. How should I deal with fast interrupts? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 17:59:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 13BBE37B402; Sat, 23 Feb 2002 17:59:46 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id MAA03882; Sun, 24 Feb 2002 12:59:39 +1100 Date: Sun, 24 Feb 2002 12:59:55 +1100 (EST) From: Bruce Evans X-X-Sender: To: Matthew Dillon Cc: Terry Lambert , Alfred Perlstein , Bosko Milekic , Seigo Tanimura , , John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) In-Reply-To: <200202240049.g1O0noD15327@apollo.backplane.com> Message-ID: <20020224125005.N31250-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 23 Feb 2002, Matthew Dillon wrote: > Bruce, I've looked at the vector assembly and it looks like cleaning > up critical_enter() and critical_exit() for i386 ought to be simple. > > If you have a complete patch set I would like to see it posted for > review or comitted, or if you don't want to deal with the commit I > would love to have it so I can bang it into shape for commit. Patches for most of my sys tree are in sys.tar.gz in my home directory on freefall. > Having a sleek critical_enter()/critical_exit() would double sched_lock's > performance. I'm not sure about that. Perhaps I've already optimized sched_lock enough that I don't notice. My changes were actually directed at avoiding sched_lock's interrupt latency and it wasn't until the critical_enter()/ exit() calls pessimized mtx_{lock,unlock}_spin in -current that I managed to share enough code (the critnest increment/decrement) to avoid losing efficiency. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 18: 8:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 76AA037B404; Sat, 23 Feb 2002 18:08:15 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id NAA04292; Sun, 24 Feb 2002 13:08:09 +1100 Date: Sun, 24 Feb 2002 13:08:26 +1100 (EST) From: Bruce Evans X-X-Sender: To: Matthew Dillon Cc: Terry Lambert , Alfred Perlstein , Bosko Milekic , Seigo Tanimura , , John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) In-Reply-To: <200202240051.g1O0p3E16932@apollo.backplane.com> Message-ID: <20020224130010.W31250-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 23 Feb 2002, Matthew Dillon wrote: > :It's too messy and unfinished (doesn't work right for SMP or irqs >= 16), > :and dificult to untangle from my other patches. I posted these partial > :ones to attempt to inhibit() recomplication of the current critical* > :functions in directions that I don't want to go :-). > > Oh, ok. Hmm. Well, do you mind if I throw together an interrupt-set-cli- > in-return-frame patch set? I think it would wind up being just as fast. I don't see how that would work. We need to call critical_enter() from ordinary code, so there is no free frame pop. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 18:18:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 973C337B402; Sat, 23 Feb 2002 18:18:43 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1O2IfL40500; Sat, 23 Feb 2002 18:18:41 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Feb 2002 18:18:41 -0800 (PST) From: Matthew Dillon Message-Id: <200202240218.g1O2IfL40500@apollo.backplane.com> To: Bruce Evans Cc: Terry Lambert , Alfred Perlstein , Bosko Milekic , Seigo Tanimura , , John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) References: <20020224130010.W31250-100000@gamplex.bde.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :On Sat, 23 Feb 2002, Matthew Dillon wrote: : :> :It's too messy and unfinished (doesn't work right for SMP or irqs >= 16), :> :and dificult to untangle from my other patches. I posted these partial :> :ones to attempt to inhibit() recomplication of the current critical* :> :functions in directions that I don't want to go :-). :> :> Oh, ok. Hmm. Well, do you mind if I throw together an interrupt-set-cli- :> in-return-frame patch set? I think it would wind up being just as fast. : :I don't see how that would work. We need to call critical_enter() from :ordinary code, so there is no free frame pop. : :Bruce I'm trying it your way, with an ipending variable. The set-cli-in-return-frame mechanism would only work well for level interrupts. Basically the interrupt occurs and you set PS_I in the return frame (that was pushed on entry to the interrupt). critical_exit() would then detect the 1->0 transition and simply STI. But since we have a combination of level and edge it gets too messy for my tastes, so I'm trying it with an ipending variable. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 18:55:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 2AD8437B402; Sat, 23 Feb 2002 18:55:18 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id NAA06661; Sun, 24 Feb 2002 13:55:10 +1100 Date: Sun, 24 Feb 2002 13:55:27 +1100 (EST) From: Bruce Evans X-X-Sender: To: Matthew Dillon Cc: Terry Lambert , Alfred Perlstein , Bosko Milekic , Seigo Tanimura , , John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) In-Reply-To: <200202240154.g1O1suv36741@apollo.backplane.com> Message-ID: <20020224131027.I31343-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 23 Feb 2002, Matthew Dillon wrote: > :ipending here works much as in RELENG_4. It is ORed into by sched_ithd() > :if curthread->td_critnest != 0. Nothing special is needed for pci > :(the ICU masks pending interrupts). > : > :Bruce > > Ok, I have most of it coded up. Could you explain what 'spending' > was for? Like the SWI bits in ipending in RELENG_4. In RELENG_4, we have to pass around all the bits to spl*(), so we had to pack them in at least some places (not required in inpending, but efficient). In -current, packing is not so important even if it is possible, so I didn't attempt it. > I am doing it slightly different then you. To avoid having to use > locked instructions I have placed ipending in the thread structure: Mine is global partly for historical reasons. BTW, I've found that variables in the thread struct are more fragile than per-cpu globals. You have to remember to deal with them all before you switch threads. I needed to clone td_critnest to the next thread in one or two places (at least one related to the complications for forking). > > void > critical_enter(void) > { > struct thread *td = curthread; > ++td->td_critnest; > } > > void > critical_exit(void) > { > struct thread *td = curthread; > KASSERT(td->td_critnest > 0, ("bad td_critnest value!")); > if (--td->td_critnest == 0) { > if (td->td_ipending) > unpend(); > } > } > > The apic and icu vector code will do a simple td_critnest test and > OR the irq bit into td->td_ipending (it conveniently already has > the struct thread in %ebx). And the vector code will also check and I do this at the start of sched_ithd(). This is efficient enough because the nested case is rare. > handle any non-zero td_ipending if critnest is 0, handling the > 1->0 transition/preemption race. > > I'll post the patch when it gets a little further along. > > How should I deal with fast interrupts? Hmm, this gets complicated. First, you need the td_critnest test in Xfastintr* (do it before Xfastintr* calls critical_enter()). It is important in -current (although bad for latency) that critical_enter() keeps masking even fast interupts although it doesn't do it in software). Next, you need to mask the fast interrupt. It probably needs to be masked in the ICU/APIC on i386's, so it will become not-so-fast. Finally, unpend() needs to do more for fast interrupts: - give them highest priority - unmask the in the ICU/APIC/wherever, either before or after calling the handler. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 19:30:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1BED637B405; Sat, 23 Feb 2002 19:30:27 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1O3UO189713; Sat, 23 Feb 2002 19:30:24 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Feb 2002 19:30:24 -0800 (PST) From: Matthew Dillon Message-Id: <200202240330.g1O3UO189713@apollo.backplane.com> To: Bruce Evans Cc: Terry Lambert , Alfred Perlstein , Bosko Milekic , Seigo Tanimura , , John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) References: <20020224131027.I31343-100000@gamplex.bde.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :> :(the ICU masks pending interrupts). :> : :> :Bruce :> :> Ok, I have most of it coded up. Could you explain what 'spending' :> was for? : :Like the SWI bits in ipending in RELENG_4. In RELENG_4, we have to pass :around all the bits to spl*(), so we had to pack them in at least some :places (not required in inpending, but efficient). In -current, packing :is not so important even if it is possible, so I didn't attempt it. : :> I am doing it slightly different then you. To avoid having to use :> locked instructions I have placed ipending in the thread structure: : :Mine is global partly for historical reasons. BTW, I've found that :variables in the thread struct are more fragile than per-cpu globals. :You have to remember to deal with them all before you switch threads. :I needed to clone td_critnest to the next thread in one or two places :(at least one related to the complications for forking). Ah, task switching... that's a stickymess. In that case, I think placing it in a per-cpu variable is the correct solution. I can still avoid the locked bus cycle. I dealt with the fork issue by having the trampoline code setup td_critnest before doing to the sti, since it is far too late to setup critnest in fork_exit. :> OR the irq bit into td->td_ipending (it conveniently already has :> the struct thread in %ebx). And the vector code will also check and : :I do this at the start of sched_ithd(). This is efficient enough because :the nested case is rare. Yup, same here. :> handle any non-zero td_ipending if critnest is 0, handling the :> 1->0 transition/preemption race. :> :> I'll post the patch when it gets a little further along. :> :> How should I deal with fast interrupts? : :Hmm, this gets complicated. First, you need the td_critnest test :in Xfastintr* (do it before Xfastintr* calls critical_enter()). It is :important in -current (although bad for latency) that critical_enter() :keeps masking even fast interupts although it doesn't do it in software). :Next, you need to mask the fast interrupt. It probably needs to be :masked in the ICU/APIC on i386's, so it will become not-so-fast. Finally, :unpend() needs to do more for fast interrupts: :- give them highest priority :- unmask the in the ICU/APIC/wherever, either before or after calling the : handler. : :Bruce This is fairly straightforward. I will give the per-cpu area a separate pending variable for fast interrupts and maybe a master 'some kind of interrupt is pending' flag for critical_exit() to test. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 20:25:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 505E937B404 for ; Sat, 23 Feb 2002 20:25:25 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g1O4PFPA110844; Sat, 23 Feb 2002 23:25:16 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Sat, 23 Feb 2002 23:25:14 -0500 To: Dag-Erling Smorgrav , current@FreeBSD.org From: Garance A Drosihn Subject: Re: -CURRENT in pretty good shape, after all Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 6:24 PM +0100 2/23/02, Dag-Erling Smorgrav wrote: >Thumbs up and big cheers to all of you (well, us) guys working on >-CURRENT. It's pretty stable and has been for a while now - and >even on my poor old 350 MHz K6-2, it performs well enough to make >a kickass desktop & development platform. Let's hope it'll only >get better from here on out :) It is working fairly well for me too, on a dual-pentium machine. I can't get vmware2 working, but most of everything else that I do is working, and I'm not running into any mysterious crashes. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 20:42:26 2002 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id B51FA37B402; Sat, 23 Feb 2002 20:42:19 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g1O4gDi18006; Sat, 23 Feb 2002 21:42:13 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g1O4gCL08226; Sat, 23 Feb 2002 21:42:12 -0700 (MST) (envelope-from imp@village.org) Date: Sat, 23 Feb 2002 21:41:52 -0700 (MST) Message-Id: <20020223.214152.103234640.imp@village.org> To: gnn@neville-neil.com Cc: freebsd-smp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: TWiki as promised... From: "M. Warner Losh" In-Reply-To: <200202221920.LAA704177@meer.meer.net> References: <200202221920.LAA704177@meer.meer.net> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG So how do I add NewCard project to this TWiki? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 21: 2: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from outboundx.mv.meer.net (outboundx.mv.meer.net [209.157.152.12]) by hub.freebsd.org (Postfix) with ESMTP id BA5D137B402; Sat, 23 Feb 2002 21:02:05 -0800 (PST) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by outboundx.mv.meer.net (8.11.6/8.11.6) with ESMTP id g1O521s26456; Sat, 23 Feb 2002 21:02:01 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from neville-neil.com ([209.157.133.226]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id VAA894540; Sat, 23 Feb 2002 21:01:38 -0800 (PST) Message-Id: <200202240501.VAA894540@meer.meer.net> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: "M. Warner Losh" Cc: freebsd-smp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: TWiki as promised... In-Reply-To: Message from "M. Warner Losh" of "Sat, 23 Feb 2002 21:41:52 MST." <20020223.214152.103234640.imp@village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 23 Feb 2002 21:01:38 -0800 From: "George V. Neville-Neil" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > So how do I add NewCard project to this TWiki? > Go into the CurrentProjects area and edit the page. Add a WikiWord that's something like NewCard. You'll see that when you're done editing the new word shows up as an incomplete link (It has a ? at the end). Click on the ? and then you get a fresh page. Add whatever you like to it. Later, George -- George V. Neville-Neil gnn@neville-neil.com NIC:GN82 "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 21:12:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id B110137B402; Sat, 23 Feb 2002 21:12:19 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 8CBF85343; Sun, 24 Feb 2002 06:12:17 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "George V. Neville-Neil" Cc: "M. Warner Losh" , freebsd-smp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: TWiki as promised... References: <200202240501.VAA894540@meer.meer.net> From: Dag-Erling Smorgrav Date: 24 Feb 2002 06:12:17 +0100 In-Reply-To: <200202240501.VAA894540@meer.meer.net> Message-ID: Lines: 7 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Would you mind changing the description of the twiki to something else than "where all FreeBSD collaboration happens"? It might give people the wrong impression. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 21:18:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from outboundx.mv.meer.net (outboundx.mv.meer.net [209.157.152.12]) by hub.freebsd.org (Postfix) with ESMTP id 2872137B400; Sat, 23 Feb 2002 21:18:05 -0800 (PST) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by outboundx.mv.meer.net (8.11.6/8.11.6) with ESMTP id g1O5I1s26576; Sat, 23 Feb 2002 21:18:01 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from neville-neil.com ([209.157.133.226]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id VAA897648; Sat, 23 Feb 2002 21:17:28 -0800 (PST) Message-Id: <200202240517.VAA897648@meer.meer.net> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Dag-Erling Smorgrav Cc: "M. Warner Losh" , freebsd-smp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: TWiki as promised... In-Reply-To: Message from Dag-Erling Smorgrav of "24 Feb 2002 06:12:17 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 23 Feb 2002 21:17:28 -0800 From: "George V. Neville-Neil" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Would you mind changing the description of the twiki to something else > than "where all FreeBSD collaboration happens"? It might give people > the wrong impression. Sure. Suggestions? I don't mind what people put into this, that's much of the point. It's just a place holder. Remember, anyone can edit, it's social pressure that keeps things from a state of chaos. Anyways, what would people like? Later, George -- George V. Neville-Neil gnn@neville-neil.com NIC:GN82 "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 22: 0:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 0A5C437B402; Sat, 23 Feb 2002 22:00:11 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 930CB5341; Sun, 24 Feb 2002 07:00:08 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "George V. Neville-Neil" Cc: "M. Warner Losh" , freebsd-smp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: TWiki as promised... References: <200202240517.VAA897648@meer.meer.net> From: Dag-Erling Smorgrav Date: 24 Feb 2002 07:00:07 +0100 In-Reply-To: <200202240517.VAA897648@meer.meer.net> Message-ID: Lines: 10 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "George V. Neville-Neil" writes: > Anyways, what would people like? "Information and discussions about various FreeBSD subprojects"? BTW, why don't you want a FreeBSD WikiTerm? DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 22: 8: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from outboundx.mv.meer.net (outboundx.mv.meer.net [209.157.152.12]) by hub.freebsd.org (Postfix) with ESMTP id 5841637B402; Sat, 23 Feb 2002 22:08:05 -0800 (PST) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by outboundx.mv.meer.net (8.11.6/8.11.6) with ESMTP id g1O681s26953; Sat, 23 Feb 2002 22:08:01 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from neville-neil.com ([209.157.133.226]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id WAA929178; Sat, 23 Feb 2002 22:07:52 -0800 (PST) Message-Id: <200202240607.WAA929178@meer.meer.net> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Dag-Erling Smorgrav Cc: "M. Warner Losh" , freebsd-smp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: TWiki as promised... In-Reply-To: Message from Dag-Erling Smorgrav of "24 Feb 2002 07:00:07 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 23 Feb 2002 22:07:52 -0800 From: "George V. Neville-Neil" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > "Information and discussions about various FreeBSD subprojects"? Sounds good. Check that in there. > BTW, why don't you want a FreeBSD WikiTerm? > Well it's a bit odd. Anywhere you put the word FreeBSD lights up as a link. I guess we could put a generic page under it or something but it's annoying (to me at least) to see FreeBSD as a link everywhere when it's mostly just a name. Later, George -- George V. Neville-Neil gnn@neville-neil.com NIC:GN82 "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 22:11:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id BA72037B404; Sat, 23 Feb 2002 22:11:46 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 1A8E55341; Sun, 24 Feb 2002 07:11:44 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "George V. Neville-Neil" Cc: "M. Warner Losh" , freebsd-smp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: TWiki as promised... References: <200202240607.WAA929178@meer.meer.net> From: Dag-Erling Smorgrav Date: 24 Feb 2002 07:11:44 +0100 In-Reply-To: <200202240607.WAA929178@meer.meer.net> Message-ID: Lines: 12 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "George V. Neville-Neil" writes: > > BTW, why don't you want a FreeBSD WikiTerm? > Well it's a bit odd. Anywhere you put the word FreeBSD lights up as a link. > I guess we could put a generic page under it or something but it's > annoying (to me at least) to see FreeBSD as a link everywhere when it's > mostly just a name. Pfooey. That's just the way Wiki works :) DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 23:27:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail-relay1.yahoo.com (mail-relay1.yahoo.com [216.145.48.34]) by hub.freebsd.org (Postfix) with ESMTP id D8E0D37B400 for ; Sat, 23 Feb 2002 23:27:38 -0800 (PST) Received: from DougBarton.net (12-234-22-238.client.attbi.com [12.234.22.238]) by mail-relay1.yahoo.com (Postfix) with ESMTP id EEDD38B5AE; Sat, 23 Feb 2002 23:27:37 -0800 (PST) Message-ID: <3C7895E9.A79E91CA@DougBarton.net> Date: Sat, 23 Feb 2002 23:27:37 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: David Wolfskill , current@FreeBSD.ORG, ggombert@imatowns.com Subject: Re: Install World fails in -Current References: <200202221338.g1MDceE75453@bunrab.catwhisker.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > David Wolfskill writes: > > Sounds like a botched (or not run) "mergemaster" execution: > > No - mergemaster will croak because it runs mtree to build its temp > directory, so if you're trying to update a pre-smmsp system you have > to add the smmsp user and group manually. Every time I suggest adding special handling for master.passwd or group people scream because they are afraid that they'll accidentally overwrite their files. Every time we introduce a new user or group, people scream because mm didn't magically fix things for them. One solution I've considered in the past is to have a pre-world mm option to do just master.passwd and group for just this purpose. One of the reasons I liked /etc/defaults/make.conf was because this pre-world script I have also compared my /etc/make.conf to the defaults to make sure that the options I have in there are still doing what I think they are doing. I'd kind of like to see this sort of thing return... it was nice to have a somewhat canonical list of options available. Doug -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 23 23:40:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from angelica.unixdaemons.com (angelica.unixdaemons.com [209.148.64.135]) by hub.freebsd.org (Postfix) with ESMTP id A274B37B402; Sat, 23 Feb 2002 23:40:25 -0800 (PST) Received: from angelica.unixdaemons.com (bmilekic@localhost.unixdaemons.com [127.0.0.1]) by angelica.unixdaemons.com (8.12.2/8.12.1) with ESMTP id g1O7eCh4035568; Sun, 24 Feb 2002 02:40:12 -0500 (EST) Received: (from bmilekic@localhost) by angelica.unixdaemons.com (8.12.2/8.12.1/Submit) id g1O7eBJb035566; Sun, 24 Feb 2002 02:40:11 -0500 (EST) (envelope-from bmilekic) Date: Sun, 24 Feb 2002 02:40:11 -0500 From: Bosko Milekic To: Matthew Dillon Cc: Terry Lambert , Alfred Perlstein , Seigo Tanimura , current@FreeBSD.ORG, John Baldwin Subject: Re: malloc_bucket() idea (was Re: How to fix malloc.) Message-ID: <20020224024011.A35319@unixdaemons.com> References: <200201241022.g0OAMISM093913@faber.r.dl.itc.u-tokyo.ac.jp> <20020124024534.V13686@elvis.mu.org> <200202131739.g1DHdZT5023794@rina.r.dl.itc.u-tokyo.ac.jp> <200202190945.g1J9j9kg076110@rina.r.dl.itc.u-tokyo.ac.jp> <200202232051.g1NKpE741310@apollo.backplane.com> <20020223211449.GJ80761@elvis.mu.org> <200202232243.g1NMhZP49110@apollo.backplane.com> <3C78200E.EC89C4E1@mindspring.com> <200202232312.g1NNCaH54765@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200202232312.g1NNCaH54765@apollo.backplane.com>; from dillon@apollo.backplane.com on Sat, Feb 23, 2002 at 03:12:36PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Feb 23, 2002 at 03:12:36PM -0800, Matthew Dillon wrote: > > :OTOH, A per CPU bucket list means no bucket mtx would be necessary; > :without that, it's just replacing one type of contention for another, > :I think, until you start making mutex selection indeterminate. 8^(. > : > :Really, this delayed freeing idea is starting to get uglier than > :just going to per CPU pools... > : > :-- Terry > > Well, if we want to rewrite malloc() a per-cpu pool inside a critical > section would not be that difficult. The 'bucket' array would > simply be placed in the per-cpu area. However, with malloc() we still > have a serious problem with the malloc_type structure statistics. There > would have to be per-cpu information for those as well. Someone (jeffr) is already working on a new allocator to hopefully [at least] eventually replace malloc(9) and various other kernel allocators. It will support per CPU working-sets and some cache friendly goodies. -- Bosko Milekic bmilekic@unixdaemons.com bmilekic@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message