From owner-freebsd-current Sun Aug 23 03:26:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA21180 for freebsd-current-outgoing; Sun, 23 Aug 1998 03:26:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA21174 for ; Sun, 23 Aug 1998 03:26:40 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id GAA15381 for ; Sun, 23 Aug 1998 06:25:56 -0400 (EDT) Date: Sun, 23 Aug 1998 06:25:55 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: current@FreeBSD.ORG Subject: crashed current, no panic Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I managed to crash yesterday's current by doing a 'make -j64 world > /tmp/world.out 2>&1 &' and not much more. There was no panic or anything, the build just died with some errors and then the machine rebooted. A few minutes earlier it had emitted a warning on the console that I needed more swap space, but it didn't look like I was using all my swap. Now make world dies here: --- cleandepend --- rm -f .depend /usr/src/usr.bin/tclsh/GRTAGS /usr/src/usr.bin/tclsh/GSYMS /usr/src/usr.bin/tclsh/GTAGS 1 error *** Error code 2 1 error *** Error code 2 1 error Deleting and re-cvsupping /usr/src/usr.bin didn't help. Any suggestions? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 04:47:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03295 for freebsd-current-outgoing; Sun, 23 Aug 1998 04:47:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA03278 for ; Sun, 23 Aug 1998 04:47:36 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id NAA15881; Sun, 23 Aug 1998 13:42:32 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id NAA07271; Sun, 23 Aug 1998 13:41:05 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808231141.NAA07271@semyam.dinoco.de> To: Kris Kennaway cc: Mike Smith , freebsd-current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: lpr code cleanup? (was: Re: gcc 2.8 ) In-reply-to: My message of "Sun, 23 Aug 1998 13:38:28 +0200." <199808231138.NAA06941@semyam.dinoco.de> Date: Sun, 23 Aug 1998 13:41:04 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While I looked at the code there I noticed other parts of the printing > system like lpq don't use CWARNFLAGS and just add -Wall. Shall I try ^^^ Sorry, make that lpd. Stefan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 04:48:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03448 for freebsd-current-outgoing; Sun, 23 Aug 1998 04:48:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA03418 for ; Sun, 23 Aug 1998 04:48:08 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id NAA15880; Sun, 23 Aug 1998 13:42:29 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id NAA06941; Sun, 23 Aug 1998 13:38:29 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808231138.NAA06941@semyam.dinoco.de> To: Kris Kennaway cc: Mike Smith , freebsd-current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: lpr code cleanup? (was: Re: gcc 2.8 ) In-reply-to: Your message of "Sun, 23 Aug 1998 12:47:34 +0930." Date: Sun, 23 Aug 1998 13:38:28 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Unfortunately I'm not a very experienced C/C++ coder; I doubt I would have > the skills to identify how to fix these problems, but I'll see if I can > would be able to do better, though. lpr (one of the bits which fails due > to warnings being treated as errors) is probably an easy target for > someone who has a good understanding of C semantics and standards; there's [Just did an experiment by checking out the lpr module, adding an empty Makefile.inc on which it insisted in the parent directory and then doing "CC=egcc make" there. Egcc was from sometime in July.] It's easy to explain. Some parts of the code like lpr itself use the macro CWARNFLAGS which include -Werror changing all warnings to errors. Now egcs sees "register i" in lpr.c which isn't nice, issues a warning and then it makes a loud *boom*. The compilation failed. :-( While I looked at the code there I noticed other parts of the printing system like lpq don't use CWARNFLAGS and just add -Wall. Shall I try to correct this and get it compile w/o any warnings? In the case above a "register int i" won't hurt. It's even OK for K&R compilers so I think such a change would be a good thing. If so how shall I set the warning flags? Use the more complete CWARNFLAGS in all parts of the printing system or leave it as it is now? Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 08:18:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25061 for freebsd-current-outgoing; Sun, 23 Aug 1998 08:18:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lambic.physics.montana.edu (lambic.physics.montana.edu [153.90.192.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25055; Sun, 23 Aug 1998 08:18:44 -0700 (PDT) (envelope-from handy@lambic.physics.montana.edu) Received: from localhost (handy@localhost) by lambic.physics.montana.edu (8.8.8/8.8.7) with SMTP id JAA00667; Sun, 23 Aug 1998 09:17:49 -0600 (MDT) (envelope-from handy@lambic.physics.montana.edu) Date: Sun, 23 Aug 1998 09:17:49 -0600 (MDT) From: Brian Handy To: "Jonathan M. Bresler" cc: freebsd-current@FreeBSD.ORG Subject: Re: Not receiving CVS commit messages In-Reply-To: <199808230336.UAA16220@hub.freebsd.org> Message-ID: X-files: The truth is out there MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> [Regarding CVS logs being broken up into several different lists] >> Since it took this long to get even one complaint, I doubt >> anyone's going to re-enable this again, soon... > > yep....seems that we sub-divided the lists to a greater > extent than nearly anyone wanted or needed. > > in fairness, i have to say that a couple people have > asked about it....less than 6 people. I have to agree, it was broken up probably a bit agressively and could be toned down some. For a while I was only following cvs-ports; I imagine some of the portsmeisters would go for that too. It would be nice to see that again, but I have no opinion on whether all the src/ subdivisions should return. Happy trails, Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 08:24:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25585 for freebsd-current-outgoing; Sun, 23 Aug 1998 08:24:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25574; Sun, 23 Aug 1998 08:24:03 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id LAA02470; Sun, 23 Aug 1998 11:23:13 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: wollman@FreeBSD.ORG CC: current@FreeBSD.ORG From: "Gary Palmer" Subject: -current broken by mbuf changes? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Aug 1998 11:23:13 -0400 Message-ID: <2466.903885793@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Did you forget to commit changes to keep userland in sync with the kernel? cc -O2 -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/mbuf.c /usr/src/usr.bin/netstat/mbuf.c:80: `MT_SOOPTS' undeclared here (not in a function) /usr/src/usr.bin/netstat/mbuf.c:80: initializer element for `mbtypes[7].mt_type' is not constant *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error I just commited a change which will allow it to compile, but I'm not sure if just commenting out the use of MT_SOOPTS is all that is needed... Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 10:41:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05979 for freebsd-current-outgoing; Sun, 23 Aug 1998 10:41:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05972 for ; Sun, 23 Aug 1998 10:41:17 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id NAA23791; Sun, 23 Aug 1998 13:40:06 -0400 (EDT) (envelope-from wollman) Date: Sun, 23 Aug 1998 13:40:06 -0400 (EDT) From: Garrett Wollman Message-Id: <199808231740.NAA23791@khavrinen.lcs.mit.edu> To: Stefan Eggers Cc: Kris Kennaway , Mike Smith , freebsd-current@FreeBSD.ORG Subject: lpr code cleanup? (was: Re: gcc 2.8 ) In-Reply-To: <199808231138.NAA06941@semyam.dinoco.de> References: <199808231138.NAA06941@semyam.dinoco.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > It's easy to explain. Some parts of the code like lpr itself use the > macro CWARNFLAGS which include -Werror changing all warnings to > errors. The intent of this was to make sure that anyone who introduced warnings after I had laboriously eliminated them would get pounded on by the -current regulars for breaking the build. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 11:22:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09921 for freebsd-current-outgoing; Sun, 23 Aug 1998 11:22:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09911; Sun, 23 Aug 1998 11:22:04 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id OAA17721; Sun, 23 Aug 1998 14:21:44 -0400 (EDT) Date: Sun, 23 Aug 1998 14:21:44 -0400 (EDT) From: Daniel Eischen Message-Id: <199808231821.OAA17721@pcnet1.pcnet.com> To: handy@lambic.physics.montana.edu, jmb@FreeBSD.ORG Subject: Re: Not receiving CVS commit messages Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > yep....seems that we sub-divided the lists to a greater > > extent than nearly anyone wanted or needed. > > > in fairness, i have to say that a couple people have > > asked about it....less than 6 people. > > I have to agree, it was broken up probably a bit agressively and could be > toned down some. For a while I was only following cvs-ports; I imagine > some of the portsmeisters would go for that too. It would be nice to see > that again, but I have no opinion on whether all the src/ subdivisions > should return. And I'd like to see src and _not_ ports. Perhaps at least a separate list for each? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 11:31:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10834 for freebsd-current-outgoing; Sun, 23 Aug 1998 11:31:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10827 for ; Sun, 23 Aug 1998 11:31:37 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id UAA27481 for ; Sun, 23 Aug 1998 20:35:22 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sun, 23 Aug 1998 20:35:21 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: Something changed in sendmail cf? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Recently I updated my machine to latest current, and noticed that my procmail stopped working - it seems it isn't even called by sendmail via .forward file (and it worked just fine before). I went as far as changing Mlocal definition in /etc/sendmail.cf, but it still doesn't work - all mail still goes to my /var/mail/abial. Where should I look now? What has changed with sendmail? What should I do to make it work? TIA Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 11:34:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11206 for freebsd-current-outgoing; Sun, 23 Aug 1998 11:34:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11198; Sun, 23 Aug 1998 11:34:15 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id NAA28603; Sun, 23 Aug 1998 13:33:19 -0500 (CDT) Message-ID: <19980823133318.33414@futuresouth.com> Date: Sun, 23 Aug 1998 13:33:18 -0500 From: "Matthew D. Fuller" To: Brian Handy Cc: "Jonathan M. Bresler" , freebsd-current@FreeBSD.ORG Subject: Re: Not receiving CVS commit messages References: <199808230336.UAA16220@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Brian Handy on Sun, Aug 23, 1998 at 09:17:49AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 23, 1998 at 09:17:49AM -0600, Brian Handy woke me up to tell me: > > I have to agree, it was broken up probably a bit agressively and could be > toned down some. For a while I was only following cvs-ports; I imagine > some of the portsmeisters would go for that too. It would be nice to see > that again, but I have no opinion on whether all the src/ subdivisions > should return. I'd think it'd be reasonable to have cvs-ports seperate... And a seperate list for src/sys too, since that's all a lot of people may want. We certainly didn't need a list for every subdir, though... *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 12:59:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16156 for freebsd-current-outgoing; Sun, 23 Aug 1998 12:59:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat0118.mpoweredpc.net [142.177.188.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16149 for ; Sun, 23 Aug 1998 12:59:47 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.8.8) with SMTP id QAA00542 for ; Sun, 23 Aug 1998 16:59:01 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 23 Aug 1998 16:59:00 -0300 (ADT) From: The Hermit Hacker To: current@FreeBSD.ORG Subject: AVA-1505 card for CDR...system hang... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Morning... The other day, I purchased an AVA-1505 SCSI card in order to move my external CD-R to a seperate SCSI bus, because I was having problems writing CDs. When the system boots, it recognizes the AVA and the CDR, but as soon as I get to a login prompt, if I try to do a mount of a known-to-work CD, it hangs and tells me that 'cd1 timed out', and just hangs there indefinitely. It *feels* like an IRQ conflict, except I can't find one looking through both a boot and a boot -v. The boot -v included here is for a system with just the NCR controller (boot drive(s)), video controller and the AVA-1505 controller. The operating system is 3.0-CURRENT as of yesterday, no CAM drivers. Can someone suggestion something that I'm overlooking here? Or is there a known problem with the 1505's that I missed? Thanks... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Sat Aug 22 20:20:58 ADT 1998 root@thelab.hub.org:/usr/src/sys/compile/thelab Calibrating clock(s) ... TSC clock: 149688012 Hz, i8254 clock: 1193168 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz cost 2530 ns CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 149690744 Hz cost 157 ns CPU: Pentium/P54C (149.69-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x001ff000 - 0x07ffdfff, 132116480 bytes (32255 pages) avail memory = 128253952 (125248K bytes) Found BIOS32 Service Directory header at 0xf00f8440 Entry = 0xf7e90 (0xf00f7e90) Rev = 0 Len = 1 PCI BIOS entry at 0x7ec0 Other BIOS signatures found: ACPI: 00000000 $PnP: 000fc4e0 pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12508086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x1250, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 chip0: rev 0x03 on pci0.0.0 found-> vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 chip1: rev 0x01 on pci0.7.0 I/O Recovery Timing: 8-bit 3.5 clocks, 16-bit 3.5 clocks Extended BIOS: disabled Lower BIOS: enabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: IRQ12, B: disabled, C: disabled, D: disabled MB0: disabled, MB1: found-> vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 ide_pci0: rev 0x00 on pci0.7.1 found-> vendor=0x1002, dev=0x4758, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 map[0]: type 1, range 32, base fb000000, size 23 vga0: rev 0x00 on pci0.9.0 found-> vendor=0x1000, dev=0x0001, revid=0x02 class=01-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=12 map[0]: type 4, range 32, base 0000e000, size 8 map[1]: type 1, range 32, base fa800000, size 8 ncr0: rev 0x02 int a irq 12 on pci0.12.0 ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo ncr0: single-ended, open drain IRQ driver ncr0: restart (scsi reset). ncr0 scanning for targets 0..6 (V2 pl24 96/12/14) scbus0 at ncr0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access sd0: NCR quirks=0x2 sd0: 10.0 MB/s (100 ns, offset 8) 2049MB (4197405 512 byte sectors) sd0: with 4177 cyls, 8 heads, and an average 125 sectors/track sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access sd1: NCR quirks=0x2 sd1: 10.0 MB/s (100 ns, offset 8) 234MB (479350 512 byte sectors) sd1: with 1818 cyls, 4 heads, and an average 65 sectors/track sd2 at scbus0 target 2 lun 0 sd2: type 0 fixed SCSI 2 sd2: Direct-Access sd2: NCR quirks=0x2 sd2: 10.0 MB/s (100 ns, offset 8) 327MB (670506 512 byte sectors) sd2: with 2337 cyls, 4 heads, and an average 71 sectors/track cd0 at scbus0 target 3 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM cd0: NCR quirks=0x2 cd0: 10.0 MB/s (100 ns, offset 8) can't get the size Probing for PnP devices: Trying Read_Port at 203 CSN 1 Vendor ID: ADP1505 [0x05159004] Serial 0x45e5863c Called nullpnp_probe with tag 0x00000001, type 0x05159004 Probing for devices on the ISA bus: sc0: the current keyboard controller command byte 0065 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0: keyboard device ID: ab41 sc0 at 0x60-0x6f irq 1 on motherboard sc0: BIOS video mode:3 sc0: VGA registers upon power-up 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: video mode:24 sc0: VGA registers in BIOS for mode:24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: VGA registers to be used for mode:24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: rows_offset:1 sc0: VGA color <16 virtual consoles, flags=0x0> sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A mss_probe: no address supplied, try default 0x530 mss_detect error, busy still set (0xff) sb_probe: no address supplied, try defaults (0x220,0x240) pcm0 not found fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 aic0 at 0x140-0x15f irq 10 on isa scbus1 at aic0 bus 0 cd1 at scbus1 target 6 lun 0 cd1: type 5 removable SCSI 2 cd1: CD-ROM can't get the size scd0 not found at 0x230 npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 131319763 bytes/sec bzero() bandwidth = 79308430 bytes/sec imasks: bio c0081440, tty c003001a, net c0060000 BIOS Geometries: 0:03f0413f 0..1008=1009 cylinders, 0..65=66 heads, 1..63=63 sectors 1:03f6073b 0..1014=1015 cylinders, 0..7=8 heads, 1..59=59 sectors 2:03f60a3c 0..1014=1015 cylinders, 0..10=11 heads, 1..60=60 sectors 0 accounted for Device configuration finished. Intel Pentium F00F detected, installing workaround bpf: tun0 attached bpf: lo0 attached IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging disabled Considering FFS root f/s. changing root device to sd0s1a sd0s1: type 0xa5, start 0, end = 4197404, size 4197405 sd0s1: C/H/S end 261/70/30 (558059) != end 4197404: invalid WARNING: / was not properly dismounted. sd1s1: type 0xa5, start 0, end = 479349, size 479350 : OK sd2s1: type 0xa5, start 0, end = 670505, size 670506 : OK sd2s1: type 0xa5, start 0, end = 670505, size 670506 : OK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 14:33:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24469 for freebsd-current-outgoing; Sun, 23 Aug 1998 14:33:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24450 for ; Sun, 23 Aug 1998 14:33:34 -0700 (PDT) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.8.8/8.8.7) id RAA22375; Sun, 23 Aug 1998 17:32:21 -0400 (EDT) (envelope-from lee) Message-ID: <19980823173221.A22349@st-lcremean.tidalwave.net> Date: Sun, 23 Aug 1998 17:32:21 -0400 From: Lee Cremeans To: The Hermit Hacker , current@FreeBSD.ORG Subject: Re: AVA-1505 card for CDR...system hang... Reply-To: lcremean@tidalwave.net References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from The Hermit Hacker on Sun, Aug 23, 1998 at 04:59:00PM -0300 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 23, 1998 at 04:59:00PM -0300, The Hermit Hacker wrote: > > Morning... > > The other day, I purchased an AVA-1505 SCSI card in order to move > my external CD-R to a seperate SCSI bus, because I was having problems > writing CDs. When the system boots, it recognizes the AVA and the CDR, > but as soon as I get to a login prompt, if I try to do a mount of a > known-to-work CD, it hangs and tells me that 'cd1 timed out', and just > hangs there indefinitely. > > It *feels* like an IRQ conflict, except I can't find one looking > through both a boot and a boot -v. The boot -v included here is for a > system with just the NCR controller (boot drive(s)), video controller and > the AVA-1505 controller. The operating system is 3.0-CURRENT as of > yesterday, no CAM drivers. > > Can someone suggestion something that I'm overlooking here? Or is > there a known problem with the 1505's that I missed? The aha driver (AIC636x chips, including the 1505) is in a rather advanced state of bitrot. I've had it panic my machine back when I tried it in -stable (2.2.5-ish, I think). I'd adopt it if I knew enough about SCSI to fix it, since we have TONS of 1510s and 152x cards lying around :| -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 14:33:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24515 for freebsd-current-outgoing; Sun, 23 Aug 1998 14:33:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mumford.stuy.edu (mumford.stuy.edu [149.89.1.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24508 for ; Sun, 23 Aug 1998 14:33:48 -0700 (PDT) (envelope-from galatalt@stuy.edu) Received: from nyc-ny64-59.ix.netcom.com (nyc-ny64-59.ix.netcom.com [209.109.224.187]) by mumford.stuy.edu (8.8.5/8.8.5) with SMTP id RAA10401; Sun, 23 Aug 1998 17:33:51 -0400 Date: Sun, 23 Aug 1998 17:30:58 -0400 (EDT) From: Tugrul Galatali X-Sender: galatalt@europa.novastar.com To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: Something changed in sendmail cf? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Aug 1998, Andrzej Bialecki wrote: > Hi, > > Recently I updated my machine to latest current, and noticed that my > procmail stopped working - it seems it isn't even called by sendmail via > .forward file (and it worked just fine before). I went as far as changing > Mlocal definition in /etc/sendmail.cf, but it still doesn't work - all > mail still goes to my /var/mail/abial. > Same thing happened to me on my 486 which has been up 7 days since its last world when this happened. Been meaning to email the list about it, but I patched around the problem with a frequently called cron process :), so I haven't investigated it much yet. Tugrul Galatali To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 14:56:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26968 for freebsd-current-outgoing; Sun, 23 Aug 1998 14:56:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26963 for ; Sun, 23 Aug 1998 14:56:55 -0700 (PDT) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with SMTP id RAA01228; Sun, 23 Aug 1998 17:59:08 -0400 (EDT) Date: Sun, 23 Aug 1998 17:59:08 -0400 (EDT) From: Mike To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: Something changed in sendmail cf? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Aug 1998, Andrzej Bialecki wrote: > Where should I look now? What has changed with sendmail? What should I do > to make it work? Perhaps the 'latest current' is using sendmail 8.9.1? -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 16:47:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07705 for freebsd-current-outgoing; Sun, 23 Aug 1998 16:47:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07700 for ; Sun, 23 Aug 1998 16:47:14 -0700 (PDT) (envelope-from dillon@backplane.com) Received: (dillon@localhost) by apollo.backplane.com (8.8.8/8.6.5) id QAA09537; Sun, 23 Aug 1998 16:46:30 -0700 (PDT) Date: Sun, 23 Aug 1998 16:46:30 -0700 (PDT) From: Matthew Dillon Message-Id: <199808232346.QAA09537@apollo.backplane.com> To: current@FreeBSD.ORG Subject: kern/7557, More on inode deadlock (was Re: Bizarre deadlock) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have submitted an update to my kern/7557 PR. Except it hasn't seemed to have made it into the system. Oh well.. here's the jist: I managed to get two full debug crash dumps from the inode lockup problem I reported in kern/7557. A pattern has emerged. Specifically, in all crashes a ps shows that two processes are stuck on a busy page and busy bp, as shown below. The key appears to be a deadlock somewhere, and although it isn't these two processes specifically that are deadlocking, I believe they are involved somehow. Together they (I think) hold a shared lock (lockcnt = 2) on the associated inode which locks up the remainder of the system when the system tries to get a lock on that inode. I do not know what has actually busied the bp and vm_page_t involved in these two process's sleep, but I'm guessing that whatever it is is in a deadlock situation waiting for the inode while these processes have a shared lock on the inode and are waiting on the page and bp. If anyone knows the bp/vm system better, perhaps they can figure the deadlock out from here. My test SMP box running -current gets deadlocked once every few days or so from this. -Matt original report: 9896 0xfa87c1c0 0xfa8fc000 8 202 202 000105 3 pgtblk 0xf0f6f78c diablo 9890 0xfa796f00 0xfa84c000 8 202 202 000105 3 getblk 0xf6d16868 diablo new information: nntp3:/var/crash# ps -M vmcore.7 -N kernel.7 -axl | egrep 'pgtblk|getblk' 8 280 198 1 -18 0 44312 0 pgtblk D ?? 0:00.00 (diablo) 8 319 198 1 -2 0 44312 0 getblk D ?? 0:00.00 (diablo) nntp3:/var/crash# ps -M vmcore.6 -N kernel.6 -axl | egrep 'pgtblk|getblk' 8 10400 198 0 -2 0 43780 0 getblk D ?? 0:00.00 (diablo) 8 10419 198 0 -18 0 43788 0 pgtblk D ?? 0:00.00 (diablo) (kgdb) proc 319 (kgdb) back #0 mi_switch () at ../../kern/kern_synch.c:661 #1 0xf0119fb1 in tsleep (ident=0xf6e400b0, priority=0x14, wmesg=0xf013432f "getblk", timo=0x0) at ../../kern/kern_synch.c:435 #2 0xf01343dd in getblk (vp=0xfc24d180, blkno=0xc, size=0x2000, slpflag=0x0, slptimeo=0x0) at ../../kern/vfs_bio.c:1437 #3 0xf01366fb in cluster_read (vp=0xfc24d180, filesize=0x4034b2, lblkno=0xc, size=0x2000, cred=0x0, totread=0x10000, seqcount=0x8, bpp=0xfc10fd60) at ../../kern/vfs_cluster.c:114 #4 0xf01ac721 in ffs_read (ap=0xfc10fe18) at ../../ufs/ufs/ufs_readwrite.c:168 #5 0xf01ad2bd in ffs_getpages (ap=0xfc10fe70) at vnode_if.h:303 #6 0xf01c386a in vnode_pager_getpages (object=0xfc3f0220, m=0xfc10ff1c, count=0x2, reqpage=0x0) at vnode_if.h:1067 #7 0xf01c2587 in vm_pager_get_pages (object=0xfc3f0220, m=0xfc10ff1c, count=0x2, reqpage=0x0) at ../../vm/vm_pager.c:256 #8 0xf01b6f34 in vm_fault (map=0xfc073380, vaddr=0x22897000, fault_type=0x1, fault_flags=0x0) at ../../vm/vm_fault.c:424 #9 0xf01daca2 in trap_pfault (frame=0xfc10ffbc, usermode=0x1) at ../../i386/i386/trap.c:753 #10 0xf01da7e3 in trap (frame={tf_es = 0xefbf0027, tf_ds = 0xfc100027, tf_edi = 0x1, tf_esi = 0x17fea, tf_ebp = 0xefbfd58c, tf_isp = 0xfc10ffe4, tf_ebx = 0x18000, tf_edx = 0x2287f000, tf_ecx = 0x0, tf_eax = 0x9cf7f, tf_trapno = 0xc, tf_err = 0x4, tf_eip = 0x414c, tf_cs = 0x1f, tf_eflags = 0x10297, tf_esp = 0xefbfd520, tf_ss = 0x27}) at ../../i386/i386/trap.c:317 #11 0x414c in ?? () #12 0x276e in ?? () #13 0x1ee1 in ?? () #14 0x1809 in ?? () #15 0x107e in ?? () (kgdb) frame 2 #2 0xf01343dd in getblk (vp=0xfc24d180, blkno=0xc, size=0x2000, slpflag=0x0, slptimeo=0x0) at ../../kern/vfs_bio.c:1437 1437 if (!tsleep(bp, (kgdb) print bp $11 = (struct buf *) 0xf6e400b0 (kgdb) print *bp $12 = { b_hash = { le_next = 0x0, le_prev = 0xf6e2f0f8 }, b_vnbufs = { le_next = 0xf6e4f258, le_prev = 0xfc24d1b0 }, b_freelist = { tqe_next = 0xf6d77f08, tqe_prev = 0xf0202158 }, b_act = { tqe_next = 0x0, tqe_prev = 0xf1ca0e14 }, b_proc = 0x0, b_flags = 0x20800030, b_qindex = 0x0, b_usecount = 0x6, b_error = 0x0, b_bufsize = 0x0, b_bufsize = 0x0, b_bcount = 0x0, b_resid = 0x0, b_dev = 0xffffffff, b_data = 0xf95ae000
, b_kvabase = 0xf95ae000
, b_kvasize = 0x2000, b_lblkno = 0xc, b_blkno = 0xc, b_offset = 0x0000000000018000, b_iodone = 0, b_iodone_chain = 0x0, b_vp = 0xfc24d180, b_dirtyoff = 0x0, b_dirtyend = 0x0, b_rcred = 0x0, b_wcred = 0x0, b_validoff = 0x0, b_validend = 0x0, b_pblkno = 0x9804d0, b_saveaddr = 0x0, b_savekva = 0x0, b_driver1 = 0x0, b_driver2 = 0x0, b_spc = 0x0, b_cluster = { cluster_head = { tqh_first = 0xf6d77f08, tqh_last = 0xf6d850e8 }, cluster_entry = { tqe_next = 0xf6d77f08, tqe_prev = 0xf6d850e8 } }, b_pages = {0x0 }, b_npages = 0x0, b_dep = { lh_first = 0x0 } } (kgdb) proc 280 (kgdb) back #0 mi_switch () at ../../kern/kern_synch.c:661 #1 0xf0119fb1 in tsleep (ident=0xf0e19ba0, priority=0x4, wmesg=0xf01346d2 "pgtblk", timo=0x0) at ../../kern/kern_synch.c:435 #2 0xf0134afa in allocbuf (bp=0xf6e400b0, size=0x2000) at ../../kern/vfs_bio.c:1799 #3 0xf0134612 in getblk (vp=0xfc24d180, blkno=0xc, size=0x2000, slpflag=0x0, slptimeo=0x0) at ../../kern/vfs_bio.c:1557 #4 0xf0136a5e in cluster_read (vp=0xfc24d180, filesize=0x4034b2, lblkno=0xc, size=0x2000, cred=0x0, totread=0xc000, seqcount=0x8, bpp=0xfc0f6d60) at ../../kern/vfs_cluster.c:235 #5 0xf01ac721 in ffs_read (ap=0xfc0f6e18) at ../../ufs/ufs/ufs_readwrite.c:168 #6 0xf01ad2bd in ffs_getpages (ap=0xfc0f6e70) at vnode_if.h:303 #7 0xf01c386a in vnode_pager_getpages (object=0xfc3f0220, m=0xfc0f6f1c, count=0x2, reqpage=0x0) at vnode_if.h:1067 #8 0xf01c2587 in vm_pager_get_pages (object=0xfc3f0220, m=0xfc0f6f1c, count=0x2, reqpage=0x0) at ../../vm/vm_pager.c:256 #9 0xf01b6f34 in vm_fault (map=0xfc0738c0, vaddr=0x22891000, fault_type=0x1, fault_flags=0x0) at ../../vm/vm_fault.c:424 #10 0xf01daca2 in trap_pfault (frame=0xfc0f6fbc, usermode=0x1) at ../../i386/i386/trap.c:753 #11 0xf01da7e3 in trap (frame={tf_es = 0xefbf0027, tf_ds = 0xfc0f0027, tf_edi = 0x1, tf_esi = 0x11fd1, tf_ebp = 0xefbfd58c, tf_isp = 0xfc0f6fe4, tf_ebx = 0x12000, tf_edx = 0x2287f000, tf_ecx = 0x0, tf_eax = 0x9cf7f, tf_trapno = 0xc, tf_err = 0x4, tf_eip = 0x414c, tf_cs = 0x1f, tf_eflags = 0x10297, tf_esp = 0xefbfd520, tf_ss = 0x27}) at ../../i386/i386/trap.c:317 #12 0x414c in ?? () #13 0x276e in ?? () #14 0x1ee1 in ?? () #15 0x1809 in ?? () #16 0x107e in ?? () (kgdb) (kgdb) print bp $14 = (struct buf *) 0xf6e400b0 (this is the same bp) Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 17:15:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09615 for freebsd-current-outgoing; Sun, 23 Aug 1998 17:15:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09608 for ; Sun, 23 Aug 1998 17:15:42 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id UAA24930; Sun, 23 Aug 1998 20:14:49 -0400 (EDT) (envelope-from wollman) Date: Sun, 23 Aug 1998 20:14:49 -0400 (EDT) From: Garrett Wollman Message-Id: <199808240014.UAA24930@khavrinen.lcs.mit.edu> To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: kern/7557, More on inode deadlock (was Re: Bizarre deadlock) In-Reply-To: <199808232346.QAA09537@apollo.backplane.com> References: <199808232346.QAA09537@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > emerged. Specifically, in all crashes a ps shows that > two processes are stuck on a busy page and busy bp, as shown > below. This is precisely the symptom that I have seen. No SMP, no soft updates. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 18:00:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15161 for freebsd-current-outgoing; Sun, 23 Aug 1998 18:00:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15156 for ; Sun, 23 Aug 1998 18:00:52 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id TAA11329 for ; Sun, 23 Aug 1998 19:58:32 -0400 (EDT) Date: Sun, 23 Aug 1998 19:58:31 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: freebsd-current@FreeBSD.ORG Subject: pciconf Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While investigating pci stuff (for an audio driver) I saw a man page for pciconf. It says that there's a -l option, so I tried that, as both a regular user and root, and both times I got: picnic:/usr2/chuckr:55 >pciconf -l pciconf: ioctl(PCIOCGETCONF): Operation not supported by device I figured to use the pciconf utility (the source code) to educate myself as to what pci functions might work like, so this is unsettling. Does anyone know what's going on here? Below, I'm excerpting the part of my dmesg that I figure might be relevant: FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 vga0: rev 0xfc on pci0.11.0 ncr0: rev 0x03 int a irq 17 on pci0.13.0 ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 18:46:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24320 for freebsd-current-outgoing; Sun, 23 Aug 1998 18:46:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA24257 for ; Sun, 23 Aug 1998 18:45:45 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id VAA19462; Sun, 23 Aug 1998 21:47:59 -0400 From: Bill Paul Message-Id: <199808240147.VAA19462@skynet.ctr.columbia.edu> Subject: Re: pciconf To: chuckr@glue.umd.edu (Chuck Robey) Date: Sun, 23 Aug 1998 21:47:58 -0400 (EDT) Cc: current@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at Aug 23, 98 07:58:31 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Chuck Robey had to walk into mine and say: > While investigating pci stuff (for an audio driver) I saw a man page for > pciconf. It says that there's a -l option, so I tried that, as both a > regular user and root, and both times I got: > > picnic:/usr2/chuckr:55 >pciconf -l > pciconf: ioctl(PCIOCGETCONF): Operation not supported by device It looks like somebody put a nice bit #ifdef NOTYET around the PCIOCGETCONF case in the ioctl routine in /sys/pci/pci.c. The CAM snapshot that I've been using doesn't have this. I don't know why the code is turned off. It looks as though the other cases should work though. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 19:29:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02238 for freebsd-current-outgoing; Sun, 23 Aug 1998 19:29:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02211 for ; Sun, 23 Aug 1998 19:28:51 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id UAA05491; Sun, 23 Aug 1998 20:27:57 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199808240227.UAA05491@panzer.plutotech.com> Subject: Re: pciconf In-Reply-To: from Chuck Robey at "Aug 23, 98 07:58:31 pm" To: chuckr@glue.umd.edu (Chuck Robey) Date: Sun, 23 Aug 1998 20:27:57 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote... > While investigating pci stuff (for an audio driver) I saw a man page for > pciconf. It says that there's a -l option, so I tried that, as both a > regular user and root, and both times I got: > > picnic:/usr2/chuckr:55 >pciconf -l > pciconf: ioctl(PCIOCGETCONF): Operation not supported by device > > I figured to use the pciconf utility (the source code) to educate myself > as to what pci functions might work like, so this is unsettling. Does > anyone know what's going on here? Below, I'm excerpting the part of my > dmesg that I figure might be relevant: The problem is that the PCIOCGETCONF ioctl isn't supported in -current. There's nothing wrong with your machine. I've modified the PCI code in the CAM tree to support that ioctl again. So 'pciconf -l' now produces output like: {panzer:/usr/home/ken:7:0} pciconf -l ahc1@pci1:5:0: class=0x010000 card=0x00000000 chip=0x82789004 rev=0x00 hdr=0x00 ahc0@pci1:4:0: class=0x010000 card=0x00000000 chip=0x82789004 rev=0x00 hdr=0x00 vga0@pci0:13:0: class=0x030000 card=0x00000000 chip=0x0519102b rev=0x01 hdr=0x00 de1@pci0:12:0: class=0x020000 card=0x00000000 chip=0x00091011 rev=0x12 hdr=0x00 bktr0@pci0:11:0: class=0x040000 card=0x00000000 chip=0x0350109e rev=0x11 hdr=0x00 de0@pci0:10:0: class=0x020000 card=0x00000000 chip=0x00091011 rev=0x11 hdr=0x00 chip2@pci0:9:0: class=0x060400 card=0x00000000 chip=0x00011011 rev=0x02 hdr=0x01 chip1@pci0:1:0: class=0x060100 card=0x00000000 chip=0x70008086 rev=0x01 hdr=0x00 chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x12378086 rev=0x02 hdr=0x00 The new version of that ioctl also supports matching against bus, device, function, device name and unit number. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 22:32:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23000 for freebsd-current-outgoing; Sun, 23 Aug 1998 22:32:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22964 for ; Sun, 23 Aug 1998 22:32:03 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id HAA16494; Mon, 24 Aug 1998 07:35:05 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 24 Aug 1998 07:35:05 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike cc: freebsd-current@FreeBSD.ORG Subject: Re: Something changed in sendmail cf? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Aug 1998, Mike wrote: > On Sun, 23 Aug 1998, Andrzej Bialecki wrote: > > > Where should I look now? What has changed with sendmail? What should I do > > to make it work? > > Perhaps the 'latest current' is using sendmail 8.9.1? Yes. Then what? Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 22:39:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24231 for freebsd-current-outgoing; Sun, 23 Aug 1998 22:39:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24207 for ; Sun, 23 Aug 1998 22:39:16 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from support1.cybcon.com (william@support1.cybcon.com [205.147.76.99]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id VAA09870 for ; Sun, 23 Aug 1998 21:57:10 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 23 Aug 1998 21:57:05 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: FreebSD Current Subject: Firewall Rules are weird.....look at this...in current.... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Sun, 23 Aug 1998 21:42:39 -0700 (PDT) From: William Woods To: FreeBSD Questions Subject: Firewall Rules are weird.....look at this... I just compiled todays cvsup of current and all is fine except this. Here is a portion of my firewall rules: ------------------------------------- 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 65000 allow ip from any to any 65535 allow ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any There are about 10 more occourances of the 00000 rules..... -------------------------------- Where do all those 00000 rules come from?? Here is a snip of my kernel configuration as pertaining to the firewall: # Firewall options "TCP_COMPAT_42" #emulate 4.2BSD TCP bugs options MROUTING # Multicast routing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable xparent proxy support options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPDIVERT #divert sockets options IPFILTER #kernel ipfilter support options IPFILTER_LOG #ipfilter logging #options IPFILTER_LKM #kernel support for ip_fil.o LKM options TCPDEBUG ------------------------------------ And here is the rc.conf as pertains to firewalls: firewall_enable="YES" # Set to YES to enable firewall functionality firewall_type="OPEN" # Firewall type (see /etc/rc.firewall) firewall_quiet="NO" # Set to YES to suppress rule display ------------------------------------------------ And here is the portion of rc.firewall I use.... # Only in rare cases do you want to change these rules $fwcmd add 100 pass all from any to any via lo0 $fwcmd add 200 deny all from any to 127.0.0.0/8 # Prototype setups. if [ "${firewall_type}" = "open" -o "${firewall_type}" = "OPEN" ]; then $fwcmd add 65000 pass all from any to any elif [ "${firewall_type}" = "client" ]; then --------------------------------- The firewall actually works, blocks ports when I add then, I am just unnerved by all those 00000 rules.....any ideas? --------------------- William Woods Date: 23-Aug-98 / Time: 21:42:39 goto to: http//www.freebsd.org. --> FreeBSD 3.0 CURRENT <-- --------------End of forwarded message------------------------- --------------------- William Woods Date: 23-Aug-98 / Time: 21:56:28 goto to: http//www.freebsd.org. --> FreeBSD 3.0 CURRENT <-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 23 23:53:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03864 for freebsd-current-outgoing; Sun, 23 Aug 1998 23:53:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03856 for ; Sun, 23 Aug 1998 23:53:26 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id CAA14173; Mon, 24 Aug 1998 02:52:22 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Bill Paul cc: chuckr@glue.umd.edu (Chuck Robey), current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: pciconf In-reply-to: Your message of "Sun, 23 Aug 1998 21:47:58 EDT." <199808240147.VAA19462@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Aug 1998 02:52:21 -0400 Message-ID: <14169.903941541@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Paul wrote in message ID <199808240147.VAA19462@skynet.ctr.columbia.edu>: > I don't know why the code is turned off. It looks as though the > other cases should work though. To quote the code: case PCIOCGETCONF: #ifdef NOTYET static struct pci_conf *pci_dev_list; static unsigned pci_dev_list_count; static unsigned pci_dev_list_size; cio = (struct pci_conf_io *)data; iolen = min(cio->pci_len, pci_dev_list_count * sizeof(struct pci_conf)); cio->pci_len = pci_dev_list_count * sizeof(struct pci_conf); error = copyout(pci_dev_list, cio->pci_buf, iolen); Spot that (even if you move the variable decls to the proper location), that pci_dev_list_count and pci_dev_list_size are never calculated. My guess is that there is meant to be code elsewhere to initialize those, but its not written yet. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 00:32:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09122 for freebsd-current-outgoing; Mon, 24 Aug 1998 00:32:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09111 for ; Mon, 24 Aug 1998 00:32:36 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id JAA28168; Mon, 24 Aug 1998 09:37:35 +0200 (CEST) (envelope-from regnauld@deepo.prosa.dk) Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id JAA09505; Mon, 24 Aug 1998 09:41:14 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id JAA11250; Mon, 24 Aug 1998 09:30:37 +0200 (CEST) Message-ID: <19980824093037.55193@deepo.prosa.dk> Date: Mon, 24 Aug 1998 09:30:37 +0200 From: Philippe Regnauld To: wwoods@cybcon.com Cc: FreebSD Current Subject: Re: Firewall Rules are weird.....look at this...in current.... References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from William Woods on Sun, Aug 23, 1998 at 09:57:05PM -0700 X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG William Woods writes: > > I just compiled todays cvsup of current and all is fine except this. Here is a > portion of my firewall rules: > > ------------------------------------- > 00100 allow ip from any to any via lo0 > 00200 deny ip from any to 127.0.0.0/8 > 65000 allow ip from any to any > 65535 allow ip from any to any > 00000 deny ip from any to any > 00000 deny ip from any to any [...] > options IPFIREWALL #firewall > options IPFIREWALL_VERBOSE #print information about > # dropped packets > options IPFIREWALL_FORWARD #enable xparent proxy support > options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity > options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default > options IPDIVERT #divert sockets > options IPFILTER #kernel ipfilter support > options IPFILTER_LOG #ipfilter logging > #options IPFILTER_LKM #kernel support for ip_fil.o LKM Why do you have both IPFILTER and IPFW ? -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 00:48:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11437 for freebsd-current-outgoing; Mon, 24 Aug 1998 00:48:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11432 for ; Mon, 24 Aug 1998 00:48:52 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from support1.cybcon.com (william@support1.cybcon.com [205.147.76.99]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id AAA16227; Mon, 24 Aug 1998 00:48:03 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19980824093037.55193@deepo.prosa.dk> Date: Mon, 24 Aug 1998 00:47:59 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: Philippe Regnauld Subject: Re: Firewall Rules are weird.....look at this...in current.... Cc: FreebSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just copied it out of LINT..... On 24-Aug-98 Philippe Regnauld wrote: > William Woods writes: >> >> I just compiled todays cvsup of current and all is fine except this. Here is >> a >> portion of my firewall rules: >> >> ------------------------------------- >> 00100 allow ip from any to any via lo0 >> 00200 deny ip from any to 127.0.0.0/8 >> 65000 allow ip from any to any >> 65535 allow ip from any to any >> 00000 deny ip from any to any >> 00000 deny ip from any to any > > [...] >> options IPFIREWALL #firewall >> options IPFIREWALL_VERBOSE #print information about >> # dropped packets >> options IPFIREWALL_FORWARD #enable xparent proxy support >> options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity >> options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default >> options IPDIVERT #divert sockets >> options IPFILTER #kernel ipfilter support >> options IPFILTER_LOG #ipfilter logging >> #options IPFILTER_LKM #kernel support for ip_fil.o LKM > > Why do you have both IPFILTER and IPFW ? > > -- > -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- > > The Internet is busy. Please try again later. --------------------- William Woods Date: 24-Aug-98 / Time: 00:44:13 goto to: http//www.freebsd.org. --> FreeBSD 3.0 CURRENT <-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 01:10:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14782 for freebsd-current-outgoing; Mon, 24 Aug 1998 01:10:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA14774 for ; Mon, 24 Aug 1998 01:10:34 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zArhD-0005nM-00; Mon, 24 Aug 1998 02:09:47 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id CAA11654; Mon, 24 Aug 1998 02:11:05 -0600 (MDT) Message-Id: <199808240811.CAA11654@harmony.village.org> To: The Hermit Hacker Subject: Re: AVA-1505 card for CDR...system hang... Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 23 Aug 1998 16:59:00 -0300." References: Date: Mon, 24 Aug 1998 02:11:03 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message The Hermit Hacker writes: : Can someone suggestion something that I'm overlooking here? Or is : there a known problem with the 1505's that I missed? The aic driver sucks in -current. Sometimes it works, sometimes (usually) it doesn't. The 6360 is a big PITA to program correctly. I've looked at the docs for it in the hope of writing a driver for CAM, and am working on a 1542 driver instead because it looks to be much easier... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 01:14:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15331 for freebsd-current-outgoing; Mon, 24 Aug 1998 01:14:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA15325 for ; Mon, 24 Aug 1998 01:14:11 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zArki-0005nV-00; Mon, 24 Aug 1998 02:13:24 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id CAA11679; Mon, 24 Aug 1998 02:14:42 -0600 (MDT) Message-Id: <199808240814.CAA11679@harmony.village.org> To: lcremean@tidalwave.net Subject: Re: AVA-1505 card for CDR...system hang... Cc: The Hermit Hacker , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 23 Aug 1998 17:32:21 EDT." <19980823173221.A22349@st-lcremean.tidalwave.net> References: <19980823173221.A22349@st-lcremean.tidalwave.net> Date: Mon, 24 Aug 1998 02:14:40 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980823173221.A22349@st-lcremean.tidalwave.net> Lee Cremeans writes: : The aha driver (AIC636x chips, including the 1505) is in a rather advanced : state of bitrot. I've had it panic my machine back when I tried it in : -stable (2.2.5-ish, I think). I'd adopt it if I knew enough about SCSI to : fix it, since we have TONS of 1510s and 152x cards lying around :| The aha driver is for the 1542 cards. The aic driver is for the AIC-6[23]60 chips made by adaptech. These have been found mostly on 15xx cards: 1502 (the smallest ISA card I've ever seen), 1505, 1510, 1515, 1520, 1520A, 1522 and 1522A (and likely a few I've missed, like the fabled 1522B). The aic driver is in need of a complete rewrite, or lots of TLC from someone who has the technical tools to do the work. The manual scared me off into easier pastures, at least for the moment :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 01:16:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15862 for freebsd-current-outgoing; Mon, 24 Aug 1998 01:16:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15843 for ; Mon, 24 Aug 1998 01:16:47 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id KAA29378; Mon, 24 Aug 1998 10:21:49 +0200 (CEST) (envelope-from regnauld@deepo.prosa.dk) Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id KAA09596; Mon, 24 Aug 1998 10:25:29 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id KAA11980; Mon, 24 Aug 1998 10:14:52 +0200 (CEST) Message-ID: <19980824101451.02376@deepo.prosa.dk> Date: Mon, 24 Aug 1998 10:14:51 +0200 From: Philippe Regnauld To: wwoods@cybcon.com Cc: FreebSD Current Subject: Re: Firewall Rules are weird.....look at this...in current.... References: <19980824093037.55193@deepo.prosa.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from William Woods on Mon, Aug 24, 1998 at 12:47:59AM -0700 X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG William Woods writes: > I just copied it out of LINT..... > > >> options IPFIREWALL #firewall > >> options IPFIREWALL_VERBOSE #print information about > >> # dropped packets > >> options IPFIREWALL_FORWARD #enable xparent proxy support > >> options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity > >> options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default > >> options IPDIVERT #divert sockets > >> options IPFILTER #kernel ipfilter support > >> options IPFILTER_LOG #ipfilter logging > >> #options IPFILTER_LKM #kernel support for ip_fil.o LKM Ok -- IPFIREWALL and IPFILTER are two _different_ filtering systems -- you should choose one or the other, not both -- I think your problem might be there (just guessing, I do not know how IPFILTER interacts at network level). -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 02:18:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23815 for freebsd-current-outgoing; Mon, 24 Aug 1998 02:18:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23809 for ; Mon, 24 Aug 1998 02:18:41 -0700 (PDT) (envelope-from wosch@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id LAA10715 for current@freebsd.org; Mon, 24 Aug 1998 11:17:55 +0200 (CEST) (envelope-from wosch@panke.de.freebsd.org) Received: (from wosch@localhost) by campa.panke.de (8.8.8/8.8.8) id VAA04727; Sun, 23 Aug 1998 21:06:24 +0200 (MET DST) (envelope-from wosch) Date: Sun, 23 Aug 1998 21:06:24 +0200 (MET DST) Message-Id: <199808231906.VAA04727@campa.panke.de> From: Wolfram Schneider To: current@FreeBSD.ORG Subject: file segment sizes of a core dump MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I added an option to size(1) which print the file segment sizes of a core dump. For example: $ ./size /bin/sh text data bss dec hex 294912 12288 35656 342856 53b48 $ ./size -c sh.core text data bss dec hex 294912 69632 131072 495616 79000 If nobody objects I will commit the change. Index: size.1 =================================================================== RCS file: /usr/cvs/src/usr.bin/size/size.1,v retrieving revision 1.3 diff -u -r1.3 size.1 --- size.1 1997/08/11 07:28:18 1.3 +++ size.1 1998/08/23 17:13:04 @@ -39,6 +39,7 @@ .Nd display object file segment sizes (text, data and bss) .Sh SYNOPSIS .Nm size +.Op Fl c .Op Ar object_file ... .Sh DESCRIPTION .Nm Size @@ -52,8 +53,20 @@ .Nm attempts to report on the file .Pa a.out . +.Pp +The options are as follows: +.Bl -tag -width indent +.It Fl c +Print the size of a +.Ar core dump +file instead a +.Ar object_file . +.El +.Pp .Sh SEE ALSO +.Xr gcore 1 .Xr a.out 5 +.Xr core 5 .Sh HISTORY A .Nm Index: size.c =================================================================== RCS file: /usr/cvs/src/usr.bin/size/size.c,v retrieving revision 1.4 diff -u -r1.4 size.c --- size.c 1998/07/06 21:01:32 1.4 +++ size.c 1998/08/23 18:58:03 @@ -47,6 +47,9 @@ #include #include +#include +#include +#include #include #include #include @@ -57,6 +60,8 @@ int show __P((int, char *)); static void usage __P((void)); +int coredumpsize; /* run as coredumpsize(1) command */ + int main(argc, argv) int argc; @@ -64,8 +69,11 @@ { int ch, eval; - while ((ch = getopt(argc, argv, "")) != -1) + while ((ch = getopt(argc, argv, "c")) != -1) switch(ch) { + case 'c': + coredumpsize = 1; + break; case '?': default: usage(); @@ -90,6 +98,8 @@ { static int first = 1; struct exec head; + struct user user; + struct stat stat; u_long total; int fd; @@ -97,20 +107,47 @@ warn("%s", name); return (1); } - if (read(fd, &head, sizeof(head)) != sizeof(head) || N_BADMAG(head)) { - (void)close(fd); - warnx("%s: not in a.out format", name); - return (1); + + if (!coredumpsize) { + if (read(fd, &head, sizeof(head)) != sizeof(head) || + N_BADMAG(head)) { + (void)close(fd); + warnx("%s: not in a.out format", name); + return (1); + } + } else { + if (read(fd, &user, sizeof(user)) != sizeof(user) || + fstat(fd, &stat) == -1) { + (void)close(fd); + warnx("%s: not in core format", name); + return (1); + } + if (stat.st_size < ptoa(UPAGES + user.u_dsize + user.u_ssize)) { + warnx("%s: seems not to be a valid core dump file", name); + close(fd); + return(1); + } } (void)close(fd); if (first) { first = 0; (void)printf("text\tdata\tbss\tdec\thex\n"); + } + + if (!coredumpsize) { + total = head.a_text + head.a_data + head.a_bss; + (void)printf("%lu\t%lu\t%lu\t%lu\t%lx", (u_long)head.a_text, + (u_long)head.a_data, (u_long)head.a_bss, total, total); + } else { + total = ptoa(user.u_tsize) + ptoa(user.u_dsize) + + ptoa(user.u_ssize); + (void)printf("%lu\t%lu\t%lu\t%lu\t%lx", + (u_long)ptoa(user.u_tsize), + (u_long)ptoa(user.u_dsize), + (u_long)ptoa(user.u_ssize), total, total); } - total = head.a_text + head.a_data + head.a_bss; - (void)printf("%lu\t%lu\t%lu\t%lu\t%lx", (u_long)head.a_text, - (u_long)head.a_data, (u_long)head.a_bss, total, total); + if (count > 1) (void)printf("\t%s", name); (void)printf("\n"); @@ -120,6 +157,6 @@ static void usage() { - (void)fprintf(stderr, "usage: size [file ...]\n"); + (void)fprintf(stderr, "usage: size [-c] [file ...]\n"); exit(1); } -- Wolfram Schneider http://www.freebsd.org/~w/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 02:29:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24948 for freebsd-current-outgoing; Mon, 24 Aug 1998 02:29:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from darkstar.psa.at (uvo1-42.univie.ac.at [131.130.231.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24942 for ; Mon, 24 Aug 1998 02:29:06 -0700 (PDT) (envelope-from root@darkstar.psa.at) Received: (from root@localhost) by darkstar.psa.at (8.8.8/8.8.8) id LAA00238 for freebsd-current@freebsd.org; Mon, 24 Aug 1998 11:19:24 +0200 (CEST) (envelope-from root) Message-ID: <19980824111923.A207@compufit.at> Date: Mon, 24 Aug 1998 11:19:23 +0200 From: Alexander Sanda To: freebsd-current@FreeBSD.ORG Subject: encountered possible VM bug ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I'am running -current (dated 08/17) on a PPro/200, Gigabyte MB, 128 M. Ok, what happened ? While I was playing with the KDE newsreader (krn), I encountered a bug in krn, probably caused by some kind of infinite recursion or similar. Fact is, while krn tried to "thread" a group, it started to eat memory like crazy. After a while, I noticed quite a bit swapping. I checked ps, and found out that krn has allocated more than 160 MB (!!) of RAM (I have 128 physical, about 100 MB swap). I assume, that the overall memory consumtion of the system must have been somewhere around 200 MB at this time. I was running X, full KDE desktop; a Netscape session and a copy of gimp were active on another desktop aswell). However, I managed to kill -9 the crazy krn app, and everything seemed to be ok. The only message I found in the log is: Aug 24 01:53:05 darkstar /kernel: swap_pager: suggest more swap space: 254 MB Next time, I tried to connect to my local newsserver (nntpd, handled by inetd), I got an error. I telnet'ed to port 119 and got something like "realloc() junk pointer, too low" as an error message from inetd. I had to kill and restart inetd to restore normal operation. What the hell happened to inetd ? BTW: no other problems occured so far; system is still up and running. -- # /AS/ http://privat.schlund.de/entropy/ # # # # XX has detected, that your mouse cursor has changed position. Please # # restart XX, so it can be updated. -- From The Gimp manual # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 02:41:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26058 for freebsd-current-outgoing; Mon, 24 Aug 1998 02:41:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26052 for ; Mon, 24 Aug 1998 02:41:01 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id LAA29359 for ; Mon, 24 Aug 1998 11:44:43 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 24 Aug 1998 11:44:42 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: PicoBSD CVS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm glad to inform you that it has been decided to put PicoBSD project into the source tree of standard FreeBSD distribution, so that it can be tracked closely by other people as well, using cvsup. The question remaining is _where_ to put it in the current hierarchy. Perhaps /usr/src/contrib? Jordan proposed /usr/src/share, but it's intended to keep only shared text files... What are your ideas? Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 02:44:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26440 for freebsd-current-outgoing; Mon, 24 Aug 1998 02:44:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26435 for ; Mon, 24 Aug 1998 02:44:52 -0700 (PDT) (envelope-from paulz@trantor.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <11119-31475>; Mon, 24 Aug 1998 11:43:58 +0200 Received: from trantor.stuyts.nl (uucp@localhost) by terminus.stuyts.nl (8.9.1/8.8.8) with UUCP id LAA14062; Mon, 24 Aug 1998 11:17:29 +0200 (MET DST) (envelope-from paulz@trantor.stuyts.nl) Received: from trantor.stuyts.nl (localhost [127.0.0.1]) by trantor.stuyts.nl (8.9.1/8.8.5) with ESMTP id LAA13070; Mon, 24 Aug 1998 11:15:07 +0200 (MET DST) Message-Id: <199808240915.LAA13070@trantor.stuyts.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: Philippe Regnauld Cc: FreebSD Current Subject: Re: Firewall Rules are weird.....look at this...in current.... In-reply-to: Your message of "Mon, 24 Aug 1998 09:30:37 +0200." <19980824093037.55193@deepo.prosa.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Aug 1998 11:15:07 +0200 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > William Woods writes: > > > > I just compiled todays cvsup of current and all is fine except this. Here is a > > portion of my firewall rules: > > > > ------------------------------------- > > 00100 allow ip from any to any via lo0 > > 00200 deny ip from any to 127.0.0.0/8 > > 65000 allow ip from any to any > > 65535 allow ip from any to any > > 00000 deny ip from any to any > > 00000 deny ip from any to any > > [...] > > options IPFIREWALL #firewall > > options IPFIREWALL_VERBOSE #print information about > > # dropped packets > > options IPFIREWALL_FORWARD #enable xparent proxy support > > options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity > > options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default > > options IPDIVERT #divert sockets > > options IPFILTER #kernel ipfilter support > > options IPFILTER_LOG #ipfilter logging > > #options IPFILTER_LKM #kernel support for ip_fil.o LKM > > Why do you have both IPFILTER and IPFW ? > Same problem here. But just the following entries: options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about options IPDIVERT #divert sockets Also when I run 'ipfw show' I get exactly 1024 lines of output. Might this be related to the recent mbuf changes ??? Paul -- Paul van der Zwan paulz @ trantor.stuyts.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 Mon Aug 24 02:50:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA27130 for freebsd-current-outgoing; Mon, 24 Aug 1998 02:50:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA27118 for ; Mon, 24 Aug 1998 02:50:55 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hvergelmir.ifi.uio.no (2602@hvergelmir.ifi.uio.no [129.240.64.129]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id LAA18550 for ; Mon, 24 Aug 1998 11:50:09 +0200 (MET DST) Received: (from dag-erli@localhost) by hvergelmir.ifi.uio.no ; Mon, 24 Aug 1998 11:50:08 +0200 (MET DST) Mime-Version: 1.0 To: current@FreeBSD.ORG Subject: SCSI cd driver and SLICE Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 24 Aug 1998 11:50:07 +0200 Message-ID: Lines: 23 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id CAA27123 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The cd driver has been broken for some time now on SLICE systems. With a SLICE kernel, any attempt at doing anything with an audio CD results in a deadlock (e.g. 'tosha -i' hanging in vn_lock state). The drive bay is locked solid, cdcontrol can't unlock it (and hangs in vn_lock). If I try to reboot, the system may or may not succeed in syncing the disks, but does not set the clean flag on the root filesystem, and either hangs after the sync or complains about a deadlock and panics (no dump available, despite running with the fixed kern_shutdown.c and autoconf.c). One other thing is that the device nodes for the CD aren't present (except for /dev/cd0) - I have to try to mount the CD first (which won't work since it's an audio CD, but will make the device nodes appear). Mounting cd9660 CDs seems to work fine. If someone wants a dump, I could try forcing a panic with the kernel debugger and see if it dumps. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 02:59:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28040 for freebsd-current-outgoing; Mon, 24 Aug 1998 02:59:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28030 for ; Mon, 24 Aug 1998 02:59:32 -0700 (PDT) (envelope-from pb@hsc.fr) Received: from mars.hsc.fr (mars.hsc.fr [192.70.106.44]) by itesec.hsc.fr (8.8.8/8.8.5/itesec-1.12-nospam) with ESMTP id LAA14025; Mon, 24 Aug 1998 11:58:18 +0200 (MET DST) Received: (from pb@localhost) by mars.hsc.fr (8.8.8/8.8.8/pb-19980526) id LAA15562; Mon, 24 Aug 1998 11:58:17 +0200 (CEST) (envelope-from pb) Message-ID: <19980824115816.A15512@mars.hsc.fr> Date: Mon, 24 Aug 1998 11:58:16 +0200 From: Pierre Beyssac To: Alexander Sanda , freebsd-current@FreeBSD.ORG Subject: Re: encountered possible VM bug ? References: <19980824111923.A207@compufit.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: <19980824111923.A207@compufit.at>; from Alexander Sanda on Mon, Aug 24, 1998 at 11:19:23AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 24, 1998 at 11:19:23AM +0200, Alexander Sanda wrote: > "realloc() junk pointer, too low" as an error message from inetd. > > I had to kill and restart inetd to restore normal operation. > > What the hell happened to inetd ? Under out of memory conditions, inetd tends to fall in a weird state. Apparently this is an interaction between the malloc library and inetd, but nobody has managed yet to find out exactly what happens. Maybe error checking is lacking somewhere. -- Pierre.Beyssac@hsc.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 03:03:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA28611 for freebsd-current-outgoing; Mon, 24 Aug 1998 03:03:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from maks.bhg.ru (dialup-29186.dialup.ptt.ru [195.34.29.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA28600 for ; Mon, 24 Aug 1998 03:03:36 -0700 (PDT) (envelope-from ramax@maks.bhg.ru) Received: from news (ramax.maks.ru [10.0.0.4]) by maks.bhg.ru (8.8.5/8.8.5) with SMTP id OAA00991 for ; Mon, 24 Aug 1998 14:00:51 GMT Date: Mon, 24 Aug 1998 14:02:13 +0400 From: =?Windows-1251?B?zODq8ejsINDg5eLx6ujpIA==?= =?Windows-1251?B??= X-Mailer: The Bat! (v1.020) S/N 35751953 Reply-To: =?Windows-1251?B?zODq8ejsINDg5eLx6ujpIA==?= =?Windows-1251?B??= Organization: MAKS Message-ID: <1584.980824@maks.bhg.ru> To: freebsd-current@FreeBSD.ORG Subject: Re: encountered possible VM bug ? References: <19980824111923.A207@compufit.at> Mime-Version: 1.0 Content-Type: text/plain; charset=Windows-1251 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Alexander, AS> I'am running -current (dated 08/17) on a PPro/200, Gigabyte MB, 128 M. AS> Ok, what happened ? AS> While I was playing with the KDE newsreader (krn), I encountered a bug AS> in krn, probably caused by some kind of infinite recursion or similar. AS> Fact is, while krn tried to "thread" a group, it started to eat memory AS> like crazy. After a while, I noticed quite a bit swapping. I checked AS> ps, and found out that krn has allocated more than 160 MB (!!) of RAM AS> (I have 128 physical, about 100 MB swap). I assume, that the overall AS> memory consumtion of the system must have been somewhere around 200 MB AS> at this time. I was running X, full KDE desktop; a Netscape session and AS> a copy of gimp were active on another desktop aswell). However, I AS> managed to kill -9 the crazy krn app, and everything seemed to be ok. AS> The only message I found in the log is: AS> Aug 24 01:53:05 darkstar /kernel: swap_pager: suggest more swap space: 254 MB AS> Next time, I tried to connect to my local newsserver (nntpd, handled by AS> inetd), I got an error. I telnet'ed to port 119 and got something like AS> "realloc() junk pointer, too low" as an error message from inetd. AS> I had to kill and restart inetd to restore normal operation. AS> What the hell happened to inetd ? AS> BTW: no other problems occured so far; system is still up and running. I am following KDE mailing lists. There was a mention of a memory leak in KDE, confirmed (as fat as I understood) by the programmers. So keep calm, it's not FreeBSD-related To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 03:06:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29207 for freebsd-current-outgoing; Mon, 24 Aug 1998 03:06:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29174 for ; Mon, 24 Aug 1998 03:05:50 -0700 (PDT) (envelope-from netchild@wurzelausix.cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id MAA24637 for ; Mon, 24 Aug 1998 12:05:00 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (vodix.cs.uni-sb.de [134.96.247.43]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id MAA04378 for ; Mon, 24 Aug 1998 12:05:00 +0200 (CEST) Message-ID: <35E13ACB.10D29949@wurzelausix.cs.uni-sb.de> Date: Mon, 24 Aug 1998 12:04:59 +0200 From: Alexander Leidinger Organization: Uni-SB, Lehrstuhl für Rechnerarchitektur X-Mailer: Mozilla 4.05 [de] (X11; U; SunOS 5.7 i86pc) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: printer didn't work after cvsup Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, short: cvsup from 21th & 22th. After make world/kernel my printer didn't print anymore. (nlpt0, ppbus) long: It's a Deskjet500 compatible printer. After turning power on (printer) it resets itself (thats normal, all LEDs on for a short time, after that the LEDs display the status). But instead of going online all LEDs went on again. It seems my printer gets a permanent reset signal (If the PC isn't turned on, the same thing happens, so i assume there is something "LOW" which must be "HIGH"). If I send something directly (echo blubb >/dev/lpt0) the LEDs display for a short time the status, but after that the went all on again. If I print something (lpr xxx) nothing going on (it gets schedulled correctly in the queue, which isn't stopped or disabled). Bye, Alexander. -- 2^{F_{h+1}-1} z^{F_{h+2}-1} + 2^{F_{h+1}-2} L_{h-1} z^{F_{h+2}} + complicated terms + 2^{h-1} z^{2^h - 2} + z^{2^h - 1} Donald E. Knuth, "The Art of Computer Programming" http://fsinfo.cs.uni-sb.de/~netchild mailto:netchild@studcs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 03:14:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29917 for freebsd-current-outgoing; Mon, 24 Aug 1998 03:14:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pasebo.nnettown.or.jp (pasebo.nnettown.or.jp [202.229.198.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29911 for ; Mon, 24 Aug 1998 03:14:18 -0700 (PDT) (envelope-from sean@pasebo.nnet.ne.jp) Received: from mail.nnet.ne.jp (fire.nnet.ne.jp [202.229.198.15]) by pasebo.nnettown.or.jp (8.9.1/3.5Wpl7-pasebo-97/08/31/18) with ESMTP id TAA03797 for ; Mon, 24 Aug 1998 19:13:43 +0900 (JST) Message-ID: <35E13D49.3B9F3FCA@mail.nnet.ne.jp> Date: Mon, 24 Aug 1998 19:15:37 +0900 From: Sean Bennett Reply-To: sean@pasebo.nnet.ne.jp Organization: N-NET (Nakamura Shoji Co.) X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: What happened to my 'find' command?? Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [running FreeBSD 2.2.6] Hi all; last week my 'find' command suddenly went on the fritz; find / -name -print used to work fine, searching my whole disk for the file in question. Now however, it immediately prints out a list of 50-60 lines like the following, yet can't find which I know does exist. sean# find / -name httpd -print *returns* find: /usr/include/isofs: No such file or directory find: /usr/include/machine: No such file or directory find: /usr/include/msdosfs: No such file or directory find: /usr/include/net: No such file or directory find: /usr/include/netatalk: No such file or directory ... -OR- sean# find . -name httpd -print *returns* find: ./usr/include/isofs: No such file or directory find: ./usr/include/machine: No such file or directory find: ./usr/include/msdosfs: No such file or directory find: ./usr/include/net: No such file or directory find: ./usr/include/netatalk: No such file or directory .... The directories, such as "/usr/include/isofs" do infact exist. Any ideas as to what's wrong, or what changed; these commands worked in the past. I even ftp'd a new 'find' command from a working server, but get the same results. TIA Sean sean@mail.nnet.ne.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 03:22:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA01348 for freebsd-current-outgoing; Mon, 24 Aug 1998 03:22:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01339 for ; Mon, 24 Aug 1998 03:21:57 -0700 (PDT) (envelope-from netchild@wurzelausix.cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id MAA24725 for ; Mon, 24 Aug 1998 12:21:10 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (vodix.cs.uni-sb.de [134.96.247.43]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id MAA04559 for ; Mon, 24 Aug 1998 12:21:09 +0200 (CEST) Message-ID: <35E13E95.F6ACD682@wurzelausix.cs.uni-sb.de> Date: Mon, 24 Aug 1998 12:21:09 +0200 From: Alexander Leidinger Organization: Uni-SB, Lehrstuhl für Rechnerarchitektur X-Mailer: Mozilla 4.05 [de] (X11; U; SunOS 5.7 i86pc) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: kbd hang with damaged(?) ide-HD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Configuration: - current from ~4 weeks ago, not tested with actual cvsup. - Master HD: SCSI - first IDE bus: CD-ROM - second IDE bus: HD (added), CD-ROM On SCSI: - Win98 (needed for Unreal) - current whats wrong: I've formatted the IDE drive as described in the handbook (disklabel, newfs). Worked perfectly, but after booting Win, playing Unreal and the booting again into current the system didn't react anymore on a key-press. Normaly I see "login:" just before X goes up, but in this situation it was a little bit before this message. X comes up without problems, but if I try to enter something sothing happens. Mouse works. After disabling mounting of the IDE drive in /etc/fstab everything works fine. Bye, Alexander. -- 2^{F_{h+1}-1} z^{F_{h+2}-1} + 2^{F_{h+1}-2} L_{h-1} z^{F_{h+2}} + complicated terms + 2^{h-1} z^{2^h - 2} + z^{2^h - 1} Donald E. Knuth, "The Art of Computer Programming" http://fsinfo.cs.uni-sb.de/~netchild mailto:netchild@studcs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 03:30:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA02468 for freebsd-current-outgoing; Mon, 24 Aug 1998 03:30:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA02407 for ; Mon, 24 Aug 1998 03:29:58 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id GAA13383; Mon, 24 Aug 1998 06:29:11 -0400 (EDT) (envelope-from luoqi) Date: Mon, 24 Aug 1998 06:29:11 -0400 (EDT) From: Luoqi Chen Message-Id: <199808241029.GAA13383@lor.watermarkgroup.com> To: current@FreeBSD.ORG, scrappy@hub.org Subject: Re: AVA-1505 card for CDR...system hang... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Morning... > > The other day, I purchased an AVA-1505 SCSI card in order to move > my external CD-R to a seperate SCSI bus, because I was having problems > writing CDs. When the system boots, it recognizes the AVA and the CDR, > but as soon as I get to a login prompt, if I try to do a mount of a > known-to-work CD, it hangs and tells me that 'cd1 timed out', and just > hangs there indefinitely. > > It *feels* like an IRQ conflict, except I can't find one looking > through both a boot and a boot -v. The boot -v included here is for a > system with just the NCR controller (boot drive(s)), video controller and > the AVA-1505 controller. The operating system is 3.0-CURRENT as of > yesterday, no CAM drivers. > > Can someone suggestion something that I'm overlooking here? Or is > there a known problem with the 1505's that I missed? > > Thanks... > > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org There are two jumpers you need to set if you change the IRQ settings (how stupid!), make sure both of them are set to the *same* IRQ value. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 03:40:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA04113 for freebsd-current-outgoing; Mon, 24 Aug 1998 03:40:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04107 for ; Mon, 24 Aug 1998 03:40:50 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id LAA16853; Mon, 24 Aug 1998 11:39:58 +0100 (BST) Message-ID: <35E142FC.56D506E@tdx.co.uk> Date: Mon, 24 Aug 1998 11:39:56 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b1 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: sean@pasebo.nnet.ne.jp CC: current@FreeBSD.ORG Subject: Re: What happened to my 'find' command?? References: <35E13D49.3B9F3FCA@mail.nnet.ne.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean Bennett wrote: > last week my 'find' command suddenly went on the fritz; > > find / -name -print > > used to work fine, searching my whole disk for the file in > question. Now however, it immediately prints out a list of 50-60 > lines like the following, yet can't find which I know does exist. > > sean# find / -name httpd -print > *returns* > find: /usr/include/isofs: No such file or directory > find: /usr/include/machine: No such file or directory > find: /usr/include/msdosfs: No such file or directory > find: /usr/include/net: No such file or directory > find: /usr/include/netatalk: No such file or directory > [snip] Just a quick thought - Are you sure your running Find as root, or someone who actually has full permission to go search those directories? Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 04:03:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08195 for freebsd-current-outgoing; Mon, 24 Aug 1998 04:03:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08164 for ; Mon, 24 Aug 1998 04:03:07 -0700 (PDT) (envelope-from netchild@wurzelausix.cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id NAA25063 for ; Mon, 24 Aug 1998 13:02:11 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (vodix.cs.uni-sb.de [134.96.247.43]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id NAA05063 for ; Mon, 24 Aug 1998 13:02:11 +0200 (CEST) Message-ID: <35E14833.FD00676F@wurzelausix.cs.uni-sb.de> Date: Mon, 24 Aug 1998 13:02:11 +0200 From: Alexander Leidinger Organization: Uni-SB, Lehrstuhl für Rechnerarchitektur X-Mailer: Mozilla 4.05 [de] (X11; U; SunOS 5.7 i86pc) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: sysinstall bug Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Configuration: - ASUS P2L97-S - 1x SCSI-HD (Main-disk) - 1. IDE-bus: CD-ROM - 2. IDE-bus: HD (added), CD-ROM - current from 22th (cvsup). symptom: After adding the IDE-drive sysinstall isn't able to find any HD (for labeling, ...). Bye, Alexander. -- 2^{F_{h+1}-1} z^{F_{h+2}-1} + 2^{F_{h+1}-2} L_{h-1} z^{F_{h+2}} + complicated terms + 2^{h-1} z^{2^h - 2} + z^{2^h - 1} Donald E. Knuth, "The Art of Computer Programming" http://fsinfo.cs.uni-sb.de/~netchild mailto:netchild@studcs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 05:04:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15649 for freebsd-current-outgoing; Mon, 24 Aug 1998 05:04:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15644 for ; Mon, 24 Aug 1998 05:04:39 -0700 (PDT) (envelope-from ekagarc@kkeka.ericsson.se) Received: from kkdus8.kkeka.ericsson.se (kkdus8.kkeka.ericsson.se [130.100.159.107]) by penguin.wise.edt.ericsson.se (8.9.0/8.9.0/glacier-1.11) with ESMTP id OAA14415; Mon, 24 Aug 1998 14:03:48 +0200 (MET DST) Received: from kkeka.ericsson.se (kkdus7.kkeka.ericsson.se [130.100.158.73]) by kkdus8.kkeka.ericsson.se (8.8.8/8.8.8) with ESMTP id OAA16913; Mon, 24 Aug 1998 14:03:46 +0200 (MET DST) Message-ID: <35E156A1.DE22CDA4@kkeka.ericsson.se> Date: Mon, 24 Aug 1998 14:03:46 +0200 From: Felipe Garcia Organization: Ericsson Conentents AB Energy Systems Devision X-Mailer: Mozilla 4.05 [en] (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: Alexander Leidinger , "freebsd-current@FreeBSD.ORG" Subject: Re: sysinstall bug References: <35E14833.FD00676F@wurzelausix.cs.uni-sb.de> Content-Type: multipart/alternative; boundary="------------B4A4D89AB92489ACFCC8600D" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------B4A4D89AB92489ACFCC8600D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Alexander Leidinger wrote: > Hi, > > Configuration: > - ASUS P2L97-S > - 1x SCSI-HD (Main-disk) > - 1. IDE-bus: CD-ROM > - 2. IDE-bus: HD (added), CD-ROM > - current from 22th (cvsup). > > symptom: > After adding the IDE-drive sysinstall isn't able to find any HD (for > labeling, ...). > > Bye, > Alexander. > try booting with 1:sd(0,a)kernal or somthing like that. Once you find the right combination create a file in / (root) called boot.config containing the right boot command, i.e. 1:sd(0,a)kernal or what ever works for you. The Reason being that you scsi disk is probally bios disk1 (not 0) and after booting up the kernel trys to mount scsi disk (bios disk number ) which is wrong if you have and IDE in the way. scsi disk(bios disk number) is then sd1 nor sd0 and PANIK!! > -- > 2^{F_{h+1}-1} z^{F_{h+2}-1} + 2^{F_{h+1}-2} L_{h-1} z^{F_{h+2}} > + complicated terms + 2^{h-1} z^{2^h - 2} + z^{2^h - 1} > Donald E. Knuth, "The Art of Computer Programming" > http://fsinfo.cs.uni-sb.de/~netchild mailto:netchild@studcs.uni-sb.de > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- =--------=/////////////////\\\\\\\\\\\\\\\\\\\\=--------= ((___)) | Felipe Garcia | ((___)) [ x x ] | ekagarc@kkeka.ericsson.se | [ x x ] \ / =\\\\\\\\\\\\\\\\\////////////////////= \ / (' ') | | (' ') (U) | Live UNIX or DIE | (U) =--------=-------------------------------------=--------= Definition of Win 95 32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. --------------B4A4D89AB92489ACFCC8600D Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Alexander Leidinger wrote:
Hi,

Configuration:
 - ASUS P2L97-S
 - 1x SCSI-HD (Main-disk)
 - 1. IDE-bus: CD-ROM
 - 2. IDE-bus: HD (added), CD-ROM
 - current from 22th (cvsup).

symptom:
After adding the IDE-drive sysinstall isn't able to find any HD (for
labeling, ...).

Bye,
Alexander.
 

try booting with 1:sd(0,a)kernal  or somthing like that. Once you find the right combination create a file in /  (root) called boot.config containing the right boot command, i.e. 1:sd(0,a)kernal  or what ever works for you.

The Reason being that you scsi disk is probally bios disk1 (not 0) and after booting up the kernel trys to mount scsi disk (bios disk number ) which is wrong if you have and IDE in the way.  scsi disk(bios disk number) is then sd1 nor sd0 and PANIK!!
 
 

--
2^{F_{h+1}-1} z^{F_{h+2}-1} + 2^{F_{h+1}-2} L_{h-1} z^{F_{h+2}}
+ complicated terms + 2^{h-1} z^{2^h - 2} + z^{2^h - 1}
                      Donald E. Knuth, "The Art of Computer Programming"
http://fsinfo.cs.uni-sb.de/~netchild    mailto:netchild@studcs.uni-sb.de

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

  
-- 
=--------=/////////////////\\\\\\\\\\\\\\\\\\\\=--------=
 ((___)) |           Felipe Garcia             | ((___))
 [ x x ] |      ekagarc@kkeka.ericsson.se      | [ x x ]
  \   /  =\\\\\\\\\\\\\\\\\////////////////////=  \   / 
  (' ')  |                                     |  (' ')
   (U)   |         Live UNIX or DIE            |   (U)
=--------=-------------------------------------=--------=
                 Definition of Win 95
 32 bit extensions and a graphical shell for a 16 bit
 patch to an 8 bit operating system originally coded
 for a 4 bit microprocessor, written by a 2 bit company
 that can't stand 1 bit of competition.
  --------------B4A4D89AB92489ACFCC8600D-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 05:14:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17070 for freebsd-current-outgoing; Mon, 24 Aug 1998 05:14:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA16987 for ; Mon, 24 Aug 1998 05:13:58 -0700 (PDT) (envelope-from netchild@wurzelausix.cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id OAA25698 for ; Mon, 24 Aug 1998 14:13:01 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (vodix.cs.uni-sb.de [134.96.247.43]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id OAA05998 for ; Mon, 24 Aug 1998 14:13:01 +0200 (CEST) Message-ID: <35E158CD.33AA8FC9@wurzelausix.cs.uni-sb.de> Date: Mon, 24 Aug 1998 14:13:01 +0200 From: Alexander Leidinger Organization: Uni-SB, Lehrstuhl für Rechnerarchitektur X-Mailer: Mozilla 4.05 [de] (X11; U; SunOS 5.7 i86pc) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: [Fwd: sysinstall bug] Content-Type: multipart/mixed; boundary="------------54ACD537EB22D2CB634D2D3A" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------54ACD537EB22D2CB634D2D3A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit What about configuring majordomo to set the reply-to field to the list? Bye, Alexander. -- 2^{F_{h+1}-1} z^{F_{h+2}-1} + 2^{F_{h+1}-2} L_{h-1} z^{F_{h+2}} + complicated terms + 2^{h-1} z^{2^h - 2} + z^{2^h - 1} Donald E. Knuth, "The Art of Computer Programming" http://fsinfo.cs.uni-sb.de/~netchild mailto:netchild@studcs.uni-sb.de --------------54ACD537EB22D2CB634D2D3A Content-Type: message/rfc822 Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-ID: <35E15879.E27D90F@wurzelausix.cs.uni-sb.de> Date: Mon, 24 Aug 1998 14:11:37 +0200 From: Alexander Leidinger Organization: Uni-SB, Lehrstuhl für Rechnerarchitektur X-Mailer: Mozilla 4.05 [de] (X11; U; SunOS 5.7 i86pc) MIME-Version: 1.0 To: Felipe Garcia Subject: Re: sysinstall bug References: <35E14833.FD00676F@wurzelausix.cs.uni-sb.de> <35E156A1.DE22CDA4@kkeka.ericsson.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Felipe Garcia schrieb: > > After adding the IDE-drive sysinstall isn't able to find any HD (for > > labeling, ...). > try booting with 1:sd(0,a)kernal or somthing like that. Once you find > the right combination create a file in / (root) called boot.config > containing the right boot command, i.e. 1:sd(0,a)kernal or what ever > works for you. > > The Reason being that you scsi disk is probally bios disk1 (not 0) and > after booting up the kernel trys to mount scsi disk (bios disk number ) > which is wrong if you have and IDE in the way. scsi disk(bios disk > number) is then sd1 nor sd0 and PANIK!! Errm, there must be a misunderstanding... It boots without problems. (Bios setting: SCSI first) But after starting /stand/sysinstall for configurating the newly added IDE-disk isn't recognized by sysinstall. And the worsest, it can't find my SCSI disk anymore. Bye, Alexander. -- 2^{F_{h+1}-1} z^{F_{h+2}-1} + 2^{F_{h+1}-2} L_{h-1} z^{F_{h+2}} + complicated terms + 2^{h-1} z^{2^h - 2} + z^{2^h - 1} Donald E. Knuth, "The Art of Computer Programming" http://fsinfo.cs.uni-sb.de/~netchild mailto:netchild@studcs.uni-sb.de --------------54ACD537EB22D2CB634D2D3A-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 06:21:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24799 for freebsd-current-outgoing; Mon, 24 Aug 1998 06:21:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA24468 for ; Mon, 24 Aug 1998 06:19:00 -0700 (PDT) (envelope-from nbm@rucus.ru.ac.za) Received: (qmail 4703 invoked by uid 1003); 24 Aug 1998 13:17:53 -0000 Message-ID: <19980824151753.A4019@rucus.ru.ac.za> Date: Mon, 24 Aug 1998 15:17:53 +0200 From: Neil Blakey-Milner To: Alexander Leidinger , freebsd-current@FreeBSD.ORG Subject: Re: [Fwd: sysinstall bug] References: <35E158CD.33AA8FC9@wurzelausix.cs.uni-sb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <35E158CD.33AA8FC9@wurzelausix.cs.uni-sb.de>; from Alexander Leidinger on Mon, Aug 24, 1998 at 02:13:01PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon 1998-08-24 (14:13), Alexander Leidinger wrote: > What about configuring majordomo to set the reply-to field to the list? It clobbers the senders address, so you have to search for that address if you want to reply personally. Also, it might remove Reply-To's that people set if they want to move the thread to other lists. And if the person sending the original message isn't on the list, he doesn't get a reply. Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 06:54:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27960 for freebsd-current-outgoing; Mon, 24 Aug 1998 06:54:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27955 for ; Mon, 24 Aug 1998 06:54:25 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with SMTP id JAA04755; Mon, 24 Aug 1998 09:52:21 -0400 (EDT) Date: Mon, 24 Aug 1998 09:52:20 -0400 (EDT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: Sean Bennett cc: "current@FreeBSD.ORG" Subject: Re: What happened to my 'find' command?? In-Reply-To: <35E13D49.3B9F3FCA@mail.nnet.ne.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you're running as root, and this is happening, you have two choices to help you find out what's going on: 1. ktrace 2. truss Go on, do one and comb through the output. Cheers, Brian Feldman On Mon, 24 Aug 1998, Sean Bennett wrote: > [running FreeBSD 2.2.6] > > Hi all; > > last week my 'find' command suddenly went on the fritz; > > find / -name -print > > used to work fine, searching my whole disk for the file in > question. Now however, it immediately prints out a list of 50-60 > lines like the following, yet can't find which I know does exist. > > sean# find / -name httpd -print > *returns* > find: /usr/include/isofs: No such file or directory > find: /usr/include/machine: No such file or directory > find: /usr/include/msdosfs: No such file or directory > find: /usr/include/net: No such file or directory > find: /usr/include/netatalk: No such file or directory > ... > > -OR- > > sean# find . -name httpd -print > *returns* > find: ./usr/include/isofs: No such file or directory > find: ./usr/include/machine: No such file or directory > find: ./usr/include/msdosfs: No such file or directory > find: ./usr/include/net: No such file or directory > find: ./usr/include/netatalk: No such file or directory > .... > > The directories, such as "/usr/include/isofs" do infact exist. > > Any ideas as to what's wrong, or what changed; these commands > worked in the past. I even ftp'd a new 'find' command from a > working server, but get the same results. > > > > TIA > > Sean > sean@mail.nnet.ne.jp > > > > 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 Aug 24 07:14:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01303 for freebsd-current-outgoing; Mon, 24 Aug 1998 07:14:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01297 for ; Mon, 24 Aug 1998 07:14:39 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA26862; Mon, 24 Aug 1998 10:13:46 -0400 (EDT) (envelope-from wollman) Date: Mon, 24 Aug 1998 10:13:46 -0400 (EDT) From: Garrett Wollman Message-Id: <199808241413.KAA26862@khavrinen.lcs.mit.edu> To: Pierre Beyssac Cc: Alexander Sanda , freebsd-current@FreeBSD.ORG Subject: Re: encountered possible VM bug ? In-Reply-To: <19980824115816.A15512@mars.hsc.fr> References: <19980824111923.A207@compufit.at> <19980824115816.A15512@mars.hsc.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Under out of memory conditions, inetd tends to fall in a weird > state. Apparently this is an interaction between the malloc library > and inetd, but nobody has managed yet to find out exactly what > happens. Maybe error checking is lacking somewhere. No, this is the ``daemons dying'' bug which nobody has fixed yet. When the system runs out of swap, some random selection of processes which are in swap get corrupted. Usually this results in a daemon which dies whenever it fork()s, but sometimes it is manifested as other sorts of corruption. The message you see from realloc is indicative of a corrupted pointer. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 07:37:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03715 for freebsd-current-outgoing; Mon, 24 Aug 1998 07:37:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03706 for ; Mon, 24 Aug 1998 07:37:11 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with SMTP id KAA06702; Mon, 24 Aug 1998 10:35:03 -0400 (EDT) Date: Mon, 24 Aug 1998 10:35:03 -0400 (EDT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: PicoBSD CVS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And what about src/release? Wouldn't it make sense for the PicoBSD, being a floppy image, to live near where its cousins (parents? :) boot.flp and fixit.flp live? Cheers, Brian Feldman On Mon, 24 Aug 1998, Andrzej Bialecki wrote: > Hi, > > I'm glad to inform you that it has been decided to put PicoBSD project > into the source tree of standard FreeBSD distribution, so that it can be > tracked closely by other people as well, using cvsup. > > The question remaining is _where_ to put it in the current hierarchy. > Perhaps /usr/src/contrib? Jordan proposed /usr/src/share, but it's > intended to keep only shared text files... What are your ideas? > > Andrzej Bialecki > > +---------------------+------------------------+--------------------------+ > | | When in problem or in | if(halt_per_mth > 0) { | > | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | > | Network in Poland | scream and shout. | } | > + --------------------+------------------------+--------------------------+ > > > 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 Aug 24 08:06:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07159 for freebsd-current-outgoing; Mon, 24 Aug 1998 08:06:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07154 for ; Mon, 24 Aug 1998 08:06:34 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id IAA17984; Mon, 24 Aug 1998 08:05:05 -0700 (PDT) (envelope-from dhw) Date: Mon, 24 Aug 1998 08:05:05 -0700 (PDT) From: David Wolfskill Message-Id: <199808241505.IAA17984@pau-amma.whistle.com> To: freebsd-current@FreeBSD.ORG, netchild@wurzelausix.cs.uni-sb.de Subject: Re: [Fwd: sysinstall bug] In-Reply-To: <35E158CD.33AA8FC9@wurzelausix.cs.uni-sb.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Mon, 24 Aug 1998 14:13:01 +0200 >From: Alexander Leidinger >What about configuring majordomo to set the reply-to field to the list? Well, that would break significant usefulness of the list, from my perspective. Is there a problem you're trying to solve? david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 08:13:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08412 for freebsd-current-outgoing; Mon, 24 Aug 1998 08:13:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08403 for ; Mon, 24 Aug 1998 08:13:46 -0700 (PDT) (envelope-from netchild@wurzelausix.cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id RAA27474; Mon, 24 Aug 1998 17:12:28 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (vodix.cs.uni-sb.de [134.96.247.43]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id RAA08671; Mon, 24 Aug 1998 17:12:27 +0200 (CEST) Message-ID: <35E182DB.12FE8E68@wurzelausix.cs.uni-sb.de> Date: Mon, 24 Aug 1998 17:12:27 +0200 From: Alexander Leidinger Organization: Uni-SB, Lehrstuhl für Rechnerarchitektur X-Mailer: Mozilla 4.05 [de] (X11; U; SunOS 5.7 i86pc) MIME-Version: 1.0 To: David Wolfskill , freebsd-current@FreeBSD.ORG Subject: Majordomo and reply-to (was: [Fwd: sysinstall bug]) References: <199808241505.IAA17984@pau-amma.whistle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Wolfskill schrieb: > Is there a problem you're trying to solve? No, but most of the time I have the "Sh*t! No freebsd-current@... in the to-field." effect. Bye, Alexander. -- 2^{F_{h+1}-1} z^{F_{h+2}-1} + 2^{F_{h+1}-2} L_{h-1} z^{F_{h+2}} + complicated terms + 2^{h-1} z^{2^h - 2} + z^{2^h - 1} Donald E. Knuth, "The Art of Computer Programming" http://fsinfo.cs.uni-sb.de/~netchild mailto:netchild@studcs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 08:21:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09629 for freebsd-current-outgoing; Mon, 24 Aug 1998 08:21:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hotmail.com (f222.hotmail.com [207.82.251.113]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA09616 for ; Mon, 24 Aug 1998 08:21:31 -0700 (PDT) (envelope-from troogzork@hotmail.com) Received: (qmail 24904 invoked by uid 0); 24 Aug 1998 15:20:46 -0000 Message-ID: <19980824152046.24903.qmail@hotmail.com> Received: from 204.253.137.241 by www.hotmail.com with HTTP; Mon, 24 Aug 1998 08:20:45 PDT X-Originating-IP: [204.253.137.241] From: "Michael Imamura" To: freebsd-current@FreeBSD.ORG Subject: Re: encountered possible VM bug ? Content-Type: text/plain Date: Mon, 24 Aug 1998 08:20:45 PDT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Would this be related to my problem of cron all of a sudden dying off repeatedly, sometimes every few minutes, after the system has been compiling for a while? - Michael Imamura Ucod Data Systems http://i.am/ucod/ >Date: Mon, 24 Aug 1998 10:13:46 -0400 (EDT) >From: Garrett Wollman >To: Pierre Beyssac >Cc: Alexander Sanda , freebsd-current@FreeBSD.ORG >Subject: Re: encountered possible VM bug ? > >< said: > >> Under out of memory conditions, inetd tends to fall in a weird >> state. Apparently this is an interaction between the malloc library >> and inetd, but nobody has managed yet to find out exactly what >> happens. Maybe error checking is lacking somewhere. > >No, this is the ``daemons dying'' bug which nobody has fixed yet. >When the system runs out of swap, some random selection of processes >which are in swap get corrupted. Usually this results in a daemon >which dies whenever it fork()s, but sometimes it is manifested as >other sorts of corruption. The message you see from realloc is >indicative of a corrupted pointer. > >-GAWollman > >-- >Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same >wollman@lcs.mit.edu | O Siem / The fires of freedom >Opinions not those of| Dance in the burning flame >MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 09:04:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17458 for freebsd-current-outgoing; Mon, 24 Aug 1998 09:04:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gwinnett.gwinnett.com (mail.gwinnett.com [204.89.227.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17453; Mon, 24 Aug 1998 09:04:29 -0700 (PDT) (envelope-from lee@gwinnett.com) Received: from venus.gwinnett.com ([204.89.227.91]) by gwinnett.gwinnett.com (8.9.1a/8.8.5) with SMTP id MAA11633; Mon, 24 Aug 1998 12:03:44 -0400 Message-ID: <35E18DC8.41C67EA6@gwinnett.com> Date: Mon, 24 Aug 1998 11:59:04 -0400 From: Lee Reese X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG CC: freebsd-current@FreeBSD.ORG Subject: SCSI devices on FIC VA-2013 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone had trouble with SCSI (like HP Scanners and Yamaha Cd-writers) devices when using a FIC PA-2013 (or VA-503+)? Thanks. Lee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 09:07:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18114 for freebsd-current-outgoing; Mon, 24 Aug 1998 09:07:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18081 for ; Mon, 24 Aug 1998 09:07:10 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id MAA28618; Mon, 24 Aug 1998 12:06:20 -0400 (EDT) (envelope-from wollman) Date: Mon, 24 Aug 1998 12:06:20 -0400 (EDT) From: Garrett Wollman Message-Id: <199808241606.MAA28618@khavrinen.lcs.mit.edu> To: "Michael Imamura" Cc: freebsd-current@FreeBSD.ORG Subject: Re: encountered possible VM bug ? In-Reply-To: <19980824152046.24903.qmail@hotmail.com> References: <19980824152046.24903.qmail@hotmail.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Would this be related to my problem of cron all of a sudden dying off > repeatedly, sometimes every few minutes, after the system has been > compiling for a while? Yes. If cron gets into this state, then it will segfault every five minutes as it attempts to run atrun. [I wrote:] >> No, this is the ``daemons dying'' bug which nobody has fixed yet. >> When the system runs out of swap, some random selection of processes >> which are in swap get corrupted. Usually this results in a daemon >> which dies whenever it fork()s, but sometimes it is manifested as >> other sorts of corruption. The message you see from realloc is >> indicative of a corrupted pointer. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 09:12:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19405 for freebsd-current-outgoing; Mon, 24 Aug 1998 09:12:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19261 for ; Mon, 24 Aug 1998 09:11:59 -0700 (PDT) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-14-100.camtech.net.au [203.55.242.228]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id BAA01707; Tue, 25 Aug 1998 01:40:21 +0930 (CST) Message-ID: <35E18FF5.B7FADA7B@camtech.net.au> Date: Tue, 25 Aug 1998 01:38:21 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Wolfram Schneider CC: current@FreeBSD.ORG Subject: Re: file segment sizes of a core dump References: <199808231906.VAA04727@campa.panke.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why require an option ? Why not make size do what you want automatically when it detects that you are running it on a core file ? Possibly an informational message should be printed to stderr something like "sh.core is a core file" Wolfram Schneider wrote: > > I added an option to size(1) which print the > file segment sizes of a core dump. > > For example: > > $ ./size /bin/sh > text data bss dec hex > 294912 12288 35656 342856 53b48 > > $ ./size -c sh.core > text data bss dec hex > 294912 69632 131072 495616 79000 > > If nobody objects I will commit the change. [snip] > -- > Wolfram Schneider http://www.freebsd.org/~w/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 09:36:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23264 for freebsd-current-outgoing; Mon, 24 Aug 1998 09:36:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA23124 for ; Mon, 24 Aug 1998 09:36:23 -0700 (PDT) (envelope-from nbm@rucus.ru.ac.za) Received: (qmail 20097 invoked by uid 1003); 24 Aug 1998 16:35:03 -0000 Message-ID: <19980824183503.A19727@rucus.ru.ac.za> Date: Mon, 24 Aug 1998 18:35:03 +0200 From: Neil Blakey-Milner To: freebsd-current@FreeBSD.ORG Subject: Re: Majordomo and reply-to (was: [Fwd: sysinstall bug]) References: <199808241505.IAA17984@pau-amma.whistle.com> <35E182DB.12FE8E68@wurzelausix.cs.uni-sb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <35E182DB.12FE8E68@wurzelausix.cs.uni-sb.de>; from Alexander Leidinger on Mon, Aug 24, 1998 at 05:12:27PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon 1998-08-24 (17:12), Alexander Leidinger wrote: > No, but most of the time I have the > "Sh*t! No freebsd-current@... in the to-field." > effect. If you're using elm or mutt, use "g" for group reply. Get used to it. Make it your default. It'll be your friend. :) Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 10:33:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03192 for freebsd-current-outgoing; Mon, 24 Aug 1998 10:33:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03183 for ; Mon, 24 Aug 1998 10:33:25 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:9m7/UqFmGLcKFDFeqvMnu7bwXKHJRHTn@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id TAA05102; Mon, 24 Aug 1998 19:31:17 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199808241731.TAA05102@gratis.grondar.za> To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: PicoBSD CVS Date: Mon, 24 Aug 1998 19:31:14 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > Hi, > > I'm glad to inform you that it has been decided to put PicoBSD project > into the source tree of standard FreeBSD distribution, so that it can be > tracked closely by other people as well, using cvsup. > > The question remaining is _where_ to put it in the current hierarchy. > Perhaps /usr/src/contrib? Jordan proposed /usr/src/share, but it's > intended to keep only shared text files... What are your ideas? Put your clever stuff into a subdirectory of src/release/, and add a target to src/release/Makefile to do the "right stuff". M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 10:44:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04912 for freebsd-current-outgoing; Mon, 24 Aug 1998 10:44:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04881 for ; Mon, 24 Aug 1998 10:44:03 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id TAA17880; Mon, 24 Aug 1998 19:46:35 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 24 Aug 1998 19:46:34 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: "Robert D. Keys" cc: freebsd-current@FreeBSD.ORG Subject: Re: PicoBSD CVS In-Reply-To: <199808241424.KAA18080@seedlab1.cropsci.ncsu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Aug 1998, Robert D. Keys wrote: > > Hi, > > > > I'm glad to inform you that it has been decided to put PicoBSD project > > into the source tree of standard FreeBSD distribution, so that it can be > > tracked closely by other people as well, using cvsup. > > > > The question remaining is _where_ to put it in the current hierarchy. > > Perhaps /usr/src/contrib? Jordan proposed /usr/src/share, but it's > > intended to keep only shared text files... What are your ideas? > > I would favor /usr/src/picobsd. Hmm... But it's not a totally different category (like bin and sbin), it's just a package... > Any possibility of having picobsd come up on a 4 meg ram machine > in a commandline mode to make a tiny system work? :-)) You obviously haven't read my last announcement - go and see the good news on the PicoBSD home page. Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 10:48:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05839 for freebsd-current-outgoing; Mon, 24 Aug 1998 10:48:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05828 for ; Mon, 24 Aug 1998 10:48:42 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id TAA19798; Mon, 24 Aug 1998 19:51:41 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 24 Aug 1998 19:51:41 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Brian Feldman cc: freebsd-current@FreeBSD.ORG Subject: Re: PicoBSD CVS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Aug 1998, Brian Feldman wrote: > And what about src/release? Wouldn't it make sense for the PicoBSD, being > a floppy image, to live near where its cousins (parents? :) boot.flp and > fixit.flp live? Sounds good enough to me. But I'm not sure what Jordan thinks about cluttering his backyard... Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 11:28:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11974 for freebsd-current-outgoing; Mon, 24 Aug 1998 11:28:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcpsj.pfcs.com (harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11740 for ; Mon, 24 Aug 1998 11:27:27 -0700 (PDT) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Mon, 24 Aug 1998 14:25:00 -0400 (EDT) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Mon, 24 Aug 1998 11:24:51 -0700 (PDT) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Mon, 24 Aug 1998 14:24:50 -0400 (EDT) X-Mailer: exmh version 2.0.2 2/24/98 To: Harlan Stenn cc: Alex , Mike Smith , Alexander Sanda , wwoods@cybcon.com, freebsd-current@FreeBSD.ORG Subject: Re: gcc 2.8 In-Reply-To: Harlan Stenn's (Harlan.Stenn@pfcs.com) message dated Sat, 22 Aug 1998 22:33:46. <20089.903839626@brown.pfcs.com> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Aug 1998 14:24:49 -0400 Message-ID: <28885.903983089@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just did another test of performance using TenDRA, comparing it to FreeBSD's "cc". Basically, the performance of the overall package was the same. There are some performance differences, depending upon what sort of operations are being done. For example, switch statement dispatching seems to be *much* slower with TenDRA (this includes things like Duff's device). Certain other operations (like string length scanning) are faster, and *maybe* byte moving is slower. I can't tell exactly where different other operations might be faster or slower, since the benchmark I used is pretty coarse-grained. If I can find a TenDRA function profiler, I might be able to learn more. And I suspect it was good for me to get this code base compiling under TenDRA without TenDRA complaining... H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 11:29:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12006 for freebsd-current-outgoing; Mon, 24 Aug 1998 11:29:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from algw1.lucent.com (algw1.lucent.com [205.147.213.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA12001 for ; Mon, 24 Aug 1998 11:29:11 -0700 (PDT) (envelope-from ghiugan@algw1.lucent.com) Received: from emsr3.emsr.lucent.com by alig1.firewall.lucent.com (SMI-8.6/EMS-L sol2) id OAA26706; Mon, 24 Aug 1998 14:48:31 -0400 Received: by emsr3.emsr.lucent.com (SMI-8.6/EMS-1.2 Solaris/emsr) id OAA22482 for freebsd-current@FreeBSD.ORG.smtp; Mon, 24 Aug 1998 14:28:07 -0400 Received: from lucent.com by emsr3.emsr.lucent.com (SMI-8.6/EMS-1.2 Solaris/emsr) id OAA22477 for ; Mon, 24 Aug 1998 14:28:07 -0400 Message-ID: <35E1AFFF.4950EC6A@lucent.com> Date: Mon, 24 Aug 1998 14:25:03 -0400 From: Anton Ghiugan Reply-To: ghiugan@lucent.com Organization: Lucent Technologies X-Mailer: Mozilla 4.04 [en] (X11; U; Linux 2.0.34 i686) MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: Multihomed hosts question Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is possible to use more than one netdevice (i.e. network card) on the *same* machine and to have same IP address for both of them ? (I know it sounds stupid but I don't see any reason why not). If the answer is 'YES' then how can you "enforce" the kernel to use a specific netcard for when 'taking' to certain addresses (i.e. how can you route some addresses via a specific netcard)? Thanks P.S. : Under Linux this is possible - at least in respect with the tunnel device - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 11:39:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13851 for freebsd-current-outgoing; Mon, 24 Aug 1998 11:39:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vortex.starix.net (vortex.starix.net [208.219.83.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13845 for ; Mon, 24 Aug 1998 11:39:56 -0700 (PDT) (envelope-from syko@sykotik.org) Received: from localhost (syko@localhost) by vortex.starix.net (8.7.6/8.7.3) with SMTP id OAA01844; Mon, 24 Aug 1998 14:38:54 -0400 X-Authentication-Warning: vortex.starix.net: syko owned process doing -bs Date: Mon, 24 Aug 1998 14:38:54 -0400 (EDT) From: Dusk Auriel Sykotik X-Sender: syko@vortex.starix.net To: Alexander Leidinger cc: David Wolfskill , freebsd-current@FreeBSD.ORG Subject: Re: Majordomo and reply-to (was: [Fwd: sysinstall bug]) In-Reply-To: <35E182DB.12FE8E68@wurzelausix.cs.uni-sb.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Use pine's Reply to all recipients feature when you reply to a posting here. Thats what I do for this and all other lists. /* ** Matt Harris Syko ** BPSOFH, BIOFH, C, SQL, PERL http://www.sykotik.org/~syko/ ** FreeBSD SysAdmin sykotik.org ** IRC TechnoNet - dark.technonet.net Cabalnet - dark-temple.cabalnet.org ** "Those who are right in the mind are left in the dust." -- Me. */ On Mon, 24 Aug 1998, Alexander Leidinger wrote: > David Wolfskill schrieb: > > > Is there a problem you're trying to solve? > > No, but most of the time I have the > "Sh*t! No freebsd-current@... in the to-field." > effect. > > Bye, > Alexander. > > -- > 2^{F_{h+1}-1} z^{F_{h+2}-1} + 2^{F_{h+1}-2} L_{h-1} z^{F_{h+2}} > + complicated terms + 2^{h-1} z^{2^h - 2} + z^{2^h - 1} > Donald E. Knuth, "The Art of Computer Programming" > http://fsinfo.cs.uni-sb.de/~netchild mailto:netchild@studcs.uni-sb.de > > 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 Aug 24 11:46:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14957 for freebsd-current-outgoing; Mon, 24 Aug 1998 11:46:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ryouko.nas.nasa.gov (ryouko.nas.nasa.gov [129.99.34.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14949 for ; Mon, 24 Aug 1998 11:46:15 -0700 (PDT) (envelope-from greg@nas.nasa.gov) Received: from ryouko.nas.nasa.gov (localhost [127.0.0.1]) by ryouko.nas.nasa.gov (8.8.7/NAS.6.1) with ESMTP id LAA00873; Mon, 24 Aug 1998 11:45:02 -0700 (PDT) Message-Id: <199808241845.LAA00873@ryouko.nas.nasa.gov> To: tom@uniserve.com Cc: current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter In-reply-to: Your message of "Sun, 23 Aug 1998 10:41:20 PDT." <199808231741.KAA05988@hub.freebsd.org> Date: Mon, 24 Aug 1998 11:45:02 -0700 From: "Gregory P. Smith" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Gigabit ethernet is 125MB/s, so would use more of PCI. The only hope is > multiple independant PCI buses (some motherboards already have this). Good luck getting a single x86 CPU to handle the interrupt load of even a single card with the overhead of processing 1500 byte packets at Gigabit speeds... (based on observations of other Gig speed class drivers and NICs I've seen). ;) Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 11:54:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16148 for freebsd-current-outgoing; Mon, 24 Aug 1998 11:54:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16119 for ; Mon, 24 Aug 1998 11:53:50 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id UAA09041; Mon, 24 Aug 1998 20:51:34 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id UAA25824; Mon, 24 Aug 1998 20:40:10 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808241840.UAA25824@semyam.dinoco.de> To: Garrett Wollman cc: Kris Kennaway , Mike Smith , freebsd-current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: lpr code cleanup? (was: Re: gcc 2.8 ) In-reply-to: Your message of "Sun, 23 Aug 1998 13:40:06 EDT." <199808231740.NAA23791@khavrinen.lcs.mit.edu> Date: Mon, 24 Aug 1998 20:40:09 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The intent of this was to make sure that anyone who introduced > warnings after I had laboriously eliminated them would get pounded on > by the -current regulars for breaking the build. I took a look at the code and CWARNFLAGS didn't get used in all of the makefiles so I fixed that in a local copy of the lpr source - and of course corrected the complaints egcs (which I used for the test as it seems to be a little bit more picky than the system's gcc) gave me after doing that. In the course of doing this I found a misdeclared function. Nothing serious as it was the result type and the result wasn't used anyway. The "register varname;" definitions in some of the functions I changed to "register int varname;" which silenced egcs and is OK for K&R, too. Compiling now works for me with a recent egcs (a July snapshot) for the lpr subsystem. Don't know about the rest as I buildworld with gcc. I will now take a close look at my changes in the next few days, inte- grate it in my local source tree and then install the new executables. Maybe it still works afterward. ;-) Anybody interested in the changes I made can of course get a diff via email before I dare to send a PR. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 12:22:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22391 for freebsd-current-outgoing; Mon, 24 Aug 1998 12:22:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22386 for ; Mon, 24 Aug 1998 12:22:31 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA01194 for ; Mon, 24 Aug 1998 12:14:26 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdAy1180; Mon Aug 24 19:14:22 1998 Message-ID: <35E1BB8A.237C228A@whistle.com> Date: Mon, 24 Aug 1998 12:14:18 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: locking in -current. donate 15 minutes. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to put together a small documant describing the various aspects of locing involved in the -current kernel. this goes from the giant lock, all the way through to standard things such as the vnode locking, and more diverse things such as the FreeBSD lock-manager. locked buffers, vm objects etc. are all of interest. I have been unable to find such a document, so if anyone would like to contribute a paragraph or two about any locking they feel they can talk about, (whether a simple thing such as "locks in the foo subsystem" to: "how the lockmanager works" please send me info or pointers. examples of questions I don't have lear answers for.. "when exactly is the right time to use the "interlock" locks in vnode locking an dwhat do they do? what is an interlock in the context of the lock manager? what locking should filesystems do in SMP? how is the 'giant lock' implemented? and how does a kernel thread use it? (e.g. syncer() for soft updates) If I can get a few paragraphs from many people on this I can make something worth while from this.. spend 15 minutes to sent me a paragraph of your choice and get involved :-) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 13:22:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00485 for freebsd-current-outgoing; Mon, 24 Aug 1998 13:22:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00455 for ; Mon, 24 Aug 1998 13:22:44 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id WAA18984; Mon, 24 Aug 1998 22:21:20 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id WAA03485; Mon, 24 Aug 1998 22:17:25 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808242017.WAA03485@semyam.dinoco.de> To: Julian Elischer cc: current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: locking in -current. donate 15 minutes. In-reply-to: Your message of "Mon, 24 Aug 1998 12:14:18 PDT." <35E1BB8A.237C228A@whistle.com> Date: Mon, 24 Aug 1998 22:17:25 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If I can get a few paragraphs from many people on this I can make > something worth while from this.. Anybody wanting the VM subsysten? ;-) If nobody else does it I could try to put in writing the knowledge I got from reading the source. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 15:08:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14110 for freebsd-current-outgoing; Mon, 24 Aug 1998 15:08:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14104 for ; Mon, 24 Aug 1998 15:08:32 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id OAA02254; Mon, 24 Aug 1998 14:42:38 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Andrzej Bialecki cc: Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: PicoBSD CVS In-reply-to: Your message of "Mon, 24 Aug 1998 19:51:41 +0200." Date: Mon, 24 Aug 1998 14:42:38 -0700 Message-ID: <2251.903994958@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Mon, 24 Aug 1998, Brian Feldman wrote: > > > And what about src/release? Wouldn't it make sense for the PicoBSD, being > > a floppy image, to live near where its cousins (parents? :) boot.flp and > > fixit.flp live? > > Sounds good enough to me. But I'm not sure what Jordan thinks about > cluttering his backyard... I could live with a /usr/src/release/picobsd directory, sure. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 15:25:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16515 for freebsd-current-outgoing; Mon, 24 Aug 1998 15:25:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-db.dialup.hilink.com.au [203.2.144.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16510 for ; Mon, 24 Aug 1998 15:25:17 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00683; Mon, 24 Aug 1998 15:22:50 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808241522.PAA00683@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: ghiugan@lucent.com cc: "freebsd-current@FreeBSD.ORG" Subject: Re: Multihomed hosts question In-reply-to: Your message of "Mon, 24 Aug 1998 14:25:03 -0400." <35E1AFFF.4950EC6A@lucent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Aug 1998 15:22:49 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It is possible to use more than one netdevice (i.e. network card) on > the *same* machine and to have same IP address for both of them ? (I > know it sounds stupid but I don't see any reason why not). > If the answer is 'YES' then how can you "enforce" the kernel to use a > specific netcard for when 'taking' to certain addresses (i.e. how can > you route some addresses via a specific netcard)? It is possible to have an arbitrary number of point-to-point interfaces and one broadcast interface share an address. You can't have more than one broadcast interface cover a specific mask. > P.S. : Under Linux this is possible - at least in respect with the tunnel device Who cares? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 15:38:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18202 for freebsd-current-outgoing; Mon, 24 Aug 1998 15:38:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18197 for ; Mon, 24 Aug 1998 15:38:23 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id IAA25725; Tue, 25 Aug 1998 08:37:31 +1000 Date: Tue, 25 Aug 1998 08:37:31 +1000 From: Bruce Evans Message-Id: <199808242237.IAA25725@godzilla.zeta.org.au> To: current@FreeBSD.ORG, dag-erli@ifi.uio.no Subject: Re: SCSI cd driver and SLICE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The cd driver has been broken for some time now on SLICE systems. With >a SLICE kernel, any attempt at doing anything with an audio CD results >in a deadlock (e.g. 'tosha -i' hanging in vn_lock state). The drive SLICE systems have no special blo^H^H^Hsupport for SCSI cd devices (or non-SCSI cd devices, or od devices, or worm devices, or wfd devices ...), so the old DEVFS code gets used. Apparently it still has deadlock problems in the drivers that support slices (mainly cd, od and wfd). dsopen() calls devfs_remove_dev() on possibly-open devices, expecting it to much the same things as unlink() (just remove the device from the namespace), but DEVFS apparently does something with the possibly-open vnode and deadlocks. >bay is locked solid, cdcontrol can't unlock it (and hangs in vn_lock). >If I try to reboot, the system may or may not succeed in syncing the >disks, but does not set the clean flag on the root filesystem, and >either hangs after the sync or complains about a deadlock and panics >(no dump available, despite running with the fixed kern_shutdown.c and >autoconf.c). This is normal for a panic for an fs problem in -current. Something is likely to be locked and the sync is likely to run into it. The unmount of all file systems is certain to run in to any lock. >One other thing is that the device nodes for the CD aren't present >(except for /dev/cd0) - I have to try to mount the CD first (which >won't work since it's an audio CD, but will make the device nodes >appear). This is normal for old DEVFS/slice devices - you have to open the whole disk device to get slices and partitions generated. The open routine then flounders around looking for MBRs and labels. New DEVFS/SLICE devices are completely different. Slices and partitions are added asynchronously, initially at boot time, automatically at least for the media that is present at boot time. The mbr interrupt routines flounder and race around looking for MBRs and labels. >Mounting cd9660 CDs seems to work fine. Strange. It thought I tested it, but now always hangs on vn_loc (sic). Workaround 1: never use cd0a or cd0c. They are just compatibility cruft (aliases for cd0). dsopen() only calls devfs_remove_dev() on cd0a and cd0c, so there are no problems if they are possibly-but-not-actually open. Workaround 2: open cd0 first and keep it open until you change the disk. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 15:47:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19422 for freebsd-current-outgoing; Mon, 24 Aug 1998 15:47:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-db.dialup.hilink.com.au [203.2.144.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19417 for ; Mon, 24 Aug 1998 15:47:45 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00887; Mon, 24 Aug 1998 15:44:30 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808241544.PAA00887@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Stefan Eggers cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: locking in -current. donate 15 minutes. In-reply-to: Your message of "Mon, 24 Aug 1998 22:17:25 +0200." <199808242017.WAA03485@semyam.dinoco.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Aug 1998 15:44:29 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If I can get a few paragraphs from many people on this I can make > > something worth while from this.. > > Anybody wanting the VM subsysten? ;-) If nobody else does it I > could try to put in writing the knowledge I got from reading the > source. Please do. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 15:53:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20148 for freebsd-current-outgoing; Mon, 24 Aug 1998 15:53:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isua4.iastate.edu (isua4.iastate.edu [129.186.1.204]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20142 for ; Mon, 24 Aug 1998 15:53:56 -0700 (PDT) (envelope-from graphix@iastate.edu) Received: (from graphix@localhost) by isua4.iastate.edu (8.8.5/8.8.5) id RAA27685 for freebsd-current@freebsd.org; Mon, 24 Aug 1998 17:53:10 -0500 (CDT) Date: Mon, 24 Aug 1998 17:53:10 -0500 (CDT) From: Kent A Vander Velden Message-Id: <199808242253.RAA27685@isua4.iastate.edu> To: freebsd-current@FreeBSD.ORG Subject: Threads across processors Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. Does -current support spliting the threads of a single process across multiple processors? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 16:16:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23723 for freebsd-current-outgoing; Mon, 24 Aug 1998 16:16:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-db.dialup.hilink.com.au [203.2.144.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23717 for ; Mon, 24 Aug 1998 16:16:17 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01077; Mon, 24 Aug 1998 16:13:12 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808241613.QAA01077@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: PicoBSD CVS In-reply-to: Your message of "Mon, 24 Aug 1998 11:44:42 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Aug 1998 16:13:10 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The question remaining is _where_ to put it in the current hierarchy. > Perhaps /usr/src/contrib? Jordan proposed /usr/src/share, but it's > intended to keep only shared text files... What are your ideas? What parts are actually going to be committed? Just the build tools? I'd suggest either release/picobsd, share/examples/picobsd or tools/picobsd. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 16:50:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27688 for freebsd-current-outgoing; Mon, 24 Aug 1998 16:50:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27683 for ; Mon, 24 Aug 1998 16:50:23 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id BAA04601 for freebsd-current@FreeBSD.ORG; Tue, 25 Aug 1998 01:49:32 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 1E5291543; Tue, 25 Aug 1998 01:19:52 +0200 (CEST) Message-ID: <19980825011952.A21110@keltia.freenix.fr> Date: Tue, 25 Aug 1998 01:19:52 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: Majordomo and reply-to (was: [Fwd: sysinstall bug]) Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199808241505.IAA17984@pau-amma.whistle.com> <35E182DB.12FE8E68@wurzelausix.cs.uni-sb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <35E182DB.12FE8E68@wurzelausix.cs.uni-sb.de>; from Alexander Leidinger on Mon, Aug 24, 1998 at 05:12:27PM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4583 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Alexander Leidinger: > No, but most of the time I have the > "Sh*t! No freebsd-current@... in the to-field." > effect. Use a decent mailer not an overgrown and bloated www reader. Mailers like Muttallow you to specify which lists you're on and send the reply on to that address, just like I did. Lists with Reply-To: are evil. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #62: Mon Jul 27 20:47:08 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 17:33:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03559 for freebsd-current-outgoing; Mon, 24 Aug 1998 17:33:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03554 for ; Mon, 24 Aug 1998 17:33:07 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id KAA02971; Tue, 25 Aug 1998 10:32:12 +1000 Date: Tue, 25 Aug 1998 10:32:12 +1000 From: Bruce Evans Message-Id: <199808250032.KAA02971@godzilla.zeta.org.au> To: current@FreeBSD.ORG, wosch@panke.de.freebsd.org Subject: Re: file segment sizes of a core dump Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I added an option to size(1) which print the >file segment sizes of a core dump. >... >If nobody objects I will commit the change. The a.out size utility is the wrong place to put this in an ELF world. How does binutils do this? Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 19:43:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18788 for freebsd-current-outgoing; Mon, 24 Aug 1998 19:43:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18762 for ; Mon, 24 Aug 1998 19:43:51 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id MAA05278; Tue, 25 Aug 1998 12:12:53 +0930 (CST) Message-Id: <199808250242.MAA05278@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: ghiugan@lucent.com cc: "freebsd-current@FreeBSD.ORG" Subject: Re: Multihomed hosts question In-reply-to: Your message of "Mon, 24 Aug 1998 14:25:03 -0400." <35E1AFFF.4950EC6A@lucent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Aug 1998 12:12:53 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It is possible to use more than one netdevice (i.e. network card) on the > *same* machine and to have same IP address for both of them ? (I know it soun > stupid but I don't see any reason why not). Well.. I can :) I would have thought this would be called channel bonding, not multihoming (which is where the same machine has multiple IP's) > If the answer is 'YES' then how can you "enforce" the kernel to use a > specific netcard for when 'taking' to certain addresses (i.e. how can you ro > some addresses via a specific netcard)? Well, I don't know if you can channel bond, but you can route by interface instead of IP. Try 'route add default -interface tun0' --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 21:48:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29786 for freebsd-current-outgoing; Mon, 24 Aug 1998 21:48:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29776 for ; Mon, 24 Aug 1998 21:48:23 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id XAA14345; Mon, 24 Aug 1998 23:45:33 -0400 (EDT) Date: Mon, 24 Aug 1998 23:45:31 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Kent A Vander Velden cc: freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-Reply-To: <199808242253.RAA27685@isua4.iastate.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Aug 1998, Kent A Vander Velden wrote: > > Hi. Does -current support spliting the threads of a single process > across multiple processors? Current still has user threads, which are pretty much unaware of which processor there on. There's been work towards kernel threads, but it's not yet to the point that you can play with it. > > Thanks. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 22:44:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04371 for freebsd-current-outgoing; Mon, 24 Aug 1998 22:44:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d7.dialup.hilink.com.au [203.2.144.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04366 for ; Mon, 24 Aug 1998 22:44:13 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA02879; Mon, 24 Aug 1998 22:41:27 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808242241.WAA02879@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: Kent A Vander Velden , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-reply-to: Your message of "Mon, 24 Aug 1998 23:45:31 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Aug 1998 22:41:26 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Mon, 24 Aug 1998, Kent A Vander Velden wrote: > > > > > Hi. Does -current support spliting the threads of a single process > > across multiple processors? > > Current still has user threads, which are pretty much unaware of which > processor there on. There's been work towards kernel threads, but it's > not yet to the point that you can play with it. This level of thread support requires that *all* thread mutexes be handled by the kernel (atomicity guarantee). It's several major steps beyond where we are now, and not something that's necessarily a good idea. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 22:56:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05383 for freebsd-current-outgoing; Mon, 24 Aug 1998 22:56:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05377 for ; Mon, 24 Aug 1998 22:56:35 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id AAA14469; Tue, 25 Aug 1998 00:52:52 -0400 (EDT) Date: Tue, 25 Aug 1998 00:52:52 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Mike Smith cc: Kent A Vander Velden , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-Reply-To: <199808242241.WAA02879@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Aug 1998, Mike Smith wrote: > > > > On Mon, 24 Aug 1998, Kent A Vander Velden wrote: > > > > > > > > Hi. Does -current support spliting the threads of a single process > > > across multiple processors? > > > > Current still has user threads, which are pretty much unaware of which > > processor there on. There's been work towards kernel threads, but it's > > not yet to the point that you can play with it. > > This level of thread support requires that *all* thread mutexes be > handled by the kernel (atomicity guarantee). It's several major steps > beyond where we are now, and not something that's necessarily a good > idea. Yeah, I agree. I've written some threaded code for classes, and it worked just fine. You get some definite speed improvements for threaded code (if it's kernel threads and you have multiple processors) but honestly, I don't think that there's all that much code out there that makes use of it (it's a bear to write). Even the stuff that's out there, much of it is GUI type stuff, you don't get all the improvement unless you're really seeing batch type stuff, do you? For the most part, for the batch type stuff, I'm still willing to do the multiple process route, client-server stuff. You do see benefit from that, the complexity is lower, and you don't tear your hair out dealing with locking. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 23:15:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07301 for freebsd-current-outgoing; Mon, 24 Aug 1998 23:15:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-75.ppp.wenet.net [206.15.84.75]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07295 for ; Mon, 24 Aug 1998 23:15:21 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id XAA18064; Mon, 24 Aug 1998 23:15:51 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 24 Aug 1998 23:15:51 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: "Kenneth D. Merry" cc: freebsd-current@FreeBSD.ORG Subject: Re: pciconf In-Reply-To: <199808240227.UAA05491@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Aug 1998, Kenneth D. Merry wrote: [...] > The problem is that the PCIOCGETCONF ioctl isn't supported in > -current. There's nothing wrong with your machine. I've modified the PCI > code in the CAM tree to support that ioctl again. So 'pciconf -l' now > produces output like: [..] > The new version of that ioctl also supports matching against bus, > device, function, device name and unit number. Will this perhaps be merged into the -current tree before the rest of CAM? I know I'd like to try the CAM stuff out for other reasons, but I don't quite feel like dealing with huge patches (or a whole 'nother source tree). - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 24 23:28:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08532 for freebsd-current-outgoing; Mon, 24 Aug 1998 23:28:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08527 for ; Mon, 24 Aug 1998 23:28:18 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id PAA06938; Tue, 25 Aug 1998 15:57:16 +0930 (CST) Message-Id: <199808250627.PAA06938@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Alex cc: "Kenneth D. Merry" , freebsd-current@FreeBSD.ORG Subject: Re: pciconf In-reply-to: Your message of "Mon, 24 Aug 1998 23:15:51 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Aug 1998 15:57:16 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > device, function, device name and unit number. > Will this perhaps be merged into the -current tree before the rest of CAM? > I know I'd like to try the CAM stuff out for other reasons, but I don't > quite feel like dealing with huge patches (or a whole 'nother source > tree). Well.. The CAM patches worked for -stable fine for me (I had to hand patch about 3 things) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 00:23:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12824 for freebsd-current-outgoing; Tue, 25 Aug 1998 00:23:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12817 for ; Tue, 25 Aug 1998 00:23:41 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id CAA04575 for current@freebsd.org; Tue, 25 Aug 1998 02:22:48 -0500 (EST) (envelope-from toor) Message-Id: <199808250722.CAA04575@dyson.iquest.net> Subject: Serious bug in vm_page.h in current To: current@FreeBSD.ORG Date: Tue, 25 Aug 1998 02:22:47 -0500 (EST) From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM904029767-4563-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM904029767-4563-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit PAGE_BUSY is used to set the busy flag, and not the busy bitmask. Attachment contains patch. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. --ELM904029767-4563-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=tmp1 Content-Description: /tmp/tmp1 Content-Transfer-Encoding: 7bit Index: vm_page.h =================================================================== RCS file: /local/home/ncvs/src/sys/vm/vm_page.h,v retrieving revision 1.44 diff -C2 -r1.44 vm_page.h *** vm_page.h 1998/08/24 08:39:38 1.44 --- vm_page.h 1998/08/25 07:20:55 *************** *** 299,303 **** } ! #define PAGE_BUSY(m) atomic_add_char(&(m)->busy, 1) #define PAGE_BWAKEUP(m) { \ --- 299,303 ---- } ! #define PAGE_BUSY(m) PAGE_SET_FLAG(m, PG_BUSY) #define PAGE_BWAKEUP(m) { \ --ELM904029767-4563-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 00:49:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15806 for freebsd-current-outgoing; Tue, 25 Aug 1998 00:49:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15795 for ; Tue, 25 Aug 1998 00:49:46 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id IAA23104; Tue, 25 Aug 1998 08:48:36 +0100 (BST) Date: Tue, 25 Aug 1998 08:48:34 +0100 (BST) From: Doug Rabson To: Bruce Evans cc: current@FreeBSD.ORG, wosch@panke.de.freebsd.org Subject: Re: file segment sizes of a core dump In-Reply-To: <199808250032.KAA02971@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, Bruce Evans wrote: > >I added an option to size(1) which print the > >file segment sizes of a core dump. > >... > >If nobody objects I will commit the change. > > The a.out size utility is the wrong place to put this in an ELF world. > How does binutils do this? I think objdump would be the right place for this if we used that for a.out but we don't :-(. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 00:54:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16609 for freebsd-current-outgoing; Tue, 25 Aug 1998 00:54:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16592 for ; Tue, 25 Aug 1998 00:54:16 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id DAA03690; Tue, 25 Aug 1998 03:53:18 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Chuck Robey cc: freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Threads across processors In-reply-to: Your message of "Tue, 25 Aug 1998 00:52:52 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Aug 1998 03:53:18 -0400 Message-ID: <3686.904031598@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote in message ID : > Yeah, I agree. I've written some threaded code for classes, and it > worked just fine. You get some definite speed improvements for threaded > code (if it's kernel threads and you have multiple processors) but > honestly, I don't think that there's all that much code out there that > makes use of it (it's a bear to write). >From an ISP standpoint: Cyclone, Typhoon and Breeze (from Hywind Software) are all threaded. Why? Because it allows them to be a really fast system. Intermail (and probably post.office) from software.com are threaded too (Intermail even uses threaded tcl). This allows them to do some really neat tricks with respect to mail processing. Various LDAP and Radius implimentations are threaded too. Why? Because it allows the system to block on something (e.g. looking up a username in a remote realm) but still process local requests while waiting for an answer. Threading may be work, but it makes a lot of time-critical stuff (where blocking would be bad) easier. Theres a bunch of other stuff out there that *should* be threaded, but unfortunately our threads support, while complete, seems to be a bit slow at times, so I don't think there are as many threaded apps as for (say) Solaris, which is basically totally threaded (even tho the rest of solaris sucks) > For the most part, for the batch type stuff, I'm still willing to do the > multiple process route, client-server stuff. You do see benefit from that, > the complexity is lower, and you don't tear your hair out dealing with > locking. The message passing overhead between processes is much higher than message passing between threads in the same process. I believe Cyclones time-to-transit for an article is on the order of milliseconds. By the time you dump the data on a pipe, incur the context switch, etc, you've lost the advantage. Heck, SMI wrote `doors' for the very reason that IPC *blows* in all cases, and that to pull off the speedups with NSCD that they wanted, they had to get the IPC overhead reduced a lot. I think I even have slides somewhere comparing pipes, SYSV SHM, etc times for message passing in terms of transit time. So, I think you are missing a lot of real-time applications too. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 00:55:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16776 for freebsd-current-outgoing; Tue, 25 Aug 1998 00:55:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16770 for ; Tue, 25 Aug 1998 00:55:33 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id CAA00249 for current@freebsd.org; Tue, 25 Aug 1998 02:34:25 -0500 (EST) (envelope-from toor) Message-Id: <199808250734.CAA00249@dyson.iquest.net> Subject: Follow-up on the busy page problem To: current@FreeBSD.ORG Date: Tue, 25 Aug 1998 02:34:25 -0500 (EST) From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It appears that the usage of PG_BUSY and m->busy is distorted. m->busy is used for the buffer cache code to show that I/O is active on a page. PG_BUSY blocks all other concurrent activity, while m->busy allows other concurrent activity. PAGE_BUSY would be used to set the PG_BUSY bit, while one would incr m->busy when doing concurrent (or sequential) I/Os. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 00:59:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17484 for freebsd-current-outgoing; Tue, 25 Aug 1998 00:59:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17476 for ; Tue, 25 Aug 1998 00:59:41 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id IAA23153; Tue, 25 Aug 1998 08:58:42 +0100 (BST) Date: Tue, 25 Aug 1998 08:58:42 +0100 (BST) From: Doug Rabson To: "John S. Dyson" cc: current@FreeBSD.ORG Subject: Re: Serious bug in vm_page.h in current In-Reply-To: <199808250722.CAA04575@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, John S. Dyson wrote: > > PAGE_BUSY is used to set the busy flag, and not the busy > bitmask. Attachment contains patch. I thought of setting the busy flag when I put PAGE_BUSY in but none of the places where I changed m->busy++ to PAGE_BUSY(m) set the flag. I'll fix it anyway, thanks.. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 01:02:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA17987 for freebsd-current-outgoing; Tue, 25 Aug 1998 01:02:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA17982 for ; Tue, 25 Aug 1998 01:02:32 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA23178; Tue, 25 Aug 1998 09:01:43 +0100 (BST) Date: Tue, 25 Aug 1998 09:01:43 +0100 (BST) From: Doug Rabson To: "John S. Dyson" cc: current@FreeBSD.ORG Subject: Re: Serious bug in vm_page.h in current In-Reply-To: <199808250722.CAA04575@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, John S. Dyson wrote: > > PAGE_BUSY is used to set the busy flag, and not the busy > bitmask. Attachment contains patch. Hang on. I just checked the patch and it doesn't increment m->busy. The original call before I put in the atomic arithmetic macros was 'm->busy++'. After your patch it would change to 'm->flags |= PG_BUSY' which is very different. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 01:29:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA20817 for freebsd-current-outgoing; Tue, 25 Aug 1998 01:29:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20812 for ; Tue, 25 Aug 1998 01:29:52 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hindarfjell.ifi.uio.no (2602@hindarfjell.ifi.uio.no [129.240.64.130]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id KAA15575; Tue, 25 Aug 1998 10:29:04 +0200 (MET DST) Received: (from dag-erli@localhost) by hindarfjell.ifi.uio.no ; Tue, 25 Aug 1998 10:29:03 +0200 (MET DST) Mime-Version: 1.0 To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: SCSI cd driver and SLICE References: <199808242237.IAA25725@godzilla.zeta.org.au> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 25 Aug 1998 10:29:03 +0200 In-Reply-To: Bruce Evans's message of "Tue, 25 Aug 1998 08:37:31 +1000" Message-ID: Lines: 19 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id BAA20813 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > > Mounting cd9660 CDs seems to work fine. > Strange. It thought I tested it, but now always hangs on vn_loc (sic). It Worked The Last Time I Tried (tm) which was a couple of weeks ago, before I noticed the audio CD problems (I bought a couple of CDs last week and wanted to dump them) > Workaround 1: never use cd0a or cd0c. They are just compatibility cruft > (aliases for cd0). dsopen() only calls devfs_remove_dev() on cd0a and > cd0c, so there are no problems if they are possibly-but-not-actually > open. So on SLICE systems I should force tosha to use /dev/cd0 instead of the default /dev/cd0c? DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 01:41:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22510 for freebsd-current-outgoing; Tue, 25 Aug 1998 01:41:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22505 for ; Tue, 25 Aug 1998 01:41:02 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id DAA00444; Tue, 25 Aug 1998 03:40:08 -0500 (EST) (envelope-from toor) Message-Id: <199808250840.DAA00444@dyson.iquest.net> Subject: Re: Serious bug in vm_page.h in current In-Reply-To: from Doug Rabson at "Aug 25, 98 09:01:43 am" To: dfr@nlsystems.com (Doug Rabson) Date: Tue, 25 Aug 1998 03:40:02 -0500 (EST) Cc: dyson@iquest.net, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson said: > On Tue, 25 Aug 1998, John S. Dyson wrote: > > > > > PAGE_BUSY is used to set the busy flag, and not the busy > > bitmask. Attachment contains patch. > > Hang on. I just checked the patch and it doesn't increment m->busy. The > original call before I put in the atomic arithmetic macros was > 'm->busy++'. After your patch it would change to 'm->flags |= PG_BUSY' > which is very different. > I agree that it is different, but PAGE_BUSY was originally m->flags |= PG_BUSY. I have been trying to merge in my VM updates, and the change in definition had caused some confusion. (And this along with some other changes is why my published patches don't work on -current.) It is correct as-is, considering how it is being used. Sorry. (Note my misuse of 'busy bitmask', and not 'busy count' -- that was incorrect.) I believe that there are some problems (windows) with wakeups on both m->busy and PG_BUSY. IMO, it is probably wisest to wakeup on decrementing m->busy to zero, or clearing PG_BUSY, whenever PG_WANTED is set. So, PAGE_BWAKEUP would decr busy, and wakeup if PG_WANTED and busy == 0. PAGE_WAKEUP would clear PG_BUSY, and wakeup if PG_WANTED. Each of the above would ignore the other condition. There will be extra wakeups, but those won't significantly affect performance. It is possible for one to wait on one or both conditions, so waking up on either is the right way. I was in error when I forced a wakeup criteria of *both* conditions. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 01:43:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22976 for freebsd-current-outgoing; Tue, 25 Aug 1998 01:43:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22964 for ; Tue, 25 Aug 1998 01:43:48 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id DAA00455; Tue, 25 Aug 1998 03:41:17 -0500 (EST) (envelope-from toor) Message-Id: <199808250841.DAA00455@dyson.iquest.net> Subject: Re: Serious bug in vm_page.h in current In-Reply-To: from Doug Rabson at "Aug 25, 98 08:58:42 am" To: dfr@nlsystems.com (Doug Rabson) Date: Tue, 25 Aug 1998 03:41:17 -0500 (EST) Cc: dyson@iquest.net, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson said: > On Tue, 25 Aug 1998, John S. Dyson wrote: > > > > > PAGE_BUSY is used to set the busy flag, and not the busy > > bitmask. Attachment contains patch. > > I thought of setting the busy flag when I put PAGE_BUSY in but none of the > places where I changed m->busy++ to PAGE_BUSY(m) set the flag. I'll fix > it anyway, thanks.. > After more careful (and less confused review), your code is correct. The change in definition isn't that big a deal (only a little confusing when I was trying to merge some older code in -- and being in a hurry :-)). -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 01:43:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23002 for freebsd-current-outgoing; Tue, 25 Aug 1998 01:43:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22957; Tue, 25 Aug 1998 01:43:42 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id BAA18949; Tue, 25 Aug 1998 01:42:52 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd018932; Tue Aug 25 01:42:48 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id BAA09842; Tue, 25 Aug 1998 01:42:46 -0700 (MST) From: Terry Lambert Message-Id: <199808250842.BAA09842@usr05.primenet.com> Subject: Re: Threads across processors To: gpalmer@FreeBSD.ORG (Gary Palmer) Date: Tue, 25 Aug 1998 08:42:46 +0000 (GMT) Cc: chuckr@glue.umd.edu, freebsd-current@FreeBSD.ORG In-Reply-To: <3686.904031598@gjp.erols.com> from "Gary Palmer" at Aug 25, 98 03:53:18 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From an ISP standpoint: > > Cyclone, Typhoon and Breeze (from Hywind Software) are all threaded. Why? > Because it allows them to be a really fast system. > > Intermail (and probably post.office) from software.com are threaded too > (Intermail even uses threaded tcl). This allows them to do some really neat > tricks with respect to mail processing. > > Various LDAP and Radius implimentations are threaded too. Sounds to me like you want an async call gate, not kernel threads. Kernel threads would (probably) result in a context switch overhead on a blocking call, whereas an async call gate would result in another thread in the same process getting the remainder of the quantum for that process. The context returned by an async call gate could be on a seperate processor; it doesn't matter to the call gate. > passing between threads in the same process. I believe Cyclones > time-to-transit for an article is on the order of milliseconds. By the time > you dump the data on a pipe, incur the context switch, etc, you've lost the > advantage. > > Heck, SMI wrote `doors' for the very reason that IPC *blows* in all cases, > and that to pull off the speedups with NSCD that they wanted, they had to > get the IPC overhead reduced a lot. I think I even have slides somewhere > comparing pipes, SYSV SHM, etc times for message passing in terms of > transit time. Anything requiring a process context switch overhead, like, oh, say, getting in line behind other processes in the scheduler, takes an incredible amount of overhead. So does proxying objects between address spaces, which is what you have to do if you allocate objects in thread local storage. > So, I think you are missing a lot of real-time applications too. RT, hard RT, requires kernel preeemption and priority lending and deterministic maximal interrupt processing latency, and a lot of other things which are topologically equivalent to kernel threading and SMP kernel reentrancy. The big value in kernel threads is SMP scalability, in that multiple processors can be active in different threads in the same program simultaneously. This benefit is hardly worth it in most cases unless there is also support for CPU affinity and cooperative user space scheduling to avoid context switch overhead between instances of threads in the same process. This generally only works when you hand off to another thread in the same process the remaining quantum using -- an async call gate. Otherwise you get to lose L2 and L1 cache contents, which really damages your throughput on any real machine, no matter what it does for your microbenchmarks on an unloaded machine. There is a very nice book on these topics: Scheduling and Load Balancing in Parallel and Distributed Systems Behrooz A. Shirazi, Ali R. Hurson, Krishna M. Kavi IEEE Computer Society Press IEEE Catalog number EH0417-6 ISBN: 0-8186-6587-4 This should be available from your local "Computer Literacy" bookstore. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 01:58:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25262 for freebsd-current-outgoing; Tue, 25 Aug 1998 01:58:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25249 for ; Tue, 25 Aug 1998 01:58:40 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id QAA11737 for ; Tue, 25 Aug 1998 16:56:40 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id PAA29567; Tue, 25 Aug 1998 15:53:48 +0800 Message-Id: <199808250753.PAA29567@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Floating Point Exceptions, signal handlers & subsequent ops Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Aug 1998 15:53:48 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've noticed in one of my applications that the first FP operation after return from a caught SIGFPE is invalid. I have a signal handler installed that just prints out some basic info (like "SIGFPE caught"). The first FP op after this (in my case, converting a long to a double) just gives garbage. Repeat the same statement and it gives a sensible result. Has anyone else seen this before I file a PR with code to reproduce the problem? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 02:12:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26682 for freebsd-current-outgoing; Tue, 25 Aug 1998 02:12:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26672 for ; Tue, 25 Aug 1998 02:12:26 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA28244; Tue, 25 Aug 1998 10:11:36 +0100 (BST) Date: Tue, 25 Aug 1998 10:11:36 +0100 (BST) From: Doug Rabson To: "John S. Dyson" cc: current@FreeBSD.ORG Subject: Re: Serious bug in vm_page.h in current In-Reply-To: <199808250840.DAA00444@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, John S. Dyson wrote: > Doug Rabson said: > > On Tue, 25 Aug 1998, John S. Dyson wrote: > > > > > > > > PAGE_BUSY is used to set the busy flag, and not the busy > > > bitmask. Attachment contains patch. > > > > Hang on. I just checked the patch and it doesn't increment m->busy. The > > original call before I put in the atomic arithmetic macros was > > 'm->busy++'. After your patch it would change to 'm->flags |= PG_BUSY' > > which is very different. > > > I agree that it is different, but PAGE_BUSY was originally > m->flags |= PG_BUSY. I have been trying to merge in my VM updates, > and the change in definition had caused some confusion. (And this > along with some other changes is why my published patches don't > work on -current.) I understand now after reading an old version of your VM patch. I added the macro PAGE_BUSY to encapsulate manipulations of m->busy and you added PAGE_BUSY to set the PG_BUSY bit. I think we need two macros :-). I don't mind changing the m->busy++ one; what do you think is the right name? > > It is correct as-is, considering how it is being used. Sorry. > (Note my misuse of 'busy bitmask', and not 'busy count' -- that > was incorrect.) > > I believe that there are some problems (windows) with wakeups > on both m->busy and PG_BUSY. IMO, it is probably wisest to > wakeup on decrementing m->busy to zero, or clearing PG_BUSY, > whenever PG_WANTED is set. > > So, > PAGE_BWAKEUP would decr busy, and wakeup if PG_WANTED > and busy == 0. > > PAGE_WAKEUP would clear PG_BUSY, and wakeup if PG_WANTED. > > Each of the above would ignore the other condition. There will > be extra wakeups, but those won't significantly affect performance. > It is possible for one to wait on one or both conditions, so > waking up on either is the right way. I was in error when I > forced a wakeup criteria of *both* conditions. I don't understand this part of the code of the code very well. It doesn't seem to me that a few extra wakeups is a problem. Not waking up at all is a problem... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 02:13:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26818 for freebsd-current-outgoing; Tue, 25 Aug 1998 02:13:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26736; Tue, 25 Aug 1998 02:13:02 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Tue, 25 Aug 1998 10:12:01 +0100 Message-ID: From: Paul Richards To: "'Gary Palmer'" , Chuck Robey Cc: freebsd-current@FreeBSD.ORG Subject: RE: Threads across processors Date: Tue, 25 Aug 1998 10:11:54 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hotmail are apparently dropping FreeBSD in favour of Solaris because of thread support as well :-( Paul Richards Ph.D. Originative Solutions Ltd > -----Original Message----- > From: Gary Palmer [mailto:gpalmer@FreeBSD.ORG] > Sent: Tuesday, August 25, 1998 8:53 AM > To: Chuck Robey > Cc: freebsd-current@FreeBSD.ORG > Subject: Re: Threads across processors > > > Chuck Robey wrote in message ID > : > > Yeah, I agree. I've written some threaded code for classes, and it > > worked just fine. You get some definite speed improvements > for threaded > > code (if it's kernel threads and you have multiple processors) but > > honestly, I don't think that there's all that much code out > there that > > makes use of it (it's a bear to write). > > From an ISP standpoint: > > Cyclone, Typhoon and Breeze (from Hywind Software) are all > threaded. Why? > Because it allows them to be a really fast system. > > Intermail (and probably post.office) from software.com are > threaded too > (Intermail even uses threaded tcl). This allows them to do > some really neat > tricks with respect to mail processing. > > Various LDAP and Radius implimentations are threaded too. > > Why? Because it allows the system to block on something (e.g. > looking up a > username in a remote realm) but still process local requests > while waiting for > an answer. Threading may be work, but it makes a lot of > time-critical stuff > (where blocking would be bad) easier. > > Theres a bunch of other stuff out there that *should* be > threaded, but > unfortunately our threads support, while complete, seems to > be a bit slow at > times, so I don't think there are as many threaded apps as > for (say) Solaris, > which is basically totally threaded (even tho the rest of > solaris sucks) > > > For the most part, for the batch type stuff, I'm still > willing to do the > > multiple process route, client-server stuff. You do see > benefit from that, > > the complexity is lower, and you don't tear your hair out > dealing with > > locking. > > The message passing overhead between processes is much higher > than message > passing between threads in the same process. I believe Cyclones > time-to-transit for an article is on the order of > milliseconds. By the time > you dump the data on a pipe, incur the context switch, etc, > you've lost the > advantage. > > Heck, SMI wrote `doors' for the very reason that IPC *blows* > in all cases, and > that to pull off the speedups with NSCD that they wanted, > they had to get the > IPC overhead reduced a lot. I think I even have slides > somewhere comparing > pipes, SYSV SHM, etc times for message passing in terms of > transit time. > > So, I think you are missing a lot of real-time applications too. > > Gary > -- > Gary Palmer FreeBSD > Core Team Member > FreeBSD: Turning PC's into workstations. See > http://www.FreeBSD.ORG/ for info > > > > To Unsubscribe: send mail > to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 02:14:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26921 for freebsd-current-outgoing; Tue, 25 Aug 1998 02:14:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26915 for ; Tue, 25 Aug 1998 02:14:30 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA28248; Tue, 25 Aug 1998 10:13:40 +0100 (BST) Date: Tue, 25 Aug 1998 10:13:40 +0100 (BST) From: Doug Rabson To: "John S. Dyson" cc: current@FreeBSD.ORG Subject: Re: Serious bug in vm_page.h in current In-Reply-To: <199808250841.DAA00455@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, John S. Dyson wrote: > Doug Rabson said: > > On Tue, 25 Aug 1998, John S. Dyson wrote: > > > > > > > > PAGE_BUSY is used to set the busy flag, and not the busy > > > bitmask. Attachment contains patch. > > > > I thought of setting the busy flag when I put PAGE_BUSY in but none of the > > places where I changed m->busy++ to PAGE_BUSY(m) set the flag. I'll fix > > it anyway, thanks.. > > > After more careful (and less confused review), your code is correct. The > change in definition isn't that big a deal (only a little confusing when > I was trying to merge some older code in -- and being in a hurry :-)). Likewise, I just read your old patch and understand the confusion. You could set the PG_BUSY flag with PAGE_SET_FLAG(m, PG_BUSY) which uses the new atomic access macros and will be safer on the alpha. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 02:42:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01284 for freebsd-current-outgoing; Tue, 25 Aug 1998 02:42:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01278 for ; Tue, 25 Aug 1998 02:42:08 -0700 (PDT) (envelope-from wosch@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id LAA03475; Tue, 25 Aug 1998 11:40:36 +0200 (CEST) (envelope-from wosch@panke.de.freebsd.org) Received: (from wosch@localhost) by campa.panke.de (8.8.8/8.8.8) id TAA04144; Mon, 24 Aug 1998 19:37:29 +0200 (MET DST) (envelope-from wosch) Message-ID: <19980824193728.B4111@panke.de> Date: Mon, 24 Aug 1998 19:37:28 +0200 From: Wolfram Schneider To: Matthew Thyer , Wolfram Schneider Cc: current@FreeBSD.ORG Subject: Re: file segment sizes of a core dump References: <199808231906.VAA04727@campa.panke.de> <35E18FF5.B7FADA7B@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <35E18FF5.B7FADA7B@camtech.net.au>; from Matthew Thyer on Tue, Aug 25, 1998 at 01:38:21AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-08-25 01:38:21 +0930, Matthew Thyer wrote: > Why require an option ? > > Why not make size do what you want automatically when it detects > that you are running it on a core file ? How do you know that the file is a FreeBSD core file and not garbage? file(1) has a gross hack to identify core files, see /usr/share/misc/magic. > Wolfram Schneider wrote: > > I added an option to size(1) which print the > > file segment sizes of a core dump. -- Wolfram Schneider http://www.freebsd.org/~w/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 03:04:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA03199 for freebsd-current-outgoing; Tue, 25 Aug 1998 03:04:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA03193; Tue, 25 Aug 1998 03:04:37 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id MAA01661; Tue, 25 Aug 1998 12:08:27 +0200 (CEST) (envelope-from regnauld@deepo.prosa.dk) Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id MAA11953; Tue, 25 Aug 1998 12:12:20 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id MAA10343; Tue, 25 Aug 1998 12:01:47 +0200 (CEST) Message-ID: <19980825120146.02787@deepo.prosa.dk> Date: Tue, 25 Aug 1998 12:01:46 +0200 From: Philippe Regnauld To: Paul Richards Cc: "'Gary Palmer'" , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from Paul Richards on Tue, Aug 25, 1998 at 10:11:54AM +0100 X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Paul Richards writes: > Hotmail are apparently dropping FreeBSD in favour of Solaris because of > thread support as well :-( Hotmail is Micro$loth now. If they'd had half a brain, they'd do like Yahoo and sponsor development of the ugly work... -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 03:49:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09138 for freebsd-current-outgoing; Tue, 25 Aug 1998 03:49:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA09133 for ; Tue, 25 Aug 1998 03:49:56 -0700 (PDT) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id HQRPBETK; Tue, 25 Aug 98 10:49:03 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19980825124557.00901880@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 25 Aug 1998 12:45:57 +0200 To: Philippe Regnauld From: Marius Bendiksen Subject: Re: Threads across processors Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <19980825120146.02787@deepo.prosa.dk> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hotmail is Micro$loth now. If they'd had half a brain, they'd > do like Yahoo and sponsor development of the ugly work... Just because it's M$ doesn't mean we should give up on it, quite the opposite, in fact. We need to reclaim some territory. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 05:11:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19317 for freebsd-current-outgoing; Tue, 25 Aug 1998 05:11:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ren.dtir.qld.gov.au (ns.dtir.qld.gov.au [203.108.138.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19307 for ; Tue, 25 Aug 1998 05:11:08 -0700 (PDT) (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id WAA12678; Tue, 25 Aug 1998 22:10:23 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma012675; Tue, 25 Aug 98 22:10:08 +1000 Received: from atlas.dtir.qld.gov.au (atlas.dtir.qld.gov.au [167.123.8.9]) by ogre.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id WAA07290; Tue, 25 Aug 1998 22:10:08 +1000 (EST) Received: from nymph.dtir.qld.gov.au (nymph.dtir.qld.gov.au [167.123.10.10]) by atlas.dtir.qld.gov.au (8.8.5/8.8.5) with ESMTP id WAA18848; Tue, 25 Aug 1998 22:10:07 +1000 (EST) Received: from nymph.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1]) by nymph.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id WAA12649; Tue, 25 Aug 1998 22:10:05 +1000 (EST) (envelope-from syssgm@nymph.dtir.qld.gov.au) Message-Id: <199808251210.WAA12649@nymph.dtir.qld.gov.au> To: Doug Rabson cc: "John S. Dyson" , freebsd-current@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: Serious bug in vm_page.h in current References: In-Reply-To: from Doug Rabson at "Tue, 25 Aug 1998 10:11:36 +0100" Date: Tue, 25 Aug 1998 22:10:05 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 25th August 1998, Doug Rabson wrote: >I understand now after reading an old version of your VM patch. I added >the macro PAGE_BUSY to encapsulate manipulations of m->busy and you added >PAGE_BUSY to set the PG_BUSY bit. I think we need two macros :-). I don't >mind changing the m->busy++ one; what do you think is the right name? Purely on naming now, the new inline vm_object_set_flag() and friends are well named. The PAGE_BUSY and PAGE_WAKEUP macros, etc, should be similarly named inline functions. For example, vm_page_busy_add() and vm_page_wakeup(). Best of all, of course, would be to have different names for these two types of busy-ness (busy the count vs PG_BUSY the flag). John tells us that m->busy is an "active IO count". It should be named thus. Then PG_BUSY will no longer be confused with it. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 06:21:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA25978 for freebsd-current-outgoing; Tue, 25 Aug 1998 06:21:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA25971 for ; Tue, 25 Aug 1998 06:21:16 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id JAA23287; Tue, 25 Aug 1998 09:20:29 -0400 (EDT) (envelope-from luoqi) Date: Tue, 25 Aug 1998 09:20:29 -0400 (EDT) From: Luoqi Chen Message-Id: <199808251320.JAA23287@lor.watermarkgroup.com> To: current@FreeBSD.ORG, shocking@prth.pgs.com Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I've noticed in one of my applications that the first FP operation after > return from a caught SIGFPE is invalid. I have a signal handler installed that > just prints out some basic info (like "SIGFPE caught"). The first FP op after > this (in my case, converting a long to a double) just gives garbage. Repeat > the same statement and it gives a sensible result. Has anyone else seen this > before I file a PR with code to reproduce the problem? > > > Stephen > -- > The views expressed above are not those of PGS Tensor. > > "We've heard that a million monkeys at a million keyboards could produce > the Complete Works of Shakespeare; now, thanks to the Internet, we know > this is not true." Robert Wilensky, University of California > > Your SIGFPE handler has to restore the FP register stack top, and this is no easy job to do, you have to handle each exception type differently. It's not FreeBSD's problem, rather a stupid design on intel's part. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 06:39:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28416 for freebsd-current-outgoing; Tue, 25 Aug 1998 06:39:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28305; Tue, 25 Aug 1998 06:38:43 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Tue, 25 Aug 1998 14:20:41 +0100 Message-ID: From: Paul Richards To: "'Philippe Regnauld'" , Paul Richards Cc: "'Gary Palmer'" , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: RE: Threads across processors Date: Tue, 25 Aug 1998 14:20:31 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Philippe Regnauld [mailto:regnauld@deepo.prosa.dk] > Sent: Tuesday, August 25, 1998 11:02 AM > To: Paul Richards > Cc: 'Gary Palmer'; Chuck Robey; freebsd-current@FreeBSD.ORG > Subject: Re: Threads across processors > > > Paul Richards writes: > > Hotmail are apparently dropping FreeBSD in favour of > Solaris because of > > thread support as well :-( > > Hotmail is Micro$loth now. If they'd had half a brain, they'd > do like Yahoo and sponsor development of the ugly work... > Maybe someone should suggest it to them. It must be costing a fair bit to switch to Solaris. They must have some independence from Microsoft to be able to go for Solaris, although it is due to the fact that NT fell on it's face when faced with the task :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 07:11:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02277 for freebsd-current-outgoing; Tue, 25 Aug 1998 07:11:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02265; Tue, 25 Aug 1998 07:11:00 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA01928; Tue, 25 Aug 1998 10:10:12 -0400 (EDT) (envelope-from wollman) Date: Tue, 25 Aug 1998 10:10:12 -0400 (EDT) From: Garrett Wollman Message-Id: <199808251410.KAA01928@khavrinen.lcs.mit.edu> To: "Gary Palmer" Cc: Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-Reply-To: <3686.904031598@gjp.erols.com> References: <3686.904031598@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Theres a bunch of other stuff out there that *should* be threaded, but > unfortunately our threads support, while complete, seems to be a bit slow at > times It's a bit slow because of all the work necessary to ensure mutual exclusion in those parts of the thread-kernel which ought to be doable in the kernel-kernel. I've watched Cyclone hit 150,000 syscalls a SECOND when it's not doing much of anything. It's impressive that it can do that, but I'd like to have some CPU left over for useful work... Most of those system calls were to sigprocmask() to protect some critical section from the signals that drive the thred scheduler. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 07:28:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04462 for freebsd-current-outgoing; Tue, 25 Aug 1998 07:28:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04457 for ; Tue, 25 Aug 1998 07:28:33 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id KAA08892; Tue, 25 Aug 1998 10:25:05 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Paul Richards cc: "'Philippe Regnauld'" , Chuck Robey , freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Threads across processors In-reply-to: Your message of "Tue, 25 Aug 1998 14:20:31 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Aug 1998 10:25:05 -0400 Message-ID: <8887.904055105@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Paul Richards wrote in message ID : > > -----Original Message----- > > From: Philippe Regnauld [mailto:regnauld@deepo.prosa.dk] > > Sent: Tuesday, August 25, 1998 11:02 AM > > To: Paul Richards > > Cc: 'Gary Palmer'; Chuck Robey; freebsd-current@FreeBSD.ORG > > Subject: Re: Threads across processors > > > > > > Paul Richards writes: > > > Hotmail are apparently dropping FreeBSD in favour of > > Solaris because of > > > thread support as well :-( > > > > Hotmail is Micro$loth now. If they'd had half a brain, they'd > > do like Yahoo and sponsor development of the ugly work... > > > > Maybe someone should suggest it to them. It must be costing a fair bit > to switch to Solaris. They must have some independence from Microsoft to > be able to go for Solaris, although it is due to the fact that NT fell > on it's face when faced with the task :-) I'll be brutally honest at this point. There are probably two reasons to go with UltraSPARCs and Solaris. 1) Solaris is heavily threaded, and some of the designs in the kernel are actually pretty neat. 2) The PC hardware platform *BLOWS*. Looking at work at the sort of hardware we can deploy with a UE250 or UE450 makes every PC I've ever seen pale in comparison. This is not counting the E4000 series machines we have which, when combined with Solaris, are pretty nice. e.g. in 2.7, you can hot remove and insert any board in a E4000, including processor and I/O boards. And if we have any problems, our support contract will get us a spare part, and an engineer to install it for us, within 2 hours. Now, I still hate solaris. But its pretty difficult to persuade someone to stay with a PC platform which he has to support himself/herself, when (now) the company I work for has the money to let them go out and buy UltraSPARC equipment and push all that responsibility onto SMI. So I think that it is important that effort be dedicated to the UltraSPARC port and also the Alpha port (which I am helping with when I can). Or perhaps some other comodity hardware that is not as braindamaged as the PC. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 07:39:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06190 for freebsd-current-outgoing; Tue, 25 Aug 1998 07:39:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06163 for ; Tue, 25 Aug 1998 07:39:11 -0700 (PDT) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id QAA09189; Tue, 25 Aug 1998 16:38:13 +0200 (MET DST) Message-ID: <19980825163812.A9088@cons.org> Date: Tue, 25 Aug 1998 16:38:12 +0200 From: Martin Cracauer To: Stephen Hocking-Senior Programmer PGS Tensor Perth , current@FreeBSD.ORG Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops References: <199808250753.PAA29567@ariadne.tensor.pgs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808250753.PAA29567@ariadne.tensor.pgs.com>; from Stephen Hocking-Senior Programmer PGS Tensor Perth on Tue, Aug 25, 1998 at 03:53:48PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199808250753.PAA29567@ariadne.tensor.pgs.com>, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > I've noticed in one of my applications that the first FP operation after > return from a caught SIGFPE is invalid. I have a signal handler installed that > just prints out some basic info (like "SIGFPE caught"). The first FP op after > this (in my case, converting a long to a double) just gives garbage. Repeat > the same statement and it gives a sensible result. Has anyone else seen this > before I file a PR with code to reproduce the problem? Are you sure your signal handler doesn't do anything it shouldn't? For example, printf causes manipulation of FP flags and these affect the operation that may be in progress in your main code path. ANSI C just allows manipulation of 'volatile sig_atomic_t' variables. Posix adds many systems calls (amoung them read/write), but most C library stuff isn't suported. Please post a working example or at least your signal handler. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 07:43:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07061 for freebsd-current-outgoing; Tue, 25 Aug 1998 07:43:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07046 for ; Tue, 25 Aug 1998 07:43:18 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA02038; Tue, 25 Aug 1998 10:41:07 -0400 (EDT) (envelope-from wollman) Date: Tue, 25 Aug 1998 10:41:07 -0400 (EDT) From: Garrett Wollman Message-Id: <199808251441.KAA02038@khavrinen.lcs.mit.edu> To: Doug Rabson Cc: "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Serious bug in vm_page.h in current In-Reply-To: References: <199808250840.DAA00444@dyson.iquest.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > On Tue, 25 Aug 1998, John S. Dyson wrote: >> PAGE_BWAKEUP would decr busy, and wakeup if PG_WANTED >> and busy == 0. >> >> PAGE_WAKEUP would clear PG_BUSY, and wakeup if PG_WANTED. >> >> Each of the above would ignore the other condition. There will >> be extra wakeups, but those won't significantly affect performance. > I don't understand this part of the code of the code very well. It > doesn't seem to me that a few extra wakeups is a problem. Not waking up > at all is a problem... This sounds very much like it could be related to the lockup Matt Dillon and I have been seeing. I just rebooted newsswitch with this change in it; I should know by the end of the day whether it had any effect. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 07:56:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08559 for freebsd-current-outgoing; Tue, 25 Aug 1998 07:56:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08554 for ; Tue, 25 Aug 1998 07:56:49 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id OAA19451; Tue, 25 Aug 1998 14:54:33 GMT Date: Tue, 25 Aug 1998 23:54:33 +0900 (JST) From: Michael Hancock To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: locking in -current. donate 15 minutes. In-Reply-To: <35E1BB8A.237C228A@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Aug 1998, Julian Elischer wrote: > "when exactly is the right time to use the "interlock" locks in vnode > locking an dwhat do they do? > An interlock is a very short term lock while a full vnode lock is a relatively long term lock that is usually acquired during a lookup and held until the operation is complete. An interlock is used for things like incrementing refcounts and in acquiring a vnode lock. Note the interlock is acquired and released when acquiring a vnode lock. When an interlock is already held the LK_INTERLOCK flag indicates that acquiring the interlock isn't necessary and to just release it when done. In general you don't want to hold vnode locks very long either, but along with Kirk's softupdate changes I noticed that he holds vnode locks over operations where he didn't hold them before. Which leads me to think that these particular operations no longer block under softupdates. It also seems to mean that it is ok to hold it over hundreds of lines of code that operate on in-core data structures as long as they don't block. Anyway, being able to hold the lock over these operations makes it easier because you don't have to enter a race to reacquire the vnode lock. Reference counts can be held much longer so in some situations it is advantageous to separate a vput() into an VOP_UNLOCK() and delay the dereference until the end of the entire operation. Regards, Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 08:08:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09887 for freebsd-current-outgoing; Tue, 25 Aug 1998 08:08:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09880 for ; Tue, 25 Aug 1998 08:08:25 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id IAA22717 for freebsd-current@freebsd.org; Tue, 25 Aug 1998 08:06:56 -0700 (PDT) (envelope-from dhw) Date: Tue, 25 Aug 1998 08:06:56 -0700 (PDT) From: David Wolfskill Message-Id: <199808251506.IAA22717@pau-amma.whistle.com> To: freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-Reply-To: <8887.904055105@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: "Gary Palmer" >Date: Tue, 25 Aug 1998 10:25:05 -0400 >I'll be brutally honest at this point. >There are probably two reasons to go with UltraSPARCs and Solaris. >1) Solaris is heavily threaded, and some of the designs in the kernel are > actually pretty neat. >2) The PC hardware platform *BLOWS*.... 3) Platform consolidation is an administrative win. david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 08:11:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10669 for freebsd-current-outgoing; Tue, 25 Aug 1998 08:11:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10505; Tue, 25 Aug 1998 08:10:47 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id PAA19521; Tue, 25 Aug 1998 15:08:50 GMT Date: Wed, 26 Aug 1998 00:08:50 +0900 (JST) From: Michael Hancock To: Gary Palmer cc: Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-Reply-To: <3686.904031598@gjp.erols.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, Gary Palmer wrote: > Heck, SMI wrote `doors' for the very reason that IPC *blows* in all cases, and > that to pull off the speedups with NSCD that they wanted, they had to get the > IPC overhead reduced a lot. I think I even have slides somewhere comparing > pipes, SYSV SHM, etc times for message passing in terms of transit time. Our pipes are very fast. SYSV SHM's blunder is that it uses full blown system calls for synchronization. > So, I think you are missing a lot of real-time applications too. Yes, the realtime guys will always be biased toward 1-to-1 over anything else not because of performance but because of more predictable scheduling. Regards, Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 09:07:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18327 for freebsd-current-outgoing; Tue, 25 Aug 1998 09:07:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18322 for ; Tue, 25 Aug 1998 09:06:57 -0700 (PDT) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id SAA10040; Tue, 25 Aug 1998 18:06:00 +0200 (MET DST) Message-ID: <19980825180559.A9890@cons.org> Date: Tue, 25 Aug 1998 18:05:59 +0200 From: Martin Cracauer To: Stephen Hocking-Senior Programmer PGS Tensor Perth , current@FreeBSD.ORG Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops References: <199808250753.PAA29567@ariadne.tensor.pgs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808250753.PAA29567@ariadne.tensor.pgs.com>; from Stephen Hocking-Senior Programmer PGS Tensor Perth on Tue, Aug 25, 1998 at 03:53:48PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199808250753.PAA29567@ariadne.tensor.pgs.com>, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > I've noticed in one of my applications that the first FP operation after > return from a caught SIGFPE is invalid. I have a signal handler installed that > just prints out some basic info (like "SIGFPE caught"). The first FP op after > this (in my case, converting a long to a double) just gives garbage. Repeat > the same statement and it gives a sensible result. Has anyone else seen this > before I file a PR with code to reproduce the problem? I just did a short test and for me the next FP operation after a caught SIGFPE (division by zero) is still sane (without setjump/jumpjump). Please post a code example if you still have problems. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 10:25:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29321 for freebsd-current-outgoing; Tue, 25 Aug 1998 10:25:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29309 for ; Tue, 25 Aug 1998 10:24:58 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id TAA22385 for ; Tue, 25 Aug 1998 19:28:44 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 25 Aug 1998 19:28:44 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: Panic with DEVFS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, It was pointed to me that it's very easy to panic -current system running DEVFS on /dev, with / on MFS. The problem manifested itself with picobsd floppy. The following scenario causes panic with "mfs_strategy: bad dev": 1. boot with -c 2. disable at least one device 3. log in 4. cd /dev 5. ls -l What's funny is that when I do 'ls' (without -l) in step 5., everything is ok. My guess is that DEVFS doesn't like these devices which are present in kernel, but are disabled... Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 10:41:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01831 for freebsd-current-outgoing; Tue, 25 Aug 1998 10:41:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01792; Tue, 25 Aug 1998 10:41:28 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with SMTP id NAA04051; Tue, 25 Aug 1998 13:39:16 -0400 (EDT) Date: Tue, 25 Aug 1998 13:39:16 -0400 (EDT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: Gary Palmer cc: Paul Richards , "'Philippe Regnauld'" , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-Reply-To: <8887.904055105@gjp.erols.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The SPARC port's not dead? -Brian Feldman green@unixhelp.org On Tue, 25 Aug 1998, Gary Palmer wrote: > Paul Richards wrote in message ID > : > > > -----Original Message----- > > > From: Philippe Regnauld [mailto:regnauld@deepo.prosa.dk] > > > Sent: Tuesday, August 25, 1998 11:02 AM > > > To: Paul Richards > > > Cc: 'Gary Palmer'; Chuck Robey; freebsd-current@FreeBSD.ORG > > > Subject: Re: Threads across processors > > > > > > > > > Paul Richards writes: > > > > Hotmail are apparently dropping FreeBSD in favour of > > > Solaris because of > > > > thread support as well :-( > > > > > > Hotmail is Micro$loth now. If they'd had half a brain, they'd > > > do like Yahoo and sponsor development of the ugly work... > > > > > > > Maybe someone should suggest it to them. It must be costing a fair bit > > to switch to Solaris. They must have some independence from Microsoft to > > be able to go for Solaris, although it is due to the fact that NT fell > > on it's face when faced with the task :-) > > I'll be brutally honest at this point. > > There are probably two reasons to go with UltraSPARCs and Solaris. > > 1) Solaris is heavily threaded, and some of the designs in the kernel are > actually pretty neat. > > 2) The PC hardware platform *BLOWS*. Looking at work at the sort of hardware > we can deploy with a UE250 or UE450 makes every PC I've ever seen pale in > comparison. This is not counting the E4000 series machines we have which, > when combined with Solaris, are pretty nice. e.g. in 2.7, you can hot > remove and insert any board in a E4000, including processor and I/O boards. > And if we have any problems, our support contract will get us a spare part, > and an engineer to install it for us, within 2 hours. > > Now, I still hate solaris. But its pretty difficult to persuade someone to > stay with a PC platform which he has to support himself/herself, when (now) > the company I work for has the money to let them go out and buy UltraSPARC > equipment and push all that responsibility onto SMI. > > So I think that it is important that effort be dedicated to the UltraSPARC > port and also the Alpha port (which I am helping with when I can). Or perhaps > some other comodity hardware that is not as braindamaged as the PC. > > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 10:49:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03653 for freebsd-current-outgoing; Tue, 25 Aug 1998 10:49:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03611 for ; Tue, 25 Aug 1998 10:48:56 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id LAA15408; Tue, 25 Aug 1998 11:48:01 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199808251748.LAA15408@panzer.plutotech.com> Subject: Re: pciconf In-Reply-To: from Alex at "Aug 24, 98 11:15:51 pm" To: garbanzo@hooked.net (Alex) Date: Tue, 25 Aug 1998 11:48:01 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex wrote... > On Sun, 23 Aug 1998, Kenneth D. Merry wrote: > [...] > > The problem is that the PCIOCGETCONF ioctl isn't supported in > > -current. There's nothing wrong with your machine. I've modified the PCI > > code in the CAM tree to support that ioctl again. So 'pciconf -l' now > > produces output like: > [..] > > The new version of that ioctl also supports matching against bus, > > device, function, device name and unit number. > > Will this perhaps be merged into the -current tree before the rest of CAM? > I know I'd like to try the CAM stuff out for other reasons, but I don't > quite feel like dealing with huge patches (or a whole 'nother source > tree). If someone wants to do it, that's fine with me. It'll take a couple of things first, though: - clear it with Stefan, since he's the PCI dude - realize that there are a couple of limitations to it Last week I finished work on some CAM transport layer matching code that has a number of similarities to the pciconf code I wrote. (it's similar, but it's far more complex than the pci stuff) Anyway, I realized that the way I did the match/result buffer in the PCI code isn't exactly the best way to do things. In the CAM matching code, I've got two separate buffers, one for patterns to match against, the other for match results. In the PCI code, there's only one buffer that's passed in. The user passes in a matching pattern, and gets back the result in the same buffer. It would be better to have two separate buffers so if the buffer the user passed in isn't big enough for the results, the user won't have to copy the pattern back in to the buffer before sending it again. One other thing that might be nice to have in the code is the ability to match against vendor and device id's. (Justin asked for this a few weeks ago, but I haven't had time/inclination to do it yet.) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 11:09:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06511 for freebsd-current-outgoing; Tue, 25 Aug 1998 11:09:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06505 for ; Tue, 25 Aug 1998 11:09:50 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id TAA02256; Tue, 25 Aug 1998 19:08:18 +0100 (BST) Date: Tue, 25 Aug 1998 19:08:18 +0100 (BST) From: Doug Rabson To: Garrett Wollman cc: "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Serious bug in vm_page.h in current In-Reply-To: <199808251441.KAA02038@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, Garrett Wollman wrote: > < said: > > > On Tue, 25 Aug 1998, John S. Dyson wrote: > > >> PAGE_BWAKEUP would decr busy, and wakeup if PG_WANTED > >> and busy == 0. > >> > >> PAGE_WAKEUP would clear PG_BUSY, and wakeup if PG_WANTED. > >> > >> Each of the above would ignore the other condition. There will > >> be extra wakeups, but those won't significantly affect performance. > > > I don't understand this part of the code of the code very well. It > > doesn't seem to me that a few extra wakeups is a problem. Not waking up > > at all is a problem... > > This sounds very much like it could be related to the lockup Matt > Dillon and I have been seeing. I just rebooted newsswitch with this > change in it; I should know by the end of the day whether it had > any effect. I think that John's patch as posted will not work at all due to a misunderstanding. It will probably just cause hangs since vm_page::busy will be decremented but never incremented. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 11:11:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06723 for freebsd-current-outgoing; Tue, 25 Aug 1998 11:11:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06707 for ; Tue, 25 Aug 1998 11:10:53 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id OAA02595; Tue, 25 Aug 1998 14:10:02 -0400 (EDT) (envelope-from wollman) Date: Tue, 25 Aug 1998 14:10:02 -0400 (EDT) From: Garrett Wollman Message-Id: <199808251810.OAA02595@khavrinen.lcs.mit.edu> To: Doug Rabson Cc: Garrett Wollman , "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Serious bug in vm_page.h in current In-Reply-To: References: <199808251441.KAA02038@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> >> PAGE_BWAKEUP would decr busy, and wakeup if PG_WANTED >> >> and busy == 0. >> >> >> >> PAGE_WAKEUP would clear PG_BUSY, and wakeup if PG_WANTED. >> >> >> >> Each of the above would ignore the other condition. There will >> >> be extra wakeups, but those won't significantly affect performance. > I think that John's patch as posted will not work at all due to a > misunderstanding. It will probably just cause hangs since vm_page::busy > will be decremented but never incremented. Not John's patch, John's description of the correct operation (quoted). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 11:11:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06846 for freebsd-current-outgoing; Tue, 25 Aug 1998 11:11:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06830 for ; Tue, 25 Aug 1998 11:11:42 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id TAA02288; Tue, 25 Aug 1998 19:10:48 +0100 (BST) Date: Tue, 25 Aug 1998 19:10:48 +0100 (BST) From: Doug Rabson To: Stephen McKay cc: "John S. Dyson" , freebsd-current@FreeBSD.ORG Subject: Re: Serious bug in vm_page.h in current In-Reply-To: <199808251210.WAA12649@nymph.dtir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, Stephen McKay wrote: > On Tuesday, 25th August 1998, Doug Rabson wrote: > > >I understand now after reading an old version of your VM patch. I added > >the macro PAGE_BUSY to encapsulate manipulations of m->busy and you added > >PAGE_BUSY to set the PG_BUSY bit. I think we need two macros :-). I don't > >mind changing the m->busy++ one; what do you think is the right name? > > Purely on naming now, the new inline vm_object_set_flag() and friends are > well named. The PAGE_BUSY and PAGE_WAKEUP macros, etc, should be similarly > named inline functions. For example, vm_page_busy_add() and vm_page_wakeup(). > > Best of all, of course, would be to have different names for these two > types of busy-ness (busy the count vs PG_BUSY the flag). John tells us > that m->busy is an "active IO count". It should be named thus. Then > PG_BUSY will no longer be confused with it. I chose the PAGE_XXX type names since they seemed to follow the existing macros in vm_page.h. I am perfectly happy to change them to inline functions with a similar naming convention to the ones in vm_object as long as all of the other PAGE_XXX macros change at the same time. The i/o count should certainly have a less confusing name. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 11:21:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08229 for freebsd-current-outgoing; Tue, 25 Aug 1998 11:21:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08219 for ; Tue, 25 Aug 1998 11:21:49 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id TAA02328; Tue, 25 Aug 1998 19:20:55 +0100 (BST) Date: Tue, 25 Aug 1998 19:20:55 +0100 (BST) From: Doug Rabson To: Garrett Wollman cc: "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Serious bug in vm_page.h in current In-Reply-To: <199808251810.OAA02595@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, Garrett Wollman wrote: > < said: > > >> >> PAGE_BWAKEUP would decr busy, and wakeup if PG_WANTED > >> >> and busy == 0. > >> >> > >> >> PAGE_WAKEUP would clear PG_BUSY, and wakeup if PG_WANTED. > >> >> > >> >> Each of the above would ignore the other condition. There will > >> >> be extra wakeups, but those won't significantly affect performance. > > > I think that John's patch as posted will not work at all due to a > > misunderstanding. It will probably just cause hangs since vm_page::busy > > will be decremented but never incremented. > > Not John's patch, John's description of the correct operation > (quoted). > Ah, I understand. Did it help with your problem? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 11:36:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11131 for freebsd-current-outgoing; Tue, 25 Aug 1998 11:36:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.eecis.udel.edu (louie.udel.edu [128.175.7.39]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA11123; Tue, 25 Aug 1998 11:36:43 -0700 (PDT) (envelope-from alexandr@mail.eecis.udel.edu) Date: Tue, 25 Aug 1998 11:36:43 -0700 (PDT) From: alexandr@mail.eecis.udel.edu Message-Id: <199808251836.LAA11123@hub.freebsd.org> Received: from ren.eecis.udel.edu by mail.eecis.udel.edu id aa29058; 25 Aug 1998 14:33 EDT To: Gary Palmer Cc: Paul Richards , "'Philippe Regnauld'" , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: RE: Threads across processors Organization: Mos Eisley Candy Store Reply-To: alexandr@mail.eecis.udel.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Reply to Your Message of Tue, 25 Aug 1998 10: 25:05 EDT Date: Tue, 25 Aug 1998 14:33:46 -0400 From: Jerry Alexandratos Message-ID: <199808251433.aa29058@mail.eecis.udel.edu> Gary Palmer says: : : So I think that it is important that effort be dedicated to the UltraSPARC : port and also the Alpha port (which I am helping with when I can). Or perhaps : some other comodity hardware that is not as braindamaged as the PC. So does this mean that we'll start working on PPC machines to edge out AIX, or how about StrongARMs so that we can get a foothold in the NC market? --Jerry 8) Jerry Alexandratos % - % "Nothing inhabits my (8 8) alexandr@louie.udel.edu % - % thoughts, and oblivion (8 8) darkstar@strauss.udel.edu % - % drives my desires." (8 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 11:49:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13083 for freebsd-current-outgoing; Tue, 25 Aug 1998 11:49:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server1.scudc.scu.edu (server1.scudc.scu.edu [129.210.16.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13075 for ; Tue, 25 Aug 1998 11:49:39 -0700 (PDT) (envelope-from dgleeson@scudc.scu.edu) Received: from tuatara.whistle.com (s205m228.whistle.com [207.76.205.228]) by server1.scudc.scu.edu with SMTP (8.7.6/8.7.1) id LAA17726 for ; Tue, 25 Aug 1998 11:48:51 -0700 (PDT) Message-ID: <000601bdd058$a9a7fc60$e4cd4ccf@tuatara.whistle.com> From: "David Gleeson, Santa Clara University" To: Subject: subscribe Date: Tue, 25 Aug 1998 11:45:36 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 12:15:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16614 for freebsd-current-outgoing; Tue, 25 Aug 1998 12:15:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from merlin.camalott.com (merlin.camalott.com [208.229.74.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16609 for ; Tue, 25 Aug 1998 12:15:53 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-85.camalott.com [208.229.74.85]) by merlin.camalott.com (8.8.7/8.8.7) with ESMTP id OAA19287; Tue, 25 Aug 1998 14:15:53 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id OAA00899; Tue, 25 Aug 1998 14:14:36 -0500 (CDT) (envelope-from joelh) Date: Tue, 25 Aug 1998 14:14:36 -0500 (CDT) Message-Id: <199808251914.OAA00899@detlev.UUCP> To: netchild@wurzelausix.cs.uni-sb.de CC: dhw@whistle.com, freebsd-current@FreeBSD.ORG In-reply-to: <35E182DB.12FE8E68@wurzelausix.cs.uni-sb.de> (message from Alexander Leidinger on Mon, 24 Aug 1998 17:12:27 +0200) Subject: Re: Majordomo and reply-to (was: [Fwd: sysinstall bug]) From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808241505.IAA17984@pau-amma.whistle.com> <35E182DB.12FE8E68@wurzelausix.cs.uni-sb.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Is there a problem you're trying to solve? > No, but most of the time I have the > "Sh*t! No freebsd-current@... in the to-field." > effect. Find another MUA, or find out how to reconfigure yours. Your MUA should have a reply function that CC's everybody in the To: and Cc: fields of the original. Alternatively, you may be able to use procmail (or even sendmail!) to make the change locally. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 12:18:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17462 for freebsd-current-outgoing; Tue, 25 Aug 1998 12:18:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17442 for ; Tue, 25 Aug 1998 12:18:26 -0700 (PDT) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.8.8/8.8.7) with SMTP id OAA28408; Tue, 25 Aug 1998 14:17:32 -0500 (CDT) Message-Id: <199808251917.OAA28408@ns.tar.com> From: "Richard Seaman, Jr." To: "Garrett Wollman" Cc: "freebsd-current@FreeBSD.ORG" Date: Tue, 25 Aug 98 14:17:31 -0500 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Threads across processors Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998 10:10:12 -0400 (EDT), Garrett Wollman wrote: >I've watched Cyclone hit 150,000 syscalls a SECOND when it's not doing >much of anything. It's impressive that it can do that, but I'd like >to have some CPU left over for useful work... Most of those system >calls were to sigprocmask() to protect some critical section from the >signals that drive the thred scheduler. I was under the impression that signal handling in threads was changed last April to eliminate the sigprocmask calls in the scheduler? >From uthread_kern.c,v: "1.10 log @Change signal model to match POSIX (i.e. one set of signal handlers for the process, not a separate set for each thread). By default, the process now only has signal handlers installed for SIGVTALRM, SIGINFO and SIGCHLD. The thread kernel signal handler is installed for other signals on demand. This means that SIG_IGN and SIG_DFL processing is now left to the kernel, not the thread kernel. Change the signal dispatch to no longer use a signal thread, and call the signal handler using the stack of the thread that has the signal pending. Change the atomic lock method to use test-and-set asm code with a yield if blocked. This introduces separate locks for each type of object instead of blocking signals to prevent a context switch. It was this blocking of signals that caused the performance degradation the people have noted. This is a *big* change!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 12:20:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18072 for freebsd-current-outgoing; Tue, 25 Aug 1998 12:20:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18067 for ; Tue, 25 Aug 1998 12:20:44 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-85.camalott.com [208.229.74.85]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id OAA02391; Tue, 25 Aug 1998 14:20:31 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id OAA00942; Tue, 25 Aug 1998 14:18:30 -0500 (CDT) (envelope-from joelh) Date: Tue, 25 Aug 1998 14:18:30 -0500 (CDT) Message-Id: <199808251918.OAA00942@detlev.UUCP> To: Harlan.Stenn@pfcs.com CC: Harlan.Stenn@pfcs.com, garbanzo@hooked.net, mike@smith.net.au, entropy@compufit.at, wwoods@cybcon.com, freebsd-current@FreeBSD.ORG In-reply-to: <28885.903983089@brown.pfcs.com> (message from Harlan Stenn on Mon, 24 Aug 1998 14:24:49 -0400) Subject: Re: gcc 2.8 From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <28885.903983089@brown.pfcs.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just did another test of performance using TenDRA, comparing it to > FreeBSD's "cc". What was your test methodology? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 12:24:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19100 for freebsd-current-outgoing; Tue, 25 Aug 1998 12:24:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19089 for ; Tue, 25 Aug 1998 12:24:53 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA12243; Tue, 25 Aug 1998 11:57:25 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdN12241; Tue Aug 25 18:57:22 1998 Date: Tue, 25 Aug 1998 11:57:20 -0700 (PDT) From: Julian Elischer To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: Panic with DEVFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG is it possible to find out which device it is? disabled devices should not show up in devfs as they should not be probed and the probe routine should be responsible for adding the devfs entries.. (actually the attach routine but...) except for devices that do not probe, (e.g. /dev/mem) which do it in their init routine. On Tue, 25 Aug 1998, Andrzej Bialecki wrote: > Hi, > > It was pointed to me that it's very easy to panic -current system running > DEVFS on /dev, with / on MFS. > > The problem manifested itself with picobsd floppy. The following scenario > causes panic with "mfs_strategy: bad dev": > > 1. boot with -c > 2. disable at least one device > 3. log in > 4. cd /dev > 5. ls -l > > What's funny is that when I do 'ls' (without -l) in step 5., everything is > ok. > > My guess is that DEVFS doesn't like these devices which are present in > kernel, but are disabled... > > Andrzej Bialecki > > +---------------------+------------------------+--------------------------+ > | | When in problem or in | if(halt_per_mth > 0) { | > | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | > | Network in Poland | scream and shout. | } | > + --------------------+------------------------+--------------------------+ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 12:26:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19733 for freebsd-current-outgoing; Tue, 25 Aug 1998 12:26:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19703 for ; Tue, 25 Aug 1998 12:26:17 -0700 (PDT) (envelope-from stb@hanse.de) Received: from daemon.Hanse.DE (daemon.Hanse.DE [193.174.9.17]) by rrz.Hanse.DE (8.8.8/8.8.8) with ESMTP id UAA26647 for ; Tue, 25 Aug 1998 20:32:59 +0200 (CEST) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id VAA22232 for ; Tue, 25 Aug 1998 21:26:25 +0200 (CEST) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id VAA27410 for ; Tue, 25 Aug 1998 21:25:13 +0200 (CEST) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Tue, 25 Aug 1998 21:25:12 +0200 (CEST) From: Stefan Bethke To: freebsd-current@FreeBSD.ORG Subject: Semantics of MGET(m, M_WAIT, *)? [was: Huge Bug not fixed?] In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Aug 1998, Stefan Bethke wrote: > > Looking at kern/uipc_socket.c:sosend(), one can easily spot the problem > > > Because sosend() expects a MGET(m, M_WAIT, MT_DATA) to always succeed, it > > pagefaults while trying to manipulate the non-allocated mbuf > > (m->m_pkthdr.len at 0+0x18). > > > The solution would be either to make MGET() and MGETHRD() to always succeed > > (or sleep indefinitly), or check the result of any of those calls (as many > > callers already do). What are the expected semantics of MGET(m, M_WAIT, *)? I would suggest that by specifing M_WAIT, the caller wants to sleep until a mbuf becomes available, as it is already the case if the vm map must be extended. Alternatively, all callers must check whether they actually obtained a mbuf; for so_send(), this is definitly beyond my grasp. While the problem in so_send() seems to strike only under rare circumstances, I fell we should fix the problem nonetheless (instead of putting panic()s into m_retry). Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 12:32:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20669 for freebsd-current-outgoing; Tue, 25 Aug 1998 12:32:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20664 for ; Tue, 25 Aug 1998 12:32:38 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-85.camalott.com [208.229.74.85]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id OAA03189; Tue, 25 Aug 1998 14:33:20 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id OAA00986; Tue, 25 Aug 1998 14:31:30 -0500 (CDT) (envelope-from joelh) Date: Tue, 25 Aug 1998 14:31:30 -0500 (CDT) Message-Id: <199808251931.OAA00986@detlev.UUCP> To: wosch@panke.de.freebsd.org CC: thyerm@camtech.net.au, wosch@panke.de.freebsd.org, current@FreeBSD.ORG In-reply-to: <19980824193728.B4111@panke.de> (message from Wolfram Schneider on Mon, 24 Aug 1998 19:37:28 +0200) Subject: Re: file segment sizes of a core dump From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808231906.VAA04727@campa.panke.de> <35E18FF5.B7FADA7B@camtech.net.au> <19980824193728.B4111@panke.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Why require an option ? >> Why not make size do what you want automatically when it detects >> that you are running it on a core file ? > How do you know that the file is a FreeBSD core file and not garbage? > file(1) has a gross hack to identify core files, see /usr/share/misc/magic. Why would you run size on garbage? Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 12:56:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23481 for freebsd-current-outgoing; Tue, 25 Aug 1998 12:56:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcpsj.pfcs.com (harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23395 for ; Tue, 25 Aug 1998 12:55:31 -0700 (PDT) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Tue, 25 Aug 1998 15:53:07 -0400 (EDT) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Tue, 25 Aug 1998 12:53:03 -0700 (PDT) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Tue, 25 Aug 1998 15:53:02 -0400 (EDT) X-Mailer: exmh version 2.0.2 2/24/98 To: joelh@gnu.org cc: Harlan.Stenn@pfcs.com, garbanzo@hooked.net, mike@smith.net.au, entropy@compufit.at, wwoods@cybcon.com, freebsd-current@FreeBSD.ORG Subject: Re: gcc 2.8 In-Reply-To: Joel Ray Holveck's (joelh@gnu.org) message dated Tue, 25 Aug 1998 14:18:30. <199808251918.OAA00942@detlev.UUCP> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Aug 1998 15:53:02 -0400 Message-ID: <870.904074782@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tested two packages. One compares a number (6-8) byte move subroutines (memcpy, bcopy, a variety of Duff's devices (using char, short, and int), and some other "fast" byte copies I've snarfed over the years). I run a reasonable quantity of different size/alignments against each of these, and report the CPU time of each one. The second test is much less (?) useful: I compiled my Mumps implementation with each compiler, and ran 11 coarse-grained tests (for loops, subroutine calls, (string) arithmetic (integer and real number), symbol table stuff, a variety of string operations (catenation, justification, formatting), pattern matching, database ops, and probably a couple of others. I run this test on a "quiet" system, as the test uses wall-clock timing (but each test runs for 30-60 seconds, on average). If I could get TenDRA to produce an executable that can be run under gprof, I'd do that instead. H --- > > I just did another test of performance using TenDRA, comparing it to > > FreeBSD's "cc". > > What was your test methodology? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 13:41:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00982 for freebsd-current-outgoing; Tue, 25 Aug 1998 13:41:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d2.dialup.hilink.com.au [203.2.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00964; Tue, 25 Aug 1998 13:40:55 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA02533; Tue, 25 Aug 1998 13:38:19 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808251338.NAA02533@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Michael Hancock cc: Gary Palmer , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-reply-to: Your message of "Wed, 26 Aug 1998 00:08:50 +0900." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Aug 1998 13:38:18 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 25 Aug 1998, Gary Palmer wrote: > > > Heck, SMI wrote `doors' for the very reason that IPC *blows* in all cases, and > > that to pull off the speedups with NSCD that they wanted, they had to get the > > IPC overhead reduced a lot. I think I even have slides somewhere comparing > > pipes, SYSV SHM, etc times for message passing in terms of transit time. > > Our pipes are very fast. SYSV SHM's blunder is that it uses full blown > system calls for synchronization. Yes. Anyone that thinks in terms of a context switch per transaction between coprocesses is not designing properly. Using a shared mmap() region and datastructures that don't require locking is another cost-effective technique. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 14:19:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07520 for freebsd-current-outgoing; Tue, 25 Aug 1998 14:19:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07512 for ; Tue, 25 Aug 1998 14:19:00 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id HAA00759; Wed, 26 Aug 1998 07:28:59 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808252128.HAA00759@cimlogic.com.au> Subject: Re: Threads across processors In-Reply-To: <199808251410.KAA01928@khavrinen.lcs.mit.edu> from Garrett Wollman at "Aug 25, 98 10:10:12 am" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Wed, 26 Aug 1998 07:28:59 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > I've watched Cyclone hit 150,000 syscalls a SECOND when it's not doing > much of anything. It's impressive that it can do that, but I'd like > to have some CPU left over for useful work... Most of those system > calls were to sigprocmask() to protect some critical section from the > signals that drive the thred scheduler. This comment applies to 2.2.X only, not to 3.0. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 14:24:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08644 for freebsd-current-outgoing; Tue, 25 Aug 1998 14:24:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08490; Tue, 25 Aug 1998 14:24:01 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id RAA03172; Tue, 25 Aug 1998 17:22:59 -0400 (EDT) (envelope-from wollman) Date: Tue, 25 Aug 1998 17:22:59 -0400 (EDT) From: Garrett Wollman Message-Id: <199808252122.RAA03172@khavrinen.lcs.mit.edu> To: Stefan Bethke Cc: freebsd-current@FreeBSD.ORG, net@FreeBSD.ORG Reply-To: net@FreeBSD.ORG Subject: Semantics of MGET(m, M_WAIT, *)? [was: Huge Bug not fixed?] In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Please watch followups!] < said: > What are the expected semantics of MGET(m, M_WAIT, *)? I would suggest > that by specifing M_WAIT, the caller wants to sleep until a mbuf becomes > available, as it is already the case if the vm map must be extended. It should sleep, but actually doing so while avoiding deadlocks is problematic. Since the mbuf allocator as currently formulated is going away, callers to mget should expect that the allocation might fail, but that M_WAIT makes it ``try harder'' as it were. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 14:42:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12653 for freebsd-current-outgoing; Tue, 25 Aug 1998 14:42:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12608; Tue, 25 Aug 1998 14:41:54 -0700 (PDT) (envelope-from stb@hanse.de) Received: from daemon.Hanse.DE (daemon.Hanse.DE [193.174.9.17]) by rrz.Hanse.DE (8.8.8/8.8.8) with ESMTP id WAA27816; Tue, 25 Aug 1998 22:48:45 +0200 (CEST) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id XAA00354; Tue, 25 Aug 1998 23:42:20 +0200 (CEST) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id XAA01723; Tue, 25 Aug 1998 23:41:08 +0200 (CEST) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Tue, 25 Aug 1998 23:41:07 +0200 (CEST) From: Stefan Bethke To: net@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Re: Semantics of MGET(m, M_WAIT, *)? [was: Huge Bug not fixed?] In-Reply-To: <199808252122.RAA03172@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, Garrett Wollman wrote: > [Please watch followups!] > > < > said: > > > What are the expected semantics of MGET(m, M_WAIT, *)? I would suggest > > that by specifing M_WAIT, the caller wants to sleep until a mbuf becomes > > available, as it is already the case if the vm map must be extended. > > It should sleep, but actually doing so while avoiding deadlocks is > problematic. Since the mbuf allocator as currently formulated is > going away, callers to mget should expect that the allocation might > fail, but that M_WAIT makes it ``try harder'' as it were. Which leaves the problem in so_send(). Anyone working on this already? I'd be relieved if I'd rather had not to grasp so_send() and all it's implications... however, if this is too low on others list, I'd might give it a try. Anything I should know about the "mbuf allocator going away" while trying to delve into that? I did a quick search in the archives, but did't really find anything. Thanks, Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 14:52:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14314 for freebsd-current-outgoing; Tue, 25 Aug 1998 14:52:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14304; Tue, 25 Aug 1998 14:52:39 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id OAA23329; Tue, 25 Aug 1998 14:24:37 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Brian Feldman cc: Gary Palmer , Paul Richards , "'Philippe Regnauld'" , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-reply-to: Your message of "Tue, 25 Aug 1998 13:39:16 EDT." Date: Tue, 25 Aug 1998 14:24:36 -0700 Message-ID: <23326.904080276@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The SPARC port's not dead? It's not exactly alive, either, unless you've been doing something yourself which we don't know about? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 15:56:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24680 for freebsd-current-outgoing; Tue, 25 Aug 1998 15:56:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24649 for ; Tue, 25 Aug 1998 15:56:48 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-150.camalott.com [208.229.74.150]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id RAA16451; Tue, 25 Aug 1998 17:56:12 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id RAA01679; Tue, 25 Aug 1998 17:54:26 -0500 (CDT) (envelope-from joelh) Date: Tue, 25 Aug 1998 17:54:26 -0500 (CDT) Message-Id: <199808252254.RAA01679@detlev.UUCP> To: Harlan.Stenn@pfcs.com CC: Harlan.Stenn@pfcs.com, garbanzo@hooked.net, mike@smith.net.au, entropy@compufit.at, wwoods@cybcon.com, freebsd-current@FreeBSD.ORG In-reply-to: <870.904074782@brown.pfcs.com> (message from Harlan Stenn on Tue, 25 Aug 1998 15:53:02 -0400) Subject: Re: gcc 2.8 From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <870.904074782@brown.pfcs.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I tested two packages. > One compares a number (6-8) byte move subroutines (memcpy, bcopy, a variety > of Duff's devices (using char, short, and int), and some other "fast" byte > copies I've snarfed over the years). Just to be sure: these are using their own recompiled bcopy etc, and not running the ones out of libc? > I run a reasonable quantity of different size/alignments against each of > these, and report the CPU time of each one. Could you please post this data? > If I could get TenDRA to produce an executable that can be run under > gprof, I'd do that instead. Has anybody investigated why -pg doesn't work for TenDRA? -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 16:52:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04369 for freebsd-current-outgoing; Tue, 25 Aug 1998 16:52:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04361 for ; Tue, 25 Aug 1998 16:52:51 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA32306; Wed, 26 Aug 1998 09:51:57 +1000 Date: Wed, 26 Aug 1998 09:51:57 +1000 From: Bruce Evans Message-Id: <199808252351.JAA32306@godzilla.zeta.org.au> To: current@FreeBSD.ORG, luoqi@watermarkgroup.com, shocking@prth.pgs.com Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I've noticed in one of my applications that the first FP operation after >> return from a caught SIGFPE is invalid. I have a signal handler installed that This is normal. Returning from a SIGFPE handler gives explicitly undefined behaviour in ANSI C. It gives various bad behaviours for FreeBSD on i386's: 1) if the SIGFPE was for integer division by zero, then the division will be restarted and the SIGFPE will be repeated endlessly. 2) if the SIGFPE was for an FP operation, then the FP operatation will be restarted. The kernel has cleared the trap-pending flag before delivering the SIGFPE to the application, and on i386's traps are delivered to the kernel on the the first non-control FP operation after the one that caused the exception, so it is certain that the restarted FP operation won't trap; it may cause an exception which will be delivered to the kernel on the next non-control FP operation. >> just prints out some basic info (like "SIGFPE caught"). The first FP op after >> this (in my case, converting a long to a double) just gives garbage. Repeat Long to double conversion actually takes 4 or 5 FP operations. long to double conversion will only trap on i386's for FP stack overflow. It's normal for botched signal handling to leave junk on the stack. E.g., faddp normally pops one operand, but if it causes an exception then it doesn't change the stack. >Your SIGFPE handler has to restore the FP register stack top, and this is >no easy job to do, you have to handle each exception type differently. It's >not FreeBSD's problem, rather a stupid design on intel's part. It has to do much more than that if it wants to return: 1) First decide if the exception is for FP or integer division by 0, by looking at the trap code. FreeBSD's support for trap codes is primitive and unportable (see ), but probably good enough to distinguish integer division by zero. 2) Handle the easy case of integer division by zero (if this can happen). Just modify the operands so that it doesn't happen, or advance the program counter and supply a result. 3) Handle all cases of FP exceptions that can happen, much like the integer division case except there are potentially thousands more cases. You basically need an FP emulator. Changing the stack top is not sufficient. You also need to supply a result for the exception operation and leave it at the approriate place on the stack. The FPU doesn't generate a default result for trapped exceptions, presumably because leaving it on the stack would usually clobber an operand, making it impossible for smart SIGFPE handlers (which no one writes :-) to do a complete fixup. The right way to handle this problem is to avoid it, either by not trapping FP exceptions (this causes different problems), or by longjmping out of the SIGFPE handler (set up the longjmp before each FP operation that may trap), or by checking operands to ensure that there are no traps. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 16:56:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04986 for freebsd-current-outgoing; Tue, 25 Aug 1998 16:56:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-22.ppp.wenet.net [206.15.84.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04978 for ; Tue, 25 Aug 1998 16:56:39 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id QAA04206 for ; Tue, 25 Aug 1998 16:57:26 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Tue, 25 Aug 1998 16:57:26 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: current Subject: GNU Binutils? (Was: re: gcc 2.8) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Speaking of upgrading the compiler, what are the chances of upgrading the binutils to 2.9.1 (at least for the ELF bits) in -current? I mention this, because as I was trying to compile koffice, I could reliably segfault as (2.8.1 from -current), which would in turn nicely knonk out egcs (and the rest of the build process). Using the version of gas that came with binutils 2.9.1 (configured for an i586-unknown-freebsdelf system) seems to have solved my problems. Also, the building of gas from the -current sources seems to ignore CFLAGS (and CXXFLAGS), but not CC/CXX. Should I open a pr for these and other minor stuff like this? - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 17:02:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05585 for freebsd-current-outgoing; Tue, 25 Aug 1998 17:02:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05580 for ; Tue, 25 Aug 1998 17:02:36 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id UAA03536; Tue, 25 Aug 1998 20:01:47 -0400 (EDT) (envelope-from wollman) Date: Tue, 25 Aug 1998 20:01:47 -0400 (EDT) From: Garrett Wollman Message-Id: <199808260001.UAA03536@khavrinen.lcs.mit.edu> To: Garrett Wollman Cc: Doug Rabson , "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Serious bug in vm_page.h in current In-Reply-To: <199808251441.KAA02038@khavrinen.lcs.mit.edu> References: <199808250840.DAA00444@dyson.iquest.net> <199808251441.KAA02038@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < This sounds very much like it could be related to the lockup Matt > Dillon and I have been seeing. I just rebooted newsswitch with this > change in it; I should know by the end of the day whether it had > any effect. newsswitch has been up for more than nine hours now, which is longer than it had been lasting. I'll give it a full day before proclaiming success, though. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 17:25:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08002 for freebsd-current-outgoing; Tue, 25 Aug 1998 17:25:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07972; Tue, 25 Aug 1998 17:25:49 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id UAA65454; Tue, 25 Aug 1998 20:25:13 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: References: <8887.904055105@gjp.erols.com> Date: Tue, 25 Aug 1998 20:29:11 -0400 To: Brian Feldman , Gary Palmer From: Garance A Drosihn Subject: Re: Threads across processors Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG on Tue, 25 Aug 1998, Gary Palmer wrote: >> So I think that it is important that effort be dedicated to the >> UltraSPARC port and also the Alpha port (which I am helping with >> when I can). Or perhaps some other comodity hardware that is not >> as braindamaged as the PC. At 1:39 PM -0400 8/25/98, Brian Feldman replied: > The SPARC port's not dead? Gary is just saying it would be good for "the freebsd project" to put resources into something like the ultraSPARC port. Sun itself has lost it's active interest in such a port, so in that sense it is dead, but there's always the opportunity for someone else to work on it if they so desired. If you have the resources to work on it, I doubt that either Sun or the FreeBSD project would complain about the goal... :-) --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 17:33:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09056 for freebsd-current-outgoing; Tue, 25 Aug 1998 17:33:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-22.ppp.wenet.net [206.15.84.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09045 for ; Tue, 25 Aug 1998 17:33:00 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id RAA07522 for ; Tue, 25 Aug 1998 17:33:47 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Tue, 25 Aug 1998 17:33:47 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: current Subject: MAXDOUBLE and values.h? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I've got a quick question. I've got an app which uses MAXDOUBLE, and includes values.h to get at it. values.h has a #warn that tells me it's depreciated. So I grep -R'd all the headers in /usr/include, and nothing else seemed to have a #define for MAXDOUBLE? Is this a mistake, or should MAXDOUBLE be avoided? - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 17:42:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10387 for freebsd-current-outgoing; Tue, 25 Aug 1998 17:42:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d3.dialup.hilink.com.au [203.2.144.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10322 for ; Tue, 25 Aug 1998 17:41:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA01034; Tue, 25 Aug 1998 17:39:23 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808251739.RAA01034@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alex cc: current Subject: Re: MAXDOUBLE and values.h? In-reply-to: Your message of "Tue, 25 Aug 1998 17:33:47 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Aug 1998 17:39:21 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok, I've got a quick question. I've got an app which uses MAXDOUBLE, and > includes values.h to get at it. values.h has a #warn that tells me it's > depreciated. So I grep -R'd all the headers in /usr/include, and nothing > else seemed to have a #define for MAXDOUBLE? Is this a mistake, or should > MAXDOUBLE be avoided? You should use , and MAXDOUBLE will come out of the machine-specific headers in -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 18:21:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15016 for freebsd-current-outgoing; Tue, 25 Aug 1998 18:21:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14997 for ; Tue, 25 Aug 1998 18:21:37 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id VAA03694; Tue, 25 Aug 1998 21:20:26 -0400 (EDT) (envelope-from wollman) Date: Tue, 25 Aug 1998 21:20:26 -0400 (EDT) From: Garrett Wollman Message-Id: <199808260120.VAA03694@khavrinen.lcs.mit.edu> To: Mike Smith Cc: Alex , current Subject: Re: MAXDOUBLE and values.h? In-Reply-To: <199808251739.RAA01034@dingo.cdrom.com> References: <199808251739.RAA01034@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > You should use , and MAXDOUBLE will come out of the > machine-specific headers in -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 18:29:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16514 for freebsd-current-outgoing; Tue, 25 Aug 1998 18:29:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16507 for ; Tue, 25 Aug 1998 18:29:13 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id JAA04892; Wed, 26 Aug 1998 09:27:08 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id JAA02700; Wed, 26 Aug 1998 09:27:48 +0800 Message-Id: <199808260127.JAA02700@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: current@FreeBSD.ORG Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops In-reply-to: Your message of "Wed, 26 Aug 1998 09:51:57 +1000." <199808252351.JAA32306@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Aug 1998 09:27:48 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Much scary stuff regarding traps and the like...] OK, I've had a look at machine/trap.h, how do I go about getting info on exactly was exception was caused? A brief perusal of the man pages for math and fpsetmask offers no clues (unless I've missed something totally obvious). All the program wishes to do is note the fact and excveption has occured, get some runtime stats (which is where that next FP operation happens) and exit. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 18:32:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16894 for freebsd-current-outgoing; Tue, 25 Aug 1998 18:32:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-12.ppp.wenet.net [206.15.85.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16888 for ; Tue, 25 Aug 1998 18:32:42 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id SAA13966; Tue, 25 Aug 1998 18:32:43 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Tue, 25 Aug 1998 18:32:43 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Garrett Wollman cc: Mike Smith , current Subject: Re: MAXDOUBLE and values.h? In-Reply-To: <199808260120.VAA03694@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, Garrett Wollman wrote: > < said: > > > You should use , and MAXDOUBLE will come out of the > > machine-specific headers in > > Ahh. Is DBL_MAX a portable thing? Like, can I assume it complies to some obscure ANSI, POSIX or Linux standard? Or should I use another FreeBSD ifdef? - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 18:37:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17770 for freebsd-current-outgoing; Tue, 25 Aug 1998 18:37:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17761 for ; Tue, 25 Aug 1998 18:37:56 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id UAA07438; Tue, 25 Aug 1998 20:35:12 -0400 (EDT) Date: Tue, 25 Aug 1998 20:35:11 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Alex cc: current Subject: Re: MAXDOUBLE and values.h? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, Alex wrote: > Ok, I've got a quick question. I've got an app which uses MAXDOUBLE, and > includes values.h to get at it. values.h has a #warn that tells me it's > depreciated. So I grep -R'd all the headers in /usr/include, and nothing > else seemed to have a #define for MAXDOUBLE? Is this a mistake, or should > MAXDOUBLE be avoided? #include MAXDOUBLE -> DBL_MAX > > - alex > > | "Contrary to popular belief, penguins are not the salvation of modern | > | technology. Neither do they throw parties for the urban proletariat." | > | Powered by FreeBSD http://www.freebsd.org/ | > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 18:41:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18551 for freebsd-current-outgoing; Tue, 25 Aug 1998 18:41:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18546 for ; Tue, 25 Aug 1998 18:41:53 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id UAA00967; Tue, 25 Aug 1998 20:40:55 -0500 (EST) (envelope-from toor) Message-Id: <199808260140.UAA00967@dyson.iquest.net> Subject: Re: Serious bug in vm_page.h in current In-Reply-To: <199808260001.UAA03536@khavrinen.lcs.mit.edu> from Garrett Wollman at "Aug 25, 98 08:01:47 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Tue, 25 Aug 1998 20:40:55 -0500 (EST) Cc: wollman@khavrinen.lcs.mit.edu, dfr@nlsystems.com, dyson@iquest.net, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman said: > < > > This sounds very much like it could be related to the lockup Matt > > Dillon and I have been seeing. I just rebooted newsswitch with this > > change in it; I should know by the end of the day whether it had > > any effect. > > newsswitch has been up for more than nine hours now, which is longer > than it had been lasting. I'll give it a full day before proclaiming > success, though. > Yep, I did provide some info to Matt about this a few days ago, and I suspect that we would let me know if there were NEW problems. If this fixes it, it is indeed amazing how subtile some parts of the system are. I am really hoping that someone really does "get their arms" around the VM/VFS_BIO code -- and I am willing to help them as needed. The VM code is something that is tricky, even if you understand it. Also, IMO, the more people willing to become a/the VM czar, the better!!! -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 18:53:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20675 for freebsd-current-outgoing; Tue, 25 Aug 1998 18:53:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20649; Tue, 25 Aug 1998 18:53:16 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id SAA06045; Tue, 25 Aug 1998 18:52:26 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd005996; Tue Aug 25 18:52:20 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id SAA00704; Tue, 25 Aug 1998 18:52:16 -0700 (MST) From: Terry Lambert Message-Id: <199808260152.SAA00704@usr04.primenet.com> Subject: Re: Threads across processors To: paul@originative.co.uk (Paul Richards) Date: Wed, 26 Aug 1998 01:52:16 +0000 (GMT) Cc: gpalmer@FreeBSD.ORG, chuckr@Glue.umd.edu, freebsd-current@FreeBSD.ORG In-Reply-To: from "Paul Richards" at Aug 25, 98 10:11:54 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hotmail are apparently dropping FreeBSD in favour of Solaris because of > thread support as well :-( HotMail is using Solaris for the back-end data store, yes. But they are still using FreeBSD for the WWW Server front-end. Someone needs to nuke this rumor; I believe it got started when they first attempted to switch to NT, and after the failure, Sun pres-released this fact, and FreeBSD didn't press-release anything. After a recent exchange with Casper Dik, I'm pretty sure Solaris got the cooperative threading code correct in Solaris 2.6. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 18:56:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21265 for freebsd-current-outgoing; Tue, 25 Aug 1998 18:56:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21257; Tue, 25 Aug 1998 18:56:05 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA29858; Tue, 25 Aug 1998 18:55:13 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd029847; Tue Aug 25 18:55:10 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id SAA00915; Tue, 25 Aug 1998 18:55:00 -0700 (MST) From: Terry Lambert Message-Id: <199808260155.SAA00915@usr04.primenet.com> Subject: Re: Threads across processors To: mike@smith.net.au (Mike Smith) Date: Wed, 26 Aug 1998 01:55:00 +0000 (GMT) Cc: michaelh@cet.co.jp, gpalmer@FreeBSD.ORG, chuckr@glue.umd.edu, freebsd-current@FreeBSD.ORG In-Reply-To: <199808251338.NAA02533@dingo.cdrom.com> from "Mike Smith" at Aug 25, 98 01:38:18 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Our pipes are very fast. SYSV SHM's blunder is that it uses full blown > > system calls for synchronization. > > Yes. Anyone that thinks in terms of a context switch per transaction > between coprocesses is not designing properly. Using a shared mmap() > region and datastructures that don't require locking is another > cost-effective technique. A dirty little secret is that SYSV SHM in FreeBSD is much faster than mmap, because pages backed by anonymous pages instead of a vnode pager object do not have to be written through... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 19:25:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24630 for freebsd-current-outgoing; Tue, 25 Aug 1998 19:25:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24610; Tue, 25 Aug 1998 19:25:10 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id WAA20583; Tue, 25 Aug 1998 22:23:48 -0400 (EDT) Date: Tue, 25 Aug 1998 22:23:47 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Terry Lambert cc: Mike Smith , michaelh@cet.co.jp, gpalmer@FreeBSD.ORG, chuckr@glue.umd.edu, freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-Reply-To: <199808260155.SAA00915@usr04.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Aug 1998, Terry Lambert wrote: > A dirty little secret is that SYSV SHM in FreeBSD is much faster > than mmap, because pages backed by anonymous pages instead of a > vnode pager object do not have to be written through... What about this? From mmap(2): MAP_ANON Map anonymous memory not associated with any specific file. The file descriptor used for creating MAP_ANON must be -1. The offset parameter is ignored. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 19:34:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25785 for freebsd-current-outgoing; Tue, 25 Aug 1998 19:34:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ren.dtir.qld.gov.au (ns.dtir.qld.gov.au [203.108.138.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25772 for ; Tue, 25 Aug 1998 19:34:06 -0700 (PDT) (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id MAA23293; Wed, 26 Aug 1998 12:33:00 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma023262; Wed, 26 Aug 98 12:32:44 +1000 Received: from atlas.dtir.qld.gov.au (atlas.dtir.qld.gov.au [167.123.8.9]) by ogre.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id MAA25287; Wed, 26 Aug 1998 12:32:44 +1000 (EST) Received: from nymph.dtir.qld.gov.au (nymph.dtir.qld.gov.au [167.123.10.10]) by atlas.dtir.qld.gov.au (8.8.5/8.8.5) with ESMTP id MAA10123; Wed, 26 Aug 1998 12:32:43 +1000 (EST) Received: from nymph.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1]) by nymph.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id MAA06321; Wed, 26 Aug 1998 12:32:41 +1000 (EST) (envelope-from syssgm@nymph.dtir.qld.gov.au) Message-Id: <199808260232.MAA06321@nymph.dtir.qld.gov.au> To: Doug Rabson cc: "John S. Dyson" , freebsd-current@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: Serious bug in vm_page.h in current References: In-Reply-To: from Doug Rabson at "Tue, 25 Aug 1998 19:10:48 +0100" Date: Wed, 26 Aug 1998 12:32:40 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 25th August 1998, Doug Rabson wrote: >On Tue, 25 Aug 1998, Stephen McKay wrote: > >> On Tuesday, 25th August 1998, Doug Rabson wrote: >> >> Purely on naming now, the new inline vm_object_set_flag() and friends are >> well named. The PAGE_BUSY and PAGE_WAKEUP macros, etc, should be similarly >> named inline functions. For example, vm_page_busy_add() and vm_page_wakeup(). >I chose the PAGE_XXX type names since they seemed to follow the existing >macros in vm_page.h. I am perfectly happy to change them to inline >functions with a similar naming convention to the ones in vm_object as >long as all of the other PAGE_XXX macros change at the same time. I was perhaps too brief. All the PAGE_XXX macros would have to change to be consistent (hopefully changed to inline functions at the same time). I had noticed that you were being consistent with existing naming, but the naming used in vm_object.h is clearly better. >The i/o count should certainly have a less confusing name. Indeed. I'm sure you will come up with a good one. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 19:41:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26722 for freebsd-current-outgoing; Tue, 25 Aug 1998 19:41:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26717 for ; Tue, 25 Aug 1998 19:41:50 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id VAA02790; Tue, 25 Aug 1998 21:40:39 -0500 (EST) (envelope-from toor) Message-Id: <199808260240.VAA02790@dyson.iquest.net> Subject: Re: Serious bug in vm_page.h in current In-Reply-To: <199808260232.MAA06321@nymph.dtir.qld.gov.au> from Stephen McKay at "Aug 26, 98 12:32:40 pm" To: syssgm@dtir.qld.gov.au (Stephen McKay) Date: Tue, 25 Aug 1998 21:40:39 -0500 (EST) Cc: dfr@nlsystems.com, dyson@iquest.net, freebsd-current@FreeBSD.ORG, syssgm@dtir.qld.gov.au From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen McKay said: > > I was perhaps too brief. All the PAGE_XXX macros would have to change to > be consistent (hopefully changed to inline functions at the same time). > I had noticed that you were being consistent with existing naming, but the > naming used in vm_object.h is clearly better. > I agree that it is probably time to get rid of the PAGE_XXX macros. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 20:25:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01347 for freebsd-current-outgoing; Tue, 25 Aug 1998 20:25:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01337 for ; Tue, 25 Aug 1998 20:25:30 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id XAA18988; Tue, 25 Aug 1998 23:24:15 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: alexandr@mail.eecis.udel.edu cc: Paul Richards , "'Philippe Regnauld'" , Chuck Robey , freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Threads across processors In-reply-to: Your message of "Tue, 25 Aug 1998 11:36:43 PDT." <199808251836.LAA11123@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Aug 1998 23:24:15 -0400 Message-ID: <18984.904101855@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG alexandr@mail.eecis.udel.edu wrote in message ID <199808251836.LAA11123@hub.freebsd.org>: > So does this mean that we'll start working on PPC machines to edge out > AIX, or how about StrongARMs so that we can get a foothold in the NC > market? I don't know of enough PPC machines to make it worthwhile doing a port. At least in my experience SPARC's are more `available'. And I'd love to do a StrongARM port, but again its a very limited market, as I doubt that we'd actually get to run on any NC's. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 20:37:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02407 for freebsd-current-outgoing; Tue, 25 Aug 1998 20:37:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from artemis.syncom.net (artemis.syncom.net [206.64.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02399; Tue, 25 Aug 1998 20:37:09 -0700 (PDT) (envelope-from cyouse@artemis.syncom.net) Received: from localhost (localhost [[UNIX: localhost]]) by artemis.syncom.net (8.8.8/8.8.8) with SMTP id XAA04719; Tue, 25 Aug 1998 23:45:48 -0400 (EDT) Date: Tue, 25 Aug 1998 23:45:47 -0400 (EDT) From: Charles Youse To: Brian Feldman cc: Gary Palmer , Paul Richards , "'Philippe Regnauld'" , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, Brian Feldman wrote: > The SPARC port's not dead? I've been trying to get my hands on an UltraSPARC board to work on the port, but I'm experiencing a cashflow problem. :) I decided to start with the older sun architectures (i.e., sun4m), but I discovered that the differences between sun4m and sun4u are sufficient enough to make that a waste of time. Chuck Youse cyouse@syncom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 20:41:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02863 for freebsd-current-outgoing; Tue, 25 Aug 1998 20:41:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02853; Tue, 25 Aug 1998 20:41:39 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id XAA19238; Tue, 25 Aug 1998 23:40:46 -0400 (EDT) Date: Tue, 25 Aug 1998 23:40:45 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Gary Palmer cc: alexandr@mail.eecis.udel.edu, Paul Richards , "'Philippe Regnauld'" , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-Reply-To: <18984.904101855@gjp.erols.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, Gary Palmer wrote: > I don't know of enough PPC machines to make it worthwhile doing a port. At > least in my experience SPARC's are more `available'. I'd give my eye teeth to be able to run FreeBSD on Macintoshes. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 21:09:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04957 for freebsd-current-outgoing; Tue, 25 Aug 1998 21:09:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04952; Tue, 25 Aug 1998 21:09:10 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id UAA24736; Tue, 25 Aug 1998 20:41:23 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Gary Palmer" cc: alexandr@mail.eecis.udel.edu, Paul Richards , "'Philippe Regnauld'" , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-reply-to: Your message of "Tue, 25 Aug 1998 23:24:15 EDT." <18984.904101855@gjp.erols.com> Date: Tue, 25 Aug 1998 20:41:22 -0700 Message-ID: <24733.904102882@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't know of enough PPC machines to make it worthwhile doing a port. At Macintoshes. iMACs especially. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 21:20:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05773 for freebsd-current-outgoing; Tue, 25 Aug 1998 21:20:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05768; Tue, 25 Aug 1998 21:20:44 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id VAA17907; Tue, 25 Aug 1998 21:19:51 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd017888; Tue Aug 25 21:19:47 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id VAA01004; Tue, 25 Aug 1998 21:19:40 -0700 (MST) From: Terry Lambert Message-Id: <199808260419.VAA01004@usr07.primenet.com> Subject: Re: Threads across processors To: ben@rosengart.com Date: Wed, 26 Aug 1998 04:19:40 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, michaelh@cet.co.jp, gpalmer@FreeBSD.ORG, chuckr@glue.umd.edu, freebsd-current@FreeBSD.ORG In-Reply-To: from "Snob Art Genre" at Aug 25, 98 10:23:47 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > A dirty little secret is that SYSV SHM in FreeBSD is much faster > > than mmap, because pages backed by anonymous pages instead of a > > vnode pager object do not have to be written through... > > What about this? From mmap(2): > > MAP_ANON Map anonymous memory not associated with any specific file. > The file descriptor used for creating MAP_ANON must be -1. > The offset parameter is ignored. Memory mapped this way can only be shared between a parent process and children, and then only if marked for inheritance. This is a hell of a lot less useful that SYSV SHM, especially if the memory is to be attached by a non-child process for the purpose of status reporting and/or control (for example). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 21:23:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06162 for freebsd-current-outgoing; Tue, 25 Aug 1998 21:23:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from artemis.syncom.net (artemis.syncom.net [206.64.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06140; Tue, 25 Aug 1998 21:23:38 -0700 (PDT) (envelope-from cyouse@artemis.syncom.net) Received: from localhost (localhost [[UNIX: localhost]]) by artemis.syncom.net (8.8.8/8.8.8) with SMTP id AAA04776; Wed, 26 Aug 1998 00:31:50 -0400 (EDT) Date: Wed, 26 Aug 1998 00:31:50 -0400 (EDT) From: Charles Youse To: ben@rosengart.com cc: Gary Palmer , alexandr@mail.eecis.udel.edu, Paul Richards , "'Philippe Regnauld'" , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, Snob Art Genre wrote: > I'd give my eye teeth to be able to run FreeBSD on Macintoshes. Agreed; while I'm sure we all agree that MacOS blows[1], the modern Mac hardware leaves PCs in the dust. Don't crucify me for admitting to this, but I do run Linux on a Mac 7600/132 (that's a 132MHz PPC) and it absolutely flies. The problem with ports to Mac hardware has always been Apple's reluctance to release the required information, but the existence of two independent ports of Linux to the PPC (one sanctioned by Apple) indicates that Apple's attitude has changed. NetBSD actually has an experimental PowerMac port in progress. Last I checked, it was booting succesfully into single-user mode. Chuck Youse [1] This is an unfair criticism, as MacOS was ahead of its time when it was designed nearly 20 years ago, and ran on hardware primitive by today's standards. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 23:11:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14183 for freebsd-current-outgoing; Tue, 25 Aug 1998 23:11:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14172 for ; Tue, 25 Aug 1998 23:11:39 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.8.7/8.8.7) with SMTP id CAA12946 for ; Wed, 26 Aug 1998 02:10:47 -0400 (EDT) Received: by mozart (5.65c/SAS/Domains/5-6-90) id AA02989; Wed, 26 Aug 1998 02:10:47 -0400 From: "John W. DeBoskey" Message-Id: <199808260610.AA02989@mozart> Subject: ESTALE on nfs mount point(HELP!) To: freebsd-current@FreeBSD.ORG Date: Wed, 26 Aug 1998 02:10:47 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The following is occurring on a machine running 3.0-980506-SNAP. I don't have any 2.x machines to replicate this problem with. Given the following situation, how can I unmount an nfs filesystem that the system doesn't think is mounted (unless I try to mount it)??? If I reboot the machine having this problem than everything will work correctly (until it fails again). Note: 'afsserver' is runnning an AFS/NFS translator. # df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s1a 254063 20499 213239 9% / /dev/wd0s1g 4546645 521967 3660947 12% /usr /dev/wd0s1e 254063 3495 230243 1% /var procfs 4 4 0 100% /proc /dev/ccd0c 40370268 20696354 16444293 56% /hpdisk server01:/home/ss1 151811856 87502404 64309452 58% /ss1 amd:131 0 0 0 100% /u amd:131 0 0 0 100% /nfs Note: df doesn't show the filesystem as mounted. # mount afsserver:/afs /afs mount: /afs: Stale NFS file handle # umount -vf /afs /afs: unmount from afsserver:/afs umount: afsserver:/afs: No such file or directory # rmdir /afs rmdir: /afs: Device busy # showmount -e afsserver Exports list on afsserver: /afs Everyone /local Everyone / Everyone # /afs is normally mounted via the fstab file. Any accesses to /afs in it's current condition return ESTALE. So, how can I fix this problem without a reboot? For what its worth, an 'ls /nfs/afsserver/afs' automounts correctly and works. Unfortunately, I can't use that mount point (don't ask why). Any pointers are greatly appreciated. Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 25 23:52:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17557 for freebsd-current-outgoing; Tue, 25 Aug 1998 23:52:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA17552 for ; Tue, 25 Aug 1998 23:52:40 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id IAA00267; Wed, 26 Aug 1998 08:56:12 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Wed, 26 Aug 1998 08:56:12 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Julian Elischer cc: freebsd-current@FreeBSD.ORG Subject: Re: Panic with DEVFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, Julian Elischer wrote: > is it possible to find out which device it is? Doesn't matter (at least with a dozen of my tests, when I was disabling various devices). > > disabled devices should not show up in devfs as they They don't. I checked it - I was able to do 'ls -l', and got the full listing, and in a second or two later the machine panics. I'm totally lame when it comes to FS internals, but this looks to me as if some delayed action (caching? cleaning? read-ahead? whatever?) is causing this. I'm receiving also another error related to / on MFS: when I press Ctrl-Alt-Del, the system should sync disks and then unmount them, right? but I'm getting 'unmount of / failed (30)' which means EROFS, which is strange because / is mounted r/w. Any ideas? > should not be probed and the probe routine should be responsible for > adding the devfs entries.. > (actually the attach routine but...) > except for devices that do not probe, (e.g. /dev/mem) > which do it in their init routine. > > > > > > On Tue, 25 Aug 1998, Andrzej Bialecki wrote: > > > Hi, > > > > It was pointed to me that it's very easy to panic -current system running > > DEVFS on /dev, with / on MFS. > > > > The problem manifested itself with picobsd floppy. The following scenario > > causes panic with "mfs_strategy: bad dev": > > > > 1. boot with -c > > 2. disable at least one device > > 3. log in > > 4. cd /dev > > 5. ls -l > > > > What's funny is that when I do 'ls' (without -l) in step 5., everything is > > ok. > > > > My guess is that DEVFS doesn't like these devices which are present in > > kernel, but are disabled... > > > > Andrzej Bialecki > > > > +---------------------+------------------------+--------------------------+ > > | | When in problem or in | if(halt_per_mth > 0) { | > > | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | > > | Network in Poland | scream and shout. | } | > > + --------------------+------------------------+--------------------------+ > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 00:09:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18719 for freebsd-current-outgoing; Wed, 26 Aug 1998 00:09:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcpsj.pfcs.com (harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18714 for ; Wed, 26 Aug 1998 00:08:58 -0700 (PDT) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Wed, 26 Aug 1998 03:06:51 -0400 (EDT) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Wed, 26 Aug 1998 00:06:46 -0700 (PDT) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Wed, 26 Aug 1998 03:06:44 -0400 (EDT) X-Mailer: exmh version 2.0.2 2/24/98 To: joelh@gnu.org cc: garbanzo@hooked.net, mike@smith.net.au, entropy@compufit.at, wwoods@cybcon.com, freebsd-current@FreeBSD.ORG Subject: Re: gcc 2.8 In-Reply-To: Joel Ray Holveck's (joelh@gnu.org) message dated Tue, 25 Aug 1998 17:54:26. <199808252254.RAA01679@detlev.UUCP> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Aug 1998 03:06:44 -0400 Message-ID: <25448.904115204@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I tested two packages. > > One compares a number (6-8) byte move subroutines (memcpy, bcopy, a variety > > of Duff's devices (using char, short, and int), and some other "fast" byte > > copies I've snarfed over the years). > > Just to be sure: these are using their own recompiled bcopy etc, and > not running the ones out of libc? This benchmark uses whatever libc byte movers are detected (bcopy or memcpy), and 5 or 6 different "source" versions. > > I run a reasonable quantity of different size/alignments against each of > > these, and report the CPU time of each one. > > Could you please post this data? It's kinda boring, but if everybody is interested I'll post it. If only a couple of folks are interested, I'll send it directly. Basically, I added the following code to the byte-mover subroutine: #ifdef BMOVESTATS #define BMS_MAXSIZE 2049 int bms[BMS_MAXSIZE + 1][4][4]; #endif /* BMOVESTATS */ (I picked 2049 because this application hardly ever moves bigger chunks of memory.) ... and inside the byte mover subroutine: #ifdef BMOVESTATS if((n = len) > BMS_MAXSIZE) { n = BMS_MAXSIZE;} ++bms[n][((int)src) & 3][((int)dst) & 3]; #endif /* BMOVESTATS */ ... and I call this subroutine before the executable exits: void bmovestats(void) { #ifdef BMOVESTATS int i; int d; int s; FILE *fp; #define BMOVE_STATFILE "bmovestats" if((fp = fopen(BMOVE_STATFILE, "w")) == NULL) { fp = stderr;} for(i = 0; i <= BMS_MAXSIZE; ++i) for (s = 0; s < 4; s++) for (d = 0; d < 4; d++) if(bms[i][s][d]) fprintf(fp, "%d\t%d\t%d\t%d\n", i, s, d, bms[i][s][d]); if(fp != stderr) { fclose(fp);} #endif /* BMOVESTATS */ return;} Then I ran several applications under various production conditions, collected various "bmovestats" files, and then ran a little program that, for each byte mover, basically ran the following loop (in this case, for bcopy): #ifdef HAVE_BCOPY rewind(ifp); (void)times(&t_b); t_u = t_b.tms_utime; while((rc = fscanf(ifp, "%d%d%d%d", &len, &sa, &da, &qty)) != EOF) { sp = src + sa; dp = dst + da; for(i = 0; i < qty; i++) { bcopy(sp, dp, len);}} (void)times(&t_b); printf("%8.0d", t_b.tms_utime - t_u - ovhd); fflush(stdout); #endif /* HAVE_BCOPY */ the "ovhd" value is the time to run the loop with *no* byte copy being performed; I suspect a Really Good Compiler would pretty much invalidate this benchmark. "ifp" points to the current "bmovestats" file. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 00:58:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22712 for freebsd-current-outgoing; Wed, 26 Aug 1998 00:58:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22707 for ; Wed, 26 Aug 1998 00:58:52 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id IAA05136; Wed, 26 Aug 1998 08:58:00 +0100 (BST) Date: Wed, 26 Aug 1998 08:58:00 +0100 (BST) From: Doug Rabson To: Alex cc: current Subject: Re: GNU Binutils? (Was: re: gcc 2.8) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, Alex wrote: > Speaking of upgrading the compiler, what are the chances of upgrading the > binutils to 2.9.1 (at least for the ELF bits) in -current? > > I mention this, because as I was trying to compile koffice, I could > reliably segfault as (2.8.1 from -current), which would in turn nicely > knonk out egcs (and the rest of the build process). Using the version of > gas that came with binutils 2.9.1 (configured for an > i586-unknown-freebsdelf system) seems to have solved my problems. > > Also, the building of gas from the -current sources seems to ignore CFLAGS > (and CXXFLAGS), but not CC/CXX. Should I open a pr for these and other > minor stuff like this? I would also like to see 2.9.1 in our tree but I have no time to work on it. There are a few useful alpha fixes in 2.9.1. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 01:17:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23880 for freebsd-current-outgoing; Wed, 26 Aug 1998 01:17:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23875 for ; Wed, 26 Aug 1998 01:17:24 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id SAA02383; Wed, 26 Aug 1998 18:27:24 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808260827.SAA02383@cimlogic.com.au> Subject: Re: GNU Binutils? (Was: re: gcc 2.8) In-Reply-To: from Doug Rabson at "Aug 26, 98 08:58:00 am" To: dfr@nlsystems.com (Doug Rabson) Date: Wed, 26 Aug 1998 18:27:24 +1000 (EST) Cc: garbanzo@hooked.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > I would also like to see 2.9.1 in our tree but I have no time to work on > it. There are a few useful alpha fixes in 2.9.1. I think we should defer this until after 3.0 is released. Perhaps we should consider /just/ after. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 01:55:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26969 for freebsd-current-outgoing; Wed, 26 Aug 1998 01:55:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26964 for ; Wed, 26 Aug 1998 01:55:24 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA29995; Wed, 26 Aug 1998 09:54:09 +0100 (BST) Date: Wed, 26 Aug 1998 09:54:08 +0100 (BST) From: Doug Rabson To: "John S. Dyson" cc: Stephen McKay , freebsd-current@FreeBSD.ORG Subject: Re: Serious bug in vm_page.h in current In-Reply-To: <199808260240.VAA02790@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, John S. Dyson wrote: > Stephen McKay said: > > > > I was perhaps too brief. All the PAGE_XXX macros would have to change to > > be consistent (hopefully changed to inline functions at the same time). > > I had noticed that you were being consistent with existing naming, but the > > naming used in vm_object.h is clearly better. > > > I agree that it is probably time to get rid of the PAGE_XXX macros. How about this: Index: vm_page.h =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_page.h,v retrieving revision 1.44 diff -u -u -r1.44 vm_page.h --- vm_page.h 1998/08/24 08:39:38 1.44 +++ vm_page.h 1998/08/26 08:50:32 @@ -281,32 +281,58 @@ * Functions implemented as macros */ -#define PAGE_SET_FLAG(m, bits) atomic_set_short(&(m)->flags, bits) +static __inline void +vm_page_set_flag(vm_page_t m, unsigned int bits) +{ + atomic_set_short(&(m)->flags, bits); +} + +static __inline void +vm_page_clear_flag(vm_page_t m, unsigned int bits) +{ + atomic_clear_short(&(m)->flags, bits); +} -#define PAGE_CLEAR_FLAG(m, bits) atomic_clear_short(&(m)->flags, bits) +#if 0 +static __inline void +vm_page_assert_wait(vm_page_t m, int interruptible) +{ + vm_page_set_flag(m, PG_WANTED); + assert_wait((int) m, interruptible); +} +#endif -#define PAGE_ASSERT_WAIT(m, interruptible) { \ - PAGE_SET_FLAG(m, PG_WANTED); \ - assert_wait((int) (m), (interruptible)); \ +static __inline void +vm_page_busy(vm_page_t m) +{ + vm_page_busy(m); } -#define PAGE_WAKEUP(m) { \ - PAGE_CLEAR_FLAG(m, PG_BUSY); \ - if (((m)->flags & PG_WANTED) && ((m)->busy == 0)) { \ - PAGE_CLEAR_FLAG(m, PG_WANTED); \ - wakeup((m)); \ - } \ +static __inline void +vm_page_wakeup(vm_page_t m) +{ + vm_page_clear_flag(m, PG_BUSY); + if ((m->flags & PG_WANTED) && (m->busy == 0)) { + vm_page_clear_flag(m, PG_WANTED); + wakeup(m); + } } -#define PAGE_BUSY(m) atomic_add_char(&(m)->busy, 1) +static __inline void +vm_page_start_io(vm_page_t m) +{ + atomic_add_char(&(m)->busy, 1); +} -#define PAGE_BWAKEUP(m) { \ - atomic_subtract_char(&(m)->busy, 1); \ - if ((((m)->flags & (PG_WANTED | PG_BUSY)) == PG_WANTED) && \ - ((m)->busy == 0)) { \ - PAGE_CLEAR_FLAG(m, PG_WANTED); \ - wakeup((m)); \ - } \ +static __inline void +vm_page_finish_io(vm_page_t m) +{ + atomic_subtract_char(&m->busy, 1); + if (((m->flags & (PG_WANTED | PG_BUSY)) == PG_WANTED) && + (m->busy == 0)) { + vm_page_clear_flag(m, PG_WANTED); + wakeup(m); + } } @@ -381,11 +407,11 @@ if (prot == VM_PROT_NONE) { if (mem->flags & (PG_WRITEABLE|PG_MAPPED)) { pmap_page_protect(VM_PAGE_TO_PHYS(mem), VM_PROT_NONE); - PAGE_CLEAR_FLAG(mem, PG_WRITEABLE|PG_MAPPED); + vm_page_clear_flag(mem, PG_WRITEABLE|PG_MAPPED); } } else if ((prot == VM_PROT_READ) && (mem->flags & PG_WRITEABLE)) { pmap_page_protect(VM_PAGE_TO_PHYS(mem), VM_PROT_READ); - PAGE_CLEAR_FLAG(mem, PG_WRITEABLE); + vm_page_clear_flag(mem, PG_WRITEABLE); } } -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 01:58:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27365 for freebsd-current-outgoing; Wed, 26 Aug 1998 01:58:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27353 for ; Wed, 26 Aug 1998 01:58:13 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA04137; Wed, 26 Aug 1998 09:57:22 +0100 (BST) Date: Wed, 26 Aug 1998 09:57:21 +0100 (BST) From: Doug Rabson To: John Birrell cc: garbanzo@hooked.net, current@FreeBSD.ORG Subject: Re: GNU Binutils? (Was: re: gcc 2.8) In-Reply-To: <199808260827.SAA02383@cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Aug 1998, John Birrell wrote: > Doug Rabson wrote: > > I would also like to see 2.9.1 in our tree but I have no time to work on > > it. There are a few useful alpha fixes in 2.9.1. > > I think we should defer this until after 3.0 is released. Perhaps we > should consider /just/ after. I might commit the 2.9.1 version of alpha-opc.c. It has some fixes which are necessary for building SimOS. On the other hand, maybe I will just keep that change in my local tree for now. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 02:10:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28351 for freebsd-current-outgoing; Wed, 26 Aug 1998 02:10:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ren.dtir.qld.gov.au (ns.dtir.qld.gov.au [203.108.138.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28336 for ; Wed, 26 Aug 1998 02:10:10 -0700 (PDT) (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id TAA27328; Wed, 26 Aug 1998 19:09:17 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma027321; Wed, 26 Aug 98 19:09:03 +1000 Received: from atlas.dtir.qld.gov.au (atlas.dtir.qld.gov.au [167.123.8.9]) by ogre.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id TAA11892; Wed, 26 Aug 1998 19:09:03 +1000 (EST) Received: from nymph.dtir.qld.gov.au (nymph.dtir.qld.gov.au [167.123.10.10]) by atlas.dtir.qld.gov.au (8.8.5/8.8.5) with ESMTP id TAA13971; Wed, 26 Aug 1998 19:09:02 +1000 (EST) Received: from nymph.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1]) by nymph.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id TAA11802; Wed, 26 Aug 1998 19:09:01 +1000 (EST) (envelope-from syssgm@nymph.dtir.qld.gov.au) Message-Id: <199808260909.TAA11802@nymph.dtir.qld.gov.au> To: Doug Rabson cc: freebsd-current@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: Serious bug in vm_page.h in current References: In-Reply-To: from Doug Rabson at "Wed, 26 Aug 1998 09:54:08 +0100" Date: Wed, 26 Aug 1998 19:09:00 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 26th August 1998, Doug Rabson wrote: >How about this: > >Index: vm_page.h >=================================================================== >+static __inline void >+vm_page_busy(vm_page_t m) >+{ >+ vm_page_busy(m); > } An "oops"? Otherwise looking good. But to be picky, I prefer vm_page_flag_clear() and vm_page_flag_set() to vm_page_clear_flag() and vm_page_set_flag(). Similarly, I think that vm_page_io_start() and vm_page_io_finish() would be better than vm_page_start_io() and vm_page_finish_io(). I hope you can see my reasoning. But, I'm not going to arm wrestle you for it if you don't like it. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 02:19:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29708 for freebsd-current-outgoing; Wed, 26 Aug 1998 02:19:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf38.cruzers.com [205.215.232.38]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA29700 for ; Wed, 26 Aug 1998 02:19:32 -0700 (PDT) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 11834 invoked by uid 100); 26 Aug 1998 09:19:12 -0000 Message-ID: <19980826021908.A11822@top.worldcontrol.com> Date: Wed, 26 Aug 1998 02:19:08 -0700 To: freebsd-current@FreeBSD.ORG Subject: scsiconf.o: Undefined symbol `_scsi_tinit' Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why is this happening? loading kernel scsiconf.o: Undefined symbol `_scsi_tinit' referenced from text segment scsiconf.o: Undefined symbol `_scsi_tinit' referenced from text segment scsiconf.o: Undefined symbol `_scsi_tinit' referenced from text segment scsiconf.o: Undefined symbol `_scsi_cinit' referenced from text segment ... I cvsup'ed around Wed Aug 26 02:18:47 PDT 1998. -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 02:28:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00892 for freebsd-current-outgoing; Wed, 26 Aug 1998 02:28:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA00886 for ; Wed, 26 Aug 1998 02:27:57 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA05076; Wed, 26 Aug 1998 10:27:04 +0100 (BST) Date: Wed, 26 Aug 1998 10:27:04 +0100 (BST) From: Doug Rabson To: Stephen McKay cc: freebsd-current@FreeBSD.ORG, "John S. Dyson" Subject: Re: Serious bug in vm_page.h in current In-Reply-To: <199808260909.TAA11802@nymph.dtir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Aug 1998, Stephen McKay wrote: > On Wednesday, 26th August 1998, Doug Rabson wrote: > > >How about this: > > > >Index: vm_page.h > >=================================================================== > > >+static __inline void > >+vm_page_busy(vm_page_t m) > >+{ > >+ vm_page_busy(m); > > } > > An "oops"? Otherwise looking good. Dodgy global replace :-) > > But to be picky, I prefer vm_page_flag_clear() and vm_page_flag_set() to > vm_page_clear_flag() and vm_page_set_flag(). Similarly, I think that > vm_page_io_start() and vm_page_io_finish() would be better than > vm_page_start_io() and vm_page_finish_io(). I hope you can see my > reasoning. > > But, I'm not going to arm wrestle you for it if you don't like it. I normally use class,verb,noun construction in writing apis for no good reason. The api in vm_object uses class,noun,verb mostly (apart from my flag changes...) It would probably make the thing more self-consistent to change the names. What do you think John? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 04:39:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA16505 for freebsd-current-outgoing; Wed, 26 Aug 1998 04:39:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA16490 for ; Wed, 26 Aug 1998 04:39:11 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from support1.cybcon.com (william@support1.cybcon.com [205.147.76.99]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id EAA20892 for ; Wed, 26 Aug 1998 04:38:21 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 26 Aug 1998 04:38:17 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: FreebSD Current Subject: Todays cvsup....... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While Makeing world this morn.......... ------------------------------------------------- rm -f .depend /usr/local/src/sys/i386/boot/biosboot/GRTAGS /usr/local/src/sys/i386/boot/biosboot/GSYMS /usr/local/src/sys/i386/boot/biosboot/GTAGS ===> sys/i386/boot/cdboot rm -f boot.img boot.nohdr boot.strip machine boot start.o table.o boot2.o boot.o asm.o bios.o serial.o probe_keyboard.o io.o cdrom.o malloc.o rm -f .depend /usr/local/src/sys/i386/boot/cdboot/GRTAGS /usr/local/src/sys/i386/boot/cdboot/GSYMS /usr/local/src/sys/i386/boot/cdboot/GTAGS ===> sys/i386/boot/dosboot rm -f fbsdboot.exe machine ===> sys/i386/boot/kzipboot rm -f machine kztail.o kzhead.o tail.o head.o boot.o unzip.o misc.o malloc.o inflate.o rm -f .depend /usr/local/src/sys/i386/boot/kzipboot/GRTAGS /usr/local/src/sys/i386/boot/kzipboot/GSYMS /usr/local/src/sys/i386/boot/kzipboot/GTAGS ===> sys/i386/boot/netboot rm -f netboot.com makerom start2.ro 3c509.o ns8390.o machine nb8390.com nb3c509.com nb8390.rom nb3c509.rom start2.o main.o misc.o bootmenu.o rpc.o netboot.8.gz netboot.8.cat.gz rm -f .depend /usr/local/src/sys/i386/boot/netboot/GRTAGS /usr/local/src/sys/i386/boot/netboot/GSYMS /usr/local/src/sys/i386/boot/netboot/GTAGS ===> sys/i386/boot/rawboot rm -f boot.nohdr boot.strip rawboot sizetest machine boot start.o table.o boot2.o boot.o asm.o bios.o serial.o probe_keyboard.o io.o disk.o sys.o rm -f .depend /usr/local/src/sys/i386/boot/rawboot/GRTAGS /usr/local/src/sys/i386/boot/rawboot/GSYMS /usr/local/src/sys/i386/boot/rawboot/GTAGS ===> usr.bin "Makefile", line 28: Unassociated shell command "kdump key keyinfo keyinit keylogin keylogout killall ktrace kzip lam last lastcomm leave lex limits locate lock lockf logger login logname look lorder lsvfs m4 mail make mesg mkdep mkfifo mklocale mkstr mktemp mk_cmds more msgs ncal netstat newkey nfsstat nice nohup objformat opieinfo opiekey opiepasswd pagesize passwd paste pr printenv printf quota rdist renice rev rlogin rpcgen rpcinfo rs rsh rup ruptime rusers rwall rwho script sed shar showmount soelim split su symorder tail talk tconv tcopy tee tftp time tip tn3270 top touch tput tr true tset tsort tty ul uname unexpand unifdef uniq units unvis users uudecode uuencode vacation vgrind vi vis w wall wc what whereis which who whois window write xargs xinstall xlint xstr yacc yes ypcat ypmatch ypwhich" make: fatal errors encountered -- cannot continue *** Error code 1 Stop. *** Error code 1 ---------------------------------- --------------------- William Woods Date: 26-Aug-98 / Time: 04:36:52 goto to: http//www.freebsd.org. --> FreeBSD 3.0 CURRENT <-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 05:07:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19159 for freebsd-current-outgoing; Wed, 26 Aug 1998 05:07:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19150; Wed, 26 Aug 1998 05:07:50 -0700 (PDT) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id OAA20913; Wed, 26 Aug 1998 14:06:43 +0200 (MET DST) Message-ID: <19980826140642.A20511@cons.org> Date: Wed, 26 Aug 1998 14:06:42 +0200 From: Martin Cracauer To: Mike Smith , Michael Hancock Cc: Gary Palmer , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors References: <199808251338.NAA02533@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=2oS5YaxWCcQjTEyO X-Mailer: Mutt 0.93.1i In-Reply-To: <199808251338.NAA02533@dingo.cdrom.com>; from Mike Smith on Tue, Aug 25, 1998 at 01:38:18PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii In <199808251338.NAA02533@dingo.cdrom.com>, Mike Smith wrote: > > On Tue, 25 Aug 1998, Gary Palmer wrote: > > > > > Heck, SMI wrote `doors' for the very reason that IPC *blows* in all cases, and > > > that to pull off the speedups with NSCD that they wanted, they had to get the > > > IPC overhead reduced a lot. I think I even have slides somewhere comparing > > > pipes, SYSV SHM, etc times for message passing in terms of transit time. > > > > Our pipes are very fast. SYSV SHM's blunder is that it uses full blown > > system calls for synchronization. Aehm, and pipes don't require full-blown system calls to send/receive notifications and require kernel resheduling before anything happens after sending a message? > Yes. Anyone that thinks in terms of a context switch per transaction > between coprocesses is not designing properly. For your amusement, I appended a message I once forwarded to -hackers, regarding mapping of userlevel threads to kernel shedulable entities. But in a way that is like sendfile and other combined system calls: Did anyone actually gain any data how much slower a one-process-per-thread model is? For any application? > Using a shared mmap() > region and datastructures that don't require locking is another > cost-effective technique. I'm afraid I have to count this as *very* cheap shot :-) Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=l I wrote: > > I still like the simpliticity of a kernel-only thread solution. If > > that way turns out to be too inefficient, the DEC way seems to be a > > solution that doesn't need async system calls and has no efficiency > > disadvantage I can see (compared to a sysyem with async syscalls > > only). > > > > I hope to get further details on the DEC implementation. Here's what Dave Butenhof told me about DEC's interface. Dave implements the userlevel part of DEC's thread interface. This answer is a bit out of context, if you need the previous discussion, please let me know. My original question was how blocking syscalls are treated. In Digital Unix, the kernel reports a blocking syscall in one thread back to the userlevel library, which reshedules another thread on that "kernel" thread. I asked for further details how a userlevel library could get rid of an already blocking syscall, and here's what I heared: > ~Message-Id: <32A5797C.6231@zko.dec.com> > ~Date: Wed, 04 Dec 1996 08:15:40 -0500 > ~From: Dave Butenhof > ~Organization: Digital Equipment Corporation > ~To: cracauer@wavehh.hanse.de > ~Cc: "Butenhof, Dave" > ~Subject: Re: Blocking syscall handling in one-to-many thread implementations > > [...] > > [This was my, Martins, question] > > But how exactly is resheduling on your KECs done? If a KECs is waiting > > in a blocking syscall, how can the userlevel sheduler reassign it? How > > can the userlevel library free it from the syscall? > > > > And what happens to the syscall? Is it translated into a non-blocking > > version and the kernel informs the userlevel sheduler when it arrives? > > I was trying to describe what happens from YOUR perspective, more than > what actually happens in the thread library & kernel. The internals are, > as always, a little more complicated. > > The thread library maintains a constant pool of (up to) KECs, where > is normally set by the number of physical processors in the system. > (It may be smaller, if your process is locked into a processor set.) > These are the "virtual processors" (VPs). The thread library schedules > user threads on the pool of VPs, trying to keep all of them busy. If > you don't have enough user threads to keep that many VPs busy, they may > not all get started, or VPs already running may go into the "null > thread" loop and idle -- which returns the KEC to the kernel's pool for > reuse. We'll get it back if we need it later. > > When a thread blocks in the kernel, the KEC stays in the kernel, but it > gives us an upcall in a *new* (or recycled) KEC to replace the VP. When > the blocking operation finishes, the kernel gives us a completion upcall > in the original KEC. It's no longer a VP, so we just save the context > and dismiss it. > > The key is the distinction between "KEC" and "VP". There may be 100 KECs > attached to a process, but, on a typical quad-CPU system, only (up to) 4 > of them at any time are "VPs". The rest are just holding kernel context > across some blocking operation. Whereas, in a strict kernel-mode > implementation, each user thread is a KEC, we have a KEC only for each > running thread and each thread blocked in the kernel. The number of KECs > will fluctuate -- and, if you hit your quota for KECs (Mach threads), > any additional kernel blocking operations will start to lower > concurrency. The most common blocking operations, mutexes & condition > variables (and some others), however, are completely in user mode. > > We're going to continue streamlining the process as we go (like moving > some kernel blocking states out into user mode, and reducing the context > that the kernel needs to keep below a full KEC), but, in general, it > works very well. The kernel developer and I (I work mostly in the > library) have kicked around the idea of doing a paper on the design. > Mostly, I've been too busy with a book for a ridiculously long time, and > the development requirements never stop. Maybe some day. Possibly once > we've gone through a full release cycle and have the architecture > stabilized better. > > /---[ Dave Butenhof ]-----------------------[ butenhof@zko.dec.com ]---\ > | Digital Equipment Corporation 110 Spit Brook Rd ZKO2-3/Q18 | > | 603.881.2218, FAX 603.881.0120 Nashua NH 03062-2698 | > \-----------------[ Better Living Through Concurrency ]----------------/ > > --2oS5YaxWCcQjTEyO-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 05:27:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21341 for freebsd-current-outgoing; Wed, 26 Aug 1998 05:27:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA21334 for ; Wed, 26 Aug 1998 05:27:13 -0700 (PDT) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id OAA21047; Wed, 26 Aug 1998 14:25:42 +0200 (MET DST) Message-ID: <19980826142541.B20511@cons.org> Date: Wed, 26 Aug 1998 14:25:41 +0200 From: Martin Cracauer To: Stephen Hocking-Senior Programmer PGS Tensor Perth , Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops References: <199808252351.JAA32306@godzilla.zeta.org.au> <199808260127.JAA02700@ariadne.tensor.pgs.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=LpQ9ahxlCli8rRTG X-Mailer: Mutt 0.93.1i In-Reply-To: <199808260127.JAA02700@ariadne.tensor.pgs.com>; from Stephen Hocking-Senior Programmer PGS Tensor Perth on Wed, Aug 26, 1998 at 09:27:48AM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --LpQ9ahxlCli8rRTG Content-Type: text/plain; charset=us-ascii In <199808260127.JAA02700@ariadne.tensor.pgs.com>, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > [Much scary stuff regarding traps and the like...] > > OK, I've had a look at machine/trap.h, how do I go about getting info on > exactly was exception was caused? A brief perusal of the man pages for math > and fpsetmask offers no clues (unless I've missed something totally obvious). > All the program wishes to do is note the fact and excveption has occured, get > some runtime stats (which is where that next FP operation happens) and exit. As far as I know, you can't. The kernel does not pass the FP registers as they were in the mainline program flow to your signal handler. What we need here is a system call to ask the kernel for the FP register contents which it should have saved before entering the FP handler. If the user required so, by a system call, sysctl variable or kernel config option. I actually didn't beleive this :-) and wrote some code to get the registers via the "hidden" third parameter to a signal handler, but in fact the exception indication bits were cleared. Example code to copy the register contents to some save place: static int handler(int sig, int code, struct sigcontext *scp) { #define TMP "FPE handler\n" write(2,TMP,sizeof(TMP)-1); #undef TMP sig_fpe_was_here++; sig_sig = sig; sig_code = code; memcpy(&sig_context, scp, sizeof(*scp)); return sig; } It's very possible that this code is nonsense. I appended some programs tangling with FP on FreeBSD. This fragment is from "freebsd-signal.c". Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ --LpQ9ahxlCli8rRTG Content-Type: application/x-tar-gz Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="float.tar.gz" H4sIALj94zUAA+1ce3fbNrLvv+KnmLpxI9p6UbLkrBTnrmLLqe6VH8dyNtnGqZYmIYkNReqQ lB136/3sdwYAn6IsbxM73bPmOY0JcADMAIOZ3wygjm1XD6rfPegDO7XdZhO+AwBtV+N/AWry ryxAq7lb291tteoNpNK0VuM7aD4sW+JZ+IHuAXxneLqhL5i3iu56ypj9GAw97jPm64/CV0w2 9iuzTw8whlartXZ2Vq5/fXd3J15/bRepGg0N17/2ALwsPf/l66/bdrvwrNgdDFRF2T/rjvb3 96AwMQwFXwr4RdSFHw9G3eNhHynKuuNbUJ4zU3cCy4Cy+DIanrw92+8J4sPRu97ZGRG/Y57n ekpY/bo77O0VyhMon0SU3bNjTokMQfndtWcFrOwHnuVMfCzTmxGU554buMHNnPlwoRSQemb5 PpIkPoQd7p+e4hD96tSdsWq4uNWF71Utx7AXJgP8SEXbNXQ7quTdig/vNe2slaV258y5tpyw OhQpniohnQpRkSRLFJEvVbHGDm432D8cdN8MFfEn0YWqMMe0xqLzwQF+KQ9yBLGtS8APsRBU wQUYJARIUIXMY5US8jA4EEzIv3uSicFBmon+69Fx73yvAIqyWTHbsFkxFCQd/tRDzYEyM+A5 NtzH1yOSlfeFUr/k/PwOPjPh+cXz5371ovhs60K9qLgfoP1xq3qhVVx49ldoQ3VCBPAKSx3e qvAByj59+wi//w7eDMpjLD2PGBh+awb8b8WANaaVE1ttqIQairyImnbF2KuY4fpJ4hzqiHy4 TH6UQ38UNfATDRTDZrrTVgplZFBYEs58mh1XXeIvpEqyIcjSjIV0qeEFYYYjTrlVMVyPAf9H tDw6OeuN9ge97jFRKCbDbWAiw39lxtSFA15kjmGhVdGx0SVDiwIzHYXWF4E709G+oVW6UZTK 8O3hYf89jpd4hYoBFZeUwoVoX5AexEpQRvvI1/jZy5jOvyfdcB0dEbnLRM+Kckvj6y8hfXFw 0j3AzdwbokUn+y/8/5vjtzP9ExtbNnsAH7PG/0NrtxX5/2arxf1/Q3vy/4/x4HZF98K1IGB+ APytDpYTlANPn/swnpd9azLVHRPGHmOXvkllR7cVuff24ta4E3AaR+M5voiO8CXqiiqjzrBA mzPdJe6deK/uFbb+pSiD/jF6nYJt2NgPL0k3tT1xFuxzwBCGuI6vRHYqAWUV6Vm392LnTIhE VaJdgJ/K9kxRIhHaEEvjhtK41L2Uop0QKEkg5G2Hcic//XDX3pQb85fM3iRx223a1SQzbxHK rkaTrHz5+ov9f9brHhz1vry3/GfN/tda9ez+r2vNJ/z/KM8/KtVI4f8BFlqAqcU8MC0GP+mL eeDrxhRR7uamcohb9fXwoK0kQbRojP5y7qLCVqZQhoXPxgsb/afhuX6aGOumlsOqFmMM9XfK +6WtxSZ8zCvLZG0lvw3tuMoUR99SYAvOsQSE9+FKtxeI+rFOt30XPjnutYNbFDg9WhzXA0ef MZCxBBJWcUeihcBO4Xx0etb/W//4cHAuVFGqZHUL5h6yYyNjJvaGjRdGgIaGWseNX5+ehy3x acSNLz2mf+JTsrpx96x//tP5WfdU+MC4sY6xz3TGKKoiITKthskhd+NW/o0fsBnJayDL7LPB 5stjnp6dJJr/JSmtGzDB5Fhf2EG62fnZfsQoTlItamayy8UkMVjRtww1M2T3TS8eUqvHQ+oT ljdYd9B/Ey0IaDvxvNjoJGYM5zRqlWh2gOt40AsnRnsRNUurV6It6d7YRuR3VUAlxjlzrizP 5SMoY1w1/7qgKCM0tBMWeGxSPDwdDc//7++js94btaMovVBqn9St8WK3rfxcOGB8kMsb+I15 rnKAFY7rzZD133BVMP7y0PcpJ4WTK+bh1rlW3hbeIvgU76eFvsM+60bwFez6fZ8o/8MdysOM scb+7zR3drL2v7X7ZP8f5fkhxE0bUgemG4oiLJaEGaNfZ/PLxThT2oN/KgDNEtSUW9wMV66F +HDODD0wpkWye4joVIVoUu0qvn7FzJF/jR2s3FoA1hiK6XYeMxaez04xOk5/sK2ZFajITWQK jk5hY2/vFbiXV5a78O0b2p+iPdmoMtorK7hwNhRSPhqJJ5uK9RK2LPm4Ud1xEV/VsqbCS6ip ilBTalWsI3s/LHjiBEmUqF7jbN8uiRuyvb3dUZY5PDztgUC+aBzK4LgB/LqYzdFPCfZWM5bi 4jYz/zT4l67BOl5/dZ3JH+H1B5FfODwd9s6x1XjuMZ8FPjq7TzfEwvvRwc/UQuQWAGwaB8VJ SyD+lLiAHZLfdBeXNkN/ROa3GJa0EoSvdTERYbGBy4GlBk6BqUEVv3dA6p3lW864aDZUlas4 5xEnc1z0AzTUXmkDiuOFw31lG86nEoEgdEI1wymzghsVNrg6AGpdsPAcqFVqoXqIERzd+UMj HOvHd3V+7342J9hNCTmglrIfmpNQk0yX8GCR3tPzpuGEaWLAaGaxqpauErO7YgMjdSeH13Pv htIu2HkVe4NKpSIFFYskF1YrmXU1rznRk7BSGtTRTVJMIWNarBE2TIhGG0XI1QlL9ZBJXvoC aULsoaFMGYG0KupcviB8VEQr3FzF8phJeRDYvJvqAQS4rFNmfIJr3ecFRJ4+oTjEvVSMsNn/ EOahnoUggoxbiZnuf4qnwuLSSg/gX48urcCXaspNys3s0rWFAhqIfbC/KfrPLcLYnYgKG3Gd xA4+aK2P0lsA/BM7tBxUQ8sswUZc2CiBdluKSEwOmkrASUQBKaCeICF4VaLChixs8NJOgsRF jBWRUEGQvEiQkF3iNBthgdNorQQNTpURdUMF0U0j4qZWguO3gwG6wj9dDa0BX8+slg3ftWHz PSmUWH6uiagyRbD2atAB66XWoj/b26GN4obr5UsLfhQtZLX4gMtsfazwOOv7PT46fS9kR31t BfB8039e3TR5qDkh2/9bwNmIuyiBJS2csGrcydo+W9VjTmfZDvhEKLGtIwn4Ngo3hOX7uhM5 jqvYcVxJx0FSXmnbV3USUEMLpaZsMA2HW5Kzifss+qDRKN8a4931pPD/9GHGWJf/aWo5+L/+ hP8f44nw/0vcUpZbmb5SElUiK4t1ycobv8pPWjO0WL3IdrBwcGea2Q5YgF40UznTg6ms4gBx NJL5ptEoQZXJNr2KYKrAkxI1hn34CyciGPV7vd5ot7mT6A1RWLIPAcs+q4Sy8E+ingAh1vf9 /vEh/yLHyY2TQkfKA5MQRIR4gcpXro1CoG3h/lRi8Q6Zj3eWbcMlg5mL3Vvo8y9vJOYGypnb iCS4ccGRRjSUGLHDIzDKhaPBWR+6rYzWOndEEZ37IOzOMnjs5AMv4tdZzAhfSLySQgYJCBC5 +sihx25b+mOSPg/Y0Cg4qUPGyHqHqgMyLefjVNF0k92vQHfwrvv3Icx1H2F8AHVEoHTi8aJS +z6Jm+5yE50/tZ1f9Qj7Hx7WPMwY6+x/LSf/U6892f/HeO60/wmjnJMlUkTwYIkoQvcmCJNF MIDvVx8+EnCSlhiN8+GpNIUCewH/i4HBeI7+gN6LtWTcL9BlTtiZCTzTVSJUWxWOYWiF6FBC w/ywcrnpoYygcwNLQpUZEWN5ImD9HyRLOP0xrr1V/iPt2tNzvydh/8UJ/gOMscb+Nxq7tez9 j52dJ/z/KM/d+J+fmeb7hLwoYQ3G/9LI4Q86nzDXnMLdwgul7HWcfU44p4n8GPumvGwf3ZzR 2nBg+TrZ7ijp5gsbHTESZdjzUjLXMiUDpVVp+ZiJpTR6rhOVSJyA8HLePTX4hcNlqLcB3QsE LvAQAPi13RJcLgJw3DAXH/qdHE8nVKE47L85PO2VolBCpD1jZuIDHgmoEW+XCGyraq7funAO T0FeBEgj95AXSrysaNq1dR5IWLO5TYEiMsJ853kA1673CVH+zcz1ZD+rJ6axenGzs5+RdEWH O/kzfW0F0+w8r5hUis/y1yEDokjdkRZjq2U9ECsBRfEdNV5s3NzjFlWFPUQpceYvllOUs6Ie YORHZ1oZecKknMzp5beVbWKkIuNgkQUX7EYDpyK//LOufNrV+0ywGc0kwArt4ovZbEM/ccuA 5+3zVnL9Wn6F9eBR9pesyZeuSN5JlJyo1oqJchcZjlbat6yKr7c48XwkQe239rt/lkfiv8S9 zK8/xrrf/7SW8r+NnWbzCf89xhMmOYf9n3u4Bs1GK4XY8jChaVuXj5Inpg6sGftKmWKJ3iIU iEyP9MCdWcYoADQSptVZ9ZG7ztXf6h1KBdPPBIBnO+VWSl/BkGH92HUTJ+WXuidAguuirZd5 RVWMB/Q1UytOjDkx/lsVzXEeoKbENzA2KhslLWkjyaV8L7Lb2EpduiwzRPtrm5R4PtaPw4sx 97zPkecpRFKBhhKuJXVD5jYB3dOH8FbyCkHtA2nkx2SVtlS1Zc5r/Cw9XUcZFjN5IcFfzOJL CjJDbpFqeeRkrSA+nwbEoVozPElNlW47uSq3Anzn+MC+w68dCVg4Eu6dc8RXNrpJQKew4SEs 35WpY1icGIvO0+keoTsL/TzOzVItP++M3WN3cHZUClVT4EoWiEko9s/7R70zhD7dQQl+tAJx gCwYvZ6SzuPyhXdV7uYP+GRv70lGtwVrSYgR34BBSpV+2CQOWKikrsSDZ8yne5v87gppF1GH GIfrVy2FY+7N5VwoGpRBw/8Ex/NvwPLtN8Ik0v9nfobxdcdY7/+bGf+/06g/3f98lOee5795 mZ21rj7Xq3OFS9Mt+eqErxVuNeVyqYA4f3St+6Mp85iwnNkm0vmO8L/VHw3XZJ3Qd4d3nqyJ 4WKQ8jkk4e+xi6e28jQ29PAlXkmdlXJ62fKNOU9HJX0uXaeUvfxb9ydhSXy6WgqhqBQxksAQ iYc1QkqAGZsZ85vijwmxkF9jTm6BD8g5TYZKvK/bSPToDNidB9ERsHDg4SXCzgoHnzjVEN7e tc0oByffswm3peTcyeEgr1rm7NKhIMb20tnhFKPWbKnyXbg1YbSzB+nc2CfSJasD8lUhuDiJ ofk5eD0YHXXfq7CVqVgVmgt/0U6fyWQ61So1tSpe6Q7Sv9nVPfIu/yvv9aJyzul3saXsBcRU 6iV2j1mtTNwPC6Fd3nDRjyiABkMbwCEKv8y4iWNzBRYF2iUF0UlJKnuqTKRhhSqPzmTWJoQD fHNwRU/sABWqYS2/MwAWvEJ7Ala5nHuHDeBvPOnRhtrnzdqL95yvQsmif4rcIGypqS2mqogm 8GvulbRvnpQQ/j/xG80HGGOd/9dqyd//if//x9Pv/x7nudv/5/j6u85/vkb0/0di+twToiUn lMkppk6BVrmf5QjOwt3vzD/T5efAc206RRC2gN+mTXSQiAXDCD3b3xES0pUk6cWWzxP+lfRv 2dbH9+Qip2l0EYD+xwbhsOl0aRzHrj9/yHQeQxuRBSd/Eg6yfCRB5Zyf9OBqNPM+Zm/e/4kz 5vvubL4g5ERZbrqez7yZ5egB/wHNUjo97eJS+fQ1ee7lZPuxe529OBim2ZOLkRU/29FJ9Asq f+FdWVfMDFt+e8f19Dw9T88XP/8PBUqK7ABQAAA= --LpQ9ahxlCli8rRTG-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 05:42:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23165 for freebsd-current-outgoing; Wed, 26 Aug 1998 05:42:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23133 for ; Wed, 26 Aug 1998 05:42:00 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id IAA26260; Wed, 26 Aug 1998 08:41:09 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: wwoods@cybcon.com cc: FreebSD Current From: "Gary Palmer" Subject: Re: Todays cvsup....... In-reply-to: Your message of "Wed, 26 Aug 1998 04:38:17 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Aug 1998 08:41:09 -0400 Message-ID: <26256.904135269@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG William Woods wrote in message ID : > While Makeing world this morn.......... Whoops I think that was my fault. There was a space where there shouldn't have been. I just commited a fix, so let me know if you are still having problems. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 05:42:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23246 for freebsd-current-outgoing; Wed, 26 Aug 1998 05:42:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23241 for ; Wed, 26 Aug 1998 05:42:49 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id IAA04095 for current@freebsd.org; Wed, 26 Aug 1998 08:35:48 -0400 (EDT) (envelope-from luoqi) Date: Wed, 26 Aug 1998 08:35:48 -0400 (EDT) From: Luoqi Chen Message-Id: <199808261235.IAA04095@lor.watermarkgroup.com> To: current@FreeBSD.ORG Subject: possible race window for getblk? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In function getblk(), there is a check after getnewbuf() call to make sure there is no other buffer created when getnewbuf() is blocked: (vfs_bio.c) if ((bp = getnewbuf(vp, blkno, slpflag, slptimeo, size, maxsize)) == 0) { if (slpflag || slptimeo) { splx(s); return NULL; } goto loop; } /* * This code is used to make sure that a buffer is not * created while the getnewbuf routine is blocked. * Normally the vnode is locked so this isn't a problem. * VBLK type I/O requests, however, don't lock the vnode. */ if (!VOP_ISLOCKED(vp) && gbincore(vp, blkno)) { bp->b_flags |= B_INVAL; brelse(bp); goto loop; } The problem with this check is, reads only hold shared lock on the vnode, thus the vnode lock won't prevent two reads from successfully creating two new buffers at the same block offset. This check should be extended to shared lock: if (VOP_ISLOCKED(vp) != LK_EXCLUSIVE && gbincore(vp, blkno)) { bp->b_flags |= B_INVAL; brelse(bp); goto loop; } -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 05:43:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23335 for freebsd-current-outgoing; Wed, 26 Aug 1998 05:43:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23330 for ; Wed, 26 Aug 1998 05:43:54 -0700 (PDT) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id OAA21218; Wed, 26 Aug 1998 14:43:03 +0200 (MET DST) Message-ID: <19980826144302.C20511@cons.org> Date: Wed, 26 Aug 1998 14:43:02 +0200 From: Martin Cracauer To: Stephen Hocking-Senior Programmer PGS Tensor Perth , current@FreeBSD.ORG Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops References: <199808250753.PAA29567@ariadne.tensor.pgs.com> <19980825180559.A9890@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <19980825180559.A9890@cons.org>; from Martin Cracauer on Tue, Aug 25, 1998 at 06:05:59PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <19980825180559.A9890@cons.org>, Martin Cracauer wrote: > In <199808250753.PAA29567@ariadne.tensor.pgs.com>, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > > > I've noticed in one of my applications that the first FP operation after > > return from a caught SIGFPE is invalid. I have a signal handler installed that > > just prints out some basic info (like "SIGFPE caught"). The first FP op after > > this (in my case, converting a long to a double) just gives garbage. Repeat > > the same statement and it gives a sensible result. Has anyone else seen this > > before I file a PR with code to reproduce the problem? > > I just did a short test and for me the next FP operation after a > caught SIGFPE (division by zero) is still sane (without > setjump/jumpjump). I'm afraid I was talking nonsense here :-( This test program shows the problem. Now the question, why did my other test work well...? #include #include #include void handler(int s) { write(1, "sig\n", 4); } int main(void) { double f0; double f2; double f4; double f8; double res; /* Prevent optimization */ f0 = atof("0.0"); f2 = atof("2.0"); f4 = atof("4.0"); f8 = atof("8.0"); signal (SIGFPE, handler); res = f2 / f0; printf("After division by zero: %g\n", res); res = f4 + f8; if (res != 12.0) { printf("Next operation didn't work: %g\n", res); } else { printf("Next operation worked: %g\n", res); } return 0; } -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 05:46:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23912 for freebsd-current-outgoing; Wed, 26 Aug 1998 05:46:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23878; Wed, 26 Aug 1998 05:46:25 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from support1.cybcon.com (william@support1.cybcon.com [205.147.76.99]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id FAA23093; Wed, 26 Aug 1998 05:45:31 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <26256.904135269@gjp.erols.com> Date: Wed, 26 Aug 1998 05:45:26 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: Gary Palmer Subject: Re: Todays cvsup....... Cc: FreebSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thannks......Must say one thin.....You guys are DAMM GOOD.....you fix things so damm quick..... On 26-Aug-98 Gary Palmer wrote: > William Woods wrote in message ID > : >> While Makeing world this morn.......... > > Whoops > > I think that was my fault. There was a space where there shouldn't have been. > I just commited a fix, so let me know if you are still having problems. > > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info --------------------- William Woods Date: 26-Aug-98 / Time: 05:44:41 goto to: http//www.freebsd.org. --> FreeBSD 3.0 CURRENT <-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 06:14:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26856 for freebsd-current-outgoing; Wed, 26 Aug 1998 06:14:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26848 for ; Wed, 26 Aug 1998 06:14:52 -0700 (PDT) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id PAA21842; Wed, 26 Aug 1998 15:13:52 +0200 (MET DST) Message-ID: <19980826151352.A21229@cons.org> Date: Wed, 26 Aug 1998 15:13:52 +0200 From: Martin Cracauer To: Stephen Hocking-Senior Programmer PGS Tensor Perth , current@FreeBSD.ORG Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops References: <199808250753.PAA29567@ariadne.tensor.pgs.com> <19980825180559.A9890@cons.org> <19980826144302.C20511@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <19980826144302.C20511@cons.org>; from Martin Cracauer on Wed, Aug 26, 1998 at 02:43:02PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <19980826144302.C20511@cons.org>, Martin Cracauer wrote: > In <19980825180559.A9890@cons.org>, Martin Cracauer wrote: > > In <199808250753.PAA29567@ariadne.tensor.pgs.com>, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > > > > > I've noticed in one of my applications that the first FP operation after > > > return from a caught SIGFPE is invalid. I have a signal handler installed that > > > just prints out some basic info (like "SIGFPE caught"). The first FP op after > > > this (in my case, converting a long to a double) just gives garbage. Repeat > > > the same statement and it gives a sensible result. Has anyone else seen this > > > before I file a PR with code to reproduce the problem? > > > > I just did a short test and for me the next FP operation after a > > caught SIGFPE (division by zero) is still sane (without > > setjump/jumpjump). > > I'm afraid I was talking nonsense here :-( This test program shows the > problem. Now the question, why did my other test work well...? Arg, this code doesn't work because it is missing includes, please ignore it. Give me a break, I'll follow up with a useful example later. > #include > #include > #include > > void > handler(int s) > { > write(1, "sig\n", 4); > } > > int > main(void) > { > double f0; > double f2; > double f4; > double f8; > double res; > > /* Prevent optimization */ > f0 = atof("0.0"); > f2 = atof("2.0"); > f4 = atof("4.0"); > f8 = atof("8.0"); > > signal (SIGFPE, handler); > > res = f2 / f0; > > printf("After division by zero: %g\n", res); > > res = f4 + f8; > > if (res != 12.0) { > printf("Next operation didn't work: %g\n", res); > } > else { > printf("Next operation worked: %g\n", res); > } > > return 0; > } -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 06:17:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27208 for freebsd-current-outgoing; Wed, 26 Aug 1998 06:17:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tick.ssec.wisc.edu (tick.ssec.wisc.edu [144.92.108.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27183; Wed, 26 Aug 1998 06:17:18 -0700 (PDT) (envelope-from dglo@tick.ssec.wisc.edu) Received: from tick.ssec.wisc.edu (localhost [127.0.0.1]) by tick.ssec.wisc.edu (8.8.7/8.8.7) with ESMTP id IAA26671; Wed, 26 Aug 1998 08:16:22 -0500 (CDT) From: Dave Glowacki Message-Id: <199808261316.IAA26671@tick.ssec.wisc.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: "Gary Palmer" , alexandr@mail.eecis.udel.edu, Paul Richards , "'Philippe Regnauld'" , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-reply-to: Your message of "Tue, 25 Aug 1998 20:41:22 PDT." <24733.904102882@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Aug 1998 08:16:21 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I don't know of enough PPC machines to make it worthwhile doing a port. At > > Macintoshes. iMACs especially. :) Not to put a damper on this, but... According to http://www.macosrumors.com/OSX.html MacOS X will already have a version of BSD built in and a command line interface will be available. Given that (and assuming the performance is somewhat decent), how likely would people be to trade access to MacOS applications for access to an open source OS? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 06:27:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28521 for freebsd-current-outgoing; Wed, 26 Aug 1998 06:27:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28515 for ; Wed, 26 Aug 1998 06:27:06 -0700 (PDT) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-10-45.camtech.net.au [203.28.1.173]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id WAA05680; Wed, 26 Aug 1998 22:55:21 +0930 (CST) Message-ID: <35E40C49.C673670C@camtech.net.au> Date: Wed, 26 Aug 1998 22:53:21 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: joelh@gnu.org CC: wosch@panke.de.freebsd.org, current@FreeBSD.ORG Subject: Re: file segment sizes of a core dump References: <199808231906.VAA04727@campa.panke.de> <35E18FF5.B7FADA7B@camtech.net.au> <19980824193728.B4111@panke.de> <199808251931.OAA00986@detlev.UUCP> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good point. Maybe a hybrid check which includes the /usr/share/misc/magic test and a check for the existance of the segments could be used. I dont know what segments are mandatory in a core file and it could be a truncated file so maybe this is not a good idea. Assuming the user knows what they are doing along with the magic test should be enough. Joel Ray Holveck wrote: > > >> Why require an option ? > >> Why not make size do what you want automatically when it detects > >> that you are running it on a core file ? > > How do you know that the file is a FreeBSD core file and not garbage? > > file(1) has a gross hack to identify core files, see /usr/share/misc/magic. > > Why would you run size on garbage? > > Best, > joelh > > -- > Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan > Fourth law of programming: > Anything that can go wrong wi > sendmail: segmentation violation - core dumped > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 06:31:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29212 for freebsd-current-outgoing; Wed, 26 Aug 1998 06:31:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29205; Wed, 26 Aug 1998 06:31:25 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from support1.cybcon.com (william@support1.cybcon.com [205.147.76.99]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id GAA24782; Wed, 26 Aug 1998 06:30:35 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <26256.904135269@gjp.erols.com> Date: Wed, 26 Aug 1998 06:30:31 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: Gary Palmer Subject: Re: Todays cvsup....... Cc: FreebSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think that was my fault. There was a space where there shouldn't have been. > I just commited a fix, so let me know if you are still having problems. > > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info > Just finished trying again Gary, and now this... ----------------------------------------- ===> sys/i386/boot/cdboot rm -f boot.img boot.nohdr boot.strip machine boot start.o table.o boot2.o boot.o asm.o bios.o serial.o probe_keyboard.o io.o cdrom.o malloc.o rm -f .depend /usr/local/src/sys/i386/boot/cdboot/GRTAGS /usr/local/src/sys/i386/boot/cdboot/GSYMS /usr/local/src/sys/i386/boot/cdboot/GTAGS ===> sys/i386/boot/dosboot rm -f fbsdboot.exe machine ===> sys/i386/boot/kzipboot rm -f machine kztail.o kzhead.o tail.o head.o boot.o unzip.o misc.o malloc.o inflate.o rm -f .depend /usr/local/src/sys/i386/boot/kzipboot/GRTAGS /usr/local/src/sys/i386/boot/kzipboot/GSYMS /usr/local/src/sys/i386/boot/kzipboot/GTAGS ===> sys/i386/boot/netboot rm -f netboot.com makerom start2.ro 3c509.o ns8390.o machine nb8390.com nb3c509.com nb8390.rom nb3c509.rom start2.o main.o misc.o bootmenu.o rpc.o netboot.8.gz netboot.8.cat.gz rm -f .depend /usr/local/src/sys/i386/boot/netboot/GRTAGS /usr/local/src/sys/i386/boot/netboot/GSYMS /usr/local/src/sys/i386/boot/netboot/GTAGS ===> sys/i386/boot/rawboot rm -f boot.nohdr boot.strip rawboot sizetest machine boot start.o table.o boot2.o boot.o asm.o bios.o serial.o probe_keyboard.o io.o disk.o sys.o rm -f .depend /usr/local/src/sys/i386/boot/rawboot/GRTAGS /usr/local/src/sys/i386/boot/rawboot/GSYMS /usr/local/src/sys/i386/boot/rawboot/GTAGS ===> usr.bin "Makefile", line 28: Unassociated shell command "kdump key keyinfo keyinit keylogin keylogout killall ktrace kzip lam last lastcomm leave lex limits locate lock lockf logger login logname look lorder lsvfs m4 mail make mesg mkdep mkfifo mklocale mkstr mktemp mk_cmds more msgs ncal netstat newkey nfsstat nice nohup objformat opieinfo opiekey opiepasswd pagesize passwd paste pr printenv printf quota rdist renice rev rlogin rpcgen rpcinfo rs rsh rup ruptime rusers rwall rwho script sed shar showmount soelim split su symorder tail talk tconv tcopy tee tftp time tip tn3270 top touch tput tr true tset tsort tty ul uname unexpand unifdef uniq units unvis users uudecode uuencode vacation vgrind vi vis w wall wc what whereis which who whois window write xargs xinstall xlint xstr yacc yes ypcat ypmatch ypwhich" make: fatal errors encountered -- cannot continue *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 -------------------------------------------- --------------------- William Woods Date: 26-Aug-98 / Time: 06:29:10 goto to: http//www.freebsd.org. --> FreeBSD 3.0 CURRENT <-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 06:37:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00228 for freebsd-current-outgoing; Wed, 26 Aug 1998 06:37:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00214 for ; Wed, 26 Aug 1998 06:37:50 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id JAA27013; Wed, 26 Aug 1998 09:36:59 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: wwoods@cybcon.com cc: FreebSD Current From: "Gary Palmer" Subject: Re: Todays cvsup....... In-reply-to: Your message of "Wed, 26 Aug 1998 06:30:31 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Aug 1998 09:36:59 -0400 Message-ID: <27009.904138619@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG William Woods wrote in message ID : > Just finished trying again Gary, and now this... It can take up to 4 hours for the changes to propogate to the CVSUP mirrors. A machine at work is doing a build as I type to test. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 06:43:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01077 for freebsd-current-outgoing; Wed, 26 Aug 1998 06:43:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01044 for ; Wed, 26 Aug 1998 06:43:31 -0700 (PDT) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id PAA22425; Wed, 26 Aug 1998 15:42:41 +0200 (MET DST) Message-ID: <19980826154241.A22184@cons.org> Date: Wed, 26 Aug 1998 15:42:41 +0200 From: Martin Cracauer To: Bruce Evans , current@FreeBSD.ORG, luoqi@watermarkgroup.com, shocking@prth.pgs.com Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops References: <199808252351.JAA32306@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808252351.JAA32306@godzilla.zeta.org.au>; from Bruce Evans on Wed, Aug 26, 1998 at 09:51:57AM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199808252351.JAA32306@godzilla.zeta.org.au>, Bruce Evans wrote: > 2) if the SIGFPE was for an FP operation, then the FP operatation will be > restarted. The kernel has cleared the trap-pending flag before delivering > the SIGFPE to the application, and on i386's traps are delivered to the > kernel on the the first non-control FP operation after the one that > caused the exception, so it is certain that the restarted FP operation > won't trap; it may cause an exception which will be delivered to the > kernel on the next non-control FP operation. I'm not able to reproduce this behaviour. I wrote a short test program that runs like this: Trying to trigger a FPE and see if FP still works afterwards. First round - FPE-causing operation and then a non-exception operation. Operation caused exception -> right. Next operation after fpe worked and gave correct result -> right. Second round - directly following FPE-causing operations. First operation caused exception -> right. Second operation caused exception -> right >From your description, I would expect the next FP operating after a caught FPE exception to fail. Either by issuing a wrong result, by not troughing FPE where it should or throughing one where it shouldn't. Here's what I do. Don't compile this with optimization, my actions against it aren't sufficient. #include #include #include #include volatile sig_atomic_t fpe_was_here = 0; static void handler(int s) { fpe_was_here++; write(2, "sig\n", 4); } /* Don't use printf, it uses floating point */ #define TO_STDERR(arg) write(2, arg, sizeof(arg)) int main(void) { double f0; double f2; double f4; double f8; double res; double old_res; int old_fpe_was_here; double killopt = 0.0; /* Prevent optimization */ f0 = atof("0.0"); f2 = atof("2.0"); f4 = atof("4.0"); f8 = atof("8.0"); TO_STDERR("Trying to trigger a FPE and see if FP still works afterwards.\n"); TO_STDERR("\nFirst round - FPE-causing operation and then a non-exception " "operation.\n"); signal(SIGFPE, handler); res = f2 / f0; killopt += res; if (fpe_was_here) { TO_STDERR("Operation caused exception -> right.\n"); fpe_was_here--; } else { TO_STDERR("Operation works fine -> wrong.\n"); } if (fpe_was_here) { TO_STDERR("Aehm, what?\n"); exit(1); } res = f4 + f8; killopt += res; if (fpe_was_here) { TO_STDERR("Next normal operation caused exception -> wrong.\n"); fpe_was_here--; } if (res != 12.0) { TO_STDERR("Next operation gave wrong result :-(\n"); } else { TO_STDERR("Next operation after fpe worked and gave correct result " "-> right.\n"); } TO_STDERR("\nSecond round - directly following FPE-causing operations.\n"); old_res = f2 / f0; /* Don't do a any output here to keep Schroedinger happy */ old_fpe_was_here = fpe_was_here; fpe_was_here--; res = f2 / f0; killopt += old_res; killopt += res; if (old_fpe_was_here) { TO_STDERR("First operation caused exception -> right.\n"); old_fpe_was_here--; } else { TO_STDERR("First operation works fine -> wrong.\n"); } if (old_fpe_was_here) { TO_STDERR("Aehm, what?\n"); exit(1); } if (fpe_was_here) { TO_STDERR("Second operation caused exception -> right\n"); fpe_was_here--; } else { TO_STDERR("Second operation works fine -> wrong\n"); } if (fpe_was_here) { TO_STDERR("Aehm, what?\n"); exit(1); } fprintf(stderr,"For the record and against the optimizer: %g\n", killopt); return 0; } -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 07:09:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04626 for freebsd-current-outgoing; Wed, 26 Aug 1998 07:09:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04621 for ; Wed, 26 Aug 1998 07:09:40 -0700 (PDT) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id QAA22563; Wed, 26 Aug 1998 16:08:46 +0200 (MET DST) Message-ID: <19980826160845.B22184@cons.org> Date: Wed, 26 Aug 1998 16:08:45 +0200 From: Martin Cracauer To: Bruce Evans , current@FreeBSD.ORG, luoqi@watermarkgroup.com, shocking@prth.pgs.com Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops References: <199808252351.JAA32306@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808252351.JAA32306@godzilla.zeta.org.au>; from Bruce Evans on Wed, Aug 26, 1998 at 09:51:57AM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199808252351.JAA32306@godzilla.zeta.org.au>, Bruce Evans wrote: > 1) First decide if the exception is for FP or integer division by 0, by > looking at the trap code. FreeBSD's support for trap codes is > primitive and unportable (see ), but probably good > enough to distinguish integer division by zero. Ah, now I got it. If sig == SIGFPE, then expect the trap code to be one of FPE_*_TRAP values from machine/trap.h, *not* one of the T_* values. Why is this, why two classes of trap codes? [ For those who missed the discussion so far: The trap is the second argument to a signal handler. Define it like static int handler(int sig, int code, struct sigcontext *scp) ] Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 07:11:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04928 for freebsd-current-outgoing; Wed, 26 Aug 1998 07:11:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tyree.iii.co.uk (tyree.iii.co.uk [195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04909; Wed, 26 Aug 1998 07:11:24 -0700 (PDT) (envelope-from nik@iii.co.uk) From: nik@iii.co.uk Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id PAA02467; Wed, 26 Aug 1998 15:10:33 +0100 (BST) Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.8/8.8.7) id PAA11390; Wed, 26 Aug 1998 15:09:36 +0100 (BST) Message-ID: <19980826150935.A11363@iii.co.uk> Date: Wed, 26 Aug 1998 15:09:35 +0100 To: Terry Lambert , Paul Richards Cc: gpalmer@FreeBSD.ORG, chuckr@Glue.umd.edu, freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors References: <199808260152.SAA00704@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808260152.SAA00704@usr04.primenet.com>; from Terry Lambert on Wed, Aug 26, 1998 at 01:52:16AM +0000 Organization: interactive investor Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 26, 1998 at 01:52:16AM +0000, Terry Lambert wrote: > > Hotmail are apparently dropping FreeBSD in favour of Solaris because of > > thread support as well :-( > > HotMail is using Solaris for the back-end data store, yes. > > But they are still using FreeBSD for the WWW Server front-end. I'll cheerfully shout this from the rooftops. But I need a better cite than that. I can't go around saying "Terry Lambert says that Hotmail are still using FreeBSD for the webservers" if Sun (or others) are saying that they're using Solaris. Something from either Sun, or someone from Hotmail, would do quite nicely. Otherwise it just descends into mindless advocacy. N -- --+==[ Nik Clayton becomes Just Another Perl Contractor in 17 days. ]==+-- She's still dead. Deal with it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 07:42:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10108 for freebsd-current-outgoing; Wed, 26 Aug 1998 07:42:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10085 for ; Wed, 26 Aug 1998 07:42:30 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA05337; Wed, 26 Aug 1998 10:41:33 -0400 (EDT) (envelope-from wollman) Date: Wed, 26 Aug 1998 10:41:33 -0400 (EDT) From: Garrett Wollman Message-Id: <199808261441.KAA05337@khavrinen.lcs.mit.edu> To: dyson@iquest.net Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), dfr@nlsystems.com, current@FreeBSD.ORG Subject: Re: Serious bug in vm_page.h in current In-Reply-To: <199808260140.UAA00967@dyson.iquest.net> References: <199808260001.UAA03536@khavrinen.lcs.mit.edu> <199808260140.UAA00967@dyson.iquest.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Garrett Wollman said: >> newsswitch has been up for more than nine hours now, which is longer >> than it had been lasting. I'll give it a full day before proclaiming >> success, though. > Yep, I did provide some info to Matt about this a few days ago, and I > suspect that we would let me know if there were NEW problems. If this > fixes it, it is indeed amazing how subtile some parts of the system > are. It didn't fix it, but the machine did stay up for fourteen hours, which is a lot longer than it has lasted in recent history. (Usually it deadlocks in less than six hours.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 07:49:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11203 for freebsd-current-outgoing; Wed, 26 Aug 1998 07:49:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11198 for ; Wed, 26 Aug 1998 07:49:52 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id JAA10432; Wed, 26 Aug 1998 09:48:47 -0500 (EST) (envelope-from toor) Message-Id: <199808261448.JAA10432@dyson.iquest.net> Subject: Re: Serious bug in vm_page.h in current In-Reply-To: <199808261441.KAA05337@khavrinen.lcs.mit.edu> from Garrett Wollman at "Aug 26, 98 10:41:33 am" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Wed, 26 Aug 1998 09:48:47 -0500 (EST) Cc: dyson@iquest.net, wollman@khavrinen.lcs.mit.edu, dfr@nlsystems.com, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman said: > > >> newsswitch has been up for more than nine hours now, which is longer > >> than it had been lasting. I'll give it a full day before proclaiming > >> success, though. > > > Yep, I did provide some info to Matt about this a few days ago, and I > > suspect that we would let me know if there were NEW problems. If this > > fixes it, it is indeed amazing how subtile some parts of the system > > are. > > It didn't fix it, but the machine did stay up for fourteen hours, > which is a lot longer than it has lasted in recent history. (Usually > it deadlocks in less than six hours.) > It is possible that the additional wakeups just jarred the system back awake. I suspect that there is still a window condition somewhere. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 08:14:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16970 for freebsd-current-outgoing; Wed, 26 Aug 1998 08:14:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tor-dev1.nbc.netcom.ca (tor-dev1.nbc.netcom.ca [207.181.89.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16956 for ; Wed, 26 Aug 1998 08:14:52 -0700 (PDT) (envelope-from taob@tor-dev1.nbc.netcom.ca) Received: (from taob@localhost) by tor-dev1.nbc.netcom.ca (8.8.8/8.8.8) id LAA16472; Wed, 26 Aug 1998 11:13:59 -0400 (EDT) Date: Wed, 26 Aug 1998 11:13:58 -0400 (EDT) From: Brian Tao X-Sender: taob@tor-dev1.nbc.netcom.ca To: FREEBSD-CURRENT Subject: Missing termios.h output modes? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any reason why the ONLCR flag defined in , but not OCRNL? ssh2 requires OCRNL for its serial interface support. -- Brian Tao (BT300, taob@risc.org) "Though this be madness, yet there is method in't" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 09:49:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01368 for freebsd-current-outgoing; Wed, 26 Aug 1998 09:49:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01326 for ; Wed, 26 Aug 1998 09:49:32 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id JAA03343; Wed, 26 Aug 1998 09:48:27 -0700 (PDT) (envelope-from jdp) Message-Id: <199808261648.JAA03343@austin.polstra.com> To: jb@cimlogic.com.au Subject: Re: GNU Binutils? (Was: re: gcc 2.8) In-Reply-To: <199808260827.SAA02383@cimlogic.com.au> References: <199808260827.SAA02383@cimlogic.com.au> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Wed, 26 Aug 1998 09:48:27 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199808260827.SAA02383@cimlogic.com.au>, John Birrell wrote: > I think we should defer this until after 3.0 is released. Perhaps we > should consider /just/ after. Me too. We have too much to do for 3.0 already without mucking around in the tools. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 09:50:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01787 for freebsd-current-outgoing; Wed, 26 Aug 1998 09:50:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01770 for ; Wed, 26 Aug 1998 09:50:36 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id JAA03362; Wed, 26 Aug 1998 09:49:43 -0700 (PDT) (envelope-from jdp) Message-Id: <199808261649.JAA03362@austin.polstra.com> To: dfr@nlsystems.com Subject: Re: GNU Binutils? (Was: re: gcc 2.8) In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Wed, 26 Aug 1998 09:49:43 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Doug Rabson wrote: > I might commit the 2.9.1 version of alpha-opc.c. It has some fixes which > are necessary for building SimOS. On the other hand, maybe I will just > keep that change in my local tree for now. I'd prefer that you keep it in your local tree. Let's bring in 2.9.1 as a proper import when we have time to do it right. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 10:16:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06680 for freebsd-current-outgoing; Wed, 26 Aug 1998 10:16:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06675 for ; Wed, 26 Aug 1998 10:16:15 -0700 (PDT) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id NAA27820 for ; Wed, 26 Aug 1998 13:14:38 -0400 (EDT) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 26 Aug 1998 13:14:38 -0400 (EDT) From: "Alok K. Dhir" To: current@FreeBSD.ORG Subject: usr.bin/Makefile Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has an extra space at the end of line 27 which is causing 'make world' to fail.... Al To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 10:43:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10052 for freebsd-current-outgoing; Wed, 26 Aug 1998 10:43:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10035 for ; Wed, 26 Aug 1998 10:43:05 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id NAA00396; Wed, 26 Aug 1998 13:42:10 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: "Alok K. Dhir" cc: current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: usr.bin/Makefile In-reply-to: Your message of "Wed, 26 Aug 1998 13:14:38 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Aug 1998 13:42:10 -0400 Message-ID: <392.904153330@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Alok K. Dhir" wrote in message ID : > > Has an extra space at the end of line 27 which is causing 'make world' to > fail.... The fix was already commited and should be on the cvsup mirrors already, if not shortly. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 11:04:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14003 for freebsd-current-outgoing; Wed, 26 Aug 1998 11:04:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.video-collage.com (www.video-collage.com [206.15.171.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13980; Wed, 26 Aug 1998 11:04:47 -0700 (PDT) (envelope-from mi@xxx.video-collage.com) Received: from xxx.video-collage.com (mi@xxx.video-collage.com [199.232.254.68]) by www.video-collage.com (8.8.5/8.8.5) with ESMTP id OAA22178; Wed, 26 Aug 1998 14:02:35 -0400 (EDT) Received: (from mi@localhost) by xxx.video-collage.com (8.8.8/8.8.7) id OAA08562; Wed, 26 Aug 1998 14:03:54 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199808261803.OAA08562@xxx.video-collage.com> Subject: recovering disk To: questions@FreeBSD.ORG, current@FreeBSD.ORG Date: Wed, 26 Aug 1998 14:03:54 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16410 for freebsd-current-outgoing; Wed, 26 Aug 1998 11:16:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16404; Wed, 26 Aug 1998 11:16:18 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from support1.cybcon.com (william@support1.cybcon.com [205.147.76.99]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id LAA11772; Wed, 26 Aug 1998 11:15:28 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <392.904153330@gjp.erols.com> Date: Wed, 26 Aug 1998 11:15:24 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: Gary Palmer Subject: Re: usr.bin/Makefile Cc: current@FreeBSD.ORG, "Alok K. Dhir" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get my cvsups from cvsup.freebsd.org and it is not there yet. On 26-Aug-98 Gary Palmer wrote: > "Alok K. Dhir" wrote in message ID > : >> >> Has an extra space at the end of line 27 which is causing 'make world' to >> fail.... > > The fix was already commited and should be on the cvsup mirrors already, if > not shortly. > > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message --------------------- William Woods Date: 26-Aug-98 / Time: 11:14:52 goto to: http//www.freebsd.org. --> FreeBSD 3.0 CURRENT <-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 11:33:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19411 for freebsd-current-outgoing; Wed, 26 Aug 1998 11:33:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailgate.nortel.ca (mailgate.nortel.ca [192.58.194.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19371; Wed, 26 Aug 1998 11:33:06 -0700 (PDT) (envelope-from atrens@nortel.ca) Received: from zcars01t by mailgate; Wed, 26 Aug 1998 14:31:28 -0400 Received: from wmerh01q.ca.nortel.com by zcars01t; Wed, 26 Aug 1998 14:30:37 -0400 Received: from nortel.ca (atrens@nortel.ca@wmerh01q) by wmerh01q.ca.nortel.com with ESMTP (8.7.1/8.7.1) id OAA01966; Wed, 26 Aug 1998 14:30:36 -0400 (EDT) Message-ID: <35E4544B.562F7B32@nortel.ca> Date: Wed, 26 Aug 1998 14:30:35 -0400 From: "Andrew Atrens" Reply-To: "Andrew Atrens" Organization: Nortel Technologies ( formerly Bell-Northern Research ) X-Mailer: Mozilla 4.5b1 [en] (X11; I; HP-UX B.10.20 9000/778) X-Accept-Language: en To: sos@FreeBSD.ORG CC: current@FreeBSD.ORG Subject: Re: TESTERS WANTED for new ATAPI CD/CDR/CDRW driver. References: <199808141707.TAA00337@sos.freebsd.dk> MIME-version: 1.0 Content-type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id LAA19386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren, The file permissions on these are wrong - I can't access them. > 230- Connected to sos.freebsd.dk. > .. > ftp> cd /pub/ATAPI > 250 CWD command successful. > ftp> ls > 200 PORT command successful. > 150 Opening ASCII mode data connection for '/bin/ls'. > total 170 > -r-------- 1 300 10000 1648 Aug 14 17:03 README > -r-------- 1 300 10000 201 Aug 14 16:16 burnaudio.gz > -r-------- 1 300 10000 120 Aug 14 16:16 burndata.gz > -r-------- 1 300 10000 16606 Aug 14 16:16 cdd.gz > -r-------- 1 300 10000 43240 Aug 16 19:54 cdd_wormcontrol_src.tgz > -r-------- 1 300 10000 15007 Aug 14 19:59 new-files.tgz > -r-------- 1 300 10000 2105 Aug 14 16:16 sys-diffs.gz > -r-------- 1 300 10000 2840 Aug 14 16:16 wormcontrol.gz > > ftp> get README - > 200 PORT command successful. > 550 README: Permission denied. > ftp> ( Just bought a HP7200i and am itching to try it out! ) Cheers, Andrew. Søren Schmidt wrote: > > A workable snapshot is available on: > > ftp;//sos.freebsd.dk/pub/ATAPI/* > > >From the README: > > This is a snapshot of my work in progress on the new ATA/ATAPI subsystem. > Please dont distribute this, only use it for testing, as it is > alpha level code which is undergoing rapid changes. > > The main use of this snap is to test the support for ATAPI CD burners, > and the driver has been adapted to the old ATAPI system to serve only > this purpose. > > Both ATAPI CD-R & CD-RW drives are supported, and it has been tested > with a HP7200i and a BTC BCE621E (also sold under the KISS name). > The driver might scribble various messages on the console, but > most should be harmless diagnostics. As always YMMV. > > Install the new driver files new-files.tgz and apply the patches > in sys-diff, make a new entry in your configfile for the new > "acd" atapi device, config & make a new kernel. > > The acd driver uses the same devicemajor as the old wcd driver, so > you can reuse the /dev/*wcd* devices. However if you use DEVFS it > will register itself under the name /dev/*acd*. > > I have includes a modified version of "wormcontrol" that can talk > to the acd driver. It has two new commands "nextwriteable" that > tells the driver the next writeable block on a CDR/CDRW, used when > burning more that 1 track (for audio mostly). > > Example scripts for burning data & audio CD's are also included. > > The cd ripper program "cdd" is also here in a modified version > that can talk to the acd driver. > > Enjoy and let me know the results... > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end? > .. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 11:39:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20973 for freebsd-current-outgoing; Wed, 26 Aug 1998 11:39:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20556; Wed, 26 Aug 1998 11:37:52 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id NAA00584; Wed, 26 Aug 1998 13:32:46 -0400 (EDT) Date: Wed, 26 Aug 1998 13:32:46 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: ben@rosengart.com cc: Gary Palmer , alexandr@mail.eecis.udel.edu, Paul Richards , "'Philippe Regnauld'" , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Aug 1998, Snob Art Genre wrote: > On Tue, 25 Aug 1998, Gary Palmer wrote: > > > I don't know of enough PPC machines to make it worthwhile doing a port. At > > least in my experience SPARC's are more `available'. > > I'd give my eye teeth to be able to run FreeBSD on Macintoshes. I don't know if anyone else has noticed or not, but Apple has stopped doing insane marketing mistakes. They actually have put together some very nice machines lately. I'm not a Mac enthusiast, but I'm going to have to stop using them as an example of computer idiocy. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 11:45:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22616 for freebsd-current-outgoing; Wed, 26 Aug 1998 11:45:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22569 for ; Wed, 26 Aug 1998 11:45:07 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id OAA01185; Wed, 26 Aug 1998 14:44:14 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: wwoods@cybcon.com cc: current@FreeBSD.ORG, "Alok K. Dhir" From: "Gary Palmer" Subject: Re: usr.bin/Makefile In-reply-to: Your message of "Wed, 26 Aug 1998 11:15:24 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Aug 1998 14:44:13 -0400 Message-ID: <1181.904157053@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG William Woods wrote in message ID : > I get my cvsups from cvsup.freebsd.org and it is not there yet. Do you have rev 1.107? If not, it hasn't updated yet. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 11:47:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23240 for freebsd-current-outgoing; Wed, 26 Aug 1998 11:47:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA23179 for ; Wed, 26 Aug 1998 11:47:01 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 24089 invoked by uid 1000); 26 Aug 1998 19:48:05 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 26 Aug 1998 15:48:05 -0400 (EDT) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: freebsd-current@FreeBSD.ORG Subject: Mae buildworld breakage Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> sys/i386/boot/rawboot ===> usr.bin "/usr/src/3.0/src/usr.bin/Makefile", line 28: Unassociated shell command "kdump key keyinfo keyinit keylogin keylogout killall ktrace kzip lam last lastcomm leave lex limits locate lock lockf logger login logname look lorder lsvfs m4 mail make mesg mkdep mkfifo mklocale mkstr mktemp mk_cmds more msgs ncal netstat newkey nfsstat nice nohup objformat opieinfo opiekey opiepasswd pagesize passwd paste pr printenv printf quota rdist renice rev rlogin rpcgen rpcinfo rs rsh rup ruptime rusers rwall rwho script sed shar showmount soelim split su symorder tail talk tconv tcopy tee tftp time tip tn3270 top touch tput tr true tset tsort tty ul uname unexpand unifdef uniq units unvis users uudecode uuencode vacation vgrind vi vis w wall wc what whereis which who whois window write xargs xinstall xlint xstr yacc yes ypcat ypmatch ypwhich" make: fatal errors encountered -- cannot continue *** Error code 1 Hint: Look for extra spaces past \ in the line above.... Sincerely Yours, Shimon@Simon-Shapiro.ORG 770.265.7340 Simon Shapiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 11:53:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24438 for freebsd-current-outgoing; Wed, 26 Aug 1998 11:53:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24428 for ; Wed, 26 Aug 1998 11:53:50 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id UAA19802; Wed, 26 Aug 1998 20:52:24 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id UAA19508; Wed, 26 Aug 1998 20:50:45 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808261850.UAA19508@semyam.dinoco.de> To: Mikhail Teterin cc: current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: recovering disk In-reply-to: Your message of "Wed, 26 Aug 1998 14:03:54 EDT." <199808261803.OAA08562@xxx.video-collage.com> Date: Wed, 26 Aug 1998 20:50:44 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm wondering, if I can write a program which will: > 1) read /dev/rsd1 to > 2) find the beginning of the file-system partition and I did something similar on my brother's machine. Somehow it looked as if the Windows FAT partition overlapped the FreeBSD slice following it and overwrote it one some operation. Anyway, the disklabel was erased and no backup copy in any form of it was available. Thus I wrote a small programm which opened the slice and read every 8 KByte block (the block size of the filesystem's used) and checked them for being a superblock. I did the same for the cylinder group headers next to them. This is trivial to do. The comments in /usr/include/ ufs/ffs/fs.h should lead the way the the right information in there with a little bit of understanding how the filesystem is organized. This information I collected on paper and made my own conclusions from the contents of the superblock and the numbers and starts of the cylinder groups of where the filesystems itself starts. If you have two superblocks 8 KByte apart from each other (so being neighbours) the first one is 8 KByte from the start of the filesystem and the other one 16 KByte. That's the trivial case. I think one can do this with a program quite easily but I had neither time for debugging one nor did I want to trust any on this. Needless to say there were no current backup of the filesystems so a program giving bad numbers would have been fatal. > 3) write it out (all the way to the end) as a separate file, which Given you have the start and the probably size dd will do the rest if used on the slice. > 4) vn-mechanism will let me access and get to my files > ? Left as an exercise to the reader. I'd expect that to work w/o any surprises. > I'm quite sure my data is intact on the disk and it is only its beginning tha t's > hosed. Thanks in advance for your ideas and suggestions. Yours, If the start including first superblock is damaged you'll of course have to use fsck with one of the many alternative superblocks whose position you get if you do it the way I recovered the disklabel or have noted when you newfs'ed the filesystem. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 12:13:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26988 for freebsd-current-outgoing; Wed, 26 Aug 1998 12:13:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26966 for ; Wed, 26 Aug 1998 12:13:16 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id PAA127600; Wed, 26 Aug 1998 15:12:27 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <199808261316.IAA26671@tick.ssec.wisc.edu> References: Your message of "Tue, 25 Aug 1998 20:41:22 PDT." <24733.904102882@time.cdrom.com> Date: Wed, 26 Aug 1998 15:16:25 -0400 To: Dave Glowacki , "Jordan K. Hubbard" From: Garance A Drosihn Subject: Re: Threads across processors Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:16 AM -0500 8/26/98, Dave Glowacki wrote: >> > I don't know of enough PPC machines to make it worthwhile doing >> > a port. >> >> Macintoshes. iMACs especially. :) > > Not to put a damper on this, but... > > According to http://www.macosrumors.com/OSX.html MacOS X will already > have a version of BSD built in and a command line interface will be > available. > > Given that (and assuming the performance is somewhat decent), how > likely would people be to trade access to MacOS applications for > access to an open source OS? If a person bought a Mac to run MacOS, then there isn't much reason to think they'll rush to FreeBSD just because it is open source. They bought it to run Mac applications, and they will want to run Mac applications. Apple will have enough of a challange getting them interested in MacOS Ten (nee Rhapsody), never mind FreeBSD. However, you should ask the question from the opposite angle. Of people who want to run FreeBSD, how many of them might be willing to pay slightly more for hardware, if that gets them some fairly solid machine which isn't mired in the world of Intel hardware? Particularly if they need to run some freebsd-ish application on a laptop, where the PowerPC-based laptops can really outdo the Pentium-based laptops for performance. I'm all for nextstep/openstep/rhapsody/macOSten, having been a user of NeXTSTEP for many years. At the same time, I too am very interested in something like FreeBSD for G3's, assuming apple does not make that impossible. And while that will have a BSD-ish unix layer, it is clear that Apple is not concentrating on making the most perfect unix layer that the world has ever seen. Their priorities are elsewhere, they just like to have the unix layer as a base for the things they are concentrating on. I notice that OpenBSD is looking at the iMac (something about it having a "fixed" version of OpenFirmware -- although I don't know what issues that refers to), so I'm keeping an eye on that effort. I had assumed it was not likely that FreeBSD would have a PowerPC port, but if someone is keeping track of "votes/wishes", then I'm one of the people who would like to see it. Of course, maybe we want a different subject/thread for that wish-list discussion, and probably on a different mailing list as well. It's a cinch that today's freebsd-current is not running on PowerPC, whatever I might wish... :-) (and as long as this is running so long: Am I the only one who thinks of "Uncle Albert/Admiral Halsey" when seeing the subject for this thread? :-) --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 12:14:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27342 for freebsd-current-outgoing; Wed, 26 Aug 1998 12:14:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27321; Wed, 26 Aug 1998 12:14:38 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA24378; Wed, 26 Aug 1998 12:09:17 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdz24364; Wed Aug 26 19:09:10 1998 Date: Wed, 26 Aug 1998 12:09:00 -0700 (PDT) From: Julian Elischer To: Mikhail Teterin cc: questions@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: recovering disk In-Reply-To: <199808261803.OAA08562@xxx.video-collage.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG firstly fdisk partitions cannot start at 0 usually they start either at 1 or at 64 or at the beginning of the 2nd cylinder. how did you make that drive? different methids will have done differnt things. the fdisk was possibly still there.. if so, it was the disklabel that was gone.. this is likely because it appears to have complained about abad label rather than a bad MBR. julian On Wed, 26 Aug 1998, Mikhail Teterin wrote: > being my home directory. I also had "dumpon" set to save crash onto > the sd1s1b and suspect that this is the reason for this disaster... probably not.... > > sd1s1: type 0xa5, start 0, end = 4194057, size 4194058 ^^^ buzz! > sd1s1: C/H/S start 0/0/0 (4294967295) != start 0: invalid > sd1s1: C/H/S end 995/241/44 (10605407) != end 4194057: invalid > sd1s2: type 0x0, start 3804688384, end = 3314409471, size 3804688384 > sd1s2: C/H/S start 994/240/21 (10594692) != start 3804688384: invalid > sd1s2: C/H/S end 994/240/18 (10594689) != end 3314409471: invalid > sd1s3: type 0x0, start 0, end = 4294967295, size 0 > sd1s3: C/H/S start 0/240/0 (10559) != start 0: invalid > sd1s4: type 0xa5, start 1, end = 4193639, size 4193639 > sd1s4: C/H/S end 457/10/44 (4866619) != end 4193639: invalid > sd1: cannot find label (no disk label) > sd1s1: cannot find label (no disk label) > sd1: ILLEGAL REQUEST asc:21,0 Logical block address out > of range field replaceable unit: 3 sks:cf,2 > sd1s4: cannot find label (no disk label) > > I'm wondering, if I can write a program which will: > 1) read /dev/rsd1 to > 2) find the beginning of the file-system partition and > 3) write it out (all the way to the end) as a separate file, which > 4) vn-mechanism will let me access and get to my files > ? several people have written such programs before..... I guess we might find references in the archives.. if a good one exists we probably should check it in.. what order were the partitions? would a dump fit in the swap partition? > > Or may be a program can be written to wonder through the /dev/sd1, find the > correct parameters (with some human assistance/guessing) for fdisk and disklabel? > > I'm quite sure my data is intact on the disk and it is only its beginning that's > hosed. Thanks in advance for your ideas and suggestions. Yours, you can just look for the superblock backups unfortunatly, if the crash wrote a lot of data then it may have written over the first parts of the filesystem so we don;t know how much you will be able to recover.... > > -mi > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 12:23:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAB29053 for freebsd-current-outgoing; Wed, 26 Aug 1998 12:23:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.video-collage.com (www.video-collage.com [206.15.171.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29047 for ; Wed, 26 Aug 1998 12:23:34 -0700 (PDT) (envelope-from mi@xxx.video-collage.com) Received: from xxx.video-collage.com (mi@xxx.video-collage.com [199.232.254.68]) by www.video-collage.com (8.8.5/8.8.5) with ESMTP id PAA25581; Wed, 26 Aug 1998 15:21:22 -0400 (EDT) Received: (from mi@localhost) by xxx.video-collage.com (8.8.8/8.8.7) id PAA16299; Wed, 26 Aug 1998 15:22:37 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199808261922.PAA16299@xxx.video-collage.com> Subject: Re: recovering disk In-Reply-To: <199808261850.UAA19508@semyam.dinoco.de> from Stefan Eggers at "Aug 26, 98 08:50:44 pm" To: seggers@semyam.dinoco.de (Stefan Eggers) Date: Wed, 26 Aug 1998 15:22:37 -0400 (EDT) Cc: current@FreeBSD.ORG X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" 3) write it out (all the way to the end) as a separate file, which = =Given you have the start and the probably size dd will do the rest if =used on the slice. Indeed... => 4) vn-mechanism will let me access and get to my files => ? = =Left as an exercise to the reader. I'd expect that to work w/o any =surprises. => I'm quite sure my data is intact on the disk and it is only its =>beginning tha t's hosed. Thanks in advance for your ideas and =>suggestions. Yours, =If the start including first superblock is damaged you'll of course =have to use fsck with one of the many alternative superblocks whose =position you get if you do it the way I recovered the disklabel or =have noted when you newfs'ed the filesystem. Yes... Still, any chance I can re-create the partition table (with fdisk) and disklabel? Thanks a lot! -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 12:28:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29810 for freebsd-current-outgoing; Wed, 26 Aug 1998 12:28:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29735 for ; Wed, 26 Aug 1998 12:28:01 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id PAA01785; Wed, 26 Aug 1998 15:27:06 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: shimon@simon-shapiro.org cc: freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Mae buildworld breakage In-reply-to: Your message of "Wed, 26 Aug 1998 15:48:05 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Aug 1998 15:27:05 -0400 Message-ID: <1781.904159625@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Simon Shapiro wrote in message ID : > Hint: Look for extra spaces past \ in the line above.... Sigh. Fixed in rev 1.107 this morning. No idea why its not making it out to the mirrors. But its there. Honest Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 12:35:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01282 for freebsd-current-outgoing; Wed, 26 Aug 1998 12:35:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.video-collage.com (www.video-collage.com [206.15.171.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01261; Wed, 26 Aug 1998 12:35:30 -0700 (PDT) (envelope-from mi@xxx.video-collage.com) Received: from xxx.video-collage.com (mi@xxx.video-collage.com [199.232.254.68]) by www.video-collage.com (8.8.5/8.8.5) with ESMTP id PAA26064; Wed, 26 Aug 1998 15:33:18 -0400 (EDT) Received: (from mi@localhost) by xxx.video-collage.com (8.8.8/8.8.7) id PAA17500; Wed, 26 Aug 1998 15:34:37 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199808261934.PAA17500@xxx.video-collage.com> Subject: Re: recovering disk In-Reply-To: from Julian Elischer at "Aug 26, 98 12:09:00 pm" To: julian@whistle.com (Julian Elischer) Date: Wed, 26 Aug 1998 15:34:36 -0400 (EDT) Cc: questions@FreeBSD.ORG, current@FreeBSD.ORG X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15856 for freebsd-current-outgoing; Wed, 26 Aug 1998 13:54:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15798 for ; Wed, 26 Aug 1998 13:54:19 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id WAA16782; Wed, 26 Aug 1998 22:47:49 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id WAA26730; Wed, 26 Aug 1998 22:46:15 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808262046.WAA26730@semyam.dinoco.de> To: Mikhail Teterin cc: seggers@semyam.dinoco.de (Stefan Eggers), current@FreeBSD.ORG Subject: Re: recovering disk In-reply-to: Your message of "Wed, 26 Aug 1998 15:22:37 EDT." <199808261922.PAA16299@xxx.video-collage.com> Date: Wed, 26 Aug 1998 22:46:15 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Now the questions is how often this happens. Would it be worth to make an additional disklabel and - for systems having it - fdisk partition table recovery tool? How's the opinion on this?] > So, the first backup superblock is right next to the main one? Right. That's at least what I saw all the time when I used newfs. The main one is at sector 16 and the first alternative superblock ended up beging at sector 32. With default parameters the next one was 65536 sectors away but that changed with different parameters. I don't know how this gets calculated and would have to look at the code. > Ok. The disk was mounted at the time of the crash. Would not the > super blocks differ? The magic number is in the right place and the parameters are of course the same. What differs is the clean flag and maybe some other unimportant data. > So, how did you get it back? The start was clear from the two superblocks occuring in succession. The field fs_size in the superblock told me how large it was. That was fortunately all I needed. My alternative plan for recovery (in case the superblocks were not that clearly marking the filesystem start because the were over- written) was to take the distance between two cylinder group blocks (see /usr/include/ufs/ffs/fs.h) and the ordinal number of the blocks to calculate where cylinder group 0 would start, subtract from that two times the size of the superblocks and an additional 8 KByte which are reserved for the disklabel and don't get used by the FFS file- system code. Both I did with reading 8 KByte blocks and advancing 8 KByte. For other block sizes one will probably have to reduce it. I checked the magic numbers for the block and if it like either one extracted the information I needed. For the superblocks I choose fs_size and for the cylinder group blocks cg_cgx which is their ordinal number starting from 0 for the first one as far as I remem- ber. > Yes... Still, any chance I can re-create the partition table (with > fdisk) and disklabel? Once you found your filesystems you are probably able which ones were in the same disklabel. That's the disklabel. And as there is one disklabel per fdisk partition a little thinking should get you to the values for fdisk. I won't write it here as I most likely will get it wrong (it's nearly 11:00 p.m. here). The CHS information in the fdisk partition table is hard to get right by hand but I think fdisk can calculate them once you give it the correct BIOS geometry. As far as I know this is only used in the BIOS to locate the partition's boot block. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 13:58:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16906 for freebsd-current-outgoing; Wed, 26 Aug 1998 13:58:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16889 for ; Wed, 26 Aug 1998 13:58:08 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id NAA16582; Wed, 26 Aug 1998 13:57:19 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd016510; Wed Aug 26 13:57:15 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id NAA21770; Wed, 26 Aug 1998 13:57:11 -0700 (MST) From: Terry Lambert Message-Id: <199808262057.NAA21770@usr02.primenet.com> Subject: Re: GNU Binutils? (Was: re: gcc 2.8) To: garbanzo@hooked.net (Alex) Date: Wed, 26 Aug 1998 20:57:11 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: from "Alex" at Aug 25, 98 04:57:26 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Speaking of upgrading the compiler, what are the chances of upgrading the > binutils to 2.9.1 (at least for the ELF bits) in -current? I think the general consensus would be "yes, you can update "ld" and friends, if you first make them grok a.out". > Also, the building of gas from the -current sources seems to ignore CFLAGS > (and CXXFLAGS), but not CC/CXX. Should I open a pr for these and other > minor stuff like this? Don't set DESTDIR. Alternately, look at bsd.lib.mk and bsd.prog.mk, and specifically look at it with a critical eye on what it does to the include and library paths. The kludge for the includes, at least for the g++ from -ports, is: CXXINCLUDES+= -I/usr/local/lib/gcc-lib/i386-unknown-freebsd2.2.5/2.8.1/include The manifest variable agregation order is a bit different for gcc. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 14:27:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23454 for freebsd-current-outgoing; Wed, 26 Aug 1998 14:27:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23389; Wed, 26 Aug 1998 14:27:27 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA03393; Wed, 26 Aug 1998 14:26:30 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd003313; Wed Aug 26 14:26:27 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id OAA23229; Wed, 26 Aug 1998 14:26:18 -0700 (MST) From: Terry Lambert Message-Id: <199808262126.OAA23229@usr02.primenet.com> Subject: Re: Threads across processors To: nik@iii.co.uk Date: Wed, 26 Aug 1998 21:26:17 +0000 (GMT) Cc: tlambert@primenet.com, paul@originative.co.uk, gpalmer@FreeBSD.ORG, chuckr@Glue.umd.edu, freebsd-current@FreeBSD.ORG In-Reply-To: <19980826150935.A11363@iii.co.uk> from "nik@iii.co.uk" at Aug 26, 98 03:09:35 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Hotmail are apparently dropping FreeBSD in favour of Solaris because of > > > thread support as well :-( > > > > HotMail is using Solaris for the back-end data store, yes. > > > > But they are still using FreeBSD for the WWW Server front-end. > > I'll cheerfully shout this from the rooftops. But I need a better cite > than that. I can't go around saying "Terry Lambert says that Hotmail > are still using FreeBSD for the webservers" if Sun (or others) are > saying that they're using Solaris. > > Something from either Sun, or someone from Hotmail, would do quite > nicely. Otherwise it just descends into mindless advocacy. Start by asking support@hotmail.com Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 14:27:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23453 for freebsd-current-outgoing; Wed, 26 Aug 1998 14:27:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23204; Wed, 26 Aug 1998 14:26:58 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA03141; Wed, 26 Aug 1998 14:25:57 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd003008; Wed Aug 26 14:25:49 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id OAA23152; Wed, 26 Aug 1998 14:25:35 -0700 (MST) From: Terry Lambert Message-Id: <199808262125.OAA23152@usr02.primenet.com> Subject: Re: Threads across processors To: chuckr@glue.umd.edu (Chuck Robey) Date: Wed, 26 Aug 1998 21:25:35 +0000 (GMT) Cc: ben@rosengart.com, gpalmer@FreeBSD.ORG, alexandr@mail.eecis.udel.edu, paul@originative.co.uk, regnauld@deepo.prosa.dk, freebsd-current@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at Aug 26, 98 01:32:46 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't know if anyone else has noticed or not, but Apple has stopped > doing insane marketing mistakes. They actually have put together some > very nice machines lately. I'm not a Mac enthusiast, but I'm going to > have to stop using them as an example of computer idiocy. What about the insane marketing mistake of not documenting your hardware? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 14:29:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23947 for freebsd-current-outgoing; Wed, 26 Aug 1998 14:29:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23834 for ; Wed, 26 Aug 1998 14:28:54 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id XAA24325; Wed, 26 Aug 1998 23:24:48 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id XAA28041; Wed, 26 Aug 1998 23:23:07 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808262123.XAA28041@semyam.dinoco.de> To: Mikhail Teterin cc: julian@whistle.com (Julian Elischer), current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: recovering disk In-reply-to: Your message of "Wed, 26 Aug 1998 15:34:36 EDT." <199808261934.PAA17500@xxx.video-collage.com> Date: Wed, 26 Aug 1998 23:23:07 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > fdisk at all and proceed to the disklabel... So what should I do > instead of the plain: > > root@rtfm:/home/mi (108) disklabel -e sd1 > disklabel: ioctl DIOCGDINFO: Invalid argument How about "disklabel -r -e sd1s1" (if fdisk partition 4 - if it is the only one - ends up as slice 1) for a start? If it is thought of by the system as damaged or unlabled I think the best one can do is writing a new one with "disklabel -r -w sd1s1 auto" and then edit the data. One will loose the previous data in it, though. > Where is disklabel stored on the disk, can it be saved on top of > my filesystem (which, I think, starts about 64Mb from the beginning It is on top of the filesystem (if the filesystem starts at offset 0 in the slice) but the filesystem doesn't really start at the offset 0 then but leaves 8 KByte alone for boot blocks, disklabel and the like. And from what I read the disklabel area is unwriteable with normal means so even a filesystem like the Dos one which actually will start at the offset given (as far as I know) shouldn't be able to damage it. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 14:43:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26305 for freebsd-current-outgoing; Wed, 26 Aug 1998 14:43:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.video-collage.com (www.video-collage.com [206.15.171.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26286 for ; Wed, 26 Aug 1998 14:43:54 -0700 (PDT) (envelope-from mi@xxx.video-collage.com) Received: from xxx.video-collage.com (mi@xxx.video-collage.com [199.232.254.68]) by www.video-collage.com (8.8.5/8.8.5) with ESMTP id RAA00307; Wed, 26 Aug 1998 17:41:09 -0400 (EDT) Received: (from mi@localhost) by xxx.video-collage.com (8.8.8/8.8.7) id RAA29688; Wed, 26 Aug 1998 17:41:15 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199808262141.RAA29688@xxx.video-collage.com> Subject: Re: recovering disk In-Reply-To: <199808262123.XAA28041@semyam.dinoco.de> from Stefan Eggers at "Aug 26, 98 11:23:07 pm" To: seggers@semyam.dinoco.de (Stefan Eggers) Date: Wed, 26 Aug 1998 17:41:15 -0400 (EDT) Cc: julian@whistle.com, current@FreeBSD.ORG X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" fdisk at all and proceed to the disklabel... So what should I do => instead of the plain: => => root@rtfm:/home/mi (108) disklabel -e sd1 => disklabel: ioctl DIOCGDINFO: Invalid argument =How about "disklabel -r -e sd1s1" (if fdisk partition 4 - if it is the =only one - ends up as slice 1) for a start? =If it is thought of by the system as damaged or unlabled I think the =best one can do is writing a new one with "disklabel -r -w sd1s1 auto" =and then edit the data. One will loose the previous data in it, though. root@rtfm:/home/mi (112) disklabel -r sd1s1 disklabel: bad pack magic number (label is damaged, or pack is unlabeled) root@rtfm:/home/mi (113) disklabel -r -w sd1s1 auto disklabel: ioctl DIOCGDINFO: Invalid argument disklabel: auto: unknown disk type root@rtfm:/home/mi (114) disklabel -r -e sd1s1 disklabel: bad pack magic number (label is damaged, or pack is unlabeled) :-( Thanks! -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 15:13:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00971 for freebsd-current-outgoing; Wed, 26 Aug 1998 15:13:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00966 for ; Wed, 26 Aug 1998 15:13:00 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id IAA04734; Thu, 27 Aug 1998 08:22:52 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808262222.IAA04734@cimlogic.com.au> Subject: Re: GNU Binutils? (Was: re: gcc 2.8) In-Reply-To: <199808262057.NAA21770@usr02.primenet.com> from Terry Lambert at "Aug 26, 98 08:57:11 pm" To: tlambert@primenet.com (Terry Lambert) Date: Thu, 27 Aug 1998 08:22:52 +1000 (EST) Cc: garbanzo@hooked.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > Speaking of upgrading the compiler, what are the chances of upgrading the > > binutils to 2.9.1 (at least for the ELF bits) in -current? > > I think the general consensus would be "yes, you can update "ld" and > friends, if you first make them grok a.out". Umm, we're definitely going to 3.0 with elf. The decision has been made to leave the old aout tools for backward compatibility and *not* to add aout support to binutils. > > Also, the building of gas from the -current sources seems to ignore CFLAGS > > (and CXXFLAGS), but not CC/CXX. Should I open a pr for these and other > > minor stuff like this? If this is a gas build issue for the sources in the tree, it should be PR'd. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 15:21:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02251 for freebsd-current-outgoing; Wed, 26 Aug 1998 15:21:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02246 for ; Wed, 26 Aug 1998 15:21:52 -0700 (PDT) (envelope-from bright@www.hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id SAA21968; Wed, 26 Aug 1998 18:21:46 -0500 (EST) (envelope-from bright@www.hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 26 Aug 1998 18:21:46 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Mikhail Teterin cc: Stefan Eggers , julian@whistle.com, current@FreeBSD.ORG Subject: Re: recovering disk In-Reply-To: <199808262141.RAA29688@xxx.video-collage.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG are you using DEVFS? cause that's the same problems i get when trying to do a disklabel, although i can read my labels, as they are not hosed. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Wed, 26 Aug 1998, Mikhail Teterin wrote: > Stefan Eggers once stated: > > => fdisk at all and proceed to the disklabel... So what should I do > => instead of the plain: > => > => root@rtfm:/home/mi (108) disklabel -e sd1 > => disklabel: ioctl DIOCGDINFO: Invalid argument > > =How about "disklabel -r -e sd1s1" (if fdisk partition 4 - if it is the > =only one - ends up as slice 1) for a start? > > =If it is thought of by the system as damaged or unlabled I think the > =best one can do is writing a new one with "disklabel -r -w sd1s1 auto" > =and then edit the data. One will loose the previous data in it, though. > > root@rtfm:/home/mi (112) disklabel -r sd1s1 > disklabel: bad pack magic number (label is damaged, or pack is unlabeled) > root@rtfm:/home/mi (113) disklabel -r -w sd1s1 auto > disklabel: ioctl DIOCGDINFO: Invalid argument > disklabel: auto: unknown disk type > root@rtfm:/home/mi (114) disklabel -r -e sd1s1 > disklabel: bad pack magic number (label is damaged, or pack is unlabeled) > > :-( > > Thanks! > > -mi > > 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 Aug 26 15:25:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02876 for freebsd-current-outgoing; Wed, 26 Aug 1998 15:25:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02850 for ; Wed, 26 Aug 1998 15:25:21 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA13305 for freebsd-current@FreeBSD.ORG; Thu, 27 Aug 1998 00:24:31 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id A4A221459; Wed, 26 Aug 1998 23:55:31 +0200 (CEST) Date: Wed, 26 Aug 1998 23:55:31 +0200 From: Ollivier Robert To: FREEBSD-CURRENT Subject: Re: Missing termios.h output modes? Message-ID: <19980826235531.A19741@keltia.freenix.fr> Mail-Followup-To: FREEBSD-CURRENT References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i In-Reply-To: ; from Brian Tao on Wed, Aug 26, 1998 at 11:13:58AM -0400 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4590 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Brian Tao: > Any reason why the ONLCR flag defined in , but not > OCRNL? ssh2 requires OCRNL for its serial interface support. Because it is not implemented inside tty_compat.c ? :-) I stulbled upon the same problem with ssh2. Replacing OCRNL with 0 doesn't make it work better. The sshd2 binary eats 100% CPU while trying to connect to it... (there are some inconstitency with $etcdir handling with the Makefiles BTW). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #62: Mon Jul 27 20:47:08 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 15:54:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09022 for freebsd-current-outgoing; Wed, 26 Aug 1998 15:54:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09016 for ; Wed, 26 Aug 1998 15:54:49 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-110.camalott.com [208.229.74.110]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id RAA28950; Wed, 26 Aug 1998 17:55:15 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id RAA03247; Wed, 26 Aug 1998 17:53:23 -0500 (CDT) (envelope-from joelh) Date: Wed, 26 Aug 1998 17:53:23 -0500 (CDT) Message-Id: <199808262253.RAA03247@detlev.UUCP> To: thyerm@camtech.net.au CC: wosch@panke.de.freebsd.org, current@FreeBSD.ORG In-reply-to: <35E40C49.C673670C@camtech.net.au> (message from Matthew Thyer on Wed, 26 Aug 1998 22:53:21 +0930) Subject: Re: file segment sizes of a core dump From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808231906.VAA04727@campa.panke.de> <35E18FF5.B7FADA7B@camtech.net.au> <19980824193728.B4111@panke.de> <199808251931.OAA00986@detlev.UUCP> <35E40C49.C673670C@camtech.net.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> How do you know that the file is a FreeBSD core file and not garbage? >>> file(1) has a gross hack to identify core files, see /usr/share/misc/magic. >> Why would you run size on garbage? > Good point. > Maybe a hybrid check which includes the /usr/share/misc/magic test > and a check for the existance of the segments could be used. > I dont know what segments are mandatory in a core file and it could > be a truncated file so maybe this is not a good idea. > Assuming the user knows what they are doing along with the magic > test should be enough. I accept GIGO as a fact of life. I would vote against needing the switch. That's all I have to say on the topic. Any thoughts on examining the corefile for truncated segments, etc. are beyond what I feel like contemplating today. I will also add that I think this is a neat hack, and I am anxious to see it. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 16:36:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17667 for freebsd-current-outgoing; Wed, 26 Aug 1998 16:36:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17581 for ; Wed, 26 Aug 1998 16:35:58 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-110.camalott.com [208.229.74.110]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id SAA31896; Wed, 26 Aug 1998 18:36:42 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id SAA13309; Wed, 26 Aug 1998 18:34:54 -0500 (CDT) (envelope-from joelh) Date: Wed, 26 Aug 1998 18:34:54 -0500 (CDT) Message-Id: <199808262334.SAA13309@detlev.UUCP> To: seggers@semyam.dinoco.de CC: mi@video-collage.com, seggers@semyam.dinoco.de, current@FreeBSD.ORG In-reply-to: <199808262046.WAA26730@semyam.dinoco.de> (message from Stefan Eggers on Wed, 26 Aug 1998 22:46:15 +0200) Subject: Re: recovering disk From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808262046.WAA26730@semyam.dinoco.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [Now the questions is how often this happens. Would it be worth to > make an additional disklabel and - for systems having it - fdisk > partition table recovery tool? How's the opinion on this?] You know what I'd like? A general disk editor, that can take its input by the block or by the file, with a hex editor as well as some special-purpose viewers. Something like Norton's Disk Editor. Said tool has been amazingly useful to me on many an occasion. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 16:54:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20202 for freebsd-current-outgoing; Wed, 26 Aug 1998 16:54:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-67.ppp.wenet.net [206.15.84.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20195 for ; Wed, 26 Aug 1998 16:54:17 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id QAA01196; Wed, 26 Aug 1998 16:54:40 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Wed, 26 Aug 1998 16:54:39 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: GNU Binutils? (Was: re: gcc 2.8) In-Reply-To: <199808262057.NAA21770@usr02.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Aug 1998, Terry Lambert wrote: > > Speaking of upgrading the compiler, what are the chances of upgrading the > > binutils to 2.9.1 (at least for the ELF bits) in -current? > > I think the general consensus would be "yes, you can update "ld" and > friends, if you first make them grok a.out". Uh, the a.out tools are separate (at least they're in seperate dirs: src/gnu/usr.bin/binutils for 2.8.1, and IIRC src/libexec for the older stuff, and 'sides, I think that it was decided not to merge in a.out support into the newer binutils. I for one would really like to see the binutils stuff tracked more aggressively now that we've gotten a bit more up to date (esp if it fixes these odd seg faults I see). - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 17:12:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23136 for freebsd-current-outgoing; Wed, 26 Aug 1998 17:12:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23128; Wed, 26 Aug 1998 17:12:48 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from olvaldi.ifi.uio.no (2602@olvaldi.ifi.uio.no [129.240.65.43]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id AAA01621; Thu, 27 Aug 1998 00:03:39 +0200 (MET DST) Received: (from dag-erli@localhost) by olvaldi.ifi.uio.no ; Thu, 27 Aug 1998 00:03:39 +0200 (MET DST) Mime-Version: 1.0 To: Dave Glowacki Cc: "Jordan K. Hubbard" , "Gary Palmer" , alexandr@mail.eecis.udel.edu, Paul Richards , "'Philippe Regnauld'" , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors References: <199808261316.IAA26671@tick.ssec.wisc.edu> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 27 Aug 1998 00:03:38 +0200 In-Reply-To: Dave Glowacki's message of "Wed, 26 Aug 1998 08:16:21 -0500" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA23129 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dave Glowacki writes: > According to http://www.macosrumors.com/OSX.html MacOS X will already have > a version of BSD built in and a command line interface will be available. macosrumors.com make a living spreading startling but false news. Do you read the National Enquirer to get the latest on geopolitics? DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 17:29:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25805 for freebsd-current-outgoing; Wed, 26 Aug 1998 17:29:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25799 for ; Wed, 26 Aug 1998 17:28:59 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id KAA04047; Thu, 27 Aug 1998 10:27:48 +1000 Date: Thu, 27 Aug 1998 10:27:48 +1000 From: Bruce Evans Message-Id: <199808270027.KAA04047@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org, shocking@prth.pgs.com Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> OK, I've had a look at machine/trap.h, how do I go about getting info on >> exactly was exception was caused? A brief perusal of the man pages for math Have a look at the sources :-). >As far as I know, you can't. The kernel does not pass the FP registers >as they were in the mainline program flow to your signal handler. Erm, it does precisely that. This is why FP can't be used in signal handlers (any signal handler, not just SIGFPE handlers). CPU state that isn't inline is in `struct sigcontext'. >What we need here is a system call to ask the kernel for the FP >register contents which it should have saved before entering the FP >handler. If the user required so, by a system call, sysctl variable or >kernel config option. It can't be stored in the kernel because it might be nested millions of times deep for a nested signal. >I actually didn't beleive this :-) and wrote some code to get the Just as well :-). >registers via the "hidden" third parameter to a signal handler, but in >fact the exception indication bits were cleared. The exception bits are too well hidden. They probably should be in the sigcontext, but they only in the pcb_savefpu.sv_ex_sw in the pcb where they can only conveniently be got at by debuggers. Gdb fetches them from there. My version of npx.c has an option for controlling clearing of the exception bits. I found that the current behaviour is least suprising. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 19:46:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17341 for freebsd-current-outgoing; Wed, 26 Aug 1998 19:46:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA17278 for ; Wed, 26 Aug 1998 19:46:04 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zBs3g-0003az-00; Wed, 26 Aug 1998 19:45:08 -0700 Date: Wed, 26 Aug 1998 19:45:05 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= cc: freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id TAA17314 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27 Aug 1998, Dag-Erling Coidan [iso-8859-1] Smørgrav wrote: > Dave Glowacki writes: > > According to http://www.macosrumors.com/OSX.html MacOS X will already have > > a version of BSD built in and a command line interface will be available. > > macosrumors.com make a living spreading startling but false news. Do > you read the National Enquirer to get the latest on geopolitics? I wouldn't say that. First of all, the core of Rhapsody is BSD 4.4. This is positive. What isn't known, is how much Rhapsody will make it into OS X, or even what will happen to Rhapsody. People are running Rhapsody know. It has basically a full BSD like environment under a standard MacOS GUI. Cool stuff, but the current developer release (at least the one I've been allow to see) of Rhapsody has zero backwards compatibility stuff in it. There was even a Rhapsody port to x86 (imagin Mac GUI on Intel!), but Apple seems to have killed it. > DES > -- > Dag-Erling Smørgrav - dag-erli@ifi.uio.no Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 19:54:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18510 for freebsd-current-outgoing; Wed, 26 Aug 1998 19:54:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18505 for ; Wed, 26 Aug 1998 19:54:36 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA15661; Thu, 27 Aug 1998 12:53:36 +1000 Date: Thu, 27 Aug 1998 12:53:36 +1000 From: Bruce Evans Message-Id: <199808270253.MAA15661@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org, current@FreeBSD.ORG, luoqi@watermarkgroup.com, shocking@prth.pgs.com Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Ah, now I got it. > >If sig == SIGFPE, then expect the trap code to be one of FPE_*_TRAP >values from machine/trap.h, *not* one of the T_* values. Except this is not implemented. >Why is this, why two classes of trap codes? T_* is for the kernel and is unportable. FPE_* is for the user SIGFPE handler and is not so unportable in theory. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 20:58:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26207 for freebsd-current-outgoing; Wed, 26 Aug 1998 20:58:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26106 for ; Wed, 26 Aug 1998 20:57:59 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA20577; Thu, 27 Aug 1998 13:57:05 +1000 Date: Thu, 27 Aug 1998 13:57:05 +1000 From: Bruce Evans Message-Id: <199808270357.NAA20577@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, roberto@keltia.freenix.fr Subject: Re: Missing termios.h output modes? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Any reason why the ONLCR flag defined in , but not >> OCRNL? ssh2 requires OCRNL for its serial interface support. > >Because it is not implemented inside tty_compat.c ? :-) Because it is not implemented in tty.c. tty_compat.c implements compatibility cruft for the old tty interface. ONLCR is probably implemented because it corresponds to CRMOD in the old tty interface. OCRNL is probably unimplemented because there is no corresponding flag in the old tty interface. OPOST is the only output mode specifed by POSIX. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 21:31:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00497 for freebsd-current-outgoing; Wed, 26 Aug 1998 21:31:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00461 for ; Wed, 26 Aug 1998 21:31:28 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from ben by scientia.demon.co.uk with local (Exim 2.02 #20) id 0zBtfo-0005qg-00; Thu, 27 Aug 1998 05:28:36 +0100 Date: Thu, 27 Aug 1998 05:28:36 +0100 From: Ben Smithurst To: freebsd-current@FreeBSD.ORG Subject: Problems building -current Message-ID: <19980827052836.A22477@scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm currently trying to upgrade by FreeBSD 2.2.6-RELEASE box to -current, but with little success. I have a nasty feeling there's something obvious I've missed out. I've downloaded the full source tree using cvsup, but when I do a `make buildworld', I get the following errors: ---------- cc -O -pipe -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS -I/usr/obj/usr/src/tmp/usr/include -static -o gperf options.o iterator.o main.o perfect.o keylist.o listnode.o xmalloc.o hashtable.o boolarray.o readline.o stderr.o version.o getopt.o stderr.o: Undefined symbol `___error' referenced from text segment stderr.o: Undefined symbol `___error' referenced from text segment stderr.o: Undefined symbol `___error' referenced from text segment freopen.o: Undefined symbol `___error' referenced from text segment freopen.o: Undefined symbol `___error' referenced from text segment freopen.o: Undefined symbol `___error' referenced from text segment freopen.o: Undefined symbol `___error' referenced from text segment ungetc.o: Undefined symbol `_flockfile' referenced from text segment ungetc.o: Undefined symbol `_funlockfile' referenced from text segment ungetc.o: Undefined symbol `_funlockfile' referenced from text segment fputs.o: Undefined symbol `_flockfile' referenced from text segment fputs.o: Undefined symbol `_funlockfile' referenced from text segment strtol.o: Undefined symbol `___error' referenced from text segment refill.o: Undefined symbol `___error' referenced from text segment flags.o: More undefined symbol ___error refs follow fclose.o: Undefined symbol `_flockfile' referenced from text segment fclose.o: Undefined symbol `_funlockfile' referenced from text segment vfprintf.o: Undefined symbol `_flockfile' referenced from text segment vfprintf.o: Undefined symbol `_funlockfile' referenced from text segment vfprintf.o: Undefined symbol `_funlockfile' referenced from text segment vfprintf.o: Undefined symbol `_funlockfile' referenced from text segment fflush.o: Undefined symbol `_flockfile' referenced from text segment fflush.o: Undefined symbol `_funlockfile' referenced from text segment malloc.o: Undefined symbol `__spinlock' referenced from text segment malloc.o: Undefined symbol `__spinlock' referenced from text segment malloc.o: Undefined symbol `__spinlock' referenced from text segment *** Error code 1 Stop. ---------- Any ideas? Sorry if this is a basic question but I'm new to -current. Cheers, -- Ben Smithurst : ben@scientia.demon.co.uk : http://www.scientia.demon.co.uk/ PGP: 0x99392F7D - 3D 89 87 42 CE CA 93 4C 68 32 0E D5 36 05 3D 16 http://www.scientia.demon.co.uk/ben/pgp-key.html (or use keyservers) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 22:20:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08696 for freebsd-current-outgoing; Wed, 26 Aug 1998 22:20:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08691 for ; Wed, 26 Aug 1998 22:20:45 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id PAA05931; Thu, 27 Aug 1998 15:31:09 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808270531.PAA05931@cimlogic.com.au> Subject: Re: Problems building -current In-Reply-To: <19980827052836.A22477@scientia.demon.co.uk> from Ben Smithurst at "Aug 27, 98 05:28:36 am" To: ben@scientia.demon.co.uk (Ben Smithurst) Date: Thu, 27 Aug 1998 15:31:09 +1000 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Smithurst wrote: > I'm currently trying to upgrade by FreeBSD 2.2.6-RELEASE box to > -current, but with little success. I have a nasty feeling there's > something obvious I've missed out. make -m /usr/src/share/mk buildworld Your build is not linking against the library it has bootstrapped, but is getting the libc from /usr/lib instead. This is such a FAQ that I'm going to fix the makefile so that you can't get it wrong. 8-) -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 22:26:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09515 for freebsd-current-outgoing; Wed, 26 Aug 1998 22:26:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (castles320.castles.com [208.214.167.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09502 for ; Wed, 26 Aug 1998 22:26:48 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA01162; Tue, 25 Aug 1998 17:48:58 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808251748.RAA01162@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: Alex , current Subject: Re: MAXDOUBLE and values.h? In-reply-to: Your message of "Tue, 25 Aug 1998 17:39:21 GMT." <199808251739.RAA01034@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Aug 1998 17:48:57 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Ok, I've got a quick question. I've got an app which uses MAXDOUBLE, and > > includes values.h to get at it. values.h has a #warn that tells me it's > > depreciated. So I grep -R'd all the headers in /usr/include, and nothing > > else seemed to have a #define for MAXDOUBLE? Is this a mistake, or should > > MAXDOUBLE be avoided? > > You should use , and MAXDOUBLE will come out of the > machine-specific headers in Blah. I should think faster or type slower. MAXDOUBLE is deprecated. By including , you will implicitly include , which contains the approved (ANSI, POSIX, etc.) constants. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 23:10:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15115 for freebsd-current-outgoing; Wed, 26 Aug 1998 23:10:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15087 for ; Wed, 26 Aug 1998 23:10:41 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id IAA04302 for freebsd-current@FreeBSD.ORG; Thu, 27 Aug 1998 08:09:50 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id D38441459; Thu, 27 Aug 1998 07:45:00 +0200 (CEST) Date: Thu, 27 Aug 1998 07:45:00 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: Missing termios.h output modes? Message-ID: <19980827074500.A22588@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199808270357.NAA20577@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i In-Reply-To: <199808270357.NAA20577@godzilla.zeta.org.au>; from Bruce Evans on Thu, Aug 27, 1998 at 01:57:05PM +1000 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4590 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Bruce Evans: > OPOST is the only output mode specifed by POSIX. All the POSIXoides system I've checked (HP-UX, Solaris) have both OCRNL and ONLCR. Probably comes from "termio"... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #62: Mon Jul 27 20:47:08 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 26 23:58:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21583 for freebsd-current-outgoing; Wed, 26 Aug 1998 23:58:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (castles320.castles.com [208.214.167.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21568 for ; Wed, 26 Aug 1998 23:58:50 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id XAA01816; Wed, 26 Aug 1998 23:56:18 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808262356.XAA01816@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Luoqi Chen cc: current@FreeBSD.ORG Subject: Re: possible race window for getblk? In-reply-to: Your message of "Wed, 26 Aug 1998 08:35:48 -0400." <199808261235.IAA04095@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Aug 1998 23:56:17 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem with this check is, reads only hold shared lock on the vnode, > thus the vnode lock won't prevent two reads from successfully creating > two new buffers at the same block offset. This check should be extended > to shared lock: > if (VOP_ISLOCKED(vp) != LK_EXCLUSIVE && gbincore(vp, blkno)) { > bp->b_flags |= B_INVAL; > brelse(bp); > goto loop; > } Makes sense. Does this apply to -stable as well? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 00:24:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25127 for freebsd-current-outgoing; Thu, 27 Aug 1998 00:24:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25119 for ; Thu, 27 Aug 1998 00:24:51 -0700 (PDT) (envelope-from archer@grape.carrier.kiev.ua) Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111]) by burka.carrier.kiev.ua (8.9.0/8.Who.Cares) with ESMTP id KAA05452; Thu, 27 Aug 1998 10:23:56 +0300 (EEST) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id KAA27691; Thu, 27 Aug 1998 10:22:18 +0300 (EEST) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.9.1/8.8.8) id KAA02669; Thu, 27 Aug 1998 10:14:19 +0300 (EEST) (envelope-from archer) Date: Thu, 27 Aug 1998 10:14:19 +0300 (EEST) From: Alexander Litvin Message-Id: <199808270714.KAA02669@grape.carrier.kiev.ua> To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: encountered possible VM bug ? X-Newsgroups: grape.freebsd.current In-Reply-To: <19980824111923.A207@compufit.at> <19980824115816.A15512@mars.hsc.fr> <199808241413.KAA26862@khavrinen.lcs.mit.edu> Organization: Lucky Grape User-Agent: tin/pre-1.4-980202 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199808241413.KAA26862@khavrinen.lcs.mit.edu> you wrote: GW> < said: >> Under out of memory conditions, inetd tends to fall in a weird >> state. Apparently this is an interaction between the malloc library >> and inetd, but nobody has managed yet to find out exactly what >> happens. Maybe error checking is lacking somewhere. GW> No, this is the ``daemons dying'' bug which nobody has fixed yet. GW> When the system runs out of swap, some random selection of processes GW> which are in swap get corrupted. Usually this results in a daemon GW> which dies whenever it fork()s, but sometimes it is manifested as GW> other sorts of corruption. The message you see from realloc is GW> indicative of a corrupted pointer. Really, I was under impression, that it is the problem just with fork(). But now I may confirm that processes get corrupted in different manners. E.g., I have now a specially written dummy daemon running, which I was able to corrupt (intentionally exhausting swap) in such a way that it successfully forks. Than child process sleeps (just to give me chance to attach to it with debugger), allocates memory, accesses it -- and during all that it doesn't get SIGSEGV. But then it dies when trying to syslog(3). It seems that the corruption is in mmaped ld.so or libc.3.1.so. If anybody cares, I may try to give any other details. GW> -GAWollman SY, Alexander Litvin, Lucky Net ltd. --- According to Kentucky state law, every person must take a bath at least once a year. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 00:30:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25956 for freebsd-current-outgoing; Thu, 27 Aug 1998 00:30:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25925 for ; Thu, 27 Aug 1998 00:30:22 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from ben by scientia.demon.co.uk with local (Exim 2.02 #20) id 0zBvwE-0005Xe-00; Thu, 27 Aug 1998 07:53:42 +0100 Date: Thu, 27 Aug 1998 07:53:42 +0100 From: Ben Smithurst To: John Birrell Cc: freebsd-current@FreeBSD.ORG Subject: Re: Problems building -current Message-ID: <19980827075342.A21285@scientia.demon.co.uk> References: <19980827052836.A22477@scientia.demon.co.uk> <199808270531.PAA05931@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: <199808270531.PAA05931@cimlogic.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Birrell wrote: > make -m /usr/src/share/mk buildworld Thanks, but it still doesn't work, fails with the same error. Any other ideas? -- Ben Smithurst : ben@scientia.demon.co.uk : http://www.scientia.demon.co.uk/ PGP: 0x99392F7D - 3D 89 87 42 CE CA 93 4C 68 32 0E D5 36 05 3D 16 http://www.scientia.demon.co.uk/ben/pgp-key.html (or use keyservers) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 00:57:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29107 for freebsd-current-outgoing; Thu, 27 Aug 1998 00:57:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29102 for ; Thu, 27 Aug 1998 00:57:36 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl1.philips.com with ESMTP id JAA07129 for ; Thu, 27 Aug 1998 09:56:41 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id JAA17272 for ; Thu, 27 Aug 1998 09:56:41 +0200 (MET DST) Received: (qmail 5878 invoked by uid 666); 27 Aug 1998 07:57:01 -0000 Message-ID: <19980827095701.B5471@hal.mpn.cp.philips.com> Date: Thu, 27 Aug 1998 09:57:01 +0200 From: Jos Backus To: current@FreeBSD.ORG Subject: Re: recovering disk References: <199808262046.WAA26730@semyam.dinoco.de> <199808262334.SAA13309@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808262334.SAA13309@detlev.UUCP>; from Joel Ray Holveck on Wed, Aug 26, 1998 at 06:34:54PM -0500 X-Files: The Truth is out there! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 26, 1998 at 06:34:54PM -0500, Joel Ray Holveck wrote: > You know what I'd like? A general disk editor, that can take its > input by the block or by the file, with a hex editor as well as some > special-purpose viewers. Something like Norton's Disk Editor. Said > tool has been amazingly useful to me on many an occasion. There's always http://www.pobox.com/~djb/software/ufsread-0.50.shar.gz, although it is probably too fs-centric for this purpose... Cheers, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 01:07:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00950 for freebsd-current-outgoing; Thu, 27 Aug 1998 01:07:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00938 for ; Thu, 27 Aug 1998 01:07:41 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id SAA06457; Thu, 27 Aug 1998 18:18:07 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808270818.SAA06457@cimlogic.com.au> Subject: Re: Problems building -current In-Reply-To: <19980827075342.A21285@scientia.demon.co.uk> from Ben Smithurst at "Aug 27, 98 07:53:42 am" To: ben@scientia.demon.co.uk (Ben Smithurst) Date: Thu, 27 Aug 1998 18:18:06 +1000 (EST) Cc: jb@cimlogic.com.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Smithurst wrote: > John Birrell wrote: > > > make -m /usr/src/share/mk buildworld > > Thanks, but it still doesn't work, fails with the same error. Any > other ideas? Start with a clean system (/usr/obj) and try again. I have tested this more than once! -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 02:42:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15626 for freebsd-current-outgoing; Thu, 27 Aug 1998 02:42:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15616 for ; Thu, 27 Aug 1998 02:42:44 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id LAA16148; Thu, 27 Aug 1998 11:46:14 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 27 Aug 1998 11:46:13 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Julian Elischer cc: freebsd-current@FreeBSD.ORG Subject: It's MFS panic.. (Re: Panic with DEVFS) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Aug 1998, Andrzej Bialecki wrote: > I'm totally lame when it comes to FS internals, but this looks to me > as if some delayed action (caching? cleaning? read-ahead? whatever?) > is causing this. ...but it looks like I was right after all. Below is the trace (no crashdump available yet - I'm working on it). Source tree is about four days old. One important notice, though: this time I was able to reliably crash _without_ disabling any device, and even when not touching /dev at all - it was enough to do just an 'ls -l' of some directory a few times to produce sufficient number of dirty pages... The only thing that is common in all these cases is: * root on MFS * DEVFS/SLICE kernel and it seems these two definitely don't like each other.. :-( So, here's the stack trace (taken by hand.. :-<< ): _panic() _mfs_strategy(ap=...) at _mfs_strategy+0x3c [../../ufs/mfs/mfs_vnops.c:137] _bwrite(bp=...) at _bwrite+0xaf [../../kern/vfs_bio.c:891] * _vop_stdbwrite(ap=...) at _vop_defaultop+0x15 [../../kern/vfs_default.c:131] * _bawrite(bp=...) at _bawrite+0x2c [../../kern/vfs_bio.c:1122] * _spec_fsync(ap=...) at _spec_fsync+0x76 [../../miscfs/specfs/spec_vnops.c:509] _mfs_fsync(ap=...) at _mfs_fsync+0x16 [../../ufs/mfs/mfs_vnops.c:118] _sched_sync() at _sched_sync+0xa4 [../../kern/vfs_subr.c:499] _kproc_start(udata=...) at _kproc_start+0x32 [../../kern/init_main.c:248] _fork_trampoline(...,...,...,...,...) at _fork_trampoline+0x30 The lines marked with stars ('*') in other panics were replaced with the following lines: _vop_stdbwrite(ap=...) at _vop_stdbwrite+0xe [../../kern/vfs_default.c:285] _vop_defaultop(ap=...) at _vop_defaultop+0x15 [../../kern/vfs_default.c:131] _vfs_bio_awrite(bp=...) at _vfs_bio_awrite+0x103 [../../kern/vfs_bio.c:1122] _spec_fsync(ap=...) at _spec_fsync+0x1e [../../miscfs/specfs/spec_vnops.c:503] I also tried to do a 'show object' which printed: db> show object Object 0xf019bb75: type=1694529634, size=0x65007864, res=1166738538, ret=1694529635, flags=0x7363 Fatal trap 12: page fault while in kernel mode ... fault code = supervisor read, page not present ... current process = 4 (syncer) interrupt mask = bio and at this point I gave up... I'll try to get the coredump, if you're interested in having it... Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 02:52:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16438 for freebsd-current-outgoing; Thu, 27 Aug 1998 02:52:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA16430 for ; Thu, 27 Aug 1998 02:52:23 -0700 (PDT) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id LAA25044; Thu, 27 Aug 1998 11:23:18 +0200 (CEST) Message-ID: <19980827112317.A25012@cons.org> Date: Thu, 27 Aug 1998 11:23:17 +0200 From: Martin Cracauer To: Bruce Evans , cracauer@cons.org, current@FreeBSD.ORG, luoqi@watermarkgroup.com, shocking@prth.pgs.com Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops References: <199808270253.MAA15661@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808270253.MAA15661@godzilla.zeta.org.au>; from Bruce Evans on Thu, Aug 27, 1998 at 12:53:36PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199808270253.MAA15661@godzilla.zeta.org.au>, Bruce Evans wrote: > >Ah, now I got it. > > > >If sig == SIGFPE, then expect the trap code to be one of FPE_*_TRAP > >values from machine/trap.h, *not* one of the T_* values. > > Except this is not implemented. It doesn't pass floating point conditions, but I receive FPE_INTDIV_TRAP when I should. That makes the hardest case distinguishable (int devision by zero -> restarted instruction after signal handler exit). Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 03:09:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18381 for freebsd-current-outgoing; Thu, 27 Aug 1998 03:09:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA18376 for ; Thu, 27 Aug 1998 03:09:30 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id MAA29706; Thu, 27 Aug 1998 12:12:37 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 27 Aug 1998 12:12:36 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike cc: freebsd-current@FreeBSD.ORG Subject: Re: Something changed in sendmail cf? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Aug 1998, Mike wrote: > On Sun, 23 Aug 1998, Andrzej Bialecki wrote: > > > Where should I look now? What has changed with sendmail? What should I do > > to make it work? > > Perhaps the 'latest current' is using sendmail 8.9.1? Yes, it does. What should I do, then (except replacing sendmail with an older version)? Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 03:55:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA23542 for freebsd-current-outgoing; Thu, 27 Aug 1998 03:55:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA23536 for ; Thu, 27 Aug 1998 03:55:33 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA18772; Thu, 27 Aug 1998 20:54:37 +1000 Date: Thu, 27 Aug 1998 20:54:37 +1000 From: Bruce Evans Message-Id: <199808271054.UAA18772@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org, current@FreeBSD.ORG, luoqi@watermarkgroup.com, shocking@prth.pgs.com Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> 2) if the SIGFPE was for an FP operation, then the FP operatation will be >> restarted. The kernel has cleared the trap-pending flag before delivering >> the SIGFPE to the application, and on i386's traps are delivered to the >> kernel on the the first non-control FP operation after the one that >> caused the exception, so it is certain that the restarted FP operation >> won't trap; it may cause an exception which will be delivered to the >> kernel on the next non-control FP operation. > >I'm not able to reproduce this behaviour. I wrote a short test program >that runs like this: It's easiest to reproduce it using assembler code - fill up the stack with near-garbage using 8 fldz's and then attempt to clean up the stack using 8 fdivp's. The fdivp's will have no effect except to generate FP exceptions, but if a compiler had generated them, it would expect the stack to be clean at the end. I wrote the assembler code. Run it under gdb and look at the FP state using `info float'. Homework: explain why this generates only 6 SIGFPE's although it divides by 0.0 by 0.0 8 times. Bruce #include #include int main(void) { /* I'm too lazy to set up signal handler. Use gdb to watch signals. */ signal(SIGFPE, SIG_IGN); /* Ensure a SIGFPE for 0.0/0.0. */ fpsetmask(FP_X_INV); asm("fldz"); asm("fldz"); asm("fldz"); asm("fldz"); asm("fldz"); asm("fldz"); asm("fldz"); asm("fldz"); asm("fdivp %st(0)"); asm("fdivp %st(0)"); asm("fdivp %st(0)"); asm("fdivp %st(0)"); asm("fdivp %st(0)"); asm("fdivp %st(0)"); asm("fdivp %st(0)"); asm("fdivp %st(0)"); return (0); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 05:11:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02617 for freebsd-current-outgoing; Thu, 27 Aug 1998 05:11:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02612 for ; Thu, 27 Aug 1998 05:11:53 -0700 (PDT) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id OAA25489; Thu, 27 Aug 1998 14:10:40 +0200 (CEST) Message-ID: <19980827141039.B25278@cons.org> Date: Thu, 27 Aug 1998 14:10:39 +0200 From: Martin Cracauer To: Bruce Evans , cracauer@cons.org, current@FreeBSD.ORG, luoqi@watermarkgroup.com, shocking@prth.pgs.com Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops References: <199808271054.UAA18772@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808271054.UAA18772@godzilla.zeta.org.au>; from Bruce Evans on Thu, Aug 27, 1998 at 08:54:37PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199808271054.UAA18772@godzilla.zeta.org.au>, Bruce Evans wrote: > I wrote the assembler code. Run it under gdb and look at the FP > state using `info float'. Homework: explain why this generates > only 6 SIGFPE's although it divides by 0.0 by 0.0 8 times. ^ Don't you mean 7? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 05:25:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04650 for freebsd-current-outgoing; Thu, 27 Aug 1998 05:25:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04645 for ; Thu, 27 Aug 1998 05:25:54 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id WAA25445; Thu, 27 Aug 1998 22:24:58 +1000 Date: Thu, 27 Aug 1998 22:24:58 +1000 From: Bruce Evans Message-Id: <199808271224.WAA25445@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org, current@FreeBSD.ORG, luoqi@watermarkgroup.com, shocking@prth.pgs.com Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I wrote the assembler code. Run it under gdb and look at the FP >> state using `info float'. Homework: explain why this generates >> only 6 SIGFPE's although it divides by 0.0 by 0.0 8 times. > ^ >Don't you mean 7? Oops. I miscounted 6 and thought that it was missing 1 for both the first and the last division. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 07:14:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16367 for freebsd-current-outgoing; Thu, 27 Aug 1998 07:14:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16354 for ; Thu, 27 Aug 1998 07:14:23 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id QAA21978; Thu, 27 Aug 1998 16:09:24 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id KAA02095; Thu, 27 Aug 1998 10:41:58 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808270841.KAA02095@semyam.dinoco.de> To: Jonathan Lemon , freebsd-current@FreeBSD.ORG Subject: Re: Not receiving CVS commit messages In-reply-to: Your message of "Sat, 22 Aug 1998 12:14:17 CDT." <19980822121417.21415@right.PCS> Cc: seggers@semyam.dinoco.de Date: Thu, 27 Aug 1998 10:41:57 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In any case, you can get the same functionality by subscribing > to cvs-all, and using a procmail filter to weed out what you > aren't interested in. It's not the same. That would increase transfer times significantly for me as I would have to transfer all log messages instead of just the kernel related ones. It simply costs money I prefer to spend on more useful things instead. I am just interested in the kernel to get noticed when anything impor- tant happens there. I don't care much about bugs in user land prog- rams as they don't lead to the whole machine crashing. To me cvs-all, cvs-bin, cvs-ports and cvs-sys sounds like a reasonable way to split it. The hundreds of lists that previously existed are a bit too much IMHO. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 07:25:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17268 for freebsd-current-outgoing; Thu, 27 Aug 1998 07:25:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17263 for ; Thu, 27 Aug 1998 07:25:10 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id KAA15815; Thu, 27 Aug 1998 10:24:17 -0400 (EDT) (envelope-from luoqi) Date: Thu, 27 Aug 1998 10:24:17 -0400 (EDT) From: Luoqi Chen Message-Id: <199808271424.KAA15815@lor.watermarkgroup.com> To: luoqi@watermarkgroup.com, mike@smith.net.au Subject: Re: possible race window for getblk? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > The problem with this check is, reads only hold shared lock on the vnode, > > thus the vnode lock won't prevent two reads from successfully creating > > two new buffers at the same block offset. This check should be extended > > to shared lock: > > if (VOP_ISLOCKED(vp) != LK_EXCLUSIVE && gbincore(vp, blkno)) { > > bp->b_flags |= B_INVAL; > > brelse(bp); > > goto loop; > > } > > Makes sense. Does this apply to -stable as well? > Yes, it's there since 1995. I looked at the CVS history, it used to be only the incore check. VOP_ISLOCKED check was added later as an optimization, I think. Given the total number of buffers of 2K and the hash size of 512, on average each hash chain is of length 4, it doesn't seem to save us much with this optimization (if it doesn't cost more). -lq > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 08:04:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22471 for freebsd-current-outgoing; Thu, 27 Aug 1998 08:04:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22459 for ; Thu, 27 Aug 1998 08:04:53 -0700 (PDT) (envelope-from wosch@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id RAA07884; Thu, 27 Aug 1998 17:03:45 +0200 (CEST) (envelope-from wosch@panke.de.freebsd.org) Received: (from wosch@localhost) by campa.panke.de (8.8.8/8.8.8) id QAA03183; Thu, 27 Aug 1998 16:09:53 +0200 (MET DST) (envelope-from wosch) Message-ID: <19980827160951.A3164@panke.de> Date: Thu, 27 Aug 1998 16:09:51 +0200 From: Wolfram Schneider To: joelh@gnu.org, thyerm@camtech.net.au Cc: wosch@panke.de.freebsd.org, current@FreeBSD.ORG Subject: Re: file segment sizes of a core dump References: <199808231906.VAA04727@campa.panke.de> <35E18FF5.B7FADA7B@camtech.net.au> <19980824193728.B4111@panke.de> <199808251931.OAA00986@detlev.UUCP> <35E40C49.C673670C@camtech.net.au> <199808262253.RAA03247@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808262253.RAA03247@detlev.UUCP>; from Joel Ray Holveck on Wed, Aug 26, 1998 at 05:53:23PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-08-26 17:53:23 -0500, Joel Ray Holveck wrote: > I accept GIGO as a fact of life. I would vote against needing the > switch. That's all I have to say on the topic. I have now a version without the switch. size(1) checks now a value of the user structure (number of groups). If the values seems correct size(1) assume it is a core file. Index: size.c =================================================================== RCS file: /usr/cvs/src/usr.bin/size/size.c,v retrieving revision 1.4 diff -u -r1.4 size.c --- size.c 1998/07/06 21:01:32 1.4 +++ size.c 1998/08/27 12:43:08 @@ -47,6 +47,9 @@ #include #include +#include +#include +#include #include #include #include @@ -66,7 +69,6 @@ while ((ch = getopt(argc, argv, "")) != -1) switch(ch) { - case '?': default: usage(); } @@ -90,29 +92,63 @@ { static int first = 1; struct exec head; + struct user user; + struct stat stat; u_long total; int fd; + int coredump = 0; if ((fd = open(name, O_RDONLY, 0)) < 0) { warn("%s", name); return (1); } - if (read(fd, &head, sizeof(head)) != sizeof(head) || N_BADMAG(head)) { - (void)close(fd); + + if (read(fd, &head, sizeof(head)) != sizeof(head)) { warnx("%s: not in a.out format", name); + (void)close(fd); return (1); } + + /* if not a.out try coredump format */ + if (N_BADMAG(head)) { + if (lseek(fd, (off_t)0, SEEK_SET) != -1 && + read(fd, &user, sizeof(user)) == sizeof(user) && + fstat(fd, &stat) != -1 && + stat.st_size >= + ptoa(UPAGES + user.u_dsize + user.u_ssize) && + user.u_kproc.kp_eproc.e_ucred.cr_ngroups <= NGROUPS_MAX && + user.u_kproc.kp_eproc.e_ucred.cr_ngroups > 0) { + coredump = 1; + } else { + warnx("%s: not in a.out or core format", name); + (void)close(fd); + return (1); + } + } (void)close(fd); if (first) { first = 0; (void)printf("text\tdata\tbss\tdec\thex\n"); + } + + if (!coredump) { + total = head.a_text + head.a_data + head.a_bss; + (void)printf("%lu\t%lu\t%lu\t%lu\t%lx", (u_long)head.a_text, + (u_long)head.a_data, (u_long)head.a_bss, total, total); + } else { + total = ptoa(user.u_tsize) + ptoa(user.u_dsize) + + ptoa(user.u_ssize); + (void)printf("%lu\t%lu\t%lu\t%lu\t%lx", + (u_long)ptoa(user.u_tsize), + (u_long)ptoa(user.u_dsize), + (u_long)ptoa(user.u_ssize), total, total); } - total = head.a_text + head.a_data + head.a_bss; - (void)printf("%lu\t%lu\t%lu\t%lu\t%lx", (u_long)head.a_text, - (u_long)head.a_data, (u_long)head.a_bss, total, total); - if (count > 1) + + if (count > 1 || coredump) (void)printf("\t%s", name); + if (coredump) + printf(" [coredump]"); (void)printf("\n"); return (0); } -- Wolfram Schneider http://www.freebsd.org/~w/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 09:05:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29797 for freebsd-current-outgoing; Thu, 27 Aug 1998 09:05:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley-185-114.res.iastate.edu (friley-185-114.res.iastate.edu [129.186.185.114]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29784 for ; Thu, 27 Aug 1998 09:04:56 -0700 (PDT) (envelope-from ccsanady@friley-185-114.res.iastate.edu) Received: from friley-185-114.res.iastate.edu (loopback [127.0.0.1]) by friley-185-114.res.iastate.edu (8.9.1/8.9.1) with ESMTP id LAA05116; Thu, 27 Aug 1998 11:01:58 -0500 (CDT) (envelope-from ccsanady@friley-185-114.res.iastate.edu) Message-Id: <199808271601.LAA05116@friley-185-114.res.iastate.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: Stefan Eggers cc: Jonathan Lemon , freebsd-current@FreeBSD.ORG Subject: Re: Not receiving CVS commit messages In-reply-to: Your message of "Thu, 27 Aug 1998 10:41:57 +0200." <199808270841.KAA02095@semyam.dinoco.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Aug 1998 11:01:58 -0500 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> In any case, you can get the same functionality by subscribing >> to cvs-all, and using a procmail filter to weed out what you >> aren't interested in. > >It's not the same. That would increase transfer times significantly >for me as I would have to transfer all log messages instead of just >the kernel related ones. It simply costs money I prefer to spend on >more useful things instead. > >I am just interested in the kernel to get noticed when anything impor- >tant happens there. I don't care much about bugs in user land prog- >rams as they don't lead to the whole machine crashing. > >To me cvs-all, cvs-bin, cvs-ports and cvs-sys sounds like a reasonable >way to split it. The hundreds of lists that previously existed are a >bit too much IMHO. I completely agree with this. I would not mind having fewer lists, but cvs-all has quite a low signal to noise ratio for some of us. I really don't care to see the ports/web/doc commits. Perhaps at least the src commits can be seperated? Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 09:41:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06655 for freebsd-current-outgoing; Thu, 27 Aug 1998 09:41:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06619 for ; Thu, 27 Aug 1998 09:40:59 -0700 (PDT) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.9.1/8.8.8) with SMTP id MAA16553 for ; Thu, 27 Aug 1998 12:40:03 -0400 (EDT) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Thu, 27 Aug 1998 12:40:03 -0400 (EDT) From: "Alok K. Dhir" To: current@FreeBSD.ORG Subject: Can't build perl Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey all - I tried to build perl5.005_02 both from the port and manually today on 3.0-current as of yesterday. Both failed when trying to link 'miniperl' with tons of these errors: cc -L/usr/local/lib -o miniperl miniperlmain.o libperl.a -lgdbm -lm -lc -lcrypt libperl.a(perl.o): Undefined symbol `___error' referenced (use -lc ?) libperl.a(perl.o): Undefined symbol `_getpid' referenced (use -lc ?) libperl.a(perl.o): Undefined symbol `_kill' referenced (use -lc ?) libperl.a(perl.o): Undefined symbol `_fcntl' referenced (use -lc ?) libperl.a(perl.o): Undefined symbol `_fstat' referenced (use -lc ?) libperl.a(perl.o): Undefined symbol `_chdir' referenced (use -lc ?) libperl.a(perl.o): Undefined symbol `_getuid' referenced (use -lc ?) libperl.a(perl.o): Undefined symbol `_geteuid' referenced (use -lc ?) libperl.a(perl.o): Undefined symbol `_getgid' referenced (use -lc ?) libperl.a(perl.o): Undefined symbol `_getegid' referenced (use -lc ?) libperl.a(perl.o): Undefined symbol `_stat' referenced (use -lc ?) libperl.a(toke.o): Undefined symbol `___error' referenced (use -lc ?) libperl.a(toke.o): Undefined symbol `_fcntl' referenced (use -lc ?) libperl.a(util.o): Undefined symbol `_pipe' referenced (use -lc ?) libperl.a(util.o): Undefined symbol `_fork' referenced (use -lc ?) [*SNIP*] I've seen this happen on some other programs I've tried to compile lately (ever since the move from /usr/lib to /usr/lib/aout). Any help? Thanks! Al To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 09:46:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07769 for freebsd-current-outgoing; Thu, 27 Aug 1998 09:46:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (castles229.castles.com [208.214.165.229]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07747 for ; Thu, 27 Aug 1998 09:46:38 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id JAA04009; Thu, 27 Aug 1998 09:42:56 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808270942.JAA04009@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: Julian Elischer , freebsd-current@FreeBSD.ORG Subject: Re: It's MFS panic.. (Re: Panic with DEVFS) In-reply-to: Your message of "Thu, 27 Aug 1998 11:46:13 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Aug 1998 09:42:55 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > _panic() > _mfs_strategy(ap=...) at _mfs_strategy+0x3c [../../ufs/mfs/mfs_vnops.c:137] Looks like the vp is bogus (probably NULL). Unfortunately you left the faut virtual address out, which is probably the most critical corroborating item. It'd probably be < 0x100 in this case, if you're trying to get at the v_data element for struct vnode at 0. Something's definitely wrong here; ufs would have crashed at the same point. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 10:24:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13864 for freebsd-current-outgoing; Thu, 27 Aug 1998 10:24:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13854 for ; Thu, 27 Aug 1998 10:24:08 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA29228; Thu, 27 Aug 1998 10:20:08 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdn29206; Thu Aug 27 17:20:01 1998 Date: Thu, 27 Aug 1998 10:19:57 -0700 (PDT) From: Julian Elischer To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: It's MFS panic.. (Re: Panic with DEVFS) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ooooohhhhhhh specfs is not active if DEVFS is active so the spec_fsync should not be called...... I bet it's hard coded into MFS.. it should be replaced with a VOP_FSYNC(vn) whch would call devfs_fsync() instead...... (yech) I'll look at it right now julian On Thu, 27 Aug 1998, Andrzej Bialecki wrote: > > On Wed, 26 Aug 1998, Andrzej Bialecki wrote: > > > I'm totally lame when it comes to FS internals, but this looks to me > > as if some delayed action (caching? cleaning? read-ahead? whatever?) > > is causing this. > > ...but it looks like I was right after all. Below is the trace (no > crashdump available yet - I'm working on it). Source tree is about four > days old. > > One important notice, though: this time I was able to reliably crash > _without_ disabling any device, and even when not touching /dev at all - > it was enough to do just an 'ls -l' of some directory a few times to > produce sufficient number of dirty pages... The only thing that is common > in all these cases is: > > * root on MFS > * DEVFS/SLICE kernel > > and it seems these two definitely don't like each other.. :-( > > So, here's the stack trace (taken by hand.. :-<< ): > > _panic() > _mfs_strategy(ap=...) at _mfs_strategy+0x3c [../../ufs/mfs/mfs_vnops.c:137] > _bwrite(bp=...) at _bwrite+0xaf [../../kern/vfs_bio.c:891] > * _vop_stdbwrite(ap=...) at _vop_defaultop+0x15 [../../kern/vfs_default.c:131] > * _bawrite(bp=...) at _bawrite+0x2c [../../kern/vfs_bio.c:1122] > * _spec_fsync(ap=...) at _spec_fsync+0x76 [../../miscfs/specfs/spec_vnops.c:509] > _mfs_fsync(ap=...) at _mfs_fsync+0x16 [../../ufs/mfs/mfs_vnops.c:118] > _sched_sync() at _sched_sync+0xa4 [../../kern/vfs_subr.c:499] > _kproc_start(udata=...) at _kproc_start+0x32 [../../kern/init_main.c:248] > _fork_trampoline(...,...,...,...,...) at _fork_trampoline+0x30 > > The lines marked with stars ('*') in other panics were replaced with the > following lines: > > _vop_stdbwrite(ap=...) at _vop_stdbwrite+0xe [../../kern/vfs_default.c:285] > _vop_defaultop(ap=...) at _vop_defaultop+0x15 [../../kern/vfs_default.c:131] > _vfs_bio_awrite(bp=...) at _vfs_bio_awrite+0x103 [../../kern/vfs_bio.c:1122] > _spec_fsync(ap=...) at _spec_fsync+0x1e [../../miscfs/specfs/spec_vnops.c:503] > > I also tried to do a 'show object' which printed: > > db> show object > Object 0xf019bb75: type=1694529634, size=0x65007864, res=1166738538, ret=1694529635, flags=0x7363 > > Fatal trap 12: page fault while in kernel mode > ... > fault code = supervisor read, page not present > ... > current process = 4 (syncer) > interrupt mask = bio > > and at this point I gave up... > > I'll try to get the coredump, if you're interested in having it... > > Andrzej Bialecki > > +---------------------+------------------------+--------------------------+ > | | When in problem or in | if(halt_per_mth > 0) { | > | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | > | Network in Poland | scream and shout. | } | > + --------------------+------------------------+--------------------------+ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 10:37:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15781 for freebsd-current-outgoing; Thu, 27 Aug 1998 10:37:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15740 for ; Thu, 27 Aug 1998 10:37:38 -0700 (PDT) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-13-41.camtech.net.au [203.55.242.105]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id DAA08264; Fri, 28 Aug 1998 03:06:03 +0930 (CST) Message-ID: <35E59889.4BB565A5@camtech.net.au> Date: Fri, 28 Aug 1998 03:04:01 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Wolfram Schneider CC: joelh@gnu.org, current@FreeBSD.ORG Subject: Re: file segment sizes of a core dump References: <199808231906.VAA04727@campa.panke.de> <35E18FF5.B7FADA7B@camtech.net.au> <19980824193728.B4111@panke.de> <199808251931.OAA00986@detlev.UUCP> <35E40C49.C673670C@camtech.net.au> <199808262253.RAA03247@detlev.UUCP> <19980827160951.A3164@panke.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Works for me. Maybe for the coredump identification you should run 'file' on it. Maybe 'file' should be run for non-core dumps too. If 'file' is not available just "[coredump]" would do for me. Somehow the full path being there for coredumps and not for normal objects doesn't seem right. Wolfram Schneider wrote: > I have now a version without the switch. size(1) checks now > a value of the user structure (number of groups). If > the values seems correct size(1) assume it is a core file. -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 10:49:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18814 for freebsd-current-outgoing; Thu, 27 Aug 1998 10:49:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18722 for ; Thu, 27 Aug 1998 10:49:30 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id TAA04582; Thu, 27 Aug 1998 19:52:57 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 27 Aug 1998 19:52:57 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Julian Elischer cc: freebsd-current@FreeBSD.ORG Subject: Re: It's MFS panic.. (Re: Panic with DEVFS) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Aug 1998, Julian Elischer wrote: > ooooohhhhhhh I like it... This means that someone knows what's going on. :-) > specfs is not active if DEVFS is active > so the spec_fsync should not be called...... > I bet it's hard coded into MFS.. > > it should be replaced with a VOP_FSYNC(vn) > whch would call devfs_fsync() instead...... > > (yech) > I'll look at it right now Thanks! Well, this also means I'll have to prepare a bugfix release for picobsd... :-(( Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 10:54:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19714 for freebsd-current-outgoing; Thu, 27 Aug 1998 10:54:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19599 for ; Thu, 27 Aug 1998 10:53:41 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id TAA07798; Thu, 27 Aug 1998 19:56:29 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 27 Aug 1998 19:56:29 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: Julian Elischer , freebsd-current@FreeBSD.ORG Subject: Re: It's MFS panic.. (Re: Panic with DEVFS) In-Reply-To: <199808270942.JAA04009@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Aug 1998, Mike Smith wrote: > > _panic() > > _mfs_strategy(ap=...) at _mfs_strategy+0x3c [../../ufs/mfs/mfs_vnops.c:137] > > Looks like the vp is bogus (probably NULL). Unfortunately you left the > faut virtual address out, which is probably the most critical > corroborating item. It'd probably be < 0x100 in this case, if you're > trying to get at the v_data element for struct vnode at 0. Nope. It looked ok (i.e. high enough, something like 0xf0123456). Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 11:41:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28642 for freebsd-current-outgoing; Thu, 27 Aug 1998 11:41:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28604 for ; Thu, 27 Aug 1998 11:41:07 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.8.7/8.8.7) with SMTP id OAA05347; Thu, 27 Aug 1998 14:39:58 -0400 (EDT) Received: by mozart (5.65c/SAS/Domains/5-6-90) id AA02869; Thu, 27 Aug 1998 07:58:07 -0400 From: "John W. DeBoskey" Message-Id: <199808271158.AA02869@mozart> Subject: Re: cvs commit: src/etc make.conf To: mike@smith.net.au (Mike Smith) Date: Thu, 27 Aug 1998 07:58:07 -0400 (EDT) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from "Mike Smith" at Aug 26, 98 11:01:55 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, just to add a bit... I never change rc.conf on my systems. I put all changes into rc.conf.local. Thus, I can easily run a diff job across all the rc.* files and update them in an easy and straightforward manner. Additionally, the *.conf files are not network friendly. Mounting /etc from a common location is painful because of this. What I would really line to see is: rc.conf rc.conf.local <-- not a unique networkable entity rc.conf.$HOSTNAME <-- a unique networkable entity fyi: don't say it... yes, this can be done in rc.conf.local... :-( but it would be nice to have integrated support. Wishing, John > From mike@smith.net.au Wed Aug 26 23:01:55 1998 > Date: Wed, 26 Aug 1998 23:01:55 +0000 > From: Mike Smith > Subject: Re: cvs commit: src/etc make.conf > > > > Hmmm. Perhaps I'll just start storing the changed values into > > rc.conf.local from now on in sysinstall. That would sort of validate > > the concept. :) > > IMHO that should be rc.conf.template and rc.conf. The current > expectation is that rc.conf contains the current settings; moving that > elsewhere would be confusing. > > It is still valid to have rc.conf.template, rc.conf and rc.conf.local, > where the second is common to a group of machines, and the last > specific only to the machine in question. > > - -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 12:04:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03611 for freebsd-current-outgoing; Thu, 27 Aug 1998 12:04:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tor-dev1.nbc.netcom.ca (tor-dev1.nbc.netcom.ca [207.181.89.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03532 for ; Thu, 27 Aug 1998 12:04:06 -0700 (PDT) (envelope-from taob@tor-dev1.nbc.netcom.ca) Received: (from taob@localhost) by tor-dev1.nbc.netcom.ca (8.8.8/8.8.8) id PAA19014; Thu, 27 Aug 1998 15:03:06 -0400 (EDT) Date: Thu, 27 Aug 1998 15:03:06 -0400 (EDT) From: Brian Tao X-Sender: taob@tor-dev1.nbc.netcom.ca To: FREEBSD-CURRENT Subject: Re: Missing termios.h output modes? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Aug 1998, Brian Tao wrote: > > Any reason why the ONLCR flag defined in , but not > OCRNL? ssh2 requires OCRNL for its serial interface support. I just slapped the #define from a Solaris box into the affected ssh .c file to make the error go away, but they fixed it for 2.0.8 anyway, so now it builds cleanly under -current. -- Brian Tao (BT300, taob@risc.org) "Though this be madness, yet there is method in't" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 12:52:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14364 for freebsd-current-outgoing; Thu, 27 Aug 1998 12:52:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sctmg02.sct.ucarb.com (sctmg02.sct.ucarb.com [140.170.101.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14195; Thu, 27 Aug 1998 12:51:33 -0700 (PDT) (envelope-from NguyenHM@ucarb.com) Received: by sctmg02.sct.ucarb.com with Internet Mail Service (5.0.1458.49) id ; Thu, 27 Aug 1998 15:52:01 -0400 Message-ID: <332F90115D96D0119CD500805FEA976B01AFE222@HSCMS01> From: "Nguyen HM (Mike)" To: Dave Glowacki , dag-erli@ifi.uio.no Cc: "Jordan K. Hubbard" , Gary Palmer , alexandr@mail.eecis.udel.edu, Paul Richards , "'Philippe Regnauld'" , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: RE: Threads across processors Date: Thu, 27 Aug 1998 15:44:35 -0400 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id MAA14251 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, it would make sense, since MacOS X used to be Rhapsody which used to be NEXTSTEP, and I do remember that some time ago Apple incorporated large parts of NetBSD into the codebase (back when it was still Rhapsody). Mike. // Mike Nguyen // Unix Systems Analyst and Geek // Union Carbide Corporation * (281) 212-8073 // nguyenhm@ucarb.com * 1138368@skytel.com [pager] > ---------- > From: dag-erli@ifi.uio.no[SMTP:dag-erli@ifi.uio.no] > Sent: Wednesday, August 26, 1998 5:03 PM > To: Dave Glowacki > Cc: Jordan K. Hubbard; Gary Palmer; alexandr@mail.eecis.udel.edu; > Paul Richards; 'Philippe Regnauld'; Chuck Robey; > freebsd-current@FreeBSD.ORG > Subject: Re: Threads across processors > > Dave Glowacki writes: > > According to http://www.macosrumors.com/OSX.html MacOS X will > already have > > a version of BSD built in and a command line interface will be > available. > > macosrumors.com make a living spreading startling but false news. Do > you read the National Enquirer to get the latest on geopolitics? > > DES > -- > Dag-Erling Smørgrav - dag-erli@ifi.uio.no > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 13:07:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18557 for freebsd-current-outgoing; Thu, 27 Aug 1998 13:07:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18443 for ; Thu, 27 Aug 1998 13:06:48 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from ben by scientia.demon.co.uk with local (Exim 2.02 #20) id 0zC7R6-0001T7-00; Thu, 27 Aug 1998 20:10:20 +0100 Date: Thu, 27 Aug 1998 20:10:20 +0100 From: Ben Smithurst To: John Birrell Cc: freebsd-current@FreeBSD.ORG Subject: Re: Problems building -current Message-ID: <19980827201020.A5637@scientia.demon.co.uk> References: <19980827075342.A21285@scientia.demon.co.uk> <199808270818.SAA06457@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: <199808270818.SAA06457@cimlogic.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Birrell wrote: > Start with a clean system (/usr/obj) and try again. Still doesn't work. :-( I'm beginning to think I should stick with 2.2.6, oh well. Anyone else got any bright ideas before I give up? -- Ben Smithurst : ben@scientia.demon.co.uk : http://www.scientia.demon.co.uk/ PGP: 0x99392F7D - 3D 89 87 42 CE CA 93 4C 68 32 0E D5 36 05 3D 16 http://www.scientia.demon.co.uk/ben/pgp-key.html (or use keyservers) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 13:25:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22253 for freebsd-current-outgoing; Thu, 27 Aug 1998 13:25:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22219; Thu, 27 Aug 1998 13:24:48 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id WAA03161; Thu, 27 Aug 1998 22:23:48 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Thu, 27 Aug 1998 22:23:47 +0200 (MET DST) Mime-Version: 1.0 To: "Nguyen HM (Mike)" Cc: Dave Glowacki , "Jordan K. Hubbard" , Gary Palmer , alexandr@mail.eecis.udel.edu, Paul Richards , "'Philippe Regnauld'" , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors References: <332F90115D96D0119CD500805FEA976B01AFE222@HSCMS01> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 27 Aug 1998 22:23:47 +0200 In-Reply-To: "Nguyen HM's message of "Thu, 27 Aug 1998 15:44:35 -0400" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA22227 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Nguyen HM (Mike)" writes: > Actually, it would make sense, since MacOS X used to be Rhapsody which > used to be NEXTSTEP, and I do remember that some time ago Apple > incorporated large parts of NetBSD into the codebase (back when it was > still Rhapsody). I'm not saying it doesn't make sense. I'm just saying that one shouldn't believe anything on macosrumors.com unless it is confirmed by a more authoritative source. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 13:52:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27189 for freebsd-current-outgoing; Thu, 27 Aug 1998 13:52:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27169 for ; Thu, 27 Aug 1998 13:52:43 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA06783; Thu, 27 Aug 1998 13:42:58 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdNx6776; Thu Aug 27 20:42:48 1998 Date: Thu, 27 Aug 1998 13:42:44 -0700 (PDT) From: Julian Elischer To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: It's MFS panic.. (Re: Panic with DEVFS) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG here.. try the following fix: On Thu, 27 Aug 1998, Andrzej Bialecki wrote: > > On Thu, 27 Aug 1998, Julian Elischer wrote: > > > ooooohhhhhhh > > I like it... This means that someone knows what's going on. :-) > > > specfs is not active if DEVFS is active > > so the spec_fsync should not be called...... > > I bet it's hard coded into MFS.. > > > > it should be replaced with a VOP_FSYNC(vn) > > whch would call devfs_fsync() instead...... > > > > (yech) > > I'll look at it right now > > Thanks! > > Well, this also means I'll have to prepare a bugfix release for picobsd... > :-(( yep Index: mfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/mfs/mfs_vnops.c,v retrieving revision 1.37 diff -c -r1.37 mfs_vnops.c *** mfs_vnops.c 1998/07/11 07:46:05 1.37 --- mfs_vnops.c 1998/08/27 20:40:22 *************** *** 111,120 **** static int mfs_fsync(ap) ! struct vop_fsync_args *ap; { ! return (VOCALL(spec_vnodeop_p, VOFFSET(vop_fsync), ap)); } /* --- 111,126 ---- static int mfs_fsync(ap) ! struct vop_fsync_args /* { ! struct vnode *a_vp; ! struct ucred *a_cred; ! int a_waitfor; ! struct proc *a_p; ! } */ *ap; { ! return (VOP_FSYNC(ap->a_vp, ap->a_cred, ap->a_waitfor, ap->a_p)); ! /* return (VOCALL(spec_vnodeop_p, VOFFSET(vop_fsync), ap));*/ } /* *************** *** 317,324 **** static int mfs_getpages(ap) ! struct vop_getpages_args *ap; { ! return (VOCALL(spec_vnodeop_p, VOFFSET(vop_getpages), ap)); } --- 323,339 ---- static int mfs_getpages(ap) ! struct vop_getpages_args /* { ! struct vnodeop_desc *a_desc; ! struct vnode *a_vp; ! vm_page_t *a_m; ! int a_count; ! int a_reqpage; ! vm_ooffset_t a_offset; ! } */ *ap; { ! return (VOP_GETPAGES(ap->a_vp, ap->a_m, ap->a_count, ! ap->a_reqpage, ap->a_offset)); ! /*return (VOCALL(spec_vnodeop_p, VOFFSET(vop_getpages), ap));*/ } julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 13:53:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27220 for freebsd-current-outgoing; Thu, 27 Aug 1998 13:53:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27175 for ; Thu, 27 Aug 1998 13:52:48 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA25056; Thu, 27 Aug 1998 13:51:49 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma025052; Thu Aug 27 13:51:40 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id NAA27400; Thu, 27 Aug 1998 13:51:40 -0700 (PDT) From: Archie Cobbs Message-Id: <199808272051.NAA27400@bubba.whistle.com> Subject: Re: encountered possible VM bug ? In-Reply-To: <199808270714.KAA02669@grape.carrier.kiev.ua> from Alexander Litvin at "Aug 27, 98 10:14:19 am" To: archer@lucky.net (Alexander Litvin) Date: Thu, 27 Aug 1998 13:51:40 -0700 (PDT) Cc: wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Litvin writes: > >> Under out of memory conditions, inetd tends to fall in a weird > >> state. Apparently this is an interaction between the malloc library > >> and inetd, but nobody has managed yet to find out exactly what > >> happens. Maybe error checking is lacking somewhere. > > GW> No, this is the ``daemons dying'' bug which nobody has fixed yet. > GW> When the system runs out of swap, some random selection of processes > GW> which are in swap get corrupted. Usually this results in a daemon > GW> which dies whenever it fork()s, but sometimes it is manifested as > GW> other sorts of corruption. The message you see from realloc is > GW> indicative of a corrupted pointer. > > Really, I was under impression, that it is the problem just with fork(). > But now I may confirm that processes get corrupted in different manners. > E.g., I have now a specially written dummy daemon running, which I > was able to corrupt (intentionally exhausting swap) in such a way that > it successfully forks. Than child process sleeps (just to give me > chance to attach to it with debugger), allocates memory, accesses it > -- and during all that it doesn't get SIGSEGV. But then it dies when > trying to syslog(3). It seems that the corruption is in mmaped ld.so > or libc.3.1.so. > > If anybody cares, I may try to give any other details. At Whistle, we've seen this bug every so often for a long time. The common elements seem to be: 1. memory mapping is in use 2. a fork() is happening or just happened But #1 and #2 are not necessarily both related to the same process. This bug has been around for a *long* time, in both 2.x and 3.x. Running out of swap may or may not be related, not sure... I think we've seen this when swap was not an issue. Perhaps running out of swap amplifies the problem. It's really hard to pin down, because the panic seems to come a while after the initial damage is done. We've seen random processes crashing every time they try to fork(), kernel panic's because of some process being on two different queues at the same time (eg, sleep and runnable), and other manifestations. A common manifestation is that a file being written out contains some random page of memory from some other file -- we think the other file is a currently mmap'd file. Julian and Terry can supply more details. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 14:34:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04657 for freebsd-current-outgoing; Thu, 27 Aug 1998 14:34:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04585 for ; Thu, 27 Aug 1998 14:34:35 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA17540 for current@FreeBSD.ORG; Thu, 27 Aug 1998 23:33:40 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 6737B1459; Thu, 27 Aug 1998 22:45:16 +0200 (CEST) Date: Thu, 27 Aug 1998 22:45:16 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: Can't build perl Message-ID: <19980827224516.A26204@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i In-Reply-To: ; from Alok K. Dhir on Thu, Aug 27, 1998 at 12:40:03PM -0400 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4590 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Alok K. Dhir: > Hey all - I tried to build perl5.005_02 both from the port and manually > today on 3.0-current as of yesterday. Both failed when trying to link > 'miniperl' with tons of these errors: Hmmm, weird. It worked here. Summary of my perl5 (5.0 patchlevel 5 subversion 0) configuration: Platform: osname=freebsd, osvers=3.0-current, archname=i386-freebsd uname='freebsd keltia.freenix.fr 3.0-current freebsd 3.0-current #61: sun jul 12 14:38:23 cest 1998 roberto@keltia.freenix.fr:srcsrcsyscompilekeltia i386 ' hint=previous, useposix=true, d_sigaction=define usethreads=undef useperlio=undef d_sfio=undef Compiler: cc='cc', optimize='-O2 -pipe', gccversion=2.7.2.1 cppflags='-I/usr/local/include' ccflags ='-I/usr/local/include' stdchar='char', d_stdstdio=undef, usevfork=true intsize=4, longsize=4, ptrsize=4, doublesize=8 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 alignbytes=4, usemymalloc=n, prototype=define Linker and Libraries: ld='ld', ldflags =' -L/usr/local/lib' libpth=/usr/lib/aout /usr/local/lib /usr/lib libs=-lgdbm -lm -lc -lcrypt libc=/usr/lib/aout/libc.so.3.1, so=so, useshrplib=false, libperl=libperl.a Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' ' cccdlflags='-DPIC -fpic', lddlflags='-Bshareable -L/usr/local/lib' Characteristics of this binary (from libperl): Built under freebsd Compiled at Aug 23 1998 14:05:58 @INC: /opt/perl5/lib/5.005/i386-freebsd /opt/perl5/lib/5.005 /opt/perl5/site_perl/i386-freebsd /opt/perl5/site_perl . Built manually. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #62: Mon Jul 27 20:47:08 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 15:03:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10400 for freebsd-current-outgoing; Thu, 27 Aug 1998 15:03:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tick.ssec.wisc.edu (tick.ssec.wisc.edu [144.92.108.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10340 for ; Thu, 27 Aug 1998 15:03:17 -0700 (PDT) (envelope-from dglo@tick.ssec.wisc.edu) Received: from tick.ssec.wisc.edu (localhost [127.0.0.1]) by tick.ssec.wisc.edu (8.8.7/8.8.7) with ESMTP id RAA10216; Thu, 27 Aug 1998 17:02:19 -0500 (CDT) From: Dave Glowacki Message-Id: <199808272202.RAA10216@tick.ssec.wisc.edu> To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) cc: "Nguyen HM (Mike)" , freebsd-current@FreeBSD.ORG Subject: Re: Threads across processors In-reply-to: Your message of "27 Aug 1998 22:23:47 +0200." Date: Thu, 27 Aug 1998 17:02:18 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "Nguyen HM (Mike)" writes: > > Actually, it would make sense, since MacOS X used to be Rhapsody which > > used to be NEXTSTEP, and I do remember that some time ago Apple > > incorporated large parts of NetBSD into the codebase (back when it was > > still Rhapsody). > > I'm not saying it doesn't make sense. I'm just saying that one > shouldn't believe anything on macosrumors.com unless it is confirmed > by a more authoritative source. I only quoted macosrumors because they claimed to have updated their site recently ... I haven't been following the Mac world for quite a few years (even though I've owned Macs since '85 and Macs outnumber Unix systems in my house.) What's a good site for up-to-date info on MacOS? The Apple Mac OS X site provides a link labeled as "Sources to some of the software found in MacOS X Server's BSD subsystem", which includes a .tgz archive for bash 2.05 [see ftp://ftp.apple.com/devworld/Rhapsody/Sources/] The Apple site also has a MacOS X/Rhapsody FAQ which says: Will the UNIX command-line be part of Mac OS X? No. ... Mac OS X does include a POSIX-style kernel, providing most of the system services required by Unix utilities. ... We expect that a BSD command-line environment will be available for use on top of Mac OS X, though it may come from a third party. [http://developer.apple.com/macosx/server/rhapfaq/2.html] and in another place says The UNIX command line will not be necessary, but will be available for those who wish to take advantage of it. [http://developer.apple.com/macosx/server/rhapfaq/11.html] All this looks to be a couple of months old at least, so maybe even Apple doesn't know what the truth is (and is that really so surprising? :-) This is pretty far from any sort of FreeBSD discussion now, so I'll only reply to followups via email... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 15:28:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16080 for freebsd-current-outgoing; Thu, 27 Aug 1998 15:28:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16011 for ; Thu, 27 Aug 1998 15:28:21 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00718; Thu, 27 Aug 1998 15:25:33 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808271525.PAA00718@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: Andrzej Bialecki , freebsd-current@FreeBSD.ORG Subject: Re: It's MFS panic.. (Re: Panic with DEVFS) In-reply-to: Your message of "Thu, 27 Aug 1998 10:19:57 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Aug 1998 15:25:32 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ooooohhhhhhh > > > specfs is not active if DEVFS is active > so the spec_fsync should not be called...... > I bet it's hard coded into MFS.. It would seem to me that specfs shouldn't even be *built* if DEVFS is enabled. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 15:57:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20935 for freebsd-current-outgoing; Thu, 27 Aug 1998 15:57:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20909 for ; Thu, 27 Aug 1998 15:57:27 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id JAA09047 for current@freebsd.org; Fri, 28 Aug 1998 09:08:09 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808272308.JAA09047@cimlogic.com.au> Subject: HEADS UP: 3 days to E-day To: current@FreeBSD.ORG Date: Fri, 28 Aug 1998 09:08:09 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG G'day, In about 3 days from now, we'll be committing the last of the bits that will enable people to convert from aout to elf. Satoshi has started calling this E-day. This message is advance warning of a significant emotional event in the life of your -current system. Whether this turns out to be a _traumatic_ event will remain to be seen. For those who want to continue to update -current after E-day, you will have the choice as to when you convert. You will still be able to build and run an aout system like you always have. E-day is not the day that the big switch is thrown and you wake up with elves at the foot of the bed. Instead, what E-day really means is elf _enable_ day. To convert to elf, the brave will be able to do a make aout_to_elf and the world will automagically update all those things that a make world normally updates. There are some things that need to stay in aout format for the time being (kernel, lkms, etc since these rely on the completion of other projects). For the not-so-brave, a make aout_to_elf_build will do everything except touch the installed system. This is like a buildworld - in fact it is the equivalent of two buildworlds. At some point though, you will have to decide to bite the bullet and install the elf world using a make aout_to_elf_install. Once the upgrade procedure has been performed, the next make world you do will default to elf. Be warned that the upgrade to elf will break ports. It will take some time for the ports crew to update all the ports makefiles to cater for the elf system. We hope that moving the installed libs from /usr/local/lib to /usr/local/lib/aout will not break the installed ports. There are too many combinations to test this out though. I have tested the upgrade procedure on 2.2.5 and 2.2.6, and I'll do a final test on 2.2.7 before committing the makefile changes. I'm confident that the procedure works on a clean system like you get when you install from CD. On a non-clean system, YMMV. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 16:15:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23493 for freebsd-current-outgoing; Thu, 27 Aug 1998 16:15:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23471 for ; Thu, 27 Aug 1998 16:15:48 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id BAA22533 for freebsd-current@FreeBSD.ORG; Fri, 28 Aug 1998 01:14:52 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id E2F951459; Fri, 28 Aug 1998 00:32:28 +0200 (CEST) Date: Fri, 28 Aug 1998 00:32:28 +0200 From: Ollivier Robert To: FREEBSD-CURRENT Subject: Re: Missing termios.h output modes? Message-ID: <19980828003228.A27078@keltia.freenix.fr> Mail-Followup-To: FREEBSD-CURRENT References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i In-Reply-To: ; from Brian Tao on Thu, Aug 27, 1998 at 03:03:06PM -0400 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4590 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Brian Tao: > I just slapped the #define from a Solaris box into the affected > ssh .c file to make the error go away, but they fixed it for 2.0.8 > anyway, so now it builds cleanly under -current. They fixed it by deleting the affected file which was apparently not needed. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #62: Mon Jul 27 20:47:08 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 16:22:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24461 for freebsd-current-outgoing; Thu, 27 Aug 1998 16:22:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24453 for ; Thu, 27 Aug 1998 16:22:26 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01095; Thu, 27 Aug 1998 16:19:03 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808271619.QAA01095@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: current@FreeBSD.ORG Subject: Re: HEADS UP: 3 days to E-day In-reply-to: Your message of "Fri, 28 Aug 1998 09:08:09 +1000." <199808272308.JAA09047@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Aug 1998 16:19:03 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In about 3 days from now, we'll be committing the last of the bits > that will enable people to convert from aout to elf. Satoshi has > started calling this E-day. Go John! This makes you the E-man! 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 16:40:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27283 for freebsd-current-outgoing; Thu, 27 Aug 1998 16:40:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-10.ppp.wenet.net [206.15.84.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27265 for ; Thu, 27 Aug 1998 16:40:45 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id QAA01556; Thu, 27 Aug 1998 16:41:07 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 27 Aug 1998 16:41:06 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Alexander Sanda cc: freebsd-current@FreeBSD.ORG Subject: Re: encountered possible VM bug ? In-Reply-To: <19980824111923.A207@compufit.at> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Aug 1998, Alexander Sanda wrote: [...] > Ok, what happened ? > While I was playing with the KDE newsreader (krn), I encountered a bug > in krn, probably caused by some kind of infinite recursion or similar. The quick answer is, similar to the answer "what do I do; it hurts when I put my finger in my ear": don't do that. krn, as-is, will indeed eat gobs of RAM on big newsgroups (2000+ messages IIRC). Add more swap space, debug krn, or just don't grab that many subject headers. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 17:24:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05255 for freebsd-current-outgoing; Thu, 27 Aug 1998 17:24:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05014 for ; Thu, 27 Aug 1998 17:22:45 -0700 (PDT) (envelope-from Studded@dal.net) Received: from dal.net (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id RAA00558; Thu, 27 Aug 1998 17:20:46 -0700 (PDT) (envelope-from Studded@dal.net) Message-ID: <35E5F7DD.A4213FBF@dal.net> Date: Thu, 27 Aug 1998 17:20:45 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.7-STABLE-0823 i386) MIME-Version: 1.0 To: Mike Smith CC: John Birrell , current@FreeBSD.ORG Subject: Re: HEADS UP: 3 days to E-day References: <199808271619.QAA01095@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > In about 3 days from now, we'll be committing the last of the bits > > that will enable people to convert from aout to elf. Satoshi has > > started calling this E-day. > > Go John! This makes you the E-man! 8) So who is the walrus? -- *** Chief Operations Officer, DALnet IRC network *** When you don't know where you're going, every road will take you there. - Yiddish Proverb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 17:42:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09116 for freebsd-current-outgoing; Thu, 27 Aug 1998 17:42:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09055 for ; Thu, 27 Aug 1998 17:41:55 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from dstc.edu.au (sleet.dstc.edu.au [130.102.176.45]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id KAA08772; Fri, 28 Aug 1998 10:40:56 +1000 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: current@FreeBSD.ORG Subject: Re: HEADS UP: 3 days to E-day In-reply-to: Your message of "Fri, 28 Aug 1998 09:08:09 +1000." <199808272308.JAA09047@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Aug 1998 10:40:55 +1000 Message-ID: <2989.904264855@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Be warned that the upgrade to elf will break ports. It will take some time for the ports crew to update all the ports makefiles to cater for the elf system. We hope that moving the installed libs from /usr/local/lib to /usr/local/lib/aout will not break the installed ports. There are too many combinations to test this out though. I'm an ould ould lazy codger. Can you give the one line canonical recipe for manually making a port or munging its makefile to make it make? Being elf could be rilly kule (tm) but loosing some o' dem ports is a pain. -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 17:55:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11531 for freebsd-current-outgoing; Thu, 27 Aug 1998 17:55:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mumford.stuy.edu (mumford.stuy.edu [149.89.1.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11514 for ; Thu, 27 Aug 1998 17:55:25 -0700 (PDT) (envelope-from galatalt@stuy.edu) Received: from nyc-ny76-09.ix.netcom.com (nyc-ny76-09.ix.netcom.com [209.109.228.137]) by mumford.stuy.edu (8.8.5/8.8.5) with SMTP id UAA25587; Thu, 27 Aug 1998 20:56:03 -0400 Date: Thu, 27 Aug 1998 20:54:08 -0400 (EDT) From: Tugrul Galatali X-Sender: galatalt@europa.novastar.com To: "Alok K. Dhir" cc: current@FreeBSD.ORG Subject: Re: Can't build perl In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Aug 1998, Alok K. Dhir wrote: > > Hey all - I tried to build perl5.005_02 both from the port and manually > today on 3.0-current as of yesterday. Both failed when trying to link > 'miniperl' with tons of these errors: > > > I've seen this happen on some other programs I've tried to compile lately > (ever since the move from /usr/lib to /usr/lib/aout). Mozilla CVS does this too. I've tried every permutation of gcc flags quickly concievable, help would rest this mind :) > > Any help? > > Thanks! > > Al > Tugrul Galatali To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 17:56:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11635 for freebsd-current-outgoing; Thu, 27 Aug 1998 17:56:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11583 for ; Thu, 27 Aug 1998 17:55:49 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id LAA09471; Fri, 28 Aug 1998 11:06:19 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808280106.LAA09471@cimlogic.com.au> Subject: Re: HEADS UP: 3 days to E-day In-Reply-To: <2989.904264855@dstc.edu.au> from George Michaelson at "Aug 28, 98 10:40:55 am" To: ggm@dstc.edu.au (George Michaelson) Date: Fri, 28 Aug 1998 11:06:19 +1000 (EST) Cc: jb@cimlogic.com.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG George Michaelson wrote: > I'm an ould ould lazy codger. Can you give the one line canonical recipe for > manually making a port or munging its makefile to make it make? Being elf > could be rilly kule (tm) but loosing some o' dem ports is a pain. A recipe in one line: Give ports people time to work through the issues. In more than one line: If you're one of those ports people, you'll have to try building the ports you maintain to find out what needs munging. Satoshi has asked for the elf switch to thrown sooner rather than later to give people as much time as possible to work on making ports elf aware. If you're discouraged by this, you don't need to convert to elf straight away, however you should be aware that as the ports are modified, elf will be the only supported format on 3.0-CURRENT and 3.0-RELEASE. If you want to keep using aout ports, you'll have to use 2.2.7 and 2.2.8 when it is released. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 18:16:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15100 for freebsd-current-outgoing; Thu, 27 Aug 1998 18:16:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15063 for ; Thu, 27 Aug 1998 18:16:39 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from support1.cybcon.com (william@support1.cybcon.com [205.147.76.99]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id SAA06589; Thu, 27 Aug 1998 18:15:36 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <35E5F7DD.A4213FBF@dal.net> Date: Thu, 27 Aug 1998 18:15:31 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: Studded Subject: Re: HEADS UP: 3 days to E-day Cc: current@FreeBSD.ORG, John Birrell , Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Question.....the ports we already have will still function, correct ? On 28-Aug-98 Studded wrote: > Mike Smith wrote: >> >> > In about 3 days from now, we'll be committing the last of the bits >> > that will enable people to convert from aout to elf. Satoshi has >> > started calling this E-day. >> >> Go John! This makes you the E-man! 8) > > So who is the walrus? > > -- > *** Chief Operations Officer, DALnet IRC network *** > > When you don't know where you're going, every road will take you there. > - Yiddish Proverb > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message --------------------- William Woods Date: 27-Aug-98 / Time: 18:14:55 goto to: http//www.freebsd.org. --> FreeBSD 3.0 CURRENT <-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 18:45:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20948 for freebsd-current-outgoing; Thu, 27 Aug 1998 18:45:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20919 for ; Thu, 27 Aug 1998 18:45:31 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-137.camalott.com [208.229.74.137]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id UAA21392; Thu, 27 Aug 1998 20:46:08 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id UAA26752; Thu, 27 Aug 1998 20:40:53 -0500 (CDT) (envelope-from joelh) Date: Thu, 27 Aug 1998 20:40:53 -0500 (CDT) Message-Id: <199808280140.UAA26752@detlev.UUCP> To: Jos.Backus@nl.origin-it.com CC: current@FreeBSD.ORG In-reply-to: <19980827095701.B5471@hal.mpn.cp.philips.com> (message from Jos Backus on Thu, 27 Aug 1998 09:57:01 +0200) Subject: Re: recovering disk From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808262046.WAA26730@semyam.dinoco.de> <199808262334.SAA13309@detlev.UUCP> <19980827095701.B5471@hal.mpn.cp.philips.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> You know what I'd like? A general disk editor, that can take its >> input by the block or by the file, with a hex editor as well as some >> special-purpose viewers. Something like Norton's Disk Editor. Said >> tool has been amazingly useful to me on many an occasion. > There's always http://www.pobox.com/~djb/software/ufsread-0.50.shar.gz, > although it is probably too fs-centric for this purpose... Not familiar with it; I'll take a look. I've been using fsdb, which is good for its job, but I want something with a little bit different. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 18:47:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21277 for freebsd-current-outgoing; Thu, 27 Aug 1998 18:47:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21244 for ; Thu, 27 Aug 1998 18:47:15 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id JAA04029; Fri, 28 Aug 1998 09:45:05 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id JAA17381; Fri, 28 Aug 1998 09:45:45 +0800 Message-Id: <199808280145.JAA17381@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: current@FreeBSD.ORG Subject: Re: HEADS UP: 3 days to E-day In-reply-to: Your message of "Fri, 28 Aug 1998 11:06:19 +1000." <199808280106.LAA09471@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Aug 1998 09:45:45 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > George Michaelson wrote: > In more than one line: If you're one of those ports people, you'll have > to try building the ports you maintain to find out what needs munging. > Satoshi has asked for the elf switch to thrown sooner rather than later > to give people as much time as possible to work on making ports elf > aware. If you're discouraged by this, you don't need to convert to elf > straight away, however you should be aware that as the ports are modified, > elf will be the only supported format on 3.0-CURRENT and 3.0-RELEASE. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Oh bother. I bought a copy of XIG's Motif 2.0 a couple of months ago. The CD has BSDI, FreeBSD & Linux binaries on it. The linux binaries are ELF, but I don't know how deeply libXm et cetera delve into linux's libc. I wonder if I could hit them for an upgrade when 3.0-RELEASE hits the street. Then there's the Xfree86 code to be rebuilt for ELF format. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 18:59:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23463 for freebsd-current-outgoing; Thu, 27 Aug 1998 18:59:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23412 for ; Thu, 27 Aug 1998 18:59:33 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-137.camalott.com [208.229.74.137]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id UAA22378; Thu, 27 Aug 1998 20:59:09 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id UAA27847; Thu, 27 Aug 1998 20:57:21 -0500 (CDT) (envelope-from joelh) Date: Thu, 27 Aug 1998 20:57:21 -0500 (CDT) Message-Id: <199808280157.UAA27847@detlev.UUCP> To: seggers@semyam.dinoco.de CC: jlemon@americantv.com, freebsd-current@FreeBSD.ORG, seggers@semyam.dinoco.de In-reply-to: <199808270841.KAA02095@semyam.dinoco.de> (message from Stefan Eggers on Thu, 27 Aug 1998 10:41:57 +0200) Subject: Re: Not receiving CVS commit messages From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808270841.KAA02095@semyam.dinoco.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> In any case, you can get the same functionality by subscribing >> to cvs-all, and using a procmail filter to weed out what you >> aren't interested in. > It's not the same. That would increase transfer times significantly > for me as I would have to transfer all log messages instead of just > the kernel related ones. It simply costs money I prefer to spend on > more useful things instead. > I am just interested in the kernel to get noticed when anything impor- > tant happens there. I don't care much about bugs in user land prog- > rams as they don't lead to the whole machine crashing. > To me cvs-all, cvs-bin, cvs-ports and cvs-sys sounds like a reasonable > way to split it. The hundreds of lists that previously existed are a > bit too much IMHO. I agree. Note also that I use the digest. I find it easier to concentrate when I see a batch of messages at once. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 19:00:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23479 for freebsd-current-outgoing; Thu, 27 Aug 1998 19:00:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23417 for ; Thu, 27 Aug 1998 18:59:34 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from support1.cybcon.com (william@support1.cybcon.com [205.147.76.99]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id SAA09041; Thu, 27 Aug 1998 18:58:25 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 27 Aug 1998 18:58:20 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: William Woods Subject: Re: HEADS UP: 3 days to E-day Cc: Mike Smith , John Birrell , current@FreeBSD.ORG, Studded Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Probably should have specified, the ports we have already compiled will still work, right ? On 28-Aug-98 William Woods wrote: > Question.....the ports we already have will still function, correct ? > > On 28-Aug-98 Studded wrote: >> Mike Smith wrote: >>> >>> > In about 3 days from now, we'll be committing the last of the bits >>> > that will enable people to convert from aout to elf. Satoshi has >>> > started calling this E-day. >>> >>> Go John! This makes you the E-man! 8) >> >> So who is the walrus? >> >> -- >> *** Chief Operations Officer, DALnet IRC network *** >> >> When you don't know where you're going, every road will take you there. >> - Yiddish Proverb >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message > > > --------------------- > William Woods > Date: 27-Aug-98 / Time: 18:14:55 > goto to: http//www.freebsd.org. > --> FreeBSD 3.0 CURRENT <-- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message --------------------- William Woods Date: 27-Aug-98 / Time: 18:57:49 goto to: http//www.freebsd.org. --> FreeBSD 3.0 CURRENT <-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 19:51:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03144 for freebsd-current-outgoing; Thu, 27 Aug 1998 19:51:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa5-11.ix.netcom.com [206.214.137.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03018 for ; Thu, 27 Aug 1998 19:50:38 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id TAA05275; Thu, 27 Aug 1998 19:49:24 -0700 (PDT) (envelope-from tomdean) Date: Thu, 27 Aug 1998 19:49:24 -0700 (PDT) Message-Id: <199808280249.TAA05275@ix.netcom.com> From: Thomas Dean To: current@FreeBSD.ORG Subject: Re: HEADS UP: 3 days to E-day Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to misunderstand the statement about make. On E-Day, will 'make world' create an elf system? I use SMP. I cannot afford to lose the ports. Should I freeze my system two days from now? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 20:16:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06834 for freebsd-current-outgoing; Thu, 27 Aug 1998 20:16:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06758 for ; Thu, 27 Aug 1998 20:16:26 -0700 (PDT) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id WAA15767; Thu, 27 Aug 1998 22:15:28 -0500 (CDT) Received: (from bruce@localhost) by zuhause.mn.org (8.8.8/8.8.7) id WAA04624; Thu, 27 Aug 1998 22:10:41 -0500 (CDT) From: Bruce Albrecht Date: Thu, 27 Aug 1998 22:10:41 -0500 (CDT) To: Ben Smithurst Cc: John Birrell , freebsd-current@FreeBSD.ORG Subject: Re: Problems building -current In-Reply-To: <19980827075342.A21285@scientia.demon.co.uk> References: <19980827052836.A22477@scientia.demon.co.uk> <199808270531.PAA05931@cimlogic.com.au> <19980827075342.A21285@scientia.demon.co.uk> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13798.8065.539559.789659@zuhause.zuhause.mn.org> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Smithurst writes: > John Birrell wrote: > > > make -m /usr/src/share/mk buildworld > > Thanks, but it still doesn't work, fails with the same error. Any > other ideas? Also make sure that . is not in your path. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 20:21:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07579 for freebsd-current-outgoing; Thu, 27 Aug 1998 20:21:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07508 for ; Thu, 27 Aug 1998 20:21:22 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id NAA09827; Fri, 28 Aug 1998 13:31:43 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808280331.NAA09827@cimlogic.com.au> Subject: Re: HEADS UP: 3 days to E-day In-Reply-To: from William Woods at "Aug 27, 98 06:15:31 pm" To: wwoods@cybcon.com Date: Fri, 28 Aug 1998 13:31:43 +1000 (EST) Cc: Studded@dal.net, current@FreeBSD.ORG, jb@cimlogic.com.au, mike@smith.net.au X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG William Woods wrote: > Question.....the ports we already have will still function, correct ? Yes. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 20:38:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09953 for freebsd-current-outgoing; Thu, 27 Aug 1998 20:38:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-96.ppp.wenet.net [206.15.84.96]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09882 for ; Thu, 27 Aug 1998 20:38:24 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id UAA02091; Thu, 27 Aug 1998 20:39:01 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 27 Aug 1998 20:39:01 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: William Woods cc: current Subject: Re: HEADS UP: 3 days to E-day In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Aug 1998, William Woods wrote: > Probably should have specified, the ports we have already compiled will still > work, right ? Yes. Since the enviroment variable LD_LIBRARY_PATH is shared by elf and a.out rtld (perhaps we should split that up), what I found useful was to create /usr/lib/aout/X11R6 and /usr/lib/aout/local, and drop these values into rc.conf. Then, I just added /usr/local/lib, et. al. to LD_LIBRARY_PATH. Somehow I wish there was a better solution. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 20:44:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11020 for freebsd-current-outgoing; Thu, 27 Aug 1998 20:44:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10957 for ; Thu, 27 Aug 1998 20:43:44 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id NAA09940; Fri, 28 Aug 1998 13:54:19 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808280354.NAA09940@cimlogic.com.au> Subject: Re: HEADS UP: 3 days to E-day In-Reply-To: <199808280249.TAA05275@ix.netcom.com> from Thomas Dean at "Aug 27, 98 07:49:24 pm" To: tomdean@ix.netcom.com (Thomas Dean) Date: Fri, 28 Aug 1998 13:54:19 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Dean wrote: > On E-Day, will 'make world' create an elf system? It will make whatever the system is configured to default as. The default is set by the file /etc/objectformat and the environment variable OBJFORMAT. If neither of these are configured, then the default is aout. So, to answer your question in another way, a make world on your system after E-day will continue to build aout and you'll never get any elf bits until you run the conversion. If you stay as aout after E-day, all your installed ports will continue to work, but any new ports you go to make will probably not build on your aout system if they have been converted to elf. > I use SMP. I cannot afford to lose the ports. Should I freeze my > system two days from now? Ports = yes. World = not necessarily, though that won't hurt. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 23:12:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00333 for freebsd-current-outgoing; Thu, 27 Aug 1998 23:12:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00312 for ; Thu, 27 Aug 1998 23:12:17 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id XAA17423; Thu, 27 Aug 1998 23:11:23 -0700 (PDT) (envelope-from jdp) Message-Id: <199808280611.XAA17423@austin.polstra.com> To: adhir@worldbank.org Subject: Re: Can't build perl In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 27 Aug 1998 23:11:22 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Alok K. Dhir wrote: > > Hey all - I tried to build perl5.005_02 both from the port and manually > today on 3.0-current as of yesterday. Both failed when trying to link > 'miniperl' with tons of these errors: > > cc -L/usr/local/lib -o miniperl miniperlmain.o libperl.a -lgdbm -lm -lc > -lcrypt > libperl.a(perl.o): Undefined symbol `___error' referenced (use -lc ?) > libperl.a(perl.o): Undefined symbol `_getpid' referenced (use -lc ?) > libperl.a(perl.o): Undefined symbol `_kill' referenced (use -lc ?) > libperl.a(perl.o): Undefined symbol `_fcntl' referenced (use -lc ?) > libperl.a(perl.o): Undefined symbol `_fstat' referenced (use -lc ?) > libperl.a(perl.o): Undefined symbol `_chdir' referenced (use -lc ?) > libperl.a(perl.o): Undefined symbol `_getuid' referenced (use -lc ?) > libperl.a(perl.o): Undefined symbol `_geteuid' referenced (use -lc ?) > libperl.a(perl.o): Undefined symbol `_getgid' referenced (use -lc ?) > libperl.a(perl.o): Undefined symbol `_getegid' referenced (use -lc ?) > libperl.a(perl.o): Undefined symbol `_stat' referenced (use -lc ?) > libperl.a(toke.o): Undefined symbol `___error' referenced (use -lc ?) > libperl.a(toke.o): Undefined symbol `_fcntl' referenced (use -lc ?) > libperl.a(util.o): Undefined symbol `_pipe' referenced (use -lc ?) > libperl.a(util.o): Undefined symbol `_fork' referenced (use -lc ?) > [*SNIP*] > > I've seen this happen on some other programs I've tried to compile lately > (ever since the move from /usr/lib to /usr/lib/aout). Do you still have your old a.out libraries in /usr/lib? If so, delete them. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 23:16:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00775 for freebsd-current-outgoing; Thu, 27 Aug 1998 23:16:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00747 for ; Thu, 27 Aug 1998 23:16:12 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id IAA10163; Fri, 28 Aug 1998 08:19:44 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Fri, 28 Aug 1998 08:19:43 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Julian Elischer cc: freebsd-current@FreeBSD.ORG Subject: Re: It's MFS panic.. (Re: Panic with DEVFS) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Aug 1998, Julian Elischer wrote: > > here.. try the following fix: > [...] Ouch! No, it's not quite right either... ------------------------ ... WOULD SELECT /wd1a but it doesn't exist /wd1s1a exists, I'll use that rootfs is 1600 Kbyte compiled in MFS Fatal double fault: eip=0xf017fd16 esp=0xf4003fe4 ebp=0xf4004000 panic: double fault ------------------------- The 'tr' command doesn't show anything before the dblfault is called in trap.c. The 'ps' doesn't show any process running except swapper (1,2,3,4), so it seems the panic is even before starting init(8). Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 27 23:16:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00819 for freebsd-current-outgoing; Thu, 27 Aug 1998 23:16:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00782 for ; Thu, 27 Aug 1998 23:16:21 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from ben by scientia.demon.co.uk with local (Exim 2.02 #20) id 0zCGwy-00043F-00 for freebsd-current@freebsd.org; Fri, 28 Aug 1998 06:19:52 +0100 Date: Fri, 28 Aug 1998 06:19:52 +0100 From: Ben Smithurst To: freebsd-current@FreeBSD.ORG Subject: Re: Problems building -current Message-ID: <19980828061952.A14606@scientia.demon.co.uk> References: <19980827052836.A22477@scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: <19980827052836.A22477@scientia.demon.co.uk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: [various error messages] > Any ideas? Sorry if this is a basic question but I'm new to -current. Turns out I must have broken something, dunno what though. Reinstalled my /usr/{lib,libdata,libexec,bin,include,sbin} directories from the 2.2.6 CD, and it works now. (at least, it's got further than it did before, knowing my luck something else will break later.) Suppose I should have known to do it from a clean system, oh well. thanks to those who helped anyway. -- Ben Smithurst : ben@scientia.demon.co.uk : http://www.scientia.demon.co.uk/ PGP: 0x99392F7D - 3D 89 87 42 CE CA 93 4C 68 32 0E D5 36 05 3D 16 http://www.scientia.demon.co.uk/ben/pgp-key.html (or use keyservers) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 01:09:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14881 for freebsd-current-outgoing; Fri, 28 Aug 1998 01:09:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from grape.carrier.kiev.ua (grape.carrier.kiev.ua [193.193.193.219]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14872 for ; Fri, 28 Aug 1998 01:09:30 -0700 (PDT) (envelope-from archer@grape.carrier.kiev.ua) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.9.1/8.8.8) id LAA00123; Fri, 28 Aug 1998 11:08:06 +0300 (EEST) (envelope-from archer) Date: Fri, 28 Aug 1998 11:08:06 +0300 (EEST) From: Alexander Litvin Message-Id: <199808280808.LAA00123@grape.carrier.kiev.ua> To: Archie Cobbs Cc: current@FreeBSD.ORG Subject: Re: encountered possible VM bug ? X-Newsgroups: grape.freebsd.current In-Reply-To: <199808272051.NAA27400@bubba.whistle.com> Organization: Lucky Grape User-Agent: tin/pre-1.4-980202 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199808272051.NAA27400@bubba.whistle.com> you wrote: >> GW> No, this is the ``daemons dying'' bug which nobody has fixed yet. >> GW> When the system runs out of swap, some random selection of processes >> GW> which are in swap get corrupted. Usually this results in a daemon >> GW> which dies whenever it fork()s, but sometimes it is manifested as >> GW> other sorts of corruption. The message you see from realloc is >> GW> indicative of a corrupted pointer. >> >> Really, I was under impression, that it is the problem just with fork(). >> But now I may confirm that processes get corrupted in different manners. >> E.g., I have now a specially written dummy daemon running, which I >> was able to corrupt (intentionally exhausting swap) in such a way that >> it successfully forks. Than child process sleeps (just to give me >> chance to attach to it with debugger), allocates memory, accesses it >> -- and during all that it doesn't get SIGSEGV. But then it dies when >> trying to syslog(3). It seems that the corruption is in mmaped ld.so >> or libc.3.1.so. >> >> If anybody cares, I may try to give any other details. AC> At Whistle, we've seen this bug every so often for a long time. AC> The common elements seem to be: AC> 1. memory mapping is in use AC> 2. a fork() is happening or just happened AC> But #1 and #2 are not necessarily both related to the same process. AC> This bug has been around for a *long* time, in both 2.x and 3.x. I saw bash exiting with SIGSEGV. It was not trying to fork some job. It was swapped out, I just hit , and it exited with signal 11. Cron sometimes seem to just stop forking cron jobs, when it is not segfaulting -- it just doesn't try to fork. AC> Running out of swap may or may not be related, not sure... I think AC> we've seen this when swap was not an issue. Perhaps running out of AC> swap amplifies the problem. AC> It's really hard to pin down, because the panic seems to come a AC> while after the initial damage is done. We've seen random processes AC> crashing every time they try to fork(), kernel panic's because of AC> some process being on two different queues at the same time (eg, AC> sleep and runnable), and other manifestations. AC> A common manifestation is that a file being written out contains AC> some random page of memory from some other file -- we think the other AC> file is a currently mmap'd file. In my case it seems that the process have some of its pages zeroed. At least here's the simpthom (I have it still running and segfaulting -- for investigation ;): root:~/dummy_daemon:grape:> gdb dummy_daemon 29643 [...] Attaching to program `/usr/home/archer/dummy_daemon/dummy_daemon', process 29643 Reading symbols from /usr/libexec/ld.so...done. Reading symbols from /usr/lib/aout/libc.so.3.1...done. Error accessing memory address 0x0: Bad address. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ What exactly does that line mean? When I attach to not deseased dummy_daemon, it does not appear, instead I see: 0x20057c21 in nanosleep () AC> Julian and Terry can supply more details. AC> -Archie AC> ___________________________________________________________________________ AC> Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com --- It's lucky you're going so slowly, because you're going in the wrong direction. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 01:22:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16305 for freebsd-current-outgoing; Fri, 28 Aug 1998 01:22:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (castles24.castles.com [208.214.165.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16291 for ; Fri, 28 Aug 1998 01:22:10 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id BAA03086; Fri, 28 Aug 1998 01:19:09 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808280119.BAA03086@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Alexander Litvin cc: Archie Cobbs , current@FreeBSD.ORG Subject: Re: encountered possible VM bug ? In-reply-to: Your message of "Fri, 28 Aug 1998 11:08:06 +0300." <199808280808.LAA00123@grape.carrier.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Aug 1998 01:19:08 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Reading symbols from /usr/libexec/ld.so...done. > Reading symbols from /usr/lib/aout/libc.so.3.1...done. > > Error accessing memory address 0x0: Bad address. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > What exactly does that line mean? When I attach to not deseased dummy_daemon, > it does not appear, instead I see: It means that the instruction pointer obtained for the process is 0, which is invalid. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 02:03:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA21281 for freebsd-current-outgoing; Fri, 28 Aug 1998 02:03:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20746 for ; Fri, 28 Aug 1998 01:59:36 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id WAA03277; Thu, 27 Aug 1998 22:19:57 -0400 (EDT) Date: Thu, 27 Aug 1998 22:19:57 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Stephen Hocking-Senior Programmer PGS Tensor Perth cc: John Birrell , current@FreeBSD.ORG Subject: Re: HEADS UP: 3 days to E-day In-Reply-To: <199808280145.JAA17381@ariadne.tensor.pgs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Aug 1998, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > George Michaelson wrote: > > > In more than one line: If you're one of those ports people, you'll have > > to try building the ports you maintain to find out what needs munging. > > Satoshi has asked for the elf switch to thrown sooner rather than later > > to give people as much time as possible to work on making ports elf > > aware. If you're discouraged by this, you don't need to convert to elf > > straight away, however you should be aware that as the ports are modified, > > elf will be the only supported format on 3.0-CURRENT and 3.0-RELEASE. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Oh bother. I bought a copy of XIG's Motif 2.0 a couple of months > ago. The CD has BSDI, FreeBSD & Linux binaries on it. The linux > binaries are ELF, but I don't know how deeply libXm et cetera delve > into linux's libc. I wonder if I could hit them for an upgrade when No, they don't have a new one. I just checked. The salesman wasn't sure if they'd tracked 2.2.5 or 2.2.6 with the last one, but don't hold your breath. > 3.0-RELEASE hits the street. Then there's the Xfree86 code to be > rebuilt for ELF format. > > > Stephen > -- > The views expressed above are not those of PGS Tensor. > > "We've heard that a million monkeys at a million keyboards could produce > the Complete Works of Shakespeare; now, thanks to the Internet, we know > this is not true." Robert Wilensky, University of California > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 02:50:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26066 for freebsd-current-outgoing; Fri, 28 Aug 1998 02:50:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26058 for ; Fri, 28 Aug 1998 02:50:29 -0700 (PDT) (envelope-from archer@grape.carrier.kiev.ua) Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111]) by burka.carrier.kiev.ua (8.9.0/8.Who.Cares) with ESMTP id MAA03552; Fri, 28 Aug 1998 12:49:27 +0300 (EEST) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id MAA05118; Fri, 28 Aug 1998 12:42:11 +0300 (EEST) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.9.1/8.8.8) id MAA01591; Fri, 28 Aug 1998 12:24:31 +0300 (EEST) (envelope-from archer) Message-ID: <19980828122431.14123@carrier.kiev.ua> Date: Fri, 28 Aug 1998 12:24:31 +0300 From: Alexander Litvin To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: encountered possible VM bug ? References: <199808280808.LAA00123@grape.carrier.kiev.ua> <199808280119.BAA03086@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199808280119.BAA03086@word.smith.net.au>; from Mike Smith on Fri, Aug 28, 1998 at 01:19:08AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 28, 1998 at 01:19:08AM +0000, Mike Smith wrote: > > Reading symbols from /usr/libexec/ld.so...done. > > Reading symbols from /usr/lib/aout/libc.so.3.1...done. > > > > Error accessing memory address 0x0: Bad address. > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > What exactly does that line mean? When I attach to not deseased dummy_daemon, > > it does not appear, instead I see: > > It means that the instruction pointer obtained for the process is 0, > which is invalid. Do you mean eip register? 'info registers' show: eax 0xf0 240 ecx 0x4 4 edx 0x1 1 ebx 0x20084060 537411680 esp 0xefbfdbd0 0xefbfdbd0 ebp 0xefbfdbf4 0xefbfdbf4 esi 0x3c 60 edi 0x0 0 eip 0x20057c21 0x20057c21 eflags 0x282 642 cs 0x1f 31 ss 0x27 39 ds 0x27 39 es 0x27 39 fs 0x27 39 gs 0x27 39 That is, eip is pinting to the same address 0x20057c21, as it is for 'healthy' copy of the program. The code under 0x20057c21 seems to be in place. > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > --- Happiness, n.: An agreeable sensation arising from contemplating the misery of another. -- Ambrose Bierce, "The Devil's Dictionary" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 03:57:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA01278 for freebsd-current-outgoing; Fri, 28 Aug 1998 03:57:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01269 for ; Fri, 28 Aug 1998 03:56:59 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id MAA19359; Fri, 28 Aug 1998 12:55:58 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 28 Aug 1998 12:55:56 +0200 (MET DST) Mime-Version: 1.0 To: Stefan Eggers Cc: Jonathan Lemon , freebsd-current@FreeBSD.ORG Subject: Re: Not receiving CVS commit messages References: <199808270841.KAA02095@semyam.dinoco.de> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 28 Aug 1998 12:55:54 +0200 In-Reply-To: Stefan Eggers's message of "Thu, 27 Aug 1998 10:41:57 +0200" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA01274 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stefan Eggers writes: > To me cvs-all, cvs-bin, cvs-ports and cvs-sys sounds like a reasonable > way to split it. The hundreds of lists that previously existed are a > bit too much IMHO. I'd suggest cvs-doc too (for doc and www). I read committers (which is equivalent to cvs-all), but I score down everything that has a subject line =~ "commit: (doc|www|ports)/.*". I don't killfile it, though - once in a while something shows up that interests me. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 04:33:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA07122 for freebsd-current-outgoing; Fri, 28 Aug 1998 04:33:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA07113 for ; Fri, 28 Aug 1998 04:33:35 -0700 (PDT) (envelope-from croot@btp1da.phy.uni-bayreuth.de) Received: (from root@localhost) by btp1da.phy.uni-bayreuth.de (8.8.8/8.7.3) id NAA28379 for current@freebsd.org; Fri, 28 Aug 1998 13:32:23 +0200 (MEST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 28 Aug 1998 13:32:23 +0200 (MEST) Organization: university of bayreuth From: Werner Griessl To: current@FreeBSD.ORG Subject: rc and nfs-mounts problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ---------------------------------- E-Mail: Werner Griessl Date: 28-Aug-98 Time: 13:25:10 This message was sent by XFMail ---------------------------------- In /etc/rc the nfsmounts now are too early after network_pass1. The sequence: echo -n "Mounting NFS file systems" mount -a -t nfs echo . should be done after network_pass3 . Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 05:47:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13312 for freebsd-current-outgoing; Fri, 28 Aug 1998 05:47:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA13292 for ; Fri, 28 Aug 1998 05:47:04 -0700 (PDT) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id HAA07905 for ; Fri, 28 Aug 1998 07:46:07 -0500 (CDT) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma007892; Fri, 28 Aug 98 07:45:57 -0500 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with SMTP id HAA11522 for ; Fri, 28 Aug 1998 07:45:57 -0500 (CDT) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Fri, 28 Aug 1998 07:45:56 -0500 (CDT) From: Kyle Mestery To: freebsd-current@FreeBSD.ORG Subject: Make problem/User error Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running a current system from: FreeBSD khyrone.winternet.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Wed Jun 3 21:10:37 CDT 1998 mestery@khyrone.winternet.com:/usr/src/sys/compile/KHYRONE i386 I went to do a buildworld today, but first tried to do a clean. The build process continually stops when clean tries to clean directories that have been added since the last time I built world. I track the cvs tree, and did a cvs update src before I built. Shouldn't that have added the new directories? Thanks. Error below: ===> lib/libstand cd: can't cd to /usr/src/lib/libstand *** Error code 2 Stop. *** Error code 1 Stop. -- Kyle Mestery StorageTek's Storage Networking Group "I'll take what you're willing to give, and I'll teach myself to live, with a walk-on part of a background shot from a movie I'm not in." - Blink 182, "Apple Shampoo" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 06:12:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15998 for freebsd-current-outgoing; Fri, 28 Aug 1998 06:12:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA15991 for ; Fri, 28 Aug 1998 06:12:38 -0700 (PDT) (envelope-from nrahlstr@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id IAA11277; Fri, 28 Aug 1998 08:11:41 -0500 (CDT) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma011256; Fri, 28 Aug 98 08:11:20 -0500 Received: from localhost (nrahlstr@localhost) by tundra.winternet.com (8.8.7/8.8.4) with SMTP id IAA11742; Fri, 28 Aug 1998 08:11:19 -0500 (CDT) X-Authentication-Warning: tundra.winternet.com: nrahlstr owned process doing -bs Date: Fri, 28 Aug 1998 08:11:19 -0500 (CDT) From: Nathan Ahlstrom To: Kyle Mestery cc: freebsd-current@FreeBSD.ORG Subject: Re: Make problem/User error In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > did a cvs update src before I built. Shouldn't that have added the new > directories? Thanks. Error below: did you run? cvs update -d To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 06:15:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16365 for freebsd-current-outgoing; Fri, 28 Aug 1998 06:15:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16360 for ; Fri, 28 Aug 1998 06:15:45 -0700 (PDT) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id IAA11712; Fri, 28 Aug 1998 08:14:49 -0500 (CDT) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma011695; Fri, 28 Aug 98 08:14:35 -0500 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with SMTP id IAA11774; Fri, 28 Aug 1998 08:14:33 -0500 (CDT) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Fri, 28 Aug 1998 08:14:33 -0500 (CDT) From: Kyle Mestery To: Nathan Ahlstrom cc: freebsd-current@FreeBSD.ORG Subject: Re: Make problem/User error In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Aug 1998, Nathan Ahlstrom wrote: > > > did a cvs update src before I built. Shouldn't that have added the new > > directories? Thanks. Error below: > > did you run? > > cvs update -d > I will try this now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 06:55:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19790 for freebsd-current-outgoing; Fri, 28 Aug 1998 06:55:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19784 for ; Fri, 28 Aug 1998 06:55:54 -0700 (PDT) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.9.1/8.8.8) with SMTP id JAA03470; Fri, 28 Aug 1998 09:54:28 -0400 (EDT) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Fri, 28 Aug 1998 09:54:28 -0400 (EDT) From: "Alok K. Dhir" To: John Polstra cc: Alok_K._Dhir/Person/World_Bank@notes.worldbank.org, current@FreeBSD.ORG Subject: Re: Can't build perl In-Reply-To: <1204029794ACF0468525666E0024E306.0023772C8525666E@worldbank.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Aug 1998, John Polstra wrote: > Do you still have your old a.out libraries in /usr/lib? If so, > delete them. No - nothing in /usr/lib except: [shadow:~] ls /usr/lib X11@ aout/ compat/ libOSSlib.a@ locale/ Thanks for the help... Al To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 07:08:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20675 for freebsd-current-outgoing; Fri, 28 Aug 1998 07:08:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20670 for ; Fri, 28 Aug 1998 07:08:48 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca6-88.ix.netcom.com [205.186.213.88]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id HAA26747; Fri, 28 Aug 1998 07:07:49 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id HAA25052; Fri, 28 Aug 1998 07:07:46 -0700 (PDT) Date: Fri, 28 Aug 1998 07:07:46 -0700 (PDT) Message-Id: <199808281407.HAA25052@silvia.hip.berkeley.edu> To: jb@cimlogic.com.au CC: ggm@dstc.edu.au, jb@cimlogic.com.au, current@FreeBSD.ORG In-reply-to: <199808280106.LAA09471@cimlogic.com.au> (message from John Birrell on Fri, 28 Aug 1998 11:06:19 +1000 (EST)) Subject: Re: HEADS UP: 3 days to E-day From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: John Birrell * A recipe in one line: Give ports people time to work through the issues. Thanks. :) * In more than one line: If you're one of those ports people, you'll have * to try building the ports you maintain to find out what needs munging. * Satoshi has asked for the elf switch to thrown sooner rather than later * to give people as much time as possible to work on making ports elf * aware. If you're discouraged by this, you don't need to convert to elf * straight away, however you should be aware that as the ports are modified, * elf will be the only supported format on 3.0-CURRENT and 3.0-RELEASE. * If you want to keep using aout ports, you'll have to use 2.2.7 and 2.2.8 * when it is released. Clarification. There will only be ELF *packages* in 3.0R (and packages-current from E-day on -- Justin, do you want to run one final build of a.out packages before you throw the switch?). However, *ports* will continue to support both a.out and ELF worlds. This is because the ports tree is shared between 2.2 and 3.0 branches. Thus, after E-day, as ports are converted, you should be able to build either a.out or ELF packages on your -current system. Note the "as ports are converted" in the previous paragraph. We have no idea how long it will take for us to fix all the ports (or even only the important ones). There are too many of them that create shared libraries and there's just not enough time before the release. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 07:17:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21937 for freebsd-current-outgoing; Fri, 28 Aug 1998 07:17:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bsd.mbp.ee (bsd.mbp.ee [194.204.12.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21928 for ; Fri, 28 Aug 1998 07:17:55 -0700 (PDT) (envelope-from mauri@mbp.ee) Received: from nw1.mbp.ee (nw1.mbp.ee [194.204.12.68]) by bsd.mbp.ee (8.8.8/8.8.8) with ESMTP id RAA07444 for ; Fri, 28 Aug 1998 17:16:56 +0300 (EEST) (envelope-from mauri@mbp.ee) Message-Id: <199808281416.RAA07444@bsd.mbp.ee> Received: from SERVER/SpoolDir by nw1.mbp.ee (Mercury 1.43); 28 Aug 98 17:17:00 +0300 Received: from SpoolDir by SERVER (Mercury 1.43); 28 Aug 98 17:16:40 +0300 From: "Lauri Laupmaa" Organization: =?ISO-8859-1?Q?ripeva_Kirjastuse_AS?= To: current@FreeBSD.ORG Date: Fri, 28 Aug 1998 17:16:26 +0300 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Subject: Directory not empty ? X-mailer: Pegasus Mail for Win32 (v3.01b) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from Quoted-printable to 8bit by hub.freebsd.org id HAA21933 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Running current as of Fri Jul 24 13:28:09 EEST I am sure /usr/obj/usr/src/gnu/lib/libgmp/ IS empty but: bash-2.02# rm -rf /usr/obj/ rm: /usr/obj/usr/src/gnu/lib/libgmp/: Directory not empty rm: /usr/obj/usr/src/gnu/lib: Directory not empty rm: /usr/obj/usr/src/gnu: Directory not empty rm: /usr/obj/usr/src: Directory not empty rm: /usr/obj/usr: Directory not empty rm: /usr/obj/: Directory not empty ______________ Lauri Laupmaa Äripäev mauri@mbp.ee Ph. +372 66 70 369 +372 50 13 369 Fx. +372 66 70 165 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 08:10:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28568 for freebsd-current-outgoing; Fri, 28 Aug 1998 08:10:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bsd.mbp.ee (bsd.mbp.ee [194.204.12.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28563 for ; Fri, 28 Aug 1998 08:10:48 -0700 (PDT) (envelope-from mauri@mbp.ee) Received: from nw1.mbp.ee (nw1.mbp.ee [194.204.12.68]) by bsd.mbp.ee (8.8.8/8.8.8) with ESMTP id SAA07715 for ; Fri, 28 Aug 1998 18:09:54 +0300 (EEST) (envelope-from mauri@mbp.ee) Message-Id: <199808281509.SAA07715@bsd.mbp.ee> Received: from SERVER/SpoolDir by nw1.mbp.ee (Mercury 1.43); 28 Aug 98 18:09:55 +0300 Received: from SpoolDir by SERVER (Mercury 1.43); 28 Aug 98 18:09:44 +0300 From: "Lauri Laupmaa" Organization: =?ISO-8859-1?Q?ripeva_Kirjastuse_AS?= To: current@FreeBSD.ORG Date: Fri, 28 Aug 1998 18:09:27 +0300 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Subject: Re: Directory not empty ? References: Your message of "Fri, 28 Aug 1998 17:16:26 +0300." <199808281416.RAA07444@bsd.mbp.ee> In-reply-to: <18611.904316010@axl.training.iafrica.com> X-mailer: Pegasus Mail for Win32 (v3.01b) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from Quoted-printable to 8bit by hub.freebsd.org id IAA28564 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28 Aug 98, at 16:53, Sheldon Hearn wrote: > Try this: > > chflags -R noschg /usr/obj ; rm -rf /usr/obj That did NOT help, I've done that... ______________ Lauri Laupmaa Äripäev mauri@mbp.ee Ph. +372 66 70 369 +372 50 13 369 Fx. +372 66 70 165 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 09:43:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14302 for freebsd-current-outgoing; Fri, 28 Aug 1998 09:43:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14291 for ; Fri, 28 Aug 1998 09:43:31 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id MAA18288 for ; Fri, 28 Aug 1998 12:42:38 -0400 (EDT) Date: Fri, 28 Aug 1998 12:42:38 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: current@FreeBSD.ORG Subject: problems building current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- amd --- cc -O2 -pipe -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd/amd -I. -I/usr/src/usr.sbin/amd/amd -I/usr/src/usr.sbin/amd/amd/../include -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd/include -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd -DHAVE_CONFIG_H -I/usr/obj/usr/src/tmp/usr/include -o amd conf_parse.o conf_tok.o am_ops.o amd.o amfs_auto.o amfs_direct.o amfs_error.o amfs_host.o amfs_inherit.o amfs_link.o amfs_linkx.o amfs_nfsl.o amfs_nfsx.o amfs_program.o amfs_root.o amfs_toplvl.o amfs_union.o amq_subr.o amq_svc.o autil.o clock.o conf.o get_args.o info_file.o info_ndbm.o info_nis.o info_passwd.o info_union.o map.o mapc.o mntfs.o nfs_prot_svc.o nfs_start.o nfs_subr.o ops_cdfs.o ops_lofs.o ops_mfs.o ops_nfs.o ops_nfs3.o ops_nullfs.o ops_pcfs.o ops_tfs.o ops_ufs.o ops_umapfs.o ops_unionfs.o opts.o restart.o rpc_fwd.o sched.o srvr_amfs_auto.o srvr_nfs.o mount_xdr.o --- xwhere --- /usr/src/usr.sbin/amd/libamu/obj/libamu.a -lrpcsvc cc: xwhere: No such file or directory *** Error code 1 1 error Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 10:15:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18754 for freebsd-current-outgoing; Fri, 28 Aug 1998 10:15:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18737 for ; Fri, 28 Aug 1998 10:15:26 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA08962; Fri, 28 Aug 1998 10:01:42 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdCq8933; Fri Aug 28 17:01:32 1998 Date: Fri, 28 Aug 1998 10:01:27 -0700 (PDT) From: Julian Elischer To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: It's MFS panic.. (Re: Panic with DEVFS) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG yeah I figured it out... infinite recursion..... oops I need to think about this a bit.. julian On Fri, 28 Aug 1998, Andrzej Bialecki wrote: > > On Thu, 27 Aug 1998, Julian Elischer wrote: > > > > > here.. try the following fix: > > > [...] > > Ouch! No, it's not quite right either... > > ------------------------ > ... > WOULD SELECT /wd1a but it doesn't exist > /wd1s1a exists, I'll use that > rootfs is 1600 Kbyte compiled in MFS > > Fatal double fault: > eip=0xf017fd16 > esp=0xf4003fe4 > ebp=0xf4004000 > panic: double fault > ------------------------- > > The 'tr' command doesn't show anything before the dblfault is called in > trap.c. > > The 'ps' doesn't show any process running except swapper (1,2,3,4), so it > seems the panic is even before starting init(8). > > Andrzej Bialecki > > +---------------------+------------------------+--------------------------+ > | | When in problem or in | if(halt_per_mth > 0) { | > | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | > | Network in Poland | scream and shout. | } | > + --------------------+------------------------+--------------------------+ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 11:44:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29539 for freebsd-current-outgoing; Fri, 28 Aug 1998 11:44:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29493 for ; Fri, 28 Aug 1998 11:43:48 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA12602; Fri, 28 Aug 1998 11:31:31 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdl12569; Fri Aug 28 18:31:19 1998 Date: Fri, 28 Aug 1998 11:31:09 -0700 (PDT) From: Julian Elischer To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: It's MFS panic.. (Re: Panic with DEVFS) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been thinking about this.... could you make a -g kernel? (config -g) and strip -d the copy you eventually use then use the unstripped version to get the symbols from the coredump... I really need to see the value of ap->a_vn and the vnode that it points to.. On Thu, 27 Aug 1998, Andrzej Bialecki wrote: > > On Wed, 26 Aug 1998, Andrzej Bialecki wrote: > > > I'm totally lame when it comes to FS internals, but this looks to me > > as if some delayed action (caching? cleaning? read-ahead? whatever?) > > is causing this. > > ...but it looks like I was right after all. Below is the trace (no > crashdump available yet - I'm working on it). Source tree is about four > days old. > > One important notice, though: this time I was able to reliably crash > _without_ disabling any device, and even when not touching /dev at all - > it was enough to do just an 'ls -l' of some directory a few times to > produce sufficient number of dirty pages... The only thing that is common > in all these cases is: > > * root on MFS > * DEVFS/SLICE kernel > > and it seems these two definitely don't like each other.. :-( > > So, here's the stack trace (taken by hand.. :-<< ): > > _panic() > _mfs_strategy(ap=...) at _mfs_strategy+0x3c [../../ufs/mfs/mfs_vnops.c:137] > _bwrite(bp=...) at _bwrite+0xaf [../../kern/vfs_bio.c:891] > * _vop_stdbwrite(ap=...) at _vop_defaultop+0x15 [../../kern/vfs_default.c:131] > * _bawrite(bp=...) at _bawrite+0x2c [../../kern/vfs_bio.c:1122] > * _spec_fsync(ap=...) at _spec_fsync+0x76 [../../miscfs/specfs/spec_vnops.c:509] > _mfs_fsync(ap=...) at _mfs_fsync+0x16 [../../ufs/mfs/mfs_vnops.c:118] > _sched_sync() at _sched_sync+0xa4 [../../kern/vfs_subr.c:499] > _kproc_start(udata=...) at _kproc_start+0x32 [../../kern/init_main.c:248] > _fork_trampoline(...,...,...,...,...) at _fork_trampoline+0x30 > > The lines marked with stars ('*') in other panics were replaced with the > following lines: > > _vop_stdbwrite(ap=...) at _vop_stdbwrite+0xe [../../kern/vfs_default.c:285] > _vop_defaultop(ap=...) at _vop_defaultop+0x15 [../../kern/vfs_default.c:131] > _vfs_bio_awrite(bp=...) at _vfs_bio_awrite+0x103 [../../kern/vfs_bio.c:1122] > _spec_fsync(ap=...) at _spec_fsync+0x1e [../../miscfs/specfs/spec_vnops.c:503] > > I also tried to do a 'show object' which printed: > > db> show object > Object 0xf019bb75: type=1694529634, size=0x65007864, res=1166738538, ret=1694529635, flags=0x7363 > > Fatal trap 12: page fault while in kernel mode > ... > fault code = supervisor read, page not present > ... > current process = 4 (syncer) > interrupt mask = bio > > and at this point I gave up... > > I'll try to get the coredump, if you're interested in having it... > > Andrzej Bialecki > > +---------------------+------------------------+--------------------------+ > | | When in problem or in | if(halt_per_mth > 0) { | > | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | > | Network in Poland | scream and shout. | } | > + --------------------+------------------------+--------------------------+ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 12:51:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09427 for freebsd-current-outgoing; Fri, 28 Aug 1998 12:51:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from silky.cs.indiana.edu (silky.cs.indiana.edu [129.79.253.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09422 for ; Fri, 28 Aug 1998 12:51:10 -0700 (PDT) (envelope-from chiuk@cs.indiana.edu) Received: (from chiuk@localhost) by silky.cs.indiana.edu (8.8.7/8.8.7/IUCS_2.18) id OAA23290; Fri, 28 Aug 1998 14:50:15 -0500 (EST) Date: Fri, 28 Aug 1998 14:50:09 -0500 (EST) From: Kenneth Chiu X-Sender: ken@localhost To: current@FreeBSD.ORG cc: Stephen Hocking-Senior Programmer PGS Tensor Perth , John Birrell , Chuck Robey Subject: Re: HEADS UP: 3 days to E-day In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Aug 1998, Chuck Robey wrote: > On Fri, 28 Aug 1998, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > > > Oh bother. I bought a copy of XIG's Motif 2.0 a couple of months > > ago. The CD has BSDI, FreeBSD & Linux binaries on it. The linux > > binaries are ELF, but I don't know how deeply libXm et cetera delve > > into linux's libc. I wonder if I could hit them for an upgrade when > > No, they don't have a new one. I just checked. The salesman wasn't > sure if they'd tracked 2.2.5 or 2.2.6 with the last one, but don't hold > your breath. I'm thinking about getting Motif, but am concerned about being dependent on XIG for a 3.0 version. First, how hard would it be to write a program to convert a.out to ELF? Is it just a matter of converting the relocation table, symbol table, and string table? Or will the 3.0 loader be able to mix and match ELF and a.out? Second, even if the library was converted to ELF, would a 2.2.X libXm library work on a 3.0 system? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 14:32:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26277 for freebsd-current-outgoing; Fri, 28 Aug 1998 14:32:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26259 for ; Fri, 28 Aug 1998 14:32:33 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA19383 for ; Fri, 28 Aug 1998 14:18:37 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdS19370; Fri Aug 28 21:18:34 1998 Date: Fri, 28 Aug 1998 14:18:22 -0700 (PDT) From: Julian Elischer To: current@FreeBSD.ORG Subject: FS gurus please.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's a question for those who have their heads more around the filesystems.. Why does MFS unconditionally call spec_fsync() on all vnodes? One presumes that since it's a memory filesysytem, fsync should do nothing.. I'm also curious why it doesn't even check that it's a vnode for a special device. What do we gain by calling spec_fsync on a normal file in an MFS? I can understand that possibly it should be trying to sync the superblocks etc from mounted devices where the device is on an MFS /dev. In that case shouldn't it be checking the vnode types? This has been worked on by several people so hopefully there is someone out there who can give me answers tothese questions.. also: MFS also calls spec_getpages in the same way, which eventually comes back through a VOP_STRATEGY to mfs_strategey(). does this make sense? I'm trying to make systems that don't HAVE specfs and also to fix an interaction between specfs and devfs/slice. It appears that the fsync() interaction could easily be solved by makinf mfs_fsync() a nop (why not?) and the mfs_getpages dependency should be fixed by importing the relevant code from spec_getpages into mfs_getpages and optimising it.. Can I have comments from the gallery please? I'm a mu limits of understanding on this and probably need assistance. What am I missing....? julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 14:59:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28969 for freebsd-current-outgoing; Fri, 28 Aug 1998 14:59:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28920 for ; Fri, 28 Aug 1998 14:58:22 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id QAA06594; Fri, 28 Aug 1998 16:51:39 -0400 (EDT) Date: Fri, 28 Aug 1998 16:51:39 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Kenneth Chiu cc: current@FreeBSD.ORG, Stephen Hocking-Senior Programmer PGS Tensor Perth , John Birrell Subject: Re: HEADS UP: 3 days to E-day In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Aug 1998, Kenneth Chiu wrote: > On Thu, 27 Aug 1998, Chuck Robey wrote: > > On Fri, 28 Aug 1998, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > > > > > Oh bother. I bought a copy of XIG's Motif 2.0 a couple of months > > > ago. The CD has BSDI, FreeBSD & Linux binaries on it. The linux > > > binaries are ELF, but I don't know how deeply libXm et cetera delve > > > into linux's libc. I wonder if I could hit them for an upgrade when > > > > No, they don't have a new one. I just checked. The salesman wasn't > > sure if they'd tracked 2.2.5 or 2.2.6 with the last one, but don't hold > > your breath. > > I'm thinking about getting Motif, but am concerned about being > dependent on XIG for a 3.0 version. First, how hard would it be > to write a program to convert a.out to ELF? Is it just a matter > of converting the relocation table, symbol table, and string table? > Or will the 3.0 loader be able to mix and match ELF and a.out? > > Second, even if the library was converted to ELF, would a 2.2.X > libXm library work on a 3.0 system? At the moment, they only have aout libs for FreeBSD. I'll have to write them and give them a nudge. Motif'll still work, but you'll have to link aout. I don't think you can mix aout and ELF linkage. You won't lose anything you have now ... On top of that, their tech support is pretty good, and they let me upgrade from their 1.2 Motif to the 2.0 version a while back for about $20 bucks. I don't figure they'll leave the product behind. > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 15:47:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04368 for freebsd-current-outgoing; Fri, 28 Aug 1998 15:47:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04332 for ; Fri, 28 Aug 1998 15:47:06 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.7/8.7.3) id PAA27708; Fri, 28 Aug 1998 15:45:47 -0700 (PDT) Date: Fri, 28 Aug 1998 15:45:47 -0700 (PDT) Message-Id: <199808282245.PAA27708@vader.cs.berkeley.edu> To: chiuk@cs.indiana.edu CC: current@FreeBSD.ORG, shocking@prth.pgs.com, jb@cimlogic.com.au, chuckr@glue.umd.edu In-reply-to: (message from Kenneth Chiu on Fri, 28 Aug 1998 14:50:09 -0500 (EST)) Subject: Re: HEADS UP: 3 days to E-day From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * I'm thinking about getting Motif, but am concerned about being * dependent on XIG for a 3.0 version. First, how hard would it be You wouldn't have to worry too much about that. The ports tree will support compilation in a.out for quite some time. (Since the whole point of getting Motif is so you can link your own programs shared....) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 18:23:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21315 for freebsd-current-outgoing; Fri, 28 Aug 1998 18:23:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-65.ppp.wenet.net [206.15.84.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21279 for ; Fri, 28 Aug 1998 18:22:59 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id SAA00950; Fri, 28 Aug 1998 18:23:31 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Fri, 28 Aug 1998 18:23:31 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Kenneth Chiu cc: current@FreeBSD.ORG, Stephen Hocking-Senior Programmer PGS Tensor Perth , John Birrell , Chuck Robey Subject: Re: HEADS UP: 3 days to E-day In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Aug 1998, Kenneth Chiu wrote: [..] > I'm thinking about getting Motif, but am concerned about being > dependent on XIG for a 3.0 version. First, how hard would it be > to write a program to convert a.out to ELF? Is it just a matter > of converting the relocation table, symbol table, and string table? > Or will the 3.0 loader be able to mix and match ELF and a.out? If you stick with static libs, I think it's purely a matter of removing the prepended underscore. This might be the way to go until XiG releases a true ELF version. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 18:35:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23477 for freebsd-current-outgoing; Fri, 28 Aug 1998 18:35:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23454 for ; Fri, 28 Aug 1998 18:35:20 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA04537; Fri, 28 Aug 1998 18:34:26 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp04.primenet.com, id smtpd004490; Fri Aug 28 18:34:21 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id SAA29280; Fri, 28 Aug 1998 18:34:16 -0700 (MST) From: Terry Lambert Message-Id: <199808290134.SAA29280@usr01.primenet.com> Subject: Re: recovering disk To: joelh@gnu.org Date: Sat, 29 Aug 1998 01:34:16 +0000 (GMT) Cc: seggers@semyam.dinoco.de, mi@video-collage.com, current@FreeBSD.ORG In-Reply-To: <199808262334.SAA13309@detlev.UUCP> from "Joel Ray Holveck" at Aug 26, 98 06:34:54 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > [Now the questions is how often this happens. Would it be worth to > > make an additional disklabel and - for systems having it - fdisk > > partition table recovery tool? How's the opinion on this?] > > You know what I'd like? A general disk editor, that can take its > input by the block or by the file, with a hex editor as well as some > special-purpose viewers. Something like Norton's Disk Editor. Said > tool has been amazingly useful to me on many an occasion. xvi /dev/rsd0e. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 18:45:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24373 for freebsd-current-outgoing; Fri, 28 Aug 1998 18:45:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24365 for ; Fri, 28 Aug 1998 18:44:58 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id SAA22736; Fri, 28 Aug 1998 18:43:41 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd022708; Fri Aug 28 18:43:38 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id SAA29643; Fri, 28 Aug 1998 18:43:33 -0700 (MST) From: Terry Lambert Message-Id: <199808290143.SAA29643@usr01.primenet.com> Subject: Re: Floating Point Exceptions, signal handlers & subsequent ops To: bde@zeta.org.au (Bruce Evans) Date: Sat, 29 Aug 1998 01:43:33 +0000 (GMT) Cc: bde@zeta.org.au, cracauer@cons.org, current@FreeBSD.ORG, luoqi@watermarkgroup.com, shocking@prth.pgs.com In-Reply-To: <199808271224.WAA25445@godzilla.zeta.org.au> from "Bruce Evans" at Aug 27, 98 10:24:58 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> I wrote the assembler code. Run it under gdb and look at the FP > >> state using `info float'. Homework: explain why this generates > >> only 6 SIGFPE's although it divides by 0.0 by 0.0 8 times. > > ^ > >Don't you mean 7? > > Oops. I miscounted 6 and thought that it was missing 1 for both the > first and the last division. A general 5,000 foot view onto the "Homework" problem: FP exceptions are signalled on the FP instruction following the exception. That is, you have to try to use the thing again to generate an exception. This is a rather bogus hardware implementation, unless you are ignoring exceptions entirely, in which case, it saves an instruction restart for each exception. FreeBSD does lazy task switching; that it, FreeBSD does not do FP register saves on task switches, unless necessary, and does not do implict saves via TSS, since it does not use TSS for the switch (ie: it doesn't go through a task gate, except to get in and out of VM86 mode). Non-lazy task switching would cause context switch to be much higher overhead (as in Linux), but would cause the exception to be raised in the context of the process that caused it. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 18:54:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25448 for freebsd-current-outgoing; Fri, 28 Aug 1998 18:54:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25377 for ; Fri, 28 Aug 1998 18:53:58 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id SAA15627; Fri, 28 Aug 1998 18:53:03 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd015599; Fri Aug 28 18:52:59 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id SAA00390; Fri, 28 Aug 1998 18:52:50 -0700 (MST) From: Terry Lambert Message-Id: <199808290152.SAA00390@usr01.primenet.com> Subject: Re: It's MFS panic.. (Re: Panic with DEVFS) To: mike@smith.net.au (Mike Smith) Date: Sat, 29 Aug 1998 01:52:50 +0000 (GMT) Cc: julian@whistle.com, abial@nask.pl, freebsd-current@FreeBSD.ORG In-Reply-To: <199808271525.PAA00718@dingo.cdrom.com> from "Mike Smith" at Aug 27, 98 03:25:32 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ooooohhhhhhh > > > > > > specfs is not active if DEVFS is active > > so the spec_fsync should not be called...... > > I bet it's hard coded into MFS.. > > It would seem to me that specfs shouldn't even be *built* if DEVFS is > enabled. Looking over Julian's shoulder, the MFS code explicitly makes calls through the specfs VOP table. Specifically, there is a vp that represents the mount point that is treated as a physical device. When you fsync (or getpages or putpages), you call it with a vp that results in you calling the specfs with a modified version of the vp (since the backing object is really anonymous pages). This results in a call into specfs on the mountpoint vp, that calls specfs again, which call mfs_strategy. All in all, it's a pretty lame implementation, since it means that the anonymous pages backing the object are not the same as the pages hung off the vnode of the fs mounted on the object. Sure, you may have to page pages in from real swap (the swap pager backs anonymous pages), but for pages that are in core and dirty, the "sync" should be a reference count decrement. This seems to be related to the remnants of the BSD non-overcommit memory, where dirty pages would have to be written to swap. Mind you, I prefer a slightly more complex implementation: I think it should be possible to shadow RAM to a special area (let's not call it a swap area, since then you would want to overcommit the RAM), in order to support a "suspend to disk". But the current MFS code is rather arcane for something that fronts a set of anonymous pages. I would recommend reimplementing this with a "Memory device" driver, and putting your standard FS on the thing, instead. At best, you would end up with unallocated pages (a "sparse" device), and at worst, the overhead can't be more than mfs->specfs->strategy->mfs->specfs->mfs. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 18:56:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25873 for freebsd-current-outgoing; Fri, 28 Aug 1998 18:56:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25860 for ; Fri, 28 Aug 1998 18:56:44 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id UAA01169; Fri, 28 Aug 1998 20:54:16 -0400 (EDT) Date: Fri, 28 Aug 1998 20:54:16 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Alex cc: Kenneth Chiu , current@FreeBSD.ORG, Stephen Hocking-Senior Programmer PGS Tensor Perth , John Birrell Subject: Re: HEADS UP: 3 days to E-day In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Aug 1998, Alex wrote: > On Fri, 28 Aug 1998, Kenneth Chiu wrote: > [..] > > I'm thinking about getting Motif, but am concerned about being > > dependent on XIG for a 3.0 version. First, how hard would it be > > to write a program to convert a.out to ELF? Is it just a matter > > of converting the relocation table, symbol table, and string table? > > Or will the 3.0 loader be able to mix and match ELF and a.out? > > If you stick with static libs, I think it's purely a matter of removing > the prepended underscore. This might be the way to go until XiG releases > a true ELF version. Are you sure? I thought that if you were linking up a elf executeable, you'd have to use 100% pure elf libs (and vice versa), and no mixing allowed. I know about the underscore business, but it's a different linker extirely, isn't it? I also thought that the run time linker (ld.so) only knew about one flavor, so you needed an elf one, and an aout one, and no mixing. Is this untrue? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 19:06:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27021 for freebsd-current-outgoing; Fri, 28 Aug 1998 19:06:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27014 for ; Fri, 28 Aug 1998 19:06:43 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA15939; Fri, 28 Aug 1998 19:03:37 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808281903.TAA15939@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: current@FreeBSD.ORG Subject: Re: HEADS UP: 3 days to E-day In-reply-to: Your message of "Fri, 28 Aug 1998 20:54:16 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Aug 1998 19:03:36 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are you sure? I thought that if you were linking up a elf executeable, > you'd have to use 100% pure elf libs (and vice versa), and no mixing > allowed. I know about the underscore business, but it's a different > linker extirely, isn't it? > > I also thought that the run time linker (ld.so) only knew about one > flavor, so you needed an elf one, and an aout one, and no mixing. John Polstra has a tool which *may* be able to convert a static a.out library into a static ELF library. It would be trivial to frontend this to make 'shadow' ELF copies of a.out libraries. I haven't heard from John on this for a few weeks now; I do recall there were some complications, but I'll leave them to him to discuss. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 19:15:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28220 for freebsd-current-outgoing; Fri, 28 Aug 1998 19:15:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28207 for ; Fri, 28 Aug 1998 19:15:18 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id WAA19990; Fri, 28 Aug 1998 22:14:19 -0400 (EDT) (envelope-from gjp@gjp.erols.com) To: ben@rosengart.com cc: current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: problems building current In-reply-to: Your message of "Fri, 28 Aug 1998 12:42:38 EDT." Date: Fri, 28 Aug 1998 22:14:19 -0400 Message-ID: <19985.904356859@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Snob Art Genre wrote in message ID : > --- amd --- > cc -O2 -pipe -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd/amd -I. > -I/usr/src/usr.sbin/amd/amd -I/usr/src/usr.sbin/amd/amd/../include > -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd/include > -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd -DHAVE_CONFIG_H > -I/usr/obj/usr/src/tmp/usr/include -o amd conf_parse.o conf_tok.o > am_ops.o amd.o amfs_auto.o amfs_direct.o amfs_error.o amfs_host.o > amfs_inherit.o amfs_link.o amfs_linkx.o amfs_nfsl.o amfs_nfsx.o > amfs_program.o amfs_root.o amfs_toplvl.o amfs_union.o amq_subr.o > amq_svc.o autil.o clock.o conf.o get_args.o info_file.o info_ndbm.o > info_nis.o info_passwd.o info_union.o map.o mapc.o mntfs.o > nfs_prot_svc.o nfs_start.o nfs_subr.o ops_cdfs.o ops_lofs.o ops_mfs.o > ops_nfs.o ops_nfs3.o ops_nullfs.o ops_pcfs.o ops_tfs.o ops_ufs.o > ops_umapfs.o ops_unionfs.o opts.o restart.o rpc_fwd.o sched.o > srvr_amfs_auto.o srvr_nfs.o mount_xdr.o --- xwhere --- > /usr/src/usr.sbin/amd/libamu/obj/libamu.a -lrpcsvc > cc: xwhere: No such file or directory > *** Error code 1 > 1 error Ahaa!! I thought this was an alpha specific problem. I can easily recreate it. The only solution I have so far is not to do parallel compiles (which sucks, as I get much better performance on the alpha if I do). I hacked around it by changing the LIBAMUDIR path to be a ../libamu/limabu.a style path rather than an `script` expression, but I don't know if that is the right answer. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 19:28:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00151 for freebsd-current-outgoing; Fri, 28 Aug 1998 19:28:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00137 for ; Fri, 28 Aug 1998 19:28:25 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with SMTP id VAA01366; Fri, 28 Aug 1998 21:25:26 -0400 (EDT) Date: Fri, 28 Aug 1998 21:25:26 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: HEADS UP: 3 days to E-day In-Reply-To: <199808281903.TAA15939@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Aug 1998, Mike Smith wrote: > > Are you sure? I thought that if you were linking up a elf executeable, > > you'd have to use 100% pure elf libs (and vice versa), and no mixing > > allowed. I know about the underscore business, but it's a different > > linker extirely, isn't it? > > > > I also thought that the run time linker (ld.so) only knew about one > > flavor, so you needed an elf one, and an aout one, and no mixing. > > John Polstra has a tool which *may* be able to convert a static a.out > library into a static ELF library. It would be trivial to frontend > this to make 'shadow' ELF copies of a.out libraries. > > I haven't heard from John on this for a few weeks now; I do recall > there were some complications, but I'll leave them to him to discuss. I'd heard John talking about that tool for a couple of years now, but I was under the impression that it wasn't something contemplated for the short term now, so we'd still have to build (either static OR shared) stuff either all elf (all elf libs) or all aout, and not allowing any sharing at all. Certainly that's true for shared stuff, because the ld.so isn't smart enough to handle both, and I think the linker isn't either. It's a great idea, but it's not going to be true, short term, and telling folks that is going to cause more harm now. FYI, I let XIG know about the timing of the move to ELF. Maybe, if Jordan has a commercial mailing list, it'd be a real good idea to make up a form letter to email to everyone who has FreeBSD stuff being sold, to let them know all the facts, before rumors of wild tales get to them. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 19:38:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01235 for freebsd-current-outgoing; Fri, 28 Aug 1998 19:38:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01228 for ; Fri, 28 Aug 1998 19:38:15 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id TAA13342; Fri, 28 Aug 1998 19:37:22 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd013291; Fri Aug 28 19:37:13 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id TAA02872; Fri, 28 Aug 1998 19:37:06 -0700 (MST) From: Terry Lambert Message-Id: <199808290237.TAA02872@usr01.primenet.com> Subject: Re: encountered possible VM bug ? To: archie@whistle.com (Archie Cobbs) Date: Sat, 29 Aug 1998 02:37:06 +0000 (GMT) Cc: archer@lucky.net, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG In-Reply-To: <199808272051.NAA27400@bubba.whistle.com> from "Archie Cobbs" at Aug 27, 98 01:51:40 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ ... corruption after unning out of swap ... ] > At Whistle, we've seen this bug every so often for a long time. > The common elements seem to be: > > 1. memory mapping is in use > 2. a fork() is happening or just happened > > But #1 and #2 are not necessarily both related to the same process. > This bug has been around for a *long* time, in both 2.x and 3.x. > > Running out of swap may or may not be related, not sure... I think > we've seen this when swap was not an issue. Perhaps running out of > swap amplifies the problem. There are actually two seperate problems. In one, mmap'ed pages end up in other files. In the other, other files pages (perhaps other mmap'ed files pages only?) end up in mmap'ed pages. The first case is a general problem with FreeBSD, and is not limited to resource limitations. I've fixed part of this with the "valid" and "mmap file size" patches. The second is a result of running out of swap, and I haven't identified it (though it bit me the other day, I was in X, and since the CPU was pegged, I couldn't switch out of X to go to the kernel debugger, and FreeBSD can't go into the kernel directly from X because it's broken. > It's really hard to pin down, because the panic seems to come a > while after the initial damage is done. We've seen random processes > crashing every time they try to fork(), kernel panic's because of > some process being on two different queues at the same time (eg, > sleep and runnable), and other manifestations. The fork() problem is related to the first case, and not the second. It may very well be fixed by the "valid" patches; I haven't had a chance to build a kernel for Doug Ambrisko to run in his test environment. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 19:47:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01916 for freebsd-current-outgoing; Fri, 28 Aug 1998 19:47:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-90.ppp.wenet.net [206.15.84.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01911 for ; Fri, 28 Aug 1998 19:47:10 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id TAA01171; Fri, 28 Aug 1998 19:47:32 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Fri, 28 Aug 1998 19:47:32 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Chuck Robey cc: Kenneth Chiu , current@FreeBSD.ORG, Stephen Hocking-Senior Programmer PGS Tensor Perth , John Birrell Subject: Re: HEADS UP: 3 days to E-day In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Aug 1998, Chuck Robey wrote: [..] > > If you stick with static libs, I think it's purely a matter of removing > > the prepended underscore. This might be the way to go until XiG releases > > a true ELF version. > > Are you sure? I thought that if you were linking up a elf executeable, > you'd have to use 100% pure elf libs (and vice versa), and no mixing > allowed. I know about the underscore business, but it's a different > linker extirely, isn't it? > > I also thought that the run time linker (ld.so) only knew about one > flavor, so you needed an elf one, and an aout one, and no mixing. > > Is this untrue? Static libs are a different beast I think. The elf linker seems to grok old static libs. At least it did, the last time I had old a.out libs where I shouldn't have. Of course, I ran into undefined references, as the linker didn't expect an underscore. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 20:08:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03678 for freebsd-current-outgoing; Fri, 28 Aug 1998 20:08:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03673 for ; Fri, 28 Aug 1998 20:08:18 -0700 (PDT) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id WAA05792 for current@FreeBSD.ORG; Fri, 28 Aug 1998 22:07:24 -0500 (CDT) Received: (from bruce@localhost) by zuhause.mn.org (8.8.8/8.8.7) id WAA08503; Fri, 28 Aug 1998 22:04:16 -0500 (CDT) From: Bruce Albrecht Date: Fri, 28 Aug 1998 22:04:14 -0500 (CDT) To: current@FreeBSD.ORG Subject: Re: HEADS UP: 3 days to E-day X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13799.28210.383461.909654@zuhause.zuhause.mn.org> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm a -current user because I have an SMP machine, but I haven't upgraded since before the intermediate ELF changes moved the aout versions to /usr/lib/aout. After E-day occurs, what will users see when upgrading to a current -current? Will /usr/lib contain elf format libraries, and /usr/lib/aout contain a.out format libraries for compatibility? When 3.0 is released in October, will it only have elf libraries, and no a.out format libraries? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 20:20:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04668 for freebsd-current-outgoing; Fri, 28 Aug 1998 20:20:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04662 for ; Fri, 28 Aug 1998 20:20:17 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id DAA15630; Sat, 29 Aug 1998 03:17:39 GMT Date: Sat, 29 Aug 1998 12:17:38 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: Mike Smith , julian@whistle.com, abial@nask.pl, freebsd-current@FreeBSD.ORG Subject: Re: It's MFS panic.. (Re: Panic with DEVFS) In-Reply-To: <199808290152.SAA00390@usr01.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 29 Aug 1998, Terry Lambert wrote: > I would recommend reimplementing this with a "Memory device" driver, > and putting your standard FS on the thing, instead. At best, you > would end up with unallocated pages (a "sparse" device), and at worst, > the overhead can't be more than mfs->specfs->strategy->mfs->specfs->mfs. I think NetBSD has a memory disk device. I still think fronting anonymous memory is pretty cool though, but I'd like to see it done with data structures that make make sense for memory rather than using code from ufs. It would be much easier to implement a system that can grow and shrink its usage of resources than the RAM disk approach because it competes for pages like any other process. Having both of the above would be ok too. :-) 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 Aug 28 20:55:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06929 for freebsd-current-outgoing; Fri, 28 Aug 1998 20:55:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06909; Fri, 28 Aug 1998 20:54:54 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA10690; Sat, 29 Aug 1998 13:53:54 +1000 Date: Sat, 29 Aug 1998 13:53:54 +1000 From: Bruce Evans Message-Id: <199808290353.NAA10690@godzilla.zeta.org.au> To: ben@rosengart.com, gpalmer@FreeBSD.ORG Subject: Re: problems building current Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> cc -O2 -pipe -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd/amd -I. >> -I/usr/src/usr.sbin/amd/amd -I/usr/src/usr.sbin/amd/amd/../include >> -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd/include >> -I/usr/src/usr.sbin/amd/amd/../../../contrib/amd -DHAVE_CONFIG_H >> -I/usr/obj/usr/src/tmp/usr/include -o amd conf_parse.o conf_tok.o >> am_ops.o amd.o amfs_auto.o amfs_direct.o amfs_error.o amfs_host.o >> amfs_inherit.o amfs_link.o amfs_linkx.o amfs_nfsl.o amfs_nfsx.o >> amfs_program.o amfs_root.o amfs_toplvl.o amfs_union.o amq_subr.o >> amq_svc.o autil.o clock.o conf.o get_args.o info_file.o info_ndbm.o >> info_nis.o info_passwd.o info_union.o map.o mapc.o mntfs.o >> nfs_prot_svc.o nfs_start.o nfs_subr.o ops_cdfs.o ops_lofs.o ops_mfs.o >> ops_nfs.o ops_nfs3.o ops_nullfs.o ops_pcfs.o ops_tfs.o ops_ufs.o >> ops_umapfs.o ops_unionfs.o opts.o restart.o rpc_fwd.o sched.o >> srvr_amfs_auto.o srvr_nfs.o mount_xdr.o --- xwhere --- >> /usr/src/usr.sbin/amd/libamu/obj/libamu.a -lrpcsvc >> cc: xwhere: No such file or directory >> *** Error code 1 >> 1 error > >Ahaa!! I thought this was an alpha specific problem. I can easily >recreate it. The only solution I have so far is not to do parallel >compiles (which sucks, as I get much better performance on the alpha >if I do). I hacked around it by changing the LIBAMUDIR path to be a >../libamu/limabu.a style path rather than an `script` expression, but >I don't know if that is the right answer. The != expression doesn't actually work for make -j, since make -j emits "--- blah ---" to stdout (make -j's handling of stdout and stderr seems to be mostly broken). This can probably be fixed using -B. Another bug: `DPADD' is consistently misspelled as `DPDADD'. This bug is easy to find using `make checkdpadd'. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 21:16:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08133 for freebsd-current-outgoing; Fri, 28 Aug 1998 21:16:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08124 for ; Fri, 28 Aug 1998 21:16:08 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id VAA14317; Fri, 28 Aug 1998 21:15:08 -0700 (PDT) (envelope-from jdp) Message-Id: <199808290415.VAA14317@austin.polstra.com> To: mike@smith.net.au Subject: Re: HEADS UP: 3 days to E-day In-Reply-To: <199808281903.TAA15939@dingo.cdrom.com> References: <199808281903.TAA15939@dingo.cdrom.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Fri, 28 Aug 1998 21:15:08 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199808281903.TAA15939@dingo.cdrom.com>, Mike Smith wrote: > John Polstra has a tool which *may* be able to convert a static a.out > library into a static ELF library. Heh, not quite. I have _plans_ for a tool which will be able to convert an a.out _shared_ library into an ELF shared library. But it's nowhere near finished. Higher priority things keep coming up. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 21:21:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08558 for freebsd-current-outgoing; Fri, 28 Aug 1998 21:21:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08543 for ; Fri, 28 Aug 1998 21:21:16 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id OAA18168; Sat, 29 Aug 1998 14:32:05 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808290432.OAA18168@cimlogic.com.au> Subject: Re: HEADS UP: 3 days to E-day In-Reply-To: <13799.28210.383461.909654@zuhause.zuhause.mn.org> from Bruce Albrecht at "Aug 28, 98 10:04:14 pm" To: bruce@zuhause.mn.org (Bruce Albrecht) Date: Sat, 29 Aug 1998 14:32:05 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Albrecht wrote: > I'm a -current user because I have an SMP machine, but I haven't > upgraded since before the intermediate ELF changes moved the aout > versions to /usr/lib/aout. After E-day occurs, what will users see > when upgrading to a current -current? Will /usr/lib contain elf > format libraries, and /usr/lib/aout contain a.out format libraries for > compatibility? Yes, provided that you go though the aout-to-elf upgrade procedure. If you don't use the upgrade procedure, you won't get any of the elf bits, but the aout libraries will be in /usr/lib/aout (and you will have to manually delete the older aout libraries left in /usr/lib). > When 3.0 is released in October, will it only have elf > libraries, and no a.out format libraries? No. 3.0 will be shipped with aout tools and libraries too. I expect that what you see after upgrading will be what gets shipped. The only thing that might be changed for the release is the default object format which is currently aout. My preference is that 3.0-RELEASE has OBJFORMAT=elf as the default. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 28 21:58:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10515 for freebsd-current-outgoing; Fri, 28 Aug 1998 21:58:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (castles244.castles.com [208.214.165.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA10510 for ; Fri, 28 Aug 1998 21:58:40 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id VAA00507; Fri, 28 Aug 1998 21:55:56 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808282155.VAA00507@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: encountered possible VM bug ? In-reply-to: Your message of "Sat, 29 Aug 1998 02:37:06 GMT." <199808290237.TAA02872@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Aug 1998 21:55:55 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The first case is a general problem with FreeBSD, and is not > limited to resource limitations. I've fixed part of this with > the "valid" and "mmap file size" patches. What are the PR numbers? Who is reviewing them? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 29 01:30:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01155 for freebsd-current-outgoing; Sat, 29 Aug 1998 01:30:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (castles244.castles.com [208.214.165.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01132 for ; Sat, 29 Aug 1998 01:30:47 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id BAA02277; Sat, 29 Aug 1998 01:27:39 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808290127.BAA02277@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Alexander Litvin cc: Mike Smith , current@FreeBSD.ORG Subject: Re: encountered possible VM bug ? In-reply-to: Your message of "Fri, 28 Aug 1998 12:24:31 +0300." <19980828122431.14123@carrier.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Aug 1998 01:27:38 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Aug 28, 1998 at 01:19:08AM +0000, Mike Smith wrote: > > > Reading symbols from /usr/libexec/ld.so...done. > > > Reading symbols from /usr/lib/aout/libc.so.3.1...done. > > > > > > Error accessing memory address 0x0: Bad address. > > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > What exactly does that line mean? When I attach to not deseased dummy_daemon, > > > it does not appear, instead I see: > > > > It means that the instruction pointer obtained for the process is 0, > > which is invalid. > > Do you mean eip register? 'info registers' show: I was wrong; it means that at some point gdb has attempted to read from address 0, which is invalid, and it can't proceed. You would have to manually examine the core file to work out what's going on; I would guess that it's damaged somewhere. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 29 04:09:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA16989 for freebsd-current-outgoing; Sat, 29 Aug 1998 04:09:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from indigo.ie (ts01-017.dublin.indigo.ie [194.125.134.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA16983 for ; Sat, 29 Aug 1998 04:09:00 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id MAA00638; Sat, 29 Aug 1998 12:01:24 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199808291101.MAA00638@indigo.ie> Date: Sat, 29 Aug 1998 12:01:24 +0000 In-Reply-To: <199808290127.BAA02277@word.smith.net.au>; Mike Smith Reply-To: rotel@indigo.ie X-Files: The truth is out there X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: Mike Smith , Alexander Litvin Subject: Re: encountered possible VM bug ? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Aug 29, 1:27am, Mike Smith wrote: } Subject: Re: encountered possible VM bug ? > > On Fri, Aug 28, 1998 at 01:19:08AM +0000, Mike Smith wrote: > > > > Reading symbols from /usr/libexec/ld.so...done. > > > > Reading symbols from /usr/lib/aout/libc.so.3.1...done. > > > > > > > > Error accessing memory address 0x0: Bad address. > > > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > What exactly does that line mean? When I attach to not deseased dummy_daemon, > > > > it does not appear, instead I see: > > > > > > It means that the instruction pointer obtained for the process is 0, > > > which is invalid. > > I was wrong; it means that at some point gdb has attempted to read from > address 0, which is invalid, and it can't proceed. You would have to > manually examine the core file to work out what's going on; I would > guess that it's damaged somewhere. It might be finding a 0x0 where it thinks the saved eip is (usually ebp + 4) Try "x (ebp + 4)". Niall -- Niall Smart, rotel@indigo.ie. Amaze your friends and annoy your enemies: echo '#define if(x) if (!(x))' >> /usr/include/stdio.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 29 06:42:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27375 for freebsd-current-outgoing; Sat, 29 Aug 1998 06:42:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27367 for ; Sat, 29 Aug 1998 06:42:24 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id JAA01898; Sat, 29 Aug 1998 09:39:30 -0400 (EDT) (envelope-from luoqi) Date: Sat, 29 Aug 1998 09:39:30 -0400 (EDT) From: Luoqi Chen Message-Id: <199808291339.JAA01898@lor.watermarkgroup.com> To: current@FreeBSD.ORG, julian@whistle.com Subject: Re: FS gurus please.. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why does MFS unconditionally call spec_fsync() on all vnodes? One presumes > that since it's a memory filesysytem, fsync should do nothing.. I'm also > curious why it doesn't even check that it's a vnode for a special device. > What do we gain by calling spec_fsync on a normal file in an MFS? > The so called mfs_vnodeop is actually a misnomer: it is used only for the underlying block device vnode, which is not even one of mfs' vnodes. All mfs' vnodes use regular ufs vnode ops. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 29 10:28:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15130 for freebsd-current-outgoing; Sat, 29 Aug 1998 10:28:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA15115; Sat, 29 Aug 1998 10:28:03 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id NAA00918; Sat, 29 Aug 1998 13:30:14 -0400 From: Bill Paul Message-Id: <199808291730.NAA00918@skynet.ctr.columbia.edu> Subject: Looking for feedback on xl (3c905/3c905B) driver To: stable@FreeBSD.ORG, current@FreeBSD.ORG Date: Sat, 29 Aug 1998 13:30:12 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay people, it's been some time since I put the xl0 driver in -current and -stable. I need to know if people are having problems with the driver or not. So far I've gotten startlingly little feedback. This either means that it's working so well that nobody has had any trouble with it, or you guys are all just slackers and are too lazy to speak up. Basically I'm looking for as many success or failure reports as possible. If you're having trouble with the driver and you don't tell me about it, I can't help you, so speak up. If you're not having trouble and it's working well, I'd like to know that too. Here are some things I'd like to know: - What kind of adapter you have. Note that a 3c905-TX is NOT THE SAME as a 3c905B-TX. (See the 'B'? It makes a difference.) Double and triple check the model. Don't tell me you have a 3c905B when you actually only have a 3c905. If you want to be really nice, do 'dmesg | grep xl' and show me the output. - The driver version you're using. If you obtained the driver by cvsup'ing -current or -stable, then you have the latest one. If you downloaded the driver from www.freebsd.org/~wpaul/3Com within the last week, then you also have the latest one. If you're not sure, show me the rcsid strings from if_xl.c and if_xlreg.h. - Does the driver detect all of the adapter's media types correctly? - Is the system stable? Have you had problems with kernel panics since you started using the driver? Is mbuf usage normal or does it look like there's an mbuf leak? (use netstat -m to monitor mbuf usage) - Type of system (CPU type/speed). Are you using a slower system like a 486 or older Pentium (P75, P90, P1xx, etc...)? If so, are there problems with performance? Are you using SCSI disks or IDE disks? - Type of network to which the adapter is attached. Are you using a hub? A switch? Crossover cable to another machine? Coax? AUI? If a hub, are there lots of hosts on the same segment? - How many adapters in the system. - How heavily loaded is the system. Is this just a personal machine with occasional network traffic or is it a heavily used server? (http, FTP, NFS, login shell box, etc...) Is it a router? - Observed performance. Does the adapter/driver work well under load? Does the adapter lock up or otherwise misbehave under high-load conditions? Are there lots of input or output errors? (use netstat -in to check) Do you ever have to ifconfig down and ifconfig up the adapter to reset it? - 'Out of buffers' problems. Does the 'OACTIVE' flag ever show up when you do 'ifconfig xl0'? - Unusual error messages. Are there any diagnostics generated by the driver that don't look normal? (timeouts, transmission errors, etc...) - Multicast operation. Is the adapter receiving all the multicast frames that it should? (Note that the 3c905B adapters have a hash filter whereas the 3c900 and 3c905 adapters have only a 'receive all multicast frames' mode, so reports about the 3c905B are more useful.) - Unusual configurations. Are you using firewalling? Network address translation? Proxy ARP? IP aliases? Shitloads of IP aliases? Do you have Lose95/98/NT installed on your machine along with FreeBSD? Do you have problems warm booting from Lose95/98/NT to FreeBSD? (Adapter not probed, adapter not reset correctly after warm boot...) - Benchmarks. Have you compared the xl driver's performance against any others? What were the numbers? What benchmarks did you use? Was performace good? Bad? Ugly? Here are some things I don't want to hear: - "I saw some error but I forgot it, and I didn't write it down. Does this help?" - "I saw somewhere you were interested in information about 3c905 performance with FreeBSD. What exactly do you need to know?" - "I can give you the information you want, but I wanted to send you a short note first just to see if you were really interested." - "You can use Internet Explorer to find out more information about 3Com products by going to www.3Com.com..." - "Well, I'm having some trouble, but I don't have time to give you the details as I'm just about to leave for the airport and fly to some remote part of deepest, darkest Africa to start a tour with the Red Cross, and I won't be able to use my computer again for about three years. But I can try to give you more information when I get back. Is that okay?" - "It works just fine with Windows!" - "It works just fine with Linux!" - "I can't help you with this 3Com thing, but do you have a driver for the Gronkulator 2000 board? I've got, like, 20 of them and they only cost, like, $5 each." - "D00d, got any war3z?" - "Are you being investigated?" - "How do I get FreeBSD? I have Windows 98 and the Internet; will it work with that?" So speak up everyone. Send your cards and letters to wpaul@skynet.ctr.columbia.edu. Operators are standing by. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 29 11:34:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22190 for freebsd-current-outgoing; Sat, 29 Aug 1998 11:34:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22185; Sat, 29 Aug 1998 11:34:30 -0700 (PDT) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id LAA15318; Sat, 29 Aug 1998 11:33:26 -0700 (MST) From: "Chad R. Larson" Message-Id: <199808291833.LAA15318@freebie.dcfinc.com> Subject: Re: Looking for feedback on xl (3c905/3c905B) driver To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Sat, 29 Aug 1998 11:33:25 -0700 (MST) Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199808291730.NAA00918@skynet.ctr.columbia.edu> from Bill Paul at "Aug 29, 98 01:30:12 pm" Reply-to: chad@dcfinc.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Okay people, it's been some time since I put the xl0 driver in > -current and -stable. I need to know if people are having problems > with the driver or not. So far I've gotten startlingly little > feedback. This either means that it's working so well that nobody has > had any trouble with it, or you guys are all just slackers and are too > lazy to speak up. You left out a third. We don't know better. Here's an edited version of my dmesg.boot file: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= FreeBSD 2.2.7-STABLE #0: Wed Jul 29 18:26:19 MST 1998 chad@chad.anasazi.com:/usr/src/sys/compile/CHAD CPU: Pentium/P55C (166.06-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bf real memory = 33554432 (32768K bytes) chip0 rev 3 on pci0:0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 pci0:7:2: Intel Corporation, device=0x7020, class=serial, subclass=0x03 int d irq 9 [no driver assigned] vx0 <3COM 3C905 Fast Etherlink XL PCI> rev 0 int a irq 11 on pci0:16:0 mii[*mii*]: disable 'auto select' with DOS util! address 00:60:97:de:2b:a8 Intel Pentium F00F detected, installing workaround -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= As you can see, I'm running the vx0 driver. It's the one selected by the installation process. I kept it as I built my custom kernel. Should I have selected the xl driver then? If so, how would I have known that? -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 29 12:02:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25356 for freebsd-current-outgoing; Sat, 29 Aug 1998 12:02:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25346; Sat, 29 Aug 1998 12:02:40 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:AF/Jab04RYywjuZ8m4DvaE1OGPuL6h4f@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id VAA06715; Sat, 29 Aug 1998 21:01:11 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199808291901.VAA06715@gratis.grondar.za> To: Bill Paul cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Looking for feedback on xl (3c905/3c905B) driver Date: Sat, 29 Aug 1998 21:01:10 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Paul wrote: > Basically I'm looking for as many success or failure reports as possible. > If you're having trouble with the driver and you don't tell me about it, > I can't help you, so speak up. If you're not having trouble and it's > working well, I'd like to know that too. It is working on my home (CURRENT) and colleagues (STABLE) boxes extremely well. The vx0 driver would frequently go into a (suspected) lose-all-interrupts mode, and run like molasses. The xl0 driver s smooth, fast and trouble-free so far. > Here are some things I'd like to know: > > - What kind of adapter you have. Note that a 3c905-TX is NOT THE SAME > as a 3c905B-TX. (See the 'B'? It makes a difference.) Double and triple > check the model. Don't tell me you have a 3c905B when you actually only > have a 3c905. If you want to be really nice, do 'dmesg | grep xl' and > show me the output. 3c900 XL's. > - The driver version you're using. If you obtained the driver by > cvsup'ing -current or -stable, then you have the latest one. If you > downloaded the driver from www.freebsd.org/~wpaul/3Com within the > last week, then you also have the latest one. If you're not sure, > show me the rcsid strings from if_xl.c and if_xlreg.h. Regular CVSUP, so recent. > - Does the driver detect all of the adapter's media types correctly? Yes. > - Is the system stable? Have you had problems with kernel panics since > you started using the driver? Is mbuf usage normal or does it look > like there's an mbuf leak? (use netstat -m to monitor mbuf usage) Rock steady. > - Type of system (CPU type/speed). Are you using a slower system like > a 486 or older Pentium (P75, P90, P1xx, etc...)? If so, are there > problems with performance? Are you using SCSI disks or IDE disks? P5/200(SMP untested) and P5166. > - Type of network to which the adapter is attached. Are you using a > hub? A switch? Crossover cable to another machine? Coax? AUI? If a hub, > are there lots of hosts on the same segment? Home - coax. Work - utp. > - How many adapters in the system. 1 all round. > - How heavily loaded is the system. Is this just a personal machine > with occasional network traffic or is it a heavily used server? > (http, FTP, NFS, login shell box, etc...) Is it a router? Home - deveopment net - I beat the crap out of it in short bursts (CVS over NFS etc. Work - production environment - very heavy workstaion use. > - Observed performance. Does the adapter/driver work well under load? > Does the adapter lock up or otherwise misbehave under high-load > conditions? Are there lots of input or output errors? (use netstat -in > to check) Do you ever have to ifconfig down and ifconfig up the adapter > to reset it? Better perfomance than old driver, and none of the old hassles. > - 'Out of buffers' problems. Does the 'OACTIVE' flag ever show up when > you do 'ifconfig xl0'? No. > - Unusual error messages. Are there any diagnostics generated by the > driver that don't look normal? (timeouts, transmission errors, etc...) None. > - Multicast operation. Is the adapter receiving all the multicast > frames that it should? (Note that the 3c905B adapters have a hash > filter whereas the 3c900 and 3c905 adapters have only a 'receive all > multicast frames' mode, so reports about the 3c905B are more useful.) Not tested. > - Unusual configurations. Are you using firewalling? Network address > translation? Proxy ARP? IP aliases? Shitloads of IP aliases? Do you > have Lose95/98/NT installed on your machine along with FreeBSD? > Do you have problems warm booting from Lose95/98/NT to FreeBSD? > (Adapter not probed, adapter not reset correctly after warm boot...) No. > - Benchmarks. Have you compared the xl driver's performance against > any others? What were the numbers? What benchmarks did you use? > Was performace good? Bad? Ugly? Better perfomance based on "feel", rather than hard stats. > Here are some things I don't want to hear: ROTFLMAO. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 29 12:21:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27408 for freebsd-current-outgoing; Sat, 29 Aug 1998 12:21:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA27403; Sat, 29 Aug 1998 12:21:45 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id PAA01095; Sat, 29 Aug 1998 15:23:49 -0400 From: Bill Paul Message-Id: <199808291923.PAA01095@skynet.ctr.columbia.edu> Subject: Re: Looking for feedback on xl (3c905/3c905B) driver To: chad@dcfinc.com Date: Sat, 29 Aug 1998 15:23:48 -0400 (EDT) Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199808291833.LAA15318@freebie.dcfinc.com> from "Chad R. Larson" at Aug 29, 98 11:33:25 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Chad R. Larson had to walk into mine and say: > > Okay people, it's been some time since I put the xl0 driver in > > -current and -stable. I need to know if people are having problems > > with the driver or not. So far I've gotten startlingly little > > feedback. This either means that it's working so well that nobody has > > had any trouble with it, or you guys are all just slackers and are too > > lazy to speak up. > > You left out a third. We don't know better. Well, there is that... > Here's an edited version of my dmesg.boot file: > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > FreeBSD 2.2.7-STABLE #0: Wed Jul 29 18:26:19 MST 1998 I only wrote the driver in August. :) It's been in -stable about a week, and up on www.freebsd.org/~wpaul/3Com for a couple of weeks. > chad@chad.anasazi.com:/usr/src/sys/compile/CHAD > CPU: Pentium/P55C (166.06-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x543 Stepping=3 > Features=0x8001bf > real memory = 33554432 (32768K bytes) > chip0 rev 3 on pci0:0:0 > chip1 rev 1 on pci0:7:0 > chip2 rev 0 on pci0:7:1 > pci0:7:2: Intel Corporation, device=0x7020, class=serial, subclass=0x03 int d irq 9 [no driver assigned] > vx0 <3COM 3C905 Fast Etherlink XL PCI> rev 0 int a irq 11 on pci0:16:0 > mii[*mii*]: disable 'auto select' with DOS util! address 00:60:97:de:2b:a8 > Intel Pentium F00F detected, installing workaround > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > As you can see, I'm running the vx0 driver. It's the one selected by > the installation process. I kept it as I built my custom kernel. > Should I have selected the xl driver then? If so, how would I have > known that? Mea culpa. I made noises about this on -hackers and -current (and on -commiters) and thought people would notice the new driver when they cvsup'ed the latest sources, starting this week. If you don't want to go through the hassle of cvsup'ing everything and building from scratch, you can download the 2.2.x driver from www.freebsd.org/~wpaul/3Com and add it to your existing kernel. There are instructions that explain what do to. You'll probably want to replace 'device vx0' in your kernel config with 'device xl0'. And you'll need to edit your /etc/rc.conf to change all occurances of vx0 to xl0. Note that this driver is only for the 3c90x cards, not the 3c59x cards, which are still supported by the vx driver. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 29 14:20:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07501 for freebsd-current-outgoing; Sat, 29 Aug 1998 14:20:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07496; Sat, 29 Aug 1998 14:20:19 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id RAA08688; Sat, 29 Aug 1998 17:20:09 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sat, 29 Aug 1998 17:20:09 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Bill Paul cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Looking for feedback on xl (3c905/3c905B) driver In-Reply-To: <199808291730.NAA00918@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG works BEAUTIFULLY from a user standpoint, only odd thing is that when i enable a bpfilter program, trafshow/tcpdump it sorta locks up all my processes for a second. it's odd in X as i can movei my mouse, but things like x11amp (linux emulation) lock up for a good 2-3 seconds, then all is well until the program "detaches" from the bpf: releveant info (i hope): dmesg: xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x24 int a irq 3 on pci0.1 5.0 ifconfig: xl0: flags=8843 mtu 1500 inet 206.64.4.154 netmask 0xffffffc0 broadcast 206.64.4.191 ether 00:10:4b:98:fa:3b media: autoselect (100baseTX ) supported media: autoselect 100baseTX 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 10baseT/UTP i have IPFIREWALL, IPVERBOSE compiled into my kernel as well as other odd things: POSIX options, DEVFS and SLICE after an uptime of 23 hours (i downed the machine myself) a netstat -m shows: 48/160 mbufs in use: 34 mbufs allocated to data 14 mbufs allocated to packet headers 25/50/1312 mbuf clusters in use (current/peak/max) 120 Kbytes allocated to network (46% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines note that the machine is not heavily loaded, but it survived a gmake -j in the wine directory recently (was unresponcive for a good 5-10 minutes, but then came back) although that is not network related. network "stuff" being used: NFS, remote X, dns and your usual www/ftp/etc. not i can get over 9megs/second over NFS, it looks REALLY good. only concern is the odd behavior with bpfilter. sorry i don't have more exotic stuff to show such as multicast or whatnot. btw, if i set my mtu higher you think i'll get more performance? thank you again for the driver, Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Sat, 29 Aug 1998, Bill Paul wrote: > Okay people, it's been some time since I put the xl0 driver in -current > and -stable. I need to know if people are having problems with the driver > or not. So far I've gotten startlingly little feedback. This either means > that it's working so well that nobody has had any trouble with it, or > you guys are all just slackers and are too lazy to speak up. > > Basically I'm looking for as many success or failure reports as possible. > If you're having trouble with the driver and you don't tell me about it, > I can't help you, so speak up. If you're not having trouble and it's > working well, I'd like to know that too. > > Here are some things I'd like to know: > > - What kind of adapter you have. Note that a 3c905-TX is NOT THE SAME > as a 3c905B-TX. (See the 'B'? It makes a difference.) Double and triple > check the model. Don't tell me you have a 3c905B when you actually only > have a 3c905. If you want to be really nice, do 'dmesg | grep xl' and > show me the output. > - The driver version you're using. If you obtained the driver by > cvsup'ing -current or -stable, then you have the latest one. If you > downloaded the driver from www.freebsd.org/~wpaul/3Com within the > last week, then you also have the latest one. If you're not sure, > show me the rcsid strings from if_xl.c and if_xlreg.h. > - Does the driver detect all of the adapter's media types correctly? > - Is the system stable? Have you had problems with kernel panics since > you started using the driver? Is mbuf usage normal or does it look > like there's an mbuf leak? (use netstat -m to monitor mbuf usage) > - Type of system (CPU type/speed). Are you using a slower system like > a 486 or older Pentium (P75, P90, P1xx, etc...)? If so, are there > problems with performance? Are you using SCSI disks or IDE disks? > - Type of network to which the adapter is attached. Are you using a > hub? A switch? Crossover cable to another machine? Coax? AUI? If a hub, > are there lots of hosts on the same segment? > - How many adapters in the system. > - How heavily loaded is the system. Is this just a personal machine > with occasional network traffic or is it a heavily used server? > (http, FTP, NFS, login shell box, etc...) Is it a router? > - Observed performance. Does the adapter/driver work well under load? > Does the adapter lock up or otherwise misbehave under high-load > conditions? Are there lots of input or output errors? (use netstat -in > to check) Do you ever have to ifconfig down and ifconfig up the adapter > to reset it? > - 'Out of buffers' problems. Does the 'OACTIVE' flag ever show up when > you do 'ifconfig xl0'? > - Unusual error messages. Are there any diagnostics generated by the > driver that don't look normal? (timeouts, transmission errors, etc...) > - Multicast operation. Is the adapter receiving all the multicast > frames that it should? (Note that the 3c905B adapters have a hash > filter whereas the 3c900 and 3c905 adapters have only a 'receive all > multicast frames' mode, so reports about the 3c905B are more useful.) > - Unusual configurations. Are you using firewalling? Network address > translation? Proxy ARP? IP aliases? Shitloads of IP aliases? Do you > have Lose95/98/NT installed on your machine along with FreeBSD? > Do you have problems warm booting from Lose95/98/NT to FreeBSD? > (Adapter not probed, adapter not reset correctly after warm boot...) > - Benchmarks. Have you compared the xl driver's performance against > any others? What were the numbers? What benchmarks did you use? > Was performace good? Bad? Ugly? > > Here are some things I don't want to hear: > > - "I saw some error but I forgot it, and I didn't write it down. Does > this help?" > - "I saw somewhere you were interested in information about 3c905 > performance with FreeBSD. What exactly do you need to know?" > - "I can give you the information you want, but I wanted to send you a > short note first just to see if you were really interested." > - "You can use Internet Explorer to find out more information about > 3Com products by going to www.3Com.com..." > - "Well, I'm having some trouble, but I don't have time to give you > the details as I'm just about to leave for the airport and fly to > some remote part of deepest, darkest Africa to start a tour with the > Red Cross, and I won't be able to use my computer again for about > three years. But I can try to give you more information when I get > back. Is that okay?" > - "It works just fine with Windows!" > - "It works just fine with Linux!" > - "I can't help you with this 3Com thing, but do you have a driver for > the Gronkulator 2000 board? I've got, like, 20 of them and they only > cost, like, $5 each." > - "D00d, got any war3z?" > - "Are you being investigated?" > - "How do I get FreeBSD? I have Windows 98 and the Internet; will it > work with that?" > > So speak up everyone. Send your cards and letters to > wpaul@skynet.ctr.columbia.edu. Operators are standing by. > > -Bill > > -- > ============================================================================= > -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu > Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research > Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City > ============================================================================= > "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" > ============================================================================= > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 29 14:53:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09700 for freebsd-current-outgoing; Sat, 29 Aug 1998 14:53:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (castles153.castles.com [208.214.165.153]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09686; Sat, 29 Aug 1998 14:53:13 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id OAA08636; Sat, 29 Aug 1998 14:50:21 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808291450.OAA08636@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein cc: Bill Paul , stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Looking for feedback on xl (3c905/3c905B) driver In-reply-to: Your message of "Sat, 29 Aug 1998 17:20:09 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Aug 1998 14:50:20 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ifconfig: > xl0: flags=8843 mtu 1500 > inet 206.64.4.154 netmask 0xffffffc0 broadcast 206.64.4.191 > ether 00:10:4b:98:fa:3b > media: autoselect (100baseTX ) > supported media: autoselect 100baseTX 100baseTX > 100baseTX 10baseT/UTP 10baseT/UTP > 10baseT/UTP ... > btw, if i set my mtu higher you think i'll get more performance? No; 1500 is the conventional limit. If you go larger, you stop being Ethernet. ObPedantAvoidance: yes, there are standards for larger frames. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 29 17:32:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20081 for freebsd-current-outgoing; Sat, 29 Aug 1998 17:32:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from darkstar.vmx (uvo-86.univie.ac.at [131.130.230.86]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA20076 for ; Sat, 29 Aug 1998 17:32:44 -0700 (PDT) (envelope-from root@darkstar.psa.at) Received: (qmail 5520 invoked by uid 0); 30 Aug 1998 00:24:32 -0000 Message-ID: <19980830022432.A5501@compufit.at> Date: Sun, 30 Aug 1998 02:24:32 +0200 From: Alexander Sanda To: freebsd-current@FreeBSD.ORG Subject: IPFILTER LKM ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wonder, if everyone has managed to build IPFILTER as a lkm without doing ugly things :) First, I tried it "the normal way" but without success. Activating IPFILTER_LKM doesn't result in a loadable module, so I disabled the "options IPFILTER" which resulted in no ipfilter at all. The lkm build process in src/lkm doesn't seem to know anything about if_ipl.o and the build process in src/contrib/ipfilter doesn't work on -current (at least it doesn't for me). However, after looking a bit into the code, I managed to build the if_ipl.o module from the sources in sys/netinet. I wrote my own makefile (derived from the makefile in src/contrib/ipfilter) and corrected 2 lines in mlf_ipl.c (MOD_MISC() instead of MOD_DECL, and updated DISPATCH() ). I rebuilt the kernel with IPFILTER disabled and IPFILTER_LKM enabled, compiled the ipfilter module, and everthing seems to work. Am I doing something wrong here ? I'am not a very experienced kernel guy, so I would like to consult the gurus here. -- # /AS/ http://privat.schlund.de/entropy/ # # # # XX has detected, that your mouse cursor has changed position. Please # # restart XX, so it can be updated. -- From The Gimp manual # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 29 18:39:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24149 for freebsd-current-outgoing; Sat, 29 Aug 1998 18:39:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA24144; Sat, 29 Aug 1998 18:39:28 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id VAA01492; Sat, 29 Aug 1998 21:41:33 -0400 From: Bill Paul Message-Id: <199808300141.VAA01492@skynet.ctr.columbia.edu> Subject: Re: Looking for feedback on xl (3c905/3c905B) driver To: bright@hotjobs.com (Alfred Perlstein) Date: Sat, 29 Aug 1998 21:41:32 -0400 (EDT) Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: from "Alfred Perlstein" at Aug 29, 98 05:20:09 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Alfred Perlstein had to walk into mine and say: > works BEAUTIFULLY from a user standpoint, only odd thing is that when i > enable a bpfilter program, trafshow/tcpdump it sorta locks up all my > processes for a second. it's odd in X as i can movei my mouse, but things > like x11amp (linux emulation) lock up for a good 2-3 seconds, then all is > well until the program "detaches" from the bpf: This happens because changing the interface flags (via xl_ioctl(), when setting the IFF_PROMISC flag) causes xl_init() to be invoked, and xl_init() forcibly puts the interface into an initialized state, flushes out the receive and transmit queues and resets the receiver and transmitter. The receive and transmit reset appears to take some time, during which NIC operations are temporarily suspended. This is probably a bit much considering that the only thing that really needs to be done is to set the RX filter bits to allow reception of all frames. I think I inherited this behavior from the fxp driver, which is what I used as a reference when I got started with driver writing. I'll look into changing this. Note that using BPF without setting the IFF_PROMISC flag shouldn't cause any delay. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 29 19:07:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27452 for freebsd-current-outgoing; Sat, 29 Aug 1998 19:07:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27443 for ; Sat, 29 Aug 1998 19:06:57 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA17384; Sun, 30 Aug 1998 11:35:58 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA06057; Sun, 30 Aug 1998 11:35:56 +0930 (CST) Message-ID: <19980830113556.P17530@freebie.lemis.com> Date: Sun, 30 Aug 1998 11:35:56 +0930 From: Greg Lehey To: "Gregory P. Smith" , tom@uniserve.com Cc: current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter References: <199808231741.KAA05988@hub.freebsd.org> <199808241845.LAA00873@ryouko.nas.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808241845.LAA00873@ryouko.nas.nasa.gov>; from Gregory P. Smith on Mon, Aug 24, 1998 at 11:45:02AM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 24 August 1998 at 11:45:02 -0700, Gregory P. Smith wrote: > tom@uniserve.com wrote: >> Gigabit ethernet is 125MB/s, so would use more of PCI. The only hope is >> multiple independant PCI buses (some motherboards already have this). > > Good luck getting a single x86 CPU to handle the interrupt load of even > a single card with the overhead of processing 1500 byte packets at > Gigabit speeds... (based on observations of other Gig speed class > drivers and NICs I've seen). ;) Who said that gigabit Ethernet transfers data between individual machines at 125 MB/s? It's the theoretical maximum speed of a broadcast medium. Connect 100 machines together over gigabit Ethernet and you can (theoretically) still transfer 1 MB/s without problems. Sure, there are cases where you may want to use the bandwidth, but IMO that's not the real purpose of gigabit Ethernet. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 29 19:56:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02248 for freebsd-current-outgoing; Sat, 29 Aug 1998 19:56:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02243 for ; Sat, 29 Aug 1998 19:56:35 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id MAA11594 for ; Sun, 30 Aug 1998 12:25:38 +0930 (CST) Received: by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA01306; Sun, 30 Aug 1998 12:25:38 +0930 Date: Sun, 30 Aug 1998 12:25:38 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@mercury To: current@FreeBSD.ORG Subject: IPFW showing extra lines Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since updating to a current kernel and rebuilding the world, my ipfw is showing a bunch of extraneous firewall rules of the form 00000 0 0 deny ip from any to any Specifically, ipfw -at l now shows a total of 1024 lines, whereas I should only have about 15 firewall rules set up. Relevant parts of my kernel config: options IPFIREWALL options IPFIREWALL_VERBOSE #options IPFIREWALL_DEFAULT_TO_ACCEPT I've seen this bug reported here before; is someone looking at this? Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 29 20:50:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05991 for freebsd-current-outgoing; Sat, 29 Aug 1998 20:50:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05986 for ; Sat, 29 Aug 1998 20:50:11 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-89.camalott.com [208.229.74.89]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id WAA24771; Sat, 29 Aug 1998 22:50:37 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA05934; Sat, 29 Aug 1998 22:48:47 -0500 (CDT) (envelope-from joelh) Date: Sat, 29 Aug 1998 22:48:47 -0500 (CDT) Message-Id: <199808300348.WAA05934@detlev.UUCP> To: tlambert@primenet.com CC: seggers@semyam.dinoco.de, mi@video-collage.com, current@FreeBSD.ORG In-reply-to: <199808290134.SAA29280@usr01.primenet.com> (message from Terry Lambert on Sat, 29 Aug 1998 01:34:16 +0000 (GMT)) Subject: Re: recovering disk From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808290134.SAA29280@usr01.primenet.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> [Now the questions is how often this happens. Would it be worth to >>> make an additional disklabel and - for systems having it - fdisk >>> partition table recovery tool? How's the opinion on this?] >> You know what I'd like? A general disk editor, that can take its >> input by the block or by the file, with a hex editor as well as some >> special-purpose viewers. Something like Norton's Disk Editor. Said >> tool has been amazingly useful to me on many an occasion. > xvi /dev/rsd0e. Let's start with me reminding you that I had asked for special-purpose viewers, like superblock and directory block viewers or some such. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 29 22:57:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16854 for freebsd-current-outgoing; Sat, 29 Aug 1998 22:57:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA16849 for ; Sat, 29 Aug 1998 22:57:32 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id AAA23313; Sun, 30 Aug 1998 00:55:33 -0500 (CDT) Message-ID: <19980830005533.31625@futuresouth.com> Date: Sun, 30 Aug 1998 00:55:33 -0500 From: "Matthew D. Fuller" To: Greg Lehey Cc: "Gregory P. Smith" , tom@uniserve.com, current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter References: <199808231741.KAA05988@hub.freebsd.org> <199808241845.LAA00873@ryouko.nas.nasa.gov> <19980830113556.P17530@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980830113556.P17530@freebie.lemis.com>; from Greg Lehey on Sun, Aug 30, 1998 at 11:35:56AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 30, 1998 at 11:35:56AM +0930, Greg Lehey woke me up to tell me: > > On Monday, 24 August 1998 at 11:45:02 -0700, Gregory P. Smith wrote: > > > > Good luck getting a single x86 CPU to handle the interrupt load of even > > a single card with the overhead of processing 1500 byte packets at > > Gigabit speeds... (based on observations of other Gig speed class > > drivers and NICs I've seen). ;) > > Who said that gigabit Ethernet transfers data between individual > machines at 125 MB/s? It's the theoretical maximum speed of a > broadcast medium. Connect 100 machines together over gigabit Ethernet > and you can (theoretically) still transfer 1 MB/s without problems. > > Sure, there are cases where you may want to use the bandwidth, but IMO > that's not the real purpose of gigabit Ethernet. For a general setup, I'd agree with that. But didn't this thread start (or maybe it was another related thread) with using this in routing between multiple smaller nets? If you're using a box with 1 (or 2) of these to route between two physical subnets, it's not unlikely at all that that single machine is going to need to run 100+ MB/s. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message