From owner-freebsd-current Sun Aug 16 00:28:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10056 for freebsd-current-outgoing; Sun, 16 Aug 1998 00:28: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 AAA10049 for ; Sun, 16 Aug 1998 00:28:46 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id IAA03887; Sun, 16 Aug 1998 08:27:18 +0100 (BST) Date: Sun, 16 Aug 1998 08:27:18 +0100 (BST) From: Doug Rabson To: Terry Lambert cc: mike@smith.net.au, jdp@polstra.com, current@FreeBSD.ORG Subject: Re: ELF problems to occur In-Reply-To: <199808152125.OAA23138@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, 15 Aug 1998, Terry Lambert wrote: > > Loading an ELF kernel with the new bootstrap is pretty easy. I did it > > today on the alpha. It should be possible to use the same ELF loader for > > i386 with some extra work. > > Was this a NetBSD ELF kernel or a FreeBSD ELF kernel? 8-). FreeBSD of course! -- 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 Sun Aug 16 01:20:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12821 for freebsd-current-outgoing; Sun, 16 Aug 1998 01:20:20 -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 BAA12780; Sun, 16 Aug 1998 01:20:01 -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 JAA23247; Sun, 16 Aug 1998 09:19:29 +0100 (BST) Message-ID: <35D69611.A45E9EBE@tdx.co.uk> Date: Sun, 16 Aug 1998 09:19:29 +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: Gary Palmer CC: current@FreeBSD.ORG Subject: Re: Can't build kernel with 15/08/98 @ 23:17 source References: <9673.903228490@gjp.erols.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary Palmer wrote: > > [snip] > > Do you have: > > controller scbus0 at ahc0 > controller scbus1 at ahc1 > controller scbus2 at ahc2 Argh! - Told you pilot error ;-) - I've just added another controller to the machine, and the boot device's controller got moved around, hence all my wiring down the SCSI devices was mucking up... I commented out all the code to wire down the devices, including the 'controller' lines :-) > > Also? > > You could actually cut this down do: > > controller ahc0 > controller scbus0 > [snip] Yes, I know - once I've got the new controller map sorted out, I'll probably be wiring the devices down again, though at this rate I may just leave them to auto assign ;-) Thanks for the help! Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 01:41:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14765 for freebsd-current-outgoing; Sun, 16 Aug 1998 01:41:32 -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 BAA14760 for ; Sun, 16 Aug 1998 01:41:29 -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 EAA13849 for ; Sun, 16 Aug 1998 04:40:56 -0400 (EDT) (envelope-from gjp@gjp.erols.com) To: current@FreeBSD.ORG From: "Gary Palmer" Subject: make installworld failing in share Date: Sun, 16 Aug 1998 04:40:56 -0400 Message-ID: <13845.903256856@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone else having problems in the new locale stuff? 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 16 02:05:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17064 for freebsd-current-outgoing; Sun, 16 Aug 1998 02:05:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay1.aha.ru (relay1.aha.ru [195.2.83.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17058 for ; Sun, 16 Aug 1998 02:05:26 -0700 (PDT) (envelope-from osa@serv.etrust.ru) Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112]) by relay1.aha.ru (8.9.1/aha-r/0.04B) with ESMTP id NAA04471; Sun, 16 Aug 1998 13:04:44 +0400 (MSD) Received: by sunny.aha.ru id NAA03041; (8.8.8/vak/1.9) Sun, 16 Aug 1998 13:03:53 +0400 (MSD) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma002955; Sun Aug 16 13:03:26 1998 Received: from ozz.etrust.ru by serv.etrust.ru with ESMTP id NAA21373; (8.9.1/vak/1.9) Sun, 16 Aug 1998 13:06:22 +0400 (MSD) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.0) with SMTP id NAA00342; Sun, 16 Aug 1998 13:03:40 +0400 (MSD) Date: Sun, 16 Aug 1998 13:03:39 +0400 (MSD) From: oZZ!!! X-Sender: osa@localhost To: ben@rosengart.com cc: Simon Shapiro , freebsd-current@FreeBSD.ORG Subject: Re: Where is my 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 Sat, 15 Aug 1998, Snob Art Genre wrote: > I added "#include " to my copy of big5.c and everything > compiled. > > However, the make world died installing in usr.bin/mklocale with this: > > install: mkstemp: /usr/share/locale/zh_TW.BIG5/INS@4350 for > /usr/share/locale/zh > _TW.BIG5/LC_CTYPE: No such file or directory > If don't want use this feature, you trying following Manualy: # mkdir /usr/share/locale/zh_TW.BIG5 # cp /usr/share/locale/US-ASCII/LC_* /usr/share/locale/zh_TW.BIG5 # cd /usr/src # make installworld Rgdz, Osokin Sergey aka oZZ, osa@chat.ru FreeBSD - Power to Serve! http://www.chat.ru/~osa/main.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 03:12:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA21925 for freebsd-current-outgoing; Sun, 16 Aug 1998 03:12:20 -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 DAA21917 for ; Sun, 16 Aug 1998 03:12:18 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from grjottunagard.ifi.uio.no (2602@grjottunagard.ifi.uio.no [129.240.64.131]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id MAA00794; Sun, 16 Aug 1998 12:11:10 +0200 (MET DST) Received: (from dag-erli@localhost) by grjottunagard.ifi.uio.no ; Sun, 16 Aug 1998 12:11:09 +0200 (MET DST) Mime-Version: 1.0 To: Bruce Evans Cc: jdp@polstra.com, julian@whistle.com, current@FreeBSD.ORG Subject: Re: Funky DEVFS stuff. References: <199808151956.FAA24483@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: 16 Aug 1998 12:11:08 +0200 In-Reply-To: Bruce Evans's message of "Sun, 16 Aug 1998 05:56:13 +1000" Message-ID: Lines: 17 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 DAA21919 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > > Also, 'b' used to be magic (reserved for swap) in some Unix variants. > > Not for us, right? > It is conventionally reserved for swap in FreeBSD too. It is a bit > more than conventionally reserved for kernel dumps in FreeBSD - > dumps are not permitted on devices whose minor is 1 modulo 8 (see > kern_shutdown.c:dumpsys() and autoconf.c:setdumpdev()). Except on DEVFS/SLICE systems, where this check is commented out since the minor numbers are not as predictable. By the way, how much work would it be to make using more than 8 partitions per slice possible? 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 Sun Aug 16 03:29:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24321 for freebsd-current-outgoing; Sun, 16 Aug 1998 03:29:36 -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 DAA24315 for ; Sun, 16 Aug 1998 03:29:29 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from grjottunagard.ifi.uio.no (2602@grjottunagard.ifi.uio.no [129.240.64.131]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id MAA01334; Sun, 16 Aug 1998 12:28:57 +0200 (MET DST) Received: (from dag-erli@localhost) by grjottunagard.ifi.uio.no ; Sun, 16 Aug 1998 12:28:56 +0200 (MET DST) Mime-Version: 1.0 To: John Paul Campbell Cc: freebsd-current@FreeBSD.ORG Subject: Re: make world error in libstdc++ References: <35D5DEA2.6EE9E85B@rice.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: 16 Aug 1998 12:28:56 +0200 In-Reply-To: John Paul Campbell's message of "Sat, 15 Aug 1998 19:16:50 +0000" Message-ID: Lines: 17 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 DAA24317 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Paul Campbell writes: > The file I used to cvsup the sources was: > > *default host=cvsup.FreeBSD.org > *default base=/usr/local/etc/cvsup > *default prefix=/usr > *default release=cvs delete use-rel-suffix compress > *default delete use-rel-suffix > *default compress > src-all > cvs-crypto Foo! You forgot the tag! 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 Sun Aug 16 03:41:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25170 for freebsd-current-outgoing; Sun, 16 Aug 1998 03:41:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.pipeline.ch (freefall.pipeline.ch [195.134.128.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA25033 for ; Sun, 16 Aug 1998 03:39:48 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.140.6]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA320; Sun, 16 Aug 1998 12:38:02 +0200 Message-ID: <35D6B6C7.C9ABD9C0@pipeline.ch> Date: Sun, 16 Aug 1998 12:39:03 +0200 From: Andre Oppermann Organization: Internet Business Solutions Ltd. X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: John Birrell CC: current@FreeBSD.ORG Subject: Re: ELF problems to occur References: <199808152148.HAA13299@cimlogic.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Birrell wrote: > > Terry Lambert wrote: > > > Loading an ELF kernel with the new bootstrap is pretty easy. I did it > > > today on the alpha. It should be possible to use the same ELF loader for > > > i386 with some extra work. > > > > Was this a NetBSD ELF kernel or a FreeBSD ELF kernel? 8-). > > FreeBSD/Alpha is now using a native kernel. I'm about to remove all the > NetBSD kludges from libc that provided the NetBSD syscall interface we've > used until now. Pls. tell me when it's time to buy an Alpha box! TIA -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 03:51:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27215 for freebsd-current-outgoing; Sun, 16 Aug 1998 03:51:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA27190 for ; Sun, 16 Aug 1998 03:51:24 -0700 (PDT) (envelope-from pierre.dampure@k2c.co.uk) Received: (qmail 18797 invoked from network); 16 Aug 1998 10:50:50 -0000 Received: from userk929.uk.uudial.com (HELO k2c.co.uk) (193.149.72.251) by smtp.dial.pipex.com with SMTP; 16 Aug 1998 10:50:50 -0000 Message-ID: <35D6B8BD.EE8D13B5@k2c.co.uk> Date: Sun, 16 Aug 1998 11:47:25 +0100 From: "Pierre Y. Dampure" Organization: K2C Limited X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Gary Palmer CC: current@FreeBSD.ORG Subject: Re: make installworld failing in share References: <13845.903256856@gjp.erols.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary Palmer wrote: > Anyone else having problems in the new locale stuff? > > 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 Yep. I just created the BIG5 directory it needed and it worked okay. Best Regards, Pierre Y. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 03:57:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27923 for freebsd-current-outgoing; Sun, 16 Aug 1998 03:57:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27914 for ; Sun, 16 Aug 1998 03:57:19 -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 UAA04271; Sun, 16 Aug 1998 20:56:43 +1000 Date: Sun, 16 Aug 1998 20:56:43 +1000 From: Bruce Evans Message-Id: <199808161056.UAA04271@godzilla.zeta.org.au> To: bde@zeta.org.au, dag-erli@ifi.uio.no Subject: Re: Funky DEVFS stuff. Cc: current@FreeBSD.ORG, jdp@polstra.com, julian@whistle.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > Also, 'b' used to be magic (reserved for swap) in some Unix variants. >> > Not for us, right? >> It is conventionally reserved for swap in FreeBSD too. It is a bit >> more than conventionally reserved for kernel dumps in FreeBSD - >> dumps are not permitted on devices whose minor is 1 modulo 8 (see >> kern_shutdown.c:dumpsys() and autoconf.c:setdumpdev()). > >Except on DEVFS/SLICE systems, where this check is commented out since >the minor numbers are not as predictable. DEVFS/SLICE systems are just broken. There are 2 checks (see above), but only one is ifdefed out. >By the way, how much work would it be to make using more than 8 >partitions per slice possible? None. Everything is possible in software :-), and in theory the MAXPARTITIONS parameter can simply be increased up to about 22 as in NetBSD. You also have to change at least the size of openmask bitmap variables in FreeBSD. Our default of setting the number of partitions to the max isn't so good if the max is large. Sysinstall would probably have problems displaying 22 partitions on a 25-line screen. It would be more work to support a flexibly sized array of partitions - several places want `struct disklabel' to actually be a struct. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 04:20:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA02276 for freebsd-current-outgoing; Sun, 16 Aug 1998 04:20:57 -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 EAA02271 for ; Sun, 16 Aug 1998 04:20:55 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from grjottunagard.ifi.uio.no (2602@grjottunagard.ifi.uio.no [129.240.64.131]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id NAA03671; Sun, 16 Aug 1998 13:20:13 +0200 (MET DST) Received: (from dag-erli@localhost) by grjottunagard.ifi.uio.no ; Sun, 16 Aug 1998 13:20:13 +0200 (MET DST) Mime-Version: 1.0 To: Bruce Evans Cc: current@FreeBSD.ORG, jdp@polstra.com, julian@whistle.com Subject: Re: Funky DEVFS stuff. References: <199808161056.UAA04271@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: 16 Aug 1998 13:20:12 +0200 In-Reply-To: Bruce Evans's message of "Sun, 16 Aug 1998 20:56:43 +1000" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id EAA02272 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > > Except on DEVFS/SLICE systems, where this check is commented out since > > the minor numbers are not as predictable. > DEVFS/SLICE systems are just broken. There are 2 checks (see above), > but only one is ifdefed out. Works perfectly on my boxen. 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 Sun Aug 16 04:23:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA02545 for freebsd-current-outgoing; Sun, 16 Aug 1998 04:23:48 -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 EAA02536 for ; Sun, 16 Aug 1998 04:23:41 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from grjottunagard.ifi.uio.no (2602@grjottunagard.ifi.uio.no [129.240.64.131]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id NAA03742; Sun, 16 Aug 1998 13:22:47 +0200 (MET DST) Received: (from dag-erli@localhost) by grjottunagard.ifi.uio.no ; Sun, 16 Aug 1998 13:22:47 +0200 (MET DST) Mime-Version: 1.0 To: Bruce Evans Cc: current@FreeBSD.ORG, jdp@polstra.com, julian@whistle.com Subject: Re: Funky DEVFS stuff. References: <199808161056.UAA04271@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: 16 Aug 1998 13:22:46 +0200 In-Reply-To: Bruce Evans's message of "Sun, 16 Aug 1998 20:56:43 +1000" Message-ID: Lines: 12 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 EAA02539 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > > Except on DEVFS/SLICE systems, where this check is commented out since > > the minor numbers are not as predictable. > DEVFS/SLICE systems are just broken. There are 2 checks (see above), > but only one is ifdefed out. Correction: setting the dump device works on my boxen. Dumping doesn't. I'll fix this ASAP. 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 Sun Aug 16 05:36:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA06902 for freebsd-current-outgoing; Sun, 16 Aug 1998 05:36:49 -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 FAA06897 for ; Sun, 16 Aug 1998 05:36:45 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id WAA14758; Sun, 16 Aug 1998 22:44:39 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808161244.WAA14758@cimlogic.com.au> Subject: Re: ELF problems to occur In-Reply-To: from "Matthew N. Dodd" at "Aug 15, 98 07:12:10 pm" To: winter@jurai.net (Matthew N. Dodd) Date: Sun, 16 Aug 1998 22:44:39 +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 Matthew N. Dodd wrote: > On Sun, 16 Aug 1998, John Birrell wrote: > > FreeBSD/Alpha is now using a native kernel. I'm about to remove all the > > NetBSD kludges from libc that provided the NetBSD syscall interface we've > > used until now. > > If they're non-intrusive for native FreeBSD systems, why not leave them > in. > > It would make bootstrapping another port from NetBSD that much easier. That's true. I haven't asked for opinions, but I was working on the theory that it is not difficult to do if and when it is required again and by deleting the hacks now I would avoid the bit-rot that will occur. The FreeBSD tree is now very close to being able to cross-build one architecture on another architecture, subject to the availability of cross tools, so the need to keep a NetBSD syscall interface seems unnecessary. As it happens, building elf on and aout x86 system is virtually a cross-build. There are a few bogons that are preventing a true cross-build. I've been unsuccessful trying to convince someone (who knows who he is) that this is achievable now as part of the preparation for the switch to elf and the release of 3.0. I was expecting that people would be prepared to concede some ground to allow this to happen, but that doesn't seem to be happening. 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 Sun Aug 16 05:45:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07503 for freebsd-current-outgoing; Sun, 16 Aug 1998 05:45:20 -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 FAA07495 for ; Sun, 16 Aug 1998 05:45:15 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id WAA14771; Sun, 16 Aug 1998 22:53:12 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808161253.WAA14771@cimlogic.com.au> Subject: Re: ELF problems to occur In-Reply-To: <35D6B6C7.C9ABD9C0@pipeline.ch> from Andre Oppermann at "Aug 16, 98 12:39:03 pm" To: oppermann@pipeline.ch (Andre Oppermann) Date: Sun, 16 Aug 1998 22:53:12 +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 Andre Oppermann wrote: > John Birrell wrote: > > > > Terry Lambert wrote: > > > > Loading an ELF kernel with the new bootstrap is pretty easy. I did it > > > > today on the alpha. It should be possible to use the same ELF loader for > > > > i386 with some extra work. > > > > > > Was this a NetBSD ELF kernel or a FreeBSD ELF kernel? 8-). > > > > FreeBSD/Alpha is now using a native kernel. I'm about to remove all the > > NetBSD kludges from libc that provided the NetBSD syscall interface we've > > used until now. > > Pls. tell me when it's time to buy an Alpha box! Would a FreeBSD/Alpha 3.0 release be sufficient for you to do that? It might be called a beta release, or perhaps a snapshot. -- 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 Sun Aug 16 06:16:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA09978 for freebsd-current-outgoing; Sun, 16 Aug 1998 06:16:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA09969 for ; Sun, 16 Aug 1998 06:16:22 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id GAA00184; Sun, 16 Aug 1998 06:15:30 -0700 (PDT) Message-Id: <199808161315.GAA00184@implode.root.com> To: Terry Lambert cc: current@FreeBSD.ORG, karl@mcs.net Subject: Re: Better VM patches (was Tentative fix for VM bug) In-reply-to: Your message of "Sun, 16 Aug 1998 01:13:33 -0000." <199808160113.SAA17303@usr07.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 16 Aug 1998 06:15:30 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The problem with vm_object_page_remove() is that in the clean_only != 0 >case, the page is marked invalid. > >This will result in orphaned pages. I don't think "orphaned" pages will be created, but I can imagine that changes might be lost in the wired && clean_only case. I agree that this appears to be a bug. It might be a bug in the wired && !clean_only case, too - in other words, setting valid=0 might never be correct for wired pages. >This may be the source of the: > > * XXX: sometimes we get pages which aren't wired down or on any queue - > * we need to put them on the inactive queue also, otherwise we lose > * track of them. Paul Mackerras (paulus@cs.anu.edu.au) 9-Jan-93. > >comment in vm_page.c, and it may be the source of the zero page >phenomenon. That comment simply means what it says and must be taken in the context of the function where it appears (vm_page_deactivate). The system sometimes needs to put a page on a queue - any queue, and vm_page_deactivate needs to be able to handle the case of not-on-any-queue. Really, the comment is obsolete and dates back to a time when the VM system didn't manage the page queues properly. >Another problem in the mmap code is that when the vnode_pager object >is created, it is set to be the number of pages times the page size >in length; but also in vnode_pager, the setsize on the object sets >the length to the actual file length. > >This discrepancy opens a window in which some changes may be lost. My reading of the code shows that the object size is set to the rounded-up index. vnp_size is set to the unrounded new size, but that's expected and I don't see any bugs related to doing that; rounding it will likely break the proper reading of partial pages. Am I missing something? vnp_size is mostly private to the vnode_pager. The rounded-up object->size is used outside of the vnode pager. >John also suggested another change for detecting a case where page >orphans can be created. in vm_page.c, it's possible that an object >entry in the page insert function will overwrite an existing entry; >I added a DIAGNOSTIC panic to catch this when it happens. You mean that there can be multiple pages at the same offset? It would be bad if that happend, but I'm skeptical that it actually does. >*************** >*** 990,995 **** >--- 990,1002 ---- > handle, OFF_TO_IDX(objsize), prot, foff); > if (object == NULL) > return (type == OBJT_DEVICE ? EINVAL : ENOMEM); >+ /* >+ * XXX we are in a race here. If the file is extended >+ * between the time we get the object and the time >+ * we set the size, then we lose... >+ */ >+ if (!(flags & MAP_ANON) && vp->v_type != VCHR) >+ object->un_pager.vnp.vnp_size = vat.va_size; Hmmm. >+ /* >+ * The object is allocated to a page boundary. This is >+ * incorrect if page is only partially backed by the vp; >+ * we must fix this up in the caller. >+ */ > object->un_pager.vnp.vnp_size = (vm_ooffset_t) size * PAGE_SIZE; I think the above change is wrong. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 07:14:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15008 for freebsd-current-outgoing; Sun, 16 Aug 1998 07:14:45 -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 HAA15003 for ; Sun, 16 Aug 1998 07:14:44 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id HAA17262; Sun, 16 Aug 1998 07:14:11 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd017251; Sun Aug 16 07:14:10 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id HAA16245; Sun, 16 Aug 1998 07:14:06 -0700 (MST) From: Terry Lambert Message-Id: <199808161414.HAA16245@usr08.primenet.com> Subject: Re: Better VM patches (was Tentative fix for VM bug) To: dg@root.com Date: Sun, 16 Aug 1998 14:14:05 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG, karl@mcs.net In-Reply-To: <199808161315.GAA00184@implode.root.com> from "David Greenman" at Aug 16, 98 06:15:30 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 > >This may be the source of the: > > > > * XXX: sometimes we get pages which aren't wired down or on any queue - > > * we need to put them on the inactive queue also, otherwise we lose > > * track of them. Paul Mackerras (paulus@cs.anu.edu.au) 9-Jan-93. > > > >comment in vm_page.c, and it may be the source of the zero page > >phenomenon. > > That comment simply means what it says and must be taken in the context > of the function where it appears (vm_page_deactivate). The system sometimes > needs to put a page on a queue - any queue, and vm_page_deactivate needs to > be able to handle the case of not-on-any-queue. Really, the comment is > obsolete and dates back to a time when the VM system didn't manage the page > queues properly. Then it should be replaced with a DIAGNOSTIC panic. The issue that's being addressed here is the "XXX", more than anything else. I really think there are three cases in the code where pages can be orphaned; I think the object code only deals with one of these; the other two can be implemented with late-binding reaps without a problem (ie: the code is not technically correct, except in reduction). > >Another problem in the mmap code is that when the vnode_pager object > >is created, it is set to be the number of pages times the page size > >in length; but also in vnode_pager, the setsize on the object sets > >the length to the actual file length. > > > >This discrepancy opens a window in which some changes may be lost. > > My reading of the code shows that the object size is set to the rounded-up > index. vnp_size is set to the unrounded new size, but that's expected and > I don't see any bugs related to doing that; rounding it will likely break the > proper reading of partial pages. Am I missing something? vnp_size is mostly > private to the vnode_pager. The rounded-up object->size is used outside of > the vnode pager. OK, consider the boundry cases: 1) The page is less than the boundary, but is extended to less than the boundary. This is seen as a truncation by setsize. 2) The page is less than the boundary, but is extended to the boundary. This is seen as a NOP by the first compare in the setsize code. 3) The mapped page is written (an implicit extend without a write fault -- this is, I believe, Karl Denniger's case when the code provided failed -- between the mapping and the actual size). There are actually two more failure modes, but they are hellaciously complex to describe. 8-(. > >John also suggested another change for detecting a case where page > >orphans can be created. in vm_page.c, it's possible that an object > >entry in the page insert function will overwrite an existing entry; > >I added a DIAGNOSTIC panic to catch this when it happens. > > You mean that there can be multiple pages at the same offset? It would > be bad if that happend, but I'm skeptical that it actually does. So was I, when John suggested it. John's suggested change would detect an orphaning event. Since I believe that what is happening is actually an alias event (for the bug that is at the top of my list), the DIAGNOSTIC change is a NOP, as far as I'm concerned. But it's a nice thing to have to detect the XXX comment case, which, in theory, should never occur (ie: a page should be on a queue, and this recovery mechanism was a kludge which covers the real problem, which is orphaned pages). > >+ /* > >+ * XXX we are in a race here. If the file is extended > >+ * between the time we get the object and the time > >+ * we set the size, then we lose... > >+ */ > >+ if (!(flags & MAP_ANON) && vp->v_type != VCHR) > >+ object->un_pager.vnp.vnp_size = vat.va_size; > > Hmmm. This is, in fact, the most interesting change, as far as Karl Denniger is concerned. I would like to close the race window here (by adding an "actual_length" parameter to the various "allocate" routines) to see if this resolves Karl's remaining bugs (per the SPLVM bug noted in the comment here)... I suspect that Karl has two bugs; the one I hit, and a sepoerate one, and the remaining window accounts for a tiny fraction of the misbehaviour that he is still experiencing. The real way out of this mes is to reference cont everything and to note 1->2 transitions for page references. This takes a significant amount of code and structure changes to accomplish; it would be nice if the problem were a bit easier to duplicate, but it's not. I have to make changes that narrow down the problem instead of resolve it; A/B tests. 8-(. > >+ /* > >+ * The object is allocated to a page boundary. This is > >+ * incorrect if page is only partially backed by the vp; > >+ * we must fix this up in the caller. > >+ */ > > object->un_pager.vnp.vnp_size = (vm_ooffset_t) size * PAGE_SIZE; > > I think the above change is wrong. It's only a comment. The actual change is: if (!(flags & MAP_ANON) && vp->v_type != VCHR) object->un_pager.vnp.vnp_size = vat.va_size; But me too, since it allows a race window. A correct fix would get rid of the window by passing an additional parameter to those alloc routines that need to care about actual backing length (ie: vnode_pager). It was more of a test case than anything else... if the problem decreased, it points to the race window that was partially closed. If it didn't, then the operation was a boundary condition, which, while nice to address, did nothing to address reported bugs. For non-page-aligned pagers, this would be important; for all others, I expect that round_page() would be used to assure page alignment. This is very tricky; I nearly posted code to page align setsize instead, but that would have been a mistake, since the real issue is the bzero that occurs in the setsize code. The point is to set the size in such a way that it is not misinterpreted as a truncate between the set event and the truncation event handler. This is the remaining race. A very real problem here is that the code is hideously poorly commented, which makes fixes problematic. I haven't investigated what it would take to put asserts of locking state in there; from a naieve examination of the code, there would need to be a parent map pointer in vm_map_t that was used to see if the parent was locked (this may exist; I haven't looked for it). The PITA is that there is an implicit rather than an explicit hierarchical lock relationship. 8-(. At a minimum, it would be nice if each function asserted its assumptions with regard to locks based on its parameters... at least in the DIAGNOSTIC case, so that runtime checks could be enabled. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 07:31:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16274 for freebsd-current-outgoing; Sun, 16 Aug 1998 07:31:25 -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 HAA16265 for ; Sun, 16 Aug 1998 07:31:18 -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 JAA23187; Sun, 16 Aug 1998 09:30:25 -0500 (CDT) Message-Id: <199808161430.JAA23187@ns.tar.com> From: "Richard Seaman, Jr." To: "John Birrell" , "Brian Cully" , "Daniel Eischen" Cc: "freebsd-current@FreeBSD.ORG" Date: Sun, 16 Aug 98 09:30:25 -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: Bug in pthread scheduler? (Was pthreads woes revisited) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Aug 1998 10:06:43 -0400, Brian Cully wrote: >On Thu, Aug 06, 1998 at 05:13:02PM -0400, Daniel Eischen wrote: >> You're not adding the pthread_yield() call that I added after >> the pthread_cond_signal(). Your program is bogus because there >> is no guarantee that the main thread will release the CPU in >> order for the other task to run. You need to perform some >> sort of blocking operation after the pthread_cond_signal. I >> chose to use pthread_yield, although sleep would work just as >> well. > >Do'h! I missed that. That did make the sample program work, so >it looks like the error was mine all along, sorry for troubling >everybody. Actually, its not at all clear to me that you need the pthread_yield() call. In looking at the pthread scheduler, it appears that the scheduler should preempt (with in the context of the process) the main thread periodically. It also appears that there might be a bug in the scheduler code. Try the following diff and see what you get. *** uthread_kern.c Sun Aug 16 09:07:14 1998 --- uthread_kern.c.orig Sun Aug 16 09:06:17 1998 *************** *** 661,667 **** * Do a sigreturn to restart the thread that * was interrupted by a signal: */ - _thread_kern_in_sched = 0; _thread_sys_sigreturn(&_thread_run->saved_sigcontext); } else /* --- 661,666 ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 07:32:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16392 for freebsd-current-outgoing; Sun, 16 Aug 1998 07:32:49 -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 HAA16378 for ; Sun, 16 Aug 1998 07:32:44 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id HAA15046; Sun, 16 Aug 1998 07:32:11 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpd014993; Sun Aug 16 07:32:05 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id HAA16709; Sun, 16 Aug 1998 07:31:59 -0700 (MST) From: Terry Lambert Message-Id: <199808161431.HAA16709@usr08.primenet.com> Subject: Re: Better VM patches (was Tentative fix for VM bug) To: dg@root.com Date: Sun, 16 Aug 1998 14:31:59 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG, karl@mcs.net In-Reply-To: <199808161315.GAA00184@implode.root.com> from "David Greenman" at Aug 16, 98 06:15:30 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 > >John also suggested another change for detecting a case where page > >orphans can be created. in vm_page.c, it's possible that an object > >entry in the page insert function will overwrite an existing entry; > >I added a DIAGNOSTIC panic to catch this when it happens. > > You mean that there can be multiple pages at the same offset? It would > be bad if that happend, but I'm skeptical that it actually does. To elaborate: I think that the behaviour I am seeing in the "mmap'ed file contents, on a page boundary, written to another file" case is a result of a single page being in multiple maps. The code that I have provided so far fails to address this bug. I think a rather elaborate diagnostic (which I am constructing on my home machine) is about the only chance of detecting something like this; each page allocation and deallocation must be resource tracked, at great expense. A bug like this is really the only explanation for non-zeroed page contents from one file appearing in another file; there are other symptoms, but the are attributable to other bugs. This is the only bug that satisfies this case and all the others, all at the same time. Left only the improbable, however unlikely... well, Arthur Conan Doyle fans know the rest... Initially, I thought this was 486dx4 specific (per Julian); however, recent information has come to light that indicates that this is a general problem (ie: it is not a noise problem on my hardware); that is, someone has repeated the problem on Cyrix and Pentium hardware. Right now, I am concentrating on the mmap code (the password file is mmap'ed, and that is generally what shows up in the crontab as the corrupt page contents) and the TLB shootdown code (which could also account for the problem, though it would be a really bizare set of circumstances that would be required to lead to this...). Basically, it's code review time... kill the obvious races and see what's left. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 07:55:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18500 for freebsd-current-outgoing; Sun, 16 Aug 1998 07:55:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18495 for ; Sun, 16 Aug 1998 07:55:16 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id HAA02148; Sun, 16 Aug 1998 07:54:32 -0700 (PDT) Message-Id: <199808161454.HAA02148@implode.root.com> To: Terry Lambert cc: current@FreeBSD.ORG, karl@mcs.net Subject: Re: Better VM patches (was Tentative fix for VM bug) In-reply-to: Your message of "Sun, 16 Aug 1998 14:14:05 -0000." <199808161414.HAA16245@usr08.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 16 Aug 1998 07:54:31 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >OK, consider the boundry cases: > >1) The page is less than the boundary, but is extended to less > than the boundary. This is seen as a truncation by setsize. > >2) The page is less than the boundary, but is extended to the > boundary. This is seen as a NOP by the first compare in the > setsize code. I assume you mean "old size" rather than "page" above. I'm probably not correctly parsing what you are trying to communicate. In any case, I just read the vnode_pager_setsize code again (third reading), and don't see any of the bugs you are describing. Are we reading the same source code? >3) The mapped page is written (an implicit extend without a write > fault -- this is, I believe, Karl Denniger's case when the > code provided failed -- between the mapping and the actual size). That will need some further looks. There could be a problem with writing an mmaped file in the last page, beyond the original EOF, without first extending the file to a page boundry. Changes beyond the original EOF might be lost in some cases. I would consider this an application bug, however. >> > object->un_pager.vnp.vnp_size = (vm_ooffset_t) size * PAGE_SIZE; >> >> I think the above change is wrong. > >It's only a comment. The actual change is: No, That was the change to the vnode_pager_setsize function and as I said previously, such a change would break partial page reads. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 08:06:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19848 for freebsd-current-outgoing; Sun, 16 Aug 1998 08:06:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19843 for ; Sun, 16 Aug 1998 08:06:45 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id IAA02398; Sun, 16 Aug 1998 08:06:00 -0700 (PDT) Message-Id: <199808161506.IAA02398@implode.root.com> To: Terry Lambert cc: current@FreeBSD.ORG, karl@mcs.net Subject: Re: Better VM patches (was Tentative fix for VM bug) In-reply-to: Your message of "Sun, 16 Aug 1998 14:31:59 -0000." <199808161431.HAA16709@usr08.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 16 Aug 1998 08:05:59 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >John also suggested another change for detecting a case where page >> >orphans can be created. in vm_page.c, it's possible that an object >> >entry in the page insert function will overwrite an existing entry; >> >I added a DIAGNOSTIC panic to catch this when it happens. >> >> You mean that there can be multiple pages at the same offset? It would >> be bad if that happend, but I'm skeptical that it actually does. > >To elaborate: I think that the behaviour I am seeing in the "mmap'ed >file contents, on a page boundary, written to another file" case is a >result of a single page being in multiple maps. Uh, what does "single page being in multiple maps" mean exactly? What map? Pages belong to objects. A page can belong to only one object (there's only one set of list pointers, so nothing else is possible. :-)). If you see some of one file show up in another, then this suggests to me that a bzero isn't happening when it needs to, resulting in stale cached file data being considered valid. I have a suggestion. Let's not throw out random guesses about what may or may not be a problem. Let's actually understand the issue thoroghly, come up with a fix, and then tell people all about it. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 08:17:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21138 for freebsd-current-outgoing; Sun, 16 Aug 1998 08:17:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.pipeline.ch (intranet.pipeline.ch [195.134.128.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21133 for ; Sun, 16 Aug 1998 08:17:14 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.140.6]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA307; Sun, 16 Aug 1998 17:15:18 +0200 Message-ID: <35D6F7C5.5EF9E07C@pipeline.ch> Date: Sun, 16 Aug 1998 17:16:21 +0200 From: Andre Oppermann Organization: Internet Business Solutions Ltd. X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: John Birrell CC: current@FreeBSD.ORG Subject: Re: ELF problems to occur References: <199808161253.WAA14771@cimlogic.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Birrell wrote: > Andre Oppermann wrote: > > John Birrell wrote: -snip- > > > FreeBSD/Alpha is now using a native kernel. I'm about to remove all the > > > NetBSD kludges from libc that provided the NetBSD syscall interface we've > > > used until now. > > > > Pls. tell me when it's time to buy an Alpha box! > > Would a FreeBSD/Alpha 3.0 release be sufficient for you to do that? Yea. It should be relative easy to install (no NetBSD or tape or whatever kludges, the best would be a floppy like on i386). > It might be called a beta release, or perhaps a snapshot. Snapshot is fine. How far is the port? (I used to follow the cvs-sys mails once a week, but the archiver on ftp.freebsd.org isn't working anymore). Are there any pitfalls on FreeBSD/Alpha or what does not work / or is completely different than on i386? TIA -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 08:43:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23168 for freebsd-current-outgoing; Sun, 16 Aug 1998 08:43:58 -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 IAA23146 for ; Sun, 16 Aug 1998 08:43:40 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id LAA08806; Sun, 16 Aug 1998 11:43:34 -0400 (EDT) Date: Sun, 16 Aug 1998 11:43:34 -0400 (EDT) From: Daniel Eischen Message-Id: <199808161543.LAA08806@pcnet1.pcnet.com> To: eischen@vigrid.com, jb@cimlogic.com.au, lists@tar.com, shmit@kublai.com Subject: Re: Bug in pthread scheduler? (Was pthreads woes revisited) Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Seaman, Jr wrote: > > On Fri, 7 Aug 1998 10:06:43 -0400, Brian Cully wrote: > > >On Thu, Aug 06, 1998 at 05:13:02PM -0400, Daniel Eischen wrote: > >> You're not adding the pthread_yield() call that I added after > >> the pthread_cond_signal(). Your program is bogus because there > >> is no guarantee that the main thread will release the CPU in > >> order for the other task to run. You need to perform some > >> sort of blocking operation after the pthread_cond_signal. I > >> chose to use pthread_yield, although sleep would work just as > >> well. > > > >Do'h! I missed that. That did make the sample program work, so > >it looks like the error was mine all along, sorry for troubling > >everybody. > > Actually, its not at all clear to me that you need the pthread_yield() > call. In looking at the pthread scheduler, it appears that the > scheduler should preempt (with in the context of the process) the > main thread periodically. It also appears that there might be a bug > in the scheduler code. Try the following diff and see what you get. The scheduler should preempt the threads periodically, but the way the sample was coded, the main thread was sleeping while holding the mutex that the other thread needed to run. When the main thread sleeps, its "time running" should get reset. The main thread didn't do much while awake, so there is no guarantee that it will have its time quantum exceeded. Note that the same program *never* allowed the other thread to run under Solaris. I still maintain the program is bogus because you can't guarantee that the other thread will run when you want it to run (every time it is signaled). Perhaps you've found a bug, but you haven't convinced me that the sample program should work as it was intended to ;-) 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 16 10:03:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27738 for freebsd-current-outgoing; Sun, 16 Aug 1998 10:03:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coredump.int.tele.dk (fw1.inet.tele.dk [193.163.158.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27731 for ; Sun, 16 Aug 1998 10:02:59 -0700 (PDT) (envelope-from pivrnec@vszbr.cz) Received: from localhost (pivrnec@localhost) by coredump.int.tele.dk (8.9.1/8.8.8) with SMTP id TAA00260 for ; Sun, 16 Aug 1998 19:02:24 +0200 (CEST) (envelope-from pivrnec@vszbr.cz) X-Authentication-Warning: coredump.int.tele.dk: pivrnec owned process doing -bs Date: Sun, 16 Aug 1998 19:02:22 +0200 (CEST) From: Barry Bierbauch X-Sender: pivrnec@coredump.int.tele.dk Reply-To: Barry Bouwsma To: freebsd-current@FreeBSD.ORG Subject: Re: make installworld failing in share In-Reply-To: <13845.903256856@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 16 Aug 1998, Gary Palmer wrote: > Anyone else having problems in the new locale stuff? Briefly... As a hack, I created the directory, where it was failing, beforehand: ls -la /usr/share/locale/zh_TW.BIG5/ total 211 drwxr-xr-x 2 bin bin 512 Aug 16 18:41 . drwxr-xr-x 38 bin bin 1536 Aug 16 18:36 .. -rw-r--r-- 1 bin bin 202076 Aug 16 18:41 LC_CTYPE That was enough to let make installworld populate this directory and complete, barring a Real solution. On a related note, is anyone interested if I bundle up all the changes I had to make to the CAM diffs of 16.07 with the latest source, and make 'em public? No guarantees I did anything right, but I've been up all of a few minutes (my machine, that is, not me, I've been up far, far longer and should crash real soon now) Barry Bouwsma, Tele Danmark Internet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 11:02:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02591 for freebsd-current-outgoing; Sun, 16 Aug 1998 11:02:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hen.scotland.net (phys-hen.scotland.net [194.247.64.128] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02586 for ; Sun, 16 Aug 1998 11:02:37 -0700 (PDT) (envelope-from freebsd@timog.prestel.co.uk) Received: from e1c2p7.scotland.net ([148.176.232.71] helo=timog.prestel.co.uk) by hen.scotland.net with esmtp (Exim 1.90 #5) for current@FreeBSD.org id 0z8778-00042q-00; Sun, 16 Aug 1998 19:01:10 +0100 Received: (qmail 25980 invoked by uid 1002); 16 Aug 1998 12:19:56 -0000 Message-ID: <19980816131955.A25942@prestel.co.uk> Date: Sun, 16 Aug 1998 13:19:55 +0100 From: Timo Geusch To: current@FreeBSD.ORG Subject: Re: new compiler? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from Kyle Mestery on Fri, Aug 14, 1998 at 09:47:46AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 14, 1998 at 09:47:46AM -0500, Kyle Mestery wrote: > > gcc 2.8.1? (i've heard masses of people complain it's buggy) > > ecgs (not heard much... but i know it has some interesting optimizations > > for i386, and better C++ support) > > anything else? > > > I have heard the opposite. I have heard that egcs is buggy.:) On one of > the NetBSD lists, someone said the latest egcs release only compiles > decent code on ix86 and sparc platforms. And Terry has said before that > the way they handle threads is broken, because you must compile thread > support into the compiler. I haven't heard as many bad things about > gcc-2.8.1. Well, it seems to depend on the architecture that you are running on. I used the gcc28 port to build FreeBSD kernels on my box here and it works fine. At work, however, I'm running several Sparcs with OpenBSD 2.3 (which includes gcc 2.8.1 as default compiler). This compiler is REALLY buggy - there are lots of ways to make it barf with internal compiler errors, even on source code that compiles cleanly on a '386 gcc 2.8.1. So I guess YMMV, but I'd rather stay with 2.7.2.1 as default for the moment and have an additional gcc28 in my local tree just in case want/need it for C++ work. Timo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 12:11:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08448 for freebsd-current-outgoing; Sun, 16 Aug 1998 12:11:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08438 for ; Sun, 16 Aug 1998 12:11:20 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id OAA10231; Sun, 16 Aug 1998 14:10:39 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id OAA29674; Sun, 16 Aug 1998 14:10:39 -0500 (CDT) Message-ID: <19980816141039.48318@mcs.net> Date: Sun, 16 Aug 1998 14:10:39 -0500 From: Karl Denninger To: Terry Lambert Cc: dg@root.com, current@FreeBSD.ORG Subject: Re: Better VM patches (was Tentative fix for VM bug) References: <199808161315.GAA00184@implode.root.com> <199808161414.HAA16245@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199808161414.HAA16245@usr08.primenet.com>; from Terry Lambert on Sun, Aug 16, 1998 at 02:14:05PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 16, 1998 at 02:14:05PM +0000, Terry Lambert wrote: > > This is, in fact, the most interesting change, as far as Karl Denniger is > concerned. I would like to close the race window here (by adding an > "actual_length" parameter to the various "allocate" routines) to see > if this resolves Karl's remaining bugs (per the SPLVM bug noted in the > comment here)... I suspect that Karl has two bugs; the one I hit, and > a sepoerate one, and the remaining window accounts for a tiny fraction > of the misbehaviour that he is still experiencing. > > The real way out of this mes is to reference cont everything and to note > 1->2 transitions for page references. This takes a significant amount of > code and structure changes to accomplish; it would be nice if the problem > were a bit easier to duplicate, but it's not. I have to make changes > that narrow down the problem instead of resolve it; A/B tests. 8-(. The changes you posted do in fact decrease the number of these errors. They DO NOT eliminate them, but decrease them measurably. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 12:48:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13180 for freebsd-current-outgoing; Sun, 16 Aug 1998 12:48:45 -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 MAA13161 for ; Sun, 16 Aug 1998 12:48:36 -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 PAA07089; Sun, 16 Aug 1998 15:48:57 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sun, 16 Aug 1998 15:48:57 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: William Woods cc: current@FreeBSD.ORG Subject: Re: x11amp port on current.... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG yes, use the pcm audio from luigi and get the linux statically linked version. -Alfred -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- http://www.freebsd.org/ On Sat, 15 Aug 1998, William Woods wrote: > I just noticed, x11amp port doesnt work on current......I am useiong kernel > sound...is there a fix for this? > > --------------------- > William Woods > Date: 15-Aug-98 / Time: 13:57:18 > --> FreeBSD 3.0 CURRENT <-- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 13:01:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15550 for freebsd-current-outgoing; Sun, 16 Aug 1998 13:01:48 -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 NAA15544 for ; Sun, 16 Aug 1998 13:01:47 -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 QAA07115; Sun, 16 Aug 1998 16:02:03 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sun, 16 Aug 1998 16:02:03 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Karl Pielorz cc: current@FreeBSD.ORG Subject: Re: Can't build kernel with 15/08/98 @ 23:17 source In-Reply-To: <35D61631.47D5DACA@tdx.co.uk> 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 urm controller scbus0 ??? -Alfred -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- http://www.freebsd.org/ On Sun, 16 Aug 1998, Karl Pielorz wrote: > Hi All, > > I can't seem to build a kernel with the latest sources... It falls over with: > > " > caladan# make > loading kernel > cd.o: Undefined symbol `_scsi_device_register' referenced from text segment > cd.o: Undefined symbol `_scsi_open' referenced from text segment > cd.o: Undefined symbol `_scsi_ioctl' referenced from text segment > cd.o: Undefined symbol `_scsi_close' referenced from text segment > cd.o: Undefined symbol `_scsi_minphys' referenced from text segment > cd.o: Undefined symbol `_scsi_strategy' referenced from text segment > cd.o: Undefined symbol `_extend_get' referenced from text segment > cd.o: Undefined symbol `_extend_get' referenced from text segment > cd.o: Undefined symbol `_extend_get' referenced from text segment > cd.o: Undefined symbol `_extend_get' referenced from text segment > (heaps of more like the above) > " > > Can anybody suggest anything? - I have the following lines in the kernel config: > > " > controller ahc0 > controller ahc1 > controller ahc2 > options AHC_TAGENABLE > options AHC_SCBPAGING_ENABLE > options AHC_ALLOW_MEMIO > > device sd0 > device st0 > device cd0 #Only need one of these, the code dynamically grows > " > > I've made sure to do a 'make clean; make depend; make'... > > I have a horrible feeling that this is pilot error, but I'm stumped... ;-( > > Regards, > > Karl Pielorz > > > ---------------------------------------------------------------------------- > Karl Pielorz 'mailto:kpielorz@tdx.co.uk' This system runs http://freebsd.org > ~ - Any opinions in this posting are my own and not those of my employer - ~ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 13:05:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16102 for freebsd-current-outgoing; Sun, 16 Aug 1998 13:05:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16097 for ; Sun, 16 Aug 1998 13:05:44 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id GAA15685; Mon, 17 Aug 1998 06:13:09 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808162013.GAA15685@cimlogic.com.au> Subject: Re: ELF problems to occur In-Reply-To: <35D6F7C5.5EF9E07C@pipeline.ch> from Andre Oppermann at "Aug 16, 98 05:16:21 pm" To: oppermann@pipeline.ch (Andre Oppermann) Date: Mon, 17 Aug 1998 06:13:09 +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 Andre Oppermann wrote: > Yea. It should be relative easy to install (no NetBSD or tape or > whatever kludges, the best would be a floppy like on i386). bootp, CD or perhaps a floppy. > Snapshot is fine. How far is the port? (I used to follow the cvs-sys > mails once a week, but the archiver on ftp.freebsd.org isn't working > anymore). > > Are there any pitfalls on FreeBSD/Alpha or what does not work / or is > completely different than on i386? FreeBSD/Alpha is built from the same sources as i386 and it uses the same build tools (elf). Device support needs testing on a variety of hardware. Ditto for all sorts of applications in the tree that build but nobody has tested thoroughly. People should _not_ expect a production class release since this is the first one. -- 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 Sun Aug 16 13:08:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16736 for freebsd-current-outgoing; Sun, 16 Aug 1998 13:08:43 -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 NAA16726 for ; Sun, 16 Aug 1998 13:08:40 -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 QAA07130; Sun, 16 Aug 1998 16:08:54 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sun, 16 Aug 1998 16:08:54 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Bruce Evans cc: dag-erli@ifi.uio.no, current@FreeBSD.ORG, jdp@polstra.com, julian@whistle.com Subject: Re: Funky DEVFS stuff. In-Reply-To: <199808161056.UAA04271@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 > >By the way, how much work would it be to make using more than 8 > >partitions per slice possible? > > None. Everything is possible in software :-), and in theory the > MAXPARTITIONS parameter can simply be increased up to about 22 as in > NetBSD. You also have to change at least the size of openmask bitmap > variables in FreeBSD. Our default of setting the number of partitions to > the max isn't so good if the max is large. Sysinstall would probably > have problems displaying 22 partitions on a 25-line screen. It would > be more work to support a flexibly sized array of partitions - several > places want `struct disklabel' to actually be a struct. urm, sysinstall can't deal with SLICE/DEVFS, it says it can't find the devices, someone has to mess with libdisk. -Alfred -- Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] |-- There are operating systems, and then there's BSD. \-- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 13:13:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17692 for freebsd-current-outgoing; Sun, 16 Aug 1998 13:13: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 NAA17686 for ; Sun, 16 Aug 1998 13:13:57 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA12895; Sun, 16 Aug 1998 13:09:45 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdQ12893; Sun Aug 16 20:09:42 1998 Date: Sun, 16 Aug 1998 13:09:39 -0700 (PDT) From: Julian Elischer To: Kris Kennaway cc: current@FreeBSD.ORG Subject: Re: Softupdates patches In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG thanks for the feedback! julian On Sat, 15 Aug 1998, Kris Kennaway wrote: > The recent softupdates patches committed by Julian solve the problem case > I pointed out, and things have been running smoothly in the softupdates > department. > > Thanks, > > Kris > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 13:22:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18610 for freebsd-current-outgoing; Sun, 16 Aug 1998 13:22:08 -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 NAA18598 for ; Sun, 16 Aug 1998 13:22:02 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id QAA09561 for ; Sun, 16 Aug 1998 16:21:30 -0400 (EDT) Date: Sun, 16 Aug 1998 16:21:29 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: current@FreeBSD.ORG Subject: more installworld breakage 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 /usr/share/man/man4/i386/../xl.4 -> /usr/share/man/man4/i386/xl.4 ln: /usr/share/man/man4/i386/xl.4: No such file or directory *** Error code 1 This hasn't been a good couple of days -- what's that, three world breakages? 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 16 13:34:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20069 for freebsd-current-outgoing; Sun, 16 Aug 1998 13:34:11 -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 NAA20059 for ; Sun, 16 Aug 1998 13:34:09 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA13280; Sun, 16 Aug 1998 13:31:04 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdu13276; Sun Aug 16 20:30:56 1998 Date: Sun, 16 Aug 1998 13:30:52 -0700 (PDT) From: Julian Elischer To: Alfred Perlstein cc: Bruce Evans , dag-erli@ifi.uio.no, current@FreeBSD.ORG, jdp@polstra.com Subject: Re: Funky DEVFS stuff. 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 yep we know (but that doesn't mean we shouldn't be reminded) :-) julian On Sun, 16 Aug 1998, Alfred Perlstein wrote: > > >By the way, how much work would it be to make using more than 8 > > >partitions per slice possible? > > > > None. Everything is possible in software :-), and in theory the > > MAXPARTITIONS parameter can simply be increased up to about 22 as in > > NetBSD. You also have to change at least the size of openmask bitmap > > variables in FreeBSD. Our default of setting the number of partitions to > > the max isn't so good if the max is large. Sysinstall would probably > > have problems displaying 22 partitions on a 25-line screen. It would > > be more work to support a flexibly sized array of partitions - several > > places want `struct disklabel' to actually be a struct. > > urm, sysinstall can't deal with SLICE/DEVFS, it says it can't find the > devices, someone has to mess with libdisk. > > -Alfred > -- > > Programmer @ HotJobs Inc. [- http://www.hotjobs.com/ -] > |-- There are operating systems, and then there's BSD. > \-- http://www.freebsd.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 13:42:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21101 for freebsd-current-outgoing; Sun, 16 Aug 1998 13:42:21 -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 NAA21096 for ; Sun, 16 Aug 1998 13:42:14 -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 QAA05509; Sun, 16 Aug 1998 16:44:46 -0400 From: Bill Paul Message-Id: <199808162044.QAA05509@skynet.ctr.columbia.edu> Subject: Re: more installworld breakage To: ben@rosengart.com Date: Sun, 16 Aug 1998 16:44:44 -0400 (EDT) Cc: current@FreeBSD.ORG In-Reply-To: from "Snob Art Genre" at Aug 16, 98 04:21:29 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, Snob Art Genre had to walk into mine and say: > /usr/share/man/man4/i386/../xl.4 -> /usr/share/man/man4/i386/xl.4 > ln: /usr/share/man/man4/i386/xl.4: No such file or directory > *** Error code 1 > > This hasn't been a good couple of days -- what's that, three world > breakages? Okay okay, it's my fault. I fixed this already, not very long after I screwed it up. I added an MLINKS entry to this Makefile but forgot to add the xl.4 entry to the MAN4 line that goes with it. Grab a fresh copy of /usr/src/share/man/man4/man4.i386/Makefile and try again; it should work now. I knew that Murphy's Law would see to it that somebody would try to do a build during the just the right couple of minutes to run into this, but I thought I could get away with it. *sigh* -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 16 13:59:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23253 for freebsd-current-outgoing; Sun, 16 Aug 1998 13:59:58 -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 NAA23248 for ; Sun, 16 Aug 1998 13:59:56 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-45.camalott.com [208.229.74.45]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id QAA08499; Sun, 16 Aug 1998 16:00:43 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id PAA07268; Sun, 16 Aug 1998 15:56:19 -0500 (CDT) (envelope-from joelh) Date: Sun, 16 Aug 1998 15:56:19 -0500 (CDT) Message-Id: <199808162056.PAA07268@detlev.UUCP> To: freebsd-current@FreeBSD.ORG Subject: mbuf leaks? From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anybody noticed mbuf leaks in either the ed or tun drivers in the last week or so? Thanks, 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 Sun Aug 16 16:08:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04642 for freebsd-current-outgoing; Sun, 16 Aug 1998 16:08:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04637 for ; Sun, 16 Aug 1998 16:08:23 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.2232.9) id ; Sun, 16 Aug 1998 19:05:31 -0400 Message-ID: From: tcobb To: "'freebsd-current@freebsd.org'" Subject: PANIC: NULLFS not synced with rest of vm? Date: Sun, 16 Aug 1998 19:05:30 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NULLFS panics when used much on the 19980804 SNAP. It appears that isn't caught up with other changes that have happened in the VM. Is there anyone working on this yet? Is there anyone willing to take an hour or two to fix it (we ARE willing to pay for this time if it results in a stable implementation of NULLFS). The problem seems to be that in the NULLFS code, there is no v_object (0x0) in any of the vnodes, but a valid v_object is expected by most everything else. Not knowing the FS/VM code, that's as far as I got with a debug :) Here's the panic and bt when I do this: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x40 fault code = supervisor read, page not present instruction pointer = 0x8:0xf0197254 stack pointer = 0x10:0xf66a7bd4 frame pointer = 0x10:0xf66a7cb0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 220 (chroot) interrupt mask = net bio cam trap number = 12 panic: page fault #0 boot (howto=256) at ../../kern/kern_shutdown.c:286 #1 0xf01112f6 in panic (fmt=0xf01b9121 "page fault") at ../../kern/kern_shutdown.c:427 #2 0xf01b9d71 in trap_fatal (frame=0xf66a7b98) at ../../i386/i386/trap.c:879 #3 0xf01b9804 in trap_pfault (frame=0xf66a7b98, usermode=0) at ../../i386/i386/trap.c:772 #4 0xf01b9463 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = -160793236, tf_ebp = -160793424, tf_isp = -160793664, tf_ebx = 1, tf_edx = 0, tf_ecx = 0, tf_eax = -160733536, tf_trapno = 12, tf_err = 0, tf_eip = -266767788, tf_cs = 8, tf_eflags = 66118, tf_esp = 1, tf_ss = -160793236}) at ../../i386/i386/trap.c:396 #5 0xf0197254 in ffs_getpages (ap=0xf66a7d68) at ../../ufs/ufs/ufs_readwrite.c:466 #6 0xf013dff0 in null_bypass (ap=0xf66a7d68) at ../../miscfs/nullfs/null_vnops.c:295 #7 0xf01ad302 in vnode_pager_getpages (object=0xf66ab880, m=0xf66a7dc4, count=16, reqpage=0) at vnode_if.h:1067 #8 0xf01abfd7 in vm_pager_get_pages (object=0xf66ab880, m=0xf66a7dc4, count=16, reqpage=0) at ../../vm/vm_pager.c:256 #9 0xf0109e46 in exec_map_first_page (imgp=0xf66a7ea0) at ../../kern/kern_exec.c:387 #10 0xf0109912 in execve (p=0xf6658ac0, uap=0xf66a7f94) at ../../kern/kern_exec.c:166 #11 0xf01b9fbf in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 0, tf_esi = 2, tf_ebp = -272638852, tf_isp = -160792604, tf_ebx = 537411680, tf_edx = -272638666, tf_ecx = -272638666, tf_eax = 59, tf_trapno = 12, tf_err = 7, tf_eip = 537114897, tf_cs = 31, tf_eflags = 642, tf_esp = -272640028, tf_ss = 39}) at ../../i386/i386/trap.c:1031 #12 0x2003b911 in ?? () #13 0x1661 in ?? () #14 0x1099 in ?? () Once again, we are willing to pay some reasonable fee to fix it, especially if they will do so TODAY. -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 17:34:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14369 for freebsd-current-outgoing; Sun, 16 Aug 1998 17:34:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from att.com (kcgw2.att.com [192.128.133.152]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA14362 for ; Sun, 16 Aug 1998 17:34:07 -0700 (PDT) (envelope-from jwb@homer.att.com) Received: from kcig2.att.att.com by kcgw2.att.com (AT&T/UPAS) for freebsd.org!freebsd-current sender homer.att.com!jwb (homer.att.com!jwb); Thu Aug 13 14:04 CDT 1998 Received: from ulysses.homer.att.com (ulysses.homer.att.com [135.205.212.4]) by kcig2.att.att.com (AT&T/GW-1.0) with ESMTP id OAA25625 for ; Thu, 13 Aug 1998 14:24:31 -0500 (CDT) Received: from akiva.homer.att.com (akiva.homer.att.com [135.205.213.77]) by ulysses.homer.att.com (8.8.8/8.8.8) with SMTP id PAA29037 for ; Thu, 13 Aug 1998 15:24:25 -0400 (EDT) Received: by akiva.homer.att.com (4.1) id AA19126; Thu, 13 Aug 98 15:24:26 EDT Message-Id: <9808131924.AA19126@akiva.homer.att.com> Received: from localhost.homer.att.com [127.0.0.1] by akiva; Thu Aug 13 15:24:25 EDT 1998 X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: signal 11 on bootup Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 15:24:24 -0400 From: "J. W. Ballantine" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running 3.0-980804-SNAP with an AHA-2490 scsi controller board, and I just replaced the memory with new memory. Today when I rebooted the system I received: pid 10 (fsck), uid 0: Exited on signal 11. Now I've been having problems with scsi 0 going into hard lock when I tried to access the disk during install (either during the prob prior to the the menu appearing or during the partitioning update write). Is this a hardware or software error?? Jim Ballantine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 19:08:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24178 for freebsd-current-outgoing; Sun, 16 Aug 1998 19:08:26 -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 TAA24170 for ; Sun, 16 Aug 1998 19:08:24 -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 WAA10312; Sun, 16 Aug 1998 22:08:48 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sun, 16 Aug 1998 22:08:48 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "J. W. Ballantine" cc: freebsd-current@FreeBSD.ORG Subject: Re: signal 11 on bootup In-Reply-To: <9808131924.AA19126@akiva.homer.att.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG if all you've done is change the memory, looks like hardware no? Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's BSD. -- http://www.freebsd.org/ On Thu, 13 Aug 1998, J. W. Ballantine wrote: > > I'm running 3.0-980804-SNAP with an AHA-2490 scsi controller board, and I > just replaced the memory with new memory. Today when I rebooted the > system I received: > > pid 10 (fsck), uid 0: Exited on signal 11. > > Now I've been having problems with scsi 0 going into hard lock when I tried > to access the disk during install (either during the prob prior to the > the menu appearing or during the partitioning update write). > > Is this a hardware or software error?? > > Jim Ballantine > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 19:18:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25237 for freebsd-current-outgoing; Sun, 16 Aug 1998 19:18:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25230 for ; Sun, 16 Aug 1998 19:18:16 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id UAA20697; Sun, 16 Aug 1998 20:17:32 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id UAA04040; Sun, 16 Aug 1998 20:17:30 -0600 Date: Sun, 16 Aug 1998 20:17:30 -0600 Message-Id: <199808170217.UAA04040@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: dg@root.com Cc: Terry Lambert , current@FreeBSD.ORG, karl@mcs.net Subject: Re: Better VM patches (was Tentative fix for VM bug) In-Reply-To: <199808161506.IAA02398@implode.root.com> References: <199808161431.HAA16709@usr08.primenet.com> <199808161506.IAA02398@implode.root.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman writes: > I have a suggestion. Let's not throw out random guesses about what may or > may not be a problem. Let's actually understand the issue thoroghly, come up > with a fix, and then tell people all about it. Actually, I'm with Terry here. I think throwing out random guesses is a *much* better solution than what's occurred so far. At least this way folks have a clue about what *might* be going on, and some of the 'random guesses' may trigger someone's mind. This is how *real* companies work on complex problems, and how the state of the art progresses. (Though I'd replace the term 'random' with 'educated', but still leave the term 'guess' in the mix.) The lack of progress on these bugs from the kernel hackers until Terry makes up an 'educated guess' seems to be a good motivator. :) ;) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 19:34:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27499 for freebsd-current-outgoing; Sun, 16 Aug 1998 19:34:35 -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 TAA27492 for ; Sun, 16 Aug 1998 19:34:31 -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 MAA06776; Mon, 17 Aug 1998 12:04:00 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA05802; Mon, 17 Aug 1998 12:04:00 +0930 (CST) Message-ID: <19980817120400.R24176@freebie.lemis.com> Date: Mon, 17 Aug 1998 12:04:00 +0930 From: Greg Lehey To: Mike Smith , John Polstra Cc: current@FreeBSD.ORG Subject: Re: ELF problems to occur References: <199808151705.KAA17832@austin.polstra.com> <199808151043.KAA00827@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199808151043.KAA00827@word.smith.net.au>; from Mike Smith on Sat, Aug 15, 1998 at 10:43:31AM +0000 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 Saturday, 15 August 1998 at 10:43:31 +0000, Mike Smith wrote: >>> And supposedly the ELF kernel is bootable nowadays with a few >>> patches; do lkm's work? >> >> I doubt we'll have time to switch the kernel to ELF before 3.0 >> release. > > The lkm system will not be ported for ELF, we will be using kld > instead. Where do I find information about kld? 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 Sun Aug 16 20:05:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01001 for freebsd-current-outgoing; Sun, 16 Aug 1998 20:05:37 -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 UAA00996 for ; Sun, 16 Aug 1998 20:05:35 -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 UAA27879; Sun, 16 Aug 1998 20:04:17 -0700 (PDT) (envelope-from jdp) Message-Id: <199808170304.UAA27879@austin.polstra.com> To: Greg Lehey cc: Mike Smith , current@FreeBSD.ORG Subject: Re: ELF problems to occur In-reply-to: Your message of "Mon, 17 Aug 1998 12:04:00 +0930." <19980817120400.R24176@freebie.lemis.com> Date: Sun, 16 Aug 1998 20:04:17 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Where do I find information about kld? In kldload(8) and related man pages, and in the sources for those programs. And in the kernel, in kern/kern_linker.c and kern/link_aout.c. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 20:50:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06550 for freebsd-current-outgoing; Sun, 16 Aug 1998 20:50:55 -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 UAA06542 for ; Sun, 16 Aug 1998 20:50:52 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id NAA20210; Mon, 17 Aug 1998 13:57:11 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808170357.NAA20210@cimlogic.com.au> Subject: Re: ELF problems to occur In-Reply-To: <199808170304.UAA27879@austin.polstra.com> from John Polstra at "Aug 16, 98 08:04:17 pm" To: jdp@polstra.com (John Polstra) Date: Mon, 17 Aug 1998 13:57:09 +1000 (EST) Cc: grog@lemis.com, mike@smith.net.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 John Polstra wrote: > > Where do I find information about kld? > > In kldload(8) and related man pages, and in the sources for > those programs. And in the kernel, in kern/kern_linker.c and > kern/link_aout.c. ... and Doug has kern/link_elf.c that he hasn't committed yet. -- 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 Sun Aug 16 22:02:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15203 for freebsd-current-outgoing; Sun, 16 Aug 1998 22:02:06 -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 WAA15172 for ; Sun, 16 Aug 1998 22:02:02 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id WAA17008; Sun, 16 Aug 1998 22:01:28 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd016966; Sun Aug 16 22:01:25 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id WAA18680; Sun, 16 Aug 1998 22:01:20 -0700 (MST) From: Terry Lambert Message-Id: <199808170501.WAA18680@usr09.primenet.com> Subject: Re: Better VM patches (was Tentative fix for VM bug) To: dg@root.com Date: Mon, 17 Aug 1998 05:01:20 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG, karl@mcs.net In-Reply-To: <199808161506.IAA02398@implode.root.com> from "David Greenman" at Aug 16, 98 08:05:59 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >To elaborate: I think that the behaviour I am seeing in the "mmap'ed > >file contents, on a page boundary, written to another file" case is a > >result of a single page being in multiple maps. > > Uh, what does "single page being in multiple maps" mean exactly? What map? > Pages belong to objects. A page can belong to only one object (there's only > one set of list pointers, so nothing else is possible. :-)). This precisely what is happening in the cases I have observed in deployed machines: The contents of the cron tab are being overwritten with the contents of a dbm file which the dbm routines mmap'ed. The new content of the file begins on a page boundary beginning. > If you see some > of one file show up in another, then this suggests to me that a bzero isn't > happening when it needs to, resulting in stale cached file data being > considered valid. This would be true if the file data was intact up to the EOF, then contained the cached data. This is not what is happening. What is happening suggests that when mmap'ed backing store is discarded, an object alias remains after the discard, and the physical page is reused while it is still referenced. > I have a suggestion. Let's not throw out random guesses about what may or > may not be a problem. Let's actually understand the issue thoroghly, come up > with a fix, and then tell people all about it. The case I am worried about with the setsize fix is the case where the file was mmap'ed. The file did not end on an even page boundary. The file is extended, either below or exactly on a page boundary. The first "if" in "setsize" is true because the file length was erroneously saved in the object. A subsequent read reference on the mmap'ed section, which is believed to be swapped out, results in a page reactivation. The perfectly valid data (written via normal file I/O) in the extended area is lost. So the setsize code fixes a real bug, even if it breaks an abstraction. The race window from my comment refers to a read completion interrupt from a disk controller being processed in the time between the bogus value being set in the alloc, and the value being corrected. The XXX comment I pointed to is an indication that orphaned objects can and do exist. This is a seperate problem, and can't result in the "mmap'ed file contents overwrite valid file contents" corruption that got me interested in this in the first place. Neither could John's orphaned object fix for invalidation of good pages, and my order fix on the protection before the invalidation. All that said, I think that my fix does not resolve all of the problems, only some of them. The "backup one if you can" kludge I originally posted was more diagnostic than anything else; it was very informative to me that (1) it didn't result in more "freeing free page" panics, and (2) it didn't help the mmap bug in the news server, which I think is a more repeatable version of the crontab corruption bug I am suffering. So anyway, I hope I've convinced you that there is actually an error in the allocate code setting the size to a page boundary; the valid = 0 bug is so obvious (once John Dyson pointed it out after looking at my "backup one" patch 8-)) that it doesn't need more justification. Anyway, I'm currently looking for similar order of operation things; if I can come up with patches that fix Karl Denniger's news server, I'm pretty convinced my problem will go away as well. If you would prefer I target my patches instead of posting to the list, I'll post asking for people who have problems and restrict the distribution. Should I do this? I'd really prefer that diagnostic patches get the widest possible audience, especially if they make things worse. Getting a limited set of positive responses is the worst thing that could happen if there is a negative effect that goes undiscovered. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 16 22:11:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16252 for freebsd-current-outgoing; Sun, 16 Aug 1998 22:11: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 WAA16243 for ; Sun, 16 Aug 1998 22:11:24 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id BAA25184 for ; Mon, 17 Aug 1998 01:10:50 -0400 (EDT) Date: Mon, 17 Aug 1998 01:10:50 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: current@FreeBSD.ORG Subject: allscreens_flags 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 me, or has the allscreens_flags variable in rc.conf ceased to work? I have mine set thusly: allscreens_flags="-m on"# Set this vidcontrol mode for all virtual screens But my mouse only works on ttyv0 unless I enable it by hand. I have X, and I do most everything remotely anyway, so this isn't a big deal, but I'm curious as to whether this is broken or merely misconfigured locally. I'm also curious about the newish /etc/etc.i386 directory; are the files in here used in preference to the files of the same name in /etc? Should I delete /etc/disktab, rc.i386 and ttys? 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 16 22:38:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20088 for freebsd-current-outgoing; Sun, 16 Aug 1998 22:38:31 -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 WAA20081 for ; Sun, 16 Aug 1998 22:38:29 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id WAA01440; Sun, 16 Aug 1998 22:37:55 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpd001399; Sun Aug 16 22:37:46 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id WAA19870; Sun, 16 Aug 1998 22:37:37 -0700 (MST) From: Terry Lambert Message-Id: <199808170537.WAA19870@usr09.primenet.com> Subject: Re: Better VM patches (was Tentative fix for VM bug) To: nate@mt.sri.com (Nate Williams) Date: Mon, 17 Aug 1998 05:37:37 +0000 (GMT) Cc: dg@root.com, tlambert@primenet.com, current@FreeBSD.ORG, karl@mcs.net In-Reply-To: <199808170217.UAA04040@mt.sri.com> from "Nate Williams" at Aug 16, 98 08:17:30 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 have a suggestion. Let's not throw out random guesses about what may or > > may not be a problem. Let's actually understand the issue thoroghly, come up > > with a fix, and then tell people all about it. > > Actually, I'm with Terry here. I think throwing out random guesses is a > *much* better solution than what's occurred so far. At least this way > folks have a clue about what *might* be going on, and some of the > 'random guesses' may trigger someone's mind. Actually this is too adversarial. There is a real problem with the vnode_pager_alloc; it should *NOT* set the actual size of the backing file to something other than the actual size of the backing file. I think I cleared up the misunderstanding caused by my inability to communicate *why* this was a problem in my initial post. My "wild guess" that fits the most problems is that there is a page that is multiply referenced (or an object; a page makes more sense to me becuase of the symptoms I've seen). This is a read-cache bug (which is why I initially asked that someone with the SIG-11 or the zeroed-page bugs compile their kernel NO_SWAPPING). > The lack of progress on these bugs from the kernel hackers until Terry > makes up an 'educated guess' seems to be a good motivator. :) ;) I think the problems are more severe than are generally thought, but are very infrequent. I'm pretty sure that, until my last post, that I had given David the impression that the file corruption I was seeing was partial page corruption of a file that ended before a page boundary. In fact, I was seeing corruption beginning on a page boundary, and extending for 4k (or the end of the file, whichever came first). I don't think anyone has been very good at communicating these bugs, or their severity ("What idiot would extend a file that has been mmap'ed without redoing the mapping?", etc.). David's patches for the NFS problem were well thought out. I don't think he needed me poking him to find them. 8-). The reason I did the backup-one patch at all was that I was looking for a panacea; a multiply referenced page, however it has occurred, is about the only thing that can explain my problem, other than bad hardware (which I refuse to believe, since "it worked before"). While trodding down the mmap path after the backup-one failed to preterb Karl's bug or result in a "freeing free page" panic, I found the mmap backing object end-of-file problem. This actually doesn't help me; I am still hunting my normally-accessed-file corrupted by contents of mmaped-file-from-different-process bug, and I may still be looking for the "pages zeroed at random" problem. No one who has this problem has enabled DIAGNOSTIC with the new patch to see if the insert is stomping things, so I can't tell if John fixing the bogus-invalid-during-cleanup bug was all that was necessary for that. 8-(. Anyway, after all that, I am actually very happy to be using the -current list as something other than an overflow from -ports or -questions or -I-didn't-read-the-FAQ. So shoot me. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 17 04:14:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23592 for freebsd-current-outgoing; Mon, 17 Aug 1998 04:14:05 -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 EAA23587 for ; Mon, 17 Aug 1998 04:14:02 -0700 (PDT) (envelope-from paulz@trantor.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <4329-4659>; Mon, 17 Aug 1998 13:13:09 +0200 Received: from trantor.stuyts.nl (uucp@localhost) by terminus.stuyts.nl (8.9.1/8.8.8) with UUCP id NAA17846 for current@FreeBSD.ORG; Mon, 17 Aug 1998 13:10:31 +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 NAA23662 for ; Mon, 17 Aug 1998 13:04:54 +0200 (MET DST) Message-Id: <199808171104.NAA23662@trantor.stuyts.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Cards sharing irq's on PCI bus Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Aug 1998 13:04:53 +0200 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running very low on available irq's and I noticed that the bios put both my SMC 8432BT and my Adaptec 2740 on irq 9. Network performance was terrible, iozone on NFS only 300kB/s. After disabling my IDE controller (only need that when running Solaris) the Adaptrec was put on irq 14 (where the IDE used to be) and my network performance was back ( more than 900kB/s). Is it allowed to put have more than one PCI card use the same irq ??? It sort of worked. No errors or so, just lousy performance ?? Maybe someone can shed some light on this ?? 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 17 04:52:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26924 for freebsd-current-outgoing; Mon, 17 Aug 1998 04:52:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ha1.rdc1.nj.home.com (ha1.rdc1.nj.home.com [24.3.128.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA26919 for ; Mon, 17 Aug 1998 04:52:06 -0700 (PDT) (envelope-from damascus@eden.rutgers.edu) Message-Id: <199808171152.EAA26919@hub.freebsd.org> Received: from athena ([24.3.219.36]) by ha1.rdc1.nj.home.com (Netscape Mail Server v2.02) with SMTP id AAA7030; Mon, 17 Aug 1998 04:51:32 -0700 X-Sender: damascus@eden-backend.rutgers.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 Date: Mon, 17 Aug 1998 07:55:38 -0500 To: Paul van der Zwan , current@FreeBSD.ORG From: Carroll Kong Subject: Re: Cards sharing irq's on PCI bus In-Reply-To: <199808171104.NAA23662@trantor.stuyts.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:04 PM 8/17/98 +0200, Paul van der Zwan wrote: >I am running very low on available irq's and I noticed that the bios put both >my SMC 8432BT and my Adaptec 2740 on irq 9. Network performance was terrible, >iozone on NFS only 300kB/s. After disabling my IDE controller (only need that >when running Solaris) the Adaptrec was put on irq 14 (where the IDE used to be) >and my network performance was back ( more than 900kB/s). > >Is it allowed to put have more than one PCI card use the same irq ??? >It sort of worked. No errors or so, just lousy performance ?? >Maybe someone can shed some light on this ?? > > > Paul For MS Oses, PCI Irq sharing is pretty "safe"... at least in the foreground... who knows if it really works 100%. But.. I quad boot... so when I go to a Unix OS.. I want 100% workability.. or at least 99.9%... :) I tried pci irq sharing and found problems immediately when sharing a NIC with a SCSI card. (3Com would not work.. kernel had problems with linux... I didn't even bother with booting into FreeBSD to see what kind of errors I would get there.. hehe all for one... one for all) Usually, the safest one to irq share is your video card. Technically it doesn't need an irq... (I would do it though), share the video irq with another device like the NIC. Check performance again. Should be similar... if not the same. (I am going to test my NIC performance now that it is shared.... Hm... need large contiguous file.... I should use dd if=/dev/zero of=contig.file bs=1024000 count=5? Wil that make a 5 meg file named contig.file?) -Carroll Kong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 17 08:41:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16871 for freebsd-current-outgoing; Mon, 17 Aug 1998 08:41:26 -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 IAA16864 for ; Mon, 17 Aug 1998 08:41:23 -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 KAA06328; Mon, 17 Aug 1998 10:11:10 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Mon, 17 Aug 1998 10:11:10 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Paul van der Zwan cc: current@FreeBSD.ORG Subject: Re: Cards sharing irq's on PCI bus In-Reply-To: <199808171104.NAA23662@trantor.stuyts.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG well, that's unclear, last i heard linux was the only OS to support shared IRQs and i don't even know how well it handled it. (i think it was more of a "don't use them at the same time" deal) but, you can twiddle your bios to give more IRQs to PCI/pnp devices, look around in it, you should be able to switch IRQ reservations from something like "LEGACY ISA" to "PCI/pnp" (perhaps you used all of your IRQs, but i did this to give my PCI system more IRQs because too many were reserved for ISA) Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's BSD. -- http://www.freebsd.org/ On Mon, 17 Aug 1998, Paul van der Zwan wrote: > I am running very low on available irq's and I noticed that the bios put both > my SMC 8432BT and my Adaptec 2740 on irq 9. Network performance was terrible, > iozone on NFS only 300kB/s. After disabling my IDE controller (only need that > when running Solaris) the Adaptrec was put on irq 14 (where the IDE used to be) > and my network performance was back ( more than 900kB/s). > > Is it allowed to put have more than one PCI card use the same irq ??? > It sort of worked. No errors or so, just lousy performance ?? > Maybe someone can shed some light on this ?? > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 17 09:51:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28404 for freebsd-current-outgoing; Mon, 17 Aug 1998 09:51:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA28372 for ; Mon, 17 Aug 1998 09:51:16 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 4024 invoked by uid 1001); 17 Aug 1998 16:50:32 +0000 (GMT) To: bright@www.hotjobs.com Cc: current@FreeBSD.ORG Subject: Re: Cards sharing irq's on PCI bus In-Reply-To: Your message of "Mon, 17 Aug 1998 10:11:10 -0500 (EST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 17 Aug 1998 18:50:32 +0200 Message-ID: <4022.903372632@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > well, that's unclear, last i heard linux was the only OS to support shared > IRQs and i don't even know how well it handled it. (i think it was more of > a "don't use them at the same time" deal) FreeBSD supports shared IRQs for PCI just fine. I have a host here with an Adaptec 2940UW and a ZNYX 4-port Ethernet card on IRQ 10, and two SMC 2-port Ethernet cards sharing IRQ 11. No problem. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 17 10:05:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01593 for freebsd-current-outgoing; Mon, 17 Aug 1998 10:05:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coredump.int.tele.dk (fw1.inet.tele.dk [193.163.158.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01584 for ; Mon, 17 Aug 1998 10:05:53 -0700 (PDT) (envelope-from pivrnec@vszbr.cz) Received: from localhost (pivrnec@localhost) by coredump.int.tele.dk (8.9.1/8.8.8) with SMTP id TAA01363 for ; Mon, 17 Aug 1998 19:05:04 +0200 (CEST) (envelope-from pivrnec@vszbr.cz) X-Authentication-Warning: coredump.int.tele.dk: pivrnec owned process doing -bs Date: Mon, 17 Aug 1998 19:05:03 +0200 (CEST) From: Barry Bierbauch X-Sender: pivrnec@coredump.int.tele.dk Reply-To: Barry Bouwsma To: freebsd-current@FreeBSD.ORG Subject: /kernel: arpresolve: can't allocate llinfo 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 Howdy... I had been running a -current snap from last November, which usually worked well, but sometimes, after a few weeks of uptime, it would disappear as seen from the outside world, while being reachable locally. At the same time, I would see the following messages in /var/log/messages, which, coincidentally, I'm seeing again with a snapshot from 3.0-19980802-SNAP.... Aug 17 12:11:15 marley /kernel: arpresolve: can't allocate llinfo for 195.178.72 .111rt Aug 17 12:11:46 marley inetd[157]: chargen from 131.114.21.10 Aug 17 12:12:21 marley inetd[157]: chargen from 131.114.21.10 Aug 17 12:13:21 marley inetd[157]: chargen from 131.114.21.10 Aug 17 12:19:21 marley last message repeated 2 times Aug 17 12:27:21 marley inetd[157]: chargen from 131.114.21.10 Aug 17 12:28:19 marley /kernel: arpresolve: can't allocate llinfo for 195.178.72 .111rt Aug 17 12:34:04 marley /kernel: arpresolve: can't allocate llinfo for 195.178.72 .111rt Aug 17 12:36:05 marley last message repeated 803 times Aug 17 12:41:44 marley last message repeated 4612 times Aug 17 12:41:44 marley /kernel: arpresolve: can't allocate llinfo Aug 17 12:41:44 marley /kernel: for 195.178.72.111rt Aug 17 12:41:44 marley /kernel: arpresolve: can't allocate llinfo for 195.178.72 .111rt Aug 17 12:42:15 marley last message repeated 514 times Aug 17 12:44:16 marley last message repeated 1682 times Aug 17 12:54:17 marley last message repeated 9008 times Aug 17 13:04:17 marley last message repeated 7611 times Aug 17 13:14:17 marley last message repeated 5513 times [etc.] The IP address is the router acting as gateway to the real world. I'm running routed, and I've added a configuration line, among others, options NMBCLUSTERS=4096 This machine has only been up for just over a day now when these messages are appearing in force, and there has been once or twice when I've seen these messages earlier with this recent snap, although uptime has never been more than a few days before it wedges solid. Any suggestions? I think I'll be disabling routed and adding this host as the default gateway for the upcoming reboot which should return me to the net... Thanks, Barry Bouwsma, Mendelova Univerzita v Brne, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 17 10:07:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02019 for freebsd-current-outgoing; Mon, 17 Aug 1998 10:07:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01996 for ; Mon, 17 Aug 1998 10:07:46 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA18381; Tue, 18 Aug 1998 03:07:03 +1000 Date: Tue, 18 Aug 1998 03:07:03 +1000 From: Bruce Evans Message-Id: <199808171707.DAA18381@godzilla.zeta.org.au> To: bright@www.hotjobs.com, paulz@trantor.stuyts.nl Subject: Re: Cards sharing irq's on PCI bus Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >well, that's unclear, last i heard linux was the only OS to support shared >IRQs and i don't even know how well it handled it. (i think it was more of >a "don't use them at the same time" deal) PCI irq sharing is standard in FreeBSD. 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 17 10:16:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03173 for freebsd-current-outgoing; Mon, 17 Aug 1998 10:16:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03162 for ; Mon, 17 Aug 1998 10:16:43 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id KAA12329; Mon, 17 Aug 1998 10:15:47 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808171715.KAA12329@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein cc: Paul van der Zwan , current@FreeBSD.ORG Subject: Re: Cards sharing irq's on PCI bus In-reply-to: Your message of "Mon, 17 Aug 1998 10:11:10 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Aug 1998 10:15:47 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > well, that's unclear, last i heard linux was the only OS to support shared > IRQs and i don't even know how well it handled it. (i think it was more of > a "don't use them at the same time" deal) Nah, I have shared IRQs for instance one of the options in the Bt848 driver is to specify the IRQ and I have shared the IRQ of up to 3 bt848 cards. In the process I discovered others that were doing the same thing. Cheers, Amancio > but, you can twiddle your bios to give more IRQs to PCI/pnp devices, look > around in it, you should be able to switch IRQ reservations from something > like "LEGACY ISA" to "PCI/pnp" > > (perhaps you used all of your IRQs, but i did this to give my PCI system > more IRQs because too many were reserved for ISA) > > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com > -- There are operating systems, and then there's BSD. > -- http://www.freebsd.org/ > > On Mon, 17 Aug 1998, Paul van der Zwan wrote: > > > I am running very low on available irq's and I noticed that the bios put both > > my SMC 8432BT and my Adaptec 2740 on irq 9. Network performance was terrible, > > iozone on NFS only 300kB/s. After disabling my IDE controller (only need that > > when running Solaris) the Adaptrec was put on irq 14 (where the IDE used to be) > > and my network performance was back ( more than 900kB/s). > > > > Is it allowed to put have more than one PCI card use the same irq ??? > > It sort of worked. No errors or so, just lousy performance ?? > > Maybe someone can shed some light on this ?? > > > > > > 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 > > > > > 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 17 10:26:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05453 for freebsd-current-outgoing; Mon, 17 Aug 1998 10:26:38 -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 KAA05447 for ; Mon, 17 Aug 1998 10:26:33 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id TAA17727; Mon, 17 Aug 1998 19:25:58 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Mon, 17 Aug 1998 19:25:58 +0200 (MET DST) Mime-Version: 1.0 To: tcobb Cc: "'freebsd-current@freebsd.org'" Subject: Re: PANIC: NULLFS not synced with rest of vm? References: 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: 17 Aug 1998 19:25:57 +0200 In-Reply-To: tcobb's message of "Sun, 16 Aug 1998 19:05:30 -0400" Message-ID: Lines: 18 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 KAA05448 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG tcobb writes: > NULLFS panics when used much on the 19980804 SNAP. It appears that isn't We know. This is cut'n'paste from LINT: # NB: The NULL, PORTAL, UMAP and UNION filesystems are known to be # buggy, and WILL panic your system if you attempt to do anything with # them. They are included here as an incentive for some enterprising # soul to sit down and fix them. > Once again, we are willing to pay some reasonable fee to fix it, especially > if they will do so TODAY. That's very nice of you. 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 17 10:55:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09979 for freebsd-current-outgoing; Mon, 17 Aug 1998 10:55:09 -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 KAA09974 for ; Mon, 17 Aug 1998 10:55:06 -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 0z8TU9-0007dr-00; Mon, 17 Aug 1998 10:54:25 -0700 Date: Mon, 17 Aug 1998 10:54:24 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Alfred Perlstein cc: Paul van der Zwan , current@FreeBSD.ORG Subject: Re: Cards sharing irq's on PCI bus 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, 17 Aug 1998, Alfred Perlstein wrote: > well, that's unclear, last i heard linux was the only OS to support shared > IRQs and i don't even know how well it handled it. (i think it was more of > a "don't use them at the same time" deal) Add FreeBSD to that list. How well this works will depend a bit on your motherboard. Performance should not be noticable different when sharing IRQs. > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com > -- There are operating systems, and then there's BSD. > -- http://www.freebsd.org/ Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 17 11:17:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15578 for freebsd-current-outgoing; Mon, 17 Aug 1998 11:17:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-asfm08--171.sirius.net [205.134.241.171]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15523 for ; Mon, 17 Aug 1998 11:17:25 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id LAA08023; Mon, 17 Aug 1998 11:16:29 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199808171816.LAA08023@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein cc: Paul van der Zwan , current@FreeBSD.ORG Subject: Re: Cards sharing irq's on PCI bus In-reply-to: Your message of "Mon, 17 Aug 1998 10:11:10 CDT." X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Aug 1998 11:16:29 -0700 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >well, that's unclear, last i heard linux was the only OS to support shared >IRQs and i don't even know how well it handled it. (i think it was more of >a "don't use them at the same time" deal) Um - I've used shared IRQs on non-Intel systems with OpenBSD/MIPS (the arc port) successfully. This was as a first-cut port to a somewhat broken NKK/MIPS eval board that simply connected each PCI IRQ from each slot together instead of "rotating" them like PC motherboards typically do. (It then ran them all into an Intel SIO chip's PC-compatible interrupt handler which would then be initially programmed to raise a single ISA IRQ for any PCI interrupt.) As long as a PCI driver's interrupt handler first checks the card to see if the interrupt is for it, and if not return, shared IRQs shouldn't be a problem, nor slow down performance too much. Some chips may be really slow to query and see if they really generated an interrupt, or some drivers may be assuming that if their i-handlers were called then they must have something to do instead of checking first. (Newer NKK eval boards and our customer's custom design route each PCI interrupt line directly to one of six separate interrupt pins on the MIPS processor, making things a whole lot more sensible as well as quite a bit faster.) -- Parag To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 17 11:43:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21291 for freebsd-current-outgoing; Mon, 17 Aug 1998 11:43:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21282 for ; Mon, 17 Aug 1998 11:43:08 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.2232.9) id ; Mon, 17 Aug 1998 14:40:11 -0400 Message-ID: From: tcobb To: "'dag-erli@ifi.uio.no'" Cc: "'freebsd-current@freebsd.org'" Subject: RE: PANIC: NULLFS not synced with rest of vm? Date: Mon, 17 Aug 1998 14:40:10 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) 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 LAA21286 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, are you willing to fix it and get paid for it? I'm trying to create a situation where there can be no excuse for not getting this fixed. Circle Net needs it working, I don't have time to get as deeply into FS as I'd need to repair it. If someone has time, and experience in this area, and would like to get paid for that time while still generating code for release to the FreeBSD project, then PLEASE contact me. In case you didn't realize it, this is that company-sponsorship of FreeBSD concept trying to work, here. -Troy Cobb Circle Net, Inc. http://www.circle.net > -----Original Message----- > From: dag-erli@ifi.uio.no [mailto:dag-erli@ifi.uio.no] > Sent: Monday, August 17, 1998 1:26 PM > To: tcobb > Cc: 'freebsd-current@freebsd.org' > Subject: Re: PANIC: NULLFS not synced with rest of vm? > > > tcobb writes: > > NULLFS panics when used much on the 19980804 SNAP. It > appears that isn't > > We know. This is cut'n'paste from LINT: > > # NB: The NULL, PORTAL, UMAP and UNION filesystems are known to be > # buggy, and WILL panic your system if you attempt to do anything with > # them. They are included here as an incentive for some enterprising > # soul to sit down and fix them. > > > Once again, we are willing to pay some reasonable fee to > fix it, especially > > if they will do so TODAY. > > That's very nice of you. > > 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 17 12:32:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28386 for freebsd-current-outgoing; Mon, 17 Aug 1998 12:32:47 -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 MAA28378 for ; Mon, 17 Aug 1998 12:32:45 -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 0z8V0d-0001Po-00; Mon, 17 Aug 1998 12:32:03 -0700 Date: Mon, 17 Aug 1998 12:32:01 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Barry Bouwsma cc: freebsd-current@FreeBSD.ORG Subject: Re: /kernel: arpresolve: can't allocate llinfo 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, 17 Aug 1998, Barry Bierbauch wrote: > Howdy... > > I had been running a -current snap from last November, which usually > worked well, but sometimes, after a few weeks of uptime, it would > disappear as seen from the outside world, while being reachable locally. > At the same time, I would see the following messages in /var/log/messages, > which, coincidentally, I'm seeing again with a snapshot from > 3.0-19980802-SNAP.... > > Aug 17 12:11:15 marley /kernel: arpresolve: can't allocate llinfo for 195.178.72 > .111rt > Aug 17 12:11:46 marley inetd[157]: chargen from 131.114.21.10 > Aug 17 12:12:21 marley inetd[157]: chargen from 131.114.21.10 > Aug 17 12:13:21 marley inetd[157]: chargen from 131.114.21.10 > Aug 17 12:19:21 marley last message repeated 2 times > Aug 17 12:27:21 marley inetd[157]: chargen from 131.114.21.10 You should probably disable the chargen service in /etc/inetd.conf It doesn't seem to have much these days, except to allow outsiders to use your system to launch DoS of attacks. While you are doing that, disable the echo service too. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 17 13:53:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17376 for freebsd-current-outgoing; Mon, 17 Aug 1998 13:53:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from yfn2.ysu.edu (YFN2.YSU.EDU [150.134.50.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA17362 for ; Mon, 17 Aug 1998 13:53:33 -0700 (PDT) (envelope-from ag786@yfn.ysu.edu) Received: from ag786 by yfn2.ysu.edu with local (Exim 1.62 #2) id 0z8WGs-000573-00; Mon, 17 Aug 1998 16:52:54 -0400 From: ag786@yfn.ysu.edu (Barry Bouwsma) To: tom@uniserve.com Subject: Re: /kernel: arpresolve: can't allocate llinfo Cc: freebsd-current@FreeBSD.ORG Reply-To: ag786@yfn.ysu.edu Message-Id: Date: Mon, 17 Aug 1998 16:52:54 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Aug 17 12:27:21 marley inetd[157]: chargen from 131.114.21.10 > > You should probably disable the chargen service in /etc/inetd.conf It >doesn't seem to have much these days, except to allow outsiders to use >your system to launch DoS of attacks. Actually, this chargen is running on port 119 of this news swerver, with the real NNTP port elsewhere. It's just that a peer or two has botched the configuration and is no longer connecting to the proper port, using the wrong one by default... It's left as an exercise for the reader to determine the reasoning behind greeting a few curious NNTP explorers daily with chargen (hint: take a look at the NNTP port of news-feed.inet.tele.dk) Barry Bouwsma, Bastard Newsadmin From Hell, Tele Danmark Internet et al. -- Barry Bouwsma, Intanet an' Netwerkin' gooru-type kind o' ner to be found in the Swiss Appenzell eating cheese or biking somewhere in the area, hacking to Internet connectivity This sig is five lines long. Check your newsreader configuration if you do 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 17 14:09:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20595 for freebsd-current-outgoing; Mon, 17 Aug 1998 14:09: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 OAA20583 for ; Mon, 17 Aug 1998 14:09:10 -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 0z8WW0-0003ku-00; Mon, 17 Aug 1998 14:08:32 -0700 Date: Mon, 17 Aug 1998 14:08:30 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Barry Bouwsma cc: freebsd-current@FreeBSD.ORG Subject: Re: /kernel: arpresolve: can't allocate llinfo 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, 17 Aug 1998, Barry Bouwsma wrote: > >> Aug 17 12:27:21 marley inetd[157]: chargen from 131.114.21.10 > > > > You should probably disable the chargen service in /etc/inetd.conf It > >doesn't seem to have much these days, except to allow outsiders to use > >your system to launch DoS of attacks. > > Actually, this chargen is running on port 119 of this news swerver, > with the real NNTP port elsewhere. It's just that a peer or two > has botched the configuration and is no longer connecting to the > proper port, using the wrong one by default... But it is also bad for you. chargen can easily consume tons of your bandwidth. Refusing connections is so much cheaper for your server, and your network. You chargen trick will backfire on you. > Barry Bouwsma, Bastard Newsadmin From Hell, Tele Danmark Internet et al. > > > > > -- > Barry Bouwsma, Intanet an' Netwerkin' gooru-type kind o' ner > to be found in the Swiss Appenzell eating cheese > or biking somewhere in the area, hacking to Internet connectivity > This sig is five lines long. Check your newsreader configuration if you do no Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 17 15:00:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01307 for freebsd-current-outgoing; Mon, 17 Aug 1998 15:00:47 -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 PAA01299 for ; Mon, 17 Aug 1998 15:00:42 -0700 (PDT) (envelope-from paulz@trantor.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <3138-10894>; Tue, 18 Aug 1998 00:00:01 +0200 Received: from trantor.stuyts.nl (uucp@localhost) by terminus.stuyts.nl (8.9.1/8.8.8) with UUCP id XAA03470; Mon, 17 Aug 1998 23:45:01 +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 XAA06319; Mon, 17 Aug 1998 23:27:38 +0200 (MET DST) Message-Id: <199808172127.XAA06319@trantor.stuyts.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: Cards sharing irq's on PCI bus In-reply-to: Your message of "Tue, 18 Aug 1998 03:07:03 +1000." <199808171707.DAA18381@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Aug 1998 23:27:38 +0200 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >well, that's unclear, last i heard linux was the only OS to support shared > >IRQs and i don't even know how well it handled it. (i think it was more of > >a "don't use them at the same time" deal) > > PCI irq sharing is standard in FreeBSD. > > Bruce > If it is , what might be the cause of the terrible network performance if the SMC and the 2940 are both on irq 9 ?? 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 17 15:23:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06321 for freebsd-current-outgoing; Mon, 17 Aug 1998 15:23:11 -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 PAA06307 for ; Mon, 17 Aug 1998 15:23: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 IAA03632; Tue, 18 Aug 1998 08:22:26 +1000 Date: Tue, 18 Aug 1998 08:22:26 +1000 From: Bruce Evans Message-Id: <199808172222.IAA03632@godzilla.zeta.org.au> To: bde@zeta.org.au, paulz@trantor.stuyts.nl Subject: Re: Cards sharing irq's on PCI bus Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> PCI irq sharing is standard in FreeBSD. >If it is , what might be the cause of the terrible network performance if >the SMC and the 2940 are both on irq 9 ?? Probably SMC driver bugs. I forget which SMC you have. 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 17 15:54:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12066 for freebsd-current-outgoing; Mon, 17 Aug 1998 15:54:57 -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 PAA12041 for ; Mon, 17 Aug 1998 15:54:50 -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 SAA00797; Mon, 17 Aug 1998 18:46:41 -0400 (EDT) (envelope-from lee) Message-ID: <19980817184641.A789@st-lcremean.tidalwave.net> Date: Mon, 17 Aug 1998 18:46:41 -0400 From: Lee Cremeans To: Paul van der Zwan Cc: current@FreeBSD.ORG Subject: Re: Cards sharing irq's on PCI bus Reply-To: lcremean@tidalwave.net References: <199808171707.DAA18381@godzilla.zeta.org.au> <199808172127.XAA06319@trantor.stuyts.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808172127.XAA06319@trantor.stuyts.nl>; from Paul van der Zwan on Mon, Aug 17, 1998 at 11:27:38PM +0200 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 17, 1998 at 11:27:38PM +0200, Paul van der Zwan wrote: > > >well, that's unclear, last i heard linux was the only OS to support shared > > >IRQs and i don't even know how well it handled it. (i think it was more of > > >a "don't use them at the same time" deal) > > > > PCI irq sharing is standard in FreeBSD. > > > > Bruce > > > If it is , what might be the cause of the terrible network performance if > the SMC and the 2940 are both on irq 9 ?? > > Paul Have you checked your BIOS to see if PCI interrupts are set to "level" trigger instead of "edge"? You have to have it set to "level" for IRQ sharing to work correctly. -- 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 Mon Aug 17 16:58:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23084 for freebsd-current-outgoing; Mon, 17 Aug 1998 16:58:15 -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 QAA23060 for ; Mon, 17 Aug 1998 16:58:09 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id TAA19159; Mon, 17 Aug 1998 19:57:01 -0400 (EDT) (envelope-from luoqi) Date: Mon, 17 Aug 1998 19:57:01 -0400 (EDT) From: Luoqi Chen Message-Id: <199808172357.TAA19159@lor.watermarkgroup.com> To: dag-erli@ifi.uio.no, tcobb@staff.circle.net Subject: RE: PANIC: NULLFS not synced with rest of vm? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, are you willing to fix it and get paid for it? > > I'm trying to create a situation where there can be > no excuse for not getting this fixed. Circle Net needs > it working, I don't have time to get as deeply into FS > as I'd need to repair it. If someone has time, and experience > in this area, and would like to get paid for that time > while still generating code for release to the FreeBSD project, > then PLEASE contact me. > > In case you didn't realize it, this is that company-sponsorship > of FreeBSD concept trying to work, here. > > -Troy Cobb > Circle Net, Inc. > http://www.circle.net > It takes much more than a couple of hours to fix nullfs or other stackable file system. Cache coherence is one of the biggest problems. But for the panic you had, you may try the following band-aid. -lq Index: null_subr.c =================================================================== RCS file: /fun/cvs/src/sys/miscfs/nullfs/null_subr.c,v retrieving revision 1.19 diff -u -r1.19 null_subr.c --- null_subr.c 1998/07/30 17:40:45 1.19 +++ null_subr.c 1998/08/17 23:43:51 @@ -173,6 +173,13 @@ return 0; }; VREF(lowervp); /* Extra VREF will be vrele'd in null_node_create */ + + simple_lock(&lowervp->v_interlock); + if (lowervp->v_type == VREG && !lowervp->v_object) + vfs_object_create(lowervp, curproc, NOCRED, + VOP_ISLOCKED(lowervp)); + simple_unlock(&lowervp->v_interlock); + hd = NULL_NHASH(lowervp); LIST_INSERT_HEAD(hd, xp, null_hash); return 0; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 17 17:31:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29930 for freebsd-current-outgoing; Mon, 17 Aug 1998 17:31:20 -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 RAA29903 for ; Mon, 17 Aug 1998 17:31:01 -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 RAA20315; Mon, 17 Aug 1998 17:28:24 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Alfred Perlstein cc: Paul van der Zwan , current@FreeBSD.ORG Subject: Re: Cards sharing irq's on PCI bus In-reply-to: Your message of "Mon, 17 Aug 1998 10:11:10 CDT." Date: Mon, 17 Aug 1998 17:28:23 -0700 Message-ID: <20311.903400103@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > well, that's unclear, last i heard linux was the only OS to support shared > IRQs and i don't even know how well it handled it. (i think it was more of > a "don't use them at the same time" deal) That's bogus - FreeBSD supports IRQ sharing just fine and has for a long time. - 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 17 22:21:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01300 for freebsd-current-outgoing; Mon, 17 Aug 1998 22:21:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa4-33.ix.netcom.com [207.93.136.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01293 for ; Mon, 17 Aug 1998 22:21:31 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id WAA00323; Mon, 17 Aug 1998 22:20:56 -0700 (PDT) (envelope-from tomdean) Date: Mon, 17 Aug 1998 22:20:56 -0700 (PDT) Message-Id: <199808180520.WAA00323@ix.netcom.com> From: Thomas Dean To: current@FreeBSD.ORG Subject: Calloc or VM Problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I noted some previous problems with calloc, and, thought they were fixed. However, I seem to have a problem with calloc or vm. It appears that calloc is stomping on a structure. I collected some numbers on calloc operations. After poking with gdb for a long time, I found that some of the structure entries were changing around the calloc statement. It always changed the same section of the structure. I added some fixed value checks just to catch this problem. The "frame changed" message was always the line after the calloc. I changed calloc to malloc and the problem is the same. The process allocated a total of 1813088 bytes in 3713 operations. ========================================================================== Here is the code fragment about the problem: (I xxxx'ed some names) listPtr = xxxxHeader->xxxxEntry; while(listPtr->entry != NULL) { listPtr = listPtr->next; } if (xxxxHeader->xxxxx.len != 653) { print("frame changed to %d at line %d\n", xxxxHeader->xxxxx.len, __LINE__); } listPtr->entry= (Entry_t *) calloc((numEntries+1),sizeof(Entry_t)); if (xxxxHeader->xxxxx.len != 653) { print("frame changed to %d at line %d\n", xxxxHeader->xxxxx.len, __LINE__); } ========================================================================== # uname -a FreeBSD celebris 3.0-CURRENT FreeBSD 3.0-CURRENT #1: Sat Aug 8 06:36:42 PDT1998 ========================================================================== # dmesg Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #1: Sat Aug 8 06:36:42 PDT 1998 root@celebris:/usr/src/sys/compile/CELEBRIS-SMP Timecounter "i8254" frequency 1193182 Hz cost 2540 ns CPU: Pentium/P54C (586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x3bf real memory = 100663296 (98304K bytes) avail memory = 95268864 (93036K bytes) FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev0x11on pci0.0.0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 17 22:36:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02531 for freebsd-current-outgoing; Mon, 17 Aug 1998 22:36:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com ([203.8.14.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02515 for ; Mon, 17 Aug 1998 22:36:50 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.hilink.com.au [127.0.0.1] (may be forged)) by dingo.cdrom.com (8.8.8/8.8.8) with ESMTP id WAA12072; Mon, 17 Aug 1998 22:33:53 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808172233.WAA12072@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Thomas Dean cc: current@FreeBSD.ORG Subject: Re: Calloc or VM Problem In-reply-to: Your message of "Mon, 17 Aug 1998 22:20:56 MST." <199808180520.WAA00323@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Aug 1998 22:33:53 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sounds like you've accidentally freed the list header at some point. > I noted some previous problems with calloc, and, thought they were > fixed. However, I seem to have a problem with calloc or vm. > > It appears that calloc is stomping on a structure. I collected some > numbers on calloc operations. After poking with gdb for a long time, > I found that some of the structure entries were changing around the > calloc statement. It always changed the same section of the > structure. I added some fixed value checks just to catch this > problem. The "frame changed" message was always the line after the > calloc. I changed calloc to malloc and the problem is the same. > > The process allocated a total of 1813088 bytes in 3713 operations. > > ========================================================================== > Here is the code fragment about the problem: (I xxxx'ed some names) > > listPtr = xxxxHeader->xxxxEntry; > > while(listPtr->entry != NULL) { > listPtr = listPtr->next; > } > > if (xxxxHeader->xxxxx.len != 653) { > print("frame changed to %d at line %d\n", > xxxxHeader->xxxxx.len, __LINE__); > } > > listPtr->entry= (Entry_t *) calloc((numEntries+1),sizeof(Entry_t)); > > if (xxxxHeader->xxxxx.len != 653) { > print("frame changed to %d at line %d\n", > xxxxHeader->xxxxx.len, __LINE__); > } > > ========================================================================== > # uname -a > FreeBSD celebris 3.0-CURRENT FreeBSD 3.0-CURRENT #1: Sat Aug 8 06:36:42 PDT1998 > > ========================================================================== > # dmesg > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.0-CURRENT #1: Sat Aug 8 06:36:42 PDT 1998 > root@celebris:/usr/src/sys/compile/CELEBRIS-SMP > Timecounter "i8254" frequency 1193182 Hz cost 2540 ns > CPU: Pentium/P54C (586-class CPU) > Origin = "GenuineIntel" Id = 0x525 Stepping=5 > Features=0x3bf > real memory = 100663296 (98304K bytes) > avail memory = 95268864 (93036K bytes) > FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 > cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec00000 > Probing for devices on PCI bus 0: > chip0: rev0x11on pci0.0.0 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ 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 17 23:50:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08042 for freebsd-current-outgoing; Mon, 17 Aug 1998 23:50:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coredump.int.tele.dk (fw1.inet.tele.dk [193.163.158.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08037 for ; Mon, 17 Aug 1998 23:50:23 -0700 (PDT) (envelope-from pivrnec@vszbr.cz) Received: from localhost (pivrnec@localhost) by coredump.int.tele.dk (8.9.1/8.8.8) with SMTP id IAA02265 for ; Tue, 18 Aug 1998 08:49:47 +0200 (CEST) (envelope-from pivrnec@vszbr.cz) X-Authentication-Warning: coredump.int.tele.dk: pivrnec owned process doing -bs Date: Tue, 18 Aug 1998 08:49:46 +0200 (CEST) From: Barry Bierbauch X-Sender: pivrnec@coredump.int.tele.dk Reply-To: Barry Bouwsma To: freebsd-current@FreeBSD.ORG Subject: Re: /kernel: arpresolve: can't allocate llinfo 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 17 Aug 1998, some BoZo masquerading as Barry Bierbauch drooled: > Aug 17 12:28:19 marley /kernel: arpresolve: can't allocate llinfo for 195.178.72.111rt > Aug 17 12:34:04 marley /kernel: arpresolve: can't allocate llinfo for 195.178.72.111rt And just as a followup, when I logged into that machine from the local netwerk and did a netstat, here's what I saw: su-2.02# netstat -nr Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 195.178.72.111 UGc -9358 4337645 vx0 127.0.0.1 127.0.0.1 UH 1 4328 lo0 195.178.72 link#1 UC 1 376 vx0 [...] Hmmm. Barry Bouwsma To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 18 00:34:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12757 for freebsd-current-outgoing; Tue, 18 Aug 1998 00:34:49 -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 AAA12752 for ; Tue, 18 Aug 1998 00:34: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 JAA15480; Tue, 18 Aug 1998 09:34:11 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Tue, 18 Aug 1998 09:34:10 +0200 (MET DST) Mime-Version: 1.0 To: tcobb Cc: "'dag-erli@ifi.uio.no'" , "'freebsd-current@freebsd.org'" Subject: Re: PANIC: NULLFS not synced with rest of vm? References: 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: 18 Aug 1998 09:34:09 +0200 In-Reply-To: tcobb's message of "Mon, 17 Aug 1998 14:40:10 -0400" Message-ID: Lines: 14 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 AAA12753 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG tcobb writes: > Well, are you willing to fix it and get paid for it? No, I have no fs experience (and way too much work pending already) > In case you didn't realize it, this is that company-sponsorship > of FreeBSD concept trying to work, here. I did realize it, but I think it was a little hidden away in your first posting, which is why I quoted it for all to see :) 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 18 01:46:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19151 for freebsd-current-outgoing; Tue, 18 Aug 1998 01:46: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 BAA19144 for ; Tue, 18 Aug 1998 01:46:53 -0700 (PDT) (envelope-from paulz@trantor.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <9538-21070>; Tue, 18 Aug 1998 10:46:09 +0200 Received: from trantor.stuyts.nl (uucp@localhost) by terminus.stuyts.nl (8.9.1/8.8.8) with UUCP id KAA19635; Tue, 18 Aug 1998 10:41:05 +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 KAA28583; Tue, 18 Aug 1998 10:26:15 +0200 (MET DST) Message-Id: <199808180826.KAA28583@trantor.stuyts.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: Cards sharing irq's on PCI bus In-reply-to: Your message of "Tue, 18 Aug 1998 08:22:26 +1000." <199808172222.IAA03632@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Aug 1998 10:26:14 +0200 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> PCI irq sharing is standard in FreeBSD. > > >If it is , what might be the cause of the terrible network performance if > >the SMC and the 2940 are both on irq 9 ?? > > Probably SMC driver bugs. I forget which SMC you have. According to dmesg : de0: rev 0x23 int a irq 9 on pci0.14.0 de0: SMC 8432BT 21040 [10Mb/s] pass 2.3 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 Tue Aug 18 02:27:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23884 for freebsd-current-outgoing; Tue, 18 Aug 1998 02:27:03 -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 CAA23873 for ; Tue, 18 Aug 1998 02:27:00 -0700 (PDT) (envelope-from paulz@trantor.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <468-21070>; Tue, 18 Aug 1998 11:26:10 +0200 Received: from trantor.stuyts.nl (uucp@localhost) by terminus.stuyts.nl (8.9.1/8.8.8) with UUCP id LAA20454; Tue, 18 Aug 1998 11:17:45 +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 LAA00399; Tue, 18 Aug 1998 11:03:40 +0200 (MET DST) Message-Id: <199808180903.LAA00399@trantor.stuyts.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: lcremean@tidalwave.net Cc: current@FreeBSD.ORG Subject: Re: Cards sharing irq's on PCI bus In-reply-to: Your message of "Mon, 17 Aug 1998 18:46:41 EDT." <19980817184641.A789@st-lcremean.tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Aug 1998 11:03:40 +0200 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Have you checked your BIOS to see if PCI interrupts are set to "level" > trigger instead of "edge"? You have to have it set to "level" for IRQ > sharing to work correctly. > I have checked all BIOS settings, no way te switch from level te edge triggerred or back. Aren't you confusing it with EISA slots ?? Just to be sure it is a Chaintech 5TDM2 ( Intel TX) motherboard with an Award 4.51 BIOS. 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 Tue Aug 18 04:08:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05972 for freebsd-current-outgoing; Tue, 18 Aug 1998 04:08:55 -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 EAA05966 for ; Tue, 18 Aug 1998 04:08:52 -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 NAA02554 for current@freebsd.org; Tue, 18 Aug 1998 13:08:12 +0200 (MEST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.3.p0.FreeBSD:980818130812:5324=_" Date: Tue, 18 Aug 1998 13:08:12 +0200 (MEST) Organization: university of bayreuth From: Werner Griessl To: current@FreeBSD.ORG Subject: softupdates and smp crash Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:980818130812:5324=_ Content-Type: text/plain; charset=us-ascii ---------------------------------- E-Mail: Werner Griessl Date: 18-Aug-98 Time: 12:58:27 This message was sent by XFMail ---------------------------------- My system with current-smp from yesterday (Aug. 17) crashes with "make buildworld -jx" with x>1 and softupdates on for /usr/obj. Have no problems with j1,softupdates on and j4 or j8 with softupdates off. Appended is a crash-log "gdb6.log" with j4 Werner --_=XFMail.1.3.p0.FreeBSD:980818130812:5324=_ Content-Disposition: attachment; filename="gdb6.log" Content-Transfer-Encoding: base64 Content-Description: gdb6.log Content-Type: application/octet-stream; name=gdb6.log; SizeOnDisk=4604 R0RCIGlzIGZyZWUgc29mdHdhcmUgYW5kIHlvdSBhcmUgd2VsY29tZSB0byBkaXN0cmlidXRlIGNv cGllcyBvZiBpdAogdW5kZXIgY2VydGFpbiBjb25kaXRpb25zOyB0eXBlICJzaG93IGNvcHlpbmci IHRvIHNlZSB0aGUgY29uZGl0aW9ucy4KVGhlcmUgaXMgYWJzb2x1dGVseSBubyB3YXJyYW50eSBm b3IgR0RCOyB0eXBlICJzaG93IHdhcnJhbnR5IiBmb3IgZGV0YWlscy4KR0RCIDQuMTYgKGkzODYt dW5rbm93bi1mcmVlYnNkKSwgCkNvcHlyaWdodCAxOTk2IEZyZWUgU29mdHdhcmUgRm91bmRhdGlv biwgSW5jLi4uCklkbGVQVEQgMjQ5MDM2OAppbml0aWFsIHBjYiBhdCAyMzU2OTAKcGFuaWNzdHI6 ICVzOiBkaXIgaW51bSAlZCAhPSBuZXcgJWQKcGFuaWMgbWVzc2FnZXM6Ci0tLQpwYW5pYzogaW5p dGlhdGVfd3JpdGVfZmlsZXBhZ2U6IGRpciBpbnVtIDAgIT0gbmV3IDQwMTc3Cm1wX2xvY2sgPSAw MTAwMDAwMTsgY3B1aWQgPSAxOyBsYXBpYy5pZCA9IDAxMDAwMDAwCmJvb3QoKSBjYWxsZWQgb24g Y3B1IzEKCnN5bmNpbmcgZGlza3MuLi4gcGFuaWM6IHNvZnRkZXBfbG9jazogbG9ja2luZyBhZ2Fp bnN0IG15c2VsZgptcF9sb2NrID0gMDEwMDAwMDE7IGNwdWlkID0gMTsgbGFwaWMuaWQgPSAwMTAw MDAwMApib290KCkgY2FsbGVkIG9uIGNwdSMxCgpkdW1waW5nIHRvIGRldiAzMDQwMSwgb2Zmc2V0 IDI2MjE0NApkdW1wIDEyOCAxMjcgMTI2IDEyNSAxMjQgMTIzIDEyMiAxMjEgMTIwIDExOSAxMTgg MTE3IDExNiAxMTUgMTE0IDExMyAxMTIgMTExIDExMCAxMDkgMTA4IDEwNyAxMDYgMTA1IDEwNCAx MDMgMTAyIDEwMSAxMDAgOTkgOTggOTcgOTYgOTUgOTQgOTMgOTIgOTEgOTAgODkgODggODcgODYg ODUgODQgODMgODIgODEgODAgNzkgNzggNzcgNzYgNzUgNzQgNzMgNzIgNzEgNzAgNjkgNjggNjcg NjYgNjUgNjQgNjMgNjIgNjEgNjAgNTkgNTggNTcgNTYgNTUgNTQgNTMgNTIgNTEgNTAgNDkgNDgg NDcgNDYgNDUgNDQgNDMgNDIgNDEgNDAgMzkgMzggMzcgMzYgMzUgMzQgMzMgMzIgMzEgMzAgMjkg MjggMjcgMjYgMjUgMjQgMjMgMjIgMjEgMjAgMTkgMTggMTcgMTYgMTUgMTQgMTMgMTIgMTEgMTAg OSA4IDcgNiA1IDQgMyAyIDEgCi0tLQojMCAgYm9vdCAoaG93dG89MjYwKSBhdCAuLi8uLi9rZXJu L2tlcm5fc2h1dGRvd24uYzoyODYKMjg2CQkJCQlkdW1wcGNiLnBjYl9jcjMgPSByY3IzKCk7Cihr Z2RiKSBidAojMCAgYm9vdCAoaG93dG89MjYwKSBhdCAuLi8uLi9rZXJuL2tlcm5fc2h1dGRvd24u YzoyODYKIzEgIDB4ZjAxMTUxYzEgaW4gcGFuaWMgKGZtdD0weGYwMWFiODYxICJzb2Z0ZGVwX2xv Y2s6IGxvY2tpbmcgYWdhaW5zdCBteXNlbGYiKQogICAgYXQgLi4vLi4va2Vybi9rZXJuX3NodXRk b3duLmM6NDI5CiMyICAweGYwMWFiOGM5IGluIGFjcXVpcmVfbG9jayAobGs9MHhmMDIyNjVhYykK ICAgIGF0IC4uLy4uL3Vmcy9mZnMvZmZzX3NvZnRkZXAuYzoyNjMKIzMgIDB4ZjAxYWVlNTQgaW4g aW5pdGlhdGVfd3JpdGVfZmlsZXBhZ2UgKHBhZ2VkZXA9MHhmMGM0OWUwMCwgYnA9MHhmMzUzMDBi MCkKICAgIGF0IC4uLy4uL3Vmcy9mZnMvZmZzX3NvZnRkZXAuYzoyNzQ1CiM0ICAweGYwMWFlY2Jm IGluIHNvZnRkZXBfZGlza19pb19pbml0aWF0aW9uIChicD0weGYzNTMwMGIwKQogICAgYXQgLi4v Li4vdWZzL2Zmcy9mZnNfc29mdGRlcC5jOjI2NjYKIzUgIDB4ZjAxNDNlN2EgaW4gc3BlY19zdHJh dGVneSAoYXA9MHhmNWY0YmJkMCkKICAgIGF0IC4uLy4uL21pc2Nmcy9zcGVjZnMvc3BlY192bm9w cy5jOjU1NQojNiAgMHhmMDE0MzU5OSBpbiBzcGVjX3Zub3BlcmF0ZSAoYXA9MHhmNWY0YmJkMCkK ICAgIGF0IC4uLy4uL21pc2Nmcy9zcGVjZnMvc3BlY192bm9wcy5jOjEyNwojNyAgMHhmMDFiYmI4 MSBpbiB1ZnNfdm5vcGVyYXRlc3BlYyAoYXA9MHhmNWY0YmJkMCkKICAgIGF0IC4uLy4uL3Vmcy91 ZnMvdWZzX3Zub3BzLmM6MjMwMwojOCAgMHhmMDFiYjRkMyBpbiB1ZnNfc3RyYXRlZ3kgKGFwPTB4 ZjVmNGJjMTApIGF0IHZub2RlX2lmLmg6ODkxCiM5ICAweGYwMWJiYjUxIGluIHVmc192bm9wZXJh dGUgKGFwPTB4ZjVmNGJjMTApCiAgICBhdCAuLi8uLi91ZnMvdWZzL3Vmc192bm9wcy5jOjIyODUK IzEwIDB4ZjAxMzA3MGIgaW4gYndyaXRlIChicD0weGYzNTMwMGIwKSBhdCB2bm9kZV9pZi5oOjg5 MQojMTEgMHhmMDEzNGZlYSBpbiB2b3Bfc3RkYndyaXRlIChhcD0weGY1ZjRiYzRjKSBhdCAuLi8u Li9rZXJuL3Zmc19kZWZhdWx0LmM6Mjg0CiMxMiAweGYwMTM0ZTAxIGluIHZvcF9kZWZhdWx0b3Ag KGFwPTB4ZjVmNGJjNGMpIGF0IC4uLy4uL2tlcm4vdmZzX2RlZmF1bHQuYzoxMzAKIzEzIDB4ZjAx YmJiNTEgaW4gdWZzX3Zub3BlcmF0ZSAoYXA9MHhmNWY0YmM0YykKICAgIGF0IC4uLy4uL3Vmcy91 ZnMvdWZzX3Zub3BzLmM6MjI4NQojMTQgMHhmMDEzMDkzOCBpbiBiYXdyaXRlIChicD0weGYzNTMw MGIwKSBhdCB2bm9kZV9pZi5oOjExMjEKIzE1IDB4ZjAxYjQ5YjEgaW4gZmZzX2ZzeW5jIChhcD0w eGY1ZjRiY2YwKSBhdCAuLi8uLi91ZnMvZmZzL2Zmc192bm9wcy5jOjE4NgojMTYgMHhmMDFiMmU0 MiBpbiBmZnNfc3luYyAobXA9MHhmMGI5NzgwMCwgd2FpdGZvcj0yLCBjcmVkPTB4ZjBiMWFhODAs IAogICAgcD0weGYwMjUyZDcwKSBhdCB2bm9kZV9pZi5oOjQ5OQojMTcgMHhmMDEzOWE1MyBpbiBz eW5jIChwPTB4ZjAyNTJkNzAsIHVhcD0weDApIGF0IC4uLy4uL2tlcm4vdmZzX3N5c2NhbGxzLmM6 NTE1CiMxOCAweGYwMTE0ZDQzIGluIGJvb3QgKGhvd3RvPTI1NikgYXQgLi4vLi4va2Vybi9rZXJu X3NodXRkb3duLmM6MjAzCiMxOSAweGYwMTE1MWMxIGluIHBhbmljIChmbXQ9MHhmMDFhZWUwOSAi JXM6IGRpciBpbnVtICVkICE9IG5ldyAlZCIpCiAgICBhdCAuLi8uLi9rZXJuL2tlcm5fc2h1dGRv d24uYzo0MjkKIzIwIDB4ZjAxYWVlODQgaW4gaW5pdGlhdGVfd3JpdGVfZmlsZXBhZ2UgKHBhZ2Vk ZXA9MHhmMGM0Nzc4MCwgYnA9MHhmMzUyNTBmMCkKICAgIGF0IC4uLy4uL3Vmcy9mZnMvZmZzX3Nv ZnRkZXAuYzoyNzUyCiMyMSAweGYwMWFlY2JmIGluIHNvZnRkZXBfZGlza19pb19pbml0aWF0aW9u IChicD0weGYzNTI1MGYwKQogICAgYXQgLi4vLi4vdWZzL2Zmcy9mZnNfc29mdGRlcC5jOjI2NjYK IzIyIDB4ZjAxNDNlN2EgaW4gc3BlY19zdHJhdGVneSAoYXA9MHhmNWY0YmRmNCkKICAgIGF0IC4u Ly4uL21pc2Nmcy9zcGVjZnMvc3BlY192bm9wcy5jOjU1NQojMjMgMHhmMDE0MzU5OSBpbiBzcGVj X3Zub3BlcmF0ZSAoYXA9MHhmNWY0YmRmNCkKICAgIGF0IC4uLy4uL21pc2Nmcy9zcGVjZnMvc3Bl Y192bm9wcy5jOjEyNwojMjQgMHhmMDFiYmI4MSBpbiB1ZnNfdm5vcGVyYXRlc3BlYyAoYXA9MHhm NWY0YmRmNCkKICAgIGF0IC4uLy4uL3Vmcy91ZnMvdWZzX3Zub3BzLmM6MjMwMwojMjUgMHhmMDFi YjRkMyBpbiB1ZnNfc3RyYXRlZ3kgKGFwPTB4ZjVmNGJlMzQpIGF0IHZub2RlX2lmLmg6ODkxCiMy NiAweGYwMWJiYjUxIGluIHVmc192bm9wZXJhdGUgKGFwPTB4ZjVmNGJlMzQpCiAgICBhdCAuLi8u Li91ZnMvdWZzL3Vmc192bm9wcy5jOjIyODUKIzI3IDB4ZjAxMzA3MGIgaW4gYndyaXRlIChicD0w eGYzNTI1MGYwKSBhdCB2bm9kZV9pZi5oOjg5MQojMjggMHhmMDEzNGZlYSBpbiB2b3Bfc3RkYndy aXRlIChhcD0weGY1ZjRiZTcwKSBhdCAuLi8uLi9rZXJuL3Zmc19kZWZhdWx0LmM6Mjg0CiMyOSAw eGYwMTM0ZTAxIGluIHZvcF9kZWZhdWx0b3AgKGFwPTB4ZjVmNGJlNzApIGF0IC4uLy4uL2tlcm4v dmZzX2RlZmF1bHQuYzoxMzAKIzMwIDB4ZjAxYmJiNTEgaW4gdWZzX3Zub3BlcmF0ZSAoYXA9MHhm NWY0YmU3MCkKICAgIGF0IC4uLy4uL3Vmcy91ZnMvdWZzX3Zub3BzLmM6MjI4NQojMzEgMHhmMDEz MDkzOCBpbiBiYXdyaXRlIChicD0weGYzNTI1MGYwKSBhdCB2bm9kZV9pZi5oOjExMjEKIzMyIDB4 ZjAxYjQ5YjEgaW4gZmZzX2ZzeW5jIChhcD0weGY1ZjRiZjE0KSBhdCAuLi8uLi91ZnMvZmZzL2Zm c192bm9wcy5jOjE4NgojMzMgMHhmMDFiMmU0MiBpbiBmZnNfc3luYyAobXA9MHhmMGI5NzgwMCwg d2FpdGZvcj0yLCBjcmVkPTB4ZjBiYjZkODAsIAogICAgcD0weGY1ZWJhMWMwKSBhdCB2bm9kZV9p Zi5oOjQ5OQojMzQgMHhmMDEzOWE1MyBpbiBzeW5jIChwPTB4ZjVlYmExYzAsIHVhcD0weGY1ZjRi Zjg0KQogICAgYXQgLi4vLi4va2Vybi92ZnNfc3lzY2FsbHMuYzo1MTUKIzM1IDB4ZjAxZGU3NWIg aW4gc3lzY2FsbCAoZnJhbWU9e3RmX2VzID0gMzksIHRmX2RzID0gMzksIHRmX2VkaSA9IC0yNzI2 Mzg4NDksIAogICAgICB0Zl9lc2kgPSAtMjcyNjM4NTQ0LCB0Zl9lYnAgPSAtMjcyNjM5MjI4LCB0 Zl9pc3AgPSAtMTY4NTA5NDg0LCAKICAgICAgdGZfZWJ4ID0gMTQ3NTUyLCB0Zl9lZHggPSA2LCB0 Zl9lY3ggPSAwLCB0Zl9lYXggPSAzNiwgdGZfdHJhcG5vID0gNywgCiAgICAgIHRmX2VyciA9IDcs IHRmX2VpcCA9IDUzNzI1ODUyOSwgdGZfY3MgPSAzMSwgdGZfZWZsYWdzID0gNTE0LCAKICAgICAg dGZfZXNwID0gLTI3MjYzOTIzNiwgdGZfc3MgPSAzOX0pIGF0IC4uLy4uL2kzODYvaTM4Ni90cmFw LmM6MTAzMQojMzYgMHgyMDA1ZWEyMSBpbiA/PyAoKQooa2dkYikgcXVpdAo= --_=XFMail.1.3.p0.FreeBSD:980818130812:5324=_-- End of MIME 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 18 07:14:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24013 for freebsd-current-outgoing; Tue, 18 Aug 1998 07:14:48 -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 HAA24008; Tue, 18 Aug 1998 07:14:45 -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 QAA07178; Tue, 18 Aug 1998 16:19:42 +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 QAA28650; Tue, 18 Aug 1998 16:22:08 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id QAA23756; Tue, 18 Aug 1998 16:13:35 +0200 (CEST) Message-ID: <19980818161335.30289@deepo.prosa.dk> Date: Tue, 18 Aug 1998 16:13:35 +0200 From: Philippe Regnauld To: Werner Griessl Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: softupdates and smp crash References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from Werner Griessl on Tue, Aug 18, 1998 at 01:08:12PM +0200 X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Werner Griessl writes: > > My system with current-smp from yesterday (Aug. 17) crashes with > "make buildworld -jx" with x>1 and softupdates on for /usr/obj. > Have no problems with j1,softupdates on and j4 or j8 with softupdates off. Same here last night. 2xPPro-200, 64MB, UW IBM DCAS. > Appended is a crash-log "gdb6.log" with j4 #0 boot (howto=260) at ../../kern/kern_shutdown.c:286 #1 0xf01151c1 in panic (fmt=0xf01ab861 "softdep_lock: locking against myself") at ../../kern/kern_shutdown.c:429 #2 0xf01ab8c9 in acquire_lock (lk=0xf02265ac) at ../../ufs/ffs/ffs_softdep.c:263 +-> #3 0xf01aee54 in initiate_write_filepage (pagedep=0xf0c49e00, bp=0xf35300b0) | at ../../ufs/ffs/ffs_softdep.c:2745 | #4 0xf01aecbf in softdep_disk_io_initiation (bp=0xf35300b0) | I crashed here. -- -[ 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 18 08:52:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08164 for freebsd-current-outgoing; Tue, 18 Aug 1998 08:52:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08159 for ; Tue, 18 Aug 1998 08:52:19 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id RAA12864 for ; Tue, 18 Aug 1998 17:51:38 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.1/8.9.1) with ESMTP id RAA12348 for ; Tue, 18 Aug 1998 17:51:38 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id RAA12768 for ; Tue, 18 Aug 1998 17:51:34 +0200 (CEST) From: Andre Albsmeier Message-Id: <199808181551.RAA01593@internal> Subject: Re: Cards sharing irq's on PCI bus In-Reply-To: <199808180903.LAA00399@trantor.stuyts.nl> from Paul van der Zwan at "Aug 18, 98 11:03:40 am" To: paulz@trantor.stuyts.nl (Paul van der Zwan) Date: Tue, 18 Aug 1998 17:51:26 +0200 (CEST) Cc: lcremean@tidalwave.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 > > Have you checked your BIOS to see if PCI interrupts are set to "level" > > trigger instead of "edge"? You have to have it set to "level" for IRQ > > sharing to work correctly. > > Here is a part of my dmesg: ahc0 rev 0 int a irq 15 on pci0:13:0 mapreg[10] type=1 addr=00006000 size=0100. mapreg[14] type=0 addr=e0000000 size=1000. reg20: virtual=0xf559d000 physical=0xe0000000 size=0x1000 ahc0: Reading SEEPROM...done. ahc1 rev 0 int a irq 11 on pci0:14:0 mapreg[10] type=1 addr=00006400 size=0100. mapreg[14] type=0 addr=e0001000 size=1000. reg20: virtual=0xf559e000 physical=0xe0001000 size=0x1000 ahc1: Reading SEEPROM...done. de0 rev 34 int a irq 10 on pci1:4:0 mapreg[10] type=1 addr=0000e000 size=0080. [pci1 uses memory from dc000000 to dfffffff] mapreg[14] type=0 addr=dd000000 size=0080. reg16: ioaddr=0xe000 size=0x80 de0: SMC 9332BDT 21140A [10-100Mb/s] pass 2.2 de1 rev 34 int a irq 9 on pci1:5:0 mapreg[10] type=1 addr=0000e400 size=0080. [pci1 uses memory from dc000000 to dfffffff] mapreg[14] type=0 addr=dd001000 size=0080. reg16: ioaddr=0xe400 size=0x80 de1: SMC 9332BDT 21140A [10-100Mb/s] pass 2.2 de2 rev 36 int a irq 9 on pci2:4:0 mapreg[10] type=1 addr=0000d000 size=0080. [pci2 uses memory from d8000000 to dbffffff] mapreg[14] type=0 addr=d9000000 size=0080. reg16: ioaddr=0xd000 size=0x80 using shared irq 9. de2: SMC 8434BT-CH1 21040 [10Mb/s] pass 2.4 de3 rev 36 int a irq 15 on pci2:5:0 mapreg[10] type=1 addr=0000d400 size=0080. [pci2 uses memory from d8000000 to dbffffff] mapreg[14] type=0 addr=d9001000 size=0080. reg16: ioaddr=0xd400 size=0x80 using shared irq 15. de3: SMC 8434BT-CH2 21040 [10Mb/s] pass 2.4 As you see, one Adaptec shares its int with de3 (irq 15) and also de1 and de2 share the same irq (irq9) I couldn't see any performance degrade due to the int sharing. > I have checked all BIOS settings, no way te switch from level te edge > triggerred or back. Aren't you confusing it with EISA slots ?? > Just to be sure it is a Chaintech 5TDM2 ( Intel TX) motherboard with an > Award 4.51 BIOS. Hmm, I am using Chaintechs 5IFM1, 6IDM, 6TDM and 6BTM. In all BIOSes I can enable level irq. Maybe you want to look once more :-) > > Paul -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 18 09:06:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09526 for freebsd-current-outgoing; Tue, 18 Aug 1998 09:06:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa4-35.ix.netcom.com [207.93.136.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09521 for ; Tue, 18 Aug 1998 09:06:36 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id JAA14177; Tue, 18 Aug 1998 09:05:56 -0700 (PDT) (envelope-from tomdean) Date: Tue, 18 Aug 1998 09:05:56 -0700 (PDT) Message-Id: <199808181605.JAA14177@ix.netcom.com> From: Thomas Dean To: current@FreeBSD.ORG In-reply-to: <199808172233.WAA12072@dingo.cdrom.com> (message from Mike Smith on Mon, 17 Aug 1998 22:33:53 +0000) Subject: Re: Calloc or VM Problem <== My Problem, Now Solved Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp showed me how to find this kind of problem. setenv MALLOC_OPTIONS UJA ktrace -t u ./your-program It was my problem. The initial structure was somewhat small. In all the transactions, a few dozen bytes were calloc'ed for a small table. After receiving his message, the problem was easy to find. In pouring over the entire structure, the remainder was calloc'ed for a future table and never used, thus not corrupted. Thanks for your help, tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 18 11:04:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00107 for freebsd-current-outgoing; Tue, 18 Aug 1998 11:04:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29981 for ; Tue, 18 Aug 1998 11:04:15 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id TAA00368; Tue, 18 Aug 1998 19:58:44 +0200 (CEST) To: Thomas Dean cc: current@FreeBSD.ORG Subject: Re: Calloc or VM Problem <== My Problem, Now Solved In-reply-to: Your message of "Tue, 18 Aug 1998 09:05:56 PDT." <199808181605.JAA14177@ix.netcom.com> Date: Tue, 18 Aug 1998 19:58:43 +0200 Message-ID: <366.903463123@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808181605.JAA14177@ix.netcom.com>, Thomas Dean writes: >Poul-Henning Kamp showed me how to find this >kind of problem. > > setenv MALLOC_OPTIONS UJA > ktrace -t u ./your-program > >It was my problem. You don't need the 'U' and the ktrace, unless you are making a tracefile, most malloc bugs seems to be caught with 'AJ'. I will recommend any software developer to ln -s AJ /etc/malloc.conf on their test machines. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 18 11:10:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01150 for freebsd-current-outgoing; Tue, 18 Aug 1998 11:10:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail2.stlnet.com (mail2.stlnet.com [209.96.6.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01051 for ; Tue, 18 Aug 1998 11:10:00 -0700 (PDT) (envelope-from xavier@stlnet.com) Received: from xavier.stlnet.com (xavier.stlnet.com [209.96.2.5]) by mail2.stlnet.com (8.9.1/8.9.0) with ESMTP id LAA20166 for ; Tue, 18 Aug 1998 11:35:47 -0500 (CDT) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 18 Aug 1998 11:35:30 -0500 (CDT) Organization: Pulitzer Technologies Inc. From: "Jon E. Kump" To: freebsd-current@FreeBSD.ORG Subject: Make buildworld not working on -current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having problems with building the world on a new cvsuped distrib. This is my problem The directory /usr/obj/usr/src/tmp/usr/local/share/snmp is not getting c reated. When it tries to install it fails. Not sure why the directory structu re is not getting created. The share directory is not created either. -------------------------------------------------------------- Rebuilding bootstrap libraries -------------------------------------------------------------- cd /usr/src; PATH=/usr/obj/usr/src/tmp/sbin:/usr/obj/usr/src/tmp/usr/sbin:/usr/o bj/usr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin:/usr/local/qt/bin:/home/jkump/bi n:/bin:/usr/bin:/usr/X11/bin:/usr/contrib/bin:/usr/contrib/mh/bin:/usr/games:/us r/local/bin:/sbin:/usr/sbin:/usr/local/jdk1.1.6/bin BISON_SIMPLE=/usr/obj/usr/sr c/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexe c:/usr/obj/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/usr/src/tmp/usr/local/s hare/snmp:/usr/obj/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/usr/src/tmp/us r/local/share/snmp LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/local/share/snmp:/usr/ obj/usr/src/tmp/usr/lib NOEXTRADEPEND=t OBJFORMAT_PATH=/usr/obj/usr/src/tmp/usr /libexec:/usr/libexec /usr/obj/usr/src/tmp/usr/bin/make DESTDIR=/usr/obj/usr/src /tmp bootstrap-libraries cd /usr/src/lib/csu/i386; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -D NOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DN OINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/ make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install cleandir obj cc -O -pipe -DLIBC_SCCS -fno-omit-frame-pointer -I/usr/obj/usr/src/tmp/usr/inc lude -c -DCRT0 -DDYNAMIC /usr/src/lib/csu/i386/crt0.c -o crt0.o ld -O crt0.o -x -r crt0.o cc -O -pipe -DLIBC_SCCS -fno-omit-frame-pointer -I/usr/obj/usr/src/tmp/usr/inc lude -fpic -c /usr/src/lib/csu/i386/c++rt0.c cc -O -pipe -DLIBC_SCCS -fno-omit-frame-pointer -I/usr/obj/usr/src/tmp/usr/inc lude -c -DMCRT0 -DDYNAMIC /usr/src/lib/csu/i386/crt0.c -o gcrt0.o ld -O gcrt0.o -x -r gcrt0.o cc -O -pipe -DLIBC_SCCS -fno-omit-frame-pointer -I/usr/obj/usr/src/tmp/usr/inc lude -c -DCRT0 /usr/src/lib/csu/i386/crt0.c -o scrt0.o ld -O scrt0.o -x -r scrt0.o cc -O -pipe -DLIBC_SCCS -fno-omit-frame-pointer -I/usr/obj/usr/src/tmp/usr/inc lude -c -DMCRT0 /usr/src/lib/csu/i386/crt0.c -o sgcrt0.o ld -O sgcrt0.o -x -r sgcrt0.o install -c -o bin -g bin -m 444 crt0.o c++rt0.o gcrt0.o scrt0.o sgcrt0.o /usr/o bj/usr/src/tmp/usr/local/share/snmp usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop. *** Error code 1 Stop. *** Error code 1 Stop. ------------------------------------------------------------------------- |Jon E. Kump Sr. Unix Systems Administrator, Web Programmer,| |jkump@stlnet.com Systems Programmer, Postmaster | |xavier@stlnet.com Pulitzer Technologies, Inc. | ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 18 11:24:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03239 for freebsd-current-outgoing; Tue, 18 Aug 1998 11:24:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dean.pc.sas.com (sas90102.sas.com [192.58.190.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03227 for ; Tue, 18 Aug 1998 11:24:05 -0700 (PDT) (envelope-from brdean@dean.pc.sas.com) Received: (from brdean@localhost) by dean.pc.sas.com (8.8.8/8.8.8) id OAA05715; Tue, 18 Aug 1998 14:23:26 -0400 (EDT) (envelope-from brdean) Message-Id: <199808181823.OAA05715@dean.pc.sas.com> From: "Brian Dean" Subject: Sysinstall broken: can't load config file from floppy To: freebsd-current@FreeBSD.ORG Date: Tue, 18 Aug 1998 14:23:26 -0400 (EDT) Reply-To: brdean@unx.sas.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While installing FreeBSD from today's snap (8/18), I got the following error when loading a configuration file from a floppy: "Error mounting floppy fd0 (/dev/fd0) on /dist : Invalid argument" The debug screen only said: "DEBUG: Init floppy called for xxx.cfg distribution" The floppy I'm using is MS-DOS formatted. The last snap I installed was 7/26 and it worked with no problems. I was wondering if anyone else has had this problem and if there are any known work-arounds. Thanks, -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 18 14:15:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27310 for freebsd-current-outgoing; Tue, 18 Aug 1998 14:15:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27303 for ; Tue, 18 Aug 1998 14:15:50 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id OAA26327; Tue, 18 Aug 1998 14:15:12 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 18 Aug 1998 14:15:12 -0700 (PDT) From: Doug White To: Barry Bouwsma cc: freebsd-current@FreeBSD.ORG Subject: Re: /kernel: arpresolve: can't allocate llinfo 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, 18 Aug 1998, Barry Bierbauch wrote: > On 17 Aug 1998, some BoZo masquerading as Barry Bierbauch drooled: > > > Aug 17 12:28:19 marley /kernel: arpresolve: can't allocate llinfo for 195.178.72.111rt > > Aug 17 12:34:04 marley /kernel: arpresolve: can't allocate llinfo for 195.178.72.111rt > > And just as a followup, when I logged into that machine from the local > netwerk and did a netstat, here's what I saw: > > su-2.02# netstat -nr > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > default 195.178.72.111 UGc -9358 4337645 vx0 > 127.0.0.1 127.0.0.1 UH 1 4328 lo0 > 195.178.72 link#1 UC 1 376 vx0 > [...] > > Hmmm. Your system seems to be confused about your router, or you have some seriously runaway TCP processes; refs somehow completely rolled over. :) llinfo problems usually stem from bad routing or netmasking. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 18 14:19:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27983 for freebsd-current-outgoing; Tue, 18 Aug 1998 14:19:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27973 for ; Tue, 18 Aug 1998 14:19:02 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id OAA26340; Tue, 18 Aug 1998 14:18:10 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 18 Aug 1998 14:18:10 -0700 (PDT) From: Doug White To: Brian Dean cc: freebsd-current@FreeBSD.ORG Subject: Re: Sysinstall broken: can't load config file from floppy In-Reply-To: <199808181823.OAA05715@dean.pc.sas.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, 18 Aug 1998, Brian Dean wrote: > While installing FreeBSD from today's snap (8/18), I got the following > error when loading a configuration file from a floppy: > > "Error mounting floppy fd0 (/dev/fd0) on /dist : Invalid argument" > > The debug screen only said: > > "DEBUG: Init floppy called for xxx.cfg distribution" > > The floppy I'm using is MS-DOS formatted. Are you sure? Invalid argument usually comes if /dev/fd0 isn't a MSDOS formatted floppy. > The last snap I installed was 7/26 and it worked with no problems. I > was wondering if anyone else has had this problem and if there are any > known work-arounds. Try regenerating your floppy disk. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 18 16:13:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24415 for freebsd-current-outgoing; Tue, 18 Aug 1998 16:13:57 -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 QAA24395 for ; Tue, 18 Aug 1998 16:13:40 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA07708; Wed, 19 Aug 1998 09:12:59 +1000 Date: Wed, 19 Aug 1998 09:12:59 +1000 From: Bruce Evans Message-Id: <199808182312.JAA07708@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, xavier@stlnet.com Subject: Re: Make buildworld not working on -current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The directory /usr/obj/usr/src/tmp/usr/local/share/snmp is not getting c ^^^^^^^^^^^^^^^^^^^^^ >reated. When it tries to install it fails. Not sure why the directory structu >re is not getting created. The share directory is not created either. This is caused by pollution in the environment (SHLIBDIR set to /usr/local/share/snmp) so that SHLIBDIR is not set to the default of ${LIBDIR} (normally /usr/lib/aout). 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 18 16:59:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02652 for freebsd-current-outgoing; Tue, 18 Aug 1998 16:59:09 -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 QAA02636 for ; Tue, 18 Aug 1998 16:59:04 -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 QAA14056; Tue, 18 Aug 1998 16:56:04 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: brdean@unx.sas.com cc: freebsd-current@FreeBSD.ORG Subject: Re: Sysinstall broken: can't load config file from floppy In-reply-to: Your message of "Tue, 18 Aug 1998 14:23:26 EDT." <199808181823.OAA05715@dean.pc.sas.com> Date: Tue, 18 Aug 1998 16:55:58 -0700 Message-ID: <14048.903484558@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While installing FreeBSD from today's snap (8/18), I got the following > error when loading a configuration file from a floppy: > > "Error mounting floppy fd0 (/dev/fd0) on /dist : Invalid argument" > > The debug screen only said: > > "DEBUG: Init floppy called for xxx.cfg distribution" I took MSDOSFS out of the GENERIC kernel a few days ago in order to make the snaps work again - we were out of space. This isn't critical from the DOS installation code since it doesn't use msdosfs, it uses stand-alone DOSFS parsing code in sysinstall. Unfortunately, the corner case here is the floppy mount code which tries UFS then MSDOSFS as a mount type - it doesn't go through the stand-alone stuff. Hmmmm. Is this really critical, or can you put your config file on a UFS formatted floppy? - 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 18 18:38:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21182 for freebsd-current-outgoing; Tue, 18 Aug 1998 18:38:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dean.pc.sas.com (spi11311.southpeak.com [192.58.191.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21169 for ; Tue, 18 Aug 1998 18:38:16 -0700 (PDT) (envelope-from brdean@dean.pc.sas.com) Received: (from brdean@localhost) by dean.pc.sas.com (8.8.8/8.8.8) id VAA06566; Tue, 18 Aug 1998 21:36:57 -0400 (EDT) (envelope-from brdean) Message-Id: <199808190136.VAA06566@dean.pc.sas.com> From: "Brian Dean" Subject: Re: Sysinstall broken: can't load config file from floppy In-Reply-To: <14048.903484558@time.cdrom.com> from "Jordan K. Hubbard" at "Aug 18, 98 04:55:58 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 18 Aug 1998 21:36:57 -0400 (EDT) Cc: freebsd-current@FreeBSD.ORG Reply-To: brdean@unx.sas.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > While installing FreeBSD from today's snap (8/18), I got the following > > error when loading a configuration file from a floppy: > > > > "Error mounting floppy fd0 (/dev/fd0) on /dist : Invalid argument" > > > > The debug screen only said: > > > > "DEBUG: Init floppy called for xxx.cfg distribution" > > I took MSDOSFS out of the GENERIC kernel a few days ago in order to > make the snaps work again - we were out of space. This isn't critical > from the DOS installation code since it doesn't use msdosfs, it uses > stand-alone DOSFS parsing code in sysinstall. Unfortunately, the > corner case here is the floppy mount code which tries UFS then MSDOSFS > as a mount type - it doesn't go through the stand-alone stuff. > > Hmmmm. Is this really critical, or can you put your config file on > a UFS formatted floppy? > > - Jordan It's not that critical, I can put the config file on a UFS floppy. Thanks, -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 18 19:47:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02009 for freebsd-current-outgoing; Tue, 18 Aug 1998 19:47:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ha1.rdc1.pa.home.com (ha1.rdc1.pa.home.com [24.2.5.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01995 for ; Tue, 18 Aug 1998 19:46:54 -0700 (PDT) (envelope-from nellie@home.com) Received: from cc219337-a.lwmrn1.pa.home.com ([24.3.111.2]) by ha1.rdc1.pa.home.com (Netscape Mail Server v2.02) with SMTP id AAA18920 for ; Tue, 18 Aug 1998 19:46:16 -0700 Date: Tue, 18 Aug 1998 22:41:38 -0400 (EDT) From: dmb To: freebsd-current@FreeBSD.ORG Subject: odd messages 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 After I upgrade to current I get procfs errors when trying to type ps, nothing works, but when I downgrade to 2.2.7-stable everything works fine. Any ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 18 20:07:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04785 for freebsd-current-outgoing; Tue, 18 Aug 1998 20:07:19 -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 UAA04765 for ; Tue, 18 Aug 1998 20:07:12 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id NAA29863; Wed, 19 Aug 1998 13:14:23 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808190314.NAA29863@cimlogic.com.au> Subject: Re: odd messages In-Reply-To: from dmb at "Aug 18, 98 10:41:38 pm" To: nellie@home.com (dmb) Date: Wed, 19 Aug 1998 13:14:22 +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 dmb wrote: > After I upgrade to current I get procfs errors when trying to type ps, > nothing works, but when I downgrade to 2.2.7-stable everything works fine. > Any ideas? What do you mean by "upgrade"? To upgrade to current, build and install a new world, build and install a new kernel, then reboot. It isn't a simple procedure to downgrade a current system to 2.2.7-stable. -- 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 18 21:07:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13192 for freebsd-current-outgoing; Tue, 18 Aug 1998 21:07:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com ([203.8.14.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13185 for ; Tue, 18 Aug 1998 21:06:57 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.hilink.com.au [127.0.0.1] (may be forged)) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA03757 for ; Tue, 18 Aug 1998 21:05:03 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808182105.VAA03757@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Unwanted sig24 problems? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Aug 1998 21:05:03 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG An odd one here; I recently reinstalled -current on my laptop, and with a kernel built this morning I am getting (important) processes killed with SIGXCPU. (eg. the X server). I start the server by hand, and I'm also seeing user processes (emacs, exmh, anything long-lived and busy) dying similarly. dingo:~>limit cputime unlimited filesize unlimited datasize 524288 kbytes stacksize 65536 kbytes coredumpsize unlimited memoryuse 32768 kbytes descriptors 1024 memorylocked unlimited maxproc 64 So I'm fairly happy this isn't a resource configuration problem. Any ideas? (Very irritating this is. 8( ) I managed to reproduce the problem quite quickly with 'top' running with a refresh delay of 0 in an xterm, unfortunately it took the shell with it at about 4 minutes. (Slightly over 4:15, unfortunately). -- \\ 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 18 22:17:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22224 for freebsd-current-outgoing; Tue, 18 Aug 1998 22:17:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ha1.rdc1.pa.home.com (ha1.rdc1.pa.home.com [24.2.5.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22219 for ; Tue, 18 Aug 1998 22:17:48 -0700 (PDT) (envelope-from nellie@home.com) Received: from cc219337-a.lwmrn1.pa.home.com ([24.3.111.2]) by ha1.rdc1.pa.home.com (Netscape Mail Server v2.02) with SMTP id AAA17080 for ; Tue, 18 Aug 1998 22:17:11 -0700 Date: Wed, 19 Aug 1998 01:12:33 -0400 (EDT) From: dmb To: freebsd-current@FreeBSD.ORG Subject: re: odd messages Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG well I cvsup the new source, then cd to /usr/src and make world, all of that ps and stuff should work then like it does in 2.2.7-stable. dunno why it doesn't work with current. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 18 22:30:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23191 for freebsd-current-outgoing; Tue, 18 Aug 1998 22:30:21 -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 WAA23181 for ; Tue, 18 Aug 1998 22:30:17 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id PAA00350; Wed, 19 Aug 1998 15:38:57 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808190538.PAA00350@cimlogic.com.au> Subject: Re: odd messages In-Reply-To: from dmb at "Aug 19, 98 01:12:33 am" To: nellie@home.com (dmb) Date: Wed, 19 Aug 1998 15:38:56 +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 dmb wrote: > well I cvsup the new source, then cd to /usr/src and make world, all of > that ps and stuff should work then like it does in 2.2.7-stable. dunno > why it doesn't work with current. Make world doesn't build a kernel. A -current world won't work too well with a 2.2.7-stable kernel. You shouldn't expect it to. -- 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 19 02:39:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16746 for freebsd-current-outgoing; Wed, 19 Aug 1998 02:39:39 -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 CAA16741 for ; Wed, 19 Aug 1998 02:39:37 -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 KAA22164; Wed, 19 Aug 1998 10:38:53 +0100 (BST) Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.8/8.8.7) id KAA16812; Wed, 19 Aug 1998 10:38:14 +0100 (BST) Message-ID: <19980819103813.A16779@iii.co.uk> Date: Wed, 19 Aug 1998 10:38:13 +0100 To: dmb , freebsd-current@FreeBSD.ORG Subject: Re: odd messages References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from dmb on Wed, Aug 19, 1998 at 01:12:33AM -0400 Organization: interactive investor Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 19, 1998 at 01:12:33AM -0400, dmb wrote: > well I cvsup the new source, then cd to /usr/src and make world, all of > that ps and stuff should work then like it does in 2.2.7-stable. dunno > why it doesn't work with current. Please see the tutorial at for a thorough (some would say 'too thorough') treatment of how to successfully upgrade your system using 'make world'. N -- --+==[ Nik Clayton becomes Just Another Perl Contractor in 24 days. ]==+-- "Pinky, are you pondering what I'm pondering?" "Duh, yeah Brain. But how are we going to get all those computers to crash at the same time?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 05:56:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA05363 for freebsd-current-outgoing; Wed, 19 Aug 1998 05:56:46 -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 FAA05356 for ; Wed, 19 Aug 1998 05:56:44 -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 IAA19016; Wed, 19 Aug 1998 08:57:01 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 19 Aug 1998 08:57:01 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: dmb cc: freebsd-current@FreeBSD.ORG Subject: Re: odd messages 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 have you rebuilt your whole tree? or only the kernel? you should "make world" if you haven't, and by what you're saying it looks like you haven't. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's BSD. -- http://www.freebsd.org/ On Tue, 18 Aug 1998, dmb wrote: > After I upgrade to current I get procfs errors when trying to type ps, > nothing works, but when I downgrade to 2.2.7-stable everything works fine. > Any ideas? > > > > 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 19 06:13:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07727 for freebsd-current-outgoing; Wed, 19 Aug 1998 06:13:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07708; Wed, 19 Aug 1998 06:13:49 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id PAA10187; Wed, 19 Aug 1998 15:03:40 +0200 (CEST) (envelope-from sos) Message-Id: <199808191303.PAA10187@sos.freebsd.dk> Subject: Re: softupdates and smp crash In-Reply-To: <19980818161335.30289@deepo.prosa.dk> from Philippe Regnauld at "Aug 18, 98 04:13:35 pm" To: regnauld@deepo.prosa.dk (Philippe Regnauld) Date: Wed, 19 Aug 1998 15:03:40 +0200 (CEST) Cc: croot@btp1da.phy.uni-bayreuth.de, current@FreeBSD.ORG, smp@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Philippe Regnauld who wrote: > #0 boot (howto=260) at ../../kern/kern_shutdown.c:286 > #1 0xf01151c1 in panic (fmt=0xf01ab861 "softdep_lock: locking against myself") > at ../../kern/kern_shutdown.c:429 > #2 0xf01ab8c9 in acquire_lock (lk=0xf02265ac) > at ../../ufs/ffs/ffs_softdep.c:263 > +-> #3 0xf01aee54 in initiate_write_filepage (pagedep=0xf0c49e00, bp=0xf35300b0) > | at ../../ufs/ffs/ffs_softdep.c:2745 > | #4 0xf01aecbf in softdep_disk_io_initiation (bp=0xf35300b0) > | > I crashed here. I tried it on my play-smp machine it panics also... We can still say for sure that softupdates are NOT SMP safe... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 06:40:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA10999 for freebsd-current-outgoing; Wed, 19 Aug 1998 06:40:32 -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 GAA10986; Wed, 19 Aug 1998 06:40:25 -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 PAA11932; Wed, 19 Aug 1998 15:39:47 +0200 (MEST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199808191303.PAA10187@sos.freebsd.dk> Date: Wed, 19 Aug 1998 15:39:47 +0200 (MEST) Organization: university of bayreuth From: Werner Griessl To: "S\xren Schmidt" Subject: Re: softupdates and smp crash Cc: smp@FreeBSD.ORG, current@FreeBSD.ORG, (Philippe Regnauld) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Aug-98 S\xren Schmidt wrote: > In reply to Philippe Regnauld who wrote: >> #0 boot (howto=260) at ../../kern/kern_shutdown.c:286 >> #1 0xf01151c1 in panic (fmt=0xf01ab861 "softdep_lock: locking against >> #myself") >> at ../../kern/kern_shutdown.c:429 >> #2 0xf01ab8c9 in acquire_lock (lk=0xf02265ac) >> at ../../ufs/ffs/ffs_softdep.c:263 >> +-> #3 0xf01aee54 in initiate_write_filepage (pagedep=0xf0c49e00, >> bp=0xf35300b0) >> | at ../../ufs/ffs/ffs_softdep.c:2745 >> | #4 0xf01aecbf in softdep_disk_io_initiation (bp=0xf35300b0) >> | >> I crashed here. > > > I tried it on my play-smp machine it panics also... > We can still say for sure that softupdates are NOT SMP safe... > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Cor ---------------------------------- E-Mail: Werner Griessl Date: 19-Aug-98 Time: 15:37:25 This message was sent by XFMail ---------------------------------- But with current from today (Aug. 19) i cannot reproduce the crash. Tried 3 times buildworld -j4 with softupdats enabled without problems. Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 06:43:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11997 for freebsd-current-outgoing; Wed, 19 Aug 1998 06:43:49 -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 GAA11980; Wed, 19 Aug 1998 06:43:46 -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 PAA06606; Wed, 19 Aug 1998 15:48:46 +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 PAA00776; Wed, 19 Aug 1998 15:51:25 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id PAA00981; Wed, 19 Aug 1998 15:42:56 +0200 (CEST) Message-ID: <19980819154255.54405@deepo.prosa.dk> Date: Wed, 19 Aug 1998 15:42:55 +0200 From: Philippe Regnauld To: Werner Griessl Cc: Sxren Schmidt , smp@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: softupdates and smp crash References: <199808191303.PAA10187@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from Werner Griessl on Wed, Aug 19, 1998 at 03:39:47PM +0200 X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Werner Griessl writes: > > >> +-> #3 0xf01aee54 in initiate_write_filepage (pagedep=0xf0c49e00, > >> bp=0xf35300b0) > >> | at ../../ufs/ffs/ffs_softdep.c:2745 > >> | #4 0xf01aecbf in softdep_disk_io_initiation (bp=0xf35300b0) > >> | > >> I crashed here. > > > > But with current from today (Aug. 19) i cannot reproduce the crash. > Tried 3 times buildworld -j4 with softupdats enabled without problems. > Werner I also have AHC_TAGENABLE turned on. (no CAM). I will try to turn it off tonight and see. -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 06:46:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12779 for freebsd-current-outgoing; Wed, 19 Aug 1998 06:46:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12769; Wed, 19 Aug 1998 06:46:04 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id PAA10312; Wed, 19 Aug 1998 15:44:19 +0200 (CEST) (envelope-from sos) Message-Id: <199808191344.PAA10312@sos.freebsd.dk> Subject: Re: softupdates and smp crash In-Reply-To: from Werner Griessl at "Aug 19, 98 03:39:47 pm" To: croot@btp1da.phy.uni-bayreuth.de (Werner Griessl) Date: Wed, 19 Aug 1998 15:44:19 +0200 (CEST) Cc: sos@FreeBSD.ORG, smp@FreeBSD.ORG, current@FreeBSD.ORG, regnauld@deepo.prosa.dk From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Werner Griessl who wrote: [lots about smp + softupdates crash] > But with current from today (Aug. 19) i cannot reproduce the crash. > Tried 3 times buildworld -j4 with softupdats enabled without problems. > Werner Hmm, I dont see where this should have been fixed, you should try at least -j8, there it crashed reliably for me, -j4 only crashed now and then. I'll try again tonight with a fresh src tree... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 06:53:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14058 for freebsd-current-outgoing; Wed, 19 Aug 1998 06:53:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14039; Wed, 19 Aug 1998 06:53:15 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id PAA10345; Wed, 19 Aug 1998 15:51:35 +0200 (CEST) (envelope-from sos) Message-Id: <199808191351.PAA10345@sos.freebsd.dk> Subject: Re: softupdates and smp crash In-Reply-To: <19980819154255.54405@deepo.prosa.dk> from Philippe Regnauld at "Aug 19, 98 03:42:55 pm" To: regnauld@deepo.prosa.dk (Philippe Regnauld) Date: Wed, 19 Aug 1998 15:51:35 +0200 (CEST) Cc: croot@btp1da.phy.uni-bayreuth.de, sos@FreeBSD.ORG, smp@FreeBSD.ORG, current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Philippe Regnauld who wrote: > > But with current from today (Aug. 19) i cannot reproduce the crash. > > Tried 3 times buildworld -j4 with softupdats enabled without problems. > > Werner > > I also have AHC_TAGENABLE turned on. (no CAM). I will try to > turn it off tonight and see. Wild shot but not the (total) reason as I run it on an EIDE system and it still crashes.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 06:57:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14840 for freebsd-current-outgoing; Wed, 19 Aug 1998 06:57:32 -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 GAA14776; Wed, 19 Aug 1998 06:57:18 -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 PAA12221; Wed, 19 Aug 1998 15:56:36 +0200 (MEST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199808191344.PAA10312@sos.freebsd.dk> Date: Wed, 19 Aug 1998 15:56:36 +0200 (MEST) Organization: university of bayreuth From: Werner Griessl To: "S\xren Schmidt" Subject: Re: softupdates and smp crash Cc: regnauld@deepo.prosa.dk, current@FreeBSD.ORG, smp@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Aug-98 S\xren Schmidt wrote: > In reply to Werner Griessl who wrote: > > [lots about smp + softupdates crash] > >> But with current from today (Aug. 19) i cannot reproduce the crash. >> Tried 3 times buildworld -j4 with softupdats enabled without problems. >> Werner > > Hmm, I dont see where this should have been fixed, you should try > at least -j8, there it crashed reliably for me, -j4 only crashed > now and then. I'll try again tonight with a fresh src tree... > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end? > .. I'll try -j8 . Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 07:04:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16014 for freebsd-current-outgoing; Wed, 19 Aug 1998 07:04:43 -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 HAA15988; Wed, 19 Aug 1998 07:04:31 -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 QAA12332; Wed, 19 Aug 1998 16:03:51 +0200 (MEST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199808191351.PAA10345@sos.freebsd.dk> Date: Wed, 19 Aug 1998 16:03:51 +0200 (MEST) Organization: university of bayreuth From: Werner Griessl To: "S\xren Schmidt" Subject: Re: softupdates and smp crash Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG, (Philippe Regnauld) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Aug-98 S\xren Schmidt wrote: > In reply to Philippe Regnauld who wrote: >> > But with current from today (Aug. 19) i cannot reproduce the crash. >> > Tried 3 times buildworld -j4 with softupdats enabled without problems. >> > Werner >> >> I also have AHC_TAGENABLE turned on. (no CAM). I will try to >> turn it off tonight and see. > > > Wild shot but not the (total) reason as I run it on an EIDE system > and it still crashes.... > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Cor ---------------------------------- I read from EIDE (/usr/src) and write to SCSI (/usr/obj), ncr810 without AHC_TAGENABLE. Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 07:16:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17842 for freebsd-current-outgoing; Wed, 19 Aug 1998 07:16:48 -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 HAA17810; Wed, 19 Aug 1998 07:16:31 -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 QAA12621; Wed, 19 Aug 1998 16:15:43 +0200 (MEST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199808191344.PAA10312@sos.freebsd.dk> Date: Wed, 19 Aug 1998 16:15:43 +0200 (MEST) Organization: university of bayreuth From: Werner Griessl To: "S\xren Schmidt" Subject: Re: softupdates and smp crash Cc: regnauld@deepo.prosa.dk, current@FreeBSD.ORG, smp@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Aug-98 S\xren Schmidt wrote: > In reply to Werner Griessl who wrote: > > [lots about smp + softupdates crash] > >> But with current from today (Aug. 19) i cannot reproduce the crash. >> Tried 3 times buildworld -j4 with softupdats enabled without problems. >> Werner > > Hmm, I dont see where this should have been fixed, you should try > at least -j8, there it crashed reliably for me, -j4 only crashed > now and then. I'll try again tonight with a fresh src tree... > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Cor ---------------------------------- E-Mail: Werner Griessl Date: 19-Aug-98 Time: 16:14:55 This message was sent by XFMail ---------------------------------- You are right, crash after 10 mins with -j8 ! Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 07:54:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23510 for freebsd-current-outgoing; Wed, 19 Aug 1998 07:54:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23473; Wed, 19 Aug 1998 07:54:30 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id QAA10472; Wed, 19 Aug 1998 16:52:42 +0200 (CEST) (envelope-from sos) Message-Id: <199808191452.QAA10472@sos.freebsd.dk> Subject: Re: softupdates and smp crash In-Reply-To: from Werner Griessl at "Aug 19, 98 04:15:43 pm" To: croot@btp1da.phy.uni-bayreuth.de (Werner Griessl) Date: Wed, 19 Aug 1998 16:52:42 +0200 (CEST) Cc: sos@FreeBSD.ORG, regnauld@deepo.prosa.dk, current@FreeBSD.ORG, smp@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Werner Griessl who wrote: > > > > Hmm, I dont see where this should have been fixed, you should try > > at least -j8, there it crashed reliably for me, -j4 only crashed > > now and then. I'll try again tonight with a fresh src tree... > > > > You are right, crash after 10 mins with -j8 ! > Werner So we can still say that softupdates are broken, at least for SMP. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 08:05:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25401 for freebsd-current-outgoing; Wed, 19 Aug 1998 08:05:59 -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 IAA25371; Wed, 19 Aug 1998 08:05:56 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id LAA05903; Wed, 19 Aug 1998 11:04:33 -0400 (EDT) (envelope-from luoqi) Date: Wed, 19 Aug 1998 11:04:33 -0400 (EDT) From: Luoqi Chen Message-Id: <199808191504.LAA05903@lor.watermarkgroup.com> To: regnauld@deepo.prosa.dk, sos@FreeBSD.ORG Subject: Re: softupdates and smp crash Cc: croot@btp1da.phy.uni-bayreuth.de, current@FreeBSD.ORG, smp@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In reply to Philippe Regnauld who wrote: > > #0 boot (howto=260) at ../../kern/kern_shutdown.c:286 > > #1 0xf01151c1 in panic (fmt=0xf01ab861 "softdep_lock: locking against myself") > > at ../../kern/kern_shutdown.c:429 > > #2 0xf01ab8c9 in acquire_lock (lk=0xf02265ac) > > at ../../ufs/ffs/ffs_softdep.c:263 > > +-> #3 0xf01aee54 in initiate_write_filepage (pagedep=0xf0c49e00, bp=0xf35300b0) > > | at ../../ufs/ffs/ffs_softdep.c:2745 > > | #4 0xf01aecbf in softdep_disk_io_initiation (bp=0xf35300b0) > > | > > I crashed here. > > > I tried it on my play-smp machine it panics also... > We can still say for sure that softupdates are NOT SMP safe... > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end? > .. > There is a race window between a directory entry is removed and dependency for that directory entry is deallocated. The reason that the race window has manifested itself on SMP is that the syncer process is a kernel thread, so we can have two processes both running in kernel mode. The simplest solution for now, IMO, is to make syncer process honor the giant lock. The long term solution is, of course, close those race windows one by one. -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 19 08:32:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02093 for freebsd-current-outgoing; Wed, 19 Aug 1998 08:32:51 -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 IAA02067 for ; Wed, 19 Aug 1998 08:32:41 -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 RAA03012; Wed, 19 Aug 1998 17:31:51 +0200 (MET DST) Received: (from pb@localhost) by mars.hsc.fr (8.8.8/8.8.8/pb-19980526) id RAA21401; Wed, 19 Aug 1998 17:31:50 +0200 (CEST) (envelope-from pb) Message-ID: <19980819173149.A21323@mars.hsc.fr> Date: Wed, 19 Aug 1998 17:31:49 +0200 From: Pierre Beyssac To: Mike Smith , current@FreeBSD.ORG Subject: Re: Unwanted sig24 problems? References: <199808182105.VAA03757@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: <199808182105.VAA03757@dingo.cdrom.com>; from Mike Smith on Tue, Aug 18, 1998 at 09:05:03PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 18, 1998 at 09:05:03PM +0000, Mike Smith wrote: > An odd one here; I recently reinstalled -current on my laptop, and with > a kernel built this morning I am getting (important) processes killed > with SIGXCPU. (eg. the X server). I start the server by hand, and I'm Many (maybe half a dozen) persons have reported similar problems on this list since about June; I'm having it sometimes in make world, and it's not a resource limit problem. I'm running xntpd; somehow it seems the problem occur less frequently when stopping xntpd. I haven't tried recent kernels yet. > So I'm fairly happy this isn't a resource configuration problem. Any > ideas? (Very irritating this is. 8( ) IIRC, it was because the process CPU time becomes negative. Since it's an unsigned integer, it's over even the "unlimited" limit and the process is killed. Nobody seems to know exactly _why_ it becomes negative though. -- 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 Wed Aug 19 10:58:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25074 for freebsd-current-outgoing; Wed, 19 Aug 1998 10:58:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25056; Wed, 19 Aug 1998 10:58:42 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id TAA00646; Wed, 19 Aug 1998 19:57:01 +0200 (CEST) (envelope-from sos) Message-Id: <199808191757.TAA00646@sos.freebsd.dk> Subject: Re: softupdates and smp crash In-Reply-To: <199808191504.LAA05903@lor.watermarkgroup.com> from Luoqi Chen at "Aug 19, 98 11:04:33 am" To: luoqi@watermarkgroup.com (Luoqi Chen) Date: Wed, 19 Aug 1998 19:57:01 +0200 (CEST) Cc: regnauld@deepo.prosa.dk, sos@FreeBSD.ORG, croot@btp1da.phy.uni-bayreuth.de, current@FreeBSD.ORG, smp@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Luoqi Chen who wrote: > There is a race window between a directory entry is removed and dependency > for that directory entry is deallocated. The reason that the race window > has manifested itself on SMP is that the syncer process is a kernel thread, > so we can have two processes both running in kernel mode. The simplest > solution for now, IMO, is to make syncer process honor the giant lock. > The long term solution is, of course, close those race windows one by one. Care to fix it, the giant lock method should be fine for now ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 11:15:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27909 for freebsd-current-outgoing; Wed, 19 Aug 1998 11:15:14 -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 LAA27903 for ; Wed, 19 Aug 1998 11:15:11 -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 OAA22047 for ; Wed, 19 Aug 1998 14:14:28 -0400 (EDT) Received: by mozart (5.65c/SAS/Domains/5-6-90) id AA28841; Wed, 19 Aug 1998 14:14:28 -0400 From: "John W. DeBoskey" Message-Id: <199808191814.AA28841@mozart> Subject: 13 months of user time? To: freebsd-current@FreeBSD.ORG Date: Wed, 19 Aug 1998 14:14:27 -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 folks, I found this on a 3 month old snap, and have now replicated it on 3.0-980818-SNAP. for i in /bin/*; do time rsh nodename uptime done Yields the following output: ..... 2:00PM up 1 day, 1:39, 1 user, load averages: 0.00, 0.00, 0.00 0.19s real 0.00s user 0.00s system 2:00PM up 1 day, 1:39, 1 user, load averages: 0.00, 0.00, 0.00 0.20s real 33554431.00s user 0.00s system 2:00PM up 1 day, 1:39, 1 user, load averages: 0.00, 0.00, 0.00 0.20s real 0.02s user 0.00s system 2:00PM up 1 day, 1:39, 1 user, load averages: 0.00, 0.00, 0.00 0.19s real 0.00s user 0.01s system ..... The values are very consistent until that 13 month value of 33554431.00s user time sneaks in. fyi: The value 33554431 repeats in all occurances of this bug... It seems to be coming from /usr/src/usr.bin/time/time.c: while (wait3(&status, 0, &ru) != pid); /* XXX use waitpid */ It would appear that there is a critter in our resource accounting? Has anyone else seen this problem? Comments? Critiques? Stupid user that can't count? :-) thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 12:31:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14411 for freebsd-current-outgoing; Wed, 19 Aug 1998 12:31:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14391 for ; Wed, 19 Aug 1998 12:31:09 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id FAA23515; Thu, 20 Aug 1998 05:30:30 +1000 Date: Thu, 20 Aug 1998 05:30:30 +1000 From: Bruce Evans Message-Id: <199808191930.FAA23515@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I found this on a 3 month old snap, and have now replicated it >on 3.0-980818-SNAP. > >for i in /bin/*; do > time rsh nodename uptime >done > > Yields the following output: > >..... > 2:00PM up 1 day, 1:39, 1 user, load averages: 0.00, 0.00, 0.00 > 0.19s real 0.00s user 0.00s system > 2:00PM up 1 day, 1:39, 1 user, load averages: 0.00, 0.00, 0.00 > 0.20s real 33554431.00s user 0.00s system This is probably just a symptom of a negative times bug and assorted overflows. This negative times bug usually kills processes with a SIGXCPU. 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 19 13:09:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19796 for freebsd-current-outgoing; Wed, 19 Aug 1998 13:09:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19777 for ; Wed, 19 Aug 1998 13:08:52 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id VAA04654; Wed, 19 Aug 1998 21:08:11 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from localhost by seagoon.gid.co.uk; Wed, 19 Aug 1998 20:52:41 +0100 (BST) Date: Wed, 19 Aug 1998 20:52:40 +0100 (BST) From: Bob Bishop X-Sender: rb@seagoon To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: Unwanted sig24 problems? In-Reply-To: <199808182105.VAA03757@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 Tue, 18 Aug 1998, Mike Smith wrote: > > An odd one here; I recently reinstalled -current on my laptop, and with > a kernel built this morning I am getting (important) processes killed > with SIGXCPU. [etc] I had a few days of spurious sig 24s a couple of months back. It went away... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 14:24:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06552 for freebsd-current-outgoing; Wed, 19 Aug 1998 14:24:19 -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 OAA06535 for ; Wed, 19 Aug 1998 14:24:12 -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 RAA29784; Wed, 19 Aug 1998 17:22:50 -0400 (EDT) Date: Wed, 19 Aug 1998 17:22:50 -0400 (EDT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: Bruce Evans cc: freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-Reply-To: <199808191930.FAA23515@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 It's probably a good idea to get this fixed ASAP, since people have been complaining about this exact bug for months now. Would anyone like to give me any pointers to where to start evaluating the code at, or what functions this could be caused by? I think I'll check the process accounting code first then the actual timing code, if noone has any better ideas. Brian Feldman green@unixhelp.org On Thu, 20 Aug 1998, Bruce Evans wrote: > > I found this on a 3 month old snap, and have now replicated it > >on 3.0-980818-SNAP. > > > >for i in /bin/*; do > > time rsh nodename uptime > >done > > > > Yields the following output: > > > >..... > > 2:00PM up 1 day, 1:39, 1 user, load averages: 0.00, 0.00, 0.00 > > 0.19s real 0.00s user 0.00s system > > 2:00PM up 1 day, 1:39, 1 user, load averages: 0.00, 0.00, 0.00 > > 0.20s real 33554431.00s user 0.00s system > > This is probably just a symptom of a negative times bug and assorted > overflows. This negative times bug usually kills processes with a > SIGXCPU. > > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 14:26:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06905 for freebsd-current-outgoing; Wed, 19 Aug 1998 14:26:05 -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 OAA06900 for ; Wed, 19 Aug 1998 14:26:03 -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 RAA27803 for ; Wed, 19 Aug 1998 17:26:18 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 19 Aug 1998 17:26:18 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: current@FreeBSD.ORG Subject: ping on perl5? 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 someone said that they were almost done with bringing in perl5 to -current. are they done? Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's BSD. -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 14:53:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10320 for freebsd-current-outgoing; Wed, 19 Aug 1998 14:53:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ha1.rdc1.pa.home.com (ha1.rdc1.pa.home.com [24.2.5.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10311 for ; Wed, 19 Aug 1998 14:52:57 -0700 (PDT) (envelope-from nellie@home.com) Received: from cc219337-a.lwmrn1.pa.home.com ([24.3.111.2]) by ha1.rdc1.pa.home.com (Netscape Mail Server v2.02) with SMTP id AAA27708 for ; Wed, 19 Aug 1998 14:52:19 -0700 Date: Wed, 19 Aug 1998 17:47:41 -0400 (EDT) From: dmb To: freebsd-current@FreeBSD.ORG Subject: lock.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 When trying to compile a new kernel after I cvsup and make world and config make depend it fails. The error message is don't know how to make ../../vm/lock.h. Any ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 15:15:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14594 for freebsd-current-outgoing; Wed, 19 Aug 1998 15:15:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp.algonet.se (angel.algonet.se [194.213.74.112]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA14580 for ; Wed, 19 Aug 1998 15:15:36 -0700 (PDT) (envelope-from mal@algonet.se) Received: (qmail 14594 invoked from network); 19 Aug 1998 22:14:57 -0000 Received: from kairos.algonet.se (HELO kairos) (194.213.74.18) by angel.algonet.se with SMTP; 19 Aug 1998 22:14:57 -0000 Received: (mal@localhost) by kairos (SMI-8.6/8.6.12) id AAA29928; Thu, 20 Aug 1998 00:14:56 +0200 Date: Thu, 20 Aug 1998 00:14:56 +0200 Message-Id: <199808192214.AAA29928@kairos> From: Mats Lofkvist To: sos@FreeBSD.ORG CC: croot@btp1da.phy.uni-bayreuth.de, sos@FreeBSD.ORG, regnauld@deepo.prosa.dk, current@FreeBSD.ORG, smp@FreeBSD.ORG In-reply-to: <199808191452.QAA10472@sos.freebsd.dk> Subject: Re: softupdates and smp crash References: <199808191452.QAA10472@sos.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Hmm, I dont see where this should have been fixed, you should try > > at least -j8, there it crashed reliably for me, -j4 only crashed > > now and then. I'll try again tonight with a fresh src tree... > > > > You are right, crash after 10 mins with -j8 ! > Werner So we can still say that softupdates are broken, at least for SMP. Is this a new problem? I'm running current from July 21 on a dual ppro with softupdates and ahc_tagenable and have had no crashes. (I have run a few -j4 buildworlds and just completed a -j8 ditto.) _ Mats Lofkvist mal@algonet.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 15:29:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16795 for freebsd-current-outgoing; Wed, 19 Aug 1998 15:29:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com ([208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16774 for ; Wed, 19 Aug 1998 15:29:43 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-120.camalott.com [208.229.74.120]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id RAA06835; Wed, 19 Aug 1998 17:28:45 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id RAA14669; Wed, 19 Aug 1998 17:27:06 -0500 (CDT) (envelope-from joelh) Date: Wed, 19 Aug 1998 17:27:06 -0500 (CDT) Message-Id: <199808192227.RAA14669@detlev.UUCP> To: nellie@home.com CC: freebsd-current@FreeBSD.ORG In-reply-to: (message from dmb on Wed, 19 Aug 1998 01:12:33 -0400 (EDT)) Subject: Re: odd messages From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > well I cvsup the new source, then cd to /usr/src and make world, all of > that ps and stuff should work then like it does in 2.2.7-stable. dunno > why it doesn't work with current. You need to rebuild your kernel. 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 19 16:37:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29287 for freebsd-current-outgoing; Wed, 19 Aug 1998 16:37:54 -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 QAA29259 for ; Wed, 19 Aug 1998 16:37:43 -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 QAA03487; Wed, 19 Aug 1998 16:35:15 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808191635.QAA03487@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Pierre Beyssac cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Unwanted sig24 problems? In-reply-to: Your message of "Wed, 19 Aug 1998 17:31:49 +0200." <19980819173149.A21323@mars.hsc.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Aug 1998 16:35:14 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, Aug 18, 1998 at 09:05:03PM +0000, Mike Smith wrote: > > An odd one here; I recently reinstalled -current on my laptop, and with > > a kernel built this morning I am getting (important) processes killed > > with SIGXCPU. (eg. the X server). I start the server by hand, and I'm > > Many (maybe half a dozen) persons have reported similar problems > on this list since about June; I'm having it sometimes in make > world, and it's not a resource limit problem. I'm running xntpd; > somehow it seems the problem occur less frequently when stopping > xntpd. I haven't tried recent kernels yet. > > > So I'm fairly happy this isn't a resource configuration problem. Any > > ideas? (Very irritating this is. 8( ) > > IIRC, it was because the process CPU time becomes negative. Since > it's an unsigned integer, it's over even the "unlimited" limit and > the process is killed. Nobody seems to know exactly _why_ it becomes > negative though. Ah. This sounds like the 'calcru: negative...' message. Looks like Poul has some more work to do still. -- \\ 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 19 16:48:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01372 for freebsd-current-outgoing; Wed, 19 Aug 1998 16:48:15 -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 QAA01340 for ; Wed, 19 Aug 1998 16:48:05 -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 QAA03559; Wed, 19 Aug 1998 16:45:37 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808191645.QAA03559@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: Bruce Evans , freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Wed, 19 Aug 1998 17:22:50 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Aug 1998 16:45:36 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At a guess, it's either in or related to this fragment from kern/kern_synch.c: /* * Compute the amount of time during which the current * process was running, and add that to its total so far. */ microuptime(&switchtime); p->p_runtime += (switchtime.tv_usec - p->p_switchtime.tv_usec) + (switchtime.tv_sec - p->p_switchtime.tv_sec) * (int64_t)1000000; Either microuptime() is returning garbage, or the calculation is bogus. > It's probably a good idea to get this fixed ASAP, since people have been > complaining about this exact bug for months now. Would anyone like to give > me any pointers to where to start evaluating the code at, or what > functions this could be caused by? I think I'll check the process > accounting code first then the actual timing code, if noone has any better > ideas. > > Brian Feldman > green@unixhelp.org > > On Thu, 20 Aug 1998, Bruce Evans wrote: > > > > I found this on a 3 month old snap, and have now replicated it > > >on 3.0-980818-SNAP. > > > > > >for i in /bin/*; do > > > time rsh nodename uptime > > >done > > > > > > Yields the following output: > > > > > >..... > > > 2:00PM up 1 day, 1:39, 1 user, load averages: 0.00, 0.00, 0.00 > > > 0.19s real 0.00s user 0.00s system > > > 2:00PM up 1 day, 1:39, 1 user, load averages: 0.00, 0.00, 0.00 > > > 0.20s real 33554431.00s user 0.00s system > > > > This is probably just a symptom of a negative times bug and assorted > > overflows. This negative times bug usually kills processes with a > > SIGXCPU. > > > > Bruce > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ 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 19 18:01:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13698 for freebsd-current-outgoing; Wed, 19 Aug 1998 18:01:12 -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 SAA13683; Wed, 19 Aug 1998 18:01:04 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id SAA15261; Wed, 19 Aug 1998 18:00:26 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd015210; Wed Aug 19 18:00:21 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id SAA01161; Wed, 19 Aug 1998 18:00:17 -0700 (MST) From: Terry Lambert Message-Id: <199808200100.SAA01161@usr05.primenet.com> Subject: Re: softupdates and smp crash To: sos@FreeBSD.ORG Date: Thu, 20 Aug 1998 01:00:17 +0000 (GMT) Cc: croot@btp1da.phy.uni-bayreuth.de, regnauld@deepo.prosa.dk, current@FreeBSD.ORG, smp@FreeBSD.ORG In-Reply-To: <199808191452.QAA10472@sos.freebsd.dk> from "S?ren Schmidt" at Aug 19, 98 04:52:42 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 > > You are right, crash after 10 mins with -j8 ! > > Werner > > So we can still say that softupdates are broken, at least for SMP. It would be more useful (than saying this) for people to characterize the problem they are getting so that we can find a discriminitory value. I suggest: Result: crash/stable Disk1: IDE/EIDE/SCSI Disk2: IDE/EIDE/SCSI ... DiskN: IDE/EIDE/SCSI CAM: Yes/No AHC_TAGENABLE: Yes/No /tmp is MFS Yes/No Processor: Pentium/P2/etc. SMP BIOS: 1.1/1.4 APIC INT: Yes/No Motherboard: ASUS/Compaq/HP/etc. I also suggest using the SMP list for this instead of -current. 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 19 18:13:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16180 for freebsd-current-outgoing; Wed, 19 Aug 1998 18:13:53 -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 SAA16170 for ; Wed, 19 Aug 1998 18:13:48 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id SAA01057; Wed, 19 Aug 1998 18:13:07 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpd001026; Wed Aug 19 18:13:01 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id SAA01826; Wed, 19 Aug 1998 18:12:48 -0700 (MST) From: Terry Lambert Message-Id: <199808200112.SAA01826@usr05.primenet.com> Subject: Re: 13 months of user time? To: green@unixhelp.org (Brian Feldman) Date: Thu, 20 Aug 1998 01:12:47 +0000 (GMT) Cc: bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com In-Reply-To: from "Brian Feldman" at Aug 19, 98 05:22:50 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's probably a good idea to get this fixed ASAP, since people have been > complaining about this exact bug for months now. Would anyone like to give > me any pointers to where to start evaluating the code at, or what > functions this could be caused by? I think I'll check the process > accounting code first then the actual timing code, if noone has any better > ideas. My suggestion would be to implement this timing using a monoclock. A monoclock monotonically increases; that is, it *never* goes backward. A monoclock *can* have it's ticks accelerated (or delayed) to sync it to a timebase, but this is not really necessary. If the system clock never went backwards (ie: adjtime(2) did not cause the system clock to be modified, but instead scheduled a delay or an acceleration), then you could never have negative wall values, and you would never have this bug. The merits of using gettimeofday(2)/settimeofday(2) to modify the system clock rather than a derived wall clock based on a monoclock are debateable; the calculation is not that high an overhead. It is an error for the struct timeval member, the long value "tv_sec", to be equated with time_t. 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 19 20:01:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA28819 for freebsd-current-outgoing; Wed, 19 Aug 1998 20:01:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA28793 for ; Wed, 19 Aug 1998 20:01:05 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA17907; Wed, 19 Aug 1998 22:54:10 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199808192154.WAA17907@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: Unwanted sig24 problems? In-reply-to: Your message of "Tue, 18 Aug 1998 21:05:03 -0000." <199808182105.VAA03757@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Aug 1998 22:54:08 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The only way this can be happening AFAICT is if the value pointed at by the global ``timecounter'' is fluctuating (going backwards).... Does making ``struct timecounter *timecounter'' volatile in kern_clock.c help ? I can't tell 'cos the machine that I got this problem with was given back.... > An odd one here; I recently reinstalled -current on my laptop, and with > a kernel built this morning I am getting (important) processes killed > with SIGXCPU. (eg. the X server). I start the server by hand, and I'm > also seeing user processes (emacs, exmh, anything long-lived and busy) > dying similarly. > > dingo:~>limit > cputime unlimited > filesize unlimited > datasize 524288 kbytes > stacksize 65536 kbytes > coredumpsize unlimited > memoryuse 32768 kbytes > descriptors 1024 > memorylocked unlimited > maxproc 64 > > So I'm fairly happy this isn't a resource configuration problem. Any > ideas? (Very irritating this is. 8( ) > > I managed to reproduce the problem quite quickly with 'top' running > with a refresh delay of 0 in an xterm, unfortunately it took the shell > with it at about 4 minutes. (Slightly over 4:15, unfortunately). > > -- > \\ 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 -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 21:18:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10868 for freebsd-current-outgoing; Wed, 19 Aug 1998 21:18:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA10841 for ; Wed, 19 Aug 1998 21:18:40 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id GAA02264; Thu, 20 Aug 1998 06:14:21 +0200 (CEST) To: Terry Lambert cc: green@unixhelp.org (Brian Feldman), bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Thu, 20 Aug 1998 01:12:47 -0000." <199808200112.SAA01826@usr05.primenet.com> Date: Thu, 20 Aug 1998 06:14:21 +0200 Message-ID: <2262.903586461@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808200112.SAA01826@usr05.primenet.com>, Terry Lambert writes: >> It's probably a good idea to get this fixed ASAP, since people have been >> complaining about this exact bug for months now. Would anyone like to give >> me any pointers to where to start evaluating the code at, or what >> functions this could be caused by? I think I'll check the process >> accounting code first then the actual timing code, if noone has any better >> ideas. > >My suggestion would be to implement this timing using a monoclock. I fully agree, great idea Terry! We've had that for several months already :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 21:37:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13277 for freebsd-current-outgoing; Wed, 19 Aug 1998 21:37:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13264 for ; Wed, 19 Aug 1998 21:37:04 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id GAA02328; Thu, 20 Aug 1998 06:30:07 +0200 (CEST) To: Brian Somers cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Unwanted sig24 problems? In-reply-to: Your message of "Wed, 19 Aug 1998 22:54:08 BST." <199808192154.WAA17907@awfulhak.org> Date: Thu, 20 Aug 1998 06:30:06 +0200 Message-ID: <2326.903587406@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808192154.WAA17907@awfulhak.org>, Brian Somers writes: >The only way this can be happening AFAICT is if the value pointed at >by the global ``timecounter'' is fluctuating (going backwards).... It doesn't. >Does making ``struct timecounter *timecounter'' volatile in >kern_clock.c help ? I can't tell 'cos the machine that I got this >problem with was given back.... I doubt it, if you look at how it is used you will see why. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 21:50:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15117 for freebsd-current-outgoing; Wed, 19 Aug 1998 21:50:57 -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 VAA15103 for ; Wed, 19 Aug 1998 21:50:55 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id VAA24246; Wed, 19 Aug 1998 21:50:15 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd024229; Wed Aug 19 21:50:11 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id VAA13354; Wed, 19 Aug 1998 21:50:06 -0700 (MST) From: Terry Lambert Message-Id: <199808200450.VAA13354@usr02.primenet.com> Subject: Re: 13 months of user time? To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Thu, 20 Aug 1998 04:50:05 +0000 (GMT) Cc: tlambert@primenet.com, green@unixhelp.org, bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com In-Reply-To: <2262.903586461@critter.freebsd.dk> from "Poul-Henning Kamp" at Aug 20, 98 06:14:21 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> It's probably a good idea to get this fixed ASAP, since people have been > >> complaining about this exact bug for months now. Would anyone like to give > >> me any pointers to where to start evaluating the code at, or what > >> functions this could be caused by? I think I'll check the process > >> accounting code first then the actual timing code, if noone has any better > >> ideas. > > > >My suggestion would be to implement this timing using a monoclock. > > I fully agree, great idea Terry! > > We've had that for several months already :-) Cool! We can mark this bug resolved, then! 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 21:52:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15500 for freebsd-current-outgoing; Wed, 19 Aug 1998 21:52:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15377; Wed, 19 Aug 1998 21:51:59 -0700 (PDT) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (root@shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.8.8/8.8.8) with ESMTP id IAA16535; Thu, 20 Aug 1998 08:51:12 +0400 (MSD) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (tarkhil@minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.8/8.8.7) with ESMTP id IAA09338; Thu, 20 Aug 1998 08:51:40 +0400 (MSD) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199808200451.IAA09338@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: questions@FreeBSD.ORG Cc: current@FreeBSD.ORG Reply-To: tarkhil@asteroid.svib.ru Subject: Stupid problem X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit From: Alex Povolotsky Date: Thu, 20 Aug 1998 08:51:38 +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! As far as I know, x11 subtree in ports in being reorganized. I cvsup ports regularry, and for some time lots of ports are removed from x11, but NOTHING appears at x11-*. I use cvsup-mirror at my server, and in cvs repository everything is OK. Attempt to cvsup or cvs ports tree doesn't result in x11-* creation :-( Alex. -- Alexander B. Povolotsky [2:5020/145] [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru] [Urgent messages: 234-9696 ÁÂ.#35442 or tarkhil@pager.express.ru] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 21:52:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15580 for freebsd-current-outgoing; Wed, 19 Aug 1998 21:52:30 -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 VAA15555 for ; Wed, 19 Aug 1998 21:52:26 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id VAA06280; Wed, 19 Aug 1998 21:51:39 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd006203; Wed Aug 19 21:51:31 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id VAA13481; Wed, 19 Aug 1998 21:51:25 -0700 (MST) From: Terry Lambert Message-Id: <199808200451.VAA13481@usr02.primenet.com> Subject: Re: 13 months of user time? To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Thu, 20 Aug 1998 04:51:25 +0000 (GMT) Cc: tlambert@primenet.com, green@unixhelp.org, bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com In-Reply-To: <2262.903586461@critter.freebsd.dk> from "Poul-Henning Kamp" at Aug 20, 98 06:14:21 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> It's probably a good idea to get this fixed ASAP, since people have been > >> complaining about this exact bug for months now. Would anyone like to give > >> me any pointers to where to start evaluating the code at, or what > >> functions this could be caused by? I think I'll check the process > >> accounting code first then the actual timing code, if noone has any better > >> ideas. > > > >My suggestion would be to implement this timing using a monoclock. > > I fully agree, great idea Terry! > > We've had that for several months already :-) Cool! Then we can mark this bug resolved! 8-). (Sorry if this is a duplicate; I got a SIG24 in the middle of my send because my "monoclock" went backwards during a monotomic increase...) 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 19 23:02:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25578 for freebsd-current-outgoing; Wed, 19 Aug 1998 23:02:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (obelix.trw.nl [195.193.64.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25569 for ; Wed, 19 Aug 1998 23:02:44 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id HAA00536; Thu, 20 Aug 1998 07:58:35 +0200 (CEST) To: Terry Lambert cc: green@unixhelp.org, bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Thu, 20 Aug 1998 04:51:25 -0000." <199808200451.VAA13481@usr02.primenet.com> Date: Thu, 20 Aug 1998 07:58:34 +0200 Message-ID: <534.903592714@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808200451.VAA13481@usr02.primenet.com>, Terry Lambert writes: >> >> It's probably a good idea to get this fixed ASAP, since people have been >> >> complaining about this exact bug for months now. Would anyone like to give >> >> me any pointers to where to start evaluating the code at, or what >> >> functions this could be caused by? I think I'll check the process >> >> accounting code first then the actual timing code, if noone has any better >> >> ideas. >> > >> >My suggestion would be to implement this timing using a monoclock. >> >> I fully agree, great idea Terry! >> >> We've had that for several months already :-) > >Cool! Then we can mark this bug resolved! 8-). No, we can mark your diagnosis as wrong. :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 23:11:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27904 for freebsd-current-outgoing; Wed, 19 Aug 1998 23:11: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 XAA27898 for ; Wed, 19 Aug 1998 23:11:45 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:7nl4kTrmho8wVwFIF90y/0MYOdMC8mBL@localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id IAA01711; Thu, 20 Aug 1998 08:10:29 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199808200610.IAA01711@gratis.grondar.za> To: Alfred Perlstein cc: current@FreeBSD.ORG Subject: Re: ping on perl5? Date: Thu, 20 Aug 1998 08:10:27 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > someone said that they were almost done with bringing in perl5 to > -current. > > are they done? Me. I'm working on it. 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 Wed Aug 19 23:14:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28549 for freebsd-current-outgoing; Wed, 19 Aug 1998 23:14:26 -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 XAA28541 for ; Wed, 19 Aug 1998 23:14:22 -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 CAA25275; Thu, 20 Aug 1998 02:08:08 -0400 (EDT) Date: Thu, 20 Aug 1998 02:08:08 -0400 (EDT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: Poul-Henning Kamp cc: Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-Reply-To: <534.903592714@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, how about we try out Mike's idea? Someone who experiences the SIGXCPU kill problem could try putting the following in kern/kern_synch.c line 638: if (switchtime.tv_usec < p->p_switchtime.tv_usec || switchtime.tv_sec < p->p_switchtime.tv_sec) panic("bogus microuptime twiddling"); And see if we get some nice panics and cores. Is it worth a shot? I've never gotten a SIGXCPU out of place, so my machine wouldn't be the one to test this on. Cheers, Brian Feldman green@unixhelp.org On Thu, 20 Aug 1998, Poul-Henning Kamp wrote: > In message <199808200451.VAA13481@usr02.primenet.com>, Terry Lambert writes: > >> >> It's probably a good idea to get this fixed ASAP, since people have been > >> >> complaining about this exact bug for months now. Would anyone like to give > >> >> me any pointers to where to start evaluating the code at, or what > >> >> functions this could be caused by? I think I'll check the process > >> >> accounting code first then the actual timing code, if noone has any better > >> >> ideas. > >> > > >> >My suggestion would be to implement this timing using a monoclock. > >> > >> I fully agree, great idea Terry! > >> > >> We've had that for several months already :-) > > > >Cool! Then we can mark this bug resolved! 8-). > > No, we can mark your diagnosis as wrong. :-) > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 23:31:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01187 for freebsd-current-outgoing; Wed, 19 Aug 1998 23:31:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01166; Wed, 19 Aug 1998 23:31:22 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.8.8) id IAA02030; Thu, 20 Aug 1998 08:29:44 +0200 (CEST) (envelope-from sos) Message-Id: <199808200629.IAA02030@sos.freebsd.dk> Subject: Re: softupdates and smp crash In-Reply-To: <199808200100.SAA01161@usr05.primenet.com> from Terry Lambert at "Aug 20, 98 01:00:17 am" To: tlambert@primenet.com (Terry Lambert) Date: Thu, 20 Aug 1998 08:29:44 +0200 (CEST) Cc: sos@FreeBSD.ORG, croot@btp1da.phy.uni-bayreuth.de, regnauld@deepo.prosa.dk, current@FreeBSD.ORG, smp@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Terry Lambert who wrote: > > > You are right, crash after 10 mins with -j8 ! > > > Werner > > > > So we can still say that softupdates are broken, at least for SMP. > > It would be more useful (than saying this) for people to characterize > the problem they are getting so that we can find a discriminitory > value. I suggest: I suggest reading Luoqi Chen's exelent explanation as why it breaks under SMP (hint: it has nothing todo with HW setups).. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 19 23:35:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01638 for freebsd-current-outgoing; Wed, 19 Aug 1998 23:35:10 -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 XAA01633 for ; Wed, 19 Aug 1998 23:35:07 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id XAA07008; Wed, 19 Aug 1998 23:34:27 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd006965; Wed Aug 19 23:34:20 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id XAA17678; Wed, 19 Aug 1998 23:34:15 -0700 (MST) From: Terry Lambert Message-Id: <199808200634.XAA17678@usr02.primenet.com> Subject: Re: 13 months of user time? To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Thu, 20 Aug 1998 06:34:15 +0000 (GMT) Cc: tlambert@primenet.com, green@unixhelp.org, bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com In-Reply-To: <534.903592714@critter.freebsd.dk> from "Poul-Henning Kamp" at Aug 20, 98 07:58:34 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 > >> We've had that for several months already :-) > > > >Cool! Then we can mark this bug resolved! 8-). > > No, we can mark your diagnosis as wrong. :-) I didn't diagnose this as the cause of the SIG-24. I only stated what was necessary to prevent a retrograde clock, which was being blamed for the SIG-24. 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 19 23:42:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02636 for freebsd-current-outgoing; Wed, 19 Aug 1998 23:42:51 -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 XAA02627; Wed, 19 Aug 1998 23:42:47 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id XAA08274; Wed, 19 Aug 1998 23:42:09 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd008231; Wed Aug 19 23:42:02 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id XAA18028; Wed, 19 Aug 1998 23:41:54 -0700 (MST) From: Terry Lambert Message-Id: <199808200641.XAA18028@usr02.primenet.com> Subject: Re: softupdates and smp crash To: sos@FreeBSD.ORG Date: Thu, 20 Aug 1998 06:41:53 +0000 (GMT) Cc: tlambert@primenet.com, croot@btp1da.phy.uni-bayreuth.de, regnauld@deepo.prosa.dk, current@FreeBSD.ORG, smp@FreeBSD.ORG In-Reply-To: <199808200629.IAA02030@sos.freebsd.dk> from "S?ren Schmidt" at Aug 20, 98 08:29:44 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > So we can still say that softupdates are broken, at least for SMP. > > > > It would be more useful (than saying this) for people to characterize > > the problem they are getting so that we can find a discriminitory > > value. I suggest: > > I suggest reading Luoqi Chen's exelent explanation as why it breaks > under SMP (hint: it has nothing todo with HW setups).. Perhaps clock speed? 8-). His post arrived in my mailbox after I responded to your post... I'm also not convinced that this is the only possible cause of the problem; the VM code is hardly "assert" protected everywhere, so diagnosing this thing is not trivial. Look at the VM fixes I recently did, which killed the bugs Karl Denniger was seeing in 75% of the cases, leaving 25% of the cases "clustered" (in his words), indicating a seperate problem, in addition to the ones I fixed, in a periodically executing code path. I had suspected that this would be the case when I made the fix, since it doesn't account for the buggy behaviour I'm personally seeing. 8-(. I myself haven't seen the problems described on my dual P90 system. I suspect the people seeing the bug Luoqi pointed to have very fast processors in order to have one "win" the race. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 20 01:59:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19491 for freebsd-current-outgoing; Thu, 20 Aug 1998 01:59:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19485; Thu, 20 Aug 1998 01:59:32 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id EAA11979; Thu, 20 Aug 1998 04:55:22 -0400 (EDT) From: Peter Dufault Message-Id: <199808200855.EAA11979@hda.hda.com> Subject: Re: cvs commit: src/sys/kern subr_xxx.c src/sys/scsi su.c src/sys/sys conf.h In-Reply-To: <199808200610.XAA29119@freefall.freebsd.org> from Bruce Evans at "Aug 19, 98 11:10:42 pm" To: bde@FreeBSD.ORG (Bruce Evans) Date: Thu, 20 Aug 1998 04:55:21 -0400 (EDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (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 > bde 1998/08/19 23:10:42 PDT > > Modified files: > sys/kern subr_xxx.c > sys/scsi su.c > sys/sys conf.h > Log: > Moved `nx' functions to the one place where they are used (su.c). > They shouldn't be used there either. They should have gone away > about 3 years ago when the statically initialized devswitches went > away, but su.c unfortunately still frobs the cdevswitch in the old > way. "su" should go away in -current. The reason for it was quick and dirty fixed SCSI targets before I put in the wire-down code and the "uk" device. Anyone who notices it goes away will have an easy time to change to a wired down device, and it will serve as a heads up to them for work they have to do in the CAM cutover. Does anyone disagree? Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 20 02:02:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20129 for freebsd-current-outgoing; Thu, 20 Aug 1998 02:02:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from atena.eurocontrol.fr (atena.uneec.eurocontrol.fr [147.196.69.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20043 for ; Thu, 20 Aug 1998 02:02:10 -0700 (PDT) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.30.193]) by atena.eurocontrol.fr (8.9.1/8.9.1/atena-1.1/nospam) with ESMTP id LAA15761 for ; Thu, 20 Aug 1998 11:01:28 +0200 (MET DST) (envelope-from roberto@caerdonn.eurocontrol.fr) Received: by caerdonn.eurocontrol.fr (VMailer, from userid 1193) id 3178CDF; Thu, 20 Aug 1998 11:01:26 +0200 (CEST) Message-ID: <19980820110125.A17863@caerdonn.eurocontrol.fr> Date: Thu, 20 Aug 1998 11:01:25 +0200 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Problem with Poul-Henning's commit in /etc/rc Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.1i X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Unless I'm mistaken, the latest change from Poul-Henning to /etc/rc is bad because failures are not detected anymore. The $? check is now after the "echo" and will check its return code, not the one from mount. Index: rc =================================================================== RCS file: /home/ncvs/src/etc/rc,v retrieving revision 1.148 retrieving revision 1.149 diff -u -2 -u -r1.148 -r1.149 --- rc 1998/08/10 19:53:50 1.148 +++ rc 1998/08/14 06:49:05 1.149 @@ -77,5 +77,7 @@ umount -a >/dev/null 2>&1 +echo -n "Mounting NFS file systems" mount -a -t nonfs +echo . if [ $? != 0 ]; then echo "Filesystem mount failed, startup aborted" -- Ollivier ROBERT -=- Eurocontrol EEC/TS -=- Ollivier.Robert@eurocontrol.fr FreeBSD caerdonn.eurocontrol.fr 3.0-CURRENT #5: Tue Apr 22 14:57:00 CEST 1997 roberto@caerdonn.eurocontrol.fr:/src/src/sys/compile/CAERDONN2 i386 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 20 02:28:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23222 for freebsd-current-outgoing; Thu, 20 Aug 1998 02:28:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (obelix.trw.nl [195.193.64.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23216 for ; Thu, 20 Aug 1998 02:28:12 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id LAA01272; Thu, 20 Aug 1998 11:23:50 +0200 (CEST) To: Ollivier Robert cc: "FreeBSD Current Users' list" Subject: Re: Problem with Poul-Henning's commit in /etc/rc In-reply-to: Your message of "Thu, 20 Aug 1998 11:01:25 +0200." <19980820110125.A17863@caerdonn.eurocontrol.fr> Date: Thu, 20 Aug 1998 11:23:48 +0200 Message-ID: <1270.903605028@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG you're right... In message <19980820110125.A17863@caerdonn.eurocontrol.fr>, Ollivier Robert wri tes: >Unless I'm mistaken, the latest change from Poul-Henning to /etc/rc is bad >because failures are not detected anymore. The $? check is now after the >"echo" and will check its return code, not the one from mount. > >Index: rc >=================================================================== >RCS file: /home/ncvs/src/etc/rc,v >retrieving revision 1.148 >retrieving revision 1.149 >diff -u -2 -u -r1.148 -r1.149 >--- rc 1998/08/10 19:53:50 1.148 >+++ rc 1998/08/14 06:49:05 1.149 >@@ -77,5 +77,7 @@ > umount -a >/dev/null 2>&1 > >+echo -n "Mounting NFS file systems" > mount -a -t nonfs >+echo . > if [ $? != 0 ]; then > echo "Filesystem mount failed, startup aborted" > >-- >Ollivier ROBERT -=- Eurocontrol EEC/TS -=- Ollivier.Robert@eurocontrol.fr >FreeBSD caerdonn.eurocontrol.fr 3.0-CURRENT #5: Tue Apr 22 14:57:00 CEST 1997 >roberto@caerdonn.eurocontrol.fr:/src/src/sys/compile/CAERDONN2 i386 > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 20 02:31:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23658 for freebsd-current-outgoing; Thu, 20 Aug 1998 02:31:31 -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 CAA23653 for ; Thu, 20 Aug 1998 02:31:30 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca10-63.ix.netcom.com [205.186.214.63]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id CAA11327; Thu, 20 Aug 1998 02:30:46 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id CAA04533; Thu, 20 Aug 1998 02:30:42 -0700 (PDT) Date: Thu, 20 Aug 1998 02:30:42 -0700 (PDT) Message-Id: <199808200930.CAA04533@silvia.hip.berkeley.edu> To: roberto@eurocontrol.fr CC: freebsd-current@FreeBSD.ORG In-reply-to: <19980820110125.A17863@caerdonn.eurocontrol.fr> (message from Ollivier Robert on Thu, 20 Aug 1998 11:01:25 +0200) Subject: Re: Problem with Poul-Henning's commit in /etc/rc From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Unless I'm mistaken, the latest change from Poul-Henning to /etc/rc is bad * because failures are not detected anymore. The $? check is now after the * "echo" and will check its return code, not the one from mount. * +echo -n "Mounting NFS file systems" * mount -a -t nonfs * +echo . * if [ $? != 0 ]; then * echo "Filesystem mount failed, startup aborted" Besides, the messages are all wrong. It says NFS when it's mounting non-NFS filesystems (which is one word, btw), and if it fails (it won't, but even if the second echo is taken out), the screen will read "Mounting NFS file systemsFilesystem mount failed, startup aborted" ;) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 20 02:53:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA25862 for freebsd-current-outgoing; Thu, 20 Aug 1998 02:53:15 -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 CAA25857 for ; Thu, 20 Aug 1998 02:53:12 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA21251; Thu, 20 Aug 1998 19:52:33 +1000 Date: Thu, 20 Aug 1998 19:52:33 +1000 From: Bruce Evans Message-Id: <199808200952.TAA21251@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, roberto@eurocontrol.fr Subject: Re: Problem with Poul-Henning's commit in /etc/rc Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Unless I'm mistaken, the latest change from Poul-Henning to /etc/rc is bad >because failures are not detected anymore. The $? check is now after the >"echo" and will check its return code, not the one from mount. Another point on the hat: the echoes are attached to the wrong mount command. There is no error checking for the nfs mount, so the echoes wouldn't harm the status if they were correctly placed. Bruce >Index: rc >=================================================================== >RCS file: /home/ncvs/src/etc/rc,v >retrieving revision 1.148 >retrieving revision 1.149 >diff -u -2 -u -r1.148 -r1.149 >--- rc 1998/08/10 19:53:50 1.148 >+++ rc 1998/08/14 06:49:05 1.149 >@@ -77,5 +77,7 @@ > umount -a >/dev/null 2>&1 > >+echo -n "Mounting NFS file systems" > mount -a -t nonfs >+echo . > if [ $? != 0 ]; then > echo "Filesystem mount failed, startup aborted" > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 20 06:15:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13730 for freebsd-current-outgoing; Thu, 20 Aug 1998 06:15:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gimli.cs.uct.ac.za (gimli.cs.uct.ac.za [137.158.128.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13704; Thu, 20 Aug 1998 06:15:37 -0700 (PDT) (envelope-from mwest@gimli.cs.uct.ac.za) Received: from mwest (helo=localhost) by gimli.cs.uct.ac.za with local-smtp (Exim 1.92 #1) id 0z9URZ-0001N1-00; Thu, 20 Aug 1998 15:07:57 +0200 Date: Thu, 20 Aug 1998 15:07:57 +0200 (SAST) From: Matthew West To: Alex Povolotsky cc: questions@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Stupid problem In-Reply-To: <199808200451.IAA09338@minas-tirith.pol.ru> 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, 20 Aug 1998, Alex Povolotsky wrote: > As far as I know, x11 subtree in ports in being reorganized. I cvsup > ports regularry, and for some time lots of ports are removed from x11, but > NOTHING appears at x11-*. Are you _sure_ you have ports-all in your supfile, as opposed to a list of the individual collections? If the later is the case, you just need to add in the new x11-* collections to the list. --mwest@cs.uct.ac.za http://www.cs.uct.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 20 08:49:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29858 for freebsd-current-outgoing; Thu, 20 Aug 1998 08:49:12 -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 IAA29853 for ; Thu, 20 Aug 1998 08:49:10 -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 LAA00698; Thu, 20 Aug 1998 11:48:03 -0400 (EDT) Date: Thu, 20 Aug 1998 11:48:02 -0400 (EDT) From: Brian Tao X-Sender: taob@tor-dev1.nbc.netcom.ca To: FREEBSD-CURRENT Subject: Whereabouts of mount_msdos(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 What's the decision on mount_msdos and /usr/src/sbin/i386? It looks like the buildworld target stopped looking at that directory on August 15, but mount_msdos is still in there. Recent -current snapshots don't have mount_msdos anymore. Wasn't the plan to move mount_msdos out of the i386/ subdirectory anyway? -- 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 20 10:05:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12750 for freebsd-current-outgoing; Thu, 20 Aug 1998 10:05:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12743 for ; Thu, 20 Aug 1998 10:05:29 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id KAA20074; Thu, 20 Aug 1998 10:04:46 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 20 Aug 1998 10:04:46 -0700 (PDT) From: Doug White To: dmb cc: freebsd-current@FreeBSD.ORG Subject: Re: lock.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 Wed, 19 Aug 1998, dmb wrote: > When trying to compile a new kernel after I cvsup and make world and > config make depend it fails. The error message is don't know how to make > ../../vm/lock.h. Any ideas? The usual way to deal with thiese things is to: 1. Try 'make clean' before 'make depend'. 2. Re-checkout your kernel source. I'd try this but my current box is hosed (#@#*(& Toshiba &@$#% Micropolis). Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 20 13:31:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18197 for freebsd-current-outgoing; Thu, 20 Aug 1998 13:31:10 -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 NAA18184 for ; Thu, 20 Aug 1998 13:31: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 QAA25462 for ; Thu, 20 Aug 1998 16:30:22 -0400 (EDT) Received: by mozart (5.65c/SAS/Domains/5-6-90) id AA26024; Thu, 20 Aug 1998 16:30:22 -0400 From: "John W. DeBoskey" Message-Id: <199808202030.AA26024@mozart> Subject: Intel PRO/1000 Gigabit Adapter To: freebsd-current@FreeBSD.ORG Date: Thu, 20 Aug 1998 16:30:22 -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, Has anyone done any work with the Intel PRO/1000 Gigabit network adapter? It id's as Vendor: 0x8086 Device: 0x1000 If so, I'd like to help. If not, 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 Thu Aug 20 13:38:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19789 for freebsd-current-outgoing; Thu, 20 Aug 1998 13:38:54 -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 NAA19780 for ; Thu, 20 Aug 1998 13:38:50 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id GAA06790; Fri, 21 Aug 1998 06:47:47 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199808202047.GAA06790@cimlogic.com.au> Subject: Re: Whereabouts of mount_msdos(8) In-Reply-To: from Brian Tao at "Aug 20, 98 11:48:02 am" To: taob@risc.org (Brian Tao) Date: Fri, 21 Aug 1998 06:47:47 +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 Brian Tao wrote: > What's the decision on mount_msdos and /usr/src/sbin/i386? It > looks like the buildworld target stopped looking at that directory on > August 15, but mount_msdos is still in there. Recent -current > snapshots don't have mount_msdos anymore. Wasn't the plan to move > mount_msdos out of the i386/ subdirectory anyway? Oops. That sounds like my mistake. I'll fix. -- 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 20 14:44:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00480 for freebsd-current-outgoing; Thu, 20 Aug 1998 14:44:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00372 for ; Thu, 20 Aug 1998 14:44:09 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA03270; Thu, 20 Aug 1998 22:37:35 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199808202137.WAA03270@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: Poul-Henning Kamp , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Thu, 20 Aug 1998 02:08:08 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Aug 1998 22:37:34 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Okay, how about we try out Mike's idea? Someone who experiences the > SIGXCPU kill problem could try putting the following in kern/kern_synch.c > line 638: > if (switchtime.tv_usec < p->p_switchtime.tv_usec || > switchtime.tv_sec < p->p_switchtime.tv_sec) > panic("bogus microuptime twiddling"); I had a ``if I was going to SIGXCPU, output the above values'' diagnostic in my kernel, and in all cases, switchtime.tv_usec was less than p->p_switchtime.tv_usec (tv_sec was the same for each var). Also (just for the record), the tv_usec values were *never* >1000000. >From what I can see, and given that the tv_sec values != 0 (which my diagnostics confirmed), p->p_switchtime is being copied from switchtime in mi_switch(), and then being compared at a later point (also in mi_switch()). ``switchtime'' at this point HAS GONE BACKWARDS. This means that successive calls to microuptime() are filling the passed variables with non-increasing values. This is confirmed by the only other call to microuptime() in /sys/kern as others are seeing the ``calcru: negative time...'' error which is impossible if microuptime() only ever increases (isn't it?). *If* microuptime() is returning non-increasing values under certain circumstances, then that means that either the timecounter pointer is being mis-optimised because it's not volatile (phk has pooh-poohed that idea though - I'm not sure why, but he's probably right, as tc[1] and tc[2] are the only values that *should* be getting pointed at as actual time values), *OR* that the amount that tv_usec is adjusted by is > LONG_MAX or < 0 (I think this is impossible as tc_scale_micro is assigned as something divided by 1000) *OR* tco_delta() is returning non-increasing values...... hmm In /sys/i386/isa/clock.c, should i8254_offset be reset after it's added to ``count'' ? What happens when i8254_offset wraps ? Might this be the problem ? Would it only be a problem for machines that have an irregular clock heart-beat, sometimes allowing loads of calls to i8254_get_timecount() before clkintr() happens ?? I reckon a diagnostic in microuptime() that compares the value assigned to *tv with the previous value and moans if they decrease may prove informative.... and maybe a similar thing in i8254_get_timecount() - the machine I was having problems with was running apm, so it used the i8254 timecounter rather than the tsc counter. > And see if we get some nice panics and cores. Is it worth a shot? I've > never gotten a SIGXCPU out of place, so my machine wouldn't be the one to > test this on. Same here. The machine I had that did this was given back to the shop. > Cheers, > Brian Feldman > green@unixhelp.org -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 20 14:45:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00829 for freebsd-current-outgoing; Thu, 20 Aug 1998 14:45:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00774; Thu, 20 Aug 1998 14:45:42 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA03519; Thu, 20 Aug 1998 22:44:40 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199808202144.WAA03519@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Dufault cc: bde@FreeBSD.ORG (Bruce Evans), current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern subr_xxx.c src/sys/scsi su.c src/sys/sys conf.h In-reply-to: Your message of "Thu, 20 Aug 1998 04:55:21 EDT." <199808200855.EAA11979@hda.hda.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Aug 1998 22:44:39 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > bde 1998/08/19 23:10:42 PDT > > > > Modified files: > > sys/kern subr_xxx.c > > sys/scsi su.c > > sys/sys conf.h > > Log: > > Moved `nx' functions to the one place where they are used (su.c). > > They shouldn't be used there either. They should have gone away > > about 3 years ago when the statically initialized devswitches went > > away, but su.c unfortunately still frobs the cdevswitch in the old > > way. > > "su" should go away in -current. The reason for it was quick and > dirty fixed SCSI targets before I put in the wire-down code and > the "uk" device. > > Anyone who notices it goes away will have an easy time to change > to a wired down device, and it will serve as a heads up to them > for work they have to do in the CAM cutover. > > Does anyone disagree? Maybe... the ``scsi -p'' command uses ssc(4) which requires su(4). This functionality is vital if you've got (say) an external scsi device that's the only thing on the bus and is normally switched off. Would wiring down the device cover this ? > Peter > > -- > Peter Dufault (dufault@hda.com) Realtime development, Machine control, > HD Associates, Inc. Safety critical systems, Agency approval -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 20 18:24:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05451 for freebsd-current-outgoing; Thu, 20 Aug 1998 18:24:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05446 for ; Thu, 20 Aug 1998 18:24:27 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA10669; Thu, 20 Aug 1998 18:22:54 -0700 (PDT) Message-Id: <199808210122.SAA10669@implode.root.com> To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter In-reply-to: Your message of "Thu, 20 Aug 1998 16:30:22 EDT." <199808202030.AA26024@mozart> From: David Greenman Reply-To: dg@root.com Date: Thu, 20 Aug 1998 18:22:54 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Has anyone done any work with the Intel PRO/1000 Gigabit >network adapter? > > It id's as Vendor: 0x8086 > Device: 0x1000 > > If so, I'd like to help. If not, any pointers are greatly >appreciated. I've sort of taken up the project of providing gigabit networking in FreeBSD. I just got some Alteon gigabit cards/documentation and am working on getting documentation for the Intels as well. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 20 18:41:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08247 for freebsd-current-outgoing; Thu, 20 Aug 1998 18:41:34 -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 SAA08238 for ; Thu, 20 Aug 1998 18:41:27 -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 LAA11972; Fri, 21 Aug 1998 11:40:39 +1000 Date: Fri, 21 Aug 1998 11:40:39 +1000 From: Bruce Evans Message-Id: <199808210140.LAA11972@godzilla.zeta.org.au> To: brian@Awfulhak.org, green@unixhelp.org Subject: Re: 13 months of user time? Cc: bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com, phk@critter.freebsd.dk, tlambert@primenet.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In /sys/i386/isa/clock.c, should i8254_offset be reset after it's >added to ``count'' ? What happens when i8254_offset wraps ? Might >this be the problem ? Would it only be a problem for machines that >have an irregular clock heart-beat, sometimes allowing loads of calls >to i8254_get_timecount() before clkintr() happens ?? The problem is very unlikely to be with i8254_get_timecount(). Bugs would probably make it jump forward. >I reckon a diagnostic in microuptime() that compares the value >assigned to *tv with the previous value and moans if they decrease >may prove informative.... and maybe a similar thing in >i8254_get_timecount() - the machine I was having problems with was >running apm, so it used the i8254 timecounter rather than the tsc >counter. The problem is quite likely to be with apm. It does bad things to reinitialize the time. Damage is limited by not reinitializing the time unless apm has apparently been asleep for > 2 seconds (or < -2 seconds :-). 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 20 19:01:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11380 for freebsd-current-outgoing; Thu, 20 Aug 1998 19:01:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11364 for ; Thu, 20 Aug 1998 19:01:44 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id UAA01630; Thu, 20 Aug 1998 20:58:49 -0500 (CDT) From: Kevin Day Message-Id: <199808210158.UAA01630@home.dragondata.com> Subject: Re: 13 months of user time? In-Reply-To: <199808210140.LAA11972@godzilla.zeta.org.au> from Bruce Evans at "Aug 21, 98 11:40:39 am" To: bde@zeta.org.au (Bruce Evans) Date: Thu, 20 Aug 1998 20:58:48 -0500 (CDT) Cc: brian@Awfulhak.org, green@unixhelp.org, bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com, phk@critter.freebsd.dk, tlambert@primenet.com X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I reckon a diagnostic in microuptime() that compares the value > >assigned to *tv with the previous value and moans if they decrease > >may prove informative.... and maybe a similar thing in > >i8254_get_timecount() - the machine I was having problems with was > >running apm, so it used the i8254 timecounter rather than the tsc > >counter. > > The problem is quite likely to be with apm. It does bad things to > reinitialize the time. Damage is limited by not reinitializing the > time unless apm has apparently been asleep for > 2 seconds (or < -2 > seconds :-). > > Bruce FWIW, I've got a Cyrix MediaGX system that does this, has APM turned off, and continually complains: calcru: negative time -7747 ms (or whatever the message is). It's usually 2 to 10 seconds at a time when it does it. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 20 20:31:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24171 for freebsd-current-outgoing; Thu, 20 Aug 1998 20:31:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-c0f.dialup.hilink.com.au [203.2.144.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24162 for ; Thu, 20 Aug 1998 20:31:30 -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 UAA03923 for ; Thu, 20 Aug 1998 20:29:24 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808202029.UAA03923@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: New bootstrap now available for general testing. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Aug 1998 20:29:23 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm pleased to announce that the new (three-stage) bootstrap code is now available for general testing. Please note the caveats in the commit message below. Major changes are slated for the i386 code, including: - net device additions - PnP/PCI BIOS probes - a new crt0 module borrowing from "DOS extender" technology General major changes planned: - full merge of disk- and net- bootstraps - move of the image activators from MD to MI code - PnP-based peripheral detection - module dependancy determination and autoloading Contributions, fixes, criticisms are all warmly solicited. A couple of notes specifically for the NetBSD folks: - Thanks for making your work on the i386 standalone bootstrap available. Having such a working example has made germination much more rapid. - In both this and the libstand code recently incorporated, we have done our best to respect copyright claims on existing code, and attempted to give appropriate credit where due. If you find any cases where we might have been lax in this matter, please let me know privately, so that these omissions can be corrected promptly. ------- Forwarded Message From: Michael Smith Date: Thu, 20 Aug 1998 20:17:42 -0700 (PDT) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/boot - Imported sources msmith 1998/08/20 20:17:42 PDT src/sys/boot - Imported sources Update of /home/ncvs/src/sys/boot In directory freefall.freebsd.org:/d/users/msmith/boot Log Message: This is the new unified bootstrap, sometimes known previously as the 'three-stage' bootstrap. There are a number of caveats with the code in its current state: - The i386 bootstrap only supports booting from a floppy. - The kernel and kld do not yet know how to deal with the extended information and module summary passed in. - PnP-based autodetection and demand loading of modules is not implemented. - i386 ELF kernel loading is not ready yet. - The i386 bootstrap is loaded via an ugly blockmap. On the alpha, both net- and disk-booting (SRM console machines only) is supported. No blockmaps are used by this code. Obtained from: Parts from the NetBSD/i386 standalone bootstrap. ------- End of Forwarded Message -- \\ 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 20 21:37:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01805 for freebsd-current-outgoing; Thu, 20 Aug 1998 21:37:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01800 for ; Thu, 20 Aug 1998 21:37:37 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id XAA17093; Thu, 20 Aug 1998 23:36:46 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 20 Aug 1998 23:36:45 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter In-Reply-To: <199808202030.AA26024@mozart> 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, 20 Aug 1998, John W. DeBoskey wrote: > Hi, > > Has anyone done any work with the Intel PRO/1000 Gigabit > network adapter? > > It id's as Vendor: 0x8086 > Device: 0x1000 > > If so, I'd like to help. If not, any pointers are greatly > appreciated. > *drool*... Just out of curiosity, what do these things cost? And can you get them with singlemode fiber interfaces? It is currently going to cost me about $10k for the conversion equipment to connect all of our buildings at 100Mbit (would need 10 100BTX -> singlemode converters. I have 5 remote buildings), and if I could just go directly between two of these cards (in FreeBSD boxes of course) with singlemode fiber I think I'd be in heaven. With hefty enough processors in the boxes on both ends, i could probably route a good chunk of that bandwith. More than likely not all of it though (mostly because of the PCI bus, I imagine). However I slice it, it would still be better than 100Mbit. I doubt I could get my work (K12 school district) to help pay for the development of a driver for this, but maybe if we bought a couple I could loan them out for a while to someone who would like to write a driver. :-) -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (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 20 21:39:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01992 for freebsd-current-outgoing; Thu, 20 Aug 1998 21:39:44 -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 VAA01986 for ; Thu, 20 Aug 1998 21:39:43 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id VAA04364; Thu, 20 Aug 1998 21:39:01 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma004362; Thu Aug 20 21:38:46 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id VAA11797; Thu, 20 Aug 1998 21:38:46 -0700 (PDT) From: Archie Cobbs Message-Id: <199808210438.VAA11797@bubba.whistle.com> Subject: Re: New bootstrap now available for general testing. In-Reply-To: <199808202029.UAA03923@dingo.cdrom.com> from Mike Smith at "Aug 20, 98 08:29:23 pm" To: mike@smith.net.au (Mike Smith) Date: Thu, 20 Aug 1998 21:38:46 -0700 (PDT) Cc: 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 Mike Smith writes: > I'm pleased to announce that the new (three-stage) bootstrap code is > now available for general testing. Please note the caveats in the > commit message below. > > Major changes are slated for the i386 code, including: > > - net device additions > - PnP/PCI BIOS probes > - a new crt0 module borrowing from "DOS extender" technology > > General major changes planned: > > - full merge of disk- and net- bootstraps > - move of the image activators from MD to MI code > - PnP-based peripheral detection > - module dependancy determination and autoloading > > Contributions, fixes, criticisms are all warmly solicited. How about congratulations! :-) This stuff has been wanting for a long time... -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 20 22:58:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12983 for freebsd-current-outgoing; Thu, 20 Aug 1998 22:58:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA12963 for ; Thu, 20 Aug 1998 22:57:55 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA12043; Thu, 20 Aug 1998 23:57:04 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id XAA10418; Thu, 20 Aug 1998 23:57:03 -0600 Date: Thu, 20 Aug 1998 23:57:03 -0600 Message-Id: <199808210557.XAA10418@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: dg@root.com Cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter In-Reply-To: <199808210122.SAA10669@implode.root.com> References: <199808202030.AA26024@mozart> <199808210122.SAA10669@implode.root.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Has anyone done any work with the Intel PRO/1000 Gigabit > >network adapter? .. > I've sort of taken up the project of providing gigabit networking in > FreeBSD. I just got some Alteon gigabit cards/documentation and am working > on getting documentation for the Intels as well. So does that mean the 'VM bugs John has left us with' (your words, not mine) are going to be in 3.0-RELEASE? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 20 23:04:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13678 for freebsd-current-outgoing; Thu, 20 Aug 1998 23:04:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (obelix.trw.nl [195.193.64.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13673 for ; Thu, 20 Aug 1998 23:04:23 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id IAA00379; Fri, 21 Aug 1998 08:00:10 +0200 (CEST) To: Chris Dillon cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter In-reply-to: Your message of "Thu, 20 Aug 1998 23:36:45 CDT." Date: Fri, 21 Aug 1998 08:00:09 +0200 Message-ID: <377.903679209@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >*drool*... Just out of curiosity, what do these things cost? And can >you get them with singlemode fiber interfaces? It is currently going >to cost me about $10k for the conversion equipment to connect all of >our buildings at 100Mbit (would need 10 100BTX -> singlemode >converters. I have 5 remote buildings), and if I could just go >directly between two of these cards (in FreeBSD boxes of course) with >singlemode fiber I think I'd be in heaven. Why not consider ATM cards with single mode fiber then ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 20 23:07:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14017 for freebsd-current-outgoing; Thu, 20 Aug 1998 23:07:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (obelix.trw.nl [195.193.64.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14000 for ; Thu, 20 Aug 1998 23:07:12 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id HAA00296; Fri, 21 Aug 1998 07:37:31 +0200 (CEST) To: Brian Somers cc: Brian Feldman , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Thu, 20 Aug 1998 22:37:34 BST." <199808202137.WAA03270@awfulhak.org> Date: Fri, 21 Aug 1998 07:37:30 +0200 Message-ID: <294.903677850@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >[...] the machine I was having problems with was >running apm, so it used the i8254 timecounter rather than the tsc >counter. Ahh... I bet that is it: APM sucks. Try to disable APM and see if you can reproduce it, I'll bet you my collection of genuine 11 row punched cards that you can't. Our handling of APM is probably not the best either, in sys/i386/apm/apm.c the apm_default_resume() and apm_default_resume() does things which most parents would not want their kids to see or even know about. The basic scoop on APM is: Normal mode: Your TSC may run on variable frequency, with no warning, or with warning by an APM bios event (usually after the fact). Your i8254 mostly seem to run at constant frequency, although some reports I've seen indicates it may not. The APM bios may issue events to report anomalies (post factum). Your RTC runs at nominal speed, and the interrupts will arrive one by one, mostly on time. Suspend mode: Your TSC may or may not run, frequency unknown. Your i8254 may or may not run, frequency unknown. Your RTC runs, but interrupts may be disabled or postponed and arrive in "batch mode" when the machine is resumed. There is no doubt that the right thing to do on resume is to spin-poll the RTC for a shift of second, fixup the boottime and let the system loose again. What to do about the i8254 being slowed is much more tricky. If you could add code to your system which counts the RTC interrupts and tracks the i8254 timecounter delta between irqs, then maybe we can see what is happening on your system and get an idea for handling it... "Unfortunately" both of the two laptops I have access to doesn't have any of these problems, so I can't work on it myself. I said "Unfortunately" because they were chosen partly because of that... Summary: It will take hacking by the people who see the problem on their machines to fix this problem... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 02:53:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10461 for freebsd-current-outgoing; Fri, 21 Aug 1998 02:53:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d5.dialup.hilink.com.au [203.2.144.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10453 for ; Fri, 21 Aug 1998 02:53:33 -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 CAA05733; Fri, 21 Aug 1998 02:41:46 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808210241.CAA05733@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp cc: Brian Somers , Brian Feldman , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Fri, 21 Aug 1998 07:37:30 +0200." <294.903677850@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 02:41:45 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >[...] the machine I was having problems with was > >running apm, so it used the i8254 timecounter rather than the tsc > >counter. > > Ahh... I bet that is it: APM sucks. > > Try to disable APM and see if you can reproduce it, I'll bet you > my collection of genuine 11 row punched cards that you can't. We've already had a respondent indicate that they are seeing the symptoms on non-APM systems. -- \\ 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 21 03:08:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA12133 for freebsd-current-outgoing; Fri, 21 Aug 1998 03:08:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA12128 for ; Fri, 21 Aug 1998 03:08:21 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id GAA15068; Fri, 21 Aug 1998 06:01:33 -0400 (EDT) From: Peter Dufault Message-Id: <199808211001.GAA15068@hda.hda.com> Subject: Re: cvs commit: src/sys/kern subr_xxx.c src/sys/scsi su.c src/sys/sys conf.h In-Reply-To: <199808202144.WAA03519@awfulhak.org> from Brian Somers at "Aug 20, 98 10:44:39 pm" To: brian@Awfulhak.org (Brian Somers) Date: Fri, 21 Aug 1998 06:01:33 -0400 (EDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (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 > > "su" should go away in -current. The reason for it was quick and > > dirty fixed SCSI targets before I put in the wire-down code and > > the "uk" device. > > > > Anyone who notices it goes away will have an easy time to change > > to a wired down device, and it will serve as a heads up to them > > for work they have to do in the CAM cutover. > > > > Does anyone disagree? > > Maybe... the ``scsi -p'' command uses ssc(4) which requires su(4). > This functionality is vital if you've got (say) an external scsi > device that's the only thing on the bus and is normally switched off. > > Would wiring down the device cover this ? No - but ssc could be simplified to only provide the trap door for the reprobe instead of providing access to the "device in minor number" su devices. The bus would have to be encoded still so I have to check that it is still a big improvement. Then the wiring down should cover all bases. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 03:14:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA12996 for freebsd-current-outgoing; Fri, 21 Aug 1998 03:14:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (obelix.trw.nl [195.193.64.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA12974 for ; Fri, 21 Aug 1998 03:14:22 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id MAA00940; Fri, 21 Aug 1998 12:07:49 +0200 (CEST) To: Mike Smith cc: Brian Somers , Brian Feldman , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Fri, 21 Aug 1998 02:41:45 -0000." <199808210241.CAA05733@dingo.cdrom.com> Date: Fri, 21 Aug 1998 12:07:49 +0200 Message-ID: <938.903694069@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808210241.CAA05733@dingo.cdrom.com>, Mike Smith writes: >> >> >[...] the machine I was having problems with was >> >running apm, so it used the i8254 timecounter rather than the tsc >> >counter. >> >> Ahh... I bet that is it: APM sucks. >> >> Try to disable APM and see if you can reproduce it, I'll bet you >> my collection of genuine 11 row punched cards that you can't. > >We've already had a respondent indicate that they are seeing the >symptoms on non-APM systems. I didn't see that, and I doubt it until the repondent double-checks his bios settings... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 04:18:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA18974 for freebsd-current-outgoing; Fri, 21 Aug 1998 04:18:08 -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 EAA18969 for ; Fri, 21 Aug 1998 04:18:04 -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 NAA26776; Fri, 21 Aug 1998 13:16:59 +0200 (MET DST) Received: (from pb@localhost) by mars.hsc.fr (8.8.8/8.8.8/pb-19980526) id NAA06762; Fri, 21 Aug 1998 13:16:58 +0200 (CEST) (envelope-from pb) Message-ID: <19980821131657.A6628@mars.hsc.fr> Date: Fri, 21 Aug 1998 13:16:57 +0200 From: Pierre Beyssac To: Poul-Henning Kamp , Mike Smith Cc: Brian Somers , Brian Feldman , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? References: <199808210241.CAA05733@dingo.cdrom.com> <938.903694069@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: <938.903694069@critter.freebsd.dk>; from Poul-Henning Kamp on Fri, Aug 21, 1998 at 12:07:49PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 21, 1998 at 12:07:49PM +0200, Poul-Henning Kamp wrote: > >We've already had a respondent indicate that they are seeing the > >symptoms on non-APM systems. > > I didn't see that, and I doubt it until the repondent double-checks > his bios settings... Then in my case anyway, it's not a problem of disabling APM or not: unless I'm severely mistaken about my motherboard (Asus T2P4) and its BIOS settings, it's NOT an APM system. -- 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 Fri Aug 21 04:34:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA20223 for freebsd-current-outgoing; Fri, 21 Aug 1998 04:34:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (obelix.trw.nl [195.193.64.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA20218 for ; Fri, 21 Aug 1998 04:34:23 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id NAA01120; Fri, 21 Aug 1998 13:27:04 +0200 (CEST) To: Pierre Beyssac cc: Mike Smith , Brian Somers , Brian Feldman , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Fri, 21 Aug 1998 13:16:57 +0200." <19980821131657.A6628@mars.hsc.fr> Date: Fri, 21 Aug 1998 13:27:02 +0200 Message-ID: <1118.903698822@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980821131657.A6628@mars.hsc.fr>, Pierre Beyssac writes: >On Fri, Aug 21, 1998 at 12:07:49PM +0200, Poul-Henning Kamp wrote: >> >We've already had a respondent indicate that they are seeing the >> >symptoms on non-APM systems. >> >> I didn't see that, and I doubt it until the repondent double-checks >> his bios settings... > >Then in my case anyway, it's not a problem of disabling APM or not: >unless I'm severely mistaken about my motherboard (Asus T2P4) and >its BIOS settings, it's NOT an APM system. I think it has APM, check the BIOS setting... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 04:47:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA21399 for freebsd-current-outgoing; Fri, 21 Aug 1998 04:47:35 -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 EAA21380 for ; Fri, 21 Aug 1998 04:47:30 -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 NAA27003; Fri, 21 Aug 1998 13:46:38 +0200 (MET DST) Received: (from pb@localhost) by mars.hsc.fr (8.8.8/8.8.8/pb-19980526) id NAA06869; Fri, 21 Aug 1998 13:46:38 +0200 (CEST) (envelope-from pb) Message-ID: <19980821134637.D302@mars.hsc.fr> Date: Fri, 21 Aug 1998 13:46:37 +0200 From: Pierre Beyssac To: Poul-Henning Kamp , Pierre Beyssac Cc: Mike Smith , Brian Somers , Brian Feldman , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? References: <19980821131657.A6628@mars.hsc.fr> <1118.903698822@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: <1118.903698822@critter.freebsd.dk>; from Poul-Henning Kamp on Fri, Aug 21, 1998 at 01:27:02PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 21, 1998 at 01:27:02PM +0200, Poul-Henning Kamp wrote: > >Then in my case anyway, it's not a problem of disabling APM or not: > >unless I'm severely mistaken about my motherboard (Asus T2P4) and > >its BIOS settings, it's NOT an APM system. > > I think it has APM, check the BIOS setting... Okay, sorry, I was severely mistaken then, the manual indicates there is an APM setting. Only I'm not at home right now so I can't check before late this night. As I haven't ever changed it, it must be in the "default" state for the T2P4 which is "user-defined" (other states are "disabled", "min" and "max"). The manual is not very clear about what "user-defined" exactly means, but it's clearly not "disabled". -- 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 Fri Aug 21 04:57:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA22861 for freebsd-current-outgoing; Fri, 21 Aug 1998 04:57:37 -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 EAA22847 for ; Fri, 21 Aug 1998 04:57:32 -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 EAA07874; Fri, 21 Aug 1998 04:55:14 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808210455.EAA07874@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Archie Cobbs cc: mike@smith.net.au (Mike Smith), current@FreeBSD.ORG Subject: Re: New bootstrap now available for general testing. In-reply-to: Your message of "Thu, 20 Aug 1998 21:38:46 MST." <199808210438.VAA11797@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 04:55:13 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Contributions, fixes, criticisms are all warmly solicited. > > How about congratulations! :-) This stuff has been wanting > for a long time... That can wait for when it's ready for showtime. Got a ways to go yet. Thanks, though. 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 Fri Aug 21 04:59:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23256 for freebsd-current-outgoing; Fri, 21 Aug 1998 04:59:43 -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 EAA23229 for ; Fri, 21 Aug 1998 04:59:39 -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 DAA07457; Fri, 21 Aug 1998 03:28:14 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808210328.DAA07457@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp cc: Mike Smith , Brian Somers , Brian Feldman , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Fri, 21 Aug 1998 12:07:49 +0200." <938.903694069@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 03:28:14 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199808210241.CAA05733@dingo.cdrom.com>, Mike Smith writes: > >> > >> >[...] the machine I was having problems with was > >> >running apm, so it used the i8254 timecounter rather than the tsc > >> >counter. > >> > >> Ahh... I bet that is it: APM sucks. > >> > >> Try to disable APM and see if you can reproduce it, I'll bet you > >> my collection of genuine 11 row punched cards that you can't. > > > >We've already had a respondent indicate that they are seeing the > >symptoms on non-APM systems. > > I didn't see that, and I doubt it until the repondent double-checks > his bios settings... With no APM in the kernel, the BIOS is not at liberty to play with the clock. (No connect, no enable.) You're welcome to check the archives, if you wish. I also consider it a fault in our timing support if it can't handle time moving forwards at a variable rate. "APM" doesn't send the clock backwards, so no time interval should ever be negative. Please take this issue seriously. You can't just handwave and say "it's all APM's fault". -- \\ 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 21 05:02:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23783 for freebsd-current-outgoing; Fri, 21 Aug 1998 05:02:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from infovabadus.aripaev.ee (infovabadus.aripaev.ee [194.204.12.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23741 for ; Fri, 21 Aug 1998 05:02:07 -0700 (PDT) (envelope-from root@infovabadus.aripaev.ee) Received: from localhost (root@localhost) by infovabadus.aripaev.ee (8.8.8/8.8.8) with SMTP id PAA04485 for ; Fri, 21 Aug 1998 15:00:29 +0300 (EEST) (envelope-from root@infovabadus.aripaev.ee) Date: Fri, 21 Aug 1998 15:00:29 +0300 (EEST) From: Charlie ROOT To: current@FreeBSD.ORG Subject: Problems with vx0 (3Com) 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 Todays current doesn't see vx0 anymore... Help. TIA _____________ Lauri Laupmaa mauri@mbp.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 05:02:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23833 for freebsd-current-outgoing; Fri, 21 Aug 1998 05:02:23 -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 FAA23828 for ; Fri, 21 Aug 1998 05:02:20 -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 EAA07850; Fri, 21 Aug 1998 04:53:11 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808210453.EAA07850@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp cc: Pierre Beyssac , Mike Smith , Brian Somers , Brian Feldman , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Fri, 21 Aug 1998 13:27:02 +0200." <1118.903698822@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 04:53:10 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <19980821131657.A6628@mars.hsc.fr>, Pierre Beyssac writes: > >On Fri, Aug 21, 1998 at 12:07:49PM +0200, Poul-Henning Kamp wrote: > >> >We've already had a respondent indicate that they are seeing the > >> >symptoms on non-APM systems. > >> > >> I didn't see that, and I doubt it until the repondent double-checks > >> his bios settings... > > > >Then in my case anyway, it's not a problem of disabling APM or not: > >unless I'm severely mistaken about my motherboard (Asus T2P4) and > >its BIOS settings, it's NOT an APM system. > > I think it has APM, check the BIOS setting... Only with recent BIOS upgrades. It doesn't support clock idling either. Time to fix your code, Poul. -- \\ 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 21 06:01:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00276 for freebsd-current-outgoing; Fri, 21 Aug 1998 06:01:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from priscilla.mu.org (priscilla.mu.org [206.156.231.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00265 for ; Fri, 21 Aug 1998 06:01:38 -0700 (PDT) (envelope-from paul@priscilla.mu.org) Received: (from paul@localhost) by priscilla.mu.org (8.8.8/8.8.8) id IAA28599; Fri, 21 Aug 1998 08:00:37 -0500 (CDT) (envelope-from paul) Message-ID: <19980821080037.A28574@mu.org> Date: Fri, 21 Aug 1998 08:00:37 -0500 From: Paul Saab To: Charlie ROOT , current@FreeBSD.ORG Subject: Re: Problems with vx0 (3Com) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: ; from Charlie ROOT on Fri, Aug 21, 1998 at 03:00:29PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Use the new xl driver. It is better than the vx driver for the 3com cards that support DMA. paul Charlie ROOT (root@infovabadus.aripaev.ee) wrote: > Hi > > Todays current doesn't see vx0 anymore... Help. > > TIA > _____________ > Lauri Laupmaa > mauri@mbp.ee > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 06:11:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02239 for freebsd-current-outgoing; Fri, 21 Aug 1998 06:11:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.pipeline.ch (freefall.pipeline.ch [195.134.128.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02160 for ; Fri, 21 Aug 1998 06:11:15 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.128.41]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA332; Fri, 21 Aug 1998 15:08:51 +0200 Message-ID: <35DD717B.94F99C0E@pipeline.ch> Date: Fri, 21 Aug 1998 15:09:15 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Charlie ROOT CC: current@FreeBSD.ORG Subject: Re: Problems with vx0 (3Com) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Charlie ROOT wrote: > > Hi > > Todays current doesn't see vx0 anymore... Help. It has got a new driver, it's called tx0 now. Make shure to compile device tx0 into your kernel. -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 06:17:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03146 for freebsd-current-outgoing; Fri, 21 Aug 1998 06:17:38 -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 GAA03134 for ; Fri, 21 Aug 1998 06:17:20 -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 JAA14105; Fri, 21 Aug 1998 09:19:17 -0400 From: Bill Paul Message-Id: <199808211319.JAA14105@skynet.ctr.columbia.edu> Subject: Re: Problems with vx0 (3Com) To: root@infovabadus.aripaev.ee (Charlie ROOT) Date: Fri, 21 Aug 1998 09:19:15 -0400 (EDT) Cc: mauri@mbp.ee, current@FreeBSD.ORG In-Reply-To: from "Charlie ROOT" at Aug 21, 98 03:00:29 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, Charlie ROOT had to walk into mine and say: > Hi > > Todays current doesn't see vx0 anymore... Help. Aw, couldn't you have provided more information that this? This is not enough to help you. It's not even enough to make a guess. (Well, maybe, but not an informed guess.) What kind of network card do you have that's supposed to be detected by the vx driver? A new driver (xl) was added recently to handle all of the 3Com Etherlink XL cards (3c900, 3c905 and 3c905B, which up until now was not supported. The vx driver supported some of these cards, but not fully and not very efficiently; support for the 3c90x cards in the vx driver was disabled so that the xl driver would detect them instead. Which one did you have, and did you look for xl0 instead of vx0? There are two things that could have gone wrong here: - The xl driver failed to detect your card, either because of a bug or because I screwed up somehow when I imported it (nobody else has complained about this so far though; I'll see if there's been a recent snapshot and snag a copy of the boot floppy to make sure it sees the cardson my systems). - You used an old kernel configuration file as opposed to GENERIC and your custom configuration doesn't specify the xl driver. If this is the case, add the following line your config file under where it says 'device vx0': device xl0 You will also need to edit your rc.conf file to use xl0 instead of vx0. - The driver is in the kernel and it did detect your card, but all you saw were the error messages from the rc scripts saying that there was no such interface as xl0. Check the dmesg output, and edit your /etc/rc.conf file as necessary. NOTE: If your card is a COMBO (like the 3c900 COMBO) and the driver selects the wrong media, use the ifmedia options to select the right one: # ifconfig xl0 media 10baseT/UTP (for RJ-45 twisted pair) # ifconfig xl0 media 10base2/BNC (for coax/thinnet) # ifconfig xl0 media 10base5/AUI (for AUI) You can also add the 'media foo' options to the 'interfaces' lines in your /etc/rc.conf to insure the right media is selected when the machine boots. For the TPO cards there's only one possible media so it can't get that wrong, and for the 100Mbps cards it should autoselect the speed and duplex modes. (You can still force a particular mode if you want.) -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 Fri Aug 21 06:46:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05944 for freebsd-current-outgoing; Fri, 21 Aug 1998 06:46:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.pipeline.ch (intranet.pipeline.ch [195.134.128.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05934 for ; Fri, 21 Aug 1998 06:46:50 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.128.41]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA69; Fri, 21 Aug 1998 15:44:29 +0200 Message-ID: <35DD79D4.57C523AB@pipeline.ch> Date: Fri, 21 Aug 1998 15:44:52 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Charlie ROOT , current@FreeBSD.ORG Subject: Re: Problems with vx0 (3Com) References: <35DD717B.94F99C0E@pipeline.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andre Oppermann wrote: > > Charlie ROOT wrote: > > > > Hi > > > > Todays current doesn't see vx0 anymore... Help. > > It has got a new driver, it's called tx0 now. Make shure to compile > device tx0 into your kernel. Arghhh, that was a mistake... not tx0 but xl0. I need to get some sleep. -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 07:04:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08641 for freebsd-current-outgoing; Fri, 21 Aug 1998 07:04:22 -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 HAA08500 for ; Fri, 21 Aug 1998 07:03:59 -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 QAA26771 for ; Fri, 21 Aug 1998 16:02:34 +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 QAA29489 for ; Fri, 21 Aug 1998 16:02:32 +0200 (MET DST) Message-ID: <35DD7DF8.FE395CF7@kkeka.ericsson.se> Date: Fri, 21 Aug 1998 16:02:32 +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: current@FreeBSD.ORG Subject: Re: Problems with vx0 (3Com) References: <35DD717B.94F99C0E@pipeline.ch> <35DD79D4.57C523AB@pipeline.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does what is stated below affect FreeBSD? now that vx has became tx with DMA? 100-Mbps Ethernet Performance Problem on Some Intel Motherboard Chipsets Some PCI motherboards contain DMA chipsets that are unable to support 100-Mbps Fast Ethernet. Because of this problem, the Solaris operating environment does not support 100-Mbps PCI network operation on systems containing the slow chipsets. This problem affects PCI cards only. Other buses are not affected. The following chipsets are known to exhibit this problem:  82430LX (Mercury)  82450GX (Orion) (A and B steppings only) The following chipsets do not exhibit this problem:  82430NX (Neptune)  82430FX (Triton)  82430HX (Triton II)  82440FX (Natoma)  82450GX (Orion) (C0 stepping and later) Some slow PCI motherboard chipsets do not support long data burst DMA transfers and are unable to transfer data from PCI cards to system memory sufficiently fast to sustain 100-Mbps throughput. When systems with these chipsets are connected to a 100-Mbps network, data can arrive at a PCI Ethernet card faster than DMA can transfer it from the card to system memory. When this happens, the card?s FIFO begins to fill. If this condition persists long enough, the card?s FIFO will over ow, causing loss of incoming network data. When incoming data is lost, higher-level protocols such as TCP or NFS TM will time out and retransmit the lost data. These protocols ensure that all data is transferred, but performance is lowered. If only a few packets are lost, the performance impact may be small or moderate, but if many packets are lost, a very substantial and severe performance loss can arise. In some cases, a drop in network FTP performance of two orders of magnitude has been seen when using such chipsets, rendering the network unusable. This case occurs when using 100-Mbps cards containing relatively small FIFOs. The cards are designed to be able to hold only a couple of packets, and they depend on the DMA mechanism to transfer data out of the FIFO in a timely way. In other cases, cards with larger FIFOs are not as severely impacted by the problem, and under normal conditions perform as well on machines with slow chipsets as they do on speedy ones. However, under sustained 100-Mbps operation, this cannot continue indefinitely. Because of this problem, the Solaris environment does not support 100-Mbps PCI network operation on systems containing the slow chipsets. In particular, the PCI cards supported by the dnet, iprb, and elx drivers will not provide good performance on machines with the problem chipsets. If 100-Mbps operation is required on such a machine, it is best to use a non-PCI Ethernet controller. It is also possible that the PCI cards supported by the ieef driver, which have larger FIFOs, may function adequately. You must decide whether the performance on a particular machine is adequate for the intended purpose. -- =--------=/////////////////\\\\\\\\\\\\\\\\\\\\=--------= ((___)) | 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 07:12:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09693 for freebsd-current-outgoing; Fri, 21 Aug 1998 07:12:02 -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 HAA09627 for ; Fri, 21 Aug 1998 07:11: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 QAA12126; Fri, 21 Aug 1998 16:06:49 +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 KAA02477; Fri, 21 Aug 1998 10:36:22 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808210836.KAA02477@semyam.dinoco.de> To: Brian Feldman Subject: Re: 13 months of user time? In-reply-to: Your message of "Thu, 20 Aug 1998 02:08:08 EDT." Cc: seggers@semyam.dinoco.de, freebsd-current@FreeBSD.ORG Date: Fri, 21 Aug 1998 10:36:20 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > SIGXCPU kill problem could try putting the following in kern/kern_synch.c > line 638: I think better not this one as that is a safe way to a panic IMHO. A version I think does what you intend this to do I add below. It is untested code I just added while writing the mail. > if (switchtime.tv_usec < p->p_switchtime.tv_usec || > switchtime.tv_sec < p->p_switchtime.tv_sec) > panic("bogus microuptime twiddling"); > > And see if we get some nice panics and cores. Is it worth a shot? I've As far as I can see the timeval in the process structure is a real timeval and not abused to be something else. So tv_usec contains the micro seconds part and tv_sec the seconds. Let's assume that p->p_switchtime.tv_usec contains 999999 now and p->p_switchtime.tv_sec is 0. Lets suppose the time continues a little bit and when we reach the if statement switchtime.tv_usec might contain 0 and switchtime.tv_sec 1. The time didn't go backward but with the code above causes a panic. > never gotten a SIGXCPU out of place, so my machine wouldn't be the one to > test this on. And I don't think you want the test this way, anyway. ;-) One has first to calculate a 64 bit integer from the seconds and micro seconds and then compare the two resulting numbers. With that it could actually detect switchtime going backward. Something like this: int64_t time1, time2; [...] time1 = switchtime.tv_usec + switchtime.tv_sec * (int64_t)1000000; time2 = p->p_switchtime.tv_usec + p->p_switchtime.tv_sec * (int64_t)1000000; if (time1 < time2) panic("Ooops! Switchtime going backward!"); Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 07:15:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10270 for freebsd-current-outgoing; Fri, 21 Aug 1998 07:15:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (mexcom.net.mx [207.249.162.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10264 for ; Fri, 21 Aug 1998 07:15:41 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (mexcom.net.mx [207.249.162.140]) by dns.webwizard.net.mx (8.8.8/8.8.7) with ESMTP id JAA05479; Fri, 21 Aug 1998 09:07:08 -0500 (CDT) Message-ID: <35DD7F0B.7EBFC645@webwizard.org.mx> Date: Fri, 21 Aug 1998 09:07:08 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Bill Paul CC: Charlie ROOT , mauri@mbp.ee, current@FreeBSD.ORG Subject: Re: Problems with vx0 (3Com) References: <199808211319.JAA14105@skynet.ctr.columbia.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anybody tried it with the 3c595, that poor folks like us might still have? Thanks ed Bill Paul wrote: > Of all the gin joints in all the towns in all the world, Charlie ROOT > had to walk into mine and say: > > > Hi > > > > Todays current doesn't see vx0 anymore... Help. > > Aw, couldn't you have provided more information that this? This is not > enough to help you. It's not even enough to make a guess. (Well, maybe, > but not an informed guess.) > > What kind of network card do you have that's supposed to be detected > by the vx driver? A new driver (xl) was added recently to handle all of > the 3Com Etherlink XL cards (3c900, 3c905 and 3c905B, which up until > now was not supported. The vx driver supported some of these cards, > but not fully and not very efficiently; support for the 3c90x cards > in the vx driver was disabled so that the xl driver would detect them > instead. Which one did you have, and did you look for xl0 instead of vx0? > > There are two things that could have gone wrong here: > > - The xl driver failed to detect your card, either because of a bug > or because I screwed up somehow when I imported it (nobody else has > complained about this so far though; I'll see if there's been a recent > snapshot and snag a copy of the boot floppy to make sure it sees the > cardson my systems). > > - You used an old kernel configuration file as opposed to GENERIC > and your custom configuration doesn't specify the xl driver. If this > is the case, add the following line your config file under where > it says 'device vx0': > > device xl0 > > You will also need to edit your rc.conf file to use xl0 instead of > vx0. > > - The driver is in the kernel and it did detect your card, but all you > saw were the error messages from the rc scripts saying that there was > no such interface as xl0. Check the dmesg output, and edit your > /etc/rc.conf file as necessary. > > NOTE: If your card is a COMBO (like the 3c900 COMBO) and the driver > selects the wrong media, use the ifmedia options to select the > right one: > > # ifconfig xl0 media 10baseT/UTP (for RJ-45 twisted pair) > # ifconfig xl0 media 10base2/BNC (for coax/thinnet) > # ifconfig xl0 media 10base5/AUI (for AUI) > > You can also add the 'media foo' options to the 'interfaces' > lines in your /etc/rc.conf to insure the right media is selected > when the machine boots. > > For the TPO cards there's only one possible media so it can't > get that wrong, and for the 100Mbps cards it should autoselect > the speed and duplex modes. (You can still force a particular > mode if you want.) > > -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 Fri Aug 21 07:22:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10900 for freebsd-current-outgoing; Fri, 21 Aug 1998 07:22:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10893 for ; Fri, 21 Aug 1998 07:22:24 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id PAA01382; Fri, 21 Aug 1998 15:20:34 +0200 (CEST) To: Mike Smith cc: Brian Somers , Brian Feldman , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Fri, 21 Aug 1998 03:28:14 -0000." <199808210328.DAA07457@dingo.cdrom.com> Date: Fri, 21 Aug 1998 15:20:34 +0200 Message-ID: <1380.903705634@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >With no APM in the kernel, the BIOS is not at liberty to play with the >clock. (No connect, no enable.) > >You're welcome to check the archives, if you wish. Yes, it is at liberty to play with it, but must do so in a "transparent" way. >I also consider it a fault in our timing support if it can't handle >time moving forwards at a variable rate. "APM" doesn't send the clock >backwards, so no time interval should ever be negative. > >Please take this issue seriously. You can't just handwave and say >"it's all APM's fault". Belive me, I'm taking this very seriously, but until I can make it fail on one of my machines, I'll have a hard time fixing it. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 08:06:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17450 for freebsd-current-outgoing; Fri, 21 Aug 1998 08:06:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.98.150]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17438 for ; Fri, 21 Aug 1998 08:06:17 -0700 (PDT) (envelope-from root@myhakas.matti.ee) Received: (from root@localhost) by myhakas.matti.ee (8.9.1/8.8.5) id SAA08827; Fri, 21 Aug 1998 18:04:58 +0300 (EEST) Message-ID: <19980821180458.39148@matti.ee> Date: Fri, 21 Aug 1998 18:04:58 +0300 From: Vallo Kallaste To: Edwin Culp Cc: current@FreeBSD.ORG Subject: Re: Problems with vx0 (3Com) Reply-To: vallo@matti.ee References: <199808211319.JAA14105@skynet.ctr.columbia.edu> <35DD7F0B.7EBFC645@webwizard.org.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <35DD7F0B.7EBFC645@webwizard.org.mx>; from Edwin Culp on Fri, Aug 21, 1998 at 09:07:08AM -0500 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Edwin Culp wrote: > Anybody tried it with the 3c595, that poor folks like us might still have? > > Thanks *** I can try. About what are you interested ? Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 08:06:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17491 for freebsd-current-outgoing; Fri, 21 Aug 1998 08:06:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17476 for ; Fri, 21 Aug 1998 08:06:36 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id KAA18429; Fri, 21 Aug 1998 10:02:13 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 21 Aug 1998 10:02:13 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: Poul-Henning Kamp cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter In-Reply-To: <377.903679209@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Aug 1998, Poul-Henning Kamp wrote: > > >*drool*... Just out of curiosity, what do these things cost? And can > >you get them with singlemode fiber interfaces? It is currently going > >to cost me about $10k for the conversion equipment to connect all of > >our buildings at 100Mbit (would need 10 100BTX -> singlemode > >converters. I have 5 remote buildings), and if I could just go > >directly between two of these cards (in FreeBSD boxes of course) with > >singlemode fiber I think I'd be in heaven. > > Why not consider ATM cards with single mode fiber then ? Hmm.. Well, its a thought. I will actually probably put a switch on one end of the fiber run, so i would need to find one with an ATM interface. I also don't know ATM all too well, so I'd kinda like to stick to Ethernet. It all comes down to price (and what is supported in FreeBSD), though. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (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 21 08:23:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20554 for freebsd-current-outgoing; Fri, 21 Aug 1998 08:23:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20545 for ; Fri, 21 Aug 1998 08:23:37 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id RAA00438; Fri, 21 Aug 1998 17:19:29 +0200 (CEST) To: Chris Dillon cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter In-reply-to: Your message of "Fri, 21 Aug 1998 10:02:13 CDT." Date: Fri, 21 Aug 1998 17:19:29 +0200 Message-ID: <436.903712769@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , >> >to cost me about $10k for the conversion equipment to connect all of >> >our buildings at 100Mbit (would need 10 100BTX -> singlemode >> >converters. I have 5 remote buildings), and if I could just go >> >directly between two of these cards (in FreeBSD boxes of course) with >> >singlemode fiber I think I'd be in heaven. >> >> Why not consider ATM cards with single mode fiber then ? > >Hmm.. Well, its a thought. I will actually probably put a switch on >one end of the fiber run, so i would need to find one with an ATM >interface. I also don't know ATM all too well, so I'd kinda like to >stick to Ethernet. It all comes down to price (and what is supported >in FreeBSD), though. FreeBSDs current ATM is about $1000/port for 155Mbit on copper, I don't know the singlemode prices. You can connect two such back-to-back, so you don't need a switch as such. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 08:38:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21896 for freebsd-current-outgoing; Fri, 21 Aug 1998 08:38:40 -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 IAA21883 for ; Fri, 21 Aug 1998 08:38:31 -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 RAA00186; Fri, 21 Aug 1998 17:37:31 +0200 (MET DST) Received: (from pb@localhost) by mars.hsc.fr (8.8.8/8.8.8/pb-19980526) id RAA07794; Fri, 21 Aug 1998 17:37:31 +0200 (CEST) (envelope-from pb) Message-ID: <19980821173730.A7689@mars.hsc.fr> Date: Fri, 21 Aug 1998 17:37:30 +0200 From: Pierre Beyssac To: Poul-Henning Kamp , Mike Smith Cc: Brian Somers , Brian Feldman , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? References: <199808210328.DAA07457@dingo.cdrom.com> <1380.903705634@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: <1380.903705634@critter.freebsd.dk>; from Poul-Henning Kamp on Fri, Aug 21, 1998 at 03:20:34PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 21, 1998 at 03:20:34PM +0200, Poul-Henning Kamp wrote: > >Please take this issue seriously. You can't just handwave and say > >"it's all APM's fault". > > Belive me, I'm taking this very seriously, but until I can make > it fail on one of my machines, I'll have a hard time fixing it. Maybe a first step should be : which code can we add to our kernels to help you track the bug ? I can put the code discussed by Brian Feldman and Brian Somers, is there anything else worth trying ? What's the best place to put a few printfs testing for weird conditions so we can begin to narrow it down progressively ? -- 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 Fri Aug 21 08:50:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23387 for freebsd-current-outgoing; Fri, 21 Aug 1998 08:50:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (mexcom.net.mx [207.249.162.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23239 for ; Fri, 21 Aug 1998 08:50:00 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (mexcom.net.mx [207.249.162.140]) by dns.webwizard.net.mx (8.8.8/8.8.7) with ESMTP id KAA06340; Fri, 21 Aug 1998 10:47:06 -0500 (CDT) Message-ID: <35DD967A.69EC860D@webwizard.org.mx> Date: Fri, 21 Aug 1998 10:47:06 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: vallo@matti.ee CC: current@FreeBSD.ORG Subject: Re: Problems with vx0 (3Com) References: <199808211319.JAA14105@skynet.ctr.columbia.edu> <35DD7F0B.7EBFC645@webwizard.org.mx> <19980821180458.39148@matti.ee> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vallo Kallaste wrote: > Edwin Culp wrote: > > > Anybody tried it with the 3c595, that poor folks like us might still have? > > > > Thanks > > *** > > I can try. About what are you interested ? > > Vallo Kallaste > vallo@matti.ee > So can I. I just wondered if anyone was using the xl0 with the 3c595 that I have about 25 of. Just being lazy. I will do a make world and build a new kernel and enjoy the surprise:-) I just did it, but on a machine with fxp0 (intel). Thanks again. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 09:00:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24928 for freebsd-current-outgoing; Fri, 21 Aug 1998 09:00:09 -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 IAA24822 for ; Fri, 21 Aug 1998 08:59:56 -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 MAA01333 for ; Fri, 21 Aug 1998 12:00:11 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 21 Aug 1998 12:00:10 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: current@FreeBSD.ORG Subject: PEBCAK with modunload. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG this might be fixed but i don't want to test it for obvious reasons. if you unload the linux emulator while linux programs are running you will crash your box. (forgot i had x11amp running) a nice thing would be an option to modunload to force an unload so it would work something like this: ~ % modstat Type Id Off Loadaddr Size Info Rev Module Name MISC 0 0 f614c000 0018 f6151000 1 ibcs2_mod EXEC 1 4 f6153000 0008 f6154000 1 ibcs2_coff_mod EXEC 2 5 f6155000 0020 f615c010 1 linux_mod ~ % modunload -i 3 Error: you have linux programs running. Specify -f to force. (list of pids/commands passed back somehow from the lkm) ~ % modunload -f -i 3 Killing all linux programs running. (list of pids follow, then the lkm is unloaded) btw i think PEBCAK = problem between chair and keyboard the reason this would be nice is that you can get "inuse" errors and other lkms can then refuse to unload unless told to forcfully do so. They could then revoke access to files/devices they control for other lkms such as filesystem lkms and device lkms. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 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 Fri Aug 21 09:05:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25804 for freebsd-current-outgoing; Fri, 21 Aug 1998 09:05:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from priscilla.mu.org (priscilla.mu.org [206.156.231.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25797 for ; Fri, 21 Aug 1998 09:05:14 -0700 (PDT) (envelope-from paul@priscilla.mu.org) Received: (from paul@localhost) by priscilla.mu.org (8.8.8/8.8.8) id LAA29560 for current@freebsd.org; Fri, 21 Aug 1998 11:04:19 -0500 (CDT) (envelope-from paul) Message-ID: <19980821110419.A29556@mu.org> Date: Fri, 21 Aug 1998 11:04:19 -0500 From: Paul Saab To: current@FreeBSD.ORG Subject: Re: Problems with vx0 (3Com) References: <199808211319.JAA14105@skynet.ctr.columbia.edu> <35DD7F0B.7EBFC645@webwizard.org.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <35DD7F0B.7EBFC645@webwizard.org.mx>; from Edwin Culp on Fri, Aug 21, 1998 at 09:07:08AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the vx driver will continue to work for the 3c590 and 3c595 cards. paul Edwin Culp (eculp@webwizard.org.mx) wrote: > Anybody tried it with the 3c595, that poor folks like us might still have? > > Thanks > > ed > > Bill Paul wrote: > > > Of all the gin joints in all the towns in all the world, Charlie ROOT > > had to walk into mine and say: > > > > > Hi > > > > > > Todays current doesn't see vx0 anymore... Help. > > > > Aw, couldn't you have provided more information that this? This is not > > enough to help you. It's not even enough to make a guess. (Well, maybe, > > but not an informed guess.) > > > > What kind of network card do you have that's supposed to be detected > > by the vx driver? A new driver (xl) was added recently to handle all of > > the 3Com Etherlink XL cards (3c900, 3c905 and 3c905B, which up until > > now was not supported. The vx driver supported some of these cards, > > but not fully and not very efficiently; support for the 3c90x cards > > in the vx driver was disabled so that the xl driver would detect them > > instead. Which one did you have, and did you look for xl0 instead of vx0? > > > > There are two things that could have gone wrong here: > > > > - The xl driver failed to detect your card, either because of a bug > > or because I screwed up somehow when I imported it (nobody else has > > complained about this so far though; I'll see if there's been a recent > > snapshot and snag a copy of the boot floppy to make sure it sees the > > cardson my systems). > > > > - You used an old kernel configuration file as opposed to GENERIC > > and your custom configuration doesn't specify the xl driver. If this > > is the case, add the following line your config file under where > > it says 'device vx0': > > > > device xl0 > > > > You will also need to edit your rc.conf file to use xl0 instead of > > vx0. > > > > - The driver is in the kernel and it did detect your card, but all you > > saw were the error messages from the rc scripts saying that there was > > no such interface as xl0. Check the dmesg output, and edit your > > /etc/rc.conf file as necessary. > > > > NOTE: If your card is a COMBO (like the 3c900 COMBO) and the driver > > selects the wrong media, use the ifmedia options to select the > > right one: > > > > # ifconfig xl0 media 10baseT/UTP (for RJ-45 twisted pair) > > # ifconfig xl0 media 10base2/BNC (for coax/thinnet) > > # ifconfig xl0 media 10base5/AUI (for AUI) > > > > You can also add the 'media foo' options to the 'interfaces' > > lines in your /etc/rc.conf to insure the right media is selected > > when the machine boots. > > > > For the TPO cards there's only one possible media so it can't > > get that wrong, and for the 100Mbps cards it should autoselect > > the speed and duplex modes. (You can still force a particular > > mode if you want.) > > > > -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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 09:21:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27665 for freebsd-current-outgoing; Fri, 21 Aug 1998 09:21:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27659 for ; Fri, 21 Aug 1998 09:21:01 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id SAA00556; Fri, 21 Aug 1998 18:13:53 +0200 (CEST) To: Pierre Beyssac cc: Mike Smith , Brian Somers , Brian Feldman , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Fri, 21 Aug 1998 17:37:30 +0200." <19980821173730.A7689@mars.hsc.fr> Date: Fri, 21 Aug 1998 18:13:53 +0200 Message-ID: <554.903716033@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980821173730.A7689@mars.hsc.fr>, Pierre Beyssac writes: >On Fri, Aug 21, 1998 at 03:20:34PM +0200, Poul-Henning Kamp wrote: >> >Please take this issue seriously. You can't just handwave and say >> >"it's all APM's fault". >> >> Belive me, I'm taking this very seriously, but until I can make >> it fail on one of my machines, I'll have a hard time fixing it. > >Maybe a first step should be : which code can we add to our kernels >to help you track the bug ? I need to know if you can reproduce it with APM set to a definitive state of "disabled". If you can reproduce it there, remove the call to init_timecounter() in sys/i386/isa/clock.c where it changes to the tsc_timecounter. printfs can be pretty lethal inside the clock/timecounter code, so be very careful with that. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 09:22:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28109 for freebsd-current-outgoing; Fri, 21 Aug 1998 09:22:57 -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 JAA28101 for ; Fri, 21 Aug 1998 09:22:53 -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 MAA14366; Fri, 21 Aug 1998 12:24:38 -0400 From: Bill Paul Message-Id: <199808211624.MAA14366@skynet.ctr.columbia.edu> Subject: Re: Problems with vx0 (3Com) To: vallo@matti.ee Date: Fri, 21 Aug 1998 12:24:37 -0400 (EDT) Cc: eculp@webwizard.org.mx, current@FreeBSD.ORG In-Reply-To: <19980821180458.39148@matti.ee> from "Vallo Kallaste" at Aug 21, 98 06:04:58 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, Vallo Kallaste had to walk into mine and say: > Edwin Culp wrote: > > > Anybody tried it with the 3c595, that poor folks like us might still have? > > > > Thanks > > *** > > I can try. About what are you interested ? The xl driver is for 3c90x cards only: this includes the 3c900 and 3c905 "boomerang" adapters and the 3c905B "cyclone" adapters. The 3c59x cards are based on the "vortex" chipset, which actually does have a DMA mechanism but not the same as the "boomerang" and "cyclone" chips. The "boomerang" chips happened to work with the vx driver because 3Com maintained support for the old PIO packet transfer mechanism that the vx driver uses. But starting with the 3c905B, the PIO mechanism was dropped and now bus-master DMA is required. Since all 3c90x cards support the same DMA interface, I decided to split out all of the 3c90x support from the vx driver. The vx driver is still used for the 3c59x PCI cards; I only turned off support in the vx driver for the Etherlink XL PCI cards, not the Etherlink III PCI cards. -Bill > > Vallo Kallaste > vallo@matti.ee > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- ============================================================================= -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 Fri Aug 21 09:50:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01215 for freebsd-current-outgoing; Fri, 21 Aug 1998 09:50:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (mexcom.net.mx [207.249.162.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01208 for ; Fri, 21 Aug 1998 09:50:22 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (mexcom.net.mx [207.249.162.140]) by dns.webwizard.net.mx (8.8.8/8.8.7) with ESMTP id LAA06991; Fri, 21 Aug 1998 11:47:29 -0500 (CDT) Message-ID: <35DDA4A1.CDD4D346@webwizard.org.mx> Date: Fri, 21 Aug 1998 11:47:29 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Bill Paul CC: vallo@matti.ee, current@FreeBSD.ORG Subject: Re: Problems with vx0 (3Com) References: <199808211624.MAA14366@skynet.ctr.columbia.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Paul wrote: > Of all the gin joints in all the towns in all the world, Vallo Kallaste > had to walk into mine and say: > > > Edwin Culp wrote: > > > > > Anybody tried it with the 3c595, that poor folks like us might still have? > > > > > > Thanks > > > > *** > > > > I can try. About what are you interested ? > > The xl driver is for 3c90x cards only: this includes the 3c900 and 3c905 > "boomerang" adapters and the 3c905B "cyclone" adapters. The 3c59x cards > are based on the "vortex" chipset, which actually does have a DMA mechanism > but not the same as the "boomerang" and "cyclone" chips. The "boomerang" > chips happened to work with the vx driver because 3Com maintained support > for the old PIO packet transfer mechanism that the vx driver uses. But > starting with the 3c905B, the PIO mechanism was dropped and now bus-master > DMA is required. Since all 3c90x cards support the same DMA interface, I > decided to split out all of the 3c90x support from the vx driver. > > The vx driver is still used for the 3c59x PCI cards; I only turned > off support in the vx driver for the Etherlink XL PCI cards, not the > Etherlink III PCI cards. > > -Bill Thanks a lot. You had me worried for a bit :-) ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 10:05:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03435 for freebsd-current-outgoing; Fri, 21 Aug 1998 10:05:52 -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 KAA03429 for ; Fri, 21 Aug 1998 10:05:51 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id JAA00556; Fri, 21 Aug 1998 09:44:50 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdvSd552; Fri Aug 21 16:44:45 1998 Date: Fri, 21 Aug 1998 09:44:42 -0700 (PDT) From: Julian Elischer To: Poul-Henning Kamp cc: Mike Smith , Brian Somers , Brian Feldman , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-Reply-To: <938.903694069@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG we get it all the time and our bios is not APM capable, nor is our 486DX4 CPU and custom motherboard. (If you don't believe me I can show you the BIOS sources :-). (well maybe not but you get the drift) julian On Fri, 21 Aug 1998, Poul-Henning Kamp wrote: > In message <199808210241.CAA05733@dingo.cdrom.com>, Mike Smith writes: > >> > >> >[...] the machine I was having problems with was > >> >running apm, so it used the i8254 timecounter rather than the tsc > >> >counter. > >> > >> Ahh... I bet that is it: APM sucks. > >> > >> Try to disable APM and see if you can reproduce it, I'll bet you > >> my collection of genuine 11 row punched cards that you can't. > > > >We've already had a respondent indicate that they are seeing the > >symptoms on non-APM systems. > > I didn't see that, and I doubt it until the repondent double-checks > his bios settings... > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 11:04:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09422 for freebsd-current-outgoing; Fri, 21 Aug 1998 11:04:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09416 for ; Fri, 21 Aug 1998 11:04:55 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id TAA00294; Fri, 21 Aug 1998 19:56:43 +0200 (CEST) To: Julian Elischer cc: Mike Smith , Brian Somers , Brian Feldman , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Fri, 21 Aug 1998 09:44:42 PDT." Date: Fri, 21 Aug 1998 19:56:37 +0200 Message-ID: <292.903722197@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Jul ian Elischer writes: >we get it all the time and our bios is not APM capable, nor is our 486DX4 >CPU and custom motherboard. (If you don't believe me I can show you >the BIOS sources :-). (well maybe not but you get the drift) Can't you send me one of those gadgets ? I can't seem to reproduce it here :-( -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 13:26:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25434 for freebsd-current-outgoing; Fri, 21 Aug 1998 13:26:28 -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 NAA25415 for ; Fri, 21 Aug 1998 13:26:24 -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 WAA26827; Fri, 21 Aug 1998 22:24:07 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Fri, 21 Aug 1998 22:24:06 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Poul-Henning Kamp cc: Chris Dillon , "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter In-Reply-To: <436.903712769@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Aug 1998, Poul-Henning Kamp wrote: > In message , > > >> >to cost me about $10k for the conversion equipment to connect all of > >> >our buildings at 100Mbit (would need 10 100BTX -> singlemode > >> >converters. I have 5 remote buildings), and if I could just go > >> >directly between two of these cards (in FreeBSD boxes of course) with > >> >singlemode fiber I think I'd be in heaven. > >> > >> Why not consider ATM cards with single mode fiber then ? > > > >Hmm.. Well, its a thought. I will actually probably put a switch on > >one end of the fiber run, so i would need to find one with an ATM > >interface. I also don't know ATM all too well, so I'd kinda like to > >stick to Ethernet. It all comes down to price (and what is supported > >in FreeBSD), though. > > FreeBSDs current ATM is about $1000/port for 155Mbit on copper, I don't > know the singlemode prices. You can connect two such back-to-back, > so you don't need a switch as such. Single-mode cards are very expensive (the optics), for short distances (several hundred meters) use multimode, the fiber is also much cheaper then. And yes, you don't need any switches - I use them exactly this way. As for the price... Frankly, I don't remember, the company paid for this :-), I vaguely remember something like $700 per multimode 155Mbps card. And the difference in pricing between single- and multi-mode card was something like 3:1. 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 21 13:31:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25992 for freebsd-current-outgoing; Fri, 21 Aug 1998 13:31:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25987 for ; Fri, 21 Aug 1998 13:31:20 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id PAA19325; Fri, 21 Aug 1998 15:27:00 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 21 Aug 1998 15:26:59 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: Poul-Henning Kamp cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter In-Reply-To: <436.903712769@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Aug 1998, Poul-Henning Kamp wrote: > In message , > > >> >to cost me about $10k for the conversion equipment to connect all of > >> >our buildings at 100Mbit (would need 10 100BTX -> singlemode > >> >converters. I have 5 remote buildings), and if I could just go > >> >directly between two of these cards (in FreeBSD boxes of course) with > >> >singlemode fiber I think I'd be in heaven. > >> > >> Why not consider ATM cards with single mode fiber then ? > > > >Hmm.. Well, its a thought. I will actually probably put a switch on > >one end of the fiber run, so i would need to find one with an ATM > >interface. I also don't know ATM all too well, so I'd kinda like to > >stick to Ethernet. It all comes down to price (and what is supported > >in FreeBSD), though. > > FreeBSDs current ATM is about $1000/port for 155Mbit on copper, I don't > know the singlemode prices. You can connect two such back-to-back, > so you don't need a switch as such. Well, that is already too expensive for what I need (I don't need the higher QoS or any of the other things ATM offers me... at least not yet). According to Pricewatch, I can get a Pro/1000 for $584. Not bad at all. According to Intel, it has a multi-mode interface with SC connectors, so I would need to buy a single/multi converter. If I can get one of those for $550 or less, I'm still way ahead. Stick a bunch of those in a FreeBSD box and I have myself a router, and I can eventually buy a gigabit layer3 IP switch (when the price comes down) to replace it and use all the gigabit cards in our servers. All for the same or less money than it would have cost me to do 100Mbit in my situation. Did I get lucky or does the industry just do this on purpose? :-) -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (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 21 16:50:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15621 for freebsd-current-outgoing; Fri, 21 Aug 1998 16:50:38 -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 QAA15610 for ; Fri, 21 Aug 1998 16:50:36 -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 TAA24470; Fri, 21 Aug 1998 19:49:35 -0400 (EDT) Date: Fri, 21 Aug 1998 19:49:34 -0400 (EDT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: Stefan Eggers cc: freebsd-current@FreeBSD.ORG Subject: Re: 13 months of user time? In-Reply-To: <199808210836.KAA02477@semyam.dinoco.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 Argh, you're right, I entirely forgot about having to handle the microsecond counter, that it's not like seconds since the epoch, and rolls over all the time ;) But in all these cases, it's a BIG change, so tv_usec shouldn't matter at all anyway, so the following should do: if (switchtime.tv_sec < p->p_switchtime.tv_sec) panic("%s at line %d: time check failed, time going backwards", __FILE__, __LINE__); Cheers, Brian Feldman On Fri, 21 Aug 1998, Stefan Eggers wrote: > > SIGXCPU kill problem could try putting the following in kern/kern_synch.c > > line 638: > > I think better not this one as that is a safe way to a panic IMHO. A > version I think does what you intend this to do I add below. It is > untested code I just added while writing the mail. > > > if (switchtime.tv_usec < p->p_switchtime.tv_usec || > > switchtime.tv_sec < p->p_switchtime.tv_sec) > > panic("bogus microuptime twiddling"); > > > > And see if we get some nice panics and cores. Is it worth a shot? I've > > As far as I can see the timeval in the process structure is a real > timeval and not abused to be something else. So tv_usec contains the > micro seconds part and tv_sec the seconds. > > Let's assume that p->p_switchtime.tv_usec contains 999999 now and > p->p_switchtime.tv_sec is 0. Lets suppose the time continues a little > bit and when we reach the if statement switchtime.tv_usec might > contain 0 and switchtime.tv_sec 1. The time didn't go backward but > with the code above causes a panic. > > > never gotten a SIGXCPU out of place, so my machine wouldn't be the one to > > test this on. > > And I don't think you want the test this way, anyway. ;-) > > One has first to calculate a 64 bit integer from the seconds and micro > seconds and then compare the two resulting numbers. With that it > could actually detect switchtime going backward. > > Something like this: > > int64_t time1, time2; > [...] > time1 = switchtime.tv_usec + switchtime.tv_sec * (int64_t)1000000; > time2 = p->p_switchtime.tv_usec + p->p_switchtime.tv_sec * (int64_t)1000000; > if (time1 < time2) > panic("Ooops! Switchtime going backward!"); > > Stefan. > -- > Stefan Eggers Lu4 yao2 zhi1 ma3 li4, > Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. > 51109 Koeln > Federal Republic of Germany > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 16:57:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16480 for freebsd-current-outgoing; Fri, 21 Aug 1998 16:57:47 -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 QAA16474 for ; Fri, 21 Aug 1998 16:57:44 -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 QAA10776; Fri, 21 Aug 1998 16:55:20 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808211655.QAA10776@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: 13 months of user time? In-reply-to: Your message of "Fri, 21 Aug 1998 04:53:10 GMT." <199808210453.EAA07850@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 16:55:18 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >Then in my case anyway, it's not a problem of disabling APM or not: > > >unless I'm severely mistaken about my motherboard (Asus T2P4) and > > >its BIOS settings, it's NOT an APM system. > > > > I think it has APM, check the BIOS setting... > > Only with recent BIOS upgrades. It doesn't support clock idling either. Actually, I should correct myself there; *if* I recall the part number correctly, that's a 430FX-based board, and I don't believe that said chipset supports clock idling of any sort. The clock may still "jump" forwards courtesy of SMI activity, etc. -- \\ 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 21 17:07:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17988 for freebsd-current-outgoing; Fri, 21 Aug 1998 17:07:30 -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 RAA17938 for ; Fri, 21 Aug 1998 17:07:22 -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 RAA10894; Fri, 21 Aug 1998 17:05:07 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808211705.RAA10894@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein cc: current@FreeBSD.ORG Subject: Re: PEBCAK with modunload. In-reply-to: Your message of "Fri, 21 Aug 1998 12:00:10 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 17:05:05 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > this might be fixed but i don't want to test it for obvious reasons. It's not; it demonstrates a flaw in the lkm system that's not trivially fixed. > if you unload the linux emulator while linux programs are running you will > crash your box. (forgot i had x11amp running) The "new lkm" system (kld) provides reference counting for modules, which will help alleviate this problem. You will probably just get EBUSY if you try to unload an "in use" module. -- \\ 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 21 17:09:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18666 for freebsd-current-outgoing; Fri, 21 Aug 1998 17:09:30 -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 RAA18640 for ; Fri, 21 Aug 1998 17:09:24 -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 RAA10862; Fri, 21 Aug 1998 17:00:25 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808211700.RAA10862@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp cc: Mike Smith , Brian Somers , Brian Feldman , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Fri, 21 Aug 1998 15:20:34 +0200." <1380.903705634@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 17:00:24 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >Please take this issue seriously. You can't just handwave and say > >"it's all APM's fault". > > Belive me, I'm taking this very seriously, but until I can make > it fail on one of my machines, I'll have a hard time fixing it. Ok. Do you have any instrumentation suggestions? I thought that it had "gone away" because I ran for a day without seeing anything, but then it came back for long enough to kill a couple of processes, then stopped happening again. All sorts of bizarre carry-related bugs suggest themselves, but I don't fully understand your new design. I am, however, more than happy to instrument the crap out of my kernel if it helps you find what's going on. -- \\ 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 21 17:11:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19235 for freebsd-current-outgoing; Fri, 21 Aug 1998 17:11:09 -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 RAA19230; Fri, 21 Aug 1998 17:11:06 -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 RAA04703; Fri, 21 Aug 1998 17:10:19 -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: Fri, 21 Aug 1998 17:10:17 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: FreeBSD Questions To: FreeBSD Questions , FreebSD Current Subject: gcc 2.8 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anybody here useing gcc 2.8 to compile world and/or kernel? --------------------- William Woods Date: 21-Aug-98 / Time: 17:09:39 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 Fri Aug 21 18:12:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28826 for freebsd-current-outgoing; Fri, 21 Aug 1998 18:12:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mordred.cs.ucla.edu (Mordred.CS.UCLA.EDU [131.179.48.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28820 for ; Fri, 21 Aug 1998 18:12:30 -0700 (PDT) (envelope-from scottm@mordred.cs.ucla.edu) Received: from mordred.cs.ucla.edu (localhost [127.0.0.1]) by mordred.cs.ucla.edu (8.9.1/8.8.8) with ESMTP id SAA23303 for ; Fri, 21 Aug 1998 18:11:47 -0700 (PDT) (envelope-from scottm@mordred.cs.ucla.edu) Message-Id: <199808220111.SAA23303@mordred.cs.ucla.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter In-reply-to: Your message of "Fri, 21 Aug 1998 22:24:06 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 18:11:45 -0700 From: Scott Michel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [slightly off topic] Ewwwwwwwww! Friends never let friends build networks with ATM unless absolutely necessary and even then ... It'd be like perpetrating an MS Operating system on someone. If the network can't support mcast naturally, should we really be using it? The good news is that ATM is being relegated to the dust heap of history now that PPP/Packet over Sonet is operational. All we need now is operational PCI bus cards. > > FreeBSDs current ATM is about $1000/port for 155Mbit on copper, I don't > > know the singlemode prices. You can connect two such back-to-back, > > so you don't need a switch as such. > > Single-mode cards are very expensive (the optics), for short distances > (several hundred meters) use multimode, the fiber is also much cheaper > then. And yes, you don't need any switches - I use them exactly this way. > As for the price... Frankly, I don't remember, the company paid for this > :-), I vaguely remember something like $700 per multimode 155Mbps card. > And the difference in pricing between single- and multi-mode card was > something like 3:1. > > 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 Fri Aug 21 19:38:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11512 for freebsd-current-outgoing; Fri, 21 Aug 1998 19:38:31 -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 TAA11492 for ; Fri, 21 Aug 1998 19:38:27 -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 TAA11913; Fri, 21 Aug 1998 19:36:04 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808211936.TAA11913@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Felipe Garcia cc: current@FreeBSD.ORG Subject: Re: Problems with vx0 (3Com) In-reply-to: Your message of "Fri, 21 Aug 1998 16:02:32 +0200." <35DD7DF8.FE395CF7@kkeka.ericsson.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 19:36:03 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Does what is stated below affect FreeBSD? now that vx has became tx with > DMA? vx has become xl (as previously noted). The issues outlined in the Sun announcement are quite valid; note that the only chipsets that are listed as having problems are the '430LX and early '450GX sets. The former are quite rare (only found on very old Pentium boards), and the latter even more so (mostly only found on very old, expensive Pentium Pro boards). There are a substantial number of chipsets *not* listed in the Sun announcement, (anything not from Intel, 430VX, 430TX, 440LX, 440BX, etc.) however I don't believe that the problem is likely to resurface. Unless you posess one of these extremely old and mouldy boards, don't worry about it. -- \\ 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 21 20:48:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19118 for freebsd-current-outgoing; Fri, 21 Aug 1998 20:48:36 -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 UAA19101 for ; Fri, 21 Aug 1998 20:48:33 -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 0zA4eZ-0003tc-00; Fri, 21 Aug 1998 20:47:47 -0700 Date: Fri, 21 Aug 1998 20:47:44 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Scott Michel cc: freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter In-Reply-To: <199808220111.SAA23303@mordred.cs.ucla.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 Fri, 21 Aug 1998, Scott Michel wrote: > [slightly off topic] > > Ewwwwwwwww! Friends never let friends build networks with ATM unless > absolutely necessary and even then ... It'd be like perpetrating an > MS Operating system on someone. If the network can't support mcast > naturally, should we really be using it? More important to me, is the ATM overhead of 10 to 15%. On a 155mbs OC3 link, 10 to 20mbs is wasted! You can justify ATM overhead for mixed applications, but if you just want to push IP traffic around, you'd better off using clear channel routed links. > The good news is that ATM is being relegated to the dust heap of > history now that PPP/Packet over Sonet is operational. All we need > now is operational PCI bus cards. Yep. I wonder if AGP slots can be used for non-video applications? AGP has about 4 times the bandwidth of PCI. Of course, you can only have on such adapter. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 21:01:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20768 for freebsd-current-outgoing; Fri, 21 Aug 1998 21:01:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20755 for ; Fri, 21 Aug 1998 21:01:16 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id VAA02960; Fri, 21 Aug 1998 21:00:29 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808220400.VAA02960@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Tom cc: Scott Michel , freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter In-reply-to: Your message of "Fri, 21 Aug 1998 20:47:44 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Aug 1998 21:00:29 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yep. I wonder if AGP slots can be used for non-video applications? AGP > has about 4 times the bandwidth of PCI. Of course, you can only have > on such adapter. >From little reading that I have done on AGP is ideal for very fast networking and also I don't see why it has to be limited to one adapter thats more of the function of the interface to the board or how a designer choses to interface its internal components . Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 21:46:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24234 for freebsd-current-outgoing; Fri, 21 Aug 1998 21:46:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Tandem.com (suntan.tandem.com [192.216.221.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24218 for ; Fri, 21 Aug 1998 21:46:20 -0700 (PDT) (envelope-from bruceb@panther.mpd.tandem.com) Received: from fedex.austx.tandem.com (fedex.austx.tandem.com [131.124.250.27]) by Tandem.com (8.8.8/2.0.1) with ESMTP id VAA20943 for ; Fri, 21 Aug 1998 21:45:38 -0700 (PDT) Received: from panther.mpd.tandem.com (panther.austx.tandem.com [131.124.4.106]) by fedex.austx.tandem.com (8.9.0/8.9.0) with ESMTP id XAA22538 for ; Fri, 21 Aug 1998 23:43:37 -0500 (CDT) Received: (from bruceb@localhost) by panther.mpd.tandem.com (8.8.5/8.7.1) id XAA14086 for freebsd-current@FreeBSD.ORG; Fri, 21 Aug 1998 23:43:36 -0500 (CDT) Message-Id: <199808220443.XAA14086@panther.mpd.tandem.com> Subject: OOPS! Missed a turn with CVSUP... To: freebsd-current@FreeBSD.ORG Date: Fri, 21 Aug 1998 23:43:35 -0500 (CDT) From: "Bruce Burden" Reply-To: bruceb@austx.tandem.com 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 Okay, somewhere I missed a turn with cvsup, or more properly, with cvs. I note that the CVSROOT is now /home/ncvs. Okay, fine, but /home/ncvs/CVSROOT is SIGNIFICANTLY different from what I have. So, where do I find the information to get my /home/ncvs/CVSROOT and everything else back in sync with what is happening in the freebsd world? Thanks, Bruce -- ------------------------------------------------------------------------------- Bruce Burden bruceb@isd.tandem.com Tandem Computers Inc. 512-432-8944 Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 22:14:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26625 for freebsd-current-outgoing; Fri, 21 Aug 1998 22:14:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26609 for ; Fri, 21 Aug 1998 22:14:46 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id HAA03073; Sat, 22 Aug 1998 07:10:37 +0200 (CEST) To: Scott Michel cc: freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter In-reply-to: Your message of "Fri, 21 Aug 1998 18:11:45 PDT." <199808220111.SAA23303@mordred.cs.ucla.edu> Date: Sat, 22 Aug 1998 07:10:33 +0200 Message-ID: <3033.903762633@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808220111.SAA23303@mordred.cs.ucla.edu>, Scott Michel writes: >[slightly off topic] > >Ewwwwwwwww! Friends never let friends build networks with ATM unless >absolutely necessary and even then ... It'd be like perpetrating an >MS Operating system on someone. If the network can't support mcast >naturally, should we really be using it? > >The good news is that ATM is being relegated to the dust heap of >history now that PPP/Packet over Sonet is operational. All we need >now is operational PCI bus cards. Could you please move this to Hyde Park Corner ? or -chat ? The reality is, that you can buy ATM as a service from your telco, not Packet over Sonet which requires you to have the entire fiber. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 21 22:24:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27587 for freebsd-current-outgoing; Fri, 21 Aug 1998 22:24:34 -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 WAA27566; Fri, 21 Aug 1998 22:24:27 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id AAA19739; Sat, 22 Aug 1998 00:23:34 -0500 (EST) (envelope-from toor) Message-Id: <199808220523.AAA19739@dyson.iquest.net> Subject: Re: softupdates and smp crash In-Reply-To: <199808200641.XAA18028@usr02.primenet.com> from Terry Lambert at "Aug 20, 98 06:41:53 am" To: tlambert@primenet.com (Terry Lambert) Date: Sat, 22 Aug 1998 00:23:34 -0500 (EST) Cc: sos@FreeBSD.ORG, tlambert@primenet.com, croot@btp1da.phy.uni-bayreuth.de, regnauld@deepo.prosa.dk, current@FreeBSD.ORG, smp@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 Terry Lambert said: > > > > So we can still say that softupdates are broken, at least for SMP. > > > > > > It would be more useful (than saying this) for people to characterize > > > the problem they are getting so that we can find a discriminitory > > > value. I suggest: > > > > I suggest reading Luoqi Chen's exelent explanation as why it breaks > > under SMP (hint: it has nothing todo with HW setups).. > > Perhaps clock speed? 8-). > > His post arrived in my mailbox after I responded to your post... > > I'm also not convinced that this is the only possible cause of > the problem; the VM code is hardly "assert" protected everywhere, > so diagnosing this thing is not trivial. Look at the VM fixes > I recently did, which killed the bugs Karl Denniger was seeing > in 75% of the cases, leaving 25% of the cases "clustered" (in his > words), indicating a seperate problem, in addition to the ones I > fixed, in a periodically executing code path. I had suspected > that this would be the case when I made the fix, since it doesn't > account for the buggy behaviour I'm personally seeing. 8-(. > I have to chime in here -- some of the "fixes" are work-arounds, and there are still underlying VM problems. It might be "good enough" for 3.0, but I would suggest preparing for some rework to find the root cause for the problem. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 03:28:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16054 for freebsd-current-outgoing; Sat, 22 Aug 1998 03:28:18 -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 DAA16049 for ; Sat, 22 Aug 1998 03:28:15 -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 DAA14111; Sat, 22 Aug 1998 03:23:54 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808220323.DAA14111@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: bruceb@austx.tandem.com cc: freebsd-current@FreeBSD.ORG Subject: Re: OOPS! Missed a turn with CVSUP... In-reply-to: Your message of "Fri, 21 Aug 1998 23:43:35 EST." <199808220443.XAA14086@panther.mpd.tandem.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 Aug 1998 03:23:53 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Okay, somewhere I missed a turn with cvsup, or more properly, > with cvs. I note that the CVSROOT is now /home/ncvs. Okay, fine, > but /home/ncvs/CVSROOT is SIGNIFICANTLY different from what I have. CVSROOT is wherever you put the CVS repository. > So, where do I find the information to get my /home/ncvs/CVSROOT > and everything else back in sync with what is happening in the > freebsd world? If your repository is seriously out of sync, I'd recommend blowing it away and trying 'pkg_add ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz' -- \\ 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 22 05:06:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24115 for freebsd-current-outgoing; Sat, 22 Aug 1998 05:06:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from darkstar.psa.at (uvo-42.univie.ac.at [131.130.230.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24109 for ; Sat, 22 Aug 1998 05:06:50 -0700 (PDT) (envelope-from root@darkstar.psa.at) Received: (from root@localhost) by darkstar.psa.at (8.8.8/8.8.8) id NAA00394; Sat, 22 Aug 1998 13:50:32 +0200 (CEST) (envelope-from root) Message-ID: <19980822135031.A358@compufit.at> Date: Sat, 22 Aug 1998 13:50:31 +0200 From: Alexander Sanda To: wwoods@cybcon.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc 2.8 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from William Woods on Fri, Aug 21, 1998 at 05:10:17PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 21, 1998 at 05:10:17PM -0700, William Woods wrote: > Anybody here useing gcc 2.8 to compile world and/or kernel? gcc-2.8.1 has some problems with current kernel source (as of last weekend). However, I have installed gcc-2.8.1 from the packages collection, and I have the vague feeling, that this compiler has some problems. I compiled one of my kde apps, using -O2 and -mpentiumpro and the app started to segfault occasionally. Since I recompiled with gcc-2.7.2.1, it never segfaulted again... Moving to gcc-2.8.x or egcs/pgcc makes sense for bigger C++ projects (like KDE for example). The C land doesn't gain much from it. The processor-specific optimizations (-mpentiumpro e.g.) won't give you a faster kernel. At least, this is true in the Linux world - the kernel itself contains handmade processor-specific optimizations, which - of course - work better than any compiler generated optimizations. Once a while ago, I did some experiments with compiling the Linux kernel using different compilers (stock gcc-2.7, egcs, pgcc) and benchmarking them with lmbench or byte. The results: They all ranged within measurement tolerance, imho. Even if you run lmbench twice on the same system, the results will slightly differ. For kernel code, any compiler-induced problem can be lethal and will probably result in an unstable system. Bad enough, those bugs would be extremely hard to track. As far as we all know, gcc-2.7.2.1 produces ok code. Known problems (if any, I'am not an expert here) can be workarounded by the really skilled kernel hackers. Moving to another compiler will perhaps introduce new problems - as long as the performance gain is practically non-existant, this is not very desireable. -- # /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 22 07:18:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05903 for freebsd-current-outgoing; Sat, 22 Aug 1998 07:18:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.pipeline.ch (freefall.pipeline.ch [195.134.128.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05894 for ; Sat, 22 Aug 1998 07:18:10 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.140.6]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA335; Sat, 22 Aug 1998 16:15:46 +0200 Message-ID: <35DED2F1.B646CAA3@pipeline.ch> Date: Sat, 22 Aug 1998 16:17:21 +0200 From: Andre Oppermann Organization: Internet Business Solutions Ltd. X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: Tom CC: Scott Michel , freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom wrote: > > On Fri, 21 Aug 1998, Scott Michel wrote: > > > [slightly off topic] > > > > Ewwwwwwwww! Friends never let friends build networks with ATM unless > > absolutely necessary and even then ... It'd be like perpetrating an > > MS Operating system on someone. If the network can't support mcast > > naturally, should we really be using it? > > More important to me, is the ATM overhead of 10 to 15%. On a 155mbs OC3 > link, 10 to 20mbs is wasted! You can justify ATM overhead for mixed > applications, but if you just want to push IP traffic around, you'd better > off using clear channel routed links. I thought it was even more, 20%-30%. What really sucks on ATM is when the link gets saturated, then ATM begins to drop random cells and kills whole IP packets. If that happens you're lost. 1% cell loss on ATM can give 30% packet loss on IP (it depends on traffic pattern, packet size, etc.). > > The good news is that ATM is being relegated to the dust heap of > > history now that PPP/Packet over Sonet is operational. All we need > > now is operational PCI bus cards. > > Yep. I wonder if AGP slots can be used for non-video applications? AGP > has about 4 times the bandwidth of PCI. Of course, you can only have > on such adapter. Even PCI should be enough for two or three cards (155Mbit/s are 19MByte/s and PCI can do 130MByte/s, at least on paper). The problem with APG is that there is only one slot allowed... -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 08:11:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10271 for freebsd-current-outgoing; Sat, 22 Aug 1998 08:11:56 -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 IAA10254; Sat, 22 Aug 1998 08:11:54 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id IAA01902; Sat, 22 Aug 1998 08:07:23 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdVj1897; Sat Aug 22 15:07:14 1998 Date: Sat, 22 Aug 1998 08:07:12 -0700 (PDT) From: Julian Elischer To: "John S. Dyson" cc: Terry Lambert , sos@FreeBSD.ORG, croot@btp1da.phy.uni-bayreuth.de, regnauld@deepo.prosa.dk, current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: softupdates and smp crash In-Reply-To: <199808220523.AAA19739@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 Sat, 22 Aug 1998, John S. Dyson wrote: > I have to chime in here -- some of the "fixes" are work-arounds, and > there are still underlying VM problems. It might be "good enough" > for 3.0, but I would suggest preparing for some rework to find the > root cause for the problem. > We all agree john, but we have not got a suitable set of people who really understand that code yet... several people are doing "voyages of discovery" but we do not yet have a "slot-in replacement" for you :-) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 08:19:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11495 for freebsd-current-outgoing; Sat, 22 Aug 1998 08:19:41 -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 IAA11488 for ; Sat, 22 Aug 1998 08:19:34 -0700 (PDT) (envelope-from pb@fasterix.frmug.org) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id RAA26453; Sat, 22 Aug 1998 17:13:34 +0200 (CEST) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.8.8/8.8.5/pb-19970302) id RAA00898; Sat, 22 Aug 1998 17:13:19 +0200 (CEST) Message-ID: <19980822171319.A487@fasterix.frmug.fr.net> Date: Sat, 22 Aug 1998 17:13:19 +0200 From: Pierre Beyssac To: Poul-Henning Kamp , Pierre Beyssac Cc: Mike Smith , Brian Somers , Brian Feldman , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? References: <19980821173730.A7689@mars.hsc.fr> <554.903716033@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: <554.903716033@critter.freebsd.dk>; from Poul-Henning Kamp on Fri, Aug 21, 1998 at 06:13:53PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 21, 1998 at 06:13:53PM +0200, Poul-Henning Kamp wrote: > I need to know if you can reproduce it with APM set to a definitive > state of "disabled". Yes. I've just checked my setup, and my BIOS APM setting was already "disabled" from the beginning. > If you can reproduce it there, remove the call to init_timecounter() > in sys/i386/isa/clock.c where it changes to the tsc_timecounter. Ok. I'm also trying to get more SIGXCPU's to be able to say if it changes anything :) -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.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 22 09:11:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16234 for freebsd-current-outgoing; Sat, 22 Aug 1998 09:11:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley-186-113.res.iastate.edu (friley-186-113.res.iastate.edu [129.186.186.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16226 for ; Sat, 22 Aug 1998 09:11:45 -0700 (PDT) (envelope-from mystify@friley-186-113.res.iastate.edu) Received: from friley-186-113.res.iastate.edu (loopback [127.0.0.1]) by friley-186-113.res.iastate.edu (8.9.1/8.8.8) with ESMTP id LAA17860 for ; Sat, 22 Aug 1998 11:11:01 -0500 (CDT) (envelope-from mystify@friley-186-113.res.iastate.edu) Message-Id: <199808221611.LAA17860@friley-186-113.res.iastate.edu> To: freebsd-current@FreeBSD.ORG Subject: Not receiving CVS commit messages Date: Sat, 22 Aug 1998 11:11:00 -0500 From: Patrick Hartling Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For some time now, I have not been receiving any CVS commit logs. I'm on several such lists and have tried unsubscribing and resubscribing. I don't know exactly when I stopped receiving the commit messages, but I think it was around mid to late July. Did I miss something about a change in policy? Thanks. -Patrick Patrick L. Hartling | Research Assistant, ICEMT mystify@friley-186-113.res.iastate.edu | SE Lab - 1117 Black Engineering http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 10:15:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20277 for freebsd-current-outgoing; Sat, 22 Aug 1998 10:15:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20272 for ; Sat, 22 Aug 1998 10:15:32 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id MAA10094; Sat, 22 Aug 1998 12:14:49 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id MAA10426; Sat, 22 Aug 1998 12:14:17 -0500 Message-ID: <19980822121417.21415@right.PCS> Date: Sat, 22 Aug 1998 12:14:17 -0500 From: Jonathan Lemon To: Patrick Hartling Cc: freebsd-current@FreeBSD.ORG Subject: Re: Not receiving CVS commit messages References: <199808221611.LAA17860@friley-186-113.res.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199808221611.LAA17860@friley-186-113.res.iastate.edu>; from Patrick Hartling on Aug 08, 1998 at 11:11:00AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Aug 08, 1998 at 11:11:00AM -0500, Patrick Hartling wrote: > For some time now, I have not been receiving any CVS commit logs. I'm on > several such lists and have tried unsubscribing and resubscribing. I don't > know exactly when I stopped receiving the commit messages, but I think it was > around mid to late July. Did I miss something about a change in policy? I believe that the postmaster dropped all the cvs-* mailing lists, except for cvs-all. The rationale was that almost nobody was subscribed to the lists; even the token-ring list had more readers. Another reasons was probably to cut down on the amount of crossposting that was being done between the lists. 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. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 10:21:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20833 for freebsd-current-outgoing; Sat, 22 Aug 1998 10:21:28 -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 KAA20816; Sat, 22 Aug 1998 10:21:24 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id MAA02475; Sat, 22 Aug 1998 12:20:27 -0500 (EST) (envelope-from toor) Message-Id: <199808221720.MAA02475@dyson.iquest.net> Subject: Re: softupdates and smp crash In-Reply-To: from Julian Elischer at "Aug 22, 98 08:07:12 am" To: julian@whistle.com (Julian Elischer) Date: Sat, 22 Aug 1998 12:20:27 -0500 (EST) Cc: dyson@iquest.net, tlambert@primenet.com, sos@FreeBSD.ORG, croot@btp1da.phy.uni-bayreuth.de, regnauld@deepo.prosa.dk, current@FreeBSD.ORG, smp@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 Julian Elischer said: > > > On Sat, 22 Aug 1998, John S. Dyson wrote: > > > I have to chime in here -- some of the "fixes" are work-arounds, and > > there are still underlying VM problems. It might be "good enough" > > for 3.0, but I would suggest preparing for some rework to find the > > root cause for the problem. > > > > We all agree john, but we have not got a suitable set of people who really > understand that code yet... several people are doing "voyages of > discovery" but we do not yet have a "slot-in replacement" for you :-) > That wasn't clear. The "fix" to the page_remove code has really concerned me. The effort was good, but I am still thinking about where the problem really is. I wasn't meaning to put the effort down, and I think that Terry is a person who has a good chance of figuring the code out to the point of being creative with it. (Even though some-people think that he is sometimes "off the wall", I also don't think that some-people listen to him *enough*.) He has been in contact with me, and I am certainly willing to help him. Especially after meetings personally with him, I trust his ability to comprehend and create. (For VM code, I also believe that some of the Alpha people, and others who were helping even when I was actively working on the code, are able to take off where I left it.) None of the VM stuff is brain surgery, but there are some end cases that I believe have BOTH existed since day one, and also some problems that I might have caused. Those who are actually working on/with the code should feel very free to contact me. This strategy has apparently been fairly successful, with not only Terry, but others who have just chatted with me about other technical things. The locking situations and critical region problems are existant throughout the VFS and VM code (and probably in other places too.) I am working to help solve those sorts of problems coherently and completely in another forum. However, when I can help (without totally distracting me in my new work), I will (and do.) FreeBSD's success is still important to me, so using me as a resource when I can help effectively is okay. My current schedule is quite full, but use me when you need to. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 11:09:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24886 for freebsd-current-outgoing; Sat, 22 Aug 1998 11:09:55 -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 LAA24881 for ; Sat, 22 Aug 1998 11:09:53 -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 0zAI5i-0000a5-00; Sat, 22 Aug 1998 11:08:42 -0700 Date: Sat, 22 Aug 1998 11:08:40 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Andre Oppermann cc: Scott Michel , freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter In-Reply-To: <35DED2F1.B646CAA3@pipeline.ch> 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, 22 Aug 1998, Andre Oppermann wrote: > > Yep. I wonder if AGP slots can be used for non-video applications? AGP > > has about 4 times the bandwidth of PCI. Of course, you can only have > > on such adapter. > > Even PCI should be enough for two or three cards (155Mbit/s are > 19MByte/s > and PCI can do 130MByte/s, at least on paper). Gigabit ethernet is 125MB/s, so would use more of PCI. The only hope is multiple independant PCI buses (some motherboards already have this). > The problem with APG is that there is only one slot allowed... Apparently not. Apparently AGP is very good for fast network interfaces. > -- > Andre > > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 14:36:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08720 for freebsd-current-outgoing; Sat, 22 Aug 1998 14:36:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sumter.awod.com (sumter.awod.com [208.140.99.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08715 for ; Sat, 22 Aug 1998 14:36:40 -0700 (PDT) (envelope-from klam@awod.com) Received: from tsunami..awod.com (wa0237.tnt1-56k.awod.com [208.140.98.237]) by sumter.awod.com (8.8.7/8.8.8) with SMTP id RAA05210; Sat, 22 Aug 1998 17:35:28 -0400 (EDT) (envelope-from klam@awod.com) Message-Id: <3.0.3.32.19980822173527.033939f8@awod.com> X-Sender: klam@awod.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sat, 22 Aug 1998 17:35:27 -0400 To: Tom , Andre Oppermann From: Ken Lam Subject: Re: Intel PRO/1000 Gigabit Adapter Cc: Scott Michel , freebsd-current@FreeBSD.ORG In-Reply-To: References: <35DED2F1.B646CAA3@pipeline.ch> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:08 AM 8/22/98 -0700, Tom wrote: > >On Sat, 22 Aug 1998, Andre Oppermann wrote: > >> > Yep. I wonder if AGP slots can be used for non-video applications? AGP >> > has about 4 times the bandwidth of PCI. Of course, you can only have >> > on such adapter. >> >> Even PCI should be enough for two or three cards (155Mbit/s are >> 19MByte/s >> and PCI can do 130MByte/s, at least on paper). > > Gigabit ethernet is 125MB/s, so would use more of PCI. The only hope is >multiple independant PCI buses (some motherboards already have this). Well, Micron's Samurai chipset and the new Intel Server chipset have 64bit pci. Not to say that either is supported, or that there are 64bit NIC cards. I've seen the 64bit pci video, though. -k To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 15:35:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13584 for freebsd-current-outgoing; Sat, 22 Aug 1998 15:35:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13565 for ; Sat, 22 Aug 1998 15:34:59 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id PAA05215; Sat, 22 Aug 1998 15:32:13 -0700 (PDT) Message-Id: <199808222232.PAA05215@implode.root.com> To: Ken Lam cc: Tom , Andre Oppermann , Scott Michel , freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit Adapter In-reply-to: Your message of "Sat, 22 Aug 1998 17:35:27 EDT." <3.0.3.32.19980822173527.033939f8@awod.com> From: David Greenman Reply-To: dg@root.com Date: Sat, 22 Aug 1998 15:32:13 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >At 11:08 AM 8/22/98 -0700, Tom wrote: >> >>On Sat, 22 Aug 1998, Andre Oppermann wrote: >> >>> > Yep. I wonder if AGP slots can be used for non-video applications? >AGP >>> > has about 4 times the bandwidth of PCI. Of course, you can only have >>> > on such adapter. >>> >>> Even PCI should be enough for two or three cards (155Mbit/s are >>> 19MByte/s >>> and PCI can do 130MByte/s, at least on paper). >> >> Gigabit ethernet is 125MB/s, so would use more of PCI. The only hope is >>multiple independant PCI buses (some motherboards already have this). > >Well, Micron's Samurai chipset and the new Intel Server chipset have 64bit >pci. >Not to say that either is supported, or that there are 64bit NIC cards. I've >seen the 64bit pci video, though. All of the gigabit ethernet cards I've seen are 64bit PCI. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 15:45:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15112 for freebsd-current-outgoing; Sat, 22 Aug 1998 15:45:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-92.ppp.wenet.net [206.15.84.92]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15100 for ; Sat, 22 Aug 1998 15:45:34 -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 PAA20595; Sat, 22 Aug 1998 15:45:54 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sat, 22 Aug 1998 15:45:53 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Alexander Sanda cc: wwoods@cybcon.com, freebsd-current@FreeBSD.ORG Subject: Re: gcc 2.8 In-Reply-To: <19980822135031.A358@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 Sat, 22 Aug 1998, Alexander Sanda wrote: [...] > However, I have installed gcc-2.8.1 from the packages collection, and I > have the vague feeling, that this compiler has some problems. I > compiled one of my kde apps, using -O2 and -mpentiumpro and the app > started to segfault occasionally. Since I recompiled with gcc-2.7.2.1, > it never segfaulted again... I think this is an a.out problem. I'm using egcs from their anon cvs repository, and after building ELF libs and X (and all other X related goodies), egcs works wonderfully. I don't have any major cli C++ programs, so I didn't bother with building an ELF world. gdb seems to be the only stumbling block for me. [...] > Once a while ago, I did some experiments with compiling the Linux kernel > using different compilers (stock gcc-2.7, egcs, pgcc) and benchmarking > them with lmbench or byte. The results: They all ranged within > measurement tolerance, imho. Even if you run lmbench twice on the same > system, the results will slightly differ. I think the P5 (not clones) benefits more from compiler optimizations than do other chips (esp. the P6). > For kernel code, any compiler-induced problem can be lethal and will > probably result in an unstable system. Bad enough, those bugs would be > extremely hard to track. Fair enough, but I've built kernels with gcc 2.8 and earlier egcs snapshots, and pgcc and it's worked well for me. > As far as we all know, gcc-2.7.2.1 produces ok code. Known problems (if > any, I'am not an expert here) can be workarounded by the really skilled > kernel hackers. Moving to another compiler will perhaps introduce new > problems - as long as the performance gain is practically non-existant, > this is not very desireable. gcc 2.7 produces OK code, however, it's C++ support is really quite lacking. If you bend over backwards far enough to support it (which I have done) you really do miss out on some of the more fun features. Even Windows has the Unix world beat here (IBM and Sun's C++ compilers are far more broken than any post 2.6 gcc). I think most of the problems you'll encounter with newer compilers will be related to using a.out, and shared a.out libs, I think that since x86 Linux is such a popular platform, most code generation problems that would inflict pain on the FreeBSD will have been quashed long ago. - alex A person who has both feet planted firmly in the air can be safely called a liberal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 16:00:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16096 for freebsd-current-outgoing; Sat, 22 Aug 1998 16:00:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from localhost.my.domain (ppp1606.on.bellglobal.com [206.172.249.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16067 for ; Sat, 22 Aug 1998 15:59:58 -0700 (PDT) (envelope-from hoek@FreeBSD.ORG) Received: from localhost (tim@localhost) by localhost.my.domain (8.8.8/8.8.8) with SMTP id SAA00994; Sat, 22 Aug 1998 18:58:37 -0400 (EDT) (envelope-from ac199@hwcn.org) X-Authentication-Warning: localhost.my.domain: tim owned process doing -bs Date: Sat, 22 Aug 1998 18:58:36 -0400 (EDT) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: Jonathan Lemon cc: Patrick Hartling , freebsd-current@FreeBSD.ORG Subject: Re: Not receiving CVS commit messages In-Reply-To: <19980822121417.21415@right.PCS> 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, 22 Aug 1998, Jonathan Lemon wrote: > I believe that the postmaster dropped all the cvs-* mailing > lists, except for cvs-all. The rationale was that almost Actually, I think it was wosch. He did so because jmb (the postmaster) had accidentally caused all commit messages cross-posted to several cvs-* lists to bounce. When jmb fixed this condition, no one bothered to re-enable the posting of commit messages to each relevant cvs-* list. At least, that's how I understand what happened. :-) Since it took this long to get even one complaint, I doubt anyone's going to re-enable this again, soon... -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 17:09:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21900 for freebsd-current-outgoing; Sat, 22 Aug 1998 17:09:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley-186-113.res.iastate.edu (friley-186-113.res.iastate.edu [129.186.186.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21895 for ; Sat, 22 Aug 1998 17:09:40 -0700 (PDT) (envelope-from mystify@friley-186-113.res.iastate.edu) Received: from friley-186-113.res.iastate.edu (loopback [127.0.0.1]) by friley-186-113.res.iastate.edu (8.9.1/8.8.8) with ESMTP id TAA01173; Sat, 22 Aug 1998 19:02:51 -0500 (CDT) (envelope-from mystify@friley-186-113.res.iastate.edu) Message-Id: <199808230002.TAA01173@friley-186-113.res.iastate.edu> Reply-to: Patrick Hartling To: ac199@hwcn.org cc: Jonathan Lemon , freebsd-current@FreeBSD.ORG Subject: Re: Not receiving CVS commit messages In-reply-to: Message from Tim Vanderhoek of "Sat, 22 Aug 1998 18:58:36 EDT." Date: Sat, 22 Aug 1998 19:02:51 -0500 From: Patrick Hartling Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ac199@hwcn.org wrote: } Since it took this long to get even one complaint, I doubt } anyone's going to re-enable this again, soon... Well, I personally would like to see it re-enabled simply because I don't want to get every single commit but would like to follow kernel changes and other things. Prior to being on cvs-all, I was using slocal to sort incoming commit logs into appropriate folders based on the sender. Now I'm experimenting with sorting by subject which I know could be unreliable, but it's the best slocal can do in this case. I've always preferred having mail sent to separate lists over the way NetBSD does it, for example, but that's just my opinion. -Patrick Patrick L. Hartling | Research Assistant, ICEMT mystify@friley-186-113.res.iastate.edu | SE Lab - 1117 Black Engineering http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 17:21:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24035 for freebsd-current-outgoing; Sat, 22 Aug 1998 17:21:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d6.dialup.hilink.com.au [203.2.144.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24026 for ; Sat, 22 Aug 1998 17:21:49 -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 RAA20220; Sat, 22 Aug 1998 17:19:04 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808221719.RAA20220@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alex cc: Alexander Sanda , wwoods@cybcon.com, freebsd-current@FreeBSD.ORG Subject: Re: gcc 2.8 In-reply-to: Your message of "Sat, 22 Aug 1998 15:45:53 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 Aug 1998 17:19:03 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 22 Aug 1998, Alexander Sanda wrote: > [...] > > However, I have installed gcc-2.8.1 from the packages collection, and I > > have the vague feeling, that this compiler has some problems. I > > compiled one of my kde apps, using -O2 and -mpentiumpro and the app > > started to segfault occasionally. Since I recompiled with gcc-2.7.2.1, > > it never segfaulted again... > > I think this is an a.out problem. That's an interesting assertion. Unfortunately, the parts of GCC that generate bad code and the parts that produce the output object format aren't really related. It's also been observed that egcs is only producing worthwhile code on i386 and sparc, and the alpha is becoming very important for us. > I'm using egcs from their anon cvs > repository, and after building ELF libs and X (and all other X related > goodies), egcs works wonderfully. I don't have any major cli C++ > programs, so I didn't bother with building an ELF world. gdb seems to be > the only stumbling block for me. Try building the rest of the world, and run with it for a few weeks. Agreed, we need better C++ support. But obtaining it at the price of damaging the operating system itself is not a tradeoff I think any of us would be happy with. -- \\ 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 22 19:15:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04449 for freebsd-current-outgoing; Sat, 22 Aug 1998 19:15:28 -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 TAA04444 for ; Sat, 22 Aug 1998 19:15:26 -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 TAA12847; Sat, 22 Aug 1998 19:15:43 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sat, 22 Aug 1998 19:15:42 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Mike Smith cc: Alexander Sanda , wwoods@cybcon.com, freebsd-current@FreeBSD.ORG Subject: Re: gcc 2.8 In-Reply-To: <199808221719.RAA20220@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 Sat, 22 Aug 1998, Mike Smith wrote: [..] > > I think this is an a.out problem. > > That's an interesting assertion. Unfortunately, the parts of GCC that > generate bad code and the parts that produce the output object format > aren't really related. Well, with an a.out system, gcc 2.8.1 with all the latest patches from the port linked all my KDE apps and whatnot, but they all segfaulted when they ran. The egcs "snapshot" I was using, generated static kde libs fine, but some apps tended to segfault, but generally refused to create useable position independant code (multiply defined symbols). > It's also been observed that egcs is only producing worthwhile code on > i386 and sparc, and the alpha is becoming very important for us. I've heard it been observed from Linux/Alpha users that gcc has very poor 64 bit optimizations anyways. I think I've heard somewhere on one of these fbsd lists that it's not so much a problem paying people to do these types of optimizations, as it is finding the talent to do the grunt work. I wonder if compensation could persuade some Cygnus folks to work a little bit more on the Alpha bits. > Try building the rest of the world, and run with it for a few weeks. Been there, done that. I've got no reason to really do it again, until perhaps, perl5 gets imported. > Agreed, we need better C++ support. But obtaining it at the price of > damaging the operating system itself is not a tradeoff I think any of > us would be happy with. Yes, but is egcs really _worse_ than gcc 2.7 on the Alpha, or is just not as improved as the x86? Ideally I'd love to see TenDRA imported... Either way, I really haven't seen egcs break any C code, and hell if they got gnat working with it.. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 19:35:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06851 for freebsd-current-outgoing; Sat, 22 Aug 1998 19:35:33 -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 TAA06845 for ; Sat, 22 Aug 1998 19:35:29 -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 ; Sat, 22 Aug 1998 22:33:48 -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 ; Sat, 22 Aug 1998 19:33:47 -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 ; Sat, 22 Aug 1998 22:33:46 -0400 (EDT) X-Mailer: exmh version 2.0.2 2/24/98 To: Alex cc: Mike Smith , Alexander Sanda , wwoods@cybcon.com, freebsd-current@FreeBSD.ORG Subject: Re: gcc 2.8 In-Reply-To: Alex's (garbanzo@hooked.net) message dated Sat, 22 Aug 1998 19:15:42. 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: Sat, 22 Aug 1998 22:33:46 -0400 Message-ID: <20089.903839626@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While it's been several months since I last did a performance comparison between TenDRA and gcc/egcs, I remember that the TenDRA-compiled code was significantly slower than the code produced by gcc or egcs. I could be mistaken. OTOH, I have some code that uses some "extensions" provided by gcc (labels as values) that I just haven't figured out how to get TenDRA to compile. It's no big deal if this code won't compile with TenDRA - it would just give me another set of routines where I could do a performance test. I think I'll try compiling another package with TenDRA that has a "useful" benchmark. I'll let folks know if I learn anything new. 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 22 19:47:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08220 for freebsd-current-outgoing; Sat, 22 Aug 1998 19:47:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08201 for ; Sat, 22 Aug 1998 19:47:51 -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 MAA32617; Sun, 23 Aug 1998 12:16:40 +0930 (CST) Received: by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA32123; Sun, 23 Aug 1998 12:16:39 +0930 Date: Sun, 23 Aug 1998 12:16:38 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@mercury To: Mike Smith Cc: Alex , Alexander Sanda , wwoods@cybcon.com, freebsd-current@FreeBSD.ORG Subject: Re: gcc 2.8 In-Reply-To: <199808221719.RAA20220@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 Sat, 22 Aug 1998, Mike Smith wrote: > > I'm using egcs from their anon cvs > > repository, and after building ELF libs and X (and all other X related > > goodies), egcs works wonderfully. I don't have any major cli C++ > > programs, so I didn't bother with building an ELF world. gdb seems to be > > the only stumbling block for me. > > Try building the rest of the world, and run with it for a few weeks. For what it's worth, I've been using egcs (-O2 -mpentium -march=pentium) to compile my kernel and all the compilable parts of the world for some time now (there are about 10 things which egcs can't compile at present). I haven't experienced any problems whatsoever with things misbehaving or crashing randomly; in fact at the moment my system is about the most stable it's been all year. When I encounter a suspicious problem with a utility, I'll usually try recompiling it with gcc to see if it might be a compiler problem - but all the problems so far have been to do with current itself. I don't know whether there's any benefit to be gained by doing what I'm doing but it does at least seem to work :-) > Agreed, we need better C++ support. But obtaining it at the price of > damaging the operating system itself is not a tradeoff I think any of > us would be happy with. For the record, most of the C++ stuff in the source tree is not compilable with egcs..from memory the other parts which I have to compile with gcc are due to extra compiler warnings which cause compilation to fail (i.e. warnings treated as errors), the lkms (egcs doesnt have -aout) and the biosboot stuff (exceeds maximum length). Kris > \\ 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 22 19:56:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09424 for freebsd-current-outgoing; Sat, 22 Aug 1998 19:56:10 -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 TAA09412 for ; Sat, 22 Aug 1998 19:56:03 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id TAA16964; Sat, 22 Aug 1998 19:55:19 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd016956; Sat Aug 22 19:55:17 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id TAA20534; Sat, 22 Aug 1998 19:55:16 -0700 (MST) From: Terry Lambert Message-Id: <199808230255.TAA20534@usr04.primenet.com> Subject: Re: PEBCAK with modunload. To: bright@www.hotjobs.com (Alfred Perlstein) Date: Sun, 23 Aug 1998 02:55:16 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: from "Alfred Perlstein" at Aug 21, 98 12:00:10 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 > this might be fixed but i don't want to test it for obvious reasons. > > if you unload the linux emulator while linux programs are running you will > crash your box. (forgot i had x11amp running) Return non-zero from the LKM unload code in the module to veto unloading. > ~ % modunload -i 3 > Error: you have linux programs running. Specify -f to force. > (list of pids/commands passed back somehow from the lkm) Already possible to veto unload. The message is problematic, but can be implemented using a console message (kernel printf) for minimal function. > ~ % modunload -f -i 3 > Killing all linux programs running. > (list of pids follow, then the lkm is unloaded) Also possible, from within the kernel module, if you are willing to potentially hang the modunload in an ioctl on /dev/lkm (ie: a blocking device driver control to the lkm pseudo-device). This should not be a big problem, but it's a potential one. > the reason this would be nice is that you can get "inuse" errors and other > lkms can then refuse to unload unless told to forcfully do so. They could > then revoke access to files/devices they control for other lkms such as > filesystem lkms and device lkms. All LKM's are permitted to refuse unload. Whether or not they actually do so is implementation defined. The ability to crash the system is one of the reasons LKM twiddilng is limited to root credentialed processes. Busy system calls and filesystems are relatively trivial; the close being called only on last close of a device is problematic for resource tracking purposes, but if all you need is an "is everyone out of the pool?" mechanism, that's pretty trivial as well. I believe my sample LKM for system calls tracked usage an vetoed unload. To implement "drain", you need merely to disable the entry point, per the normal unload process, but not unload until the reference count goes to zero. This will require that you implement using a "generic" rather than a type-specific LKM type, to allow you to catch the vetoed unload request and actually prohibit future access to the device, system call, etc.. The normal semantics of a refusal to unload assume that the user space program wanting the unload will retry again later, and that subsequent reentry is not a problem. 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 Sat Aug 22 20:01:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10171 for freebsd-current-outgoing; Sat, 22 Aug 1998 20:01:39 -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 UAA10158 for ; Sat, 22 Aug 1998 20:01:37 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id UAA06089; Sat, 22 Aug 1998 20:00:54 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd006075; Sat Aug 22 20:00:49 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id UAA20904; Sat, 22 Aug 1998 20:00:48 -0700 (MST) From: Terry Lambert Message-Id: <199808230300.UAA20904@usr04.primenet.com> Subject: Re: gcc 2.8 To: entropy@compufit.at (Alexander Sanda) Date: Sun, 23 Aug 1998 03:00:48 +0000 (GMT) Cc: wwoods@cybcon.com, freebsd-current@FreeBSD.ORG In-Reply-To: <19980822135031.A358@compufit.at> from "Alexander Sanda" at Aug 22, 98 01:50:31 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 > > Anybody here useing gcc 2.8 to compile world and/or kernel? > > gcc-2.8.1 has some problems with current kernel source (as of last > weekend). > > However, I have installed gcc-2.8.1 from the packages collection, and I > have the vague feeling, that this compiler has some problems. I > compiled one of my kde apps, using -O2 and -mpentiumpro and the app > started to segfault occasionally. Since I recompiled with gcc-2.7.2.1, > it never segfaulted again... Be aware that using DESTDIR at all will result in your compiler getting the gcc 2.7.2 rather than the 2.8.1 headers and libgcc.a. FreeBSD (incorrectly) overrides these values in the .mk files (see the files /usr/share/mk/bsd.prog.mk and /usr/share/mk/bsd.lib.mk for details). So it is at least unsuitable for building the world (without you hacking these files) and probably unsuitable for building ports in the context of a build hierarchy. > Once a while ago, I did some experiments with compiling the Linux kernel > using different compilers (stock gcc-2.7, egcs, pgcc) and benchmarking > them with lmbench or byte. The results: They all ranged within > measurement tolerance, imho. Even if you run lmbench twice on the same > system, the results will slightly differ. Now try the very old (and small) gcc 1.x that we used to use. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 20:01:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10264 for freebsd-current-outgoing; Sat, 22 Aug 1998 20:01:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d6.dialup.hilink.com.au [203.2.144.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10213 for ; Sat, 22 Aug 1998 20:01:47 -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 TAA21095; Sat, 22 Aug 1998 19:59:23 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808221959.TAA21095@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kris Kennaway cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc 2.8 In-reply-to: Your message of "Sun, 23 Aug 1998 12:16:38 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 Aug 1998 19:59:21 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 22 Aug 1998, Mike Smith wrote: > > > > I'm using egcs from their anon cvs > > > repository, and after building ELF libs and X (and all other X related > > > goodies), egcs works wonderfully. I don't have any major cli C++ > > > programs, so I didn't bother with building an ELF world. gdb seems to be > > > the only stumbling block for me. > > > > Try building the rest of the world, and run with it for a few weeks. > > For what it's worth, I've been using egcs (-O2 -mpentium -march=pentium) > to compile my kernel and all the compilable parts of the world for some > time now (there are about 10 things which egcs can't compile at present). > I haven't experienced any problems whatsoever with things misbehaving or > crashing randomly; in fact at the moment my system is about the most > stable it's been all year. This is a useful datapoint, thanks. > For the record, most of the C++ stuff in the source tree is not compilable > with egcs..from memory the other parts which I have to compile with gcc > are due to extra compiler warnings which cause compilation to fail (i.e. > warnings treated as errors), the lkms (egcs doesnt have -aout) and the > biosboot stuff (exceeds maximum length). All of these are interesting. - Why won't it compile the C++ code (ie. groff)? is there a newer groff that does build? - Can you submit fixes to these build killers as PRs? - Which parts of the biosboot code grow with egcs? By how much? Thanks for your input; this sort of monitoring and evaluation is where the real answers come from. -- \\ 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 22 20:07:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11263 for freebsd-current-outgoing; Sat, 22 Aug 1998 20:07:05 -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 UAA11245 for ; Sat, 22 Aug 1998 20:07:02 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id UAA18972; Sat, 22 Aug 1998 20:06:20 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd018953; Sat Aug 22 20:06:14 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id UAA21114; Sat, 22 Aug 1998 20:06:07 -0700 (MST) From: Terry Lambert Message-Id: <199808230306.UAA21114@usr04.primenet.com> Subject: Re: gcc 2.8 To: garbanzo@hooked.net (Alex) Date: Sun, 23 Aug 1998 03:06:07 +0000 (GMT) Cc: mike@smith.net.au, entropy@compufit.at, wwoods@cybcon.com, freebsd-current@FreeBSD.ORG In-Reply-To: from "Alex" at Aug 22, 98 07:15:42 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 > Well, with an a.out system, gcc 2.8.1 with all the latest patches from the > port linked all my KDE apps and whatnot, but they all segfaulted when they > ran. The egcs "snapshot" I was using, generated static kde libs fine, but > some apps tended to segfault, but generally refused to create useable > position independant code (multiply defined symbols). Compile it with the 2.8.1 headers and libraries instead of the ones you will get by default when installing gcc 2.8.1 as a port. > I've heard it been observed from Linux/Alpha users that gcc has very poor > 64 bit optimizations anyways. I think I've heard somewhere on one of > these fbsd lists that it's not so much a problem paying people to do these > types of optimizations, as it is finding the talent to do the grunt work. > I wonder if compensation could persuade some Cygnus folks to work a little > bit more on the Alpha bits. The Digital developed Alpha pipeline reordering code has been (and still is) downloadable from gatekeeper.dec.com. > > Agreed, we need better C++ support. But obtaining it at the price of > > damaging the operating system itself is not a tradeoff I think any of > > us would be happy with. > > Yes, but is egcs really _worse_ than gcc 2.7 on the Alpha, or is just not > as improved as the x86? Ideally I'd love to see TenDRA imported... Me too, but it will be a lot of work; I was hoping to piggy-back off of some of the Alpha work, which will have, by necessity, seperated out the machine dependent pieces, like inline assembly, that make TenDRA unhappy. Of course, TenDRA is also ELF-centric in the installers, at this point (just more work that needs doing...). > Either way, I really haven't seen egcs break any C code, and hell if they > got gnat working with it.. I have seen it break per thread exceptions stacks in multithreaded C++ code, but you can fix this if you are willing to link all of your non-threaded programs with libc_r (fat chance, that...). 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 Sat Aug 22 20:18:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12868 for freebsd-current-outgoing; Sat, 22 Aug 1998 20:18:22 -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 UAA12859 for ; Sat, 22 Aug 1998 20:18:19 -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 MAA00092; Sun, 23 Aug 1998 12:47:35 +0930 (CST) Received: by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA31192; Sun, 23 Aug 1998 12:47:34 +0930 Date: Sun, 23 Aug 1998 12:47:34 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@mercury To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc 2.8 In-Reply-To: <199808221959.TAA21095@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 Sat, 22 Aug 1998, Mike Smith wrote: > > For the record, most of the C++ stuff in the source tree is not compilable > > with egcs..from memory the other parts which I have to compile with gcc > > are due to extra compiler warnings which cause compilation to fail (i.e. > > warnings treated as errors), the lkms (egcs doesnt have -aout) and the > > biosboot stuff (exceeds maximum length). > > All of these are interesting. > > - Why won't it compile the C++ code (ie. groff)? is there a newer > groff that does build? > - Can you submit fixes to these build killers as PRs? > - Which parts of the biosboot code grow with egcs? By how much? 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 narrow anything down. I am sure that someone else with more experience 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 probably some nonconformity in the source which egcs is picking up on. I can however investigate whether I can get a newer gnu groff to compile with egcs. 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 22 20:20:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13193 for freebsd-current-outgoing; Sat, 22 Aug 1998 20:20:19 -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 UAA13172; Sat, 22 Aug 1998 20:20:14 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id UAA04959; Sat, 22 Aug 1998 20:19:31 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd004906; Sat Aug 22 20:19:23 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id UAA21616; Sat, 22 Aug 1998 20:19:17 -0700 (MST) From: Terry Lambert Message-Id: <199808230319.UAA21616@usr04.primenet.com> Subject: Re: softupdates and smp crash To: dyson@iquest.net Date: Sun, 23 Aug 1998 03:19:16 +0000 (GMT) Cc: tlambert@primenet.com, sos@FreeBSD.ORG, croot@btp1da.phy.uni-bayreuth.de, regnauld@deepo.prosa.dk, current@FreeBSD.ORG, smp@FreeBSD.ORG In-Reply-To: <199808220523.AAA19739@dyson.iquest.net> from "John S. Dyson" at Aug 22, 98 00:23:34 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 > > I'm also not convinced that this is the only possible cause of > > the problem; the VM code is hardly "assert" protected everywhere, > > so diagnosing this thing is not trivial. Look at the VM fixes > > I recently did, which killed the bugs Karl Denniger was seeing > > in 75% of the cases, leaving 25% of the cases "clustered" (in his > > words), indicating a seperate problem, in addition to the ones I > > fixed, in a periodically executing code path. I had suspected > > that this would be the case when I made the fix, since it doesn't > > account for the buggy behaviour I'm personally seeing. 8-(. > > > I have to chime in here -- some of the "fixes" are work-arounds, and > there are still underlying VM problems. It might be "good enough" > for 3.0, but I would suggest preparing for some rework to find the > root cause for the problem. Can you identify which of the "better fixes" are workarounds? The two fixes I have done, and now have enough confidence in to want them committed, are: o The "valid = 0 at wrong time" that you told me about. o The "setting the recorded size of a backing object to a page boundary instead of to the actual size". You could argue that this second, which promiscuously sets the vnode object size after instancing the object, is a workaround which should be repaired by adding a "real_size" parameter to the allocator, but the fact is that the setsize code path is not a problem at the only time when it is called (ie: it can't be called at interrupt level as a result of a disk I/O completion interrupt); so the window I noted has been analyzed, and is not there. The code is ugly, but it does the intended job, without side effects. The other "fix", the "back up one" is, indeed, a kludge that happens to work for some cases, but I would not want that one committed (I explicitly posted that it should be tried as a dianostic). The only other changes packaged with the two real changes, above, are panics in the diagnostic case, which is basically an "assert" that map contents aren't being stomped on page insertion, and a lock acquisition logging that was arguably erroneously missing. I haven't been able to get anyone to run with the "DIAGNOSTIC" flag to test the first nor the "MAP_LOCK_DIAGNOSTIC" for the second (but they run without error here, where I can't trigger the failures at will). 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 Sat Aug 22 20:24:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13918 for freebsd-current-outgoing; Sat, 22 Aug 1998 20:24:00 -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 UAA13901; Sat, 22 Aug 1998 20:23:56 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id WAA01043; Sat, 22 Aug 1998 22:22:58 -0500 (EST) (envelope-from toor) Message-Id: <199808230322.WAA01043@dyson.iquest.net> Subject: Re: softupdates and smp crash In-Reply-To: <199808221720.MAA02475@dyson.iquest.net> from "John S. Dyson" at "Aug 22, 98 12:20:27 pm" To: dyson@iquest.net Date: Sat, 22 Aug 1998 22:22:58 -0500 (EST) Cc: julian@whistle.com, dyson@iquest.net, tlambert@primenet.com, sos@FreeBSD.ORG, croot@btp1da.phy.uni-bayreuth.de, regnauld@deepo.prosa.dk, current@FreeBSD.ORG, smp@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John S. Dyson said: > completely in another forum. However, when I can help (without totally > distracting me in my new work), I will (and do.) > > FreeBSD's success is still important to me, so using me as a resource > when I can help effectively is okay. My current schedule is quite full, > but use me when you need to. > Following up on my posting: I am porting my (SMP) patches to -current for my own use. I have found a few bugs and incompatibilites, bug will make the patches available. (I want to upgrade to a more current -current for stability and feature reasons, but don't want to loose any of the performance features that I have been using.) I will be leaving out the improved vnode dirty buffer queuing (which improves sync times, with non-softupdate filesystems.) -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 20:27:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14535 for freebsd-current-outgoing; Sat, 22 Aug 1998 20:27:07 -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 UAA14489; Sat, 22 Aug 1998 20:26:52 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id WAA01058; Sat, 22 Aug 1998 22:26:04 -0500 (EST) (envelope-from toor) Message-Id: <199808230326.WAA01058@dyson.iquest.net> Subject: Re: softupdates and smp crash In-Reply-To: <199808230319.UAA21616@usr04.primenet.com> from Terry Lambert at "Aug 23, 98 03:19:16 am" To: tlambert@primenet.com (Terry Lambert) Date: Sat, 22 Aug 1998 22:26:04 -0500 (EST) Cc: dyson@iquest.net, tlambert@primenet.com, sos@FreeBSD.ORG, croot@btp1da.phy.uni-bayreuth.de, regnauld@deepo.prosa.dk, current@FreeBSD.ORG, smp@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 Terry Lambert said: > > The other "fix", the "back up one" is, indeed, a kludge that happens > to work for some cases, but I would not want that one committed (I > explicitly posted that it should be tried as a dianostic). > That is what worried me. Since I don't track the cvs tree very closely any more, I was mistakenly under the false impression that change was adopted. Other than that, your stuff appears to be pretty good!!! As I posted (perhaps in another forum -- or not?!?!), I'll be making available an updated version of my SMP and pmap improvements (Since I don't want to loose anything.) It might be a good time for someone to look at the code seriously for bugs/etc, and perhaps adoption. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 20:27:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14808 for freebsd-current-outgoing; Sat, 22 Aug 1998 20:27:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com ([208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14778 for ; Sat, 22 Aug 1998 20:27:52 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-144.camalott.com [208.229.74.144]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id WAA20753; Sat, 22 Aug 1998 22:27:48 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA07414; Sat, 22 Aug 1998 22:26:07 -0500 (CDT) (envelope-from joelh) Date: Sat, 22 Aug 1998 22:26:07 -0500 (CDT) Message-Id: <199808230326.WAA07414@detlev.UUCP> To: Harlan.Stenn@pfcs.com CC: garbanzo@hooked.net, mike@smith.net.au, entropy@compufit.at, wwoods@cybcon.com, freebsd-current@FreeBSD.ORG In-reply-to: <20089.903839626@brown.pfcs.com> (message from Harlan Stenn on Sat, 22 Aug 1998 22:33:46 -0400) Subject: Re: gcc 2.8 From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <20089.903839626@brown.pfcs.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While it's been several months since I last did a performance > comparison between TenDRA and gcc/egcs, I remember that the > TenDRA-compiled code was significantly slower than the code produced > by gcc or egcs. I've got most of a test suite I hacked together. Mostly benchmark type stuff, but it's better than nothing. It compares both compiler speed and emitted code speed. If there is significant interest, I can rerun it against various compilers (send me URLs or ports names) and post the results. 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 22 20:33:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15781 for freebsd-current-outgoing; Sat, 22 Aug 1998 20:33:35 -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 UAA15775; Sat, 22 Aug 1998 20:33:33 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id UAA07547; Sat, 22 Aug 1998 20:32:50 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd007505; Sat Aug 22 20:32:43 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id UAA22340; Sat, 22 Aug 1998 20:32:35 -0700 (MST) From: Terry Lambert Message-Id: <199808230332.UAA22340@usr04.primenet.com> Subject: Re: softupdates and smp crash To: dyson@iquest.net Date: Sun, 23 Aug 1998 03:32:35 +0000 (GMT) Cc: julian@whistle.com, tlambert@primenet.com, sos@FreeBSD.ORG, croot@btp1da.phy.uni-bayreuth.de, regnauld@deepo.prosa.dk, current@FreeBSD.ORG, smp@FreeBSD.ORG In-Reply-To: <199808221720.MAA02475@dyson.iquest.net> from "John S. Dyson" at Aug 22, 98 12:20:27 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 > That wasn't clear. The "fix" to the page_remove code has really concerned > me. The effort was good, but I am still thinking about where the problem > really is. Are you talking about the initial diagnostic fix, which was never intended for integration (I would have squawked over a commit), the "backup one", or the "valid = 0" fix, based on your suggestion? I'm pretty sure that I understand the ramifications of the "valid = 0" fix enough that I think that it is "right". I'd like to put another panic in vm_page.c, where the kludge for "9-Jan-93" XXX; I think it's a kludge, but I doubt a panic there would make me very popular. 8-). > The locking situations and critical region problems are existant > throughout the VFS and VM code (and probably in other places too.) I > am working to help solve those sorts of problems coherently and > completely in another forum. However, when I can help (without totally > distracting me in my new work), I will (and do.) The locking stuff is noted; I have the copy of your diffs, and I'm slowly going through them with your list of what should and should not be taken, in hand. For the most part, these appear to be SMP issues, and unrelated to the problems I'm seeing. For what it's worth, I believe the two fixes I want in will do nothing for the problems I'm seeing; one was from you, and the other was from my own code review of what I felt was the place to look for the contact lens "because that's where the light is". David Greenamn made the suggestion that I look instead at the vfs_bio code for my own problems; that, of course, is "where the light isn't", but it's a good suggestion anyway, and I'm looking... 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 20:36:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16234 for freebsd-current-outgoing; Sat, 22 Aug 1998 20:36:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16220; Sat, 22 Aug 1998 20:36:16 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199808230336.UAA16220@hub.freebsd.org> Subject: Re: Not receiving CVS commit messages In-Reply-To: from Tim Vanderhoek at "Aug 22, 98 06:58:36 pm" To: ac199@hwcn.org Date: Sat, 22 Aug 1998 20:36:16 -0700 (PDT) Cc: jlemon@americantv.com, mystify@friley-186-113.res.iastate.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tim Vanderhoek wrote: > On Sat, 22 Aug 1998, Jonathan Lemon wrote: > > > I believe that the postmaster dropped all the cvs-* mailing > > lists, except for cvs-all. The rationale was that almost > > Actually, I think it was wosch. He did so because jmb (the > postmaster) had accidentally caused all commit messages > cross-posted to several cvs-* lists to bounce. When jmb fixed > this condition, no one bothered to re-enable the posting of > commit messages to each relevant cvs-* list. that's what i remember. > > At least, that's how I understand what happened. :-) > > 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. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 20:57:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18792 for freebsd-current-outgoing; Sat, 22 Aug 1998 20:57:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-70.ppp.wenet.net [206.15.84.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18780 for ; Sat, 22 Aug 1998 20:56:49 -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 UAA02646; Sat, 22 Aug 1998 20:52:23 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sat, 22 Aug 1998 20:51:57 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Kris Kennaway cc: Mike Smith , Alexander Sanda , wwoods@cybcon.com, freebsd-current@FreeBSD.ORG Subject: 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 Sun, 23 Aug 1998, Kris Kennaway wrote: [...] > > Agreed, we need better C++ support. But obtaining it at the price of > > damaging the operating system itself is not a tradeoff I think any of > > us would be happy with. > > For the record, most of the C++ stuff in the source tree is not compilable > with egcs..from memory the other parts which I have to compile with gcc > are due to extra compiler warnings which cause compilation to fail (i.e. > warnings treated as errors), the lkms (egcs doesnt have -aout) and the > biosboot stuff (exceeds maximum length). This is somewhat bogus. The libg++ and stdc++ in the source tree will be ditched anyways (as they should be), as will lkms. What do you mean that it exceeds maximum length? As for the rest.. I'm sure it's easily fixed. - 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 Sat Aug 22 21:01:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19393 for freebsd-current-outgoing; Sat, 22 Aug 1998 21:01:07 -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 VAA19388 for ; Sat, 22 Aug 1998 21:01:04 -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 NAA00481; Sun, 23 Aug 1998 13:30:19 +0930 (CST) Received: by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA30586; Sun, 23 Aug 1998 13:30:19 +0930 Date: Sun, 23 Aug 1998 13:30:18 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@mercury To: Alex Cc: freebsd-current@FreeBSD.ORG Subject: 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 Sat, 22 Aug 1998, Alex wrote: > > For the record, most of the C++ stuff in the source tree is not compilable > > with egcs..from memory the other parts which I have to compile with gcc > > are due to extra compiler warnings which cause compilation to fail (i.e. > > warnings treated as errors), the lkms (egcs doesnt have -aout) and the > > biosboot stuff (exceeds maximum length). > > This is somewhat bogus. The libg++ and stdc++ in the source tree will be > ditched anyways (as they should be), as will lkms. What do you mean that > it exceeds maximum length? As for the rest.. I'm sure it's easily fixed. By this, I mean these parts of the source tree, as supplied in -current, do not compile with egcs (either due to incompatibilities between the C++ include files, incompatible language semantics, missing compiler features (-aout) or whatever). If the broken parts are discarded in the future, then all the better :) The biosboot code needs to be below a certain length to fit in the bootblock (or something), and egcs compiling this code produces a result which exceeds this length. Mike is renovating the bootstrap code at the moment, so this probably isnt a big problem. As for easily fixed, I'm sure at least some of it is, but since I don't have the skills to do it myself I'm not going ot make a big deal out of it :-) 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 22 22:38:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01795 for freebsd-current-outgoing; Sat, 22 Aug 1998 22:38:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-26.ppp.wenet.net [206.15.84.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01790 for ; Sat, 22 Aug 1998 22:38: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 WAA03132; Sat, 22 Aug 1998 22:39:17 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sat, 22 Aug 1998 22:39:15 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Kris Kennaway cc: freebsd-current@FreeBSD.ORG Subject: 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 Sun, 23 Aug 1998, Kris Kennaway wrote: [..] > As for easily fixed, I'm sure at least some of it is, but since I don't have > the skills to do it myself I'm not going ot make a big deal out of it :-) Well, it's better that something is said of it before it's released ;) - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 22 23:23:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04383 for freebsd-current-outgoing; Sat, 22 Aug 1998 23:23:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-26.ppp.wenet.net [206.15.84.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04378 for ; Sat, 22 Aug 1998 23:23:33 -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 XAA23144; Sat, 22 Aug 1998 23:22:57 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sat, 22 Aug 1998 23:22:56 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Mike Smith cc: Kris Kennaway , freebsd-current@FreeBSD.ORG Subject: Re: gcc 2.8 In-Reply-To: <199808221959.TAA21095@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 Sat, 22 Aug 1998, Mike Smith wrote: [...] > - Why won't it compile the C++ code (ie. groff)? is there a newer > groff that does build? > - Can you submit fixes to these build killers as PRs? > - Which parts of the biosboot code grow with egcs? By how much? > > Thanks for your input; this sort of monitoring and evaluation is where > the real answers come from. groff built just fine for me (I just tested it), did need to install osfcn.h tho, which would be a non issue if egcs was properly integrated (as it's installed in /usr/include/g++, where egcs doesn't look). - 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