From owner-freebsd-current Sun Jun 1 00:10:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA10679 for current-outgoing; Sun, 1 Jun 1997 00:10:35 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA10674; Sun, 1 Jun 1997 00:10:32 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id AAA09117; Sun, 1 Jun 1997 00:10:23 -0700 (PDT) Message-Id: <199706010710.AAA09117@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: John Hay cc: gpalmer@FreeBSD.ORG (Gary Palmer), freebsd-current@FreeBSD.ORG Subject: Re: ucd-snmp-3.1.3 doesn't like FreeBSD3? In-reply-to: Your message of "Sat, 01 Jun 1997 08:21:04 +0200." <199706010621.IAA05068@angel.cids.org.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Jun 1997 00:10:23 -0700 From: Amancio Hasty Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Please post the patches again and if you can make sure that the ports package works. Tnks, Amancio >From The Desk Of John Hay : > Well, I did send you a set of patches to make it work on FreeBSD 3.0-CURRENT > and still work on 2.2. Should I send it again? I'm using it here on 2.2 and > 3.0 machines, so I'm pretty sure it works. > > John > -- > John Hay > > > Scott G. Akmentins-Taylor wrote in message ID > > <199705312329.QAA01776@mrynet.com>: > > > Gang- > > > > > > I may have missed something important, so feel free to flame--but PLEASE > > > refer me to the pertinant info :) > > > > > > ucd-snmp-3.1.3 doesn't seem to go well with FreeBSD-CURRENT (aka FreeBSD3 ). > > > > I don't have a -current box to try it on. Sorry. (Together with the > > fact I don't really have time to track all the changes right now) > > > > Gary > > -- > > Gary Palmer FreeBSD Core Team Memb er > > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for in fo > > > From owner-freebsd-current Sun Jun 1 01:04:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA12349 for current-outgoing; Sun, 1 Jun 1997 01:04:28 -0700 (PDT) Received: from callisto.cids.org.za (callisto.cids.org.za [146.64.58.43]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA12344; Sun, 1 Jun 1997 01:04:20 -0700 (PDT) Received: from angel.cids.org.za (angel.cids.org.za [146.64.84.9]) by callisto.cids.org.za (8.8.5/8.8.5) with ESMTP id KAA29734; Sun, 1 Jun 1997 10:03:59 +0200 (SAT) Received: (from jhay@localhost) by angel.cids.org.za (8.8.5/8.8.5) id KAA03424; Sun, 1 Jun 1997 10:03:56 +0200 (SAT) From: John Hay Message-Id: <199706010803.KAA03424@angel.cids.org.za> Subject: Re: ucd-snmp-3.1.3 doesn't like FreeBSD3? In-Reply-To: <199706010710.AAA09117@rah.star-gate.com> from Amancio Hasty at "Jun 1, 97 00:10:23 am" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sun, 1 Jun 1997 10:03:56 +0200 (SAT) Cc: jhay@mikom.csir.co.za, gpalmer@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Please post the patches again and if you can make sure that the > ports package works. > Ok, you can get it from: ftp://ftp.za.freebsd.org/pub/local/snmp-patch-aa.gz Just take the current port, delete everything in the patches directory, unzip this and put it in there. John -- John Hay - jhay@mikom.csir.co.za From owner-freebsd-current Sun Jun 1 01:18:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA12825 for current-outgoing; Sun, 1 Jun 1997 01:18:16 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA12816; Sun, 1 Jun 1997 01:18:13 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id BAA14119; Sun, 1 Jun 1997 01:18:01 -0700 (PDT) Message-Id: <199706010818.BAA14119@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: John Hay cc: gpalmer@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: ucd-snmp-3.1.3 doesn't like FreeBSD3? In-reply-to: Your message of "Sat, 01 Jun 1997 10:03:56 +0200." <199706010803.KAA03424@angel.cids.org.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Jun 1997 01:18:01 -0700 From: Amancio Hasty Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tnks the patches seems to work pretty well over here. Once exception is: cc -I.. -O2 -pipe -Dfreebsd3 -c md5.c md5.c: In function `MDblock': md5.c:157: warning: decimal constant is so large that it is unsigned md5.c:158: warning: decimal constant is so large that it is unsigned md5.c:160: warning: decimal constant is so large that it is unsigned md5.c:161: warning: decimal constant is so large that it is unsigned md5.c:163: warning: decimal constant is so large that it is unsigned md5.c:164: warning: decimal constant is so large that it is unsigned md5.c:166: warning: decimal constant is so large that it is unsigned md5.c:167: warning: decimal constant is so large that it is unsigned md5.c:168: warning: decimal constant is so large that it is unsigned md5.c:170: warning: decimal constant is so large that it is unsigned md5.c:171: warning: decimal constant is so large that it is unsigned md5.c:173: warning: decimal constant is so large that it is unsigned md5.c:174: warning: decimal constant is so large that it is unsigned md5.c:176: warning: decimal constant is so large that it is unsigned md5.c:177: warning: decimal constant is so large that it is unsigned md5.c:179: warning: decimal constant is so large that it is unsigned This probably will not cause problems however if you can get rid of the warning messages it will save e-mail traffic. Many Thanks! Amancio >From The Desk Of John Hay : > > Please post the patches again and if you can make sure that the > > ports package works. > > > > Ok, you can get it from: ftp://ftp.za.freebsd.org/pub/local/snmp-patch-aa.gz > > Just take the current port, delete everything in the patches directory, > unzip this and put it in there. > > John > -- > John Hay - jhay@mikom.csir.co.za From owner-freebsd-current Sun Jun 1 01:23:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA13020 for current-outgoing; Sun, 1 Jun 1997 01:23:01 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA13015; Sun, 1 Jun 1997 01:22:50 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id BAA14188; Sun, 1 Jun 1997 01:22:42 -0700 (PDT) Message-Id: <199706010822.BAA14188@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: John Hay cc: gpalmer@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: ucd-snmp-3.1.3 doesn't like FreeBSD3? In-reply-to: Your message of "Sat, 01 Jun 1997 10:03:56 +0200." <199706010803.KAA03424@angel.cids.org.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Jun 1997 01:22:42 -0700 From: Amancio Hasty Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I usually run an snmp daemon on my system feel free to query it for testing purposes. I am running FreeBSD-3.0 current as of about a week ago. Tnks Again Amancio From owner-freebsd-current Sun Jun 1 02:01:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA14400 for current-outgoing; Sun, 1 Jun 1997 02:01:51 -0700 (PDT) Received: from helbig.informatik.ba-stuttgart.de (helbig.informatik.ba-stuttgart.de [141.31.166.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA14391 for ; Sun, 1 Jun 1997 02:01:48 -0700 (PDT) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.5/8.8.5) id LAA00332; Sun, 1 Jun 1997 11:01:37 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199706010901.LAA00332@helbig.informatik.ba-stuttgart.de> Subject: Re: -current build failed In-Reply-To: from Vincent Poy at "May 31, 97 10:48:19 pm" To: vince@mail.MCESTATE.COM (Vincent Poy) Date: Sun, 1 Jun 1997 11:01:36 +0200 (MET DST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > THanks to Jordan for fixing the pcicard lkm but it seems to fail > here this time: > > ===> syscons > ===> syscons/blank > make: don't know how to make /usr/include/machine/spl.h. Stop > *** Error code 2 > > Stop. > *** Error code 1 Seems something went wrong with your installation. The file spl.h is supposed to be in /usr/sys/i386/include. Two symbolic links should be set: /usr/include/machine -> /sys/i386/include /sys -> /usr/src/sys Under these three preconditions spl.h should be found by make. The link /sys -> /usr/src/sys is set by the make target `hierarchy'. I did not find out where the link /usr/include/machine -> /sys/i386/include is made, but there seem to be a lot of machines where this link is not set. Wolfgang From owner-freebsd-current Sun Jun 1 02:09:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA14690 for current-outgoing; Sun, 1 Jun 1997 02:09:56 -0700 (PDT) Received: from mail.MCESTATE.COM (mail.MCESTATE.COM [207.211.200.50]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA14685 for ; Sun, 1 Jun 1997 02:09:54 -0700 (PDT) Received: from localhost (vince@localhost) by mail.MCESTATE.COM (8.8.5/8.8.5) with SMTP id CAA06069; Sun, 1 Jun 1997 02:09:43 -0700 (PDT) Date: Sun, 1 Jun 1997 02:09:41 -0700 (PDT) From: Vincent Poy To: Wolfgang Helbig cc: current@FreeBSD.ORG Subject: Re: -current build failed In-Reply-To: <199706010901.LAA00332@helbig.informatik.ba-stuttgart.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 1 Jun 1997, Wolfgang Helbig wrote: =)> THanks to Jordan for fixing the pcicard lkm but it seems to fail =)> here this time: =)> =)> ===> syscons =)> ===> syscons/blank =)> make: don't know how to make /usr/include/machine/spl.h. Stop =)> *** Error code 2 =)> =)> Stop. =)> *** Error code 1 =) =)Seems something went wrong with your installation. The file spl.h =)is supposed to be in /usr/sys/i386/include. Two symbolic =)links should be set: I just tried doing /usr/src/include first to make sure that wasn't it but same thing happened. =)/usr/include/machine -> /sys/i386/include This is the problem I think. =)/sys -> /usr/src/sys =) =)Under these three preconditions spl.h should be found by make. =) =)The link /sys -> /usr/src/sys is set by the make target `hierarchy'. =) =)I did not find out where the link =) =)/usr/include/machine -> /sys/i386/include =) =)is made, but there seem to be a lot of machines where this link is not set. I just did a resup and there is still no spl.h in the /sys/i386/include directory. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] From owner-freebsd-current Sun Jun 1 02:21:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA15205 for current-outgoing; Sun, 1 Jun 1997 02:21:19 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA15196 for ; Sun, 1 Jun 1997 02:21:15 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id KAA21236; Sun, 1 Jun 1997 10:21:04 +0100 (BST) Date: Sun, 1 Jun 1997 10:21:04 +0100 (BST) From: Doug Rabson To: Vincent Poy cc: current@freebsd.org Subject: Re: -current build failed In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 31 May 1997, Vincent Poy wrote: > THanks to Jordan for fixing the pcicard lkm but it seems to fail > here this time: > > ===> syscons > ===> syscons/blank > make: don't know how to make /usr/include/machine/spl.h. Stop > *** Error code 2 > > Stop. > *** Error code 1 > > Stop. > root@mercury [10:46pm][/usr/src/lkm] >> This one sounds like a stale .depend file. Try running 'make cleandepend depend' -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 From owner-freebsd-current Sun Jun 1 02:28:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA15449 for current-outgoing; Sun, 1 Jun 1997 02:28:20 -0700 (PDT) Received: from online.no (pilt.online.no [193.212.1.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA15444 for ; Sun, 1 Jun 1997 02:28:18 -0700 (PDT) Received: from online.no (toazt@ti18a95-0021.dialup.online.no [130.67.231.21]) by online.no (8.7.6/8.7.3) with SMTP id LAA19705 for ; Sun, 1 Jun 1997 11:28:15 +0200 (MET DST) Message-Id: <199706010928.LAA19705@online.no> Comments: Authenticated sender is From: "Morten A. Middelthon" To: current@freebsd.org Date: Sun, 1 Jun 1997 11:26:09 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: qcam Reply-to: toazt@online.no Priority: normal X-mailer: Pegasus Mail for Win32 (v2.53/R1) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Isn't this the ccorrect line for QuickCam in the kernel conf file: device qcam0 at isa? at IO_LPT0 ? Morten A. Middelthon toazt@online.no From owner-freebsd-current Sun Jun 1 02:33:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA15625 for current-outgoing; Sun, 1 Jun 1997 02:33:24 -0700 (PDT) Received: from mail.MCESTATE.COM (mail.MCESTATE.COM [207.211.200.50]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA15620 for ; Sun, 1 Jun 1997 02:33:22 -0700 (PDT) Received: from localhost (vince@localhost) by mail.MCESTATE.COM (8.8.5/8.8.5) with SMTP id CAA06158; Sun, 1 Jun 1997 02:33:15 -0700 (PDT) Date: Sun, 1 Jun 1997 02:33:13 -0700 (PDT) From: Vincent Poy To: Doug Rabson cc: current@freebsd.org Subject: Re: -current build failed In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 1 Jun 1997, Doug Rabson wrote: =)> ===> syscons/blank =)> make: don't know how to make /usr/include/machine/spl.h. Stop =)> *** Error code 2 =)> =)> Stop. =)> *** Error code 1 =)> =)> Stop. =)> root@mercury [10:46pm][/usr/src/lkm] >> =) =)This one sounds like a stale .depend file. Try running 'make cleandepend =)depend' THis one worked, thanks again for all those that helped! For some reason, -current build fine yesterday. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] From owner-freebsd-current Sun Jun 1 04:21:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA18598 for current-outgoing; Sun, 1 Jun 1997 04:21:11 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA18587 for ; Sun, 1 Jun 1997 04:21:07 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA07235; Sun, 1 Jun 1997 13:21:05 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id NAA05185; Sun, 1 Jun 1997 13:15:08 +0200 (MET DST) Message-ID: <19970601131508.GE62220@uriah.heep.sax.de> Date: Sun, 1 Jun 1997 13:15:08 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Cc: toazt@online.no Subject: Re: qcam References: <199706010928.LAA19705@online.no> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706010928.LAA19705@online.no>; from Morten A. Middelthon on Jun 1, 1997 11:26:09 +0000 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Morten A. Middelthon wrote: > Isn't this the ccorrect line for QuickCam in the kernel conf file: > > device qcam0 at isa? at IO_LPT0 j@uriah 296% fgrep qcam /sys/i386/conf/LINT device qcam0 at isa? port "IO_LPT3" tty -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Jun 1 10:26:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA28084 for current-outgoing; Sun, 1 Jun 1997 10:26:22 -0700 (PDT) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA27827 for ; Sun, 1 Jun 1997 10:20:42 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id UAA04693 for current@freebsd.org; Sun, 1 Jun 1997 20:20:14 +0300 (EET DST) From: mika ruohotie Message-Id: <199706011720.UAA04693@shadows.aeon.net> Subject: page fault To: current@freebsd.org Date: Sun, 1 Jun 1997 20:20:14 +0300 (EET DST) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk this is a May 26 08:18 EET kernel and as for some time now, it's still possible to reboot my machine with either telnet from win 95 (it reboots often during the first minute after logged in). several different machine with different win95 installations _can_ do this. also in a setup where my box has kernel ppp to world, and ed0 to the ether, somewhat heavy load from ether to ppp crashes my machine. (heavy as web surfing from one machine) yesterday i turned the crashdump on, this is what i got today: IdlePTD 23e000 current pcb at 21b728 panic: page fault #0 0xf0114b5e in boot () (kgdb) where #0 0xf0114b5e in boot () #1 0xf0114e4a in panic () #2 0xf01ce0ba in trap_fatal () #3 0xf01cdb69 in trap_pfault () #4 0xf01cd7cb in trap () #5 0xf01cc939 in small_i586_bcopy () #6 0xf014f04e in ether_output () #7 0xf015ff03 in ip_output () #8 0xf016730d in udp_output () #9 0xf01676c5 in udp_send () #10 0xf012cabf in sosend () #11 0xf012fa9e in sendit () #12 0xf012fb56 in sendto () #13 0xf01ce317 in syscall () #14 0x8082af1 in ?? () #15 0x1a5a7 in ?? () #16 0x149a4 in ?? () #17 0x10c71 in ?? () #18 0x1096 in ?? () (kgdb) is that at all helpfull? anyone wants to have the crashdumps? i'll keep it on coz now it should not crash too often (i'm low on drive space for crashes coz of 64 megs ram makes relatively big dumps) will be going current (cvsup 20:30 EET DST Sun 1st) in 4 hours. but as i mentioned, these win95_reboots_freebsd_? -probs has been around from the first time i suspected it publicly here... weeks ago. is it just somewhat related to ppp? or is my hardware _bad_? mickey From owner-freebsd-current Sun Jun 1 11:10:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA29474 for current-outgoing; Sun, 1 Jun 1997 11:10:50 -0700 (PDT) Received: from nagual.pp.ru (ache.relcom.ru [194.58.229.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA29462; Sun, 1 Jun 1997 11:10:34 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.8.5/8.8.5) id WAA00283; Sun, 1 Jun 1997 22:11:35 +0400 (MSD) Date: Sun, 1 Jun 1997 22:11:32 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: FreeBSD-current cc: se@freebsd.org Subject: Shared irq's broke sounddriver badly Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What I always have worked in my kernel configure: controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr device sbxvi0 at isa? port? irq? drq 5 conflicts device opl0 at isa? port 0x388 device sbmidi0 at isa? port 0x330 irq? conflicts What I got now with new shared interrupts code: sb0 at 0x220-0x22f irq 5 drq 1 on isa sb0: sbxvi0 at 0x220-0x22f irq 5 drq 5 on isa sbxvi0: device combination doesn't support shared irq5 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ intr_connect(irq5) failed, result=-1 opl0 at 0x388-0x38b irq 31 on isa ^^^^^^ opl0: create_intr: requested irq31 too high, limit is 15 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sbmidi0 at 0x330-0x331 irq 5 on isa sbmidi0: device combination doesn't support shared irq5 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ intr_connect(irq5) failed, result=-1 I.e. "conflicts" keyword not work anymore and misterious "irq 31" appearse from nowhere. Please fix this bugs. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-current Sun Jun 1 12:01:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA01050 for current-outgoing; Sun, 1 Jun 1997 12:01:05 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA01045; Sun, 1 Jun 1997 12:00:58 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id EAA30970; Mon, 2 Jun 1997 04:58:15 +1000 Date: Mon, 2 Jun 1997 04:58:15 +1000 From: Bruce Evans Message-Id: <199706011858.EAA30970@godzilla.zeta.org.au> To: ache@nagual.pp.ru, current@FreeBSD.ORG Subject: Re: Shared irq's broke sounddriver badly Cc: se@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >What I always have worked in my kernel configure: > >controller snd0 >device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr >device sbxvi0 at isa? port? irq? drq 5 conflicts >device opl0 at isa? port 0x388 >device sbmidi0 at isa? port 0x330 irq? conflicts > >What I got now with new shared interrupts code: > >sb0 at 0x220-0x22f irq 5 drq 1 on isa >sb0: >sbxvi0 at 0x220-0x22f irq 5 drq 5 on isa >sbxvi0: > device combination doesn't support shared irq5 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > intr_connect(irq5) failed, result=-1 This is not a new error. intr_connect() just reports the error. config_isadev_c() ignores errors from register_intr(). I get this for all my ISA devices because I register the interrupts earlier without telling config_isadev_c(). >opl0 at 0x388-0x38b irq 31 on isa > ^^^^^^ What was it originally? Bruce From owner-freebsd-current Sun Jun 1 12:18:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA01523 for current-outgoing; Sun, 1 Jun 1997 12:18:46 -0700 (PDT) Received: from nagual.pp.ru (ache.relcom.ru [194.58.229.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA01516; Sun, 1 Jun 1997 12:18:34 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.8.5/8.8.5) id XAA06504; Sun, 1 Jun 1997 23:19:18 +0400 (MSD) Date: Sun, 1 Jun 1997 23:19:14 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: Bruce Evans cc: current@FreeBSD.ORG, se@FreeBSD.ORG Subject: Re: Shared irq's broke sounddriver badly In-Reply-To: <199706011858.EAA30970@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 2 Jun 1997, Bruce Evans wrote: > >What I always have worked in my kernel configure: > > > >controller snd0 > >device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr > >device sbxvi0 at isa? port? irq? drq 5 conflicts > >device opl0 at isa? port 0x388 > >device sbmidi0 at isa? port 0x330 irq? conflicts > > > >What I got now with new shared interrupts code: > > > >sb0 at 0x220-0x22f irq 5 drq 1 on isa > >sb0: > >sbxvi0 at 0x220-0x22f irq 5 drq 5 on isa > >sbxvi0: > > device combination doesn't support shared irq5 > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > intr_connect(irq5) failed, result=-1 > > This is not a new error. intr_connect() just reports the error. > config_isadev_c() ignores errors from register_intr(). I get this for > all my ISA devices because I register the interrupts earlier without > telling config_isadev_c(). Hmm. I just care about resolving this issue than about where this error belongs too. If you know such deep details, could you please fix it somehow? > >opl0 at 0x388-0x38b irq 31 on isa > > ^^^^^^ > > What was it originally? There is no IRQ for this device at all (according to config line). -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-current Sun Jun 1 12:21:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA01668 for current-outgoing; Sun, 1 Jun 1997 12:21:10 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA01663 for ; Sun, 1 Jun 1997 12:21:05 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id UAA03499; Sun, 1 Jun 1997 20:09:57 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 1 Jun 1997 20:13:33 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: References: <199705301253.OAA04727@sliphost37.uni-trier.de> <199705300624.IAA03466@sos.freebsd.dk> <199705300624.IAA03466@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 1 Jun 1997 20:10:27 +0100 To: Richard Wackerbarth From: Bob Bishop Subject: Re: ctm Cc: freebsd-current@freefall.FreeBSD.org Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 19:23 +0100 31/5/97, Richard Wackerbarth wrote: >At 6:49 AM -0500 5/31/97, Bob Bishop wrote: >>>14 amicus-networks.Dallas.mci.net (204.70.147.70) 207 ms * 211 ms >>>15 10.1.1.3 (10.1.1.3) 230 ms 187 ms 187 ms >> >>Eeek! Noone should be advertising a route to 10.x.x.x (see RFC1918). Try >>shouting at mci.net > >Who says that they are advertising a route to 10.x.x.x? >The advertised route is to 208.2.87.x You're right, of course; ISC. However, I share Gary Palmer's misgivings about using private space in this way. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Sun Jun 1 12:22:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA01724 for current-outgoing; Sun, 1 Jun 1997 12:22:07 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA01719 for ; Sun, 1 Jun 1997 12:22:05 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (8.8.5/8.8.5) with ESMTP id PAA01899; Sun, 1 Jun 1997 15:22:01 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPN/970116) with ESMTP id PAA17193; Sun, 1 Jun 1997 15:22:00 -0400 (EDT) To: Amancio Hasty cc: John Hay , freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: ucd-snmp-3.1.3 doesn't like FreeBSD3? In-reply-to: Your message of "Sun, 01 Jun 1997 01:18:01 PDT." <199706010818.BAA14119@rah.star-gate.com> Date: Sun, 01 Jun 1997 15:22:00 -0400 Message-ID: <17191.865192920@orion.webspan.net> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Amancio Hasty wrote in message ID <199706010818.BAA14119@rah.star-gate.com>: > Tnks the patches seems to work pretty well over here. > > Once exception is: > > cc -I.. -O2 -pipe -Dfreebsd3 -c md5.c > md5.c: In function `MDblock': > md5.c:157: warning: decimal constant is so large that it is unsigned > md5.c:158: warning: decimal constant is so large that it is unsigned > md5.c:160: warning: decimal constant is so large that it is unsigned > md5.c:161: warning: decimal constant is so large that it is unsigned > md5.c:163: warning: decimal constant is so large that it is unsigned > md5.c:164: warning: decimal constant is so large that it is unsigned > md5.c:166: warning: decimal constant is so large that it is unsigned > md5.c:167: warning: decimal constant is so large that it is unsigned > md5.c:168: warning: decimal constant is so large that it is unsigned > md5.c:170: warning: decimal constant is so large that it is unsigned > md5.c:171: warning: decimal constant is so large that it is unsigned > md5.c:173: warning: decimal constant is so large that it is unsigned > md5.c:174: warning: decimal constant is so large that it is unsigned > md5.c:176: warning: decimal constant is so large that it is unsigned > md5.c:177: warning: decimal constant is so large that it is unsigned > md5.c:179: warning: decimal constant is so large that it is unsigned > > This probably will not cause problems however if you can get rid of the > warning messages it will save e-mail traffic. Those warnings have been there since day one. I have no idea if they mean anything or not (that code is pretty nasty from memory). I meant to replace it with our libmd but never got a chance. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Sun Jun 1 12:44:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA02379 for current-outgoing; Sun, 1 Jun 1997 12:44:59 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA02370; Sun, 1 Jun 1997 12:44:39 -0700 (PDT) Received: (from pallenby@localhost) by zibbi.mikom.csir.co.za (8.8.5/8.8.5) id VAA05847; Sun, 1 Jun 1997 21:44:32 +0200 (SAT) From: Paul Allenby Message-Id: <199706011944.VAA05847@zibbi.mikom.csir.co.za> Subject: Re: ucd-snmp-3.1.3 doesn't like FreeBSD3? In-Reply-To: <17191.865192920@orion.webspan.net> from Gary Palmer at "Jun 1, 97 03:22:00 pm" To: gpalmer@FreeBSD.ORG (Gary Palmer) Date: Sun, 1 Jun 1997 21:44:32 +0200 (SAT) Cc: hasty@rah.star-gate.com, jhay@mikom.csir.co.za, freebsd-current@FreeBSD.ORG 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-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Gary Palmer wrote:" > Amancio Hasty wrote in message ID > <199706010818.BAA14119@rah.star-gate.com>: > > Tnks the patches seems to work pretty well over here. > > > > Once exception is: > > > > cc -I.. -O2 -pipe -Dfreebsd3 -c md5.c > > md5.c: In function `MDblock': > > md5.c:157: warning: decimal constant is so large that it is unsigned > > md5.c:158: warning: decimal constant is so large that it is unsigned > > md5.c:160: warning: decimal constant is so large that it is unsigned > > md5.c:161: warning: decimal constant is so large that it is unsigned > > md5.c:163: warning: decimal constant is so large that it is unsigned > > md5.c:164: warning: decimal constant is so large that it is unsigned > > md5.c:166: warning: decimal constant is so large that it is unsigned > > md5.c:167: warning: decimal constant is so large that it is unsigned > > md5.c:168: warning: decimal constant is so large that it is unsigned > > md5.c:170: warning: decimal constant is so large that it is unsigned > > md5.c:171: warning: decimal constant is so large that it is unsigned > > md5.c:173: warning: decimal constant is so large that it is unsigned > > md5.c:174: warning: decimal constant is so large that it is unsigned > > md5.c:176: warning: decimal constant is so large that it is unsigned > > md5.c:177: warning: decimal constant is so large that it is unsigned > > md5.c:179: warning: decimal constant is so large that it is unsigned > > > > This probably will not cause problems however if you can get rid of the > > warning messages it will save e-mail traffic. > > Those warnings have been there since day one. I have no idea if they > mean anything or not (that code is pretty nasty from memory). I meant > to replace it with our libmd but never got a chance. > > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info > add a UL to the end of the lines. Paul From owner-freebsd-current Sun Jun 1 12:56:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA02790 for current-outgoing; Sun, 1 Jun 1997 12:56:52 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA02782; Sun, 1 Jun 1997 12:56:39 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id FAA32060; Mon, 2 Jun 1997 05:53:16 +1000 Date: Mon, 2 Jun 1997 05:53:16 +1000 From: Bruce Evans Message-Id: <199706011953.FAA32060@godzilla.zeta.org.au> To: ache@nagual.pp.ru, bde@zeta.org.au Subject: Re: Shared irq's broke sounddriver badly Cc: current@FreeBSD.ORG, se@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> >opl0 at 0x388-0x38b irq 31 on isa >> > ^^^^^^ >> >> What was it originally? > >There is no IRQ for this device at all (according to config line). This is another old, previously unreported, bug. soundcard.c corrupts no-IRQ to irq 31 via the following operations: hw_config.irq = ipri_to_irq(dev->id_irq); /* in sndprobe() */ dev->id_irq = (1 << hw_config.irq); /* in sndattach() */ ipri_to_irq(0) = (unsigned short)-1 = 0xffff (assuming 16-bit unsigned shorts). 1 << 0xffff = 1 < (0xfffff) & 0x1f) = 1 << 31 (assuming a 386). Bruce From owner-freebsd-current Sun Jun 1 13:38:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA04164 for current-outgoing; Sun, 1 Jun 1997 13:38:45 -0700 (PDT) Received: from peedub.gj.org (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA04159 for ; Sun, 1 Jun 1997 13:38:41 -0700 (PDT) Received: from peedub.gj.org (localhost [127.0.0.1]) by peedub.gj.org (8.8.5/8.6.9) with ESMTP id WAA28504 for ; Sun, 1 Jun 1997 22:38:32 GMT Message-Id: <199706012238.WAA28504@peedub.gj.org> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-current@freebsd.org Subject: Re: if.h inclusion of Reply-To: Gary Jennejohn In-reply-to: Your message of "Sat, 31 May 1997 20:30:37 +0200." <19970531203037.IM15621@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Jun 1997 22:38:32 +0000 From: Gary Jennejohn Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch writes: >As Garrett Wollman wrote: > >> > #if defined(__FreeBSD__) && __FreeBSD__>=3 >> > #include >> > #endif >> > #include >> >> > That's horrible. >> >> There is no reason for the include of to be >> conditional. > >Yep. > even if you're trying to support versions <= 2.1.7 ? --- Gary Jennejohn Home - Gary.Jennejohn@munich.netsurf.de Work - gjennejohn@frt.dec.com From owner-freebsd-current Sun Jun 1 13:51:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA04573 for current-outgoing; Sun, 1 Jun 1997 13:51:28 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA04568 for ; Sun, 1 Jun 1997 13:51:26 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id NAA21801; Sun, 1 Jun 1997 13:51:17 -0700 (PDT) Message-Id: <199706012051.NAA21801@austin.polstra.com> To: blank@fox.uni-trier.de Subject: Re: ctm Newsgroups: polstra.freebsd.current In-Reply-To: <199705312109.XAA02312@sliphost37.uni-trier.de> References: <199705312109.XAA02312@sliphost37.uni-trier.de> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Date: Sun, 01 Jun 1997 13:51:17 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199705312109.XAA02312@sliphost37.uni-trier.de>, Sascha Blank wrote: > In case I can find an entirely statically linked > version of CVSup 15 that will work on BSDI 2.1 and 3.0, I would be > willing to do a little testing The FreeBSD static binary works under BSDI, but you have to run it with an extra magical command line argument "@M3novm". If you just add that to the command line (client or server) it works fine. The static binaries are available from hub.freebsd.org in /pub/CVSup. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Sun Jun 1 14:39:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA06122 for current-outgoing; Sun, 1 Jun 1997 14:39:10 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA06116 for ; Sun, 1 Jun 1997 14:39:05 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA16614 for current@FreeBSD.ORG; Sun, 1 Jun 1997 23:39:04 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA06837; Sun, 1 Jun 1997 22:24:29 +0200 (MET DST) Message-ID: <19970601222428.RH40488@uriah.heep.sax.de> Date: Sun, 1 Jun 1997 22:24:28 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Subject: Re: page fault References: <199706011720.UAA04693@shadows.aeon.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706011720.UAA04693@shadows.aeon.net>; from mika ruohotie on Jun 1, 1997 20:20:14 +0300 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As mika ruohotie wrote: > #3 0xf01cdb69 in trap_pfault () > #4 0xf01cd7cb in trap () > #5 0xf01cc939 in small_i586_bcopy () > #6 0xf014f04e in ether_output () > is that at all helpfull? Rebuild a few object files with -g, and see where it crashes in ether_output(). > keep it on coz now it should not crash too often (i'm low on drive > space for crashes coz of 64 megs ram makes relatively big dumps) If it's always the same spot, you only need one dump. > will be going current (cvsup 20:30 EET DST Sun 1st) in 4 hours. Nobody has changed anything in this area (if_ethersubr.c), nothing that i would remember of. The last functional change was on May 10, and supposedly only related to IPX. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Jun 1 14:39:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA06161 for current-outgoing; Sun, 1 Jun 1997 14:39:39 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA06141 for ; Sun, 1 Jun 1997 14:39:19 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA16616 for freebsd-current@FreeBSD.ORG; Sun, 1 Jun 1997 23:39:09 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA06871; Sun, 1 Jun 1997 22:31:24 +0200 (MET DST) Message-ID: <19970601223118.VX29490@uriah.heep.sax.de> Date: Sun, 1 Jun 1997 22:31:18 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG Subject: Re: ucd-snmp-3.1.3 doesn't like FreeBSD3? References: <199706010818.BAA14119@rah.star-gate.com> <17191.865192920@orion.webspan.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <17191.865192920@orion.webspan.net>; from Gary Palmer on Jun 1, 1997 15:22:00 -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Gary Palmer wrote: > > cc -I.. -O2 -pipe -Dfreebsd3 -c md5.c > > md5.c: In function `MDblock': > > md5.c:157: warning: decimal constant is so large that it is unsigned > > md5.c:158: warning: decimal constant is so large that it is unsigned > Those warnings have been there since day one. I have no idea if they > mean anything or not They simply mean someone defined a constant that would have the sign bit set, but it wasn't declared to be a negative constant. You could supposedly get around this by appending a `U' to the constant (thus indicating to the compiler that it is really meant to be unsigned). Seems gcc does already believe into the good intentions of the programmer if he used a hexadecimal constant: j@uriah 405% cat > foo.c int main(void) { unsigned a, b; a = 0xd76aa478; b = 3614090360; return 0; } ^D j@uriah 406% cc -Wall foo.c foo.c: In function `main': foo.c:7: warning: decimal constant is so large that it is unsigned Both values above are identical. Appending the `U' silences the warning, of course. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Jun 1 15:03:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA07133 for current-outgoing; Sun, 1 Jun 1997 15:03:25 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA07124 for ; Sun, 1 Jun 1997 15:03:22 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA16910 for freebsd-current@FreeBSD.ORG; Mon, 2 Jun 1997 00:03:15 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id XAA07416; Sun, 1 Jun 1997 23:51:15 +0200 (MET DST) Message-ID: <19970601235114.EU38483@uriah.heep.sax.de> Date: Sun, 1 Jun 1997 23:51:14 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG Subject: Re: if.h inclusion of References: <19970531203037.IM15621@uriah.heep.sax.de> <199706012238.WAA28504@peedub.gj.org> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706012238.WAA28504@peedub.gj.org>; from Gary Jennejohn on Jun 1, 1997 22:38:32 +0000 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Gary Jennejohn wrote: > >> There is no reason for the include of to be > >> conditional. > > > >Yep. > > > > even if you're trying to support versions <= 2.1.7 ? Yep. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Jun 1 15:09:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA07505 for current-outgoing; Sun, 1 Jun 1997 15:09:58 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA07495 for ; Sun, 1 Jun 1997 15:09:55 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id PAA21171; Sun, 1 Jun 1997 15:09:57 -0700 (PDT) Message-Id: <199706012209.PAA21171@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.ORG Subject: C++ or Java interface ala ORB for snmp? In-reply-to: Your message of "Sun, 01 Jun 1997 22:31:18 +0200." <19970601223118.VX29490@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Jun 1997 15:09:57 -0700 From: Amancio Hasty Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thank you. Adding ul to the large constants silenced the warnings and if the ucd-snmp patch is modified to reflect this last change then are pretty much done with the port. Now a different topic, given that we have ported communication platforms such as OmniORB, OmniBroker, ILU, and ACE . It will be good to develop a generic set of interfaces for the purpose of deploying network management apps. If we can interface snmp to JAVA using CORBA it will be fantastic: portable network management apps. Additionally, if use CORBA we should be able to come up with interesting network managements apps that don't necessarily use snmp rather programmable agent/application. Enjoy, Amancio From owner-freebsd-current Sun Jun 1 16:02:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA11604 for current-outgoing; Sun, 1 Jun 1997 16:02:26 -0700 (PDT) Received: from goethe.c4systm.com (jds@goethe.c4systm.com [204.120.124.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA11572 for ; Sun, 1 Jun 1997 16:02:13 -0700 (PDT) Received: from localhost (jds@localhost) by goethe.c4systm.com (8.8.5/8.7.3) with SMTP id TAA19314 for ; Sun, 1 Jun 1997 19:01:22 -0400 (EDT) X-Authentication-Warning: goethe.c4systm.com: jds owned process doing -bs Date: Sun, 1 Jun 1997 19:01:22 -0400 (EDT) From: "James D. Stewart" To: freebsd-current@freebsd.org Subject: time daemon error in rc files Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk TWIMC, We have just started running with the -current, and have switched our set of /etc/rc* files with those in /usr/src/etc. We noticed that the timed daemon was not starting at boot. It seems there is a misspelling of the timed_enable variable that is set in rc.conf, and used in rc.network: rc.conf:timed_enabled="YES" # Run the time daemon (or NO). ^^^^^^^^^^^^^ rc.network: if [ "X${timed_enable}" = X"YES" ]; then We left rc.conf alone, but took out the past tense in the rc.conf.local file in our working directory. It probably should be fixed in the source tree, though. Jim Stewart From owner-freebsd-current Sun Jun 1 16:06:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA12036 for current-outgoing; Sun, 1 Jun 1997 16:06:03 -0700 (PDT) Received: from myname.my.domain (1Cust76.Max33.Boston.MA.MS.UU.NET [153.35.85.204]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA11998 for ; Sun, 1 Jun 1997 16:05:57 -0700 (PDT) Received: from myname.my.domain (localhost [127.0.0.1]) by myname.my.domain (8.8.5/8.8.5) with SMTP id TAA19776 for ; Sun, 1 Jun 1997 19:18:53 GMT Message-ID: <3391CB1C.41C67EA6@earthlink.net> Date: Sun, 01 Jun 1997 19:18:52 +0000 From: "Michael J. Pelletier" X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2.1-RELEASE i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk subscribe From owner-freebsd-current Sun Jun 1 19:59:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA21428 for current-outgoing; Sun, 1 Jun 1997 19:59:29 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA21415 for ; Sun, 1 Jun 1997 19:59:24 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id TAA01858; Sun, 1 Jun 1997 19:59:11 -0700 (PDT) To: "James D. Stewart" cc: freebsd-current@FreeBSD.ORG Subject: Re: time daemon error in rc files In-reply-to: Your message of "Sun, 01 Jun 1997 19:01:22 EDT." Date: Sun, 01 Jun 1997 19:59:10 -0700 Message-ID: <1854.865220350@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > We have just started running with the -current, and have switched our set > of /etc/rc* files with those in /usr/src/etc. We noticed that the timed > daemon was not starting at boot. It seems there is a misspelling of the > timed_enable variable that is set in rc.conf, and used in rc.network: Fixed, thanks! Jordan From owner-freebsd-current Sun Jun 1 20:03:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA21643 for current-outgoing; Sun, 1 Jun 1997 20:03:35 -0700 (PDT) Received: from intrepid.leaky.com (shaffer-s.nosc.mil [128.49.236.16]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA21634 for ; Sun, 1 Jun 1997 20:03:31 -0700 (PDT) Received: (from admin@localhost) by intrepid.leaky.com (8.8.5/8.8.5) id TAA16979; Sun, 1 Jun 1997 19:47:37 -0700 (PDT) Message-Id: <199706020247.TAA16979@intrepid.leaky.com> X-Authentication-Warning: intrepid.leaky.com: admin set sender to using -f Received: from localhost(127.0.0.1) by intrepid.leaky.com via smap (V1.3) id sma016966; Sun Jun 1 19:47:19 1997 X-Mailer: exmh version 1.6.7 5/3/96 To: current@freebsd.org cc: gshaffer@intrepid.leaky.com Subject: Current build fails Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Jun 1997 19:47:18 -0700 From: Greg Shaffer Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I get the following error when I try to rebuild current (as of cvs-cur.3345 ===> usr.bin/chkey Warning: Object directory not changed from original /home/FreeBSD-current/src/usr.bin/chkey cc -O2 -m486 -pipe -DYP -c chkey.c cc -O2 -m486 -pipe -DYP -c /home/FreeBSD-current/src/usr.bin/chkey/../newkey/ update.c cc -O2 -m486 -pipe -DYP -c /home/FreeBSD-current/src/usr.bin/chkey/../newkey/ generic.c cc -O2 -m486 -pipe -DYP -o chkey chkey.o update.o generic.o -lrpcsvc -lmp -lgmp chkey.o: Undefined symbol `_host2netname' referenced from text segment chkey.o: Undefined symbol `_user2netname' referenced from text segment chkey.o: Undefined symbol `_xencrypt' referenced from text segment chkey.o: Undefined symbol `_xdecrypt' referenced from text segment chkey.o: Undefined symbol `_key_setsecret' referenced from text segment chkey.o: Undefined symbol `_yp_update' referenced from text segment *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Recompiling libraries took care of the last 4. Any suggestions? Thanks in advance. Greg Shaffer From owner-freebsd-current Sun Jun 1 20:51:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA23836 for current-outgoing; Sun, 1 Jun 1997 20:51:33 -0700 (PDT) Received: from goethe.c4systm.com (jds@goethe.c4systm.com [204.120.124.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA23825 for ; Sun, 1 Jun 1997 20:51:26 -0700 (PDT) Received: from localhost (jds@localhost) by goethe.c4systm.com (8.8.5/8.7.3) with SMTP id XAA27265 for ; Sun, 1 Jun 1997 23:51:06 -0400 (EDT) X-Authentication-Warning: goethe.c4systm.com: jds owned process doing -bs Date: Sun, 1 Jun 1997 23:51:06 -0400 (EDT) From: "James D. Stewart" To: freebsd-current@freebsd.org Subject: Removal of *.pid files from /var/run. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi All, I know this thread had some activity a day or two ago, but it just occurred to me that inn tests the presence of /var/run/innd.pid to determine whether a system crash has happened when rebooting. If that file is present, it starts inn differently and launches a renumber, etc. This is not only in inn-1.5.1, but in prior versions also. This may not be the only system that uses this technique. JDS From owner-freebsd-current Sun Jun 1 21:00:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA24204 for current-outgoing; Sun, 1 Jun 1997 21:00:36 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA24199 for ; Sun, 1 Jun 1997 21:00:34 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id NAA08264 for current@freebsd.org; Mon, 2 Jun 1997 13:56:59 +1000 Date: Mon, 2 Jun 1997 13:56:59 +1000 From: Bruce Evans Message-Id: <199706020356.NAA08264@godzilla.zeta.org.au> To: current@freebsd.org Subject: processes hanging in getblk for shutdown on nfs client Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On my nfs client system with /usr nfs-mounted, a plain reboot command now always leaves sendmail and/or xntpd hanging on getblk. The sync then fails because of dirty blocks. There was no problem until a week or two ago. There is no problem with the same kernel and similar utilities on my nfs server system. Bruce From owner-freebsd-current Sun Jun 1 21:40:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA25770 for current-outgoing; Sun, 1 Jun 1997 21:40:11 -0700 (PDT) Received: from Gforce.iamerica.net (iax-covington-ppp0007.iamerica.net [207.101.35.16]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA25762; Sun, 1 Jun 1997 21:40:06 -0700 (PDT) Received: from Gforce.iamerica.net (localhost.iamerica.net [127.0.0.1]) by Gforce.iamerica.net (8.8.5/8.8.5) with ESMTP id XAA07595; Sun, 1 Jun 1997 23:39:25 -0500 (CDT) Message-Id: <199706020439.XAA07595@Gforce.iamerica.net> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-questions@freebsd.org cc: freebsd-current@freebsd.org Subject: GIMP From: Glenn Johnson Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Jun 1997 23:39:25 -0500 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone else had trouble with the 'gimp-devel 0.99.9 port'? I am running 3.0 current and am getting the following: gmake[3]: Leaving directory `/usr/ports/graphics/gimp-devel/work/gimp-0.99.9/pl ug-ins/dgimp' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/graphics/gimp-devel/work/gimp-0.99.9/pl ug-ins' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/gimp-devel/work/gimp-0.99.9' gmake: *** [all-recursive-am] Error 2 *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Thanks for any help. -- Glenn Johnson gljohnsn@iamerica.net From owner-freebsd-current Sun Jun 1 22:26:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA27819 for current-outgoing; Sun, 1 Jun 1997 22:26:50 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA27814 for ; Sun, 1 Jun 1997 22:26:48 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id WAA02303; Sun, 1 Jun 1997 22:26:06 -0700 (PDT) To: Bruce Evans cc: current@FreeBSD.ORG Subject: Re: processes hanging in getblk for shutdown on nfs client In-reply-to: Your message of "Mon, 02 Jun 1997 13:56:59 +1000." <199706020356.NAA08264@godzilla.zeta.org.au> Date: Sun, 01 Jun 1997 22:26:06 -0700 Message-ID: <2298.865229166@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I see this too, but also in RELENG_2_2; I haven't been able to simply reboot either of my 2.2.2+ machines for some time now, being NFS clients (which mutually mount one another using AMD). They always hang up trying to unmount the NFS volumes and force my application of the old reset button. Jordan > On my nfs client system with /usr nfs-mounted, a plain reboot command > now always leaves sendmail and/or xntpd hanging on getblk. The sync > then fails because of dirty blocks. There was no problem until a > week or two ago. There is no problem with the same kernel and similar > utilities on my nfs server system. > > Bruce From owner-freebsd-current Mon Jun 2 03:59:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA12878 for current-outgoing; Mon, 2 Jun 1997 03:59:37 -0700 (PDT) Received: from relay.linkdesign.com (nserv1.hlink.com.cy [194.42.131.14]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA12860 for ; Mon, 2 Jun 1997 03:59:23 -0700 (PDT) Received: from bsd.linkdesign.com (andrease1.cylink.net [194.42.135.70]) by relay.linkdesign.com (8.8.5/8.8.2) with ESMTP id NAA03428 for ; Mon, 2 Jun 1997 13:59:59 +0300 (EET DST) Received: (from michael.bielicki@localhost) by bsd.linkdesign.com (8.8.5/8.8.5) id NAA03963; Mon, 2 Jun 1997 13:56:57 +0300 (EEST) From: Michael Bielicki Message-ID: <19970602135655.32975@linkdesign.com> Date: Mon, 2 Jun 1997 13:56:56 +0300 To: current@freebsd.org Subject: Problems with todays CURRENT Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=odhTwj0NAgWpTeJT X-Mailer: Mutt 0.68 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk --odhTwj0NAgWpTeJT Content-Type: text/plain; charset=us-ascii Hmmm, since I updated a couple of hours ago I have the following problem: SSH works perfectly SCP to my workstation from another station is impossible and times out. Am I missing something ??? -- Michael Bielicki Link Design International Ltd. Buisnetco Telecommunications Ltd. 65 Cliff Road, Tramore, Office 23, 13, Iras Street Co. Waterford, Ireland Nicosia 1061, Rep. of Cyprus Tel: +353-51-390880 We use FreeBSD Tel: +357 2 362 421 Fax: +353 51 386921 http://www.linkdesign.com Fax: +357 2 362 429 --odhTwj0NAgWpTeJT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Comment: Requires PGP version 2.6 or later. iQCVAwUBM5Km98neSpf+YTVhAQHeQwP/eLZv7NHpJtio/jRQA1nwR41Kh/1Y/p+p 9ePMRGQ7hr3iy2/pUl+bneFOjsP/h1RKGP604qXVVXuqzhoBW2cR/a6PIBSeNtFp Pp7UIJxXoqP3y0bBQ9+g0Oq9WZWR/BJSW/ukpgnWuN1TmpNQ+pfE9pHTZPH6UHwo JP1AvSEa6ik= =tZbn -----END PGP SIGNATURE----- --odhTwj0NAgWpTeJT-- From owner-freebsd-current Mon Jun 2 04:49:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA14965 for current-outgoing; Mon, 2 Jun 1997 04:49:54 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA14957 for ; Mon, 2 Jun 1997 04:49:50 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id MAA01927; Mon, 2 Jun 1997 12:49:37 +0100 (BST) Date: Mon, 2 Jun 1997 12:49:37 +0100 (BST) From: Doug Rabson To: Bruce Evans cc: current@freebsd.org Subject: Re: processes hanging in getblk for shutdown on nfs client In-Reply-To: <199706020356.NAA08264@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 2 Jun 1997, Bruce Evans wrote: > On my nfs client system with /usr nfs-mounted, a plain reboot command > now always leaves sendmail and/or xntpd hanging on getblk. The sync > then fails because of dirty blocks. There was no problem until a > week or two ago. There is no problem with the same kernel and similar > utilities on my nfs server system. Can you try this patch and see if it helps: Index: vfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.117 diff -u -r1.117 vfs_bio.c --- vfs_bio.c 1997/05/30 22:25:35 1.117 +++ vfs_bio.c 1997/06/02 10:38:23 @@ -514,11 +514,11 @@ * This can avoid unnecessary re-reads of the buffer. */ if ((bp->b_flags & B_VMIO) - && (bp->b_vp->v_tag != VT_NFS + /* && (bp->b_vp->v_tag != VT_NFS || (bp->b_flags & (B_NOCACHE | B_INVAL | B_ERROR)) || bp->b_validend == 0 || (bp->b_validoff == 0 - && bp->b_validend == bp->b_bufsize))) { + && bp->b_validend == bp->b_bufsize)) */) { vm_ooffset_t foff; vm_object_t obj; int i, resid; -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 From owner-freebsd-current Mon Jun 2 05:12:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA15877 for current-outgoing; Mon, 2 Jun 1997 05:12:34 -0700 (PDT) Received: from scds.ziplink.net (scds.ziplink.net [206.15.128.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA15872 for ; Mon, 2 Jun 1997 05:12:31 -0700 (PDT) Received: (from jseger@localhost) by scds.ziplink.net (8.8.5/8.8.4) id HAA17189 for current@freebsd.org; Mon, 2 Jun 1997 07:22:34 -0400 (EDT) Date: Mon, 2 Jun 1997 07:22:34 -0400 (EDT) From: "Justin M. Seger" Message-Id: <199706021122.HAA17189@scds.ziplink.net> To: current@freebsd.org Subject: Compiling the source tree... Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can I compile the source tree as a normal account and then install it as root? Will there be any permission problems or anything else? Thanks in advance, -Justin Seger- From owner-freebsd-current Mon Jun 2 05:59:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA17857 for current-outgoing; Mon, 2 Jun 1997 05:59:26 -0700 (PDT) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA17852 for ; Mon, 2 Jun 1997 05:59:22 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id PAA05257 for current@freebsd.org; Mon, 2 Jun 1997 15:59:02 +0300 (EET DST) From: mika ruohotie Message-Id: <199706021259.PAA05257@shadows.aeon.net> Subject: Re: page fault In-Reply-To: <19970601222428.RH40488@uriah.heep.sax.de> from J Wunsch at "Jun 1, 97 10:24:28 pm" To: current@freebsd.org Date: Mon, 2 Jun 1997 15:59:01 +0300 (EET DST) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As mika ruohotie wrote: > Rebuild a few object files with -g, and see where it crashes in > ether_output(). i'm sorry but you lost me there... :\ little more info what exactly i gotta do and i should be able to do it... > > keep it on coz now it should not crash too often (i'm low on drive > If it's always the same spot, you only need one dump. true, but my machine doesnt know it if it keeps crashing alone. ofcourse, my dumps go to a filesystem i can afford to flood... > > will be going current (cvsup 20:30 EET DST Sun 1st) in 4 hours. > Nobody has changed anything in this area (if_ethersubr.c), nothing ok. btw, that make world was "ok", except that old tcl thing... > cheers, J"org mickey From owner-freebsd-current Mon Jun 2 07:35:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA21850 for current-outgoing; Mon, 2 Jun 1997 07:35:33 -0700 (PDT) Received: from Symbion.srrc.usda.gov (glenn@[199.78.118.118]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA21843 for ; Mon, 2 Jun 1997 07:35:26 -0700 (PDT) Received: (from glenn@localhost) by Symbion.srrc.usda.gov (8.8.5/8.8.5) id KAA28489 for freebsd-current@FreeBSD.ORG; Mon, 2 Jun 1997 10:32:55 -0500 Message-ID: X-Mailer: XFMail 1.1 [p0] on Linux Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 02 Jun 1997 10:27:42 -0500 (CDT) Organization: USDA-ARS-SRRC; CFQ From: Glenn Johnson To: freebsd-current@FreeBSD.ORG Subject: make world fails at xinstall Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I just cvsupped this morning and did a 'make world'. It fails at /usr/src/usr.bin/xinstall with undeclared functions of SF_NOUNLINK and UF_NOUNLINK. I remember a post a while back about a workaround for this, but I can't find the e-mail. Can someone help? ------------- Glenn Johnson USDA-ARS-SRRC; CFQ Phone: (504) 286-4252; FAX: (504) 286-4217 e-mail: gjohnson@nola.srrc.usda.gov From owner-freebsd-current Mon Jun 2 09:56:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA28337 for current-outgoing; Mon, 2 Jun 1997 09:56:07 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA28329 for ; Mon, 2 Jun 1997 09:56:04 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id CAA03936; Tue, 3 Jun 1997 02:52:26 +1000 Date: Tue, 3 Jun 1997 02:52:26 +1000 From: Bruce Evans Message-Id: <199706021652.CAA03936@godzilla.zeta.org.au> To: bde@zeta.org.au, dfr@nlsystems.com Subject: Re: processes hanging in getblk for shutdown on nfs client Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> On my nfs client system with /usr nfs-mounted, a plain reboot command >> now always leaves sendmail and/or xntpd hanging on getblk. The sync >Can you try this patch and see if it helps: It helps a little at best. sendmail once hung on nfsaio. The busy buffers in one case had flags: Bruce From owner-freebsd-current Mon Jun 2 11:12:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA03148 for current-outgoing; Mon, 2 Jun 1997 11:12:24 -0700 (PDT) Received: from mexico.brainstorm.eu.org (mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA03142 for ; Mon, 2 Jun 1997 11:12:18 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id UAA09501 for ; Mon, 2 Jun 1997 20:12:11 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id UAA09125 for current@FreeBSD.ORG; Mon, 2 Jun 1997 20:11:41 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id TAA22992; Mon, 2 Jun 1997 19:54:22 +0200 (CEST) Message-ID: <19970602195422.16538@keltia.freenix.fr> Date: Mon, 2 Jun 1997 19:54:22 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: Compiling the source tree... References: <199706021122.HAA17189@scds.ziplink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 In-Reply-To: <199706021122.HAA17189@scds.ziplink.net>; from Justin M. Seger on Mon, Jun 02, 1997 at 07:22:34AM -0400 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3332 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Justin M. Seger: > Can I compile the source tree as a normal account and then install it as root? > Will there be any permission problems or anything else? I am afraid it won't work if you want to use "make world". "make world" has several phases, many installing what has been just compiled like libraries, .mk files and so on. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #10: Fri May 23 22:47:39 CEST 1997 From owner-freebsd-current Mon Jun 2 12:40:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA07508 for current-outgoing; Mon, 2 Jun 1997 12:40:03 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA07429; Mon, 2 Jun 1997 12:39:49 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id VAA09606; Mon, 2 Jun 1997 21:39:42 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id VAA09967; Mon, 2 Jun 1997 21:39:11 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id VAA23641; Mon, 2 Jun 1997 21:38:05 +0200 (CEST) Message-ID: <19970602213805.05855@keltia.freenix.fr> Date: Mon, 2 Jun 1997 21:38:05 +0200 From: Ollivier Robert To: "FreeBSD Current Users' list" Cc: kato@FreeBSD.ORG Subject: Patch to display MMX feature bit Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3332 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to AMD's documentation, bit 23 of the CPUID value indicates that the MMX feature is supported. Here is a -- yet untested -- patch to display this bit. My P133 used to give me a value of 0x1bf or . My K6 has a value of 0x8001bf but displays the same string. With the patch, it will display . Index: identcpu.c =================================================================== RCS file: /spare/FreeBSD-current/src/sys/i386/i386/identcpu.c,v retrieving revision 1.21 diff -u -2 -r1.21 identcpu.c --- identcpu.c 1997/05/23 06:22:47 1.21 +++ identcpu.c 1997/06/02 19:37:17 @@ -381,4 +381,5 @@ "\017MCA" "\020CMOV" + "\030MMX" ); } PS: why is the bitfield in kprintf one-based ? -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #10: Fri May 23 22:47:39 CEST 1997 From owner-freebsd-current Mon Jun 2 14:42:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA14143 for current-outgoing; Mon, 2 Jun 1997 14:42:48 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA14119 for ; Mon, 2 Jun 1997 14:42:39 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA03753 for current@FreeBSD.ORG; Mon, 2 Jun 1997 23:42:31 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA12391; Mon, 2 Jun 1997 22:07:44 +0200 (MET DST) Message-ID: <19970602220739.KN28267@uriah.heep.sax.de> Date: Mon, 2 Jun 1997 22:07:39 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Subject: Re: page fault References: <19970601222428.RH40488@uriah.heep.sax.de> <199706021259.PAA05257@shadows.aeon.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706021259.PAA05257@shadows.aeon.net>; from mika ruohotie on Jun 2, 1997 15:59:01 +0300 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As mika ruohotie wrote: > > Rebuild a few object files with -g, and see where it crashes in > > ether_output(). > > i'm sorry but you lost me there... :\ > > little more info what exactly i gotta do and i should be able to do it... Well, if you don't know much about kernel debugging, it's always best to start with the section about kernel debugging in the handbook. :) I've answered these questions quite too often in the past, and thus decided to better write it down there. ;-) I'm still waiting on someone (was it Doug?) who promised to contribute the part about LKM debugging... I hope, after reading that stuff, you know what i mean by the above comment. > > > keep it on coz now it should not crash too often (i'm low on drive > > If it's always the same spot, you only need one dump. > > true, but my machine doesnt know it if it keeps crashing alone. > > ofcourse, my dumps go to a filesystem i can afford to flood... No need to flood filesystems with coredumps. /var/crash/minfree is your friend (and now finally works since FreeBSD 2.2). Could i hint you again to RTFM? :^) (minfree is documented.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Jun 2 14:55:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA15019 for current-outgoing; Mon, 2 Jun 1997 14:55:02 -0700 (PDT) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA15007 for ; Mon, 2 Jun 1997 14:54:57 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id AAA01794 for current@freebsd.org; Tue, 3 Jun 1997 00:54:27 +0300 (EET DST) From: mika ruohotie Message-Id: <199706022154.AAA01794@shadows.aeon.net> Subject: panic To: current@freebsd.org Date: Tue, 3 Jun 1997 00:54:27 +0300 (EET DST) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk now that i have the trace on, i might as well post the panics here, considering i run on the edge... ofcourse, if this is not helping, then i wont post them. this is kernel from sunday night 20:30 EET DST cvsup:ed src-base... (kgdb) where #0 0xf0114f2e in boot () #1 0xf011521a in panic () #2 0xf01c755a in trap_fatal () #3 0xf01c7009 in trap_pfault () #4 0xf01c6c8b in trap () #5 0xf01c5df9 in small_i586_bcopy () #6 0xf01d35f8 in edintr_sc () #7 0xf01d365a in edintr () #8 0x3057 in ?? () is the small_i586_bcopy already in the panic's side? or did it happen "there"? since it's been present in both panics i've got dumps from. crash again happened when the ether win95 caused "load" with it's netscape, bsd was probably idle since i was miles away. mickey From owner-freebsd-current Mon Jun 2 18:48:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA26653 for current-outgoing; Mon, 2 Jun 1997 18:48:31 -0700 (PDT) Received: from freebsd.scds.com (scds.ziplink.net [206.15.128.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA26648 for ; Mon, 2 Jun 1997 18:48:28 -0700 (PDT) Received: (from jseger@localhost) by freebsd.scds.com (8.8.5/8.8.4) id UAA03857 for current@freebsd.org; Mon, 2 Jun 1997 20:55:43 -0400 (EDT) Date: Mon, 2 Jun 1997 20:55:43 -0400 (EDT) From: "Justin M. Seger" Message-Id: <199706030055.UAA03857@freebsd.scds.com> To: current@freebsd.org Subject: Kernel building problems Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have the current sources as of today, 6/2/97... I get this error when building the kernel # make loading kernel vfs_init.o: Undefined symbol `_vfs_set' referenced from text segment vfs_init.o: Undefined symbol `_vfs_set' referenced from text segment *** Error code 1 Stop. Any ideas? Thanks in advance, -Justin Seger- From owner-freebsd-current Mon Jun 2 19:24:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA28119 for current-outgoing; Mon, 2 Jun 1997 19:24:17 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA28111 for ; Mon, 2 Jun 1997 19:24:10 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA17124; Mon, 2 Jun 1997 19:21:43 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd017119; Tue Jun 3 02:21:38 1997 Message-ID: <33937F82.2F1CF0FB@whistle.com> Date: Mon, 02 Jun 1997 19:20:50 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org CC: brian@awfulhak.org, archie@alpo.whistle.com Subject: Libalias probably broken Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just realised that libalias was *probably* broken by the ipfw changes I imported last night, as the method of controlling ipfw has changed. I'll get archie to have a look. julian From owner-freebsd-current Mon Jun 2 20:31:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA00749 for current-outgoing; Mon, 2 Jun 1997 20:31:31 -0700 (PDT) Received: from tok.qiv.com ([204.214.141.211]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA00740; Mon, 2 Jun 1997 20:31:13 -0700 (PDT) Received: (from uucp@localhost) by tok.qiv.com (8.8.5/8.8.5) with UUCP id WAA00421; Mon, 2 Jun 1997 22:30:57 -0500 (CDT) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.5/8.8.5) with SMTP id WAA00708; Mon, 2 Jun 1997 22:17:57 -0500 (CDT) X-Authentication-Warning: acp.qiv.com: jdn owned process doing -bs Date: Mon, 2 Jun 1997 22:17:57 -0500 (CDT) From: "Jay D. Nelson" To: Glenn Johnson cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: GIMP In-Reply-To: <199706020439.XAA07595@Gforce.iamerica.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It made clean and works fine on 2.2.1. -- Jay On Sun, 1 Jun 1997, Glenn Johnson wrote: ->Has anyone else had trouble with the 'gimp-devel 0.99.9 port'? I am running ->3.0 current and am getting the following: -> ->gmake[3]: Leaving directory `/usr/ports/graphics/gimp-devel/work/gimp-0.99.9/pl ->ug-ins/dgimp' ->gmake[2]: *** [all-recursive] Error 1 ->gmake[2]: Leaving directory `/usr/ports/graphics/gimp-devel/work/gimp-0.99.9/pl ->ug-ins' ->gmake[1]: *** [all-recursive] Error 1 ->gmake[1]: Leaving directory `/usr/ports/graphics/gimp-devel/work/gimp-0.99.9' ->gmake: *** [all-recursive-am] Error 2 ->*** Error code 2 -> ->Stop. ->*** Error code 1 -> ->Stop. ->*** Error code 1 -> ->Stop. -> ->Thanks for any help. ->-- ->Glenn Johnson ->gljohnsn@iamerica.net -> -> From owner-freebsd-current Tue Jun 3 00:30:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA13149 for current-outgoing; Tue, 3 Jun 1997 00:30:46 -0700 (PDT) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA13129 for ; Tue, 3 Jun 1997 00:30:41 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id KAA09291 for current@freebsd.org; Tue, 3 Jun 1997 10:30:19 +0300 (EET DST) From: mika ruohotie Message-Id: <199706030730.KAA09291@shadows.aeon.net> Subject: Re: page fault In-Reply-To: <19970602220739.KN28267@uriah.heep.sax.de> from J Wunsch at "Jun 2, 97 10:07:39 pm" To: current@freebsd.org Date: Tue, 3 Jun 1997 10:30:19 +0300 (EET DST) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > i'm sorry but you lost me there... :\ > Well, if you don't know much about kernel debugging, it's always best > to start with the section about kernel debugging in the handbook. :) hmm, last time i checked, it didnt look like that... > I've answered these questions quite too often in the past, and thus > decided to better write it down there. ;-) good. =) > I hope, after reading that stuff, you know what i mean by the above > comment. yes, but i failed to get kernel -g:ed. i guess after this i'll use the 'config -g' as default. > > ofcourse, my dumps go to a filesystem i can afford to flood... > No need to flood filesystems with coredumps. /var/crash/minfree is > your friend (and now finally works since FreeBSD 2.2). Could i hint > you again to RTFM? :^) (minfree is documented.) yes, yes... > cheers, J"org mickey From owner-freebsd-current Tue Jun 3 01:47:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA16687 for current-outgoing; Tue, 3 Jun 1997 01:47:29 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA16682 for ; Tue, 3 Jun 1997 01:47:27 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id JAA05297; Tue, 3 Jun 1997 09:47:11 +0100 (BST) Date: Tue, 3 Jun 1997 09:47:11 +0100 (BST) From: Doug Rabson To: Joerg Wunsch cc: current@freebsd.org Subject: Re: page fault In-Reply-To: <19970602220739.KN28267@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 2 Jun 1997, J Wunsch wrote: > I'm still waiting on someone (was it Doug?) who promised to contribute > the part about LKM debugging... Hey! I committed that *ages* ago. You reviewed it too :-) -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 From owner-freebsd-current Tue Jun 3 08:01:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA02563 for current-outgoing; Tue, 3 Jun 1997 08:01:29 -0700 (PDT) Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA02495 for ; Tue, 3 Jun 1997 08:00:55 -0700 (PDT) Received: from itfs.UUCP (uucp@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id UAA24152 for current@freebsd.org; Tue, 3 Jun 1997 20:41:04 +0700 Received: by itfs.nsk.su; Tue, 3 Jun 97 20:48:22 +0700 (NST) Received: (from daemon@localhost) by news.itfs.nsk.su (8.7.5/8.6.12) id UAA24808; Tue, 3 Jun 1997 20:22:54 +0700 (NSD) From: nnd@itfs.nsk.su To: current@freebsd.org Subject: SMP-aware boot.flp anywhere ? Date: 3 Jun 1997 13:22:49 GMT Message-ID: <5n15r9$id8@news.itfs.nsk.su> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can I find somewhere boot.flp with SMP-aware kernel (SMP-GENERIC or even better configured for two P-133 on Gateway GA-596DX motherboard with onboard UW SCSI controller and one 2.1 GB Seagate Medalist HD). On thursday I will receive my new computer in Moscow and want to test it here before I come home (in Novosibirsk) with it and discover some problems ;-) N.Dudorov From owner-freebsd-current Tue Jun 3 11:20:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA13991 for current-outgoing; Tue, 3 Jun 1997 11:20:45 -0700 (PDT) Received: from Symbion.srrc.usda.gov (glenn@[199.78.118.118]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA13981 for ; Tue, 3 Jun 1997 11:20:40 -0700 (PDT) Received: (from glenn@localhost) by Symbion.srrc.usda.gov (8.8.5/8.8.5) id OAA03935 for freebsd-current@FreeBSD.ORG; Tue, 3 Jun 1997 14:17:40 -0500 Message-ID: X-Mailer: XFMail 1.1 [p0] on Linux Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 03 Jun 1997 14:10:55 -0500 (CDT) Organization: USDA-ARS-SRRC; CFQ From: Glenn Johnson To: freebsd-current@FreeBSD.ORG Subject: Second processor not being used? Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I just install a second Pentium Pro processor in my system. I built an SMP kernel, rebooted, and the second processor is found and brought online. However, it does not appear to do anything. I submitted two jobs that each require about 3 hours of computation time (very little disk I/O). Both jobs were being run from the primary processor however. Is there something I need to do to tell a job to go to a certain processor? Please help. ------------- Glenn Johnson USDA-ARS-SRRC; CFQ Phone: (504) 286-4252; FAX: (504) 286-4217 e-mail: gjohnson@nola.srrc.usda.gov From owner-freebsd-current Tue Jun 3 11:40:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA15276 for current-outgoing; Tue, 3 Jun 1997 11:40:29 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA15271 for ; Tue, 3 Jun 1997 11:40:23 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id TAA27469; Tue, 3 Jun 1997 19:39:43 +0100 (BST) Message-Id: <199706031839.TAA27469@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: Julian Elischer cc: current@freebsd.org, brian@awfulhak.org, archie@alpo.whistle.com, Ari Suutari Subject: Re: Libalias probably broken In-reply-to: Your message of "Mon, 02 Jun 1997 19:20:50 PDT." <33937F82.2F1CF0FB@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Jun 1997 19:39:43 +0100 From: Brian Somers Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I just realised that libalias was *probably* broken by the ipfw > changes I imported last night, as the method of controlling ipfw > has changed. > > I'll get archie to have a look. I'd be surprised if there are any problems. The libalias stuff is standalone - you pass it a packet and it fondles it and gives it back. The only possible changes are with the natd instructions (I've cc'd this to Ari, the author). I'll take a look and pass back any mods to Ari. > julian -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-current Tue Jun 3 14:14:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA23059 for current-outgoing; Tue, 3 Jun 1997 14:14:42 -0700 (PDT) Received: from mailhub.Stanford.EDU (mailhub.Stanford.EDU [36.21.0.128]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA23054 for ; Tue, 3 Jun 1997 14:14:40 -0700 (PDT) Received: from tree2.Stanford.EDU (tree2.Stanford.EDU [36.83.0.37]) by mailhub.Stanford.EDU (8.8.5/8.8.5/L) with SMTP id OAA19259; Tue, 3 Jun 1997 14:14:23 -0700 (PDT) Date: Tue, 3 Jun 1997 14:14:07 -0700 (PDT) From: "Amr A. Awadallah" Subject: TCP: Brief Comment on cwnd Inflation during Fast Recovery. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII To: undisclosed-recipients:; Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk All, For those of you who expressed interest in our comments on the effects of cwnd inflation. We added more comments/results on this subject at this URL ( http://www-leland.stanford.edu/~aaa/tcp ). We included the patch (diff file) for the current FreeBSD tcp_input.c. We would appreciate it if interested developers provide feedback to us about this change (in terms of observed throughput). The change is only a couple of lines of code and apparently leads to higher throughput TCP sources. We also provide arguments for and against the modification. The main argument for the modification is that with the current cwnd inflation, more packets are being sent into the network during the fast recovery period at the rate at which duplicate-ACKs are coming back. Which is counter intuitive to the fact that entering fast recovery means that the TCP source just lost a packet (indicated by the duplicate ACKs), hence the source should throttle back its sending rate. By continuing to send at the rate at which duplicate ACKs are coming back, the source may force the network to drop another one of its packets (e.g. due to RED gateways [Floyd and Jacobsen, IEEE Transactions on Networking, August 1993], or simple buffer overflow). This may lead to invoking another fast recovery cycle, or worse invoking slow-start (this can be clearly seen in the cwnd vs time plots on the web page). The modification we did provides the network a breathing period of less than 1 RTT which allows the network to catch up its breath by dequeuing congested buffers. This avoids another packet loss, thus leading to a smoother cwnd vs time behavior. It still allows for packets to be sent during the fast recovery period but at a much lower rate. The main argument against the modification is that by using normal congestion avoidance cwnd-increase during the fast recovery period (rather than cwnd inflation), the source will not be able to keep the pipe full (thus violating VJ recommendations). Hence this leads to a burst of back-to-back packets at the end of the fast recovery period. We note though that schemes like FACK [Mathis and Mahdavi SIGCOMM '96] allows for the regulation of such a burst (by pacing the burst). SACK [Floyd and Fall CCR paper] also tackles this problem. We also note that this burst of back-to-back packets is known to exist in current TCP implementations (at least we observed it rather frequently in FreeBSD 2.1.6, as shown on the web). The burst simply occurs due to cwnd sliding a considerable distance when the non-duplicate ACK arrives, hence opening up lots of space for new packets to be sent. The modification leads to a more aggressive TCP source since it starts with a larger window size at the end of the fast-recovery period. It has also been pointed to us that most TCP researchers think the principles behind the current fast recovery algorithm works well. One last comment, we stumbled on the cwnd inflation spikes during our research on TCP (which is on a totally different aspect). The spikes appeared strange to us at first because in most papers on TCP congestion avoidance (at least those that we read), one would rarely see a cwnd vs time plot showing the cwnd inflation spikes. This was the main reason why we were originally misled to believe that this was a bug in TCP, until others corrected us by pointing out that this is truly how fast recovery was designed to work (that is the spikes are a feature of TCP ! ). Thanks for your interest and feedback, Sincerely, Amr A. Awadallah (aaa@stanford.edu) Chetan Rai (crai@cs.stanford.edu) ----------------------------------------------------- PS: Sorry if you receive this e-mail more than once, this means you are subscribed to too many mailing lists :) From owner-freebsd-current Tue Jun 3 14:44:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA24876 for current-outgoing; Tue, 3 Jun 1997 14:44:37 -0700 (PDT) Received: from wall.jhs.no_domain (vector.muc.ditec.de [194.120.126.35]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA24861 for ; Tue, 3 Jun 1997 14:44:32 -0700 (PDT) Received: (from jhs@localhost) by desk.jhs.no_domain (8.8.5/8.8.5) id XAA23660; Tue, 3 Jun 1997 23:39:26 +0200 (MET DST) Date: Tue, 3 Jun 1997 23:39:26 +0200 (MET DST) Message-Id: <199706032139.XAA23660@desk.jhs.no_domain> To: current@freebsd.org Subject: How about creating ctm-users@ & cvsup-users@ ? From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" X-Email: jhs@freebsd.org, Fallback: jhs@gil.physik.rwth-aachen.de X-Web: http://www.freebsd.org/~jhs/ X-Company: Vector Systems Ltd, Unix & Internet Consultants. X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Tel: Phone +49.89.268616, Fax +49.89.2608126, Data +49.89.26023276 X-Software: FreeBSD (Unix) + EXMH 1.6.9 (PGP key on web) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Perhaps we should consider creating 2 new mail lists ? ctm-users@freebsd.org cvsup-users@freebsd.org to reduce traffic in current@. The new lists would save cvsup users reading irrelevant ctm problems, & ctm users reading irrelevant cvsup problems. There's only ctm-announce & ctm-[thing-you-want] at present. I see a cvs-user list but with no definition in my archived 1997.04.13 majordomo list ), Although ctm-announce is missing a definition, I assume it to be for CTM masters announcing solutions, not for consumers mentioning problems. PS I posted this to current@, but it equally applies to stable users too (but not cross posted to stable too, to avoid cross-talk). Julian --- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Tue Jun 3 14:44:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA24889 for current-outgoing; Tue, 3 Jun 1997 14:44:41 -0700 (PDT) Received: from wall.jhs.no_domain (vector.muc.ditec.de [194.120.126.35]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA24867 for ; Tue, 3 Jun 1997 14:44:35 -0700 (PDT) Received: (from jhs@localhost) by desk.jhs.no_domain (8.8.5/8.8.5) id XAA23666; Tue, 3 Jun 1997 23:39:33 +0200 (MET DST) Date: Tue, 3 Jun 1997 23:39:33 +0200 (MET DST) Message-Id: <199706032139.XAA23666@desk.jhs.no_domain> To: current@freebsd.org Subject: ftp.FreeBSD.ORG/pub/FreeBSD/CTM/cvs-cur/cvs-cur.3341.gz From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" X-Email: jhs@freebsd.org, Fallback: jhs@gil.physik.rwth-aachen.de X-Web: http://www.freebsd.org/~jhs/ X-Company: Vector Systems Ltd, Unix & Internet Consultants. X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Tel: Phone +49.89.268616, Fax +49.89.2608126, Data +49.89.26023276 X-Software: FreeBSD (Unix) + EXMH 1.6.9 (PGP key on web) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Archive incomplete: ftp.FreeBSD.ORG/pub/FreeBSD/CTM/cvs-cur/cvs-cur.3341.gz does not exist, only: -rw-r--r-- 1 1 ftp-Free 25804 May 28 07:52 cvs-cur.3340.gz -rw-r--r-- 1 1 ftp-Free 16293 May 31 15:24 cvs-cur.3342.gz -rw-r--r-- 1 1 ftp-Free 7717 May 31 23:27 cvs-cur.3343.gz -rw-r--r-- 1 1 ftp-Free 8530 Jun 1 07:30 cvs-cur.3344.gz -rw-r--r-- 1 1 ftp-Free 6537 Jun 1 15:22 cvs-cur.3345.gz -rw-r--r-- 1 1 ftp-Free 24407 Jun 1 23:47 cvs-cur.3346.gz -rw-r--r-- 1 1 ftp-Free 33889 Jun 2 07:52 cvs-cur.3347.gz -rw-r--r-- 1 1 ftp-Free 39559 Jun 2 15:26 cvs-cur.3348.gz -rw-r--r-- 1 1 ftp-Free 9876 Jun 2 23:35 cvs-cur.3349.gz -rw-r--r-- 1 1 ftp-Free 36519 Jun 3 07:51 cvs-cur.3350.gz ftp.uni-trier.de/pub/unix/systems/BSD/FreeBSD/CTM/cvs-cur/cvs-cur.3341.gz was fully loaded, so couldnt get in to look. Julian --- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Wed Jun 4 00:31:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA01566 for current-outgoing; Wed, 4 Jun 1997 00:31:45 -0700 (PDT) Received: from user2.inficad.com (straka@user2.inficad.com [207.19.74.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA01558 for ; Wed, 4 Jun 1997 00:31:43 -0700 (PDT) Received: from localhost (straka@localhost) by user2.inficad.com (8.8.5/8.7.3) with SMTP id AAA15660 for ; Wed, 4 Jun 1997 00:31:54 -0700 (MST) Date: Wed, 4 Jun 1997 00:31:54 -0700 (MST) From: Richard Straka To: current@freebsd.org Subject: sio driver performance Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have 2 16550A UARTS in a 486DX-33. During probing, the sio driver properly identifies both ports as 16550A's. When sending sustained 115200 baud data from this machine, systat (with vmstat option) indicates an interrupt rate of about 720/sec with about 2% of the processor servicing interrupts. When receiving sustained 115200 baud data, an interrupt rate of over 26,000/sec is indicated with about 15% of the processor going to service interrupts. It appears as though the fifo is not working for the receive. In an attempt to exhonerate the hardware, I swapped in another 16550 card I had laying around and got the similar results. Any help on this issue would be greatly appreciated. Richard Straka straka@inficad.com From owner-freebsd-current Wed Jun 4 00:43:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA03290 for current-outgoing; Wed, 4 Jun 1997 00:43:44 -0700 (PDT) Received: from user2.inficad.com (straka@user2.inficad.com [207.19.74.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA03281 for ; Wed, 4 Jun 1997 00:43:42 -0700 (PDT) Received: from localhost (straka@localhost) by user2.inficad.com (8.8.5/8.7.3) with SMTP id AAA15916 for ; Wed, 4 Jun 1997 00:43:55 -0700 (MST) Date: Wed, 4 Jun 1997 00:43:54 -0700 (MST) From: Richard Straka To: current@freebsd.org Subject: Re: sio driver performance In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 4 Jun 1997, Richard Straka wrote: > I have 2 16550A UARTS in a 486DX-33. During probing, the sio > driver properly identifies both ports as 16550A's. > > When sending sustained 115200 baud data from this machine, systat > (with vmstat option) indicates an interrupt rate of about 720/sec > with about 2% of the processor servicing interrupts. > When receiving sustained 115200 baud data, an interrupt rate of > over 26,000/sec is indicated with about 15% of the processor going > to service interrupts. > > It appears as though the fifo is not working for the receive. In an > attempt to exhonerate the hardware, I swapped in another 16550 card > I had laying around and got the similar results. > > Any help on this issue would be greatly appreciated. > I neglected to mention that I am running 2.2.1-RELEASE on the 486DX-33. Richard Straka straka@inficad.com From owner-freebsd-current Wed Jun 4 01:01:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA04779 for current-outgoing; Wed, 4 Jun 1997 01:01:42 -0700 (PDT) Received: from fox.uni-trier.de (blank@fox.uni-trier.de [136.199.8.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA04771; Wed, 4 Jun 1997 01:01:34 -0700 (PDT) Received: (from blank@localhost) by fox.uni-trier.de (8.8.5/8.8.5) id KAA18820; Wed, 4 Jun 1997 10:02:05 +0200 From: Sascha Blank Message-Id: <199706040802.KAA18820@fox.uni-trier.de> Subject: Re: ftp.FreeBSD.ORG/pub/FreeBSD/CTM/cvs-cur/cvs-cur.3341.gz In-Reply-To: <199706032139.XAA23666@desk.jhs.no_domain> from "Julian H. Stacey" at "Jun 3, 97 11:39:33 pm" To: jhs@FreeBSD.ORG Date: Wed, 4 Jun 1997 10:02:04 +0200 (MET DST) Cc: current@FreeBSD.ORG Reply-To: blank@fox.uni-trier.de (Sascha Blank) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello Julia, > ftp.uni-trier.de/pub/unix/systems/BSD/FreeBSD/CTM/cvs-cur/cvs-cur.3341.gz > was fully loaded, so couldnt get in to look. Yes, we've got it: -rw-rw-r-- 1 fbsdctm 185158 May 31 18:22 cvs-cur.3341.gz If you have problems getting into our site you might want to try out our ftpmail server. Send a mail with the subject "help" to ftpmail@ftp.uni-trier.de. I know it's now the most comfortable interface, but your request will be treated within some minutes. -- Sascha Blank - mailto:blank@fox.uni-trier.de Student and System Administrator at the University of Trier, Germany Finger my account to receive my Public PGP key I don't speak for my employers, they don't pay me enough for that. From owner-freebsd-current Wed Jun 4 01:40:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA06983 for current-outgoing; Wed, 4 Jun 1997 01:40:54 -0700 (PDT) Received: from hydrogen.nike.efn.org (metriclient-5.uoregon.edu [128.223.172.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA06978 for ; Wed, 4 Jun 1997 01:40:50 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id BAA26258; Wed, 4 Jun 1997 01:41:35 -0700 (PDT) Message-ID: <19970604014135.27671@hydrogen.nike.efn.org> Date: Wed, 4 Jun 1997 01:41:35 -0700 From: John-Mark Gurney To: Richard Straka Cc: current@FreeBSD.ORG Subject: Re: sio driver performance References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Richard Straka on Wed, Jun 04, 1997 at 12:31:54AM -0700 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Richard Straka scribbled this message on Jun 4: > I have 2 16550A UARTS in a 486DX-33. During probing, the sio > driver properly identifies both ports as 16550A's. > > When sending sustained 115200 baud data from this machine, systat > (with vmstat option) indicates an interrupt rate of about 720/sec > with about 2% of the processor servicing interrupts. > > When receiving sustained 115200 baud data, an interrupt rate of > over 26,000/sec is indicated with about 15% of the processor going > to service interrupts. > > It appears as though the fifo is not working for the receive. In an > attempt to exhonerate the hardware, I swapped in another 16550 card > I had laying around and got the similar results. it actually is working quite nicely... if it wasn't you would see 115,200 * 2 interrupts/sec if the fifo isn't working... but what you are probably seeing is that the recieve fifo is set to 8bytes instead of 14bytes (115200*2/26000 ~= 8.8615...)... also, it's a know fact that the 16550's are kinda heavy on overhead (not as bad as a parallel port though)... if you want to do many ports at full speed you really should invest in a smarter card, like a Digiboard/Cyclom/Riscom/Stallion smart board that has larger buffers and usually supports mapped memory access... > Any help on this issue would be greatly appreciated. if you get any kernel messages about sio, then you need to start worring... if you do plan to enable multiport usage (when you get a Boca or AST compatible board) when you need to look out, and I'm about to test/improve the sio so multiport doesn't hurt as much... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-current Wed Jun 4 03:59:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA17476 for current-outgoing; Wed, 4 Jun 1997 03:59:02 -0700 (PDT) Received: from nexis.net (customer-1.ican.net [198.133.36.101]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA17471 for ; Wed, 4 Jun 1997 03:59:00 -0700 (PDT) Received: from localhost (james@localhost) by nexis.net (8.8.5/8.8.5) with SMTP id GAA09062 for ; Wed, 4 Jun 1997 06:58:48 -0400 (EDT) Date: Wed, 4 Jun 1997 06:58:47 -0400 (EDT) From: James FitzGibbon To: current@freebsd.org Subject: Re: Use of your strptime(3) code (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk When I was trying to port mSQL-2.0b5, I needed a strptime(3) call, which we don't have. Although the need for it in mSQL-2 is no longer required, it might be a valuable addition to libcompat, since most SVR4 systems have it. This company (Powerdog Industries) have a strptime implementation that looks like we could use. It's already been added to NetBSD (sometime after v1.2 as far as I can tell) I can't seem to find the original .shar anymore, but it is available as part of the Solaris 2 Porting FAQ, found at http://ume.med.ucalgary.ca/usenet/Solaris/0377.html (and many other places I'm sure) If this is something worthy of going it, can someone add it, or should I attempt ? I've never modified the main source tree before, but If I can make it work as part of libcompat on my personal machine... ---------- Forwarded message ---------- Date: Tue, 03 Jun 1997 22:15:59 -0400 From: Kevin Ruddy To: James FitzGibbon Subject: Re: Use of your strptime(3) code This goes to show you how often I really keep up with my e-mail ... What I'd prefer to see, if you still need this, is putting it in the compat library. If that is impossible, you have my permission, as president of Powerdog Industries, to go ahead and use it in your goal to port mSQL. (Including, of course, the comment in the ports file.) I apologize for the delay, and I hope it didn't cause undue problems. Kevin Ruddy Powerdog Industries, Inc. James FitzGibbon wrote: > I'm in a bit of strange situtation with regards to using your strptime(3) > code in a program I'm working with. > > I'm part of the FreeBSD ports team. The FreeBSD ports collection > essentially amounts to a collection of makefile wrappers that lets one > change to a directory for a particular program, type 'make install', and > have the original source for the program fetched, extracted, patched (if > necessary), compiled, and installed. > > I'm trying to upgrade my port of mSQL (a lightweight SQL database). In > the latest beta release, the author makes use of strptime, which doesn't > come with FreeBSD. > > I'd like to include your strptime.c with my port, and have my patches > build it into just the msql binary. This does work (I'm sure many people > who have compiled the program themselves have already availed themselves > of your code), but in doing so, I'd break #3 of your License. I don't own > mSQL or FreeBSD, so I can't modify the advertising medium used. > > Can I have your permission to use the strptime code in just this program ? > I will add a notice re: Powerdog to the port's description file, which is > the closest one can come to 'advertising' a particular port. > > Alternatively, if you want the notice to appear directly related to > FreeBSD, I could ask the development team about the possibility of putting > into our compat library. Then, it would be easier to make the notice > publically available. > > Thanks for your help. From owner-freebsd-current Wed Jun 4 08:53:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA06126 for current-outgoing; Wed, 4 Jun 1997 08:53:43 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA06115 for ; Wed, 4 Jun 1997 08:53:38 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA02477 for current@FreeBSD.ORG; Wed, 4 Jun 1997 17:53:25 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id RAA20018; Wed, 4 Jun 1997 17:49:18 +0200 (MET DST) Message-ID: <19970604174918.CS56609@uriah.heep.sax.de> Date: Wed, 4 Jun 1997 17:49:18 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Subject: Re: page fault References: <19970602220739.KN28267@uriah.heep.sax.de> <199706030730.KAA09291@shadows.aeon.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706030730.KAA09291@shadows.aeon.net>; from mika ruohotie on Jun 3, 1997 10:30:19 +0300 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As mika ruohotie wrote: > > I hope, after reading that stuff, you know what i mean by the above > > comment. > > yes, but i failed to get kernel -g:ed. i guess after this i'll use > the 'config -g' as default. Be careful to not accidentally load this bloated kernel into memory. :) Also, i found the time ld(1) requires to link a full -g kernel to be enormous. Normally, if i just wanna examine a core dump, i modify the Makefile to use the same cc options as before (notably the same optimization level), but add -g. NB: you gotta replace the COPTS ?= line by an absolute one. Then, i remove the .o files i wanna force to rebuild, and just rebuild this part of the kernel. After this, you can usually analyze the stacktrace. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Jun 4 08:56:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA06407 for current-outgoing; Wed, 4 Jun 1997 08:56:51 -0700 (PDT) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA06396 for ; Wed, 4 Jun 1997 08:56:42 -0700 (PDT) Received: from harlie.bfd.com (bastion.bfd.com [204.160.242.14]) by horst.bfd.com (8.8.5/8.7.3) with SMTP id IAA08082; Wed, 4 Jun 1997 08:56:21 -0700 (PDT) Date: Wed, 4 Jun 1997 08:56:21 -0700 (PDT) From: "Eric J. Schwertfeger" To: John-Mark Gurney cc: Richard Straka , current@FreeBSD.ORG Subject: Re: sio driver performance In-Reply-To: <19970604014135.27671@hydrogen.nike.efn.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 4 Jun 1997, John-Mark Gurney wrote: > Richard Straka scribbled this message on Jun 4: > > When receiving sustained 115200 baud data, an interrupt rate of > > over 26,000/sec is indicated with about 15% of the processor going > > to service interrupts. > > > > It appears as though the fifo is not working for the receive. In an > > attempt to exhonerate the hardware, I swapped in another 16550 card > > I had laying around and got the similar results. > > it actually is working quite nicely... if it wasn't you would see > 115,200 * 2 interrupts/sec if the fifo isn't working... but what > you are probably seeing is that the recieve fifo is set to 8bytes > instead of 14bytes (115200*2/26000 ~= 8.8615...)... No, since 10 bits Async=1 byte to transfer, that actually looks like (115200/10)*2/26000 ~= 0.88615. Now, the fact that a 486/33 can handle 26,000 interupts/sec under FreeBSD is impressive, but it still sounds like the UART is receiving either in unbuffered mode, or with a trigger level of 1 (hopefully the latter, though it doesn't seem to be a real problem). > also, it's a know fact that the 16550's are kinda heavy on overhead > (not as bad as a parallel port though)... if you want to do many > ports at full speed you really should invest in a smarter card, > like a Digiboard/Cyclom/Riscom/Stallion smart board that has larger > buffers and usually supports mapped memory access... Any suggestions for a single port, smart serial card that is supported and can go past 115200? I'm going to be checking some serial cards that will run 16X50's and feed them a higher than normal clock, and don't expect to see any problems, (Especially not with a DX4/120 on one end, and PPro/166 on the other). From owner-freebsd-current Wed Jun 4 09:45:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA09521 for current-outgoing; Wed, 4 Jun 1997 09:45:31 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA09511 for ; Wed, 4 Jun 1997 09:45:29 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-10.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA24713 (5.67b/IDA-1.5 for ); Wed, 4 Jun 1997 18:45:12 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id SAA13588; Wed, 4 Jun 1997 18:45:10 +0200 (CEST) X-Face: " Date: Wed, 4 Jun 1997 18:45:09 +0200 From: Stefan Esser To: John-Mark Gurney Cc: Richard Straka , current@FreeBSD.ORG Subject: Re: sio driver performance References: <19970604014135.27671@hydrogen.nike.efn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <19970604014135.27671@hydrogen.nike.efn.org>; from John-Mark Gurney on Wed, Jun 04, 1997 at 01:41:35AM -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 4, John-Mark Gurney wrote: > Richard Straka scribbled this message on Jun 4: > > I have 2 16550A UARTS in a 486DX-33. During probing, the sio > > driver properly identifies both ports as 16550A's. > > > > When sending sustained 115200 baud data from this machine, systat > > (with vmstat option) indicates an interrupt rate of about 720/sec > > with about 2% of the processor servicing interrupts. > > > > When receiving sustained 115200 baud data, an interrupt rate of > > over 26,000/sec is indicated with about 15% of the processor going > > to service interrupts. > > > > It appears as though the fifo is not working for the receive. In an > > attempt to exhonerate the hardware, I swapped in another 16550 card > > I had laying around and got the similar results. > > it actually is working quite nicely... if it wasn't you would see > 115,200 * 2 interrupts/sec if the fifo isn't working... but what One interrupt per **bit** received ??? Well, I thought the UART did provide you with bytes :) > you are probably seeing is that the recieve fifo is set to 8bytes > instead of 14bytes (115200*2/26000 ~= 8.8615...)... (11520/10)/14 ~= 825 int/s per port (using a FIFO depth of 14, which allows for 170us max. interrupt latency) (11520/10)/8 ~= 1440 int/s per port (using a FIFO depth of 8, => 700us) > also, it's a know fact that the 16550's are kinda heavy on overhead > (not as bad as a parallel port though)... if you want to do many > ports at full speed you really should invest in a smarter card, > like a Digiboard/Cyclom/Riscom/Stallion smart board that has larger > buffers and usually supports mapped memory access... Well, the 16550's FIFO will be read a byte a time, and that means you will be limited to a few MB/s (Bruce Evans did some testing of ISA port latencies, recently, and posted his results). This makes some 10 microseconds per 14 bytes (if the receive FIFO was set to 14 bytes, that is). A FIFO depth of 8 will reduce the time to read out those 8 bytes to some 5 microseconds. This amounts to 7 milli- seconds per second (or just below 1%) per port, not taking the interrupt handler overhead into account ... Regards, STefan From owner-freebsd-current Wed Jun 4 09:52:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA09986 for current-outgoing; Wed, 4 Jun 1997 09:52:41 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA09977 for ; Wed, 4 Jun 1997 09:52:36 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA03300; Wed, 4 Jun 1997 18:52:28 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id SAA20540; Wed, 4 Jun 1997 18:31:47 +0200 (MET DST) Message-ID: <19970604183147.OA09251@uriah.heep.sax.de> Date: Wed, 4 Jun 1997 18:31:47 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Cc: james@nexis.net (James FitzGibbon) Subject: Re: Use of your strptime(3) code (fwd) References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from James FitzGibbon on Jun 4, 1997 06:58:47 -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As James FitzGibbon wrote: > This company (Powerdog Industries) have a strptime implementation that > looks like we could use. It's already been added to NetBSD (sometime > after v1.2 as far as I can tell) I thought about adding it to the regular libc, but as i've been partways through, i noticed the overly restrictive copyright again (no modifications allowed whatsoever). It is plain unacceptable with this copyright, and unless Powerdog can make this less restrictive, i consider rewriting it from scratch (sigh). The need for modification arises out of two things: . adding localization (it basically can share the same localization hooks strftime is using), . fixing bugs like the incompatible use of %C, which means something totally different in BSD, . adding missing specifications. Good that you've got an email address for them, the source doesn't have one. If they agree to delete the `without modifications' clause from the copyright, i can probably make what i've got so far commit-ready within one hour or so. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Jun 4 11:13:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA15963 for current-outgoing; Wed, 4 Jun 1997 11:13:08 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA15934; Wed, 4 Jun 1997 11:12:54 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA23097; Wed, 4 Jun 1997 11:11:00 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd023095; Wed Jun 4 18:10:59 1997 Message-ID: <3395AF81.4487EB71@whistle.com> Date: Wed, 04 Jun 1997 11:10:09 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org CC: dyson@freebsd.org Subject: rfork() man page wrong? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've checked the man page and the sources.. it appears to me that the following section of the man page is wrong.. john, if you are reading, can you check if this is what you understand? ------- RFMEM If set, the kernel will force sharing of the entire ad- dress space. The child will then inherit all the shared segments the parent process owns. Other segment types will be unaffected. Subsequent forks by the parent will then propagate the shared data and bss between children. The stack segment is always split. May be set only with RFPROC. -------- now, as I read it, the section "The child will then inherit all the shared segments the parent process owns. Other segment types will be unaffected." is wrong because in RFMEM case, the vmspace is simply referenced twice, once by each process. regardless of how what segments it is made up of. (in the vm code.) if (flags & RFMEM) { p2->p_vmspace = p1->p_vmspace; p1->p_vmspace->vm_refcnt++; } also: "The stack segment is always split." seems to also be wrong.. (or is the stack not in the vmspace?) though of course there is a separate kernel stack. julian From owner-freebsd-current Wed Jun 4 13:47:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA08060 for current-outgoing; Wed, 4 Jun 1997 13:47:32 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA08052 for ; Wed, 4 Jun 1997 13:47:29 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id GAA16361; Thu, 5 Jun 1997 06:43:58 +1000 Date: Thu, 5 Jun 1997 06:43:58 +1000 From: Bruce Evans Message-Id: <199706042043.GAA16361@godzilla.zeta.org.au> To: gurney_j@resnet.uoregon.edu, straka@inficad.com Subject: Re: sio driver performance Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> When receiving sustained 115200 baud data, an interrupt rate of >> over 26,000/sec is indicated with about 15% of the processor going >> to service interrupts. >> >> It appears as though the fifo is not working for the receive. In an >> attempt to exhonerate the hardware, I swapped in another 16550 card >> I had laying around and got the similar results. It works for most users. Possible problems: - noisy cables may cause a modem status interrupt for every character (or every changed bit?). - a parity mismatch may cause a line status interrupt for every character. This problem is easy to reproduce using `stty parenb ...' to change the default of 8 bits-no parity to 9 bits-1 parity bit. - a hardware bug on UMC8669F devices that prevents initialization of the fifo trigger level while data is arriving. These devices also have a h/w bug that prevents initialization of the speed while data is arriving. Both bugs are more common in tests than in normal operation. I always see the fifo bug here if I start the transmitter first. FreeBSD transmitters do a perfect job of keeping the data flowing, so the receiver never has a chance to recover :-). >it actually is working quite nicely... if it wasn't you would see >115,200 * 2 interrupts/sec if the fifo isn't working... but what >you are probably seeing is that the recieve fifo is set to 8bytes >instead of 14bytes (115200*2/26000 ~= 8.8615...)... Nope. See other replies. >also, it's a know fact that the 16550's are kinda heavy on overhead >(not as bad as a parallel port though)... if you want to do many >ports at full speed you really should invest in a smarter card, >like a Digiboard/Cyclom/Riscom/Stallion smart board that has larger >buffers and usually supports mapped memory access... The overheads for most of these boards (all except possibly Digiboard and the 'i' version of Stallion) are just as large as for 16550's. cd180's and cd1400's have smaller fifos (12 bytes instead of 16). Memory mapped access is not significantly faster, at least for ISA boards... Bruce From owner-freebsd-current Wed Jun 4 14:56:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA15345 for current-outgoing; Wed, 4 Jun 1997 14:56:55 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA15337; Wed, 4 Jun 1997 14:56:52 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id OAA08904; Wed, 4 Jun 1997 14:56:57 -0700 (PDT) To: announce@freebsd.org cc: current@freebsd.org Reply-To: current@freebsd.org Subject: current.freebsd.org / releng22.freebsd.org back on line. Date: Wed, 04 Jun 1997 14:56:57 -0700 Message-ID: <8900.865461417@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The server producing snapshots of the 3.0-current and 2.2-stable branches is now back on line. Apologies for the service interruption. Jordan From owner-freebsd-current Wed Jun 4 15:00:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA15648 for current-outgoing; Wed, 4 Jun 1997 15:00:34 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA15273; Wed, 4 Jun 1997 14:55:57 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id HAA18548; Thu, 5 Jun 1997 07:52:34 +1000 Date: Thu, 5 Jun 1997 07:52:34 +1000 From: Bruce Evans Message-Id: <199706042152.HAA18548@godzilla.zeta.org.au> To: gurney_j@resnet.uoregon.edu, se@FreeBSD.ORG Subject: Re: sio driver performance Cc: current@FreeBSD.ORG, straka@inficad.com Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> also, it's a know fact that the 16550's are kinda heavy on overhead >> (not as bad as a parallel port though)... if you want to do many >> ports at full speed you really should invest in a smarter card, >> like a Digiboard/Cyclom/Riscom/Stallion smart board that has larger >> buffers and usually supports mapped memory access... > >Well, the 16550's FIFO will be read a byte a time, and >that means you will be limited to a few MB/s (Bruce Evans >did some testing of ISA port latencies, recently, and >posted his results). This makes some 10 microseconds per >14 bytes (if the receive FIFO was set to 14 bytes, that is). My old ISA/VLB system is significantly faster than my PCI/ISA system for ISA i/o. Not too surprisingly, the BIOS has more ISA knobs to twiddle. I think I have both systems set to 8MHz 1 wait state, but I get access times of 1179 nsec (9+ clocks) for port 0x3F8 on the PCI/ISA system and 978 nsec (7+ clocks) on the ISA/VLB system. For address 0xd4000 on a Cyclades 8Yo board, the access time is 798 nsec (6+ clocks). >A FIFO depth of 8 will reduce the time to read out those >8 bytes to some 5 microseconds. This amounts to 7 milli- >seconds per second (or just below 1%) per port, not taking >the interrupt handler overhead into account ... No, 8 bytes always take at least 8 i/o's to read, and in the current version of the driver they actually take 16+ i/o's to read, because each byte is accompanied by a status byte that has to be read and there are a couple of other status bytes to read. At 1 usec per byte it takes about 20 usec to do the i/o. General (fast)interrupt overhead is approx. 10 usec on a 486/33. The FIFO depth must be at least 4 for the overhead to be no larger than the i/o time. When it is 1 (no FIFO), efficiency suffers by a factor of 4. Increasing the depth above 14 doesn't have much effect on overheads. Bruce From owner-freebsd-current Wed Jun 4 18:32:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA25646 for current-outgoing; Wed, 4 Jun 1997 18:32:42 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA25641 for ; Wed, 4 Jun 1997 18:32:40 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id SAA14576 for ; Wed, 4 Jun 1997 18:32:35 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id TAA24836; Wed, 4 Jun 1997 19:31:08 -0600 (MDT) Message-Id: <199706050131.TAA24836@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Glenn Johnson cc: freebsd-current@FreeBSD.ORG Subject: Re: Second processor not being used? In-reply-to: Your message of "Tue, 03 Jun 1997 14:10:55 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 04 Jun 1997 19:31:08 -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > I just install a second Pentium Pro processor in my system. I built an SMP > kernel, rebooted, and the second processor is found and brought online. Are you setting SMP_AUTOSTART in the config file? there are several places in the boot where references are made to the 2nd CPU, but that doesn't mean that its running processes. > However, it does not appear to do anything. I submitted two jobs that each > require about 3 hours of computation time (very little disk I/O). Both jobs > were being run from the primary processor however. Is there something I need to > do to tell a job to go to a certain processor? Please help. this doesn't make alot of sense, but then you knew that! try making a kernel with 1 cpu running: sysctl -w kern.smp_active=1 cd /usr/src/sys/compile/SMP make clean && make depend && time make -j4 then with 2 CPUs running: sysctl -w kern.smp_active=2 cd /usr/src/sys/compile/SMP make clean && make depend && time make -j8 let us know the times for each. and give us an mptable: mptable -dmesg > outfile -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Wed Jun 4 22:46:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA26642 for current-outgoing; Wed, 4 Jun 1997 22:46:13 -0700 (PDT) Received: from tweetie-bird.cs.washington.edu (tweetie-bird.cs.washington.edu [128.95.2.46]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA26622; Wed, 4 Jun 1997 22:46:07 -0700 (PDT) From: mef@cs.washington.edu Received: (mef@localhost) by tweetie-bird.cs.washington.edu (8.7.2/7.2ws+) id WAA09090; Wed, 4 Jun 1997 22:46:07 -0700 (PDT) Date: Wed, 4 Jun 1997 22:46:07 -0700 (PDT) Message-Id: <199706050546.WAA09090@tweetie-bird.cs.washington.edu> To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: pci_map_mem failed: Intel EtherExpress Pro 10/100B Ethernet Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I get the following message when I boot on a PR440 Intel SMP motherboard using a May snapshot of the FreeBSD 3.0 code: fxp0 rev 1 int a irq 10 on pci1:10:0 pci_map_mem failed: device's memrange 0xF98FF000-0xF98FFFFF is incompatible with its bridge's memrange 0xF9A00000-0xFBEFFFFF The device seems to work just fine, but I have not pushed it hard at all. Just curious whether there is something that I need to do or look into. Thanks, Marc From owner-freebsd-current Wed Jun 4 23:15:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA27696 for current-outgoing; Wed, 4 Jun 1997 23:15:47 -0700 (PDT) Received: from shell.uniserve.com (tom@shell.uniserve.com [204.244.210.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA27691 for ; Wed, 4 Jun 1997 23:15:45 -0700 (PDT) Received: from localhost (tom@localhost) by shell.uniserve.com (8.8.5/8.8.5) with SMTP id XAA26206; Wed, 4 Jun 1997 23:14:56 -0700 (PDT) X-Authentication-Warning: shell.uniserve.com: tom owned process doing -bs Date: Wed, 4 Jun 1997 23:14:56 -0700 (PDT) From: Tom To: James FitzGibbon cc: current@FreeBSD.ORG Subject: Re: Use of your strptime(3) code (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 4 Jun 1997, James FitzGibbon wrote: > When I was trying to port mSQL-2.0b5, I needed a strptime(3) call, which > we don't have. Although the need for it in mSQL-2 is no longer > required, it might be a valuable addition to libcompat, since most > SVR4 systems have it. I was a bit confused when I read this. I built msql-2.0b6 some time ago, and it built without any problems. Tom From owner-freebsd-current Thu Jun 5 00:40:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA01132 for current-outgoing; Thu, 5 Jun 1997 00:40:50 -0700 (PDT) Received: from bsd3.nyct.net (myj@bsd3.nyct.net [204.141.86.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA01125 for ; Thu, 5 Jun 1997 00:40:48 -0700 (PDT) Received: from localhost (myj@localhost) by bsd3.nyct.net (8.8.5/8.8.5) with SMTP id DAA18911; Thu, 5 Jun 1997 03:40:45 -0400 (EDT) Date: Thu, 5 Jun 1997 03:40:45 -0400 (EDT) From: Paul Sandys To: mef@cs.washington.edu cc: freebsd-current@FreeBSD.ORG Subject: Re: pci_map_mem failed: Intel EtherExpress Pro 10/100B Ethernet In-Reply-To: <199706050546.WAA09090@tweetie-bird.cs.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 4 Jun 1997 mef@cs.washington.edu wrote: > Date: Wed, 4 Jun 1997 22:46:07 -0700 (PDT) > From: mef@cs.washington.edu > To: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG > Subject: pci_map_mem failed: Intel EtherExpress Pro 10/100B Ethernet > > Hi, > > I get the following message when I boot on a PR440 Intel SMP > motherboard using a May snapshot of the FreeBSD 3.0 code: > > fxp0 rev 1 int a irq 10 on pci1:10:0 > pci_map_mem failed: device's memrange 0xF98FF000-0xF98FFFFF is incompatible with its bridge's memrange 0xF9A00000-0xFBEFFFFF > > The device seems to work just fine, but I have not pushed it hard at > all. Just curious whether there is something that I need to do or > look into. I've got exactly same motherboard (one CPU), but fxp0 maps as follows: fxp0 rev 1 int a irq 11 on pci0:6 mapreg[10] type=0 addr=ffbea000 size=1000. mapreg[14] type=1 addr=0000ff40 size=0020. mapreg[18] type=0 addr=ff800000 size=100000. > > Thanks, > > Marc > BTW did you get the Crystal audio chip going ? From owner-freebsd-current Thu Jun 5 02:41:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA05464 for current-outgoing; Thu, 5 Jun 1997 02:41:03 -0700 (PDT) Received: from shadows.aeon.net (bsdcur@[194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA05458 for ; Thu, 5 Jun 1997 02:41:00 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id MAA27014 for current@freebsd.org; Thu, 5 Jun 1997 12:40:14 +0300 (EET DST) From: mika ruohotie Message-Id: <199706050940.MAA27014@shadows.aeon.net> Subject: Re: page fault In-Reply-To: <19970604174918.CS56609@uriah.heep.sax.de> from J Wunsch at "Jun 4, 97 05:49:18 pm" To: current@freebsd.org Date: Thu, 5 Jun 1997 12:40:12 +0300 (EET DST) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > yes, but i failed to get kernel -g:ed. i guess after this i'll use > > the 'config -g' as default. > Be careful to not accidentally load this bloated kernel into > memory. :) Also, i found the time ld(1) requires to link a full -g it's only about 9 mgs. why not? it's still less than what win95/nt4.0 eats when started... besides, i didnt notice slowing (which it probably causes). memory is cheap. > the same optimization level), but add -g. NB: you gotta replace the > COPTS ?= line by an absolute one. Then, i remove the .o files i wanna > force to rebuild, and just rebuild this part of the kernel. After > this, you can usually analyze the stacktrace. hmm, but you still need to know which .o's you need to nuke, and for a person without the internal knowledge it's hard to decide... so i think i can afford running 9 meg kernels if it helps me to track down what crashed. and wouldnt i fuck up the recompiling anyway if i've cvsup:ed after i did the kernel? (i cvsup far more often than i make worlds/kernels) btw, last time my machine crashed on this: #0 boot (howto=256) at ../../kern/kern_shutdown.c:265 #1 0xf011521a in panic (fmt=0xf01c712f "page fault") at ../../kern/kern_shutdown.c:392 #2 0xf01c7d8a in trap_fatal (frame=0xf503abe0) at ../../i386/i386/trap.c:754 #3 0xf01c7839 in trap_pfault (frame=0xf503abe0, usermode=0) at ../../i386/i386/trap.c:661 #4 0xf01c74bb in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 790, tf_esi = -266200876, tf_ebp = -184352768, tf_isp = -184308728, tf_ebx = 784, tf_edx = 0, tf_ecx = 513, tf_eax = -266200865, tf_trapno = 12, tf_err = 2, tf_eip = -267370964, tf_cs = 8, tf_eflags = 66178, tf_esp = 790, tf_ss = -266200876}) at ../../i386/i386/trap.c:319 #5 0xf0103e2c in cd9660_getattr (ap=0x0) at ../../isofs/cd9660/cd9660_vnops.c:253 it doesnt list more. but, the thing got my eye is the fact i do _not_ have cdrom attached, it's few miles from the machine currently. sure, the kernel has support, but... is that suspicious? it was crashed by httpd-requests from the win95 machine (it works about every time too) since connection attempts from local ether win95 seem to crash my machine repeatedly, should i assume it's _hardware_-related? > cheers, J"org mickey From owner-freebsd-current Thu Jun 5 06:25:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA13000 for current-outgoing; Thu, 5 Jun 1997 06:25:10 -0700 (PDT) Received: from nexis.net (customer-1.ican.net [198.133.36.101]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA12992 for ; Thu, 5 Jun 1997 06:25:04 -0700 (PDT) Received: from localhost (james@localhost) by nexis.net (8.8.5/8.8.5) with SMTP id JAA14831; Thu, 5 Jun 1997 09:23:12 -0400 (EDT) Date: Thu, 5 Jun 1997 09:23:11 -0400 (EDT) From: James FitzGibbon To: Tom cc: current@FreeBSD.ORG Subject: Re: Use of your strptime(3) code (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 4 Jun 1997, Tom wrote: > I was a bit confused when I read this. I built msql-2.0b6 some time > ago, and it built without any problems. Because in 2.0b6, the author removed the requirement for a system strptime(3) call. Still, this situtation may come up again, so I offered it as something to add to libc/libcompat. -- j. From owner-freebsd-current Thu Jun 5 07:12:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA15258 for current-outgoing; Thu, 5 Jun 1997 07:12:36 -0700 (PDT) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA15249 for ; Thu, 5 Jun 1997 07:12:32 -0700 (PDT) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id JAA06055; Thu, 5 Jun 1997 09:46:55 -0500 (CDT) Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id JAA28320; Thu, 5 Jun 1997 09:14:11 -0500 Message-ID: <19970605091410.05359@right.PCS> Date: Thu, 5 Jun 1997 09:14:10 -0500 From: Jonathan Lemon To: mika ruohotie Cc: current@FreeBSD.ORG Subject: Re: page fault References: <19970604174918.CS56609@uriah.heep.sax.de> <199706050940.MAA27014@shadows.aeon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199706050940.MAA27014@shadows.aeon.net>; from mika ruohotie on Jun 06, 1997 at 12:40:12PM +0300 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 06, 1997 at 12:40:12PM +0300, mika ruohotie wrote: > > > yes, but i failed to get kernel -g:ed. i guess after this i'll use > > > the 'config -g' as default. > > Be careful to not accidentally load this bloated kernel into > > memory. :) Also, i found the time ld(1) requires to link a full -g > > it's only about 9 mgs. why not? it's still less than what win95/nt4.0 > eats when started... besides, i didnt notice slowing (which it probably > causes). memory is cheap. Because it takes an unholy amount of time to load any LKM's into such a gigantic kernel. I don't think I had the patience to wait enough for the mod_load to complete. -- Jonathan From owner-freebsd-current Thu Jun 5 08:22:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA19092 for current-outgoing; Thu, 5 Jun 1997 08:22:25 -0700 (PDT) Received: from iguana.reptiles.org (mail2.reptiles.org [198.96.117.130]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA19044; Thu, 5 Jun 1997 08:21:46 -0700 (PDT) Received: by iguana.reptiles.org via sendmail with stdio id for freebsd-hackers@freebsd.org; Thu, 5 Jun 97 11:21:31 -0400 (EDT) (Smail-3.1.93 1996-May-30 #2 built 1996-Jun-15) Message-Id: From: jim@reptiles.org (Jim Mercer) Subject: ftp://ftp.reptiles.org/pub/FreeBSD/local.patches/pppd-2.3.0.tar.gz To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Date: Thu, 5 Jun 1997 11:21:31 -0400 (EDT) X-Mailer: ELM [version 2.4 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk in the above URL you will find my hacks to make pppd-2.3.0 work with 2.2.1-RELEASE. the port is not complete, as i only required IP, and thus skipped the relevant IPX and ATALK(?) stuff. i also didn't port the MSCHAP stuff. my experience with the code is that it shouldn't be hard for someone to finish it off, assuming they have a local testbed. (i don't run apple or novell). i was pushed into doing this because i found that i couldn't get Win95 dialup networking to connect to my FreeBSD based terminal server. oddly enough, using Trumpet Winsock95 worked flawlessly. this port is based on the ppp-2.3.0 code i piked up from: ftp://cs.anu.edu.au/pub/software/ppp/ppp-2.3.0.tar.gz i had to modify a number of files, including renaming some from the ANU distribution to be consistent with the current FreeBSD file names. i provide the port with no warranties or guarantees. i have it working on 2.2.1-RELEASE on a machine with 4 Moxa C168 8 port boards. my testing thus far is that it works. i will see better when the system goes into production with 32 33.6 modems in a month or so. -- Jim Mercer Reptilian Research merce@iguana.reptiles.org +1 416 410-5633 Most people believe that if it ain't broke, don't fix it. Engineers believe that if it ain't broke, it don't have enough features yet. From owner-freebsd-current Thu Jun 5 09:16:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA22155 for current-outgoing; Thu, 5 Jun 1997 09:16:55 -0700 (PDT) Received: from bagpuss.visint.co.uk (bagpuss.vis.net.uk [194.207.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA22150 for ; Thu, 5 Jun 1997 09:16:51 -0700 (PDT) Received: from dylan.visint.co.uk (dylan.visint.co.uk [194.207.134.180]) by bagpuss.visint.co.uk (8.7.5/8.7.3) with SMTP id RAA18994 for ; Thu, 5 Jun 1997 17:16:40 +0100 (BST) Date: Thu, 5 Jun 1997 17:16:39 +0100 (BST) From: Stephen Roome To: freebsd-current@freebsd.org Subject: cc1 got fatal signal 10 in make kernel for bisdn Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk root@one# pwd /bisdn/compile/BRIAN root@one# make cc -c -x assembler-with-cpp -DLOCORE -nostdinc -I- -I. -I../.. -I../../../include -DTELES_HAS_MEMCPYB -DCOMPAT_43 -DFFS -DINET -DKERNEL ../../i386/i386/locore.s cc -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. -I../.. -I../../../include -DTELES_HAS_MEMCPYB -DCOMPAT_43 -DFFS -DINET -DKERNEL -c vnode_if.c cc: Internal compiler error: program cc1 got fatal signal 10 *** Error code 1 Stop. Well, I'm not sure what's going on here, is this a known problem, is it a bug or have I not set up bisdn properly. Even then should gcc die like this.. (nope).. Clues/Pointers/Axes welcome. Thanks. Steve. From owner-freebsd-current Thu Jun 5 09:43:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA23373 for current-outgoing; Thu, 5 Jun 1997 09:43:24 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA23363; Thu, 5 Jun 1997 09:43:20 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id KAA27170; Thu, 5 Jun 1997 10:43:11 -0600 (MDT) Message-Id: <199706051643.KAA27170@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: mef@cs.washington.edu cc: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: pci_map_mem failed: Intel EtherExpress Pro 10/100B Ethernet In-reply-to: Your message of "Wed, 04 Jun 1997 22:46:07 PDT." <199706050546.WAA09090@tweetie-bird.cs.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Jun 1997 10:43:11 -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > I get the following message when I boot on a PR440 Intel SMP > motherboard using a May snapshot of the FreeBSD 3.0 code: > > fxp0 rev 1 int a irq 10 on pci1:10:0 > pci_map_mem failed: device's memrange 0xF98FF000-0xF98FFFFF is incompatible with its bridge's memrange 0xF9A00000-0xFBEFFFFF > > The device seems to work just fine, but I have not pushed it hard at > all. Just curious whether there is something that I need to do or > look into. I'm guessing that this is a UP (ie NOT SMP) kernel? -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-current Thu Jun 5 13:53:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06529 for current-outgoing; Thu, 5 Jun 1997 13:53:50 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA06524 for ; Thu, 5 Jun 1997 13:53:46 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by agora.rdrop.com (8.8.5/8.8.5) with SMTP id NAA25209 for ; Thu, 5 Jun 1997 13:53:40 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA26317 for current@FreeBSD.ORG; Thu, 5 Jun 1997 22:51:51 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA25381; Thu, 5 Jun 1997 22:34:27 +0200 (MET DST) Message-ID: <19970605223427.LN28350@uriah.heep.sax.de> Date: Thu, 5 Jun 1997 22:34:27 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Subject: Re: page fault References: <19970604174918.CS56609@uriah.heep.sax.de> <199706050940.MAA27014@shadows.aeon.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706050940.MAA27014@shadows.aeon.net>; from mika ruohotie on Jun 5, 1997 12:40:12 +0300 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As mika ruohotie wrote: > > Be careful to not accidentally load this bloated kernel into > > memory. :) > > it's only about 9 mgs. why not? Because you're bloating physical memory with a symbol table you're never going to make _any_ use of. (DDB can't use the local symbols and various strings anyway.) It's not too hard to say ``strip -d /kernel'' before rebooting, is it? :) > > the same optimization level), but add -g. NB: you gotta replace the > > COPTS ?= line by an absolute one. Then, i remove the .o files i wanna > > force to rebuild, and just rebuild this part of the kernel. After > > this, you can usually analyze the stacktrace. > > hmm, but you still need to know which .o's you need to nuke, and for > a person without the internal knowledge it's hard to decide... It's not too hard. As long as you've got a basic clue to which subsystem (net, netinet, cd9660 etc.) the functions belong, you can just use grep. For all files which at least basically conform to style(9), the function names always start in column 1 (and now you know one reason why :), so if you look for functions foobar() and mumble(), in the netinet subsystem, say: grep -E '^(foobar|mumble)' /sys/netinet/*.c Also, now that we've got global(1) support in the tree, you should be able to use tags. > and wouldnt i fuck up the recompiling anyway if i've > cvsup:ed after i did the kernel? (i cvsup far more often than i > make worlds/kernels) Well, if you cvsup the source tree, yes. (I mirror the CVS tree, so i will only foobar the tree if i cvs update it.) > btw, last time my machine crashed on this: > #5 0xf0103e2c in cd9660_getattr (ap=0x0) > at ../../isofs/cd9660/cd9660_vnops.c:253 > > it doesnt list more. but, the thing got my eye is the fact i do _not_ > have cdrom attached, it's few miles from the machine currently. sure, > the kernel has support, but... is that suspicious? It looks suspicious regarding your hardware. If you never touched the cd9660 filesystem code (which would at least require a previous mount -t cd9660), this function should never be called. It's called in some VOP_GETATTR() macro, but of course, its argument pointer should never be zero. Also, the missing stack frame beyond this call might be an indication that something really stinks in your system. It's normal for the inlined vnode operations that they stomp a little on the stack backtrace, so you're often missing one function call when looking at it in the debugger, but it's not normal that you don't see anything in the upper layers. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Jun 5 14:23:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA07827 for current-outgoing; Thu, 5 Jun 1997 14:23:35 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA07803 for ; Thu, 5 Jun 1997 14:23:01 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA26820; Thu, 5 Jun 1997 23:22:50 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA25454; Thu, 5 Jun 1997 22:55:20 +0200 (MET DST) Message-ID: <19970605225520.HQ28541@uriah.heep.sax.de> Date: Thu, 5 Jun 1997 22:55:20 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Cc: james@nexis.net (James FitzGibbon) Subject: Re: Use of your strptime(3) code (fwd) References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from James FitzGibbon on Jun 5, 1997 09:23:11 -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As James FitzGibbon wrote: > Because in 2.0b6, the author removed the requirement for a system > strptime(3) call. Still, this situtation may come up again, so I offered > it as something to add to libc/libcompat. Again, with the existing copyright, it's simply unacceptable. I'm saying this for at least the third time now, but didn't get any response so far. /* * Copyright (c) 1994 Powerdog Industries. All rights reserved. * * Redistribution and use in source and binary forms, without ^^^^^^^ * modification, are permitted provided that the following conditions ^^^^^^^^^^^^ * are met: [... looks like a BSD copyright otherwise] I even wrote a manpage already. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Jun 5 14:50:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA09169 for current-outgoing; Thu, 5 Jun 1997 14:50:10 -0700 (PDT) Received: from shell.uniserve.com (tom@shell.uniserve.com [204.244.210.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA09161 for ; Thu, 5 Jun 1997 14:50:07 -0700 (PDT) Received: from localhost (tom@localhost) by shell.uniserve.com (8.8.5/8.8.5) with SMTP id OAA12940; Thu, 5 Jun 1997 14:49:03 -0700 (PDT) X-Authentication-Warning: shell.uniserve.com: tom owned process doing -bs Date: Thu, 5 Jun 1997 14:49:01 -0700 (PDT) From: Tom To: Joerg Wunsch cc: current@FreeBSD.ORG, James FitzGibbon Subject: Re: Use of your strptime(3) code (fwd) In-Reply-To: <19970605225520.HQ28541@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 5 Jun 1997, J Wunsch wrote: > As James FitzGibbon wrote: > > > Because in 2.0b6, the author removed the requirement for a system > > strptime(3) call. Still, this situtation may come up again, so I offered > > it as something to add to libc/libcompat. > > Again, with the existing copyright, it's simply unacceptable. I'm > saying this for at least the third time now, but didn't get any > response so far. Also, I don't think we need it. None of the hundreds of other ports need it, and as it seems neither does msql. Tom From owner-freebsd-current Thu Jun 5 18:05:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA17650 for current-outgoing; Thu, 5 Jun 1997 18:05:56 -0700 (PDT) Received: from nexis.net (customer-1.ican.net [198.133.36.101]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA17645 for ; Thu, 5 Jun 1997 18:05:51 -0700 (PDT) Received: from localhost (james@localhost) by nexis.net (8.8.5/8.8.5) with SMTP id VAA16894; Thu, 5 Jun 1997 21:03:27 -0400 (EDT) Date: Thu, 5 Jun 1997 21:03:26 -0400 (EDT) From: James FitzGibbon To: Joerg Wunsch cc: current@FreeBSD.ORG Subject: Re: Use of your strptime(3) code (fwd) In-Reply-To: <19970605225520.HQ28541@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 5 Jun 1997, J Wunsch wrote: > Again, with the existing copyright, it's simply unacceptable. I'm > saying this for at least the third time now, but didn't get any > response so far. I forwarded your last message to me to the author, but the last message I sent him took 6 weeks to get a response. Not sure if that's average turnaround or if he was away from his email for that period, but as soon as I know something I'll let you know. -- j. From owner-freebsd-current Thu Jun 5 18:12:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA17923 for current-outgoing; Thu, 5 Jun 1997 18:12:07 -0700 (PDT) Received: from nexis.net (customer-1.ican.net [198.133.36.101]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA17910 for ; Thu, 5 Jun 1997 18:12:05 -0700 (PDT) Received: from localhost (james@localhost) by nexis.net (8.8.5/8.8.5) with SMTP id VAA16925; Thu, 5 Jun 1997 21:11:22 -0400 (EDT) Date: Thu, 5 Jun 1997 21:11:22 -0400 (EDT) From: James FitzGibbon To: Tom cc: current@FreeBSD.ORG Subject: Re: Use of your strptime(3) code (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 5 Jun 1997, Tom wrote: > Also, I don't think we need it. None of the hundreds of other ports > need it, and as it seems neither does msql. True, mSQL 2.0b5 was the first one that I saw that broke without a working strptime(3). Still, just because there isn't an immediate need for something doesn't mean we shouldn't consider it for inclusion. strptime is the natural partner to strftime, which is in libc. strptime also is in Solaris. If this import makes it possible to port one program that someone wrote with only Solaris in mind, then it's in my mind worth it. Joerg had already done work on this long before I suggested it. He, being much more involved in the source tree that myself, saw a need, and I respect and agree with that opinion. Besides, I'm just running interference between the author and the developers... 8-) -- j. From owner-freebsd-current Thu Jun 5 19:45:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA22218 for current-outgoing; Thu, 5 Jun 1997 19:45:01 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA22206 for ; Thu, 5 Jun 1997 19:44:58 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id TAA22998 for ; Thu, 5 Jun 1997 19:44:37 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA29508; Fri, 6 Jun 1997 12:11:53 +0930 (CST) From: Michael Smith Message-Id: <199706060241.MAA29508@genesis.atrad.adelaide.edu.au> Subject: Re: page fault In-Reply-To: <19970605223427.LN28350@uriah.heep.sax.de> from J Wunsch at "Jun 5, 97 10:34:27 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 6 Jun 1997 12:11:51 +0930 (CST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch stands accused of saying: > As mika ruohotie wrote: > > > > Be careful to not accidentally load this bloated kernel into > > > memory. :) > > > > it's only about 9 mgs. why not? > > Because you're bloating physical memory with a symbol table you're > never going to make _any_ use of. (DDB can't use the local symbols > and various strings anyway.) It's not too hard to say ``strip -d > /kernel'' before rebooting, is it? :) ... but if you leave them in, you get filenames and line numbers with your traps. I happen to like that sometimes 8) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Thu Jun 5 21:43:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26527 for current-outgoing; Thu, 5 Jun 1997 21:43:39 -0700 (PDT) Received: from user1.inficad.com (straka@user1.inficad.com [207.19.74.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA26521 for ; Thu, 5 Jun 1997 21:43:36 -0700 (PDT) Received: from localhost (straka@localhost) by user1.inficad.com (8.8.5/8.8.5) with SMTP id VAA29253; Thu, 5 Jun 1997 21:49:52 -0700 (MST) Date: Thu, 5 Jun 1997 21:49:52 -0700 (MST) From: Richard Straka To: Bruce Evans cc: current@FreeBSD.ORG Subject: Re: sio driver performance In-Reply-To: <199706042043.GAA16361@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> When receiving sustained 115200 baud data, an interrupt rate of > >> over 26,000/sec is indicated with about 15% of the processor going > >> to service interrupts. > >> > >> It appears as though the fifo is not working for the receive. In an > >> attempt to exhonerate the hardware, I swapped in another 16550 card > >> I had laying around and got the similar results. > > It works for most users. Possible problems: > > - noisy cables may cause a modem status interrupt for every character > (or every changed bit?). > - a parity mismatch may cause a line status interrupt for every character. > This problem is easy to reproduce using `stty parenb ...' to change the > default of 8 bits-no parity to 9 bits-1 parity bit. > - a hardware bug on UMC8669F devices that prevents initialization of the > fifo trigger level while data is arriving. These devices also have a > h/w bug that prevents initialization of the speed while data is arriving. > Both bugs are more common in tests than in normal operation. I always > see the fifo bug here if I start the transmitter first. FreeBSD > transmitters do a perfect job of keeping the data flowing, so the > receiver never has a chance to recover :-). Bruce, Your suggestion of a noisy cable was right on. After swapping out a bad null modem adapter, the receive fifo seems to be working great (820 int/sec at 115200 baud). CPU utilization is also greatly reduced. Thank again for you help and thanks to everyone who responded to my problem. Richard Straka straka@inficad.com From owner-freebsd-current Thu Jun 5 23:31:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA01375 for current-outgoing; Thu, 5 Jun 1997 23:31:31 -0700 (PDT) Received: from user2.inficad.com (straka@user2.inficad.com [207.19.74.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA01370 for ; Thu, 5 Jun 1997 23:31:29 -0700 (PDT) Received: from localhost (straka@localhost) by user2.inficad.com (8.8.5/8.7.3) with SMTP id XAA11299; Thu, 5 Jun 1997 23:31:26 -0700 (MST) Date: Thu, 5 Jun 1997 23:31:25 -0700 (MST) From: Richard Straka To: Bruce Evans cc: current@freebsd.org Subject: Re: sio driver performance In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I want to use FreeBSD (2.2.1-RELEASE) on a 486DX-33 to collect some serial data from some remote test equipment. As a precursor test, I have connected this box to another FreeBSD box and have been sending serial data back and forth. I have set both boxes serial ports as follows temp.c_lflag &= ~(ECHO | ICANON | IEXTEN | ISIG); temp.c_iflag &= ~(BRKINT | ICRNL | INPCK | ISTRIP | IXON); temp.c_cflag &= ~(CRTSCTS | CSIZE | PARENB); temp.c_cflag |= CS8; temp.c_oflag &= ~(OPOST); temp.c_cc[VMIN] = 1; temp.c_cc[VTIME] = 0; cfsetispeed(&temp,(speed_t)115200); cfsetospeed(&temp,(speed_t)115200); I have a small loop on one of the boxes which wakes up on a 100Hz alarm and send 16 bytes out the serial port. On the other box, I have a loop which continuously tries to read 16 bytes from the serial port. I have noticed that the communications work great until I interrupt the process on the box which is tranmitting the data. At that point, the box which was receiving suddenly elevates to 100% CPU usage (mostly system) as if in a polling loop. When I attempt to reestablish the process which is sending the data, I get "tty-level buffer overflows" on the receiving box, the read never unblocks and the CPU utilization stays at 100%. I have to kill the receiving process and restart it to reestablish communication. Also when the receive process is started, before the transmit process is started on the other box, the read seems to periodically return -1. Shouldn't the read indefinitely block if c_cc[VMIN]=1 and c_cc[VTIME]=0? The "tty-level buffer overflows" only occurs after the transmit process is started, then halted, then restarted. This could be a real problem for my remote test equipment as the serial lines may be inadvertently disconnected and reconnected from time to time. Any help with this would be greatly appreciated. Richard Straka straka@inficad.com From owner-freebsd-current Thu Jun 5 23:51:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02624 for current-outgoing; Thu, 5 Jun 1997 23:51:33 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA02612 for ; Thu, 5 Jun 1997 23:51:30 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA02792 for current@FreeBSD.ORG; Fri, 6 Jun 1997 08:51:28 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA27535; Fri, 6 Jun 1997 08:24:19 +0200 (MET DST) Message-ID: <19970606082419.QR56672@uriah.heep.sax.de> Date: Fri, 6 Jun 1997 08:24:19 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Subject: Re: Use of your strptime(3) code (fwd) References: <19970605225520.HQ28541@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from James FitzGibbon on Jun 5, 1997 21:03:26 -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As James FitzGibbon wrote: > I forwarded your last message to me to the author, but the last message I > sent him took 6 weeks to get a response. :-) Ok, this one seems to have made it quicker. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Jun 5 23:51:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02646 for current-outgoing; Thu, 5 Jun 1997 23:51:38 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA02626 for ; Thu, 5 Jun 1997 23:51:34 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA02795 for current@FreeBSD.ORG; Fri, 6 Jun 1997 08:51:32 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA27526; Fri, 6 Jun 1997 08:23:46 +0200 (MET DST) Message-ID: <19970606082346.EJ07978@uriah.heep.sax.de> Date: Fri, 6 Jun 1997 08:23:46 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Subject: Re: Use of your strptime(3) code (fwd) References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from James FitzGibbon on Jun 5, 1997 21:11:22 -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As James FitzGibbon wrote: > Joerg had already done work on this long before I suggested it. He, being > much more involved in the source tree that myself, saw a need, and I > respect and agree with that opinion. I did it for the same reasons you mentioned. It looks like a logical counterpart to strftime(3). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Jun 5 23:57:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02951 for current-outgoing; Thu, 5 Jun 1997 23:57:06 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA02945 for ; Thu, 5 Jun 1997 23:57:02 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA02486; Fri, 6 Jun 1997 16:26:30 +0930 (CST) From: Michael Smith Message-Id: <199706060656.QAA02486@genesis.atrad.adelaide.edu.au> Subject: Re: sio driver performance In-Reply-To: from Richard Straka at "Jun 5, 97 11:31:25 pm" To: straka@inficad.com (Richard Straka) Date: Fri, 6 Jun 1997 16:26:30 +0930 (CST) Cc: bde@zeta.org.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Richard Straka stands accused of saying: > > I have noticed that the communications work great until I interrupt the > process on the box which is tranmitting the data. At that point, the box > which was receiving suddenly elevates to 100% CPU usage (mostly system) as > if in a polling loop. Read the manpage for the read() system call, and pay particular attention to the return value for EOF. I suspect that when the sender is killed it is lowering whatever control signal is driving DCD at the receiving end. Without seeing the rest of your code, it's hard to be sure if this is the case. > Also when the receive process is started, before the transmit process is > started on the other box, the read seems to periodically return -1. > Shouldn't the read indefinitely block if c_cc[VMIN]=1 and c_cc[VTIME]=0? Check errno on these occasions; I would guess that you are probably seeing EINTR. > The "tty-level buffer overflows" only occurs after the transmit process is > started, then halted, then restarted. This could be a real problem for my > remote test equipment as the serial lines may be inadvertently > disconnected and reconnected from time to time. I suspect that this is an artifact of the receiver having lost its brain. > Richard Straka -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Fri Jun 6 06:24:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA19527 for current-outgoing; Fri, 6 Jun 1997 06:24:08 -0700 (PDT) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA19479 for ; Fri, 6 Jun 1997 06:23:56 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id QAA10167 for current@freebsd.org; Fri, 6 Jun 1997 16:23:23 +0300 (EET DST) From: mika ruohotie Message-Id: <199706061323.QAA10167@shadows.aeon.net> Subject: Re: page fault In-Reply-To: <19970605223427.LN28350@uriah.heep.sax.de> from J Wunsch at "Jun 5, 97 10:34:27 pm" To: current@freebsd.org Date: Fri, 6 Jun 1997 16:23:23 +0300 (EET DST) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > it's only about 9 mgs. why not? > Because you're bloating physical memory with a symbol table you're i know... > and various strings anyway.) It's not too hard to say ``strip -d > /kernel'' before rebooting, is it? :) nope, it's not. didnt think about that first... though i strip:ed it in /sys/compile/, after i copied the kernel to kernel.debug, _then_ i installed the kernel... but now that i'm expecting a crash, i'm not getting one. :\ (sure, i could generate one with the win95) > > a person without the internal knowledge it's hard to decide... > It's not too hard. As long as you've got a basic clue to which hmm? the clue is not always "available". > style(9), the function names always start in column 1 (and now you > know one reason why :), so if you look for functions foobar() and i guess... always nice to learn new things. > Also, now that we've got global(1) support in the tree, you should be > able to use tags. uh oh, sounds like lots of rtfm:ing tonight... > Well, if you cvsup the source tree, yes. (I mirror the CVS tree, so i > will only foobar the tree if i cvs update it.) i dont yet have the space for that. soon i will... > > the kernel has support, but... is that suspicious? > It looks suspicious regarding your hardware. If you never touched the it's bad ram, right? i'm not really truting my ram, even though it never die on cc... it's still weird. another piece of my hardware i dont trust is the ethernet adapter, i bought it used, it's smc isa combo card. > cd9660 filesystem code (which would at least require a previous mount > -t cd9660), this function should never be called. It's called in some yeah. but, nada cdrom in the machine. > backtrace, so you're often missing one function call when looking at > it in the debugger, but it's not normal that you don't see anything in > the upper layers. i'll crash my machine few times tonight and see what i get, and i'll do that with bloated kernel, i like the extra info it tells me. and i have new memory on my shopping list, as well as new motherboard, and several other parts... basicly what i'll keep is the installed os, which i also feel tempted to reinstall to clean it from old files... > cheers, J"org mickey From owner-freebsd-current Fri Jun 6 06:58:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA20900 for current-outgoing; Fri, 6 Jun 1997 06:58:27 -0700 (PDT) Received: from hometeam.techpower.net (hometeam@techpower.net [206.244.73.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA20889 for ; Fri, 6 Jun 1997 06:58:22 -0700 (PDT) Received: from localhost (hometeam@localhost) by hometeam.techpower.net (8.8.5/8.8.5) with SMTP id JAA01586 for ; Fri, 6 Jun 1997 09:54:50 -0400 (EDT) Date: Fri, 6 Jun 1997 09:54:50 -0400 (EDT) From: Freebsd To: current@FreeBSD.ORG Subject: printer Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk if I were to setup a network printer on freebsd. basicly I would need what to enable it so my win95 system can print also on it ? printer is connected to bsd box. I am not sure if this is the correct mail list. From owner-freebsd-current Fri Jun 6 15:45:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA16813 for current-outgoing; Fri, 6 Jun 1997 15:45:30 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA16808 for ; Fri, 6 Jun 1997 15:45:28 -0700 (PDT) Received: from Jupiter.Mcs.Net (karl@Jupiter.mcs.net [192.160.127.88]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id RAA21170 for ; Fri, 6 Jun 1997 17:45:26 -0500 (CDT) Received: (from karl@localhost) by Jupiter.Mcs.Net (8.8.5/8.8.2) id RAA23526; Fri, 6 Jun 1997 17:45:20 -0500 (CDT) Message-ID: <19970606174520.25878@Jupiter.Mcs.Net> Date: Fri, 6 Jun 1997 17:45:20 -0500 From: Karl Denninger To: current@freebsd.org Subject: Make release failure Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Got this in the middle of the process... I noted the makefile had changed; what am I missing? ===> lkm/wcd install -c -o bin -g bin -m 555 wcd_mod.o /disk/release/lkm mkdir /disk/release//bootstrap for i in /sbin/mount /sbin/umount /usr/bin/cpio ; do cp -p /disk/release$i /disk/release//bootstrap ; done cd /disk/release/usr && rm -rf src && cvs -d co -P src cvs: invalid option -- P Usage: cvs [cvs-options] command [command-options] [files...] Where 'cvs-options' are: -H Displays Usage information for command -Q Cause CVS to be really quiet. -q Cause CVS to be somewhat quiet. .... -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | 99 Analog numbers, 77 ISDN, http://www.mcs.net/ Voice: [+1 312 803-MCS1 x219]| NOW Serving 56kbps DIGITAL on our analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal From owner-freebsd-current Fri Jun 6 17:48:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA21787 for current-outgoing; Fri, 6 Jun 1997 17:48:13 -0700 (PDT) Received: from nemesis.lonestar.org (gw8-ppp6.its.iadfw.net [207.136.11.90]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA21782 for ; Fri, 6 Jun 1997 17:48:10 -0700 (PDT) Received: by nemesis.lonestar.org (Smail3.1.27.1 #22) id m0wa9bT-000tx3C; Fri, 6 Jun 97 19:43 CDT Message-Id: Date: Fri, 6 Jun 97 19:43 CDT To: current@FreeBSD.ORG From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Fri Jun 6 1997, 19:43:35 CDT Subject: Re: cd9660 w/ Joliet extensions Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [1]This is probably a bit premature, but is anyone working on support for [1]Microsoft's Joliet cd9660 extensions? This might be moot soon since all of Microsoft new OS beta material is coming out in the "UDF - Universal Disk Format". When you stick one of these discs in an existing Windows '95, FreeBSD, or DOS system, you can only see one file that has a message saying you need to upgrade your operating system to see the full contents of the disk. [2]I would prefer mickeysoft using RR. :-] Sorry, that's a big NIH. Microsoft even avoided using CD9660 for years on their own products, shipping them out in High Sierra format. Only after they got publicly embarassed over the performance hit you have when you don't have the CD9660 Path table did they start migrating to CD9660. I think the second release of Encarta was the first MS CD9660 release. Besides, UDF was actually developed with people besides Microsoft, mainly to support the higher data capacities that exist in DVD-sized media and allow for the random read/write that rewritable media will deliver shortly. UDF is probably the format someone should spend the time on, not Ju/oliet, Romeo or any of the other short-lived Microsoft CD-ROM formats that appeared in the wake of Windows '95. Frank Durda IV - only these addresses work:|"Tandys THOR - Ten years too | early and they didn't have any or | of the patents licensed when These Anti-spam addresses expire in 25 days| they announced. Doh!" From owner-freebsd-current Fri Jun 6 21:03:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA27461 for current-outgoing; Fri, 6 Jun 1997 21:03:27 -0700 (PDT) Received: from bmccane.uit.net (bmccane.uit.net [208.129.189.48]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA27456 for ; Fri, 6 Jun 1997 21:03:13 -0700 (PDT) Received: from bmccane.uit.net (localhost.mccane.com [127.0.0.1]) by bmccane.uit.net (8.8.5/8.8.5) with ESMTP id XAA26092; Fri, 6 Jun 1997 23:02:11 -0500 (CDT) Message-Id: <199706070402.XAA26092@bmccane.uit.net> X-Mailer: exmh version 2.0gamma 1/27/96 To: Michael Smith cc: straka@inficad.com (Richard Straka), bde@zeta.org.au, current@FreeBSD.ORG Subject: Re: sio driver performance In-reply-to: Your message of "Fri, 06 Jun 1997 16:26:30 +0930." <199706060656.QAA02486@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Jun 1997 23:02:10 -0500 From: Wm Brian McCane Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Richard Straka stands accused of saying: > > > > I have noticed that the communications work great until I interrupt the > > process on the box which is tranmitting the data. At that point, the box > > which was receiving suddenly elevates to 100% CPU usage (mostly system) as > > if in a polling loop. > > Read the manpage for the read() system call, and pay particular > attention to the return value for EOF. I suspect that when the sender > is killed it is lowering whatever control signal is driving DCD at the > receiving end. Without seeing the rest of your code, it's hard to be > sure if this is the case. > > > Also when the receive process is started, before the transmit process is > > started on the other box, the read seems to periodically return -1. > > Shouldn't the read indefinitely block if c_cc[VMIN]=1 and c_cc[VTIME]=0? > > Check errno on these occasions; I would guess that you are probably > seeing EINTR. > > > The "tty-level buffer overflows" only occurs after the transmit process is > > started, then halted, then restarted. This could be a real problem for my > > remote test equipment as the serial lines may be inadvertently > > disconnected and reconnected from time to time. > > I suspect that this is an artifact of the receiver having lost its brain. > > > Richard Straka > I think Mike is right on this one. I would suggest adding a select call to your program with a read and exception fd_set. If the bit gets set in the exception fd_set, close the port and reopen it. This way you will wait until DCD is high before continuing your reads. It also makes a nice spring-board for when someone asks you to monitor more ports at once. brian From owner-freebsd-current Fri Jun 6 21:34:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA28686 for current-outgoing; Fri, 6 Jun 1997 21:34:47 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA28681 for ; Fri, 6 Jun 1997 21:34:44 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id OAA28487; Sat, 7 Jun 1997 14:31:47 +1000 Date: Sat, 7 Jun 1997 14:31:47 +1000 From: Bruce Evans Message-Id: <199706070431.OAA28487@godzilla.zeta.org.au> To: bde@zeta.org.au, straka@inficad.com Subject: Re: sio driver performance Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I have noticed that the communications work great until I interrupt the >process on the box which is tranmitting the data. At that point, the box >which was receiving suddenly elevates to 100% CPU usage (mostly system) as >if in a polling loop. When I attempt to reestablish the process which is Hangup on the tranmitter breaks the connection. There is no way (*) to get the same connection back - reads on the open fd will return -1/EIO forever. (Reads should return 0, but there is a minor bug that prevents this in some cases. POSIX allows either EOF (0) or -1/EIO.) You need to clear HUPCL on the transmitter or set CLOCAL on the receiver to avoid seeing the hangup. Using CLOCAL is often required to avoid unwanted POSIX connection semantics. Then you have to monitor the carrier status directly by polling it if you care about it. (*) actually there is a nonstandard way involving toggling CLOCAL. Don't use it. >sending the data, I get "tty-level buffer overflows" on the receiving box, >the read never unblocks and the CPU utilization stays at 100%. I have to >kill the receiving process and restart it to reestablish communication. This may be a driver bug. The new input apparently gets buffered but nothing reads it. It can't be read via the old connection, so perhaps it should be discarded. Well behaved receivers close the port when they see EOF or -1/EIO, and input to closed ports is ignored, so the problem is usually invisible. >Also when the receive process is started, before the transmit process is >started on the other box, the read seems to periodically return -1. >Shouldn't the read indefinitely block if c_cc[VMIN]=1 and c_cc[VTIME]=0? It should block before the first connection and return either EOF or -1/EIO when the connection is broken. Stale broken connections may interfere with new connections in some cases. Bruce From owner-freebsd-current Fri Jun 6 22:04:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA29961 for current-outgoing; Fri, 6 Jun 1997 22:04:04 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA29927 for ; Fri, 6 Jun 1997 22:04:01 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id PAA29223 for current@freebsd.org; Sat, 7 Jun 1997 15:01:46 +1000 Date: Sat, 7 Jun 1997 15:01:46 +1000 From: Bruce Evans Message-Id: <199706070501.PAA29223@godzilla.zeta.org.au> To: current@freebsd.org Subject: Re: cvs commit: src/gnu/usr.bin/gdb/gdb freebsd-nat.c kvm-fbsd.c tm.h Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Modified files: > gnu/usr.bin/gdb/gdb freebsd-nat.c kvm-fbsd.c tm.h > Log: > Support reading and writing of %fs and %gs (except from core files). > > Revision Changes Path > 1.15 +23 -3 src/gnu/usr.bin/gdb/gdb/freebsd-nat.c > 1.4 +3 -1 src/gnu/usr.bin/gdb/gdb/kvm-fbsd.c > 1.8 +1 -1 src/gnu/usr.bin/gdb/gdb/tm.h You probably need to recompile gdb even if you don't want this change. `struct reg' grew, and the braindamaged PT_{GET,SET}_REGS interface doesn't supply a size, so `struct reg' variables in old gdb's will be overrun. Bruce From owner-freebsd-current Fri Jun 6 22:24:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA00849 for current-outgoing; Fri, 6 Jun 1997 22:24:06 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA00810 for ; Fri, 6 Jun 1997 22:24:02 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id OAA10738; Sat, 7 Jun 1997 14:52:45 +0930 (CST) From: Michael Smith Message-Id: <199706070522.OAA10738@genesis.atrad.adelaide.edu.au> Subject: Re: cd9660 w/ Joliet extensions In-Reply-To: from Frank Durda IV at "Jun 6, 97 07:43:00 pm" To: uhclem@nemesis.lonestar.org (Frank Durda IV) Date: Sat, 7 Jun 1997 14:52:45 +0930 (CST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Frank Durda IV stands accused of saying: > > This might be moot soon since all of Microsoft new OS beta material is > coming out in the "UDF - Universal Disk Format". When you stick one > of these discs in an existing Windows '95, FreeBSD, or DOS system, you > can only see one file that has a message saying you need to upgrade your > operating system to see the full contents of the disk. So, is there any documentation on this format? Is it another sucky attempt to foist FAT on the masses, or a serious attempt at a portable filesystem implementation? > Frank Durda IV - only these addresses work:|"Tandys THOR - Ten years too -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Fri Jun 6 22:24:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA00902 for current-outgoing; Fri, 6 Jun 1997 22:24:50 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA00893 for ; Fri, 6 Jun 1997 22:24:46 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id OAA10751; Sat, 7 Jun 1997 14:54:17 +0930 (CST) From: Michael Smith Message-Id: <199706070524.OAA10751@genesis.atrad.adelaide.edu.au> Subject: Re: sio driver performance In-Reply-To: <199706070402.XAA26092@bmccane.uit.net> from Wm Brian McCane at "Jun 6, 97 11:02:10 pm" To: root@bmccane.uit.net (Wm Brian McCane) Date: Sat, 7 Jun 1997 14:54:17 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, straka@inficad.com, bde@zeta.org.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Wm Brian McCane stands accused of saying: > I think Mike is right on this one. I would suggest adding a select call to > your program with a read and exception fd_set. If the bit gets set in the > exception fd_set, close the port and reopen it. This way you will wait until > DCD is high before continuing your reads. It also makes a nice spring-board > for when someone asks you to monitor more ports at once. It's easy enough just to wait for read() to return zero, close and reopen the device, if that's all you care about. > brian -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Fri Jun 6 23:58:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA03611 for current-outgoing; Fri, 6 Jun 1997 23:58:03 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA03605 for ; Fri, 6 Jun 1997 23:58:00 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id HAA18268 for freebsd.org!freebsd-current; Sat, 7 Jun 1997 07:44:33 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sat, 7 Jun 1997 07:48:12 +0100 X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 7 Jun 1997 07:45:03 +0100 To: freebsd-current@freebsd.org From: Bob Bishop Subject: src-cur.2909 where are you? Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk src-cur.2909 never made it here, nor to the mirror at tu-berlin.de. Can't get into uni-trier.de because of login limits. And: 331-(220 freefall.freebsd.org FTP server (Version 6.00) ready.) 331 Guest login ok, send your email address as password. Password: 550 Can't set guest privileges. ftp: Login failed. Bummer. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-current Sat Jun 7 05:21:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA15224 for current-outgoing; Sat, 7 Jun 1997 05:21:52 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA15218 for ; Sat, 7 Jun 1997 05:21:49 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA24184; Sat, 7 Jun 1997 14:21:47 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id OAA02147; Sat, 7 Jun 1997 14:19:44 +0200 (MET DST) Message-ID: <19970607141944.FJ15967@uriah.heep.sax.de> Date: Sat, 7 Jun 1997 14:19:44 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: current@FreeBSD.ORG Cc: karl@Mcs.Net (Karl Denninger) Subject: Re: Make release failure References: <19970606174520.25878@Jupiter.Mcs.Net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970606174520.25878@Jupiter.Mcs.Net>; from Karl Denninger on Jun 6, 1997 17:45:20 -0500 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Karl Denninger wrote: > cd /disk/release/usr && rm -rf src && cvs -d co -P src ^ > cvs: invalid option -- P It's obvious if you look into the Makefile. You're missing the CVSROOT variable. <:-) .if !defined(RELEASETAG) cd ${CHROOTDIR}/usr && rm -rf src && \ cvs -d ${CVSROOT} co -P src ^^^^^^^^^^^^^ -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Jun 7 06:03:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA16509 for current-outgoing; Sat, 7 Jun 1997 06:03:32 -0700 (PDT) Received: from freebsd.scds.com (scds.ziplink.net [206.15.128.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA16502 for ; Sat, 7 Jun 1997 06:03:27 -0700 (PDT) Received: (from jseger@localhost) by freebsd.scds.com (8.8.5/8.7.3) id IAA02679 for current@freebsd.org; Sat, 7 Jun 1997 08:11:04 -0400 (EDT) Date: Sat, 7 Jun 1997 08:11:04 -0400 (EDT) From: "Justin M. Seger" Message-Id: <199706071211.IAA02679@freebsd.scds.com> To: current@freebsd.org Subject: crontab errors Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Anyone know what would be causing this? Jun 7 07:30:00 freebsd CRON[2614]: login_getclass: unknown class 'root' It does the same thing with inetd and cron every few minutes... Any idea what would cause it? I understand with the cron it is whenever a cron job runs... Thanks in advance, -Justin Seger- From owner-freebsd-current Sat Jun 7 06:31:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA17460 for current-outgoing; Sat, 7 Jun 1997 06:31:57 -0700 (PDT) Received: from ic.net (qmailr@srv1b.ic.net [152.160.72.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA17455 for ; Sat, 7 Jun 1997 06:31:55 -0700 (PDT) Received: (qmail 22062 invoked from network); 7 Jun 1997 13:31:29 -0000 Received: from unknown (HELO lurch.rickl.org) (152.160.108.21) by unknown with SMTP; 7 Jun 1997 13:31:29 -0000 Received: from lurch.rickl.org (lurch.rickl.org [192.168.255.1]) by lurch.rickl.org (8.8.5/8.7.3) with ESMTP id JAA00409; Sat, 7 Jun 1997 09:31:40 -0400 (EDT) Date: Sat, 7 Jun 1997 09:31:40 -0400 (EDT) From: Rick Lotoczky Reply-To: Rick Lotoczky Subject: Re: crontab errors To: jseger@freebsd.scds.com cc: current@FreeBSD.ORG In-Reply-To: <199706071211.IAA02679@freebsd.scds.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Justin, Don't know the exact cause, but it went away when I updated the /etc directory. Rick From owner-freebsd-current Sat Jun 7 07:27:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA19422 for current-outgoing; Sat, 7 Jun 1997 07:27:23 -0700 (PDT) Received: from bmccane.uit.net (bmccane.uit.net [208.129.189.48]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA19407 for ; Sat, 7 Jun 1997 07:26:59 -0700 (PDT) Received: from bmccane.uit.net (localhost.mccane.com [127.0.0.1]) by bmccane.uit.net (8.8.5/8.8.5) with ESMTP id JAA19490 for ; Sat, 7 Jun 1997 09:26:38 -0500 (CDT) Message-Id: <199706071426.JAA19490@bmccane.uit.net> X-Mailer: exmh version 2.0gamma 1/27/96 To: current@freebsd.org Subject: Lockup Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 07 Jun 1997 09:26:38 -0500 From: Wm Brian McCane Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have found an `interesting' lockup in -current involving NFS. If I have a filesystem mounted from my server machine onto one of my client machines, and then unmount the filesystem on the server, the next time I type `df' the client stops working. No panic, nothing just dead. In X the mouse stops moving, and I cannot switch to a text console. On a text console, I cannot get any response to the keyboard, including Ctrl-Alt-Del. I was thinking about adding DDB to the kernel, but with this type of lockup, I suspect it won't do any good. I discovered this the other night when I developed a couple of bad blocks on a drive and repartitioned it to allow bad144 bad sector forwarding, before reloading from tape. brian From owner-freebsd-current Sat Jun 7 07:41:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA19913 for current-outgoing; Sat, 7 Jun 1997 07:41:52 -0700 (PDT) Received: from bmccane.uit.net (bmccane.uit.net [208.129.189.48]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA19908 for ; Sat, 7 Jun 1997 07:41:49 -0700 (PDT) Received: from bmccane.uit.net (localhost.mccane.com [127.0.0.1]) by bmccane.uit.net (8.8.5/8.8.5) with ESMTP id JAA19759; Sat, 7 Jun 1997 09:40:22 -0500 (CDT) Message-Id: <199706071440.JAA19759@bmccane.uit.net> X-Mailer: exmh version 2.0gamma 1/27/96 To: "Justin M. Seger" cc: current@FreeBSD.ORG Subject: Re: crontab errors In-reply-to: Your message of "Sat, 07 Jun 1997 08:11:04 EDT." <199706071211.IAA02679@freebsd.scds.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 07 Jun 1997 09:40:22 -0500 From: Wm Brian McCane Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Anyone know what would be causing this? > > Jun 7 07:30:00 freebsd CRON[2614]: login_getclass: unknown class 'root' > > It does the same thing with inetd and cron every few minutes... Any idea what > would cause it? I understand with the cron it is whenever a cron job runs... > > Thanks in advance, > -Justin Seger- You just upgraded to a version of -current which has login classes, and you have not installed a copy of login.conf in /etc yet. Copy it from /usr/src/etc and your errors will go away. brian From owner-freebsd-current Sat Jun 7 08:02:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA20511 for current-outgoing; Sat, 7 Jun 1997 08:02:54 -0700 (PDT) Received: from plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA20506 for ; Sat, 7 Jun 1997 08:02:50 -0700 (PDT) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by plaut.de (8.6.12/8.6.12) with ESMTP id RAA19619; Sat, 7 Jun 1997 17:02:45 +0200 Received: from localhost (root@localhost) by totum.plaut.de (8.8.5/8.7.3) with SMTP id RAA21700; Sat, 7 Jun 1997 17:02:47 +0200 (MET DST) Date: Sat, 7 Jun 1997 17:02:47 +0200 (MET DST) From: Michael Reifenberger To: Wm Brian McCane cc: current@FreeBSD.ORG Subject: Re: Lockup In-Reply-To: <199706071426.JAA19490@bmccane.uit.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 7 Jun 1997, Wm Brian McCane wrote: > Date: Sat, 07 Jun 1997 09:26:38 -0500 > From: Wm Brian McCane > To: current@FreeBSD.ORG > Subject: Lockup > > I have found an `interesting' lockup in -current involving NFS. If I have a > filesystem mounted from my server machine onto one of my client machines, and > then unmount the filesystem on the server, the next time I type `df' the > client stops working. No panic, nothing just dead. In X the mouse stops > moving, and I cannot switch to a text console. On a text console, I cannot Could it be that you have mounted the remote FS to /? And you mounted it hard. So if a process traverses the rootdir it gets blocked. A workaround should be: mkdir /mnt/foo mount dest:/bla /mnt/foo ln -s /mnt/foo / I'm not shure if it is suffitient to mount the FS soft/intr. BTW: Does amd help in such a situation(server dies)? Has anybody tried? Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis From owner-freebsd-current Sat Jun 7 08:19:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA20913 for current-outgoing; Sat, 7 Jun 1997 08:19:41 -0700 (PDT) Received: from freebsd.scds.com (scds.ziplink.net [206.15.128.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA20908 for ; Sat, 7 Jun 1997 08:19:38 -0700 (PDT) Received: (from jseger@localhost) by freebsd.scds.com (8.8.5/8.7.3) id KAA05088; Sat, 7 Jun 1997 10:27:17 -0400 (EDT) Date: Sat, 7 Jun 1997 10:27:17 -0400 (EDT) From: "Justin M. Seger" Message-Id: <199706071427.KAA05088@freebsd.scds.com> To: jseger@freebsd.scds.com, root@bmccane.uit.net Subject: Re: crontab errors Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thanks. -Justin Seger- From owner-freebsd-current Sat Jun 7 09:31:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA24148 for current-outgoing; Sat, 7 Jun 1997 09:31:21 -0700 (PDT) Received: from unique.usn.blaze.net.au (unique.usn.blaze.net.au [203.17.53.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA24141 for ; Sat, 7 Jun 1997 09:31:17 -0700 (PDT) Received: from unique.usn.blaze.net.au (local [127.0.0.1]) by unique.usn.blaze.net.au (8.8.5/8.8.5) with ESMTP id CAA27373; Sun, 8 Jun 1997 02:30:53 +1000 (EST) Message-Id: <199706071630.CAA27373@unique.usn.blaze.net.au> To: Tom , current@freebsd.org Subject: Re: Use of your strptime(3) code (fwd) In-reply-to: Your message of "Thu, 05 Jun 1997 14:49:01 MST." X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P#N+Ec~Z&@;'LL!;3?y Date: Sun, 08 Jun 1997 02:30:51 +1000 From: David Nugent Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>> Because in 2.0b6, the author removed the requirement for a system >>> strptime(3) call. Still, this situtation may come up again, so I offered >>> it as something to add to libc/libcompat. >> >> Again, with the existing copyright, it's simply unacceptable. I'm >> saying this for at least the third time now, but didn't get any >> response so far. > > Also, I don't think we need it. None of the hundreds of other ports > need it, and as it seems neither does msql. By the same token, we don't "need" anything in libc which isn't a system call, right? I mean, why not have apps do it all themselves? :-) Ok, perhaps this is a little too sarcastic, but there have been two instances in the last couple of months where I could have used a strptime(). pw(8), for example, could make use of it. It currently doesn't "need" strptime() because it uses a different longhand method, but if it was available in libc, it would *certainly* use it. Same probably goes for anything that needs to parse a date/time. It is a common enough need to put it into libc, imho. Other UNIX vendors including NetBSD obviously think so too. Regards, David From owner-freebsd-current Sat Jun 7 09:44:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA24938 for current-outgoing; Sat, 7 Jun 1997 09:44:20 -0700 (PDT) Received: from watcher.isl.net (ppp-68.isl.net [199.3.25.117]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA24931 for ; Sat, 7 Jun 1997 09:44:16 -0700 (PDT) Received: (from ortmann@localhost) by watcher.isl.net (8.8.5/8.8.5) id LAA00966; Sat, 7 Jun 1997 11:43:36 -0500 (CDT) From: Daniel Ortmann Message-Id: <199706071643.LAA00966@watcher.isl.net> Subject: Re: src-cur.2909 where are you? To: rb@gid.co.uk (Bob Bishop) Date: Sat, 7 Jun 1997 11:43:34 -0500 (CDT) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from Bob Bishop at "Jun 7, 97 07:45:03 am" X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > src-cur.2909 never made it here, nor to the mirror at tu-berlin.de. > > Can't get into uni-trier.de because of login limits. > > And: > > 331-(220 freefall.freebsd.org FTP server (Version 6.00) ready.) > 331 Guest login ok, send your email address as password. > Password: > 550 Can't set guest privileges. > ftp: Login failed. > > Bummer. I ran a host command getting freebsd.org sites and auto-built a set of [ -f src-cur.2909.gz ] || fetch commands with it, thinking that this would be an efficient way to find it. (It didn't find it.) The odd thing that I discovered that a large number of the foreign freebsd addresses could not be found. Why is that? Is there a pervasive problem with DNS's? -- Daniel Ortmann 507.288.7732 (h) ortmann@isl.net 2414 30 av NW, #D 507.253.6795 (w) ortmann@vnet.ibm.com Rochester, MN 55901 "PERL: The Swiss Army Chainsaw" From owner-freebsd-current Sat Jun 7 10:39:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA28232 for current-outgoing; Sat, 7 Jun 1997 10:39:34 -0700 (PDT) Received: from sliphost37.uni-trier.de (root@sliphost37.uni-trier.de [136.199.240.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA28227 for ; Sat, 7 Jun 1997 10:39:30 -0700 (PDT) Received: (from blank@localhost) by sliphost37.uni-trier.de (8.8.5/8.8.5) id PAA00402; Sat, 7 Jun 1997 15:04:59 +0200 (CEST) From: Sascha Blank Message-Id: <199706071304.PAA00402@sliphost37.uni-trier.de> Subject: Re: src-cur.2909 where are you? In-Reply-To: from Bob Bishop at "Jun 7, 97 07:45:03 am" To: rb@gid.co.uk (Bob Bishop) Date: Sat, 7 Jun 1997 15:04:59 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG Reply-To: blank@fox.uni-trier.de (Sascha Blank) X-System: FreeBSD 2.2-STABLE X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello Bob, Bob Bishop has written recently: > src-cur.2909 never made it here, nor to the mirror at tu-berlin.de. > > Can't get into uni-trier.de because of login limits. Try our ftpmail service. Write a mail with the subject "help" to ftpmail@ftp.uni-trier.de -- Sascha Blank - mailto:blank@fox.uni-trier.de Student and System Administrator at the University of Trier, Germany Finger my account to receive my Public PGP key I don't speak for my employers, they don't pay me enough for that. From owner-freebsd-current Sat Jun 7 11:38:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA00243 for current-outgoing; Sat, 7 Jun 1997 11:38:13 -0700 (PDT) Received: from redemption.uniserve.com (redemption.uniserve.com [204.191.197.254]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA00235 for ; Sat, 7 Jun 1997 11:38:08 -0700 (PDT) Received: from haven.uniserve.com [198.53.215.121] by redemption.uniserve.com with smtp (Exim 1.62 #1) id 0waQNG-0000lI-00; Sat, 7 Jun 1997 11:38:02 -0700 Date: Sat, 7 Jun 1997 11:42:45 -0700 (PDT) From: Tom Samplonius To: Rick Lotoczky cc: jseger@freebsd.scds.com, current@freebsd.org Subject: Re: crontab errors In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 7 Jun 1997, Rick Lotoczky wrote: > Hi Justin, > > Don't know the exact cause, but it went away when I updated the /etc > directory. > > Rick > It is caused by not having a /etc/login.conf file. Tom From owner-freebsd-current Sat Jun 7 16:06:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA13144 for current-outgoing; Sat, 7 Jun 1997 16:06:38 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA13135 for ; Sat, 7 Jun 1997 16:06:32 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id AAA23800; Sun, 8 Jun 1997 00:45:21 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.5/8.8.5) id UAA24368; Sat, 7 Jun 1997 20:41:56 +0200 (CEST) Message-ID: <19970607204155.35866@klemm.gtn.com> Date: Sat, 7 Jun 1997 20:41:55 +0200 From: Andreas Klemm To: Freebsd Cc: current@FreeBSD.ORG Subject: Re: printer Reply-To: freebsd-questions@FreeBSD.ORG, andreas@klemm.gtn.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.75 In-Reply-To: ; from Freebsd on Fri, Jun 06, 1997 at 09:54:50AM -0400 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Jun 06, 1997 at 09:54:50AM -0400, Freebsd wrote: > if I were to setup a network printer on freebsd. basicly I > would need what to enable it so my win95 system can print also on it ? > printer is connected to bsd box. You need samba, to share your printer on the network for Windows operating systems. If you have Windows NT, then you only have to install TCP/IP printing on the NT box as additional service. After that you can directly print to the FreeBSD machine via lpd protocol. You might be interested in installing apsfilter on the FreeBSD machine, if your printer is a PS printer or is supported by gs, which acts as a Postscript emulator. > I am not sure if this is the correct mail list. Reply-To: set to FreeBSD-questions and me, since I don't read -questions, but am willed to help. -- Andreas Klemm | klemm.gtn.com - powered by Symmetric MultiProcessor FreeBSD http://www.freebsd.org/~fsmp/SMP/SMP.html http://www.freebsd.org/~fsmp/SMP/benches.html