From owner-freebsd-current Sun Jul 26 02:38:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00346 for freebsd-current-outgoing; Sun, 26 Jul 1998 02:38:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA00341; Sun, 26 Jul 1998 02:38:56 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id LAA17306; Sun, 26 Jul 1998 11:38:26 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sun, 26 Jul 1998 11:38:25 +0200 (MET DST) Mime-Version: 1.0 To: Garrett Wollman Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysexits References: <199807260217.WAA05555@khavrinen.lcs.mit.edu> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 26 Jul 1998 11:38:25 +0200 In-Reply-To: Garrett Wollman's message of "Sat, 25 Jul 1998 22:17:12 -0400 (EDT)" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id CAA00342 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman writes: > < > at least in some applications - a failed malloc(), calloc() or > > realloc(). I therefore suggest adding the constant EX_NOMEM, with the > > value 79, to /usr/include/sysexits.h, and bumping EX__MAX to 79 (as > Good idea. I would also add EX_NOGROUP (parallel to EX_NOUSER). > Don't forget to update the table of names in sendmail. Hmm... I didn't think of Sendmail. What will happen the next time we upgrade Sendmail (to 8.9.1)? Will somebody remember to merge that patch into the new version? Or will Sendmail suddenly no longer understand EX_NOMEM and EX_NOGROUP? DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 03:17:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA05028 for freebsd-current-outgoing; Sun, 26 Jul 1998 03:17:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04982 for ; Sun, 26 Jul 1998 03:17:01 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id MAA16090; Sun, 26 Jul 1998 12:15:07 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id LAA06566; Sun, 26 Jul 1998 11:24:01 +0200 (CEST) (envelope-from andreas) Message-ID: <19980726112401.A5570@klemm.gtn.com> Date: Sun, 26 Jul 1998 11:24:01 +0200 From: Andreas Klemm To: dg@root.com, Brian Feldman Cc: freebsd-current@FreeBSD.ORG Subject: Re: New LINT options: what is VM coloring? References: <199807260010.RAA27997@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199807260010.RAA27997@implode.root.com>; from David Greenman on Sat, Jul 25, 1998 at 05:10:54PM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 25, 1998 at 05:10:54PM -0700, David Greenman wrote: > Page coloring is the process of allocating pages that have physical > alignment that provides optimal utilization of the memory cache. This can > be a big win for direct-mapped caches (e.g. most Pentium L2 caches), but > loses effectiveness with set-associative caches (e.g. Pentium Pro, which > has a set size of 4). Do you think it would be better to turn PQ off using: options PQ_NOOPT # No coloring -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 03:23:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA05638 for freebsd-current-outgoing; Sun, 26 Jul 1998 03:23:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA05595 for ; Sun, 26 Jul 1998 03:22:41 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id DAA07327; Sun, 26 Jul 1998 03:20:23 -0700 (PDT) Message-Id: <199807261020.DAA07327@implode.root.com> To: Andreas Klemm cc: Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: New LINT options: what is VM coloring? In-reply-to: Your message of "Sun, 26 Jul 1998 11:24:01 +0200." <19980726112401.A5570@klemm.gtn.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 26 Jul 1998 03:20:23 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Sat, Jul 25, 1998 at 05:10:54PM -0700, David Greenman wrote: >> Page coloring is the process of allocating pages that have physical >> alignment that provides optimal utilization of the memory cache. This can >> be a big win for direct-mapped caches (e.g. most Pentium L2 caches), but >> loses effectiveness with set-associative caches (e.g. Pentium Pro, which >> has a set size of 4). > >Do you think it would be better to turn PQ off using: > > options PQ_NOOPT # No coloring You mean in the Pentium Pro case? No, page coloring has basically no overhead and can only help - even with associative caches. I think the "PQ_NOOPT" option is only for performance comparison/testing. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 05:16:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA18427 for freebsd-current-outgoing; Sun, 26 Jul 1998 05:16:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18422 for ; Sun, 26 Jul 1998 05:16:55 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id OAA23710; Sun, 26 Jul 1998 14:15:07 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id NAA27684; Sun, 26 Jul 1998 13:37:03 +0200 (CEST) (envelope-from andreas) Message-ID: <19980726133703.A27677@klemm.gtn.com> Date: Sun, 26 Jul 1998 13:37:03 +0200 From: Andreas Klemm To: dg@root.com Cc: Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: New LINT options: what is VM coloring? References: <19980726112401.A5570@klemm.gtn.com> <199807261020.DAA07327@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199807261020.DAA07327@implode.root.com>; from David Greenman on Sun, Jul 26, 1998 at 03:20:23AM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 26, 1998 at 03:20:23AM -0700, David Greenman wrote: > >On Sat, Jul 25, 1998 at 05:10:54PM -0700, David Greenman wrote: > >> Page coloring is the process of allocating pages that have physical > >> alignment that provides optimal utilization of the memory cache. This can > >> be a big win for direct-mapped caches (e.g. most Pentium L2 caches), but > >> loses effectiveness with set-associative caches (e.g. Pentium Pro, which > >> has a set size of 4). > > > >Do you think it would be better to turn PQ off using: > > > > options PQ_NOOPT # No coloring > > You mean in the Pentium Pro case? No, page coloring has basically no > overhead and can only help - even with associative caches. I think the > "PQ_NOOPT" option is only for performance comparison/testing. Ok, thanks ! -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 05:22:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA18801 for freebsd-current-outgoing; Sun, 26 Jul 1998 05:22:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18796 for ; Sun, 26 Jul 1998 05:22:22 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id OAA24155; Sun, 26 Jul 1998 14:21:53 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sun, 26 Jul 1998 14:21:52 +0200 (MET DST) Mime-Version: 1.0 To: Adrian Penisoara Cc: Gerald Ehritz , freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 completely References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 26 Jul 1998 14:21:50 +0200 In-Reply-To: Adrian Penisoara's message of "Sat, 25 Jul 1998 11:16:30 +0300 (EEST)" Message-ID: Lines: 20 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id FAA18797 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adrian Penisoara writes: > Other people complained about persmission issues too; it seems like > ftp.FreeBSD.org changes the permissions of the uploaded files in > /pub/FreeBSD/incoming to smth. like o-rwx ; strangely I can get the file Yes. This was necessary to stop /pub/FreeBSD/incoming from filling up with WaReZ. There was a discussion about this on -commit a while back, IIRC; you may want to search the archives. > with Netscape but not with wget or ftp... You shouldn't be able to get them at all. > Who's in charge with ftp.FreeBSD.org/pub/FreeBSD maintainance ? freebsd-maintainers@ftp.freebsd.org DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 06:42:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24936 for freebsd-current-outgoing; Sun, 26 Jul 1998 06:42:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24918 for ; Sun, 26 Jul 1998 06:42:21 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id PAA03625 for freebsd-current@FreeBSD.ORG; Sun, 26 Jul 1998 15:41:52 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 1401AA6EB; Sun, 26 Jul 1998 14:11:37 +0200 (CEST) Message-ID: <19980726141137.A11215@keltia.freenix.fr> Date: Sun, 26 Jul 1998 14:11:37 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: New LINT options: what is VM coloring? Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199807260010.RAA27997@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199807260010.RAA27997@implode.root.com>; from David Greenman on Sat, Jul 25, 1998 at 05:10:54PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4462 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to David Greenman: > be a big win for direct-mapped caches (e.g. most Pentium L2 caches), but > loses effectiveness with set-associative caches (e.g. Pentium Pro, which > has a set size of 4). The K6 has a 2-way set associative cache so I guess it is not interesting to use page coloring but does anyone know what kind of L2 cache an ASUS T2P4 use ? It is a P5-class motherboard so it is possible that the cache is direct-mapped, no ? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #61: Sun Jul 12 14:38:23 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 07:51:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00536 for freebsd-current-outgoing; Sun, 26 Jul 1998 07:51:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00531 for ; Sun, 26 Jul 1998 07:51:17 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id JAA22449; Sun, 26 Jul 1998 09:50:50 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id JAA10307; Sun, 26 Jul 1998 09:50:50 -0500 (CDT) Message-ID: <19980726095049.51700@mcs.net> Date: Sun, 26 Jul 1998 09:50:49 -0500 From: Karl Denninger To: Garrett Wollman Cc: Dan Swartzendruber , current@FreeBSD.ORG Subject: Re: MMAP problems References: <19980725155148.43084@mcs.net> <3.0.5.32.19980725172640.00944ac0@mail.kersur.net> <19980725163243.36509@mcs.net> <199807260252.WAA05646@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807260252.WAA05646@khavrinen.lcs.mit.edu>; from Garrett Wollman on Sat, Jul 25, 1998 at 10:52:34PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 25, 1998 at 10:52:34PM -0400, Garrett Wollman wrote: > < said: > > > I can verify that CAM is not related to this; it happens with NON-CAM > > kernels as well. > > I've been seeing it for several months. > > I believe it to be a coherency problem. The relevant operations here > are: > > 1) A diablo server process appends to a spool file using explicit > I/O. (Note that the file is not opened in O_APPEND mode.) Yep. Do you have any kind of guess as to whether opening the file O_APPEND would be legit (and would it fix this?) I don't THINK the server process ever "backs up", so this *should* be ok, but I don't want to make that change without having a "better than a guess" shot at it. > 2) A boatload of dnewslink processes simultaneously mmap the pages of > the spool file containing the article in question, suck the article > out of it, and blast it over to the remote feed. Yep. That's the basic model. Diablo beats the shit out of MMAP and I/O; the code is very clever in trying to avoid unnecessary I/O... > Here's my particular guess... I think this happens when the dnewslink > processes are reading another, short, article in the last page of the > file, while a diablo server is writing a new article. Somewhere, > there is a race condition in which the kernel has copied the new data > into the buffer, but blocks before it updates the valid length; this > then allows one of the mmaps to succeed, and since that part of the > buffer is marked invalid, it gets zeroed. Then the diablo process > resumes, and marks the end of the buffer valid, although the data it > was writing has just gotten clobbered. Hmmm.... why would dnntplink not mmap the file readonly though (and wouldn't this solve the problem)? > It looks, from an inspection of the relevant code in ufs_readwrite.c > and ffs_balloc.c, that this cannot happen, because the data are always > copied in last. It does appear that there are potential windows, if > ffs_balloc() blocks, where other processes might see invalid data in > the file through mmap as a result of vnode_pager_setsize() having > already been run, but it does not appear such garbage could possibly > persist and be written back to disk, and I certainly see it directly > on the disk, not just in memory. > > -GAWollman Yep. After about 6 hours of pouring over the code last night (literally and figuratively :-) this is what I think is going on as well. And I can confirm that the trash IS being written to disk; its definitely there on stable storage when you go look for it later. The data which gets written is usually a block of zeros, but it may not be; it can also be random trash. Its also not always one block (it could be more than one), but it IS always, at least from what I'm seeing here, a multiple of 512 bytes (disk blocksize). -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 08:12:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02302 for freebsd-current-outgoing; Sun, 26 Jul 1998 08:12:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ady.warpnet.ro (ady.warpnet.ro [193.230.201.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02265 for ; Sun, 26 Jul 1998 08:12:27 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.8.8/8.8.8) with ESMTP id SAA11526; Sun, 26 Jul 1998 18:10:44 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Sun, 26 Jul 1998 18:10:44 +0300 (EEST) From: Adrian Penisoara To: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= cc: Gerald Ehritz , freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 completely In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On 26 Jul 1998, Dag-Erling Coidan [iso-8859-1] Smørgrav wrote: > Adrian Penisoara writes: > > Other people complained about persmission issues too; it seems like > > ftp.FreeBSD.org changes the permissions of the uploaded files in > > /pub/FreeBSD/incoming to smth. like o-rwx ; strangely I can get the file > > Yes. This was necessary to stop /pub/FreeBSD/incoming from filling up > with WaReZ. There was a discussion about this on -commit a while back, Good reason; I'm not sure if this was such a good way to fix it... > IIRC; you may want to search the archives. I'll do that. > > > DES > -- > Dag-Erling Smørgrav - dag-erli@ifi.uio.no > Thanks, Ady (@freebsd.ady.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 09:49:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08774 for freebsd-current-outgoing; Sun, 26 Jul 1998 09:49:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles247.castles.com [208.214.165.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08769 for ; Sun, 26 Jul 1998 09:49:08 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA10667; Sun, 26 Jul 1998 09:47:55 -0700 (PDT) Message-Id: <199807261647.JAA10667@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Karl Denninger cc: Garrett Wollman , Dan Swartzendruber , current@FreeBSD.ORG Subject: Re: MMAP problems In-reply-to: Your message of "Sun, 26 Jul 1998 09:50:49 CDT." <19980726095049.51700@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 09:47:54 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And I can confirm that the trash IS being written to disk; its definitely > there on stable storage when you go look for it later. > > The data which gets written is usually a block of zeros, but it may not be; > it can also be random trash. Its also not always one block (it could be > more than one), but it IS always, at least from what I'm seeing here, a > multiple of 512 bytes (disk blocksize). The significant question in light of Garrett's description seem to be whether the trash that's written is actually being written by the process in error because that's what it got from a previous read, or whether the process is actually writing the right stuff and it's being corrupted on the way down. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 09:50:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09027 for freebsd-current-outgoing; Sun, 26 Jul 1998 09:50:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09014 for ; Sun, 26 Jul 1998 09:50:29 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id SAA07999; Sun, 26 Jul 1998 18:49:59 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sun, 26 Jul 1998 18:49:58 +0200 (MET DST) Mime-Version: 1.0 To: Adrian Penisoara Cc: "Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= =?iso-8859-1?Q?=2C?= Gerald Ehritz" , freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 completely References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 26 Jul 1998 18:49:58 +0200 In-Reply-To: Adrian Penisoara's message of "Sun, 26 Jul 1998 18:10:44 +0300 (EEST)" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA09020 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adrian Penisoara writes: > On 26 Jul 1998, Dag-Erling Coidan [iso-8859-1] Smørgrav wrote: > > Adrian Penisoara writes: > > > Other people complained about persmission issues too; it seems like > > > ftp.FreeBSD.org changes the permissions of the uploaded files in > > > /pub/FreeBSD/incoming to smth. like o-rwx ; strangely I can get the file > > Yes. This was necessary to stop /pub/FreeBSD/incoming from filling up > > with WaReZ. There was a discussion about this on -commit a while back, > Good reason; I'm not sure if this was such a good way to fix it... It's the *only* way, unless you want to shut down the incoming directory altogether. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 09:50:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09085 for freebsd-current-outgoing; Sun, 26 Jul 1998 09:50:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09070 for ; Sun, 26 Jul 1998 09:50:48 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id LAA01167; Sun, 26 Jul 1998 11:49:35 -0500 (EST) (envelope-from toor) Message-Id: <199807261649.LAA01167@dyson.iquest.net> Subject: Re: New LINT options: what is VM coloring? In-Reply-To: <19980726141137.A11215@keltia.freenix.fr> from Ollivier Robert at "Jul 26, 98 02:11:37 pm" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Sun, 26 Jul 1998 11:49:34 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier Robert said: > According to David Greenman: > > be a big win for direct-mapped caches (e.g. most Pentium L2 caches), but > > loses effectiveness with set-associative caches (e.g. Pentium Pro, which > > has a set size of 4). > > The K6 has a 2-way set associative cache so I guess it is not interesting > to use page coloring but does anyone know what kind of L2 cache an ASUS T2P4 > use ? It is a P5-class motherboard so it is possible that the cache is > direct-mapped, no ? > David is essentially right. However, the page coloring code (that has been in -current for the last >1yr) goes a little too far and colors even the 1st level cache (I know -- I did it.) Also, there is the issue of proper choice of initial color values, so I used an ad-hoc approach that appears to work correctly most of the time. Almost all P5 MB's use direct mapped 2nd level caches. Only certain of the specialized P5 cache mgr chips do a 4way set assoc scheme. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 09:58:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10004 for freebsd-current-outgoing; Sun, 26 Jul 1998 09:58:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09991 for ; Sun, 26 Jul 1998 09:58:43 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id LAA01185; Sun, 26 Jul 1998 11:58:04 -0500 (EST) (envelope-from toor) Message-Id: <199807261658.LAA01185@dyson.iquest.net> Subject: Re: panic: page fault while in kernel mode - from gcc In-Reply-To: <199807231959.OAA24934@home.dragondata.com> from Kevin Day at "Jul 23, 98 02:59:08 pm" To: toasty@home.dragondata.com (Kevin Day) Date: Sun, 26 Jul 1998 11:58:03 -0500 (EST) Cc: tlambert@primenet.com, dg@root.com, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kevin Day said: > > > >> This seems to indicate that the new process's page directory either hasn't > > > >> been allocated yet or went away for some reason. Apparantly one of several > > > >> new bugs that John has left us with. > > > >> > > > > > > > >Is there any reason why someone doesn't back out his last few batches of > > > >large vm changes? Apparently he was half done with some of it, and what we > > > >had before seemed more stable than what we have now. > > > > > > That may ultimately be what we have to do, but the fixes also fixed some > > > serious 'leak' style problems with the Mach derived VM system, so I'd rather > > > that we find the bugs and fix them rather than going back to the previous > > > code. > > > > FreeBSD doesn't currently include the batch of patches that Elvind > > saved and that John had in his home directory when it was removed, > > does it? > > > > What is the behaviour with those patches added in? > > > > Right now, with my -current server, I get a 'panic: page fault while in > kernel mode' about once a week.... Dual Processor, P/200 with 256M of ram. > Most of the problems seem to occur when the system is starting to swap.. > (obviously) > Ahha!!! There is a *severe* bug in the current SMP pmap code, that it is important to preemptively stop all processors before updating any of the shared pmap entries (actually, that isn't totally necessary, but is a solution to the problem.) It is a combo of P6/PII errata, and the fact that lazy TLB updates are almost impossible to get right. I think that my patches as distributed might have the non-lazy TLB update code in them. If someone is bona-fide going to fix the problem, I can pass them the relevent fixes (I can help with that one -- since it is just distilling out existant fixes, and won't require the endless boot/reboot cycle :-)). One caveat: removing the lazy TLB updates appears to open up other bugs elsewhere. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 10:04:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10798 for freebsd-current-outgoing; Sun, 26 Jul 1998 10:04:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ady.warpnet.ro (ady.warpnet.ro [193.230.201.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10786 for ; Sun, 26 Jul 1998 10:04:15 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.8.8/8.8.8) with ESMTP id UAA12261; Sun, 26 Jul 1998 20:03:15 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Sun, 26 Jul 1998 20:03:15 +0300 (EEST) From: Adrian Penisoara To: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= cc: freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 completely In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On 26 Jul 1998, Dag-Erling Coidan [iso-8859-1] Smørgrav wrote: > > > > Other people complained about persmission issues too; it seems like > > > > ftp.FreeBSD.org changes the permissions of the uploaded files in > > > > /pub/FreeBSD/incoming to smth. like o-rwx ; strangely I can get the file > > > Yes. This was necessary to stop /pub/FreeBSD/incoming from filling up > > > with WaReZ. There was a discussion about this on -commit a while back, > > Good reason; I'm not sure if this was such a good way to fix it... > > It's the *only* way, unless you want to shut down the incoming > directory altogether. Well, this prevents some people like me, who don't have accounts on the server, to make available to everybody useful patches & other sort of things.. But we live in a cruel world and this list isn't the right place to discuss this -- so we'd better kill this thread... > > DES > -- > Dag-Erling Smørgrav - dag-erli@ifi.uio.no > Happy hacking, Ady (@freebsd.ady.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 11:47:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22197 for freebsd-current-outgoing; Sun, 26 Jul 1998 11:47:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22189 for ; Sun, 26 Jul 1998 11:47:37 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id NAA26869; Sun, 26 Jul 1998 13:46:52 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id NAA12489; Sun, 26 Jul 1998 13:46:52 -0500 (CDT) Message-ID: <19980726134652.16525@mcs.net> Date: Sun, 26 Jul 1998 13:46:52 -0500 From: Karl Denninger To: Mike Smith Cc: Garrett Wollman , Dan Swartzendruber , current@FreeBSD.ORG Subject: Re: MMAP problems References: <19980726095049.51700@mcs.net> <199807261647.JAA10667@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807261647.JAA10667@antipodes.cdrom.com>; from Mike Smith on Sun, Jul 26, 1998 at 09:47:54AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 26, 1998 at 09:47:54AM -0700, Mike Smith wrote: > > And I can confirm that the trash IS being written to disk; its definitely > > there on stable storage when you go look for it later. > > > > The data which gets written is usually a block of zeros, but it may not be; > > it can also be random trash. Its also not always one block (it could be > > more than one), but it IS always, at least from what I'm seeing here, a > > multiple of 512 bytes (disk blocksize). > > The significant question in light of Garrett's description seem to be > whether the trash that's written is actually being written by the > process in error because that's what it got from a previous read, or > whether the process is actually writing the right stuff and it's being > corrupted on the way down. Its relavent data (its not COMPLETE junk; rather, its pieces of another article), so I would say its probably being written in error from a previous read. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 12:10:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25100 for freebsd-current-outgoing; Sun, 26 Jul 1998 12:10:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25094 for ; Sun, 26 Jul 1998 12:10:47 -0700 (PDT) (envelope-from plm@smtp1.xs4all.nl) Received: from localhost. (dc2-isdn102.dial.xs4all.nl [194.109.148.102]) by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id VAA24295 for ; Sun, 26 Jul 1998 21:10:17 +0200 (CEST) Received: (from plm@localhost) by localhost. (8.8.8/8.8.8) id VAA00396; Sun, 26 Jul 1998 21:10:35 +0200 (MET DST) (envelope-from plm) Newsgroups: comp.unix.bsd.freebsd.misc To: freebsd-current@FreeBSD.ORG Subject: UDMA works very nicely in -current From: Peter Mutsaers Date: 26 Jul 1998 21:00:35 +0200 Message-ID: <87u344e8to.fsf@muon.xs4all.nl> X-Newsreader: Gnus v5.6.24/Emacs 20.2 Posted-To: comp.unix.bsd.freebsd.misc Lines: 34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following message is a courtesy copy of an article that has been posted to comp.unix.bsd.freebsd.misc as well. Hello, I just wanted to report that I'm very pleased with -current. I have a Pentium motherboard with some weird chipset, and still UDMA is working very nicely. Linux 2.0 and 2.1 b.t.w. could not recognize my IDE controller and thus couldn't activate UDMA, which gave a huge negative difference w.r.t. disk I/O performance (measured with bonnie). Heh, often people say that FreeBSD supports less hardware, but sometimes it is vice versa, and FreeBSD supports what I need much better. I always bought SCSI disks (fast SCSI-2, Ultra SCSI is too expensive for my home machine), spending about twice as much as on IDE disks. But now it turns out that UDMA (5400 rpm Maxtor disk) clearly outperforms my fastest (7200 rpm) SCSI disk (Ultra and/or wide SCSI will still win probably), measured again with bonnie. The IDE disk can read 12 MB/s on a filesystem. Amazing, that's faster than even the theoretical limit (10MB/s) for fast-SCSI-2. CPU load (on a 200MMX) only 25% while doing this. FreeBSD's core team is doing great work; alas they get much less attention of the media than they deserve (like the Linux developers get). I just came back from using Redhat Linux (several new and stable kernels) and clearly a FreeBSD feels snappier and is easier to control. -- /\_/\ ( o.o ) Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know ) ^ ( plm@xs4all.nl | the Netherlands | what I'm doing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 12:13:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25366 for freebsd-current-outgoing; Sun, 26 Jul 1998 12:13:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.digital.com (mail1.digital.com [204.123.2.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25361 for ; Sun, 26 Jul 1998 12:13:06 -0700 (PDT) (envelope-from mitch@pa.dec.com) Received: from src-mail-too.pa.dec.com (src-mail-too.pa.dec.com [16.4.0.16]) by mail1.digital.com (8.8.8/8.8.8/WV1.0f) with SMTP id MAA09564 for ; Sun, 26 Jul 1998 12:12:40 -0700 (PDT) Received: by src-mail-too.pa.dec.com; id AA29820; Sun, 26 Jul 98 12:12:39 -0700 Received: by src-exchange.pa.dec.com with Microsoft Exchange (IMC 4.0.837.3) id <01BDB88E.1EC5D3B0@src-exchange.pa.dec.com>; Sun, 26 Jul 1998 12:08:37 -0700 Message-Id: From: Mitch Lichtenberg To: "'current@freebsd.org'" Subject: Hard hangs of -current under heavy load - how to debug? Date: Sun, 26 Jul 1998 12:08:36 -0700 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been experiencing some random hangs on -current releases over the past few months (I'm currently at 3.0-19980723, but I've seen this since last December). The systems operate under heavy load for about 24 hours, then one or two randomly hang. The hangs are hard (no console messages, no dumps/traps, can't escape to the debugger). It looks like interrupts are disabled. Generally, how do you debug a hang like this? Are there any generic techniques or kernel options that I can enable to help me figure this one out? My next step is to hook up a button to the NMI line to see if I can get into DDB that way, but perhaps there's someting easier I can do in the meantime, or maybe there are known problems with my configuration that someone can point out to me. ---- Workload / system description, for those that are interested: I've got a network of ten identical machines. They netboot from a "master" machine (I did a netboot driver for the DEC DC21143 Ethernet chip if anyone's interested). The workload is a distributed storage application I'm working on, which generates a huge amount of UDP traffic and disk I/O. When the tests are running, the net and disk are running flat out, near maximum throughput. The application is basically I/O bound - I seldom see more than 15% CPU utilization. At present, some PCs are servers (lots of disk and net traffic), and some are clients (only net traffic). Both the clients and servers are affected by this problem, so I'm tempted to believe the disk is OK, but servers do crash more often than clients. The "master" machine, identical to the others, has never crashed. Could there be anything screwy about the hardware interrupt mechanism, or known problems with the VIA VP2/97 chipset? (see http://www.research.digital.com/SRC/personal/Ed_Lee/Petal/petal.html if you'd like to know more about the project) Basic configuration: Motherboard: FIC PA-2007 motherboard (VIA VP2/97 chipset (for ECC)), Processor: Cyrix 6x86MX processor Memory: 64MB Disk: Four IBM Deskstar 8.4GB, UltraDMA, all masters (Promise Ultra33 IDE controller for drives 3 and 4) Network: DEC DE500-BA (DC21143) 100Mb/s, connected to a Prominet fast ethernet switch The machines boot via netboot. Thanks! Mitch Lichtenberg COMPAQ Systems Research Center (yes, formerly Digital Equipment Corp.) Palo Alto, CA. mitch@pa.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 12:34:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27531 for freebsd-current-outgoing; Sun, 26 Jul 1998 12:34:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from localhost.my.domain (ppp7254.on.bellglobal.com [206.172.249.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27522 for ; Sun, 26 Jul 1998 12:34:49 -0700 (PDT) (envelope-from ac199@hwcn.org) Received: from localhost (tim@localhost) by localhost.my.domain (8.8.8/8.8.8) with SMTP id PAA28534; Sun, 26 Jul 1998 15:34:29 -0400 (EDT) (envelope-from ac199@hwcn.org) X-Authentication-Warning: localhost.my.domain: tim owned process doing -bs Date: Sun, 26 Jul 1998 15:34:29 -0400 (EDT) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: Adrian Penisoara cc: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= , freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 completely In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Jul 1998, Adrian Penisoara wrote: > Well, this prevents some people like me, who don't have > accounts on the server, to make available to everybody useful > patches & other sort of things.. Stuff uploaded to incoming/ is distilled to outward branches of incoming/ by the incoming/ maintainers. I believe there is a small section in the handbook on policy, which I can't find at all right now, that should suggest how to ensure your upload to incoming/ is handled quickly. I think the email freebsd-maintainers@ftp.cdrom.com will reach the right people, too. If nothing works, email nik@FreeBSD.ORG as a more direct approach. :) -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 13:54:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05398 for freebsd-current-outgoing; Sun, 26 Jul 1998 13:54:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05378; Sun, 26 Jul 1998 13:54:28 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id NAA15723; Sun, 26 Jul 1998 13:53:53 -0700 (MST) From: Terry Lambert Message-Id: <199807262053.NAA15723@usr01.primenet.com> Subject: Re: sysexits To: bde@zeta.org.au (Bruce Evans) Date: Sun, 26 Jul 1998 20:53:52 +0000 (GMT) Cc: current@FreeBSD.ORG, dag-erli@ifi.uio.no, hackers@FreeBSD.ORG In-Reply-To: <199807260206.MAA29472@godzilla.zeta.org.au> from "Bruce Evans" at Jul 26, 98 12:06:52 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What's wrong with errx(1, "[mcre]alloc failed")? The inherent unportability of such code to non-4.4-BSD derived systems, perhaps? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 13:56:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05629 for freebsd-current-outgoing; Sun, 26 Jul 1998 13:56:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05595; Sun, 26 Jul 1998 13:55:59 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id NAA15776; Sun, 26 Jul 1998 13:55:28 -0700 (MST) From: Terry Lambert Message-Id: <199807262055.NAA15776@usr01.primenet.com> Subject: Re: sysexits To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=) Date: Sun, 26 Jul 1998 20:55:27 +0000 (GMT) Cc: wollman@khavrinen.lcs.mit.edu, hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: from "Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=" at Jul 26, 98 11:38:25 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm... I didn't think of Sendmail. What will happen the next time we > upgrade Sendmail (to 8.9.1)? Will somebody remember to merge that > patch into the new version? Or will Sendmail suddenly no longer > understand EX_NOMEM and EX_NOGROUP? It will "just work"... You *did* import sendmail on a vendor branch, right? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 14:07:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07419 for freebsd-current-outgoing; Sun, 26 Jul 1998 14:07:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hoser (root@in221.inetnebr.com [199.184.119.221]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA07400 for ; Sun, 26 Jul 1998 14:07:16 -0700 (PDT) (envelope-from cradek@in221.inetnebr.com) Message-Id: X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: ext2fs and sync panic, still Date: Sun, 26 Jul 1998 16:06:26 -0500 From: Chris Radek Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have run into the problem where mounting an ext2fs r/w panics as soon as sync is called. r/o has no problems. This is from current as of a couple days ago. This panic is due to a null pointer dereference in ext2_sync (ext2_vfsops.c:858) caused by a vnode with a NULL v_data. There is a comment in ext2_vget warning of a blocking MALLOC() that might cause this, but I don't understand the comment. Can someone explain this to me? My first thought was that this was an SMP locking problem, but a uniprocessor kernel gives the same behavior. I could of course skip syncing the vnode if its v_data is NULL but it seems to me like having this bogus vnode in the list signifies a bigger problem. There is some locking code in ext2_vget but I don't understand it. Is it possible that a sync can be called between getnewvnode() and filling in the structure? (Please excuse any questions that might be stupid... I'm new to this!) Does anyone have insight into this problem? Charlie Fluffy (fluffy@int.tele.dk) reported the same thing on June 28th and it doesn't look like anybody has made any progress. Unfortunately I can't get a memory dump from this machine because I am running it diskless. (correct me if this is wrong!) I want to convert it (gently) from Linux and to do this I need to run it diskless and mount my ext2 filesystems. Thanks, Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 14:28:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10565 for freebsd-current-outgoing; Sun, 26 Jul 1998 14:28:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles247.castles.com [208.214.165.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10546 for ; Sun, 26 Jul 1998 14:28:29 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA11981; Sun, 26 Jul 1998 14:27:19 -0700 (PDT) Message-Id: <199807262127.OAA11981@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Karl Denninger cc: Mike Smith , Garrett Wollman , Dan Swartzendruber , current@FreeBSD.ORG Subject: Re: MMAP problems In-reply-to: Your message of "Sun, 26 Jul 1998 13:46:52 CDT." <19980726134652.16525@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 14:27:19 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Jul 26, 1998 at 09:47:54AM -0700, Mike Smith wrote: > > > And I can confirm that the trash IS being written to disk; its definitely > > > there on stable storage when you go look for it later. > > > > > > The data which gets written is usually a block of zeros, but it may not be; > > > it can also be random trash. Its also not always one block (it could be > > > more than one), but it IS always, at least from what I'm seeing here, a > > > multiple of 512 bytes (disk blocksize). > > > > The significant question in light of Garrett's description seem to be > > whether the trash that's written is actually being written by the > > process in error because that's what it got from a previous read, or > > whether the process is actually writing the right stuff and it's being > > corrupted on the way down. > > Its relavent data (its not COMPLETE junk; rather, its pieces of another > article), so I would say its probably being written in error from a previous > read. It would, naturally, be useful to verify this. Can you instrument your application to check the data as they're read? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 14:41:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12888 for freebsd-current-outgoing; Sun, 26 Jul 1998 14:41:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12881 for ; Sun, 26 Jul 1998 14:41:20 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA17295; Sun, 26 Jul 1998 14:40:43 -0700 (MST) From: Terry Lambert Message-Id: <199807262140.OAA17295@usr01.primenet.com> Subject: Re: MMAP problems To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Sun, 26 Jul 1998 21:40:41 +0000 (GMT) Cc: karl@mcs.net, dswartz@druber.com, current@FreeBSD.ORG In-Reply-To: <199807260252.WAA05646@khavrinen.lcs.mit.edu> from "Garrett Wollman" at Jul 25, 98 10:52:34 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've been seeing it for several months. > > I believe it to be a coherency problem. The relevant operations here > are: > > 1) A diablo server process appends to a spool file using explicit > I/O. (Note that the file is not opened in O_APPEND mode.) > > 2) A boatload of dnewslink processes simultaneously mmap the pages of > the spool file containing the article in question, suck the article > out of it, and blast it over to the remote feed. > > Here's my particular guess... I think this happens when the dnewslink > processes are reading another, short, article in the last page of the > file, while a diablo server is writing a new article. Somewhere, > there is a race condition in which the kernel has copied the new data > into the buffer, but blocks before it updates the valid length; this > then allows one of the mmaps to succeed, and since that part of the > buffer is marked invalid, it gets zeroed. Then the diablo process > resumes, and marks the end of the buffer valid, although the data it > was writing has just gotten clobbered. > > It looks, from an inspection of the relevant code in ufs_readwrite.c > and ffs_balloc.c, that this cannot happen, because the data are always > copied in last. It does appear that there are potential windows, if > ffs_balloc() blocks, where other processes might see invalid data in > the file through mmap as a result of vnode_pager_setsize() having > already been run, but it does not appear such garbage could possibly > persist and be written back to disk, and I certainly see it directly > on the disk, not just in memory. I think it is a bit more insidious than this. I have been able to repeat this, reliably, using the dbm mmap() code. What is apparently happening is: 1) Open the password file using an access method that leaves it open. 2) Read some pages. 3) Go to sleep for a time. 4) Run a program from cron every 1 minute. The "newsyslog" program is ideal. 5) Wait for the pages associated with the mapped region to be LRU'ed out. 6) Notice that the pages are invalidated on the descriptor, but not from the mmap(). 7) Insert comment /* here is the bug*/. 8) Now wake up and access the password file data again. The data will be refreshed into the supposedly invalidated page, corrupting the file reusing the page contents. 9) See the data written to your crontab, or any other file that happens to have inherited the physical page backing both the mmap'e region, and, incorrectly, the file being corrupted. So it seems to me that this is an uncounted reference problem specific to the mmap code. The problem does not occur with anonymous memory not backed by a vnode (ie: SYSVSHM), under heavy stress. For the case you describe, if in fact it is a bug in the file extension, then a race window is involved. You can close the race window using explicit calls to msync(). I don't think this is the case, however, but you can try adding the calls to the code and see if they fix the problem. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 14:54:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14480 for freebsd-current-outgoing; Sun, 26 Jul 1998 14:54:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14389 for ; Sun, 26 Jul 1998 14:54:02 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA17869; Sun, 26 Jul 1998 14:53:28 -0700 (MST) From: Terry Lambert Message-Id: <199807262153.OAA17869@usr01.primenet.com> Subject: Re: New LINT options: what is VM coloring? To: green@zone.baldcom.net (Brian Feldman) Date: Sun, 26 Jul 1998 21:53:27 +0000 (GMT) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from "Brian Feldman" at Jul 25, 98 06:11:47 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Would anyone mind letting me in on exactly what "VM coloring" is, and > especially whether or not I should define one of these?: > # Options for the VM subsystem > #options PQ_NOOPT # No coloring > options PQ_LARGECACHE # color for 512k/16k cache > #options PQ_HUGECACHE # color for 1024k/16k cache > As far as I can tell, it would seem these would be options to set certain > parameters to optimal as far as the VM subsystem goes, and if so, is it > safe to use one? ] Page Coloring uses the operating system to control the mapping of ] virtual to physical address by controlling the physical memory page ] which virtual pages are allocated to. Coloring becomes useful when ] the page number is involved in cache indexing, i.e., for large, low ] associativity, first level caches: exactly the trends the industry ] is following. [ ... ] ] For these large physically-indexed caches, the use of the low-order ] bits of the physical page number (the color) in cache indexing ] involve the virtual to physical translation in the location of data ] in the cache. While the virtual address space is laid out very ] uniformly, the lack of control over the virtual-to-physical mapping ] by most operating systems causes the physical color (and therefore ] cache placement modulo the page size) to be ``randomly'' selected. ] Thus, depending on the order in which the physical pages are ] assigned, cache miss rate can vary significantly. See: http://umunhum.stanford.edu/res_html/great92/node13.html#SECTION00031000000000000000 Or click in William L. Lynch's name at: http://umunhum.stanford.edu/res_html/great92/node12.html For the full text of the paper. See also: http://www.pdl.cs.cmu.edu/SDI/todd_mowry.html (abstract) http://www-flash.stanford.edu/~bugnion/CDPC/ (full paper) Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 15:08:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16431 for freebsd-current-outgoing; Sun, 26 Jul 1998 15:08:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16424 for ; Sun, 26 Jul 1998 15:08:09 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id PAA18306; Sun, 26 Jul 1998 15:07:34 -0700 (MST) From: Terry Lambert Message-Id: <199807262207.PAA18306@usr01.primenet.com> Subject: Re: New LINT options: what is VM coloring? To: dyson@iquest.net Date: Sun, 26 Jul 1998 22:07:33 +0000 (GMT) Cc: roberto@keltia.freenix.fr, freebsd-current@FreeBSD.ORG In-Reply-To: <199807261649.LAA01167@dyson.iquest.net> from "John S. Dyson" at Jul 26, 98 11:49:34 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > be a big win for direct-mapped caches (e.g. most Pentium L2 caches), but > > > loses effectiveness with set-associative caches (e.g. Pentium Pro, which > > > has a set size of 4). > > > > The K6 has a 2-way set associative cache so I guess it is not interesting > > to use page coloring but does anyone know what kind of L2 cache an ASUS T2P4 > > use ? It is a P5-class motherboard so it is possible that the cache is > > direct-mapped, no ? > > > David is essentially right. However, the page coloring code (that has > been in -current for the last >1yr) goes a little too far and colors > even the 1st level cache (I know -- I did it.) Also, there is the issue > of proper choice of initial color values, so I used an ad-hoc approach that > appears to work correctly most of the time. Actually, the L1 cache is where it's most important (see paper references in my previous posting). Also, the Alpha can significantly benefit from this, per Digital UNIX: ] The Alpha EV4 CPU contains a direct mapped physical OFF chip secondary ] cache, which is organized so that if the secondary cache size is N ] pages, then every Nth page of the physical pages of memory hashes ] into the same page. Digital UNIX VM manages the physical pages of ] memory in such a way that, if an entire resident working set of a ] process can fit into the secondary cache, VM places it there. As a ] result, because VM strives to ensure that a process's entire working ] set is always in the secondary cache, the number of physical memory ] accesses is greatly reduced as a process executes. Also, for your current project, I recommend: http://www-flash.stanford.edu/OS/oschar.html Specifically, the paper: ] Scheduling and page migration for multiprocessor compute servers ] Rohit Chandra, Scott Devine, Ben Verghese, Anoop Gupta, and Mendel ] Rosenblum In Proceedings of the 6th International Conference on ] Architectural Support for Programming Languages and Operating Systems, ] October 1994 Also: http://www-flash.stanford.edu/OS/hive.html ] Hive: fault containment for shared-memory multiprocessors John Chapin, ] Mendel Rosenblum, Scott Devine, Tirthankar Lahiri, Dan Teodosiu, and ] Anoop Gupta In The 15th ACM Symposium on Operating Systems Principles, ] December 1995 And: ] Implementing efficient fault containment for shared-memory ] multiprocessors Mendel Rosenblum, John Chapin, Dan Teodosiu, Scott ] Devine, Tirthankar Lahiri, and Anoop Gupta To appear in Communications ] of the ACM, September 1996 I also have the IEEE symposium papers book on scheduling and load balancing in parallel and distributed systems; these guys figure prominently in that book as well, and the research is much more recent. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 15:12:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16965 for freebsd-current-outgoing; Sun, 26 Jul 1998 15:12:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16957 for ; Sun, 26 Jul 1998 15:12:31 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id WAA04456; Sun, 26 Jul 1998 22:10:52 GMT Date: Mon, 27 Jul 1998 07:10:52 +0900 (JST) From: Michael Hancock To: Chris Radek cc: freebsd-current@FreeBSD.ORG Subject: Re: ext2fs and sync panic, still In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Have you looked at the ffs version of the source? There aren't too many people working on ext2fs so I would try getting familiar with ffs since it is kept up to date, obviously. Ext2fs is derived from ffs. Regards, Mike Hancock On Sun, 26 Jul 1998, Chris Radek wrote: > > I have run into the problem where mounting an ext2fs r/w panics as > soon as sync is called. r/o has no problems. This is from current > as of a couple days ago. > > This panic is due to a null pointer dereference in ext2_sync > (ext2_vfsops.c:858) caused by a vnode with a NULL v_data. There is a > comment in ext2_vget warning of a blocking MALLOC() that might cause > this, but I don't understand the comment. Can someone explain this > to me? My first thought was that this was an SMP locking problem, > but a uniprocessor kernel gives the same behavior. > > I could of course skip syncing the vnode if its v_data is NULL but it > seems to me like having this bogus vnode in the list signifies a > bigger problem. There is some locking code in ext2_vget but I don't > understand it. Is it possible that a sync can be called between > getnewvnode() and filling in the structure? (Please excuse any > questions that might be stupid... I'm new to this!) > > Does anyone have insight into this problem? Charlie Fluffy > (fluffy@int.tele.dk) reported the same thing on June 28th and it > doesn't look like anybody has made any progress. > > Unfortunately I can't get a memory dump from this machine because I am > running it diskless. (correct me if this is wrong!) I want to > convert it (gently) from Linux and to do this I need to run it diskless > and mount my ext2 filesystems. > > Thanks, > > Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 15:17:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17468 for freebsd-current-outgoing; Sun, 26 Jul 1998 15:17:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17463 for ; Sun, 26 Jul 1998 15:17:03 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id PAA18637; Sun, 26 Jul 1998 15:16:22 -0700 (MST) From: Terry Lambert Message-Id: <199807262216.PAA18637@usr01.primenet.com> Subject: Re: MMAP problems To: green@zone.baldcom.net (Brian Feldman) Date: Sun, 26 Jul 1998 22:16:21 +0000 (GMT) Cc: andre@pipeline.ch, karl@mcs.net, current@FreeBSD.ORG In-Reply-To: from "Brian Feldman" at Jul 25, 98 06:20:19 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm, what is the default behavior of msync()? Is it handled automatically, > say, in-kernel? If so, maybe it needs to be explicitly called; also is > this daemon using a drive with async/softupdates by any chance? It is supposed to be automatic in the case of a unified VM and buffer cache, by definition. The one place that this is not true is non-fault based file extension, ie: when you extend a file within the last page of the file, while the file is memory mapped. Probably the correct thing to do in this case is to think of backing objects in terms of pages instead of thinking of them in terms of variable length anonymous memory. This would mean that you would grab a full page *and note that you had done so* to back frags in an mmap'ed region. Then if an extension occurs, the changes are made to the page as a page instead of as a frag, and coherency is maintained. The final issue is that when you write fault in the partial page, you look at the backing object to determine the length so that you don't fault zero-filled partial objects out, ending up with your last 0-7 physical blocks getting zeroed. This is more an issue of whether or not the additional overhead is worth avoiding the msync() or not... It is interesting to note that incoherent VM systems (ie: non-unified VM and buffer cache 8-)) do not have this problem. By definition, they will copy only the data from the region into the buffer cache from teh VM. This will result in "correct" (user expected) behaviour on file extension, without needing msync(). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 15:21:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18077 for freebsd-current-outgoing; Sun, 26 Jul 1998 15:21:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18071 for ; Sun, 26 Jul 1998 15:20:59 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id PAA18776; Sun, 26 Jul 1998 15:20:27 -0700 (MST) From: Terry Lambert Message-Id: <199807262220.PAA18776@usr01.primenet.com> Subject: Re: MMAP problems To: karl@mcs.net (Karl Denninger) Date: Sun, 26 Jul 1998 22:20:26 +0000 (GMT) Cc: green@zone.baldcom.net, andre@pipeline.ch, current@FreeBSD.ORG In-Reply-To: <19980725204141.39635@mcs.net> from "Karl Denninger" at Jul 25, 98 08:41:41 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Msync is *NOT* called anywhere in the code that I can find. However, this > code is reported to work on a lot of other platforms/systems, and on *SOME* > versions of FreeBSD without trouble. > > It is definitely broken on -current, although not "badly"; the problem > happens infrequently, but often enough to piss me off. The real problem is > that I don't know what the bad sequence of calls is, and therefore, I have > to consider mmap() and friends (including the SYSVSHM implementation, which > uses it) unusable. > > This is a *bad* thing over all, and something that the FreeBSD folks really > need to consider doing something about - not having usable and reliable > mmap/SHM capability basically destroys FreeBSD as a DBMS or news server > if you care about minor things like data integrity. If you are extending an mmap'ed file, then you are expected to call msync(). Period. This can be "fixed" in the FreeBSD VM code if there is a page attribute bit available to do the job. There are situations on non-unified VM and buffer caches, where if you don't merely extend, but you change existing data, that the non-UVM systems will fail to update the VM image of the buffer cache contents, *unless* you call msync(). Basically, any time you are accessing a file via system calls for I/O and read/write faults for I/O at the same time, expect to face race conditions requiring the use of msync(). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 15:29:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19291 for freebsd-current-outgoing; Sun, 26 Jul 1998 15:29:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19273 for ; Sun, 26 Jul 1998 15:28:53 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id PAA18917; Sun, 26 Jul 1998 15:28:09 -0700 (MST) From: Terry Lambert Message-Id: <199807262228.PAA18917@usr01.primenet.com> Subject: Re: MMAP problems To: mike@smith.net.au (Mike Smith) Date: Sun, 26 Jul 1998 22:28:08 +0000 (GMT) Cc: karl@mcs.net, wollman@khavrinen.lcs.mit.edu, dswartz@druber.com, current@FreeBSD.ORG In-Reply-To: <199807261647.JAA10667@antipodes.cdrom.com> from "Mike Smith" at Jul 26, 98 09:47:54 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The data which gets written is usually a block of zeros, but it may not be; > > it can also be random trash. Its also not always one block (it could be > > more than one), but it IS always, at least from what I'm seeing here, a > > multiple of 512 bytes (disk blocksize). > > The significant question in light of Garrett's description seem to be > whether the trash that's written is actually being written by the > process in error because that's what it got from a previous read, or > whether the process is actually writing the right stuff and it's being > corrupted on the way down. See other postings. Because the corrupt data can be non-zero, I do not believe Garrett's explanation is the correct one; instead, I believe the same page is being pointed to by two mappings at the same time because I don't believe that mmap() references are being revoked correctly. If the data were always zero, then Garret would be discussing the correct problem. The problem Garrett notes is, IMO, "pilot error" and has to do with the failure to call msync() when it is necessary. Per the discussion, it can be made possible to not need to call msync(). Note that I have seen the bug I am describing on both 2.2.6 and 3.0 systems. These are production systems that open and hild open the password file a long time, and which access the crontabe with an annoyingly (and probably undesirably) high frequency. This results in corrupt crontabs. On the other hand, corrupt crontabs are much better than silently corrupted user data... 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 16:04:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24147 for freebsd-current-outgoing; Sun, 26 Jul 1998 16:04:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24141 for ; Sun, 26 Jul 1998 16:04:20 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id SAA01355; Sun, 26 Jul 1998 18:03:50 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id SAA14631; Sun, 26 Jul 1998 18:03:50 -0500 (CDT) Message-ID: <19980726180350.54337@mcs.net> Date: Sun, 26 Jul 1998 18:03:50 -0500 From: Karl Denninger To: Terry Lambert Cc: green@zone.baldcom.net, andre@pipeline.ch, current@FreeBSD.ORG Subject: Re: MMAP problems References: <19980725204141.39635@mcs.net> <199807262220.PAA18776@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807262220.PAA18776@usr01.primenet.com>; from Terry Lambert on Sun, Jul 26, 1998 at 10:20:26PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 26, 1998 at 10:20:26PM +0000, Terry Lambert wrote: > > Msync is *NOT* called anywhere in the code that I can find. However, this > > code is reported to work on a lot of other platforms/systems, and on *SOME* > > versions of FreeBSD without trouble. > > > > It is definitely broken on -current, although not "badly"; the problem > > happens infrequently, but often enough to piss me off. The real problem is > > that I don't know what the bad sequence of calls is, and therefore, I have > > to consider mmap() and friends (including the SYSVSHM implementation, which > > uses it) unusable. > > > > This is a *bad* thing over all, and something that the FreeBSD folks really > > need to consider doing something about - not having usable and reliable > > mmap/SHM capability basically destroys FreeBSD as a DBMS or news server > > if you care about minor things like data integrity. > > If you are extending an mmap'ed file, then you are expected to call > msync(). Period. Uh, hang on a second. The way Diablo works it extends the file using write(2). It MMAPs for READ access in the dnewslink program (among other places). The comments in the config file claim it needs no msync() as a consequence of this behavior. This is intuitively correct, but may be functionally (for FreeBSD) wrong. > Basically, any time you are accessing a file via system calls for I/O > and read/write faults for I/O at the same time, expect to face race > conditions requiring the use of msync(). -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 16:16:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA25272 for freebsd-current-outgoing; Sun, 26 Jul 1998 16:16:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA25263 for ; Sun, 26 Jul 1998 16:16:31 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id SAA01589; Sun, 26 Jul 1998 18:15:56 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id SAA14765; Sun, 26 Jul 1998 18:15:55 -0500 (CDT) Message-ID: <19980726181555.49644@mcs.net> Date: Sun, 26 Jul 1998 18:15:55 -0500 From: Karl Denninger To: Terry Lambert Cc: Mike Smith , wollman@khavrinen.lcs.mit.edu, dswartz@druber.com, current@FreeBSD.ORG, dillon@best.net Subject: Re: MMAP problems References: <199807261647.JAA10667@antipodes.cdrom.com> <199807262228.PAA18917@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807262228.PAA18917@usr01.primenet.com>; from Terry Lambert on Sun, Jul 26, 1998 at 10:28:08PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 26, 1998 at 10:28:08PM +0000, Terry Lambert wrote: > > > The data which gets written is usually a block of zeros, but it may not be; > > > it can also be random trash. Its also not always one block (it could be > > > more than one), but it IS always, at least from what I'm seeing here, a > > > multiple of 512 bytes (disk blocksize). > > > > The significant question in light of Garrett's description seem to be > > whether the trash that's written is actually being written by the > > process in error because that's what it got from a previous read, or > > whether the process is actually writing the right stuff and it's being > > corrupted on the way down. > > See other postings. > > Because the corrupt data can be non-zero, I do not believe Garrett's > explanation is the correct one; instead, I believe the same page is > being pointed to by two mappings at the same time because I don't > believe that mmap() references are being revoked correctly. Hmmm... Yes, I can confirm (for certain) that the corrupt data is not always zero. It FREQUENTLY is zero, but not always. If it is non-zero it generally is identifyable as a chunk of another message (unfortunately I haven't gotten a HEADER yet; if I do, I will be able to track down where the chunk of data actually came from). > Note that I have seen the bug I am describing on both 2.2.6 and 3.0 > systems. These are production systems that open and hild open the > password file a long time, and which access the crontabe with an > annoyingly (and probably undesirably) high frequency. This results > in corrupt crontabs. On the other hand, corrupt crontabs are much > better than silently corrupted user data... 8-(. This is particularly bad, since one of the potential "fixes" Matt has given me is to back down to 2.2.6. Of course, if this problem is IN 2.2.6, then backing down on that machine will do a big nothing. I suspect the real culprit is that I'm running basically all my feeds in "realtime" mode - if I was delaying by 10 minutes, diablo would never be writing to the same file that the feeder program was reading at a given time (ie: the file that was open for MMAP would never be open for write at the same time). I *can* confirm that the files where the corruption is being seen absolutely ARE open for write when the errors occur; I've managed to catch the system "in the act" doing this, and have found the file open at the time. I'm going to put a "q1" flag on all the feeds (which should effectively force the system to not "chase its tail" so effectively) and see if the problem goes away. Doing that should prevent the software from attempting to read via mmap in the last-written (by write(2)) page. If you're right then this should make the problem disappear. Then the question becomes how to fix it. - -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 16:50:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28325 for freebsd-current-outgoing; Sun, 26 Jul 1998 16:50:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28318 for ; Sun, 26 Jul 1998 16:50:23 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id SAA05217; Sun, 26 Jul 1998 18:49:39 -0500 (EST) (envelope-from toor) Message-Id: <199807262349.SAA05217@dyson.iquest.net> Subject: Re: New LINT options: what is VM coloring? In-Reply-To: <199807262207.PAA18306@usr01.primenet.com> from Terry Lambert at "Jul 26, 98 10:07:33 pm" To: tlambert@primenet.com (Terry Lambert) Date: Sun, 26 Jul 1998 18:49:38 -0500 (EST) Cc: dyson@iquest.net, roberto@keltia.freenix.fr, freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert said: > > > > be a big win for direct-mapped caches (e.g. most Pentium L2 caches), but > > > > loses effectiveness with set-associative caches (e.g. Pentium Pro, which > > > > has a set size of 4). > > > > > > The K6 has a 2-way set associative cache so I guess it is not interesting > > > to use page coloring but does anyone know what kind of L2 cache an ASUS T2P4 > > > use ? It is a P5-class motherboard so it is possible that the cache is > > > direct-mapped, no ? > > > > > David is essentially right. However, the page coloring code (that has > > been in -current for the last >1yr) goes a little too far and colors > > even the 1st level cache (I know -- I did it.) Also, there is the issue > > of proper choice of initial color values, so I used an ad-hoc approach that > > appears to work correctly most of the time. > > Actually, the L1 cache is where it's most important (see paper references > in my previous posting). Also, the Alpha can significantly benefit from > this, per Digital UNIX: > Is the L1 cache on the Alpha is direct mapped??? On the X86, it isn't. When actually running tests, it doesn't seem to make ANY differences on the X86, due to the very small number of pages, and the mapping scheme. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 17:08:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01008 for freebsd-current-outgoing; Sun, 26 Jul 1998 17:08:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles319.castles.com [208.214.167.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00999 for ; Sun, 26 Jul 1998 17:08:30 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA12744; Sun, 26 Jul 1998 17:07:09 -0700 (PDT) Message-Id: <199807270007.RAA12744@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), karl@mcs.net, wollman@khavrinen.lcs.mit.edu, dswartz@druber.com, current@FreeBSD.ORG Subject: Re: MMAP problems In-reply-to: Your message of "Sun, 26 Jul 1998 22:28:08 -0000." <199807262228.PAA18917@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 17:07:08 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The problem Garrett notes is, IMO, "pilot error" and has to do with > the failure to call msync() when it is necessary. Per the discussion, > it can be made possible to not need to call msync(). > Subsequent to your dissertation, do you have any suggested fixes? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 17:13:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01815 for freebsd-current-outgoing; Sun, 26 Jul 1998 17:13:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hoser (root@in221.inetnebr.com [199.184.119.221]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA01796 for ; Sun, 26 Jul 1998 17:13:01 -0700 (PDT) (envelope-from cradek@in221.inetnebr.com) Message-Id: X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Cc: fluffy@int.tele.dk Subject: Re: ext2fs and sync panic, still In-reply-to: Your message of "Sun, 26 Jul 1998 16:06:26 CDT." Date: Sun, 26 Jul 1998 19:12:31 -0500 From: Chris Radek Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Jul 1998 16:06:26 CDT, Chris Radek writes: > I have run into the problem where mounting an ext2fs r/w panics as > soon as sync is called. r/o has no problems. This is from current > as of a couple days ago. Is it sane to reply to yourself? I hope so. The problem is that ext2_sync is trying to sync vnodes of type VNON (which have no associated inode and hence NULL v_data). The following patch fixes the panic: % diff -u ext2_vfsops.c.orig ext2_vfsops.c --- ext2_vfsops.c.orig Sun Jul 26 19:48:29 1998 +++ ext2_vfsops.c Sun Jul 26 20:14:15 1998 @@ -854,6 +854,8 @@ goto loop; if (VOP_ISLOCKED(vp)) continue; + if (vp->v_type == VNON) + continue; ip = VTOI(vp); if ((ip->i_flag & (IN_ACCESS | IN_CHANGE | IN_MODIFIED | IN_UPDATE)) == 0 && To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 17:17:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02544 for freebsd-current-outgoing; Sun, 26 Jul 1998 17:17:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02520 for ; Sun, 26 Jul 1998 17:17:03 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id TAA03085; Sun, 26 Jul 1998 19:16:21 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id TAA16518; Sun, 26 Jul 1998 19:16:21 -0500 (CDT) Message-ID: <19980726191621.59383@mcs.net> Date: Sun, 26 Jul 1998 19:16:21 -0500 From: Karl Denninger To: Terry Lambert Cc: Mike Smith , wollman@khavrinen.lcs.mit.edu, dswartz@druber.com, current@FreeBSD.ORG, dillon@best.net Subject: Re: MMAP problems References: <199807261647.JAA10667@antipodes.cdrom.com> <199807262228.PAA18917@usr01.primenet.com> <19980726181555.49644@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19980726181555.49644@mcs.net>; from Karl Denninger on Sun, Jul 26, 1998 at 06:15:55PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 26, 1998 at 06:15:55PM -0500, Karl Denninger wrote: > On Sun, Jul 26, 1998 at 10:28:08PM +0000, Terry Lambert wrote: > > See other postings. > > > > Because the corrupt data can be non-zero, I do not believe Garrett's > > explanation is the correct one; instead, I believe the same page is > > being pointed to by two mappings at the same time because I don't > > believe that mmap() references are being revoked correctly. > > Hmmm... > > Yes, I can confirm (for certain) that the corrupt data is not always zero. > It FREQUENTLY is zero, but not always. If it is non-zero it generally is > identifyable as a chunk of another message (unfortunately I haven't gotten > a HEADER yet; if I do, I will be able to track down where the chunk of data > actually came from). I saw Matt's posting on this. The corrupt data is USUALLY zero. HOWEVER it is not ALWAYS zero. Sometimes it is another random set of data, and so far that has always been identifyable as a piece of another message. > I suspect the real culprit is that I'm running basically all my feeds in > "realtime" mode - if I was delaying by 10 minutes, diablo would never be > writing to the same file that the feeder program was reading at a given time > (ie: the file that was open for MMAP would never be open for write at the > same time). > > I *can* confirm that the files where the corruption is being seen absolutely > ARE open for write when the errors occur; I've managed to catch the system > "in the act" doing this, and have found the file open at the time. > > I'm going to put a "q1" flag on all the feeds (which should effectively > force the system to not "chase its tail" so effectively) and see if the > problem goes away. Doing that should prevent the software from attempting > to read via mmap in the last-written (by write(2)) page. > > If you're right then this should make the problem disappear. Adding "q1" to all the feeds has basically stopped the complaints and corruption. Now the question is how to fix it so that I can run with realtime enabled :-) -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 17:43:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07460 for freebsd-current-outgoing; Sun, 26 Jul 1998 17:43:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07419 for ; Sun, 26 Jul 1998 17:43:01 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id TAA03549; Sun, 26 Jul 1998 19:42:29 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id TAA16684; Sun, 26 Jul 1998 19:42:29 -0500 (CDT) Message-ID: <19980726194229.43215@mcs.net> Date: Sun, 26 Jul 1998 19:42:29 -0500 From: Karl Denninger To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Diablo corruption on the filesystem References: <199807270026.RAA09393@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807270026.RAA09393@apollo.backplane.com>; from Matthew Dillon on Sun, Jul 26, 1998 at 05:26:11PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 26, 1998 at 05:26:11PM -0700, Matthew Dillon wrote: > :Something funny is going on here. > : > :Removing the realtime, but NOT putting a Q1 on the feeds did NOT fix it. > :Specifically, IMMEDIATELY on startup of a new set of dnewslink processes > :I'd get a whole batch of errors on files that were still open for write in > :the diablo processes at the time. > : > :The q1 seems to prevent that from happening (diablo has moved on to a new > :file before dnewslink starts up against the old queue files). > : > :-- > :-- > :Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin > :http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV > > .... or the q1 is resulting in a long enough delay that Diablo's write > position is well beyond the point where dnewslink picks up the files, > and so is (potentially) beyond the point where a last-block-is-fragment > problem would mess up mmap(). That's not the whole problem. > It sure sounds to me like a mmap()/file-fragment-block-allocation > inconsistancy that occurs near the 'end' of the file when one process has > the end-portion of the file mmap'd shared+ro and another is actively > appending to the file. Check THIS out. I turned off USE_PCOMMIT_SHM, USE_PCOMMIT_RW_MAP, USE_KP_RW_MAP and DO_COMMIT_POSTCACHE and recompiled diablo (but did NOT reinstall dnewslink, if that matters). This should shut down as much of the MMAPping as I can in diablo itself. Now, with q1 set on the feeds, the problem appears to be completely GONE! With those options ON, the error rate decreased but there was still corruption happening. Now there is not. I tried the recompile last night with REALTIME still enabled on a hunch, and while that cut the error rate down, I was still getting errors - so I assumed that whatever I had done with the options had been ineffective and I was seeing instead an artifact of lower-than-normal news rates (since its the weekend). However, with the options off and Q1 set, I'm not getting any errors (20 minutes now with no errors logged). Something significant happend when I changed the behavior of diablo internally. Does this shed any light on the issue? What have I actually done in terms of the calls made to the mmap routines by disabling these options? If it runs error-free for an hour or so I'm going to try removing the q1 and see if the problem reappears (leaving the modified diablo program in service). -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 18:03:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10737 for freebsd-current-outgoing; Sun, 26 Jul 1998 18:03:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10716 for ; Sun, 26 Jul 1998 18:03:43 -0700 (PDT) (envelope-from dillon@backplane.com) Received: (dillon@localhost) by apollo.backplane.com (8.8.8/8.6.5) id SAA09631; Sun, 26 Jul 1998 18:03:13 -0700 (PDT) Date: Sun, 26 Jul 1998 18:03:13 -0700 (PDT) From: Matthew Dillon Message-Id: <199807270103.SAA09631@apollo.backplane.com> To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: Diablo corruption on the filesystem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I turned off USE_PCOMMIT_SHM, USE_PCOMMIT_RW_MAP, USE_KP_RW_MAP and :DO_COMMIT_POSTCACHE and recompiled diablo (but did NOT reinstall dnewslink, :if that matters). I assume you mean DO_PCOMMIT_POSTCACHE here, not DO_COMMIT_POSTCACHE. :Something significant happend when I changed the behavior of diablo :internally. : :Does this shed any light on the issue? What have I actually done in terms :of the calls made to the mmap routines by disabling these options? Hmmm. If DO_PCOMMIT_POSTCACHE is turned off the stress on the history file will increase, but that's about it. It could also have a slight serialization effect on multiple feeders that are nearly-in-sync due to history file locking. *PCOMMIT_SHM & RW_MAP should not have any effect at all. -Matt :-- :-- :Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin :http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV : | NEW! Corporate ISDN Prices dropped by up to 50%! :Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS :Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 18:06:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11035 for freebsd-current-outgoing; Sun, 26 Jul 1998 18:06:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10993 for ; Sun, 26 Jul 1998 18:05:45 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id UAA04177; Sun, 26 Jul 1998 20:05:12 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id UAA16934; Sun, 26 Jul 1998 20:05:12 -0500 (CDT) Message-ID: <19980726200512.02119@mcs.net> Date: Sun, 26 Jul 1998 20:05:12 -0500 From: Karl Denninger To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: Diablo corruption on the filesystem References: <199807270103.SAA09631@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807270103.SAA09631@apollo.backplane.com>; from Matthew Dillon on Sun, Jul 26, 1998 at 06:03:13PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 26, 1998 at 06:03:13PM -0700, Matthew Dillon wrote: > :I turned off USE_PCOMMIT_SHM, USE_PCOMMIT_RW_MAP, USE_KP_RW_MAP and > :DO_COMMIT_POSTCACHE and recompiled diablo (but did NOT reinstall dnewslink, > :if that matters). > > I assume you mean DO_PCOMMIT_POSTCACHE here, not DO_COMMIT_POSTCACHE. Yes. > :Something significant happend when I changed the behavior of diablo > :internally. > : > :Does this shed any light on the issue? What have I actually done in terms > :of the calls made to the mmap routines by disabling these options? > > Hmmm. If DO_PCOMMIT_POSTCACHE is turned off the stress on the > history file will increase, but that's about it. It could also > have a slight serialization effect on multiple feeders that > are nearly-in-sync due to history file locking. > > *PCOMMIT_SHM & RW_MAP should not have any effect at all. Hmmm.... well, with those off and "q1" set I see no corruption. Remove the q1, and it *immediately* shows up again. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 21:14:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04204 for freebsd-current-outgoing; Sun, 26 Jul 1998 21:14:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04184 for ; Sun, 26 Jul 1998 21:14:35 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA08697; Mon, 27 Jul 1998 14:14:04 +1000 Date: Mon, 27 Jul 1998 14:14:04 +1000 From: Bruce Evans Message-Id: <199807270414.OAA08697@godzilla.zeta.org.au> To: current@FreeBSD.ORG, mitch@pa.dec.com Subject: Re: Hard hangs of -current under heavy load - how to debug? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I've been experiencing some random hangs on -current >releases over the past few months (I'm currently at >3.0-19980723, but I've seen this since last December). >The systems operate under heavy load for about 24 hours, >then one or two randomly hang. The hangs are hard (no >console messages, no dumps/traps, can't escape to >the debugger). It looks like interrupts are disabled. I just fixed a hang with most interrupts disabled in the swap pager. An spl nesting botch caused the entire pageout daemon to run at splvm() after the first pageout. This bug dates from 23 Feb. Now the hang occurs without interrupts disabled :-). There is a near deadlock if swap fills up during core dumping of a huge (mostly swapped out) process (an 87MB core dump would have taken a day or two to complete). >Generally, how do you debug a hang like this? Are there I removed the tty mask bit from splhigh() and other places so that the keyboard debugger hotkey worked. The BREAK_TO_DEBUGGER option should allow the serial console debugger entry (break) to work in even more cases. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 21:33:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06186 for freebsd-current-outgoing; Sun, 26 Jul 1998 21:33:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06179 for ; Sun, 26 Jul 1998 21:33:09 -0700 (PDT) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id OAA11869; Mon, 27 Jul 1998 14:02:08 +0930 (CST) Received: from eddie.dsto.defence.gov.au ([131.185.2.111]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id PMP5WHZB; Mon, 27 Jul 1998 14:02:22 +0930 Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id OAA00766; Mon, 27 Jul 1998 14:02:23 +0930 (CST) Message-ID: <35BC02D5.574F9516@dsto.defence.gov.au> Date: Mon, 27 Jul 1998 14:02:21 +0930 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Julian Elischer CC: Eivind Eklund , FreeBSD CURRENT Subject: Re: DEVFS not creating slice devices for my SCSI disks References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The patch that Julian sent me has fixed the problem. I hope it will be committed soon (I hate running separate sources). Evind: By the way I did edit my disklabels to put 'SCSI' in place of 'unknown' for the disk type but that didn't fix the problem so I applied the patch and that fixed it. So I'm back to running with DEVFS and SLICE in my kernel. eddie: {8} disklabel -r sd1 # /dev/rsd1: type: SCSI By the way: Why do I have to specify 'sd1a' when I read the label from the kernel copy i.e. 'disklabel sd1a' while 'disklabel -r sd1' works ? Julian Elischer wrote: > > ok, try this: > the fix is the removal of the EINVAL line around line 200 of mbr.c > (I think) > > julian > > ------------------------------------------------------------------------------ > > Name: xx > xx Type: Plain Text (TEXT/PLAIN) > Encoding: BASE64 -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 21:45:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07576 for freebsd-current-outgoing; Sun, 26 Jul 1998 21:45:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07537 for ; Sun, 26 Jul 1998 21:44:55 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA10989; Mon, 27 Jul 1998 14:44:19 +1000 Date: Mon, 27 Jul 1998 14:44:19 +1000 From: Bruce Evans Message-Id: <199807270444.OAA10989@godzilla.zeta.org.au> To: cradek@in221.inetnebr.com, freebsd-current@FreeBSD.ORG Subject: Re: ext2fs and sync panic, still Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I have run into the problem where mounting an ext2fs r/w panics as >soon as sync is called. r/o has no problems. This is from current >as of a couple days ago. > >This panic is due to a null pointer dereference in ext2_sync >(ext2_vfsops.c:858) caused by a vnode with a NULL v_data. There is a This is because ext2fs hasn't been updated to work with the softupdates syncer daemon. >comment in ext2_vget warning of a blocking MALLOC() that might cause >this, but I don't understand the comment. Can someone explain this >to me? My first thought was that this was an SMP locking problem, >but a uniprocessor kernel gives the same behavior. This is unrelated. There is a race that only occurs every billionth (or thereabouts) call to getnewvnode(). >Unfortunately I can't get a memory dump from this machine because I am >running it diskless. (correct me if this is wrong!) I want to >convert it (gently) from Linux and to do this I need to run it diskless >and mount my ext2 filesystems. I wouldn't trust ext2fs except for read-only mounts, especially for this. It is possible to share the swap partition and then easy to dump to it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 22:02:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10187 for freebsd-current-outgoing; Sun, 26 Jul 1998 22:02:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.baldcom.net (green@zone.BALDCOM.NET [205.232.46.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10178 for ; Sun, 26 Jul 1998 22:02:40 -0700 (PDT) (envelope-from green@zone.baldcom.net) Received: from localhost (green@localhost) by zone.baldcom.net (8.8.8/8.8.7) with SMTP id BAA06574; Mon, 27 Jul 1998 01:02:03 -0400 (EDT) Date: Mon, 27 Jul 1998 01:02:03 -0400 (EDT) From: Brian Feldman To: Jonathan Lemon cc: freebsd-current@FreeBSD.ORG Subject: Re: More doscmd adventures/lockups In-Reply-To: <19980723150547.60718@right.PCS> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alright, I've tested this a lot, and it fixes the lockups. Why don't you commit it? It might be a gross workaround, but it does the Right Thing. Cheers, Brian Feldman green@unixhelp.org On Thu, 23 Jul 1998, Jonathan Lemon wrote: > On Jul 07, 1998 at 02:14:41PM -0400, Brian Feldman wrote: > > Yessiree, doscmd has ways of locking me up without a panic. I'll explore > > what happened this time: I was using my 5[0-2][0-8]mb dos drive in bochs, > > installing MS-DOS 6.22. I tried using doscmd to boot it, doscmd -bx... > > after Starting msdos... the whole computer froze, I waited a few minutes, > > and hit reset when I was sure it was locked up solid. To recap: bochs was > > loading dos on the drive, on disk 2 by now, and doscmd -bx tried to boot > > the drive; this was standard access, no vn(4) problems. > > Sigh. I've spent the last few weeks trying to track this down, but > to no avail. It doesn't _appear_ to be a doscmd specific bug, but > rather a problem with the cpl settings. > > What I'm seeing here is that when the kernel enters vm86 mode, it > has cpl == 0, which is all well and good. When an interrupt occurs, > and the kernel is entered via one of the INTR() entry points, it > seems that cpl != 0. > > I don't know how this is possible, but that is what I seem to be > observing. This cpl is then restored in _doreti right before > returning to either user mode, or vm86 mode, which means that we > are running in non-kernel mode with AST's blocked. > > Attached is a gross workaround for the problem that fixes it on my > box. Let me know if it also fixes the lockups that you are having. > -- > Jonathan > > > Index: ipl.s > =================================================================== > RCS file: /tuna/ncvs/src/sys/i386/isa/ipl.s,v > retrieving revision 1.21 > diff -u -r1.21 ipl.s > --- ipl.s 1998/03/23 19:52:59 1.21 > +++ ipl.s 1998/07/23 19:55:53 > @@ -169,9 +169,11 @@ > * When the cpl problem is solved, this code can disappear. > */ > ICPL_LOCK > - cmpl $0,_cpl > + cmpl $0,_cpl /* cpl == 0, skip it */ > je 1f > - testl $PSL_VM,TF_EFLAGS(%esp) > + testl $PSL_VM,TF_EFLAGS(%esp) /* going to VM86 mode? */ > + jne doreti_stop > + testb $SEL_RPL_MASK,TRAPF_CS_OFF(%esp) /* to user mode? */ > je 1f > doreti_stop: > movl $0,_cpl > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 23:06:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16203 for freebsd-current-outgoing; Sun, 26 Jul 1998 23:06:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles319.castles.com [208.214.167.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16198; Sun, 26 Jul 1998 23:06:00 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA14756; Sun, 26 Jul 1998 23:04:54 -0700 (PDT) Message-Id: <199807270604.XAA14756@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: winter@jurai.net (Matthew N. Dodd), hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: temporary FreeBSD token-ring list. In-reply-to: Your message of "Thu, 16 Apr 1998 06:25:16 -0000." <199804160625.XAA13265@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 23:04:53 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > freebsd-tokenring@jurai.net is up and running as a temporary mailing list > > for the ongoing discussion of the efforts to add Token Ring and 802.2 LLC > > support to FreeBSD > > > > As there are a number of non-token ring issues that we will have to solve > > before working on any token-ring specific issues, I invite everyone who > > has an interest in making the network subsystem a bit less ethernet > > centric in the places that it is, and those who have interest in > > supporting Novell 802.3 IPX and NetBEUI. The 802.2 LLC is common to all > > of these. > > As a point of interest, MITRE announced a working NetBEUI for > FreeBSD a number of moths ago on the SAMBA list. > > To do this, they must have implemented the 802.3 LLC. > > Someone should follow up with MITRE. Did they? This would be extremely useful. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 26 23:34:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18547 for freebsd-current-outgoing; Sun, 26 Jul 1998 23:34:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA18542; Sun, 26 Jul 1998 23:34:22 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id IAA27175; Mon, 27 Jul 1998 08:33:50 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Mon, 27 Jul 1998 08:33:49 +0200 (MET DST) Mime-Version: 1.0 To: Terry Lambert Cc: wollman@khavrinen.lcs.mit.edu, hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysexits References: <199807262055.NAA15776@usr01.primenet.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 27 Jul 1998 08:33:48 +0200 In-Reply-To: Terry Lambert's message of "Sun, 26 Jul 1998 20:55:27 +0000 (GMT)" Message-ID: Lines: 8 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA18543 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert writes: > You *did* import sendmail on a vendor branch, right? Who, me? Never touched the thing. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 01:39:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01194 for freebsd-current-outgoing; Mon, 27 Jul 1998 01:39:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01187 for ; Mon, 27 Jul 1998 01:39:26 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id BAA24899; Mon, 27 Jul 1998 01:38:55 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd024890; Mon Jul 27 01:38:52 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id BAA22756; Mon, 27 Jul 1998 01:38:47 -0700 (MST) From: Terry Lambert Message-Id: <199807270838.BAA22756@usr08.primenet.com> Subject: Re: New LINT options: what is VM coloring? To: dyson@iquest.net Date: Mon, 27 Jul 1998 08:38:47 +0000 (GMT) Cc: tlambert@primenet.com, roberto@keltia.freenix.fr, freebsd-current@FreeBSD.ORG In-Reply-To: <199807262349.SAA05217@dyson.iquest.net> from "John S. Dyson" at Jul 26, 98 06:49:38 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Actually, the L1 cache is where it's most important (see paper references > > in my previous posting). Also, the Alpha can significantly benefit from > > this, per Digital UNIX: > > > Is the L1 cache on the Alpha is direct mapped??? On the X86, it isn't. When > actually running tests, it doesn't seem to make ANY differences on the X86, > due to the very small number of pages, and the mapping scheme. I'm just quoting the literature, but it seems the answer to your question is "yes". For SMP, the answer is to make the compiler do it (obviously), and to eat the overhead, as necessary. I think that when the compiler does it, the code is never invoked by the process runtime. This is more an issue of CPU affinity, however, and could be argued either way... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 01:51:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03324 for freebsd-current-outgoing; Mon, 27 Jul 1998 01:51:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03319 for ; Mon, 27 Jul 1998 01:51:18 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id JAA00188; Mon, 27 Jul 1998 09:51:47 +0100 (BST) Date: Mon, 27 Jul 1998 09:51:47 +0100 (BST) From: Doug Rabson To: "John S. Dyson" cc: Terry Lambert , roberto@keltia.freenix.fr, freebsd-current@FreeBSD.ORG Subject: Re: New LINT options: what is VM coloring? In-Reply-To: <199807262349.SAA05217@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Jul 1998, John S. Dyson wrote: > > Actually, the L1 cache is where it's most important (see paper references > > in my previous posting). Also, the Alpha can significantly benefit from > > this, per Digital UNIX: > > > Is the L1 cache on the Alpha is direct mapped??? On the X86, it isn't. When > actually running tests, it doesn't seem to make ANY differences on the X86, > due to the very small number of pages, and the mapping scheme. I'm not too sure what the layout of the alpha caches are. I expect they are different on different processor generations. I really must start reading the processor manuals for these things... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 06:27:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16354 for freebsd-current-outgoing; Mon, 27 Jul 1998 06:27:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from itesec.hsc.fr (root@itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16276 for ; Mon, 27 Jul 1998 06:27:45 -0700 (PDT) (envelope-from pb@hsc.fr) Received: from mars.hsc.fr (mars.hsc.fr [192.70.106.44]) by itesec.hsc.fr (8.8.8/8.8.5/itesec-1.12-nospam) with ESMTP id PAA03816; Mon, 27 Jul 1998 15:27:05 +0200 (MET DST) Received: (from pb@localhost) by mars.hsc.fr (8.8.8/8.8.8/pb-19980526) id PAA24349; Mon, 27 Jul 1998 15:26:59 +0200 (CEST) (envelope-from pb) Message-ID: <19980727152658.A24276@mars.hsc.fr> Date: Mon, 27 Jul 1998 15:26:58 +0200 From: Pierre Beyssac To: Karl Denninger , current@FreeBSD.ORG Subject: Re: MMAP problems References: <19980725155148.43084@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: <19980725155148.43084@mcs.net>; from Karl Denninger on Sat, Jul 25, 1998 at 03:51:48PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 25, 1998 at 03:51:48PM -0500, Karl Denninger wrote: > I believe I have found a rather serious MMAP problem in -CURRENT. > > Diablo (the news system) is the test case; with MMAP enabled it will randomly > write exactly one block (512 bytes) of zeros into the article spool files > rather than the proper data - its almost like an update via MMAP isn't I have seen an extremely similar problem, both on 2.2.6 and -current, with INN 2.0 configured to use MMAP for the active file. It is fairly easy to reproduce by doing a "ctlinnd newgroup". After that, a bunch of zeroes appears in the active file. I haven't bothered investigating the problem for lack of time because configuring INN to use read() just works and because I wasn't sure it was a FreeBSD problem, but I'm ready to do any testing I can to help fix this. -- Pierre.Beyssac@hsc.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 08:02:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00603 for freebsd-current-outgoing; Mon, 27 Jul 1998 08:02:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailgate.cadence.com (mailgate.Cadence.COM [158.140.2.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00460 for ; Mon, 27 Jul 1998 08:01:56 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: (from smap@localhost) by mailgate.cadence.com (8.8.5/8.6.8) id IAA28873; Mon, 27 Jul 1998 08:01:13 -0700 (PDT) Message-Id: <199807271501.IAA28873@mailgate.cadence.com> Received: from unknown(194.32.96.136) by mailgate.cadence.com via smap (mjr-v1.2) id xma901551672.028868; Mon, 27 Jul 98 08:01:12 -0700 Comments: Authenticated sender is From: "Duncan Barclay" To: Karl Denninger , current@FreeBSD.ORG, Pierre Beyssac Date: Mon, 27 Jul 1998 16:00:55 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: MMAP problems Reply-to: dmlb@ragnet.demon.co.uk In-reply-to: <19980727152658.A24276@mars.hsc.fr> References: <19980725155148.43084@mcs.net>; from Karl Denninger on Sat, Jul 25, 1998 at 03:51:48PM -0500 X-mailer: Pegasus Mail for Win32 (v2.53/R1) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, Jul 25, 1998 at 03:51:48PM -0500, Karl Denninger wrote: > > I believe I have found a rather serious MMAP problem in -CURRENT. > > > > Diablo (the news system) is the test case; with MMAP enabled it will randomly > > write exactly one block (512 bytes) of zeros into the article spool files > > rather than the proper data - its almost like an update via MMAP isn't > > I have seen an extremely similar problem, both on 2.2.6 and > -current, with INN 2.0 configured to use MMAP for the active file. > It is fairly easy to reproduce by doing a "ctlinnd newgroup". After > that, a bunch of zeroes appears in the active file. > > I haven't bothered investigating the problem for lack of time > because configuring INN to use read() just works and because I > wasn't sure it was a FreeBSD problem, but I'm ready to do any > testing I can to help fix this. > -- Ditto same problem with inn on -2.2.5, and inn 1.5.2. I seem to remember that this was documented in the inn instructions? Duncan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 08:05:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01011 for freebsd-current-outgoing; Mon, 27 Jul 1998 08:05:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00997 for ; Mon, 27 Jul 1998 08:05:14 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id KAA01450; Mon, 27 Jul 1998 10:04:47 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id KAA24543; Mon, 27 Jul 1998 10:04:46 -0500 (CDT) Message-ID: <19980727100446.04271@mcs.net> Date: Mon, 27 Jul 1998 10:04:46 -0500 From: Karl Denninger To: dmlb@ragnet.demon.co.uk Cc: current@FreeBSD.ORG, Pierre Beyssac Subject: Re: MMAP problems References: <19980725155148.43084@mcs.net>; <19980727152658.A24276@mars.hsc.fr> <199807271501.IAA28873@mailgate.cadence.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807271501.IAA28873@mailgate.cadence.com>; from Duncan Barclay on Mon, Jul 27, 1998 at 04:00:55PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 27, 1998 at 04:00:55PM +0000, Duncan Barclay wrote: > > On Sat, Jul 25, 1998 at 03:51:48PM -0500, Karl Denninger wrote: > > > I believe I have found a rather serious MMAP problem in -CURRENT. > > > > > > Diablo (the news system) is the test case; with MMAP enabled it will randomly > > > write exactly one block (512 bytes) of zeros into the article spool files > > > rather than the proper data - its almost like an update via MMAP isn't > > > > I have seen an extremely similar problem, both on 2.2.6 and > > -current, with INN 2.0 configured to use MMAP for the active file. > > It is fairly easy to reproduce by doing a "ctlinnd newgroup". After > > that, a bunch of zeroes appears in the active file. > > > > I haven't bothered investigating the problem for lack of time > > because configuring INN to use read() just works and because I > > wasn't sure it was a FreeBSD problem, but I'm ready to do any > > testing I can to help fix this. > > -- > > Ditto same problem with inn on -2.2.5, and inn 1.5.2. > I seem to remember that this was documented in the inn instructions? > > Duncan Sigh.... This one is pretty important folks; we need to get some attention focused on this since it appears to cut across all the various releases out there right now. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 08:21:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03802 for freebsd-current-outgoing; Mon, 27 Jul 1998 08:21:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03794 for ; Mon, 27 Jul 1998 08:21:24 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id KAA01416; Mon, 27 Jul 1998 10:20:13 -0500 (EST) (envelope-from toor) Message-Id: <199807271520.KAA01416@dyson.iquest.net> Subject: Re: New LINT options: what is VM coloring? In-Reply-To: from Doug Rabson at "Jul 27, 98 09:51:47 am" To: dfr@nlsystems.com (Doug Rabson) Date: Mon, 27 Jul 1998 10:20:13 -0500 (EST) Cc: dyson@iquest.net, tlambert@primenet.com, roberto@keltia.freenix.fr, freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson said: > On Sun, 26 Jul 1998, John S. Dyson wrote: > > > > Actually, the L1 cache is where it's most important (see paper references > > > in my previous posting). Also, the Alpha can significantly benefit from > > > this, per Digital UNIX: > > > > > Is the L1 cache on the Alpha is direct mapped??? On the X86, it isn't. When > > actually running tests, it doesn't seem to make ANY differences on the X86, > > due to the very small number of pages, and the mapping scheme. > > I'm not too sure what the layout of the alpha caches are. I expect they > are different on different processor generations. I really must start > reading the processor manuals for these things... > For two level caches, the coloring should work fine. However, it is problematical with 3-level alpha caches. My guess is that one would want to page-color for the 2nd and 3rd level caches, but of course, you might want to experiment. It is critical to color for the larger cache. To color for all three caches, you could just expand the coloring scheme in FreeBSD. I don't know if it is the right approach though. One thing: I experimented with cache-line coloring for data structures, and found absolutely no performance improvement, and perhaps a significant performance decrease on PPro, and so did not add it. You might want to investigate adding the data structure coloring if it is helpful for Alphas. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 08:32:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05771 for freebsd-current-outgoing; Mon, 27 Jul 1998 08:32:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa3-01.ix.netcom.com [206.214.137.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05761 for ; Mon, 27 Jul 1998 08:32:52 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id IAA14392; Mon, 27 Jul 1998 08:32:28 -0700 (PDT) (envelope-from tomdean) Date: Mon, 27 Jul 1998 08:32:28 -0700 (PDT) Message-Id: <199807271532.IAA14392@ix.netcom.com> From: Thomas Dean To: FreeBSD-current@FreeBSD.ORG Subject: Savecore_enable not in rc.conf Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Should savecore_enable be in rc.conf? /etc/rc contains: # enable dumpdev so that savecore can see it if [ "X${dumpdev}" != X"NO" -a -e ${dumpdev} ]; then dumpon ${dumpdev} fi # /var/crash should be a directory or a symbolic link # to the crash directory if core dumps are to be saved. if [ "X${savecore_enable}" = X"YES" -a -d /var/crash ]; then echo -n checking for core dump... savecore /var/crash fi Should we change rc.conf? dumpdev="NO" # Device name to crashdump to (if enabled). savecore_enable="NO" # Save kernel core dumps (if enables). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 08:39:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06831 for freebsd-current-outgoing; Mon, 27 Jul 1998 08:39:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA06817 for ; Mon, 27 Jul 1998 08:39:25 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id PAA04072 for current@freebsd.org; Mon, 27 Jul 1998 15:45:58 +0200 From: Luigi Rizzo Message-Id: <199807271345.PAA04072@labinfo.iet.unipi.it> Subject: SMP kernels... how many processes can be in ? To: current@FreeBSD.ORG Date: Mon, 27 Jul 1998 15:45:58 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am about to do some minor modifications to the dummynet code and, for technical reasons (don't want to change interfaces to widely used kernel functions) need to keep some state to be passed between functions in a static variable. Something similar is already done in the ipfw package using the DIVERT option. Now my doubt is, on a multiprocessor machine, could it happen that multiple instances of the code in /sys/netinet are run, in which case i should also have multiple instances of such variables where i pass state ? luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 09:40:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17553 for freebsd-current-outgoing; Mon, 27 Jul 1998 09:40:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wit393107.student.utwente.nl (root@wit393107.student.utwente.nl [130.89.235.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17542 for ; Mon, 27 Jul 1998 09:40:48 -0700 (PDT) (envelope-from gelderen@mediaport.org) Received: from wit395301.student.utwente.nl ([130.89.235.121]:30471 "HELO deskfix" ident: "NO-IDENT-SERVICE") by wit393107.student.utwente.nl with SMTP id <4112-234>; Mon, 27 Jul 1998 18:40:13 +0200 Message-ID: <001e01bdb97d$365f2ea0$1400000a@deskfix.local> From: "Jeroen C. van Gelderen" To: Subject: Minor order problem in rc.conf Date: Mon, 27 Jul 1998 18:40:06 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just installed a 3.0-980520-SNAP machine as a firewall and masquearading machine. I noticed the new natd_* options and decided to use them. All went fine, except for one thing: ntpdate doesn't work at startup. It appears that in order for ntpdate to work the masquerading code must be running, otherwise the firewall diverts packets from the outside interface to the not-yet started natd... Has this been fixed, or shall I try to fix the startup scripts? Cheers, Jeroen -- Jeroen C. van Gelderen -- gelderen@mediaport.org => Fight Spam! Join CAUCE! -- http://www.cauce.org -----Original Message----- From: Thomas Dean To: FreeBSD-current@FreeBSD.ORG Date: maandag 27 juli 1998 18:07 Subject: Savecore_enable not in rc.conf |Should savecore_enable be in rc.conf? | |/etc/rc contains: | |# enable dumpdev so that savecore can see it |if [ "X${dumpdev}" != X"NO" -a -e ${dumpdev} ]; then | dumpon ${dumpdev} |fi | |# /var/crash should be a directory or a symbolic link |# to the crash directory if core dumps are to be saved. |if [ "X${savecore_enable}" = X"YES" -a -d /var/crash ]; then | echo -n checking for core dump... | savecore /var/crash |fi | | |Should we change rc.conf? | |dumpdev="NO" # Device name to crashdump to (if enabled). |savecore_enable="NO" # Save kernel core dumps (if enables). | |To Unsubscribe: send mail to majordomo@FreeBSD.org |with "unsubscribe freebsd-current" in the body of the message | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 10:33:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26119 for freebsd-current-outgoing; Mon, 27 Jul 1998 10:33:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA26095 for ; Mon, 27 Jul 1998 10:33:17 -0700 (PDT) (envelope-from ab@paert.tse-online.de) Received: (qmail 4501 invoked by uid 1000); 27 Jul 1998 17:38:37 -0000 Message-ID: <19980727193837.A4447@paert.tse-online.de> Date: Mon, 27 Jul 1998 19:38:37 +0200 From: Andreas Braukmann To: freebsd-current@FreeBSD.ORG Subject: difficulties with CCD? ... (ok. first time CCD-user :(( ) Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i Organization: TSE TeleService GmbH Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, ... I'm trying to use the ccd-driver for mirroring. I labeled both of the chosen slices (sd1s1, sd2s1) as follows: > # size offset fstype [fsize bsize bps/cpg] > c: 8916012 0 unused 0 0 # (Cyl. 0 - 554*) > e: 8916012 0 4.2BSD 0 0 0 # (Cyl. 0 - 554*) My ccdconfig is like this: > adler# ccdconfig -g > ccd0 32 6 /dev/sd1e /dev/sd2e [BTW, I was quite astonished that I obviously have to use the compatibility- notation for the partion names ....] The 'automagically'(??) provided disklable for the ccd seems to be ok? > adler# disklabel ccd0 > # /dev/rccd0c: > type: CCD > disk: ccd > label: default label > flags: > bytes/sector: 512 > sectors/track: 2048 > tracks/cylinder: 1 > sectors/cylinder: 2048 > cylinders: 4353 > sectors/unit: 8915968 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # milliseconds > track-to-track seek: 0 # milliseconds > drivedata: 0 > > 3 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 8915968 0 4.2BSD 0 0 0 # (Cyl. 0 - 4353*) But every time a try to newfs the ccd: > adler# newfs rccd0c > Warning: 1024 sector(s) in last cylinder unallocated > /dev/rccd0c: 8915968 sectors in 2177 cylinders of 1 tracks, 4096 sectors > 4353.5MB in 137 cyl groups (16 c/g, 32.00MB/g, 7936 i/g) > super-block backups (for fsck -b #) at: > 32, 65568, 131104, 196640, 262176, 327712, 393248, 458784, 524320, 589856, > 655392, 720928, 786464, 852000, 917536, 983072, 1048608, 1114144, 1179680, [...] > 8912928, > newfs: ioctl (WDINFO): No such process > newfs: /dev/rccd0c: can't rewrite disk label Hmmm. Any hints? I have this feeling, that I might have overseen something important? TIA, Andreas -- /// TSE TeleService GmbH | Gsf: Arne Reuter | /// Hovestrasse 14 | Andreas Braukmann | We do it with /// D-48351 Everswinkel | HRB: 1430, AG WAF | FreeBSD/SMP /// ------------------------------------------------------------------- /// PGP-Key: http://www.tse-online.de/~ab/public-key /// Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 10:39:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27606 for freebsd-current-outgoing; Mon, 27 Jul 1998 10:39:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from trinity.radio-do.de (fn@trinity.Radio-do.de [193.101.164.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27570 for ; Mon, 27 Jul 1998 10:39:19 -0700 (PDT) (envelope-from fn@trinity.radio-do.de) Received: (from fn@localhost) by trinity.radio-do.de (8.8.8/8.8.5/RADIO-1.1) id TAA09230; Mon, 27 Jul 1998 19:38:44 +0200 (CEST) Message-ID: <19980727193843.A9217@radio-do.de> Date: Mon, 27 Jul 1998 19:38:43 +0200 From: Frank Nobis To: FreeBSD-current@FreeBSD.ORG Subject: Re: Savecore_enable not in rc.conf References: <199807271532.IAA14392@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807271532.IAA14392@ix.netcom.com>; from Thomas Dean on Mon, Jul 27, 1998 at 08:32:28AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 27, 1998 at 08:32:28AM -0700, Thomas Dean wrote: > Should savecore_enable be in rc.conf? > My /etc/rc reads like this # enable dumpdev so that savecore can see it # /var/crash should be a directory or a symbolic link # to the crash directory if core dumps are to be saved. if [ "X${dumpdev}" != X"NO" -a -e ${dumpdev} -a -d /var/crash ]; then dumpon ${dumpdev} echo -n checking for core dump... savecore /var/crash fi > > Should we change rc.conf? > No. Get a more recent /etc/rc > dumpdev="NO" # Device name to crashdump to (if enabled). > savecore_enable="NO" # Save kernel core dumps (if enables). Only dumdev needs to be defined for savecore Regards Frank -- Frank Nobis Email: PGP AVAILABLE Landgrafenstr. 130 dg3dcn http://www.radio-do.de/~fn/ 44139 Dortmund Powered by FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 10:43:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28361 for freebsd-current-outgoing; Mon, 27 Jul 1998 10:43:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from NIH2WAAF (smtp6.site1.csi.com [149.174.183.75]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28345 for ; Mon, 27 Jul 1998 10:43:03 -0700 (PDT) (envelope-from derm@iol.ie) Received: from mail pickup service by csi.com with Microsoft SMTPSVC; Mon, 27 Jul 1998 13:42:02 -0400 Received: from md29-072.mun.compuserve.com (md29-072.mun.compuserve.com [195.232.47.72]) by hil-img-ims-3.compuserve.com (8.8.6/8.8.6/IMS-1.3) with SMTP id NAA19115 for ; Mon, 27 Jul 1998 13:41:21 -0400 (EDT) From: derm@iol.ie (Dermot McNally) To: FreeBSD-current@FreeBSD.ORG Subject: Problems with ed driver (PCI) Date: Mon, 27 Jul 1998 17:41:15 GMT Organization: My House Message-ID: <35bcb5ac.2742218@mail.compuserve.com> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id KAA28349 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I hope someone can shed some light on this - I'm running the snapshot from 24-5-98 and pretty much everything works OK. Everything, that is, apart from the network card. It's a totally average PCI NE2000 clone, and it is even detected at boot time, thus: found-> vendor=0x10ec, dev=0x8029, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=15 map[0]: type 4, range 32, base 0000fca0, size 5 ed0: rev 0x00 int a irq 15 on pci0.15.0 However, this doesn't help, because after boot time, any attempt to configure the interface leads to the error: interface ed0 does not exist Very probably I'm forgetting something obvious, but I never remember having to do anything more than just include the driver and configure the interface... Would it help any if I grabbed a more recent set of sources? Thanks, Dermot ----------------------------------------------------------- Dermot McNally, derm@iol.ie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 11:04:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02646 for freebsd-current-outgoing; Mon, 27 Jul 1998 11:04:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02621 for ; Mon, 27 Jul 1998 11:04:24 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA19829; Mon, 27 Jul 1998 10:54:41 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdW19811; Mon Jul 27 17:54:30 1998 Date: Mon, 27 Jul 1998 10:54:21 -0700 (PDT) From: Julian Elischer To: Matthew Thyer cc: Eivind Eklund , FreeBSD CURRENT Subject: Re: DEVFS not creating slice devices for my SCSI disks In-Reply-To: <35BC02D5.574F9516@dsto.defence.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the patch was committer at teh same time I told you about it.... (It was defintly a bug so I fixed it without confirmation from you..) On Mon, 27 Jul 1998, Matthew Thyer wrote: > The patch that Julian sent me has fixed the problem. > > I hope it will be committed soon (I hate running separate sources). > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 11:32:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08847 for freebsd-current-outgoing; Mon, 27 Jul 1998 11:32:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08786 for ; Mon, 27 Jul 1998 11:31:52 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA00650; Mon, 27 Jul 1998 11:27:17 -0700 (PDT) Message-Id: <199807271827.LAA00650@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: derm@iol.ie (Dermot McNally) cc: FreeBSD-current@FreeBSD.ORG Subject: Re: Problems with ed driver (PCI) In-reply-to: Your message of "Mon, 27 Jul 1998 17:41:15 GMT." <35bcb5ac.2742218@mail.compuserve.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 11:27:17 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I hope someone can shed some light on this - I'm running the snapshot from > 24-5-98 and pretty much everything works OK. Everything, that is, apart > from the network card. It's a totally average PCI NE2000 clone, and it is > even detected at boot time, thus: > > found-> vendor=0x10ec, dev=0x8029, revid=0x00 > class=02-00-00, hdrtype=0x00, mfdev=0 > intpin=a, irq=15 > map[0]: type 4, range 32, base 0000fca0, size 5 > ed0: rev 0x00 int a irq 15 on > pci0.15.0 You have mistyped here; the device is ed1. There has to be at least one ISA instance, and that will be ed0. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 11:45:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12062 for freebsd-current-outgoing; Mon, 27 Jul 1998 11:45:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11976 for ; Mon, 27 Jul 1998 11:44:39 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA22085; Mon, 27 Jul 1998 11:36:26 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdh22055; Mon Jul 27 18:36:16 1998 Date: Mon, 27 Jul 1998 11:36:05 -0700 (PDT) From: Julian Elischer To: Luigi Rizzo cc: current@FreeBSD.ORG Subject: Re: SMP kernels... how many processes can be in ? In-Reply-To: <199807271345.PAA04072@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Jul 1998, Luigi Rizzo wrote: > Hi, > > I am about to do some minor modifications to the dummynet code and, for > technical reasons (don't want to change interfaces to widely used > kernel functions) need to keep some state to be passed between > functions in a static variable. > > Something similar is already done in the ipfw package using the > DIVERT option. Now my doubt is, on a multiprocessor machine, could > it happen that multiple instances of the code in /sys/netinet are > run, in which case i should also have multiple instances of such > variables where i pass state ? In fine-graned SMP it breaks, however the 'chunkiness' of the present SMP means that only one processor is in the networking stacks at a time.. now I've been thinking about how to fix this... 1/ Some extra flags in the header mbuf. 2/ sticking some 'MT_RIGHTS' or 'MT_CONTROL' mbufs can be added on the head or end of the packet, and used to hold this info. (encoded like tcp options.. 1 byte type, 1 byte len, data.) the hack would be to put code that 'unpacks' this info on entry to ip_input and ip_output. (and tcp_input) Normal data flow woudl be the same if the lead type or flags did not indicate the existance of these modifiers.. I would include a 'flow' as one of the modifiers. julian > > luigi > -----------------------------+-------------------------------------- > Luigi Rizzo | Dip. di Ingegneria dell'Informazione > email: luigi@iet.unipi.it | Universita' di Pisa > tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) > fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ > _____________________________|______________________________________ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 11:51:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13152 for freebsd-current-outgoing; Mon, 27 Jul 1998 11:51:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.baldcom.net (green@zone.BALDCOM.NET [205.232.46.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13000 for ; Mon, 27 Jul 1998 11:50:13 -0700 (PDT) (envelope-from green@zone.baldcom.net) Received: from localhost (green@localhost) by zone.baldcom.net (8.8.8/8.8.7) with SMTP id OAA18047; Mon, 27 Jul 1998 14:49:28 -0400 (EDT) Date: Mon, 27 Jul 1998 14:49:28 -0400 (EDT) From: Brian Feldman To: Thomas Dean cc: FreeBSD-current@FreeBSD.ORG Subject: Re: Savecore_enable not in rc.conf In-Reply-To: <199807271532.IAA14392@ix.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Your rc(5) appears to be out of date; the current revision is $Id: rc,v 1.146 1998/06/22 06:34:12 jkoshy Exp $ and it contains the following: /* begin line 182 */ # enable dumpdev so that savecore can see it # /var/crash should be a directory or a symbolic link # to the crash directory if core dumps are to be saved. if [ "X${dumpdev}" != X"NO" -a -e ${dumpdev} -a -d /var/crash ]; then dumpon ${dumpdev} echo -n checking for core dump... savecore /var/crash fi /* end line 189 */ Cheers, Brian Feldman green@unixhelp.org On Mon, 27 Jul 1998, Thomas Dean wrote: > Should savecore_enable be in rc.conf? > > /etc/rc contains: > > # enable dumpdev so that savecore can see it > if [ "X${dumpdev}" != X"NO" -a -e ${dumpdev} ]; then > dumpon ${dumpdev} > fi > > # /var/crash should be a directory or a symbolic link > # to the crash directory if core dumps are to be saved. > if [ "X${savecore_enable}" = X"YES" -a -d /var/crash ]; then > echo -n checking for core dump... > savecore /var/crash > fi > > > Should we change rc.conf? > > dumpdev="NO" # Device name to crashdump to (if enabled). > savecore_enable="NO" # Save kernel core dumps (if enables). > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 12:58:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25657 for freebsd-current-outgoing; Mon, 27 Jul 1998 12:58:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25613 for ; Mon, 27 Jul 1998 12:58:27 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id PAA14638; Mon, 27 Jul 1998 15:57:43 -0400 (EDT) (envelope-from wollman) Date: Mon, 27 Jul 1998 15:57:43 -0400 (EDT) From: Garrett Wollman Message-Id: <199807271957.PAA14638@khavrinen.lcs.mit.edu> To: Julian Elischer Cc: Luigi Rizzo , current@FreeBSD.ORG Subject: Re: SMP kernels... how many processes can be in ? In-Reply-To: References: <199807271345.PAA04072@labinfo.iet.unipi.it> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > 2/ sticking some 'MT_RIGHTS' or > 'MT_CONTROL' mbufs can be added on the head or end of the packet, and used > to hold this info. (encoded like tcp options.. 1 byte type, 1 byte len, > data.) Gross! Please don't do this! We have too much code that depends on mbuf chaining as it is! -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 13:09:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27604 for freebsd-current-outgoing; Mon, 27 Jul 1998 13:09:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27587 for ; Mon, 27 Jul 1998 13:09:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA01087; Mon, 27 Jul 1998 13:07:05 -0700 (PDT) Message-Id: <199807272007.NAA01087@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Garrett Wollman cc: Julian Elischer , Luigi Rizzo , current@FreeBSD.ORG Subject: Re: SMP kernels... how many processes can be in ? In-reply-to: Your message of "Mon, 27 Jul 1998 15:57:43 EDT." <199807271957.PAA14638@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 13:07:05 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > 2/ sticking some 'MT_RIGHTS' or > > 'MT_CONTROL' mbufs can be added on the head or end of the packet, and used > > to hold this info. (encoded like tcp options.. 1 byte type, 1 byte len, > > data.) > > Gross! Please don't do this! We have too much code that depends on > mbuf chaining as it is! Ok, so we know what's "bad". Any suggestions on "less bad"? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 13:42:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03795 for freebsd-current-outgoing; Mon, 27 Jul 1998 13:42:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from NIH2WAAE (smtp5.site1.csi.com [149.174.183.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03721 for ; Mon, 27 Jul 1998 13:41:42 -0700 (PDT) (envelope-from derm@iol.ie) Received: from mail pickup service by csi.com with Microsoft SMTPSVC; Mon, 27 Jul 1998 16:41:05 -0400 Received: from md43-086.mun.compuserve.com (md43-086.mun.compuserve.com [195.232.54.86]) by hil-img-ims-3.compuserve.com (8.8.6/8.8.6/IMS-1.4) with SMTP id QAA06504 for ; Mon, 27 Jul 1998 16:40:31 -0400 (EDT) From: derm@iol.ie (Dermot McNally) To: freebsd-current@FreeBSD.ORG Subject: Re: Problems with ed driver (PCI) Date: Mon, 27 Jul 1998 20:40:30 GMT Organization: My House Message-ID: <35bfe58c.14998109@mail.compuserve.com> References: <199807271827.LAA00650@dingo.cdrom.com> In-Reply-To: <199807271827.LAA00650@dingo.cdrom.com> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA03731 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Jul 1998 11:27:17 -0700, Mike Smith wrote: >> I hope someone can shed some light on this - I'm running the snapshot from >> 24-5-98 and pretty much everything works OK. Everything, that is, apart >> from the network card. It's a totally average PCI NE2000 clone, and it is >> even detected at boot time, thus: >> >> found-> vendor=0x10ec, dev=0x8029, revid=0x00 >> class=02-00-00, hdrtype=0x00, mfdev=0 >> intpin=a, irq=15 >> map[0]: type 4, range 32, base 0000fca0, size 5 >> ed0: rev 0x00 int a irq 15 on >> pci0.15.0 > >You have mistyped here; the device is ed1. There has to be at least >one ISA instance, and that will be ed0. Nope, I should have said - what's above is a copy and paste job, I followed earlier tips on the list about how to get the PCI device to become ed0. FWIW, it did exactly the same when I tried to drive it as ed1 (and that includes with the generic kernel). Dermot ----------------------------------------------------------- Dermot McNally, derm@iol.ie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 14:21:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11760 for freebsd-current-outgoing; Mon, 27 Jul 1998 14:21:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11661 for ; Mon, 27 Jul 1998 14:20:54 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id RAA00330 for ; Mon, 27 Jul 1998 17:20:16 -0400 (EDT) Date: Mon, 27 Jul 1998 17:20:15 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: current@FreeBSD.ORG Subject: ppp driving me nuts Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG PPP is silently dropping my connection, every few minutes. Nothing in the logs. Help! Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 15:02:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20527 for freebsd-current-outgoing; Mon, 27 Jul 1998 15:02:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (root@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20347; Mon, 27 Jul 1998 15:01:03 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA12491; Mon, 27 Jul 1998 14:32:33 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpdg10903; Mon Jul 27 14:32:27 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id LAA23030; Mon, 27 Jul 1998 11:56:04 -0700 (MST) From: Terry Lambert Message-Id: <199807271856.LAA23030@usr02.primenet.com> Subject: Re: temporary FreeBSD token-ring list. To: mike@smith.net.au (Mike Smith) Date: Mon, 27 Jul 1998 18:56:03 +0000 (GMT) Cc: tlambert@primenet.com, winter@jurai.net, hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199807270604.XAA14756@antipodes.cdrom.com> from "Mike Smith" at Jul 26, 98 11:04:53 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > As a point of interest, MITRE announced a working NetBEUI for > > FreeBSD a number of moths ago on the SAMBA list. > > > > To do this, they must have implemented the 802.3 LLC. > > > > Someone should follow up with MITRE. > > Did they? This would be extremely useful. On or about FreeBSD 2.2.4. Yes, it would be extremely useful if someone would followup with them. Someone with core team credentials would be best. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 15:13:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22118 for freebsd-current-outgoing; Mon, 27 Jul 1998 15:13:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22064 for ; Mon, 27 Jul 1998 15:12:58 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id PAA22834; Mon, 27 Jul 1998 15:12:19 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 27 Jul 1998 15:12:18 -0700 (PDT) From: Doug White To: Hostas Red cc: current@FreeBSD.ORG Subject: Re: Strange idle times In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 25 Jul 1998, Hostas Red wrote: > > > About one month or so i have a strange idle times on my -current (really > > > current - 1 hour or so :) - whenever i use 'w' or 'finger' idle time of > > > users equivalent to uptime (maybe 1 minute less). ;-( > > > > > > 'apm' disabled in kernel, nothing changed ever since. It just happend one > > > time and lasts till now. > > > > > > Anybody have such a problem? > > > > Corrupted utmp/wtmp perhaps? Something trying to use the old format? > > But why? I'm sitting on -current for more than half a year already and i'm > rebooting sometimes :). wtmp rolls daily, utmp brand new after rebooting > half an hour ago. And problem still exitst, after one more 'make world'. Perhaps you have a program using the old format, like ssh? I'm having this problem with our house router (I need to fix that). Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 15:15:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22464 for freebsd-current-outgoing; Mon, 27 Jul 1998 15:15:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22403 for ; Mon, 27 Jul 1998 15:14:53 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id RAA02566; Mon, 27 Jul 1998 17:14:08 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id RAA10677; Mon, 27 Jul 1998 17:14:08 -0500 (CDT) Message-ID: <19980727171408.52273@mcs.net> Date: Mon, 27 Jul 1998 17:14:08 -0500 From: Karl Denninger To: Matt Dillon Cc: Terry Lambert , Mike Smith , wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Subject: Re: demonstration of mmap problem References: <199807272211.PAA05424@flea.best.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807272211.PAA05424@flea.best.net>; from Matt Dillon on Mon, Jul 27, 1998 at 03:11:46PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yep. That's EXACTLY what I'm seeing here - frequently. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost On Mon, Jul 27, 1998 at 03:11:46PM -0700, Matt Dillon wrote: > (forward this to the freebsd lists if you want. I also submitted a > bug report to FreeBSD). > > I was able to catch it in the act, though I am not entirely sure when > the actual file corruption occured. > > The hexdump of the data file below demonstrates the corruption. Note > that it 'ends' at a page boundry. I was also able to ktrace the > diablo process that was responsible for writing to the file. Note > that it has no problem writing to the file and that some of the areas > to which it wrote real data got zero'd out by the corruption problem. > > There is another process, not shown... a dnewslink was simultaniously > mmap()ing the same file SHARED+RO and transfering (touching the page(s) > near the end of the file continuously) the articles to the diablo > reader running on the same box. > > -Matt > > 0002.1960 0a 20 20 20 20 20 73 6f 6d 65 68 6f 77 20 61 20 . somehow a > 0002.1970 73 61 70 6c 69 6e 67 0a 20 20 20 20 20 6f 6e 20 sapling. on > 0002.1980 74 68 69 73 20 62 65 64 72 6f 63 6b 20 6f 66 20 this bedrock of > 0002.1990 61 20 74 6f 6e 67 75 65 0a 0a 20 20 20 20 20 69 a tongue.. i > 0002.19a0 74 20 77 69 6c 6c 20 62 65 0a 20 20 20 20 20 61 t will be. a > 0002.19b0 73 20 79 6f 75 20 68 61 76 65 20 77 72 69 74 74 s you have writt > 0002.19c0 65 6e 0a 20 20 20 20 20 61 73 20 65 78 61 63 74 en. as exact > 0002.19d0 20 61 6e 64 20 6c 6f 76 65 6c 79 0a 20 20 20 20 and lovely. > 0002.19e0 20 61 73 20 61 6e 79 20 66 72 75 69 74 20 62 65 as any fruit be > 0002.19f0 61 72 69 6e 67 20 74 68 69 6e 67 0a 20 20 20 20 aring thing. > 0002.1a00 20 74 68 61 74 20 77 69 6c 6c 20 65 76 65 72 20 that will ever > 0002.1a10 6d 61 6b 65 20 61 20 73 6f 75 6e 64 0a 0a 0a 37 make a sound...7 > 0002.1a20 2d 32 37 2d 39 38 0a 64 63 6c 65 0a 0a 2d 2d 2d -27-98.dcle..--- > 0002.1a30 2d 2d 3d 3d 20 50 6f 73 74 65 64 20 76 69 61 20 --== Posted via > 0002.1a40 44 65 6a 61 20 4e 65 77 73 2c 20 54 68 65 20 4c Deja News, The L > 0002.1a50 65 61 64 65 72 20 69 6e 20 49 6e 74 65 72 6e 65 eader in Interne > 0002.1a60 74 20 44 69 73 63 75 73 73 69 6f 6e 20 3d 3d 2d t Discussion ==- > 0002.1a70 2d 2d 2d 2d 0a 68 74 74 70 3a 2f 2f 77 77 77 2e ----.http://www. > 0002.1a80 64 65 6a 61 6e 65 77 73 2e 63 6f 6d 2f 72 67 5f dejanews.com/rg_ > 0002.1a90 6d 6b 67 72 70 2e 78 70 20 20 20 43 72 65 61 74 mkgrp.xp Creat > 0002.1aa0 65 20 59 6f 75 72 20 4f 77 6e 20 46 72 65 65 20 e Your Own Free > 0002.1ab0 4d 65 6d 62 65 72 20 46 6f 72 75 6d 0a 00 00 00 Member Forum.... > 0002.1ac0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0002.1ad0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0002.1ae0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0002.1af0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0002.1b00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0002.1b10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0002.1b20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > ... > 0002.1f70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0002.1f80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0002.1f90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0002.1fa0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0002.1fb0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0002.1fc0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0002.1fd0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0002.1fe0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0002.1ff0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0002.2000 69 74 64 2e 75 6d 69 63 68 2e 65 64 75 21 6e 65 itd.umich.edu!ne > 0002.2010 77 73 2d 70 65 65 72 2e 67 69 70 2e 6e 65 74 21 ws-peer.gip.net! > 0002.2020 6e 65 77 73 2e 67 73 6c 2e 6e 65 74 21 67 69 70 news.gsl.net!gip > 0002.2030 2e 6e 65 74 21 6e 65 77 73 66 65 65 64 2e 69 6e .net!newsfeed.in > 0002.2040 74 65 72 6e 65 74 6d 63 69 2e 63 6f 6d 21 32 30 ternetmci.com!20 > 0002.2050 34 2e 32 33 38 2e 31 32 30 2e 31 33 30 21 6e 65 4.238.120.130!ne > > > 8240 diablo 0.000120 CALL lseek(0xe,0,0x21abe,0,0) > 8240 diablo 0.000041 RET lseek 137918/0x21abe > 8240 diablo 0.000032 CALL write(0xe,0x2278c020,0x283) > 8240 diablo 0.000095 GIO fd 14 wrote 643 bytes > "Path: news3.best.com!news1.best.com!feed1.news.erols.com!howland.erols.net!newsfeed.internetmci.com!204.238.120.130!news-feeds.jump.net!nntp2.dejanews.com!nnrp1.dejanews.com!not\ > -for-mail > From: parsrise@my-dejanews.com > Newsgroups: ott.business.ads > Subject: Ottawa, Centretown Apartments For Rent > Date: Mon, 27 Jul 1998 20:48:59 GMT > Organization: Deja News - The Leader in Internet Discussion > Lines: 29 > Message-ID: <6pip3s$f5b$1@nnrp1.dejanews.com> > NNTP-Posting-Host: 192.58.194.87 > X-Article-Creation-Date: Mon Jul 27 20:48:59 1998 GMT > X-Http-User-Agent: Mozilla/3.04 (X11; I; HP-UX A.09.03 9000/712) > Xref: news3.best.com ott.business.ads:12900 > " > 8240 diablo 0.000038 RET write 643/0x283 > 8240 diablo 0.000065 CALL lseek(0xe,0,0,0,0x1) > 8240 diablo 0.000032 RET lseek 138561/0x21d41 > 8240 diablo 0.000030 CALL write(0xe,0x2278c020,0x291) > 8240 diablo 0.000060 GIO fd 14 wrote 657 bytes > ... > 8240 diablo 0.000046 CALL lseek(0xe,0,0,0,0x1) > 8240 diablo 0.000033 RET lseek 139218/0x21fd2 > ... > > 139264 is the 4K boundry > > > > 8240 diablo 0.000054 CALL lseek(0xe,0,0x21fd2,0,0) > 8240 diablo 0.000037 RET lseek 139218/0x21fd2 > 8240 diablo 0.000035 CALL write(0xe,0x2278c020,0x2d9) > 8240 diablo 0.000408 GIO fd 14 wrote 729 bytes > "Path: news3.best.com!news1.best.com!newsxfer3.itd.umich.edu!news-peer.gip.net!news.gsl.net!gip.net!newsfeed.internetmci.com!204.238.120.130!news-feeds.jump.net!nntp2.dejanews.co\ > m!nnrp1.dejanews.com!not-for-mail > From: elleinad@my-dejanews.com > Newsgroups: rec.arts.disney.parks > Subject: Re: Planning 4 days at WDW > Date: Mon, 27 Jul 1998 20:52:41 GMT > Organization: Deja News - The Leader in Internet Discussion > Lines: 30 > Message-ID: <6pipaq$f81$1@nnrp1.dejanews.com> > References: <1998072618171400.OAA06477@ladder03.news.aol.com> > NNTP-Posting-Host: 204.189.84.62 > X-Article-Creation-Date: Mon Jul 27 20:52:41 1998 GMT > X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 4.0; Windows 95) > Xref: news3.best.com rec.arts.disney.parks:187617 > " > 8240 diablo 0.000056 RET write 729/0x2d9 > > 8240 diablo 0.000052 CALL lseek(0xe,0,0,0,0x1) > 8240 diablo 0.000032 RET lseek 139947/0x222ab > 8240 diablo 0.000030 CALL write(0xe,0x2278c020,0x537) > 8240 diablo 0.000066 GIO fd 14 wrote 1335 bytes > " > Well, I'm 13, and these are some of my favorites: > > Magic Kingdom: Space Mountain, Alien Encounter, Splash Mountain, Big Thunder > Mountain Railroad, the Barnstormer (back seat ONLY!) ;-) Epcot: Honey, I > Shrunk the Audience, the Image Works, Innoventions, Wonders of Life, and the > ride at Norway. MGM Studios: Tower of Terror, Star Tours, Superstar > Television, 50's Prime Time Cafe'. (It's an attraction in itself!) Animal > Kingdom: Kilimanjaro Safaris, Countdown to Extinction, Legend of the Lion > King show, Tough to Be A Bug. Water Parks: SUMMIT PLUMMET, Slush Gusher, > Downhill Double Dipper, and the fun chute slide (kind of off to itself) at > Ski Patrol Training Camp. > > Have fun! > > In article <1998072618171400.OAA06477@ladder03.news.aol.com>, > megps@aol.com (MegPS) wrote: > > We are headed to WDW on sunday for 4 days, We will be staying at CS, and we > > have passes for all of the parks and water parks. We have two girls, 14 and16, > > who will probably be on their own for much of the time, can you suggest some > > things that they might want to do while they're there? Thanks much. > > > > > -- > Danielle > Danielle@searnet.com > TDC Keeper of Pegasus, Summit Plummet, > > -----== Posted via Deja News, The Leader in Internet Discussion ==----- > http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum > \0" > 8240 diablo 0.000046 RET write 1335/0x537 > 8240 diablo 0.000040 CALL lseek(0xe,0,0,0,0x1) > 8240 diablo 0.000029 RET lseek 141282/0x227e2 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 15:34:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26253 for freebsd-current-outgoing; Mon, 27 Jul 1998 15:34:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26172 for ; Mon, 27 Jul 1998 15:34:40 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id SAA22663 for ; Mon, 27 Jul 1998 18:34:06 -0400 (EDT) Date: Mon, 27 Jul 1998 18:34:05 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: current@FreeBSD.ORG Subject: more PPP weirdness Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG PPP ON narcissus> show route Destination Gateway Flags Netif default 204.180.194.101 UGSc tun0 10/8 link#1 UC ed0 18.23.0.16 204.180.194.101 UGHW3 tun0 38.180.208.198 204.180.194.101 UGHW3 tun0 127.0.0.1 127.0.0.1 UH lo0 128.10.11.72 204.180.194.101 UGHW tun0 128.193.76.12 204.180.194.101 UGHW3 tun0 137.22.4.31 204.180.194.101 UGHW3 tun0 141.117.1.117 204.180.194.101 UGHW3 tun0 152.1.2.118 204.180.194.101 UGHW3 tun0 152.1.9.90 204.180.194.101 UGHW3 tun0 164.107.115.3 204.180.194.101 UGHW3 tun0 198.67.15.2 204.180.194.101 UGHW tun0 199.184.165.2 204.180.194.101 UGHW tun0 204.180.194.101 204.180.205.197 UH tun0 206.137.222.89 204.180.194.101 UGHW3 tun0 netstat -rn reports my routing tables as being quite normal. Now, I may be misunderstanding, but it looks like PPP is seeing all these hosts as gateways, in which case no wonder it's getting confused. When I grabbed this table from PPP, it was "up" but no packets were getting anywhere. I down'd and quit and dialed again, and now PPP works, but: PPP ON narcissus> show route Destination Gateway Flags Netif default 204.180.194.101 UGSc tun0 10/8 link#1 UC ed0 127.0.0.1 127.0.0.1 UH lo0 198.67.15.2 204.180.194.101 UGHW tun0 199.184.165.2 204.180.194.101 UGHW tun0 204.180.194.101 204.180.205.197 UH tun0 The gateways are growing again. Perhaps this is completely normal, and I'm misunderstanding something? Or perhaps there's just a flipped bit somewhere, since the only PPP-related host route not marked as a gateway is -- my gateway. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 15:50:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29124 for freebsd-current-outgoing; Mon, 27 Jul 1998 15:50:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (root@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29109 for ; Mon, 27 Jul 1998 15:50:47 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id OAA08195; Mon, 27 Jul 1998 14:30:59 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpd007414; Mon Jul 27 14:30:30 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id NAA20781; Mon, 27 Jul 1998 13:23:33 -0700 (MST) From: Terry Lambert Message-Id: <199807272023.NAA20781@usr08.primenet.com> Subject: Re: New LINT options: what is VM coloring? To: dyson@iquest.net Date: Mon, 27 Jul 1998 20:23:32 +0000 (GMT) Cc: dfr@nlsystems.com, tlambert@primenet.com, roberto@keltia.freenix.fr, freebsd-current@FreeBSD.ORG In-Reply-To: <199807271520.KAA01416@dyson.iquest.net> from "John S. Dyson" at Jul 27, 98 10:20:13 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For two level caches, the coloring should work fine. However, it is > problematical with 3-level alpha caches. My guess is that one would > want to page-color for the 2nd and 3rd level caches, but of course, > you might want to experiment. It is critical to color for the larger > cache. To color for all three caches, you could just expand the > coloring scheme in FreeBSD. I don't know if it is the right approach > though. The Digital literature suggests for small enough working sets, putting the entire working set into L1 cache and keeping it there. I don't know how you would ensure this if you were allowing interrupts and drivers to run, except to minimize the use of seperate stacks as much as possible, and reduce the amount of auto data usage and function call depth for interrupt code as much as possible. The method they state they use in order to do this is "page coloring" of the L1 cache. This is from the Digitasl UNIX 2.0 release notes. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 16:08:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02371 for freebsd-current-outgoing; Mon, 27 Jul 1998 16:08:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02354 for ; Mon, 27 Jul 1998 16:08:45 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id SAA02258; Mon, 27 Jul 1998 18:05:17 -0500 (EST) (envelope-from toor) Message-Id: <199807272305.SAA02258@dyson.iquest.net> Subject: Re: New LINT options: what is VM coloring? In-Reply-To: <199807272023.NAA20781@usr08.primenet.com> from Terry Lambert at "Jul 27, 98 08:23:32 pm" To: tlambert@primenet.com (Terry Lambert) Date: Mon, 27 Jul 1998 18:05:17 -0500 (EST) Cc: dyson@iquest.net, dfr@nlsystems.com, tlambert@primenet.com, roberto@keltia.freenix.fr, freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert said: > > For two level caches, the coloring should work fine. However, it is > > problematical with 3-level alpha caches. My guess is that one would > > want to page-color for the 2nd and 3rd level caches, but of course, > > you might want to experiment. It is critical to color for the larger > > cache. To color for all three caches, you could just expand the > > coloring scheme in FreeBSD. I don't know if it is the right approach > > though. > > The Digital literature suggests for small enough working sets, putting > the entire working set into L1 cache and keeping it there. I don't > know how you would ensure this if you were allowing interrupts and > drivers to run, except to minimize the use of seperate stacks as > much as possible, and reduce the amount of auto data usage and function > call depth for interrupt code as much as possible. > > The method they state they use in order to do this is "page coloring" > of the L1 cache. > > This is from the Digitasl UNIX 2.0 release notes. > But - but - but, the L1 cache is small!!! Is our terminology mixed-up? On X86en, L2 cache is the big one. I thought that on an Alpha, the L3 cache is the big one. I don't know how one would fit the working set into a 16K or even 128K cache?!?!?!? I can understand fitting the working set into a 1M -> 4M L3 cache though :-). -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 16:28:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06968 for freebsd-current-outgoing; Mon, 27 Jul 1998 16:28:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (root@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06907 for ; Mon, 27 Jul 1998 16:28:38 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id OAA07847; Mon, 27 Jul 1998 14:30:40 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpdd07414; Mon Jul 27 14:30:15 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id NAA21188; Mon, 27 Jul 1998 13:30:15 -0700 (MST) From: Terry Lambert Message-Id: <199807272030.NAA21188@usr08.primenet.com> Subject: Re: MMAP problems To: mike@smith.net.au (Mike Smith) Date: Mon, 27 Jul 1998 20:30:15 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, karl@Mcs.Net, wollman@khavrinen.lcs.mit.edu, dswartz@druber.com, current@FreeBSD.ORG In-Reply-To: <199807270007.RAA12744@antipodes.cdrom.com> from "Mike Smith" at Jul 26, 98 05:07:08 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The problem Garrett notes is, IMO, "pilot error" and has to do with > > the failure to call msync() when it is necessary. Per the discussion, > > it can be made possible to not need to call msync(). > > Subsequent to your dissertation, do you have any suggested fixes? Someone needs to go over the mmap code with a fine tooth comb, with a critical eye towards what happens when a page from a mapped region is nominally LRU'ed out from under it, and then subsequently read-faulted back in. Unless there is a specific difference for executable page handling, I'll note that I expect this problem to show up from use of shared libraries, as well. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 16:41:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09724 for freebsd-current-outgoing; Mon, 27 Jul 1998 16:41:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09654 for ; Mon, 27 Jul 1998 16:41:15 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id QAA07845; Mon, 27 Jul 1998 16:40:37 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 27 Jul 1998 16:40:36 -0700 (PDT) From: Doug White To: ben@rosengart.com cc: current@FreeBSD.ORG Subject: Re: more PPP weirdness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Jul 1998, Snob Art Genre wrote: > PPP ON narcissus> show route > Destination Gateway Flags Netif > default 204.180.194.101 UGSc tun0 > 10/8 link#1 UC ed0 > 18.23.0.16 204.180.194.101 UGHW3 tun0 > 38.180.208.198 204.180.194.101 UGHW3 tun0 > 127.0.0.1 127.0.0.1 UH lo0 > 128.10.11.72 204.180.194.101 UGHW tun0 > 128.193.76.12 204.180.194.101 UGHW3 tun0 > 137.22.4.31 204.180.194.101 UGHW3 tun0 > 141.117.1.117 204.180.194.101 UGHW3 tun0 > 152.1.2.118 204.180.194.101 UGHW3 tun0 > 152.1.9.90 204.180.194.101 UGHW3 tun0 > 164.107.115.3 204.180.194.101 UGHW3 tun0 > 198.67.15.2 204.180.194.101 UGHW tun0 > 199.184.165.2 204.180.194.101 UGHW tun0 > 204.180.194.101 204.180.205.197 UH tun0 > 206.137.222.89 204.180.194.101 UGHW3 tun0 > > netstat -rn reports my routing tables as being quite normal. Now, I may > be misunderstanding, but it looks like PPP is seeing all these hosts as > gateways, in which case no wonder it's getting confused. When I grabbed > this table from PPP, it was "up" but no packets were getting anywhere. > I down'd and quit and dialed again, and now PPP works, but: [...] You probably have routed turned on, and it's hearing the RIP broadcasts. Disabling routed should quit the growth and subsequent destruction of your default route. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 16:51:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11833 for freebsd-current-outgoing; Mon, 27 Jul 1998 16:51:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11702 for ; Mon, 27 Jul 1998 16:50:21 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id TAA17581; Mon, 27 Jul 1998 19:49:38 -0400 (EDT) Date: Mon, 27 Jul 1998 19:49:36 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Doug White cc: ben@rosengart.com, current@FreeBSD.ORG Subject: Re: more PPP weirdness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Jul 1998, Doug White wrote: > You probably have routed turned on, and it's hearing the RIP broadcasts. Nope, no routed running. Who would be sending these RIP broadcasts, anyway? Plus, if routed were fiddling with routes, it would show up in netstat -r[n] output, but that seems quite sane: Internet: Destination Gateway Flags Refs Use Netif Expire default 204.180.194.101 UGSc 2 38 tun0 10 link#1 UC 0 0 ed0 127.0.0.1 127.0.0.1 UH 0 1865 lo0 204.180.194.101 204.180.205.197 UH 3 0 tun0 Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 16:53:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12485 for freebsd-current-outgoing; Mon, 27 Jul 1998 16:53:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12403 for ; Mon, 27 Jul 1998 16:53:15 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id QAA19170; Mon, 27 Jul 1998 16:52:41 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd019082; Mon Jul 27 16:52:35 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id QAA06351; Mon, 27 Jul 1998 16:52:31 -0700 (MST) From: Terry Lambert Message-Id: <199807272352.QAA06351@usr05.primenet.com> Subject: Re: New LINT options: what is VM coloring? To: dyson@iquest.net Date: Mon, 27 Jul 1998 23:52:31 +0000 (GMT) Cc: tlambert@primenet.com, dfr@nlsystems.com, roberto@keltia.freenix.fr, freebsd-current@FreeBSD.ORG In-Reply-To: <199807272305.SAA02258@dyson.iquest.net> from "John S. Dyson" at Jul 27, 98 06:05:17 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But - but - but, the L1 cache is small!!! Is our terminology mixed-up? > > On X86en, L2 cache is the big one. I thought that on an Alpha, the > L3 cache is the big one. I don't know how one would fit the working > set into a 16K or even 128K cache?!?!?!? I can understand fitting > the working set into a 1M -> 4M L3 cache though :-). Maybe DEC hired coders from outside instead of bringing them over from their VMS division, where memory is free... 8-). What they call each of the caches is pretty standard, I think. Maybe it was a misprint in their white paper. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 17:16:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17841 for freebsd-current-outgoing; Mon, 27 Jul 1998 17:16:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17702 for ; Mon, 27 Jul 1998 17:15:27 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA06465; Mon, 27 Jul 1998 16:56:07 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdJi6445; Mon Jul 27 23:56:02 1998 Date: Mon, 27 Jul 1998 16:55:58 -0700 (PDT) From: Julian Elischer To: Mike Smith cc: Garrett Wollman , Luigi Rizzo , current@FreeBSD.ORG Subject: Re: SMP kernels... how many processes can be in ? In-Reply-To: <199807272007.NAA01087@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG trouble is that there needs to be some place to store data on a 'packet by packet' basis, The data is generated at one point in processing and needed at another.. but what if the packet gets queued in between? and how do you pass the information into (for example ip_input()) a function when the arguments of that function are alread defined and well known. What ever solution you have should be extensible so as to be used by as-yet un-thought-of users. The present method is to just use 'magic global variables' julian On Mon, 27 Jul 1998, Mike Smith wrote: > > < said: > > > > > 2/ sticking some 'MT_RIGHTS' or > > > 'MT_CONTROL' mbufs can be added on the head or end of the packet, and used > > > to hold this info. (encoded like tcp options.. 1 byte type, 1 byte len, > > > data.) > > > > Gross! Please don't do this! We have too much code that depends on > > mbuf chaining as it is! > > Ok, so we know what's "bad". Any suggestions on "less bad"? > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 17:49:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26782 for freebsd-current-outgoing; Mon, 27 Jul 1998 17:49:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from usr01.primenet.com (tlambert@usr01.primenet.com [206.165.6.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26681 for ; Mon, 27 Jul 1998 17:48:58 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id RAA16684 for current@freebsd.org; Mon, 27 Jul 1998 17:48:25 -0700 (MST) From: Terry Lambert Message-Id: <199807280048.RAA16684@usr01.primenet.com> Subject: Diagnostic for those with MMAP problems... To: current@FreeBSD.ORG Date: Tue, 28 Jul 1998 00:48:24 +0000 (GMT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like someone who can readily repeat these problems to try one or both of the following, and see what happens. I realize that the first is probably impractical for those repeating the glitch using INN, but it's worth mentioning. 1) Rebuild your kernel with NO_SWAPPING. This will help determine if this is a vnode pager problem, a generic pager problem, or a swap pager problem (by eliminating or indicting the swap pager). I realize that this implies you have a lot of RAM... 2) Rebuild the software using MMAP; add "PROT_WRITE" to the protection request. The logic behind this has to do with some suspicious partial page code which is XXX'ed in the comments in the VM sources, and for the COW code, which might be theoretically capable of leaking an alias (in other words, it selects a different code path that should match the write code path better than the fault code path). Basically, if this one fixes the symptom, it'll be bad in a different way because it will mean that the alias is recognized, and the file write ends up COW'ing the page. Note that msync() on FreeBSD is a kludge way of dealing with file extension of a backing object, and that a unified VM and buffer cache shouldn't need it. It's only use, really, is for transactioning, allowing user space code to force a commit of dirty data to the backing object. This should mean that adding PROT_WRITE will *NOT* require you to call msync(), contrary to the INN documentation. I would do this, but I don't really have a sandbox system I can use to run my simplified churning tests at this time, and I can't risk a non-sandbox system. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 19:03:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08990 for freebsd-current-outgoing; Mon, 27 Jul 1998 19:03:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08982 for ; Mon, 27 Jul 1998 19:02:55 -0700 (PDT) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id LAA31161; Tue, 28 Jul 1998 11:30:32 +0930 (CST) Received: from eddie.dsto.defence.gov.au ([131.185.2.111]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id PMP5W4MZ; Tue, 28 Jul 1998 11:30:51 +0930 Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id LAA01975; Tue, 28 Jul 1998 11:30:50 +0930 (CST) Message-ID: <35BD30D0.5131496B@dsto.defence.gov.au> Date: Tue, 28 Jul 1998 11:30:48 +0930 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: ben@rosengart.com CC: FreeBSD CURRENT , Brian Somers Subject: Re: ppp driving me nuts References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK that's not it, Well I have noticed user mode ppp behaving quite strangely on my system too recently. I have been getting periods of no modem activity in the middle of downloads and POP3 fetches of my mail when there is not reason for such. Possibly it's happening to you too and your provider is dropping the connection. I think there may be something wrong with user mode ppp in current right now (though I haven't updated the system it's happenning on for 2+ weeks - it's making the world now). I'm not complaining yet as I haven't investigated yet (I haven't increased my logging and looked at the logs). I think there have been a couple of other people mentioning something is wierd with their user ppp as well (Piere ?). Sent to the list for comments from others.... More info on my configuration will be forthcoming when I get home. Snob Art Genre wrote: > > On Tue, 28 Jul 1998, Matthew Thyer wrote: > > > set timeout 0 > > int: > # set ifaddr 207.38.248.13 204.180.194.1/24 255.255.255.0 > set phone 9891258 > set login "TIMEOUT 10 >-\\r-> ppp name:-\\r-name: float word: ********" > set timeout 0 > > Ben > > "You have your mind on computers, it seems." -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 19:47:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15454 for freebsd-current-outgoing; Mon, 27 Jul 1998 19:47:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell6.ba.best.com (jkb@shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15449 for ; Mon, 27 Jul 1998 19:47:00 -0700 (PDT) (envelope-from jkb@best.com) Received: from localhost (jkb@localhost) by shell6.ba.best.com (8.9.0/8.9.0/best.sh) with SMTP id TAA19485; Mon, 27 Jul 1998 19:46:29 -0700 (PDT) X-Authentication-Warning: shell6.ba.best.com: jkb owned process doing -bs Date: Mon, 27 Jul 1998 19:46:29 -0700 (PDT) From: "Jan B. Koum " X-Sender: jkb@shell6.ba.best.com To: ben@rosengart.com cc: current@FreeBSD.ORG Subject: Re: ppp driving me nuts In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think ppp has built in timeout if no packets go over the network: ppp ON rome> show timeout Idle Timer: 180 secs LQR Timer: 30 secs Retry Timer: 3 secs ppp ON rome> -- Yan Jan Koum jkb@best.com | "Turn up the lights; I don't want www.FreeBSD.org -- The Power to Serve | to go home in the dark." "Write longer sentences - they are paying us a lot of money" On Mon, 27 Jul 1998, Snob Art Genre wrote: >PPP is silently dropping my connection, every few minutes. Nothing in >the logs. Help! > > > > Ben > >"You have your mind on computers, it seems." > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 20:12:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19971 for freebsd-current-outgoing; Mon, 27 Jul 1998 20:12:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (kong@kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19786 for ; Mon, 27 Jul 1998 20:12:13 -0700 (PDT) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id HAA10178; Tue, 28 Jul 1998 07:09:42 +0400 (MSD) (envelope-from kong@kong.dorms.spbu.ru) Date: Tue, 28 Jul 1998 07:09:41 +0400 (MSD) From: Hostas Red To: Doug White cc: current@FreeBSD.ORG Subject: Re: Strange idle times In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! On Mon, 27 Jul 1998, Doug White wrote: > > > Corrupted utmp/wtmp perhaps? Something trying to use the old format? > > > > But why? I'm sitting on -current for more than half a year already and i'm > > rebooting sometimes :). wtmp rolls daily, utmp brand new after rebooting > > half an hour ago. And problem still exitst, after one more 'make world'. > > Perhaps you have a program using the old format, like ssh? I'm having > this problem with our house router (I need to fix that). Hmmm... Yes, I'm using ssh frequently, but it is fresh-compiled (1.2.26, rebuild couple of weeks ago, but problem exist at least for a month). Or it doesn't matter? Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 22:24:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04363 for freebsd-current-outgoing; Mon, 27 Jul 1998 22:24:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04349 for ; Mon, 27 Jul 1998 22:24:22 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id BAA13856; Tue, 28 Jul 1998 01:23:46 -0400 (EDT) Date: Tue, 28 Jul 1998 01:23:46 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: "Jan B. Koum " cc: ben@rosengart.com, current@FreeBSD.ORG Subject: Re: ppp driving me nuts In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Jul 1998, Jan B. Koum wrote: > I think ppp has built in timeout if no packets go over the > network: > ppp ON rome> show timeout > Idle Timer: 180 secs LQR Timer: 30 secs Retry Timer: 3 secs > ppp ON rome> This happens during telnet sessions. Anyway: PPP ON narcissus> show timeout Warning: show timeout: Invalid command Warning: show timeout: Failed 1 Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 22:44:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06385 for freebsd-current-outgoing; Mon, 27 Jul 1998 22:44:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA06375 for ; Mon, 27 Jul 1998 22:44:17 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id FAA04809; Tue, 28 Jul 1998 05:50:58 +0200 From: Luigi Rizzo Message-Id: <199807280350.FAA04809@labinfo.iet.unipi.it> Subject: Re: SMP kernels... how many processes can be in ? To: julian@whistle.com (Julian Elischer) Date: Tue, 28 Jul 1998 05:50:57 +0200 (MET DST) Cc: mike@smith.net.au, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG In-Reply-To: from "Julian Elischer" at Jul 27, 98 04:55:39 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > trouble is that there needs to be some place to store data > on a 'packet by packet' basis, The data is generated at one point in > processing and needed at another.. > but what if the packet gets queued in between? that's a minor problem in a sence because the queue must have room for the additional info in whatever form you need. > and how do you pass the information into (for example ip_input()) > a function when the arguments of that function are alread defined and well > known. What ever solution you have should be extensible so as to be used > by as-yet un-thought-of users. my idea (similar in principle to the mbuf one you propose) is to adopt one (or a set) of special structs which the caller fills up with all parameters it needs. The called function (say ip_input in this case) first checks its args and if they correspond to the special struct then operates specially. Something like struct xyz_parms { T a ; T2 b ; struct mbuf *m ; } xyz_arg ; In the caller: ... xyz_arg.m = m ; xyz_arg.a = ... ' ip_input ( struct mbuf *)&xyz_arg ); in the called fn: ip_input(struct mbuf *m) { if (m == (struct mbuf *)&xyz_arg ) { struct xyz_parms *p = (struct xyz_parms *)m ; m = p-> m ; /* do special processing with p->a */ } ... My problem is, do we have multiple instances of the kernel running in parallel, so that i need an array of xyz_arg[], one per CPU ? And if this is the case, how do i know the CPU i am running on, so that i can assign the right xyz_arg[i] without having to use locks to allocate them ? luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 22:53:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07090 for freebsd-current-outgoing; Mon, 27 Jul 1998 22:53:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles329.castles.com [208.214.167.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07085 for ; Mon, 27 Jul 1998 22:52:51 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA00911; Mon, 27 Jul 1998 22:51:13 -0700 (PDT) Message-Id: <199807280551.WAA00911@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Luigi Rizzo cc: julian@whistle.com (Julian Elischer), mike@smith.net.au, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Subject: Re: SMP kernels... how many processes can be in ? In-reply-to: Your message of "Tue, 28 Jul 1998 05:50:57 +0200." <199807280350.FAA04809@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 22:51:13 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > trouble is that there needs to be some place to store data > > on a 'packet by packet' basis, The data is generated at one point in > > processing and needed at another.. > > but what if the packet gets queued in between? > > that's a minor problem in a sence because the queue must have room for > the additional info in whatever form you need. > > > and how do you pass the information into (for example ip_input()) > > a function when the arguments of that function are alread defined and well > > known. What ever solution you have should be extensible so as to be used > > by as-yet un-thought-of users. > > my idea (similar in principle to the mbuf one you propose) is to > adopt one (or a set) of special structs which the caller fills up with > all parameters it needs. The called function (say ip_input in this > case) first checks its args and if they correspond to the special > struct then operates specially. Something like > > struct xyz_parms { > T a ; > T2 b ; > struct mbuf *m ; > } xyz_arg ; > > In the caller: > > ... > xyz_arg.m = m ; > xyz_arg.a = ... ' > > ip_input ( struct mbuf *)&xyz_arg ); > > in the called fn: > > ip_input(struct mbuf *m) > { > > if (m == (struct mbuf *)&xyz_arg ) { > struct xyz_parms *p = (struct xyz_parms *)m ; > > m = p-> m ; > /* do special processing with p->a */ > } > ... > > My problem is, do we have multiple instances of the kernel running in > parallel, so that i need an array of xyz_arg[], one per CPU ? And if > this is the case, how do i know the CPU i am running on, so that i can > assign the right xyz_arg[i] without having to use locks to allocate > them ? Given that what you're trying to do is pass state with the packet(s) that you're putting onto the queue, rather than associate state with a particular quantum of execution in the kernel space, wouldn't it make more sense to queue a non-IP control packet to pass your state around? This would allow, eg. for kernel preemption between the 'first' and 'second' functions, and keeps the state in question associated with the packet(s) rather than in some global variable. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 23:00:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07840 for freebsd-current-outgoing; Mon, 27 Jul 1998 23:00:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sarah.asstdc.com.au (root@sarah.asstdc.com.au [202.12.127.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07789 for ; Mon, 27 Jul 1998 23:00:04 -0700 (PDT) (envelope-from imb@pni.ab.ca) Received: from walkabout.asstdc.com.au (root@localhost [127.0.0.1]) by sarah.asstdc.com.au (8.8.7/BSD4.4) with SMTP id PAA10664; Tue, 28 Jul 1998 15:59:02 +1000 (EST) Message-Id: <3.0.5.32.19980727235858.007f6100@localhost> X-Sender: imb@localhost X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 27 Jul 1998 23:58:58 -0600 To: ben@rosengart.com, Doug White From: michael butler Subject: Re: more PPP weirdness Cc: current@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- At 19:49 27/7/98 -0400, Snob Art Genre wrote: >> You probably have routed turned on, and it's hearing the RIP broadcasts. >Nope, no routed running. Who would be sending these RIP broadcasts, >anyway? Plus, if routed were fiddling with routes, it would show up in >netstat -r[n] output, but that seems quite sane: User-mode ppp is simply reporting what it sees in the forwarding table since it makes no distinction between the intended routes and those which are cloned/cached to specific hosts. It is, in fact, reporting exactly what "netstat -ra[n]" will show. These cloned routes will (eventually) expire given a sufficiently long up-time, Michael -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.5.3i for non-commercial use iQCVAwUBNb1ooRIU3H6iGYQlAQFcgQQA0M06j5k9cMfXlsh/zl2O+ITyM1eGfH9K +//D+iDgWyI3AbDZY2gcacgJaaZ9GRVLetrjCIqzqSGjCf0Qnzh+s+/MIkXJKQ6C U/CEYCQLHkDS1W/bok5G8oP5ccuSTbnCJimSvJ9M7t8dMJebKNysEOOD2NKvbBhR FhOcYrK3ntc= =f/NQ -----END PGP SIGNATURE----- -- InterNIC: IMB PGP Key-Id: 0xA2198425 PGP Finger-Print: 7729 051C 7CA0 8AC2 30F0 8526 E53F 1A19 ICQ: 146868 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 23:03:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08147 for freebsd-current-outgoing; Mon, 27 Jul 1998 23:03:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA08124 for ; Mon, 27 Jul 1998 23:03:05 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA04868; Tue, 28 Jul 1998 06:10:10 +0200 From: Luigi Rizzo Message-Id: <199807280410.GAA04868@labinfo.iet.unipi.it> Subject: Re: SMP kernels... how many processes can be in ? To: mike@smith.net.au (Mike Smith) Date: Tue, 28 Jul 1998 06:10:10 +0200 (MET DST) Cc: julian@whistle.com, mike@smith.net.au, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG In-Reply-To: <199807280551.WAA00911@antipodes.cdrom.com> from "Mike Smith" at Jul 27, 98 10:50:54 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Given that what you're trying to do is pass state with the packet(s) > that you're putting onto the queue, rather than associate state with a > particular quantum of execution in the kernel space, wouldn't it make > more sense to queue a non-IP control packet to pass your state around? queueing is no problem, the problem is doing things without calling interfaces for the functions involved in the process or the packet structure. In both cases the reason not to change current interfaces is that they are widely used both in source code and documentation and you never know if you fixed all places. I already burned myself once by adding a field in the struct mbuf, to discover that i had to fix ten or so source files (and who knows if i have forgotten some) because mbufs are not initialized on allocation and so i do not know what is in my new field (of course i could have fixed the mbuf allocator... but we learn by mistakes...). Now before doing that again i want to get someone else's opinion on what would be a better solution (and possibly avoiding global vars of course). cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 23:14:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10162 for freebsd-current-outgoing; Mon, 27 Jul 1998 23:14:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from a486n1.znh.org (dialup6.gaffaneys.com [208.155.161.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10156 for ; Mon, 27 Jul 1998 23:14:40 -0700 (PDT) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by a486n1.znh.org (8.8.8/8.8.8) id GAA10054; Tue, 28 Jul 1998 06:20:17 GMT (envelope-from zach) Message-ID: <19980728012017.A8579@znh.org.> Date: Tue, 28 Jul 1998 01:20:17 -0500 From: Zach Heilig To: ben@rosengart.com, Doug White Cc: current@FreeBSD.ORG Subject: Re: more PPP weirdness References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Snob Art Genre on Mon, Jul 27, 1998 at 07:49:36PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 27, 1998 at 07:49:36PM -0400, Snob Art Genre wrote: > > You probably have routed turned on, and it's hearing the RIP broadcasts. > Nope, no routed running. Who would be sending these RIP broadcasts, > anyway? Plus, if routed were fiddling with routes, it would show up in > netstat -r[n] output, but that seems quite sane: FWIW, I'm seeing the same symptoms here. I haven't actually noticed any real problems though. (no routed here either). -- Zach Heilig -- zach@gaffaneys.com Real Programs don't use shared text. Otherwise, how can they use functions for scratch space after they are finished calling them? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 23:17:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10513 for freebsd-current-outgoing; Mon, 27 Jul 1998 23:17:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA10449 for ; Mon, 27 Jul 1998 23:17:25 -0700 (PDT) (envelope-from foo@bar.com) Received: (qmail 19872 invoked from network); 28 Jul 1998 06:16:54 -0000 Received: from userk796.uk.uudial.com (HELO bar.com) (193.149.72.118) by smtp.dial.pipex.com with SMTP; 28 Jul 1998 06:16:54 -0000 Message-ID: <35BD6C4E.B72F9DAB@bar.com> Date: Tue, 28 Jul 1998 07:14:38 +0100 From: Foo Yong X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: ben@rosengart.com, current@FreeBSD.ORG Subject: Re: ppp driving me nuts References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Snob Art Genre wrote: > > PPP ON narcissus> show timeout > Warning: show timeout: Invalid command > Warning: show timeout: Failed 1 > Did you mean show timers: PPP ON roadrunner> show ? (o) = Optional context, (c) = Context required bundle : bundle details ccp(o) : CCP status compress : VJ compression stats escape(c) : escape characters filter : packet filters hdlc(c) : HDLC errors ipcp : IPCP status lcp(c) : LCP status link(c) : (high-level) link info links : available link names log : log levels mem : mbuf allocations modem(c) : (low-level) link info mp : multilink setup proto(o) : protocol summary route : routing table stopped(c): STOPPED timeout timers : alarm timers version : version string who : client list help : Display this message PPP ON roadrunner> show timers IPCP throughput timer[0x48318]: freq = 1.00s, next = 0.10s, state = running modem throughput timer[0x65040]: freq = 1.00s, next = 0.60s, state = running modem CD timer[0x6765c]: freq = 1.00s, next = 1.00s, state = running hdlc timer[0x67310]: freq = 60.00s, next = 20.00s, state = running idle timer[0x49534]: freq = 300.00s, next = 125.70s, state = running PPP ON roadrunner> I did have problems a while ago, related to the fact that I was trying to use my ESP at or above 230400 bps, but I don't think this is related... I don't experience the weirdness you describe on a system just cvsupped from this morning, should I send you my conf files ? I do use a ppp.linkdown to get rid of the route when the link goes down and reinstate the pseudo one, this might help. Best Regards, Pierre Y. (Funny how many people have problems spelling the most common French first name...) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 23:19:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10858 for freebsd-current-outgoing; Mon, 27 Jul 1998 23:19:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles329.castles.com [208.214.167.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10819 for ; Mon, 27 Jul 1998 23:19:05 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA01083; Mon, 27 Jul 1998 23:17:44 -0700 (PDT) Message-Id: <199807280617.XAA01083@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Luigi Rizzo cc: mike@smith.net.au (Mike Smith), julian@whistle.com, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Subject: Re: SMP kernels... how many processes can be in ? In-reply-to: Your message of "Tue, 28 Jul 1998 06:10:10 +0200." <199807280410.GAA04868@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 23:17:43 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Given that what you're trying to do is pass state with the packet(s) > > that you're putting onto the queue, rather than associate state with a > > particular quantum of execution in the kernel space, wouldn't it make > > more sense to queue a non-IP control packet to pass your state around? > > queueing is no problem, the problem is doing things without calling > interfaces for the functions involved in the process or the packet > structure. I presume you mean "changing" rather than "calling". And this is what I mean; you effectively add extra arguments to the functions in question by putting them into an mbuf rather than on the stack. It also means that you can decouple the call from the invocation, if that's any use. > In both cases the reason not to change current interfaces is that they > are widely used both in source code and documentation and you never > know if you fixed all places. Understood. 8( -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 27 23:51:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15638 for freebsd-current-outgoing; Mon, 27 Jul 1998 23:51:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15611 for ; Mon, 27 Jul 1998 23:50:50 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from pilot.physics.adelaide.edu.au (pilot [129.127.36.15]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id QAA06383; Tue, 28 Jul 1998 16:20:12 +0930 (CST) Received: by pilot.physics.adelaide.edu.au (5.61+IDA+MU/UA-5.23) id AA15809; Tue, 28 Jul 1998 16:13:41 +0930 Date: Tue, 28 Jul 1998 16:13:41 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@pilot To: "Jan B. Koum " Cc: ben@rosengart.com, current@FreeBSD.ORG Subject: Re: ppp driving me nuts In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Jul 1998, Jan B. Koum wrote: > I think ppp has built in timeout if no packets go over the > network: > ppp ON rome> show timeout > Idle Timer: 180 secs LQR Timer: 30 secs Retry Timer: 3 secs > ppp ON rome> I seem to recall that theres a 3 minute idle timeout which cannot be overridden if you start the ppp session from interactive mode. I often find that my PPP session does not start packet mode automatically when I connect (but sometimes does), so I need to quit, restart, go to term mode (it won't let me just go straight to term mode without restarting) and do a ~p to trigger it. I've also found a lot of 'silent' dropouts (nothing in the logs, and the ppp driver does not seem to detect the line being down: it continues to send packets to the modem as shown by the transmission status lights). At other times I've been getting lots of repeated dropouts due to data errors (logged, which I can hunt around for and send in if required), but if I reconnect straight away using pppd I never have problems (I guess either pppd is much more forgiving of stuff like noise on the modem line, or ppp has a small bug) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 00:02:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17205 for freebsd-current-outgoing; Tue, 28 Jul 1998 00:02:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17082 for ; Tue, 28 Jul 1998 00:02:03 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id IAA21846; Tue, 28 Jul 1998 08:01:16 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807280701.IAA21846@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: ben@rosengart.com cc: current@FreeBSD.ORG Subject: Re: ppp driving me nuts In-reply-to: Your message of "Mon, 27 Jul 1998 17:20:15 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 08:01:15 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > PPP is silently dropping my connection, every few minutes. Nothing in > the logs. Help! What logs have you got ? Try set log command phase chat lcp ipcp and if that doesn't work, add ``debug''. > Ben > > "You have your mind on computers, it seems." -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 00:04:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17558 for freebsd-current-outgoing; Tue, 28 Jul 1998 00:04:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17451 for ; Tue, 28 Jul 1998 00:03:53 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.8/8.7.3) id JAA05381; Tue, 28 Jul 1998 09:03:04 +0200 (CEST) From: Holm Tiffe Message-Id: <199807280703.JAA05381@magnet.geophysik.tu-freiberg.de> Subject: Answering myself, was: URGENT! ASUS P2B/LS supported ? To: freebsd-current@FreeBSD.ORG Date: Tue, 28 Jul 1998 09:03:03 +0200 (CEST) Cc: bloom@acm.org Reply-To: freebsd@magnet.geophysik.tu-freiberg.de X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hi all, > >I need to know urgently if the onboard peripherals from the ASUS >P2B/LS Motherboard are supported under -current. > >On the ASUS website is the following information: > > Onboard Intel 82558 fast Ethernet LAN Controller > Onboard Adaptec AIC 7890 & AIC 3860 (option) 80 MBPS Ultra 2 Wide SCSI > Intel 440BX AGP Chipset > >I whish to use a Matrox Millenium II AGP in this board. > >Ist this supported ? >Should I buy this board ? >Should I buy the Matrox ? I've got no answer on this, but yesterday I have moved my System from an oldish 486/80 EISA MB to this Asus board with 100Mc busclock and a P2/350. The Machine is running fine, the AIC 7890 is supported from our CAM SCSI drivers, and the onboard Ethernet (I82558) works flawlessly whit the fxp driver. (only 10 Base T testet) Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 00:06:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18235 for freebsd-current-outgoing; Tue, 28 Jul 1998 00:06:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18153 for ; Tue, 28 Jul 1998 00:06:24 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id IAA21873; Tue, 28 Jul 1998 08:05:32 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807280705.IAA21873@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: ben@rosengart.com cc: current@FreeBSD.ORG Subject: Re: more PPP weirdness In-reply-to: Your message of "Mon, 27 Jul 1998 18:34:05 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 08:05:32 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All the W routes are cloned routes. In theory, these routes disappear when the route they were cloned from disappears. If you add delete ALL add default HISADDR to your ppp.linkup, does that fix the problem ? I think the problem *may* be that a ``changed'' route isn't fixing the routing table in the way that a ``deleted'' then ``added'' route is. > PPP ON narcissus> show route > Destination Gateway Flags Netif > default 204.180.194.101 UGSc tun0 > 10/8 link#1 UC ed0 > 18.23.0.16 204.180.194.101 UGHW3 tun0 > 38.180.208.198 204.180.194.101 UGHW3 tun0 > 127.0.0.1 127.0.0.1 UH lo0 > 128.10.11.72 204.180.194.101 UGHW tun0 > 128.193.76.12 204.180.194.101 UGHW3 tun0 > 137.22.4.31 204.180.194.101 UGHW3 tun0 > 141.117.1.117 204.180.194.101 UGHW3 tun0 > 152.1.2.118 204.180.194.101 UGHW3 tun0 > 152.1.9.90 204.180.194.101 UGHW3 tun0 > 164.107.115.3 204.180.194.101 UGHW3 tun0 > 198.67.15.2 204.180.194.101 UGHW tun0 > 199.184.165.2 204.180.194.101 UGHW tun0 > 204.180.194.101 204.180.205.197 UH tun0 > 206.137.222.89 204.180.194.101 UGHW3 tun0 > > netstat -rn reports my routing tables as being quite normal. Now, I may > be misunderstanding, but it looks like PPP is seeing all these hosts as > gateways, in which case no wonder it's getting confused. When I grabbed > this table from PPP, it was "up" but no packets were getting anywhere. > I down'd and quit and dialed again, and now PPP works, but: > > PPP ON narcissus> show route > Destination Gateway Flags Netif > default 204.180.194.101 UGSc tun0 > 10/8 link#1 UC ed0 > 127.0.0.1 127.0.0.1 UH lo0 > 198.67.15.2 204.180.194.101 UGHW tun0 > 199.184.165.2 204.180.194.101 UGHW tun0 > 204.180.194.101 204.180.205.197 UH tun0 > > The gateways are growing again. Perhaps this is completely normal, and > I'm misunderstanding something? Or perhaps there's just a flipped bit > somewhere, since the only PPP-related host route not marked as a gateway > is -- my gateway. > > > Ben > > "You have your mind on computers, it seems." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 00:30:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22075 for freebsd-current-outgoing; Tue, 28 Jul 1998 00:30:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21933 for ; Tue, 28 Jul 1998 00:30:02 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id JAA22161 ; Tue, 28 Jul 1998 09:28:12 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id JAA27469; Tue, 28 Jul 1998 09:28:10 +0200 To: Doug White Cc: Hostas Red , current@FreeBSD.ORG Subject: Re: Strange idle times References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 28 Jul 1998 09:28:08 +0200 In-Reply-To: Doug White's message of Mon, 27 Jul 1998 15:12:18 -0700 (PDT) Message-ID: Lines: 25 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White writes: > On Sat, 25 Jul 1998, Hostas Red wrote: > > > > About one month or so i have a strange idle times on my -current (really > > > > current - 1 hour or so :) - whenever i use 'w' or 'finger' idle time of > > > > users equivalent to uptime (maybe 1 minute less). ;-( > > > Corrupted utmp/wtmp perhaps? Something trying to use the old format? > > But why? I'm sitting on -current for more than half a year already and i'm > > rebooting sometimes :). wtmp rolls daily, utmp brand new after rebooting > > half an hour ago. And problem still exitst, after one more 'make world'. > Perhaps you have a program using the old format, like ssh? I'm having > this problem with our house router (I need to fix that). I checked, and I have the same problem on my -current box. All my vtys and ptys show up with as much idle time as the machine's uptime. I ssh a lot öut"from this box, but very little *into* it, so the fubared ptys are mostly xterms. On my laptop (also running -current), I have an xterm which shows up with twice as much idle time as the machine's uptime, though that is caused by a bug (feature?) in the uptime calculation (time during which the machine is suspended isn't counted as uptime) DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 02:00:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04422 for freebsd-current-outgoing; Tue, 28 Jul 1998 02:00:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04337 for ; Tue, 28 Jul 1998 01:59:59 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id EAA04617; Tue, 28 Jul 1998 04:59:22 -0400 (EDT) Date: Tue, 28 Jul 1998 04:59:22 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Kris Kennaway cc: "Jan B. Koum " , current@FreeBSD.ORG Subject: Re: ppp driving me nuts In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Jul 1998, Kris Kennaway wrote: > I seem to recall that theres a 3 minute idle timeout which cannot be > overridden if you start the ppp session from interactive mode. I often Why wouldn't "set timeout 0" override? I load my provider profile with a "load" directive in the conf file, and just log in as ppp with ppp as my shell and type "dial", btw. And a "show timers" doesn't show any idle timer running. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 02:59:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10992 for freebsd-current-outgoing; Tue, 28 Jul 1998 02:59:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10981 for ; Tue, 28 Jul 1998 02:59:44 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id TAA07364; Tue, 28 Jul 1998 19:13:14 +0930 (CST) Received: by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA28006; Tue, 28 Jul 1998 19:13:13 +0930 Date: Tue, 28 Jul 1998 19:13:13 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@mercury To: ben@rosengart.com Cc: "Jan B. Koum " , current@FreeBSD.ORG Subject: Re: ppp driving me nuts In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Jul 1998, Snob Art Genre wrote: > On Tue, 28 Jul 1998, Kris Kennaway wrote: > > > I seem to recall that theres a 3 minute idle timeout which cannot be > > overridden if you start the ppp session from interactive mode. I often > > Why wouldn't "set timeout 0" override? I load my provider profile with > a "load" directive in the conf file, and just log in as ppp with ppp as > my shell and type "dial", btw. And a "show timers" doesn't show any > idle timer running. I just know that doing that never seemed to prevent the session from timing out after 3 minutes. I was going to get around to investigating this further & submitting a formal report, but it seems to have come up anyway :) I also seem to remember something about the redial timeout not quite working as it is documented in the manpages.. Kris > > > Ben > > "You have your mind on computers, it seems." > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 03:14:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA13246 for freebsd-current-outgoing; Tue, 28 Jul 1998 03:14:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA13240 for ; Tue, 28 Jul 1998 03:14:41 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id MAA12774; Tue, 28 Jul 1998 12:13:56 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Tue, 28 Jul 1998 12:13:56 +0200 (MET DST) Mime-Version: 1.0 To: Kris Kennaway Cc: ben@rosengart.com, "Jan B. Koum " , current@FreeBSD.ORG Subject: Re: ppp driving me nuts References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 28 Jul 1998 12:13:55 +0200 In-Reply-To: Kris Kennaway's message of "Tue, 28 Jul 1998 19:13:13 +0930 (CST)" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA13241 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway writes: > I just know that doing that never seemed to prevent the session from > timing out after 3 minutes. I was going to get around to > investigating this further & submitting a formal report, but it seems to > have come up anyway :) Your ISP might have an idle timer too. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 03:37:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16924 for freebsd-current-outgoing; Tue, 28 Jul 1998 03:37:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16919 for ; Tue, 28 Jul 1998 03:37:24 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id UAA07571; Tue, 28 Jul 1998 20:06:43 +0930 (CST) Received: by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA29021; Tue, 28 Jul 1998 20:06:41 +0930 Date: Tue, 28 Jul 1998 20:06:41 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@mercury To: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= Cc: ben@rosengart.com, "Jan B. Koum " , current@FreeBSD.ORG Subject: Re: ppp driving me nuts In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28 Jul 1998, Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= wrote: > Your ISP might have an idle timer too. Yup, but that presumably wouldnt show up in the logs as "idle timeout expired; closing session" (paraphrased) :-) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 04:09:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA21039 for freebsd-current-outgoing; Tue, 28 Jul 1998 04:09:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA21027 for ; Tue, 28 Jul 1998 04:09:42 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.8/8.7.3) id NAA00456; Tue, 28 Jul 1998 13:08:58 +0200 (CEST) From: Holm Tiffe Message-Id: <199807281108.NAA00456@magnet.geophysik.tu-freiberg.de> Subject: Re: Answering myself, was: URGENT! ASUS P2B/LS supported ? In-Reply-To: <19980728051057.A14534@net.ohio-state.edu> from Mark Fullmer at "Jul 28, 98 05:10:57 am" To: maf@net.ohio-state.edu (Mark Fullmer) Date: Tue, 28 Jul 1998 13:08:58 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG Reply-To: freebsd@magnet.geophysik.tu-freiberg.de X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The Machine is running fine, the AIC 7890 is supported from our > > CAM SCSI drivers, and the onboard Ethernet (I82558) works > > flawlessly whit the fxp driver. (only 10 Base T testet) > > Do you get the following error on boot? > > pci_map_mem failed: bad memory type=0xfffff004 > No, no problems at all, where do you get this message ? After the initializing of the NIC or what ? Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 04:31:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA24803 for freebsd-current-outgoing; Tue, 28 Jul 1998 04:31:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA24708; Tue, 28 Jul 1998 04:30:34 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA32437; Tue, 28 Jul 1998 21:29:50 +1000 Date: Tue, 28 Jul 1998 21:29:50 +1000 From: Bruce Evans Message-Id: <199807281129.VAA32437@godzilla.zeta.org.au> To: dwhite@resnet.uoregon.edu, smoergrd@oslo.geco-prakla.slb.com Subject: Re: Strange idle times Cc: current@FreeBSD.ORG, kong@kong.spb.ru, phk@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I checked, and I have the same problem on my -current box. All my vtys >and ptys show up with as much idle time as the machine's uptime. I ssh >a lot öut"from this box, but very little *into* it, so the fubared >ptys are mostly xterms. Strange idle times used to be caused by mounting with -noatime. I fixed this a few weeks ago by ignoring -noatime for special files. Yesterday I enabled a better optimization for all timestamps on special files. Perhaps something in you configuration breaks this optimization. >On my laptop (also running -current), I have an xterm which shows up >with twice as much idle time as the machine's uptime, though that is >caused by a bug (feature?) in the uptime calculation (time during >which the machine is suspended isn't counted as uptime) Bug. APM calls inittodr() and inittodr() calls set_timecounter(). set_timecounter() does extra work to mess up the boot time :-). This is also a problem in settimeofday(). Suppose that the boot time and the current time were originally set correctly, but the current time has drifted and you're calling settimeofday() to fix it. Then the boot time hasn't changed, so it shouldn't be adjusted, but it is. This is essentially the same problem as in APM. OTOH, when both the boot time and the current time are initially set incorrectly because the RTC is on wall clock time or just slightly wrong, then settimeofday needs to adjust both. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 05:10:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29121 for freebsd-current-outgoing; Tue, 28 Jul 1998 05:10:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29101; Tue, 28 Jul 1998 05:10:11 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id OAA03557 ; Tue, 28 Jul 1998 14:08:22 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id OAA28294; Tue, 28 Jul 1998 14:08:20 +0200 To: Bruce Evans Cc: dwhite@resnet.uoregon.edu, current@FreeBSD.ORG, kong@kong.spb.ru, phk@FreeBSD.ORG Subject: Re: Strange idle times References: <199807281129.VAA32437@godzilla.zeta.org.au> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 28 Jul 1998 14:08:19 +0200 In-Reply-To: Bruce Evans's message of Tue, 28 Jul 1998 21:29:50 +1000 Message-ID: Lines: 13 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > Strange idle times used to be caused by mounting with -noatime. I fixed > this a few weeks ago by ignoring -noatime for special files. Yesterday > I enabled a better optimization for all timestamps on special files. > Perhaps something in you configuration breaks this optimization. I don't have any file systems mounted -noatime (there's not much point since they're all running soft updates). What are the other potential culprits? DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 05:15:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29788 for freebsd-current-outgoing; Tue, 28 Jul 1998 05:15:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29778 for ; Tue, 28 Jul 1998 05:15:10 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id FAA08699 for ; Tue, 28 Jul 1998 05:13:16 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: current@FreeBSD.ORG Subject: Advance announcement for 2.2.8 and some changes. Date: Tue, 28 Jul 1998 05:13:15 -0700 Message-ID: <8694.901627995@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just so nobody can claim that I'm going to sneak another -stable release out the door, let me just announce it NOW with plenty of advance notice! :-) The official release date for FreeBSD 2.2.8 is November 15th, 1998. This will be the LAST release along the 2.2 branch, at which point it will be well and truly dead except for a very small amount of security and other types of similar "nasty bug" fixing for the benefit of those who continue to sync themselves to the 2.2-stable branch. Since 3.0 is scheduled for release on October 15th, I figure that by the time people are looking to upgrade again sometime in Q1 of 1999, we'll have enough of the rough edges filed off for people to make a full and reasonable committment to 3.0.x. Again, November 15th is the date and I'm not going to change it, so just mark it now on your calendars and don't claim that I didn't warn you when the time comes around - I expect everyone to remember this date and, if they don't, it's their own darn fault. I may or may not make another announcement closer to that date, so simply take it as read that November 15th is the date in question and if you forget and start gritching come November, I'm merely going to forward this message to you again and say "I scheduled this almost 4 months ago and announced it widely, so it's not *my* fault if you have Alzheimers!" :-) Now that we've got that out of the way, I'd also like to make some changes to the way 2.2.x has been maintained. Rather than do a merge from hell right before the 2.2.8 release, like I did for 2.2.6 and 2.2.7, I'm just going to expect the committers to back-port any work they do in -current which fits the classic definition of something which should go into -stable (obvious bug fix, low impact, no significant new functionality unless it fixes something which is seriously broken [like MSDOSfs], etc.). If you don't take care to merge it, don't be surprised if it doesn't make it into 2.2.8 since I refuse to take that all on my own shoulders again. The quality of this last release of 2.2 will rest squarely with the committers and the various users who can help by spotting things in 3.0 which really should be back-ported and reporting that to committers@freebsd.org. Once more, 2.2.8 is going to be the VERY LAST release on the 2.2-stable branch and if you want to make it a worthy cap for what has been a highly successful line, there's no time like the present for thinking about what you need to merge. The sooner you do the work, the more time the CVSup/CTMers of 2.2-stable will also have for testing it and seeing if there are any unforseen side-effects. I propose to freeze the branch on November 7th, so please don't leave it to the last minute like everyone always does - once this release is out the door, there won't be a second chance for the 2.2 branch! This has been a public service announcement. :) Thanks! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 05:35:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA03015 for freebsd-current-outgoing; Tue, 28 Jul 1998 05:35:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA03010 for ; Tue, 28 Jul 1998 05:35:54 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id HAA00430 for ; Tue, 28 Jul 1998 07:35:24 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id HAA18439; Tue, 28 Jul 1998 07:35:24 -0500 (CDT) Message-ID: <19980728073523.02311@mcs.net> Date: Tue, 28 Jul 1998 07:35:23 -0500 From: Karl Denninger To: current@FreeBSD.ORG Subject: Serious Dump problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I have an interesting one here... I have a dump tape which is intact, yet restore complains about "hole in map" and segv's when attempting to start up in interactive mode. It appears that dump and restore are VERY old, and nobody is maintaining them. Interestingly enough, a new dump of the same filesystem produces the same error, so I suspect a problem with dump where it is writing out a bad directory map. Any ideas on this one? Is there a more recent set of sources available somewhere that might not display this problem? Needless to say, unrestorable tapes are not my idea of a good time! -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 05:50:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04502 for freebsd-current-outgoing; Tue, 28 Jul 1998 05:50:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from door.barclayscapital.com (www.barclayscapital.com [194.205.158.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04496 for ; Tue, 28 Jul 1998 05:50:52 -0700 (PDT) (envelope-from Pierre.Dampure@barclayscapital.com) From: Pierre.Dampure@barclayscapital.com Received: (from mailman@localhost) by door.barclayscapital.com (8.8.8/8.8.7) id NAA11504 for ; Tue, 28 Jul 1998 13:48:40 +0100 (BST) Received: from gate.barclayscapital.com(194.205.158.68) by door.bzw.com via smap (V2.0) id xma011294; Tue, 28 Jul 98 13:48:17 +0100 Received: (from nobody@localhost) by gate.bzw.com (8.8.7/8.8.7) id NAA04509 for ; Tue, 28 Jul 1998 13:49:54 +0100 (BST) Received: from fwgw01-dmz(194.205.158.129) by gate.bzw.com via smap (V2.0) id xma004492; Tue, 28 Jul 98 13:49:51 +0100 Received: (from nobody@localhost) by fwgw01.ldn.bzwint.com (8.8.7/8.8.7) id NAA21176 for ; Tue, 28 Jul 1998 13:49:51 +0100 (BST) Received: from oplss0001.itops.ldn.bzwint.com(30.75.1.4) by fwgw01.ldn.bzwint.com via smap (V2.0) id xma021170; Tue, 28 Jul 98 13:49:47 +0100 Received: from nmb01gw01 (smtphost.ldn.bzwint.com [30.10.1.10]) by oplss0001.itops.ldn.bzwint.com (8.8.7/8.8.6) with SMTP id NAA27810 for ; Tue, 28 Jul 1998 13:48:45 +0100 (BST) Received: from EXMSMCON02.fmcs.ldn.bzwint.com (EXMSMCON02.fmcs.ldn.bzwint.com [30.81.1.2]) by nmb01gw01 (NTMail 3.02.13) with ESMTP id ya196402 for ; Tue, 28 Jul 1998 13:42:38 +0100 Received: from exintgw03.itops.ldn.bzwint.com (unverified [30.45.1.86]) by exmsmcon02 (Integralis SMTPRS 2.0.15) with ESMTP id for ; Tue, 28 Jul 1998 13:46:36 +0100 Received: by exintgw03.itops.ldn.bzwint.com with Internet Mail Service (5.0.1460.8) id ; Tue, 28 Jul 1998 13:43:18 +0100 Message-Id: <711DCB8FB391D111B9DD00805F8BDDBA726399@exips0019.itops.ldn.bzwint.com> To: FreeBSD-Current@FreeBSD.ORG Subject: 3.3.2-patch3 Date: Tue, 28 Jul 1998 13:44:17 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1460.8) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can somebody incorporate the above (released July 25th) in PATCHFILES and files/md5 ? Best Regards, Pierre Y. ************************************************************************************** Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group unless otherwise specifically stated. ************************************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 06:22:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA08871 for freebsd-current-outgoing; Tue, 28 Jul 1998 06:22:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA08822 for ; Tue, 28 Jul 1998 06:22:00 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id PAA01418 for ; Tue, 28 Jul 1998 15:18:46 +0200 (CEST) To: current@FreeBSD.ORG Subject: make world failure... From: Poul-Henning Kamp Date: Tue, 28 Jul 1998 15:18:46 +0200 Message-ID: <1416.901631926@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE _PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I /usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc/../libc/stdtime/timelocal. c -o timelocal.o cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE _PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I /usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc/../libc/i386/sys/i386_get_ ldt.c -o i386_get_ldt.o In file included from /usr/src/lib/libc/../libc/i386/sys/i386_get_ldt.c:37: /usr/obj/usr/src/tmp/usr/include/machine/sysarch.h:58: parse error before `*' /usr/obj/usr/src/tmp/usr/include/machine/sysarch.h:59: parse error before `int' *** Error code 1 I think it is the "u_int" it barfs on... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 06:41:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA10970 for freebsd-current-outgoing; Tue, 28 Jul 1998 06:41:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gate.bulinfo.net ([195.10.34.161]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA10957 for ; Tue, 28 Jul 1998 06:41:49 -0700 (PDT) (envelope-from krassi@bulinfo.net) Received: (qmail 21652 invoked by uid 0); 28 Jul 1998 13:41:03 -0000 Received: from unknown (HELO bulinfo.net) (unknown) by unknown with SMTP; 28 Jul 1998 13:41:03 -0000 Message-ID: <35BDD45A.846006A7@bulinfo.net> Date: Tue, 28 Jul 1998 16:38:35 +0300 From: Krassimir Slavchev X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Support for Digiboard SYNC/570i PCI w CURRENT Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Does anybody know is there any support for Digiboard SYNC/570i PCI in CURRENT (ot any other RELEASE). I know there's a driver for ISA bus, but I don't know does it work with PCI cards an how (if it does). Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 07:27:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18601 for freebsd-current-outgoing; Tue, 28 Jul 1998 07:27:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.pipeline.ch (freefall.pipeline.ch [195.134.128.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18593 for ; Tue, 28 Jul 1998 07:27:34 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.128.41]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA70; Tue, 28 Jul 1998 16:25:49 +0200 Message-ID: <35BDDF77.19B4353C@pipeline.ch> Date: Tue, 28 Jul 1998 16:25:59 +0200 From: "IBS / Andre Oppermann" Organization: Internet Business Solutions Ltd. (AG) X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Krassimir Slavchev CC: current@FreeBSD.ORG Subject: Re: Support for Digiboard SYNC/570i PCI w CURRENT References: <35BDD45A.846006A7@bulinfo.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Krassimir Slavchev wrote: > > Hi, > Does anybody know is there any support for Digiboard SYNC/570i PCI in > CURRENT > (ot any other RELEASE). I know there's a driver for ISA bus, but I don't > know does it work with PCI cards an how (if it does). There is very good support. The driver is called ar0 (you'll find more information in LINT). -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 07:42:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21162 for freebsd-current-outgoing; Tue, 28 Jul 1998 07:42:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21143 for ; Tue, 28 Jul 1998 07:42:21 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id KAA19062; Tue, 28 Jul 1998 10:41:35 -0400 (EDT) (envelope-from wollman) Date: Tue, 28 Jul 1998 10:41:35 -0400 (EDT) From: Garrett Wollman Message-Id: <199807281441.KAA19062@khavrinen.lcs.mit.edu> To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: SMP kernels... how many processes can be in ? In-Reply-To: References: <199807272007.NAA01087@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > trouble is that there needs to be some place to store data > on a 'packet by packet' basis, The data is generated at one point in > processing and needed at another.. Stick it in the (mbuf) packet header. If it's too big, stick a pointer to it in the packet header. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 07:44:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21514 for freebsd-current-outgoing; Tue, 28 Jul 1998 07:44:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21487; Tue, 28 Jul 1998 07:44:10 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id AAA11114; Wed, 29 Jul 1998 00:43:21 +1000 Date: Wed, 29 Jul 1998 00:43:21 +1000 From: Bruce Evans Message-Id: <199807281443.AAA11114@godzilla.zeta.org.au> To: current@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: make world failure... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE >_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I >/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc/../libc/i386/sys/i386_get_ >ldt.c -o i386_get_ldt.o >In file included from /usr/src/lib/libc/../libc/i386/sys/i386_get_ldt.c:37: >/usr/obj/usr/src/tmp/usr/include/machine/sysarch.h:58: parse error before `*' >/usr/obj/usr/src/tmp/usr/include/machine/sysarch.h:59: parse error before `int' >*** Error code 1 > >I think it is the "u_int" it barfs on... Fix: s/u_int/unsigned/g (or unsigned int if you want to be verbose). The new ioperm man pages and the old get/set ldt man pages are also broken by this (they don't say that must be included before . OTOH, the new ioperm implementations avoid this bug by including . The ioperm man pages also specify u_int. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 08:20:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27703 for freebsd-current-outgoing; Tue, 28 Jul 1998 08:20:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pat.idi.ntnu.no (0@pat.idi.ntnu.no [129.241.103.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27698 for ; Tue, 28 Jul 1998 08:20:34 -0700 (PDT) (envelope-from Tor.Egge@fast.no) From: Tor.Egge@fast.no Received: from idi.ntnu.no (tegge@ikke.idi.ntnu.no [129.241.111.65]) by pat.idi.ntnu.no (8.8.8/8.8.8) with ESMTP id RAA12042; Tue, 28 Jul 1998 17:19:48 +0200 (MET DST) Message-Id: <199807281519.RAA12042@pat.idi.ntnu.no> To: karl@mcs.net Cc: current@FreeBSD.ORG Subject: Re: Serious Dump problems In-Reply-To: Your message of "Tue, 28 Jul 1998 07:35:23 -0500" References: <19980728073523.02311@mcs.net> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 28 Jul 1998 17:19:47 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi folks, > > I have an interesting one here... > > I have a dump tape which is intact, yet restore complains about "hole in > map" and segv's when attempting to start up in interactive mode. Philip Inglesant gave a good description of this problem on the -stable list. You probably had more than 4 million inodes on the file system. Thus the bitmaps uses more than 512 KB(i.e. more than 512 tape blocks). Running dump/restore using a 51 GB partition (with 13 million inodes gave the same problem for me. > It appears that dump and restore are VERY old, and nobody is maintaining > them. Interestingly enough, a new dump of the same filesystem produces > the same error, so I suspect a problem with dump where it is writing out a > bad directory map. It is not sufficient to only change dump. The calculation of maxino in restore depends upon the current behavior of dump, using a value larger than 512 in the c_count field when the number of inodes is larger than 4 million. Only a small change to restore is needed. > Any ideas on this one? Is there a more recent set of sources available > somewhere that might not display this problem? I suggest using a patch similar to this (barely tested) one in order to avoid the buffer overrun in restore. Index: tape.c =================================================================== RCS file: /home/ncvs/src/sbin/restore/tape.c,v retrieving revision 1.12 diff -u -r1.12 tape.c --- tape.c 1998/06/28 20:25:59 1.12 +++ tape.c 1998/07/28 13:45:29 @@ -104,6 +104,8 @@ static void xtrmapskip __P((char *, long)); static void xtrskip __P((char *, long)); +static int readmapflag; + /* * Set up an input source */ @@ -678,7 +680,7 @@ gettingfile++; loop: for (i = 0; i < spcl.c_count; i++) { - if (spcl.c_addr[i]) { + if (readmapflag || spcl.c_addr[i]) { readtape(&buf[curblk++][0]); if (curblk == fssize / TP_BSIZE) { (*fill)((char *)buf, (long)(size > TP_BSIZE ? @@ -697,7 +699,7 @@ } if ((size -= TP_BSIZE) <= 0) { for (i++; i < spcl.c_count; i++) - if (spcl.c_addr[i]) + if (readmapflag || spcl.c_addr[i]) readtape(junk); break; } @@ -1095,6 +1097,7 @@ qcvt.val[0] = i; buf->c_dinode.di_size = qcvt.qval; } + readmapflag = 0; switch (buf->c_type) { @@ -1105,8 +1108,11 @@ */ buf->c_inumber = 0; buf->c_dinode.di_size = buf->c_count * TP_BSIZE; - for (i = 0; i < buf->c_count; i++) - buf->c_addr[i]++; + if (buf->c_count > TP_NINDIR) + readmapflag = 1; + else + for (i = 0; i < buf->c_count; i++) + buf->c_addr[i]++; break; case TS_TAPE: @@ -1187,7 +1193,7 @@ blks = 0; if (header->c_type != TS_END) for (i = 0; i < header->c_count; i++) - if (header->c_addr[i] != 0) + if (readmapflag || header->c_addr[i] != 0) blks++; predict = blks; blksread = 0; > > Needless to say, unrestorable tapes are not my idea of a good time! I agree. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 08:28:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29448 for freebsd-current-outgoing; Tue, 28 Jul 1998 08:28:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29439; Tue, 28 Jul 1998 08:28:25 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.HIP.Berkeley.EDU (sji-ca7-188.ix.netcom.com [209.109.235.188]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id IAA21288; Tue, 28 Jul 1998 08:27:53 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id IAA22123; Tue, 28 Jul 1998 08:27:46 -0700 (PDT) Date: Tue, 28 Jul 1998 08:27:46 -0700 (PDT) Message-Id: <199807281527.IAA22123@silvia.HIP.Berkeley.EDU> To: jmz@FreeBSD.ORG CC: ports@FreeBSD.ORG, Pierre.Dampure@barclayscapital.com, current@FreeBSD.ORG Subject: [Pierre.Dampure@barclayscapital.com: 3.3.2-patch3] From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Please send requests like this to the maintainer and the -ports list, not -current....) Satoshi ------- From: Pierre.Dampure@barclayscapital.com To: FreeBSD-Current@FreeBSD.ORG Subject: 3.3.2-patch3 Date: Tue, 28 Jul 1998 13:44:17 +0100 Can somebody incorporate the above (released July 25th) in PATCHFILES and files/md5 ? Best Regards, Pierre Y. ************************************************************************************** Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group unless otherwise specifically stated. ************************************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 08:28:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29514 for freebsd-current-outgoing; Tue, 28 Jul 1998 08:28:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29486 for ; Tue, 28 Jul 1998 08:28:39 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id KAA10500; Tue, 28 Jul 1998 10:28:08 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id KAA21480; Tue, 28 Jul 1998 10:28:07 -0500 (CDT) Message-ID: <19980728102807.42807@mcs.net> Date: Tue, 28 Jul 1998 10:28:07 -0500 From: Karl Denninger To: Tor.Egge@fast.no Cc: current@FreeBSD.ORG Subject: Re: Serious Dump problems References: <19980728073523.02311@mcs.net> <199807281519.RAA12042@pat.idi.ntnu.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807281519.RAA12042@pat.idi.ntnu.no>; from Tor.Egge@fast.no on Tue, Jul 28, 1998 at 05:19:47PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 28, 1998 at 05:19:47PM +0200, Tor.Egge@fast.no wrote: > > Hi folks, > > > > I have an interesting one here... > > > > I have a dump tape which is intact, yet restore complains about "hole in > > map" and segv's when attempting to start up in interactive mode. > > Philip Inglesant gave a good description of this > problem on the -stable list. > > You probably had more than 4 million inodes on the file system. Thus > the bitmaps uses more than 512 KB(i.e. more than 512 tape blocks). I have more than 4M Inodes on the filesystem, but not more than 4M inodes IN USE. Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted /dev/sd0s1f 31164736 11790546 16881012 41% 417900 7375250 5% /export That's the disk that is blowing chunks on restore.... > Running dump/restore using a 51 GB partition (with 13 million inodes > gave the same problem for me. > > > It appears that dump and restore are VERY old, and nobody is maintaining > > them. Interestingly enough, a new dump of the same filesystem produces > > the same error, so I suspect a problem with dump where it is writing out a > > bad directory map. > > It is not sufficient to only change dump. The calculation of maxino > in restore depends upon the current behavior of dump, using a > value larger than 512 in the c_count field when the number of inodes > is larger than 4 million. > > Only a small change to restore is needed. > > > Any ideas on this one? Is there a more recent set of sources available > > somewhere that might not display this problem? > > I suggest using a patch similar to this (barely tested) one in order > to avoid the buffer overrun in restore. I'll try this one. Assuming it works, is there some reason it hasn't been committed? -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 08:34:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01068 for freebsd-current-outgoing; Tue, 28 Jul 1998 08:34:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gwinnett.com (mail.gwinnett.com [204.89.227.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01055 for ; Tue, 28 Jul 1998 08:34:38 -0700 (PDT) (envelope-from lee@gwinnett.com) Received: from venus.gwinnett.com ([204.89.227.91]) by mail.gwinnett.com (8.8.7/8.8.5) with SMTP id LAA07584 for ; Tue, 28 Jul 1998 11:34:00 -0400 Message-ID: <35BDEF4D.41C67EA6@gwinnett.com> Date: Tue, 28 Jul 1998 11:33:33 -0400 From: Lee Reese X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.0CAM-19980712-0 i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: GENERIC Kernel Problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just loaded the 7-25-98 SNAP release of -current and a couple of uniprocessor machines. I can't seem to run a /usr/sbin/config on the MYKERNEL file I made. The error is: cant open ../i386/config/devices.(null) Could someone tell me what is going on here? Thanks. Lee Reese PS- I just put the Usenet news server running 7-24-98 -current into production yesterday. It was doing so well, we took the Diablo feeder machine offline and ran all feeds into it. Load averages are generally staying in the .015 range, something it has never done while running Linux. Finally, after 7 months of fighting and throwing money at the server, it seems we have solved our problem. Now on to bigger and better things. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 09:01:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07010 for freebsd-current-outgoing; Tue, 28 Jul 1998 09:01:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06982 for ; Tue, 28 Jul 1998 09:01:15 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id LAA12726; Tue, 28 Jul 1998 11:00:43 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id LAA22078; Tue, 28 Jul 1998 11:00:43 -0500 (CDT) Message-ID: <19980728110043.36780@mcs.net> Date: Tue, 28 Jul 1998 11:00:43 -0500 From: Karl Denninger To: Tor.Egge@fast.no Cc: current@FreeBSD.ORG Subject: Re: Serious Dump problems References: <19980728073523.02311@mcs.net> <199807281519.RAA12042@pat.idi.ntnu.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807281519.RAA12042@pat.idi.ntnu.no>; from Tor.Egge@fast.no on Tue, Jul 28, 1998 at 05:19:47PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This patch appears to fix restore. Can someone review and commmit this PLEASE? Thanks. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost On Tue, Jul 28, 1998 at 05:19:47PM +0200, Tor.Egge@fast.no wrote: > > Hi folks, > > > > I have an interesting one here... > > > > I have a dump tape which is intact, yet restore complains about "hole in > > map" and segv's when attempting to start up in interactive mode. > > Philip Inglesant gave a good description of this > problem on the -stable list. > > You probably had more than 4 million inodes on the file system. Thus > the bitmaps uses more than 512 KB(i.e. more than 512 tape blocks). > > Running dump/restore using a 51 GB partition (with 13 million inodes > gave the same problem for me. > > > It appears that dump and restore are VERY old, and nobody is maintaining > > them. Interestingly enough, a new dump of the same filesystem produces > > the same error, so I suspect a problem with dump where it is writing out a > > bad directory map. > > It is not sufficient to only change dump. The calculation of maxino > in restore depends upon the current behavior of dump, using a > value larger than 512 in the c_count field when the number of inodes > is larger than 4 million. > > Only a small change to restore is needed. > > > Any ideas on this one? Is there a more recent set of sources available > > somewhere that might not display this problem? > > I suggest using a patch similar to this (barely tested) one in order > to avoid the buffer overrun in restore. > > Index: tape.c > =================================================================== > RCS file: /home/ncvs/src/sbin/restore/tape.c,v > retrieving revision 1.12 > diff -u -r1.12 tape.c > --- tape.c 1998/06/28 20:25:59 1.12 > +++ tape.c 1998/07/28 13:45:29 > @@ -104,6 +104,8 @@ > static void xtrmapskip __P((char *, long)); > static void xtrskip __P((char *, long)); > > +static int readmapflag; > + > /* > * Set up an input source > */ > @@ -678,7 +680,7 @@ > gettingfile++; > loop: > for (i = 0; i < spcl.c_count; i++) { > - if (spcl.c_addr[i]) { > + if (readmapflag || spcl.c_addr[i]) { > readtape(&buf[curblk++][0]); > if (curblk == fssize / TP_BSIZE) { > (*fill)((char *)buf, (long)(size > TP_BSIZE ? > @@ -697,7 +699,7 @@ > } > if ((size -= TP_BSIZE) <= 0) { > for (i++; i < spcl.c_count; i++) > - if (spcl.c_addr[i]) > + if (readmapflag || spcl.c_addr[i]) > readtape(junk); > break; > } > @@ -1095,6 +1097,7 @@ > qcvt.val[0] = i; > buf->c_dinode.di_size = qcvt.qval; > } > + readmapflag = 0; > > switch (buf->c_type) { > > @@ -1105,8 +1108,11 @@ > */ > buf->c_inumber = 0; > buf->c_dinode.di_size = buf->c_count * TP_BSIZE; > - for (i = 0; i < buf->c_count; i++) > - buf->c_addr[i]++; > + if (buf->c_count > TP_NINDIR) > + readmapflag = 1; > + else > + for (i = 0; i < buf->c_count; i++) > + buf->c_addr[i]++; > break; > > case TS_TAPE: > @@ -1187,7 +1193,7 @@ > blks = 0; > if (header->c_type != TS_END) > for (i = 0; i < header->c_count; i++) > - if (header->c_addr[i] != 0) > + if (readmapflag || header->c_addr[i] != 0) > blks++; > predict = blks; > blksread = 0; > > > > > Needless to say, unrestorable tapes are not my idea of a good time! > > I agree. > > - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 09:04:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08000 for freebsd-current-outgoing; Tue, 28 Jul 1998 09:04:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07934 for ; Tue, 28 Jul 1998 09:04:30 -0700 (PDT) (envelope-from ckempf@singularity.enigami.com) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id MAA13457; Tue, 28 Jul 1998 12:03:29 -0400 (EDT) To: freebsd-current@FreeBSD.ORG Subject: coda for current? X-Copyright: Copyright (C) 1998 Cory Kempf. All Rights Reserved X-PGP-Fingerprint: 191E 2FB7 E27D 76C3 8E79 4D26 2B3B B20F 2A9C 1E1A X-PGP-Keyloc: ; finger ckempf@enigami.com From: Cory Kempf Date: 28 Jul 1998 12:03:29 -0400 Message-ID: Lines: 18 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last newsletter, a big announcement was made about coda. From looking at the web pages, it seems like a really cool idea. Unfortunately, they only have ports for -stable Does anyone know what the issues are against making it work with -current? Is anyone working on it? (is anyone working on porting it to other platforms, so I can finally throw NFS in the trash? :-) ) +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 09:06:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08630 for freebsd-current-outgoing; Tue, 28 Jul 1998 09:06:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from is2.net.ohio-state.edu (is2.net.ohio-state.edu [128.146.48.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA08575 for ; Tue, 28 Jul 1998 09:06:28 -0700 (PDT) (envelope-from maf@dev1.net.ohio-state.edu) Received: (qmail 13089 invoked from network); 28 Jul 1998 16:05:54 -0000 Received: from dev1.net.ohio-state.edu (128.146.222.3) by is2.net.ohio-state.edu with SMTP; 28 Jul 1998 16:05:54 -0000 Received: (qmail 22965 invoked by uid 4454); 28 Jul 1998 16:05:53 -0000 Message-ID: <19980728120553.A22817@net.ohio-state.edu> Date: Tue, 28 Jul 1998 12:05:53 -0400 From: Mark Fullmer To: freebsd@magnet.geophysik.tu-freiberg.de Cc: freebsd-current@FreeBSD.ORG Subject: Re: Answering myself, was: URGENT! ASUS P2B/LS supported ? References: <19980728051057.A14534@net.ohio-state.edu> <199807281108.NAA00456@magnet.geophysik.tu-freiberg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: <199807281108.NAA00456@magnet.geophysik.tu-freiberg.de>; from Holm Tiffe on Tue, Jul 28, 1998 at 01:08:58PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 28, 1998 at 01:08:58PM +0200, Holm Tiffe wrote: > > > The Machine is running fine, the AIC 7890 is supported from our > > > CAM SCSI drivers, and the onboard Ethernet (I82558) works > > > flawlessly whit the fxp driver. (only 10 Base T testet) > > > > Do you get the following error on boot? > > > > pci_map_mem failed: bad memory type=0xfffff004 > > > > No, no problems at all, where do you get this message ? > After the initializing of the NIC or what ? This is -stable around the 2.2.7 branch, not current. The pci code has changed quite a bit in -current. chip2 rev 2 on pci0:4:0 chip3 rev 1 on pci0:4:1 chip4 rev 1 int d irq 12 on pci0:4:2 chip5 rev 2 on pci0:4:3 ahc0 rev 0 int a irq 12 on pci0:6:0 pci_map_mem failed: bad memory type=0xfffff004 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 32/255 SCBs fxp0 rev 5 int a irq 10 on pci0:7:0 -- mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 09:23:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13119 for freebsd-current-outgoing; Tue, 28 Jul 1998 09:23:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.baldcom.net (green@zone.BALDCOM.NET [205.232.46.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12991; Tue, 28 Jul 1998 09:22:38 -0700 (PDT) (envelope-from green@zone.baldcom.net) Received: from localhost (green@localhost) by zone.baldcom.net (8.8.8/8.8.7) with SMTP id MAA02710; Tue, 28 Jul 1998 12:22:11 -0400 (EDT) Date: Tue, 28 Jul 1998 12:22:11 -0400 (EDT) From: Brian Feldman To: Poul-Henning Kamp cc: current@FreeBSD.ORG Subject: Re: make world failure... In-Reply-To: <1416.901631926@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul, have you tried makeing libc after a "make includes"? I don't see a -nostdinc in there, so I think it will make sense to update your local includes... and making libc "works for me" :) Cheers, Brian Feldman green@unixhelp.org On Tue, 28 Jul 1998, Poul-Henning Kamp wrote: > > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE > _PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I > /usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc/../libc/stdtime/timelocal. > c -o timelocal.o > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE > _PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I > /usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc/../libc/i386/sys/i386_get_ > ldt.c -o i386_get_ldt.o > In file included from /usr/src/lib/libc/../libc/i386/sys/i386_get_ldt.c:37: > /usr/obj/usr/src/tmp/usr/include/machine/sysarch.h:58: parse error before `*' > /usr/obj/usr/src/tmp/usr/include/machine/sysarch.h:59: parse error before `int' > *** Error code 1 > > I think it is the "u_int" it barfs on... > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 09:29:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14579 for freebsd-current-outgoing; Tue, 28 Jul 1998 09:29:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14513 for ; Tue, 28 Jul 1998 09:29:14 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id SAA00527; Tue, 28 Jul 1998 18:25:07 +0200 (CEST) To: Brian Feldman cc: current@FreeBSD.ORG Subject: Re: make world failure... In-reply-to: Your message of "Tue, 28 Jul 1998 12:22:11 EDT." Date: Tue, 28 Jul 1998 18:25:07 +0200 Message-ID: <525.901643107@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Brian Fe ldman writes: >Poul, have you tried makeing libc after a "make includes"? I don't see a >-nostdinc in there, so I think it will make sense to update your local >includes... and making libc "works for me" :) Yes, but make world doesn't work... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 09:53:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19700 for freebsd-current-outgoing; Tue, 28 Jul 1998 09:53:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gate.bulinfo.net ([195.10.34.161]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA19665 for ; Tue, 28 Jul 1998 09:52:52 -0700 (PDT) (envelope-from krassi@bulinfo.net) Received: (qmail 26821 invoked by uid 0); 28 Jul 1998 16:52:02 -0000 Received: from unknown (HELO bulinfo.net) (unknown) by unknown with SMTP; 28 Jul 1998 16:52:02 -0000 Message-ID: <35BE011F.A2ECFB8A@bulinfo.net> Date: Tue, 28 Jul 1998 19:49:35 +0300 From: Krassimir Slavchev X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: andre@pipeline.ch CC: current@FreeBSD.ORG Subject: Digiboard SYNC/570i PCI Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the answer, but I don't know how to confiigure it, because it's a PCI card. in LINT there's an example for ISA card. Can you send me an example line for the kernel configuration for a PCI bus. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 10:04:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22199 for freebsd-current-outgoing; Tue, 28 Jul 1998 10:04:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.pipeline.ch (intranet.pipeline.ch [195.134.128.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22181 for ; Tue, 28 Jul 1998 10:04:18 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.128.41]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA339; Tue, 28 Jul 1998 19:02:38 +0200 Message-ID: <35BE0439.DDB768AB@pipeline.ch> Date: Tue, 28 Jul 1998 19:02:49 +0200 From: "IBS / Andre Oppermann" Organization: Internet Business Solutions Ltd. (AG) X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Krassimir Slavchev CC: current@FreeBSD.ORG Subject: Re: Digiboard SYNC/570i PCI References: <35BE011F.A2ECFB8A@bulinfo.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Krassimir Slavchev wrote: > > Thanks for the answer, > > but I don't know how to confiigure it, because it's a PCI card. > in LINT there's an example for ISA card. > Can you send me an example line for the kernel configuration for a PCI > bus. No idea, we have only ISA cards. Maybe John Hay, the author of the driver has some thoughts on it? -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 10:55:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03144 for freebsd-current-outgoing; Tue, 28 Jul 1998 10:55:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03091 for ; Tue, 28 Jul 1998 10:55:13 -0700 (PDT) (envelope-from bartol@salk.edu) Received: from cole.salk.edu (cole [198.202.70.113]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id KAA08385 for ; Tue, 28 Jul 1998 10:54:39 -0700 (PDT) Date: Tue, 28 Jul 1998 10:54:38 -0700 (PDT) From: Tom Bartol To: current@FreeBSD.ORG Subject: make world failure in -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Just got this failure while building strip in a make world of -current cvsupped moments ago. I'm making on a 3.0-19980711-SNAP system with SMP enabled. Thanks, Tom ===> strip cc -O2 -m486 -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/strip I/usr/src/gnu/usr.bin/binutils/strip/../libbfd/i386 -I/usr/src/gnu/usr.bin/bin ils/strip/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils trip/../libbinutils -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/ nutils/binutils -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/b utils/strip/../../../../contrib/binutils/binutils/objcopy.c cc -O2 -m486 -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/strip I/usr/src/gnu/usr.bin/binutils/strip/../libbfd/i386 -I/usr/src/gnu/usr.bin/bin ils/strip/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils trip/../libbinutils -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/ nutils/binutils -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/b utils/strip/../../../../contrib/binutils/binutils/is-strip.c cc -O2 -m486 -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/strip I/usr/src/gnu/usr.bin/binutils/strip/../libbfd/i386 -I/usr/src/gnu/usr.bin/bin ils/strip/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils trip/../libbinutils -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/ nutils/binutils -I/usr/obj/usr/src/tmp/usr/include -static -o strip objcopy is-strip.o -L../libbinutils -lbinutils -L../libbfd -lbfd -L../libiberty -lib ty cp strip maybe_stripped strip maybe_stripped strip: maybe_stripped: File format not recognized *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 11:31:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10739 for freebsd-current-outgoing; Tue, 28 Jul 1998 11:31:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10611 for ; Tue, 28 Jul 1998 11:31:11 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id LAA21511; Tue, 28 Jul 1998 11:30:34 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 28 Jul 1998 11:30:33 -0700 (PDT) From: Doug White To: ben@rosengart.com cc: current@FreeBSD.ORG Subject: Re: more PPP weirdness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Jul 1998, Snob Art Genre wrote: > On Mon, 27 Jul 1998, Doug White wrote: > > > You probably have routed turned on, and it's hearing the RIP broadcasts. > > Nope, no routed running. Who would be sending these RIP broadcasts, > anyway? Plus, if routed were fiddling with routes, it would show up in > netstat -r[n] output, but that seems quite sane: > > Internet: > Destination Gateway Flags Refs Use Netif > Expire > default 204.180.194.101 UGSc 2 38 tun0 > 10 link#1 UC 0 0 ed0 > 127.0.0.1 127.0.0.1 UH 0 1865 lo0 > 204.180.194.101 204.180.205.197 UH 3 0 tun0 Now that's wierd: ppp showing routes that netstat -rn doesn't. :-/ Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 11:36:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11653 for freebsd-current-outgoing; Tue, 28 Jul 1998 11:36:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11522 for ; Tue, 28 Jul 1998 11:35:36 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with ESMTP id LAA22474; Tue, 28 Jul 1998 11:34:27 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 28 Jul 1998 11:34:27 -0700 (PDT) From: Doug White To: =?X-UNKNOWN?Q?Dag-Erling_Coidan_Sm=F8rgrav?= cc: Hostas Red , current@FreeBSD.ORG Subject: Re: Strange idle times In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28 Jul 1998, Dag-Erling Coidan Smørgrav wrote: > Doug White writes: > > On Sat, 25 Jul 1998, Hostas Red wrote: > > > > > About one month or so i have a strange idle times on my -current (really > > > > > current - 1 hour or so :) - whenever i use 'w' or 'finger' idle time of > > > > > users equivalent to uptime (maybe 1 minute less). ;-( > > > > Corrupted utmp/wtmp perhaps? Something trying to use the old format? > > > But why? I'm sitting on -current for more than half a year already and i'm > > > rebooting sometimes :). wtmp rolls daily, utmp brand new after rebooting > > > half an hour ago. And problem still exitst, after one more 'make world'. > > Perhaps you have a program using the old format, like ssh? I'm having > > this problem with our house router (I need to fix that). > > I checked, and I have the same problem on my -current box. All my vtys > and ptys show up with as much idle time as the machine's uptime. I ssh > a lot öut"from this box, but very little *into* it, so the fubared > ptys are mostly xterms. There's a known bug in xterm. The bugfixed version doesn't use utmp (which I don't like), but it stops the corruption. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 12:07:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18598 for freebsd-current-outgoing; Tue, 28 Jul 1998 12:07:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18492 for ; Tue, 28 Jul 1998 12:06:55 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id OAA25791; Tue, 28 Jul 1998 14:06:15 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id OAA28396; Tue, 28 Jul 1998 14:06:15 -0500 (CDT) Message-ID: <19980728140615.27193@mcs.net> Date: Tue, 28 Jul 1998 14:06:15 -0500 From: Karl Denninger To: Warner Losh Cc: Tor.Egge@fast.no, current@FreeBSD.ORG Subject: Re: Serious Dump problems References: <199807281519.RAA12042@pat.idi.ntnu.no> <19980728073523.02311@mcs.net> <199807281519.RAA12042@pat.idi.ntnu.no> <199807281858.MAA16754@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807281858.MAA16754@harmony.village.org>; from Warner Losh on Tue, Jul 28, 1998 at 12:58:48PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 28, 1998 at 12:58:48PM -0600, Warner Losh wrote: > I just committed this patch. Please let me know if there is any > breakage. > > Warner Thanks. I tried a restore from a tape which had formerly been unreadable (without the patch) and it was fine. I know that's not a LOT of testing, but its some, and it definitely starts up and "plays nice" as best as I can determine. I don't happen to have an extra 30G RAID set laying around to do a *full* restore onto (which would be required for full verification). Anyone else? :-) That's what I thought. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 12:25:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22672 for freebsd-current-outgoing; Tue, 28 Jul 1998 12:25:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fledge.watson.org (root@COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22562 for ; Tue, 28 Jul 1998 12:24:49 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id PAA13517; Tue, 28 Jul 1998 15:24:00 -0400 (EDT) Date: Tue, 28 Jul 1998 15:24:00 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Cory Kempf cc: freebsd-current@FreeBSD.ORG Subject: Re: coda for current? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28 Jul 1998, Cory Kempf wrote: > In the last newsletter, a big announcement was made about coda. From > looking at the web pages, it seems like a really cool idea. > > Unfortunately, they only have ports for -stable > > Does anyone know what the issues are against making it work with > -current? Is anyone working on it? > > (is anyone working on porting it to other platforms, so I can finally > throw NFS in the trash? :-) ) Cory, I will be working on Coda for FreeBSD-CURRENT as of next week. However, Coda is currently only supported on FreeBSD-2.2.stuff, as when we were deciding on the FreeBSD version to develop under, 3.0 was pretty unstable. We didn't want our instabilities conflicting with the 3.0 instabilities :), leading to an even harder time debugging. Coda is rapidly stabilizing -- we hope to have a stable base version capable of real use in real environments in 6-12 months; at this point it still has bugs in a number of places, and is not still really appropriate outside of experimental environments. I pick up my new Coda notebook on Thursday at the end of a DARPA PI meeting, install -CURRENT that evening, and hopefully get working on it next week. Bob Baron is currently largely responsible for the BSD versions of Coda, and has looked at some of the issues involved in -CURRENT. Robert N Watson Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 12:50:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28180 for freebsd-current-outgoing; Tue, 28 Jul 1998 12:50:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ConSys.COM (ConSys.COM [209.141.107.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28024 for ; Tue, 28 Jul 1998 12:49:47 -0700 (PDT) (envelope-from rcarter@pinyon.org) Received: (from pinyon@localhost) by ConSys.COM (8.8.6/8.8.6) id MAA15407 for current@freebsd.org; Tue, 28 Jul 1998 12:49:12 -0700 (MST) Date: Tue, 28 Jul 1998 12:49:12 -0700 (MST) From: "Russell L. Carter" Message-Id: <199807281949.MAA15407@ConSys.COM> To: current@FreeBSD.ORG Subject: elf in 3.0-release? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's not clear from Jordan's announcement, what's up with ELF (and CAM and DEVFS)? Are they going to be in the October release? Thanks, Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 13:05:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01970 for freebsd-current-outgoing; Tue, 28 Jul 1998 13:05:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01770 for ; Tue, 28 Jul 1998 13:04:27 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id NAA04275; Tue, 28 Jul 1998 13:03:35 -0700 (PDT) (envelope-from jdp) Message-Id: <199807282003.NAA04275@austin.polstra.com> To: lee@gwinnett.com Subject: Re: GENERIC Kernel Problem In-Reply-To: <35BDEF4D.41C67EA6@gwinnett.com> References: <35BDEF4D.41C67EA6@gwinnett.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Tue, 28 Jul 1998 13:03:35 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <35BDEF4D.41C67EA6@gwinnett.com>, Lee Reese wrote: > I just loaded the 7-25-98 SNAP release of -current and a couple of > uniprocessor machines. I can't seem to run a /usr/sbin/config on the > MYKERNEL file I made. > > The error is: > > cant open ../i386/config/devices.(null) > > Could someone tell me what is going on here? Thanks. If I had to guess without looking, I'd say you probably left out the line machine "i386" in your config file. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 14:15:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16822 for freebsd-current-outgoing; Tue, 28 Jul 1998 14:15:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from NIH2WAAD (smtp4.site1.csi.com [149.174.183.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16792 for ; Tue, 28 Jul 1998 14:14:51 -0700 (PDT) (envelope-from derm@iol.ie) Received: from mail pickup service by csi.com with Microsoft SMTPSVC; Tue, 28 Jul 1998 17:14:16 -0400 Received: from md16-188.mun.compuserve.com (md16-188.mun.compuserve.com [195.232.40.188]) by hil-img-ims-3.compuserve.com (8.8.6/8.8.6/IMS-1.4) with SMTP id RAA03531 for ; Tue, 28 Jul 1998 17:13:32 -0400 (EDT) From: derm@iol.ie (Dermot McNally) To: freebsd-current@FreeBSD.ORG Subject: Re: Problems with ed driver (PCI) Date: Tue, 28 Jul 1998 21:13:31 GMT Organization: My House Message-ID: <35c03c26.2700750@mail.compuserve.com> References: <35bcb5ac.2742218@mail.compuserve.com> In-Reply-To: <35bcb5ac.2742218@mail.compuserve.com> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id OAA16799 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Jul 1998 17:41:15 GMT, you wrote: >However, this doesn't help, because after boot time, any attempt to >configure the interface leads to the error: > >interface ed0 does not exist OK, There have been a few suggestions so far, none of which hits the problem. I'd better give a few more details. The card is actually sold under the name "Micronet" although it is recognised as a Realtek chipset. Its little green light goes on, indicating that it sees the network OK and the corresponding little green light on the hub comes on too. There is one unusual, and possibly significant issue here - I also have a 3Com network card (calls itself an Etherlink XL, uses the vx driver). If I fit this card, and there's a driver for it in the kernel, the machine hangs after finding the card. The same kernel on a different machine will boot no problem with this card. I haven't yet tried the other machine with the NE2000 - it's a 100% NT machine anyway, so it won't help me much, but it's a useful test. That machine normally runs correctly with the 3Com card. Very strange. The spec of the machine that's causing this trouble is now as follows: Intel LX chipset, a PII 300MHz, made by Gateway 2000 NE2000 PCI network card (Realtek via Micronet) Adaptec UW 2900 SCSI contoller (card, not on board) One US SCSI HD, 1 SCSI CDROM drive STP AGP graphics card (Riva 128 chipset) That's the lot - I pulled the sound card in case it was a factor. The problem occurs with kernels from the 5/24/98 snap as well as from (I think) a 20/7/98 snap I found on ftp.de.freebsd.org but which doesn't seem to be on the main site. Any ideas? Dermot ----------------------------------------------------------- Dermot McNally, derm@iol.ie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 14:17:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17250 for freebsd-current-outgoing; Tue, 28 Jul 1998 14:17:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17202 for ; Tue, 28 Jul 1998 14:17:14 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id XAA10083 for current@FreeBSD.ORG; Tue, 28 Jul 1998 23:15:10 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id XAA03894 for current@FreeBSD.ORG; Tue, 28 Jul 1998 23:09:47 +0200 (CEST) (envelope-from andreas) Message-ID: <19980728230947.A3455@klemm.gtn.com> Date: Tue, 28 Jul 1998 23:09:47 +0200 From: Andreas Klemm To: current@FreeBSD.ORG Subject: something new in current, that might create a leased line ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The name server requests doesn't stop, so the ISDN line stays up. Look at the bad cksum lines ... Current / make world from yesterday ... 23:06:24.775498 pppak04.gtn.com.1048 > a.root-servers.net.domain: 23139 (45) (ttl 64, id 2698) 23:06:25.232311 248.17.235.100 > a.root-servers.net: (frag 17664:-27@1272) [tos 0x3] (ttl 146, bad cksum 4000!, optlen=40[|ip]) 23:06:25.236141 pppak04.gtn.com.1048 > a.root-servers.net.domain: 23140 (45) (ttl 64, id 2701) 23:06:25.725295 248.17.235.99 > a.root-servers.net: (frag 17664:-27@1272) [tos 0x3] (ttl 146, bad cksum 4000!, optlen=40[|ip]) 23:06:25.729307 pppak04.gtn.com.1048 > a.root-servers.net.domain: 23141 (45) (ttl 64, id 2704) 23:06:26.171281 248.17.235.98 > a.root-servers.net: (frag 17664:-27@1272) [tos 0x3] (ttl 146, bad cksum 4000!, optlen=40[|ip]) 23:06:26.175166 pppak04.gtn.com.1048 > a.root-servers.net.domain: 23142 (45) (ttl 64, id 2707) 23:06:26.642388 248.17.235.97 > a.root-servers.net: (frag 17664:-27@1272) [tos 0x3] (ttl 146, bad cksum 4000!, optlen=40[|ip]) 23:06:26.646341 pppak04.gtn.com.1048 > a.root-servers.net.domain: 23143 (45) (ttl 64, id 2710) 23:06:27.060156 248.17.235.96 > a.root-servers.net: (frag 17664:-27@1272) [tos 0x3] (ttl 146, bad cksum 4000!, optlen=40[|ip]) 23:06:27.064003 pppak04.gtn.com.1048 > pinea.xerox.fr.domain: 23144 (43) (ttl 64, id 2713) -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 15:11:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29866 for freebsd-current-outgoing; Tue, 28 Jul 1998 15:11:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29744 for ; Tue, 28 Jul 1998 15:10:32 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id PAA18753; Tue, 28 Jul 1998 15:09:51 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd018651; Tue Jul 28 15:09:40 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id PAA19411; Tue, 28 Jul 1998 15:09:34 -0700 (MST) From: Terry Lambert Message-Id: <199807282209.PAA19411@usr04.primenet.com> Subject: Re: Serious Dump problems To: Tor.Egge@fast.no Date: Tue, 28 Jul 1998 22:09:34 +0000 (GMT) Cc: karl@mcs.net, current@FreeBSD.ORG In-Reply-To: <199807281519.RAA12042@pat.idi.ntnu.no> from "Tor.Egge@fast.no" at Jul 28, 98 05:19:47 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have a dump tape which is intact, yet restore complains about "hole in > > map" and segv's when attempting to start up in interactive mode. > > Philip Inglesant gave a good description of this > problem on the -stable list. > > You probably had more than 4 million inodes on the file system. Thus > the bitmaps uses more than 512 KB(i.e. more than 512 tape blocks). > > Running dump/restore using a 51 GB partition (with 13 million inodes > gave the same problem for me. This is a very good catch. I looked at this problem when it was originally reported several months ago, and it seemed to me that the only way it could happen were if there actually were a hole in the map. The only thing I could conclude was that there was "something wrong with the data". > > It appears that dump and restore are VERY old, and nobody is maintaining > > them. Interestingly enough, a new dump of the same filesystem produces > > the same error, so I suspect a problem with dump where it is writing out a > > bad directory map. > > It is not sufficient to only change dump. The calculation of maxino > in restore depends upon the current behavior of dump, using a > value larger than 512 in the c_count field when the number of inodes > is larger than 4 million. > > Only a small change to restore is needed. Is it sufficient to change restore? Or is this patch going to result in part of the dumped data being inaccessable? Is a change to dump *also* necessary? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 15:58:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10238 for freebsd-current-outgoing; Tue, 28 Jul 1998 15:58:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10097 for ; Tue, 28 Jul 1998 15:57:23 -0700 (PDT) (envelope-from pb@fasterix.frmug.org) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA14902; Wed, 29 Jul 1998 00:56:31 +0200 (CEST) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.8.8/8.8.5/pb-19970302) id AAA17147; Wed, 29 Jul 1998 00:55:53 +0200 (CEST) Message-ID: <19980729005552.A16035@fasterix.frmug.fr.net> Date: Wed, 29 Jul 1998 00:55:52 +0200 From: Pierre Beyssac To: Terry Lambert , current@FreeBSD.ORG Subject: Re: Diagnostic for those with MMAP problems... References: <199807280048.RAA16684@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: <199807280048.RAA16684@usr01.primenet.com>; from Terry Lambert on Tue, Jul 28, 1998 at 12:48:24AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 28, 1998 at 12:48:24AM +0000, Terry Lambert wrote: > the first is probably impractical for those repeating the glitch > using INN, but it's worth mentioning. I don't care: a good news spool is a trashed news spool :-) I haven't yet tried the NO_SWAPPING test you suggest; I'm reporting on the following I just tried: > 2) Rebuild the software using MMAP; add "PROT_WRITE" to > the protection request. Apparently INN 2.0 does this already for the active file (but, interestingly enough, not for the dbz file when it's open read-only). >From innd/icd.c: ICDactpointer = mmap((caddr_t)0, ICDactsize, PROT_READ|PROT_WRITE, MAP__ARG, ICDactfd, (OFFSET_T)0); I'm going to try to define MMAP_SYNC to DO to enable the following code in the same file: if (msync(ICDactpointer, ICDactsize, MS_ASYNC) < 0) { syslog(L_FATAL, "%s msync failed %s %m", LogName, ICDactpath); exit(1); } I'll post the results here if anything interesting comes up. -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 16:27:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14531 for freebsd-current-outgoing; Tue, 28 Jul 1998 16:27:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14480 for ; Tue, 28 Jul 1998 16:26:30 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id XAA22161; Tue, 28 Jul 1998 23:50:43 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807282250.XAA22161@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Kris Kennaway cc: ben@rosengart.com, "Jan B. Koum " , current@FreeBSD.ORG Subject: Re: ppp driving me nuts In-reply-to: Your message of "Tue, 28 Jul 1998 19:13:13 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 23:50:42 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just know that doing that never seemed to prevent the session from > timing out after 3 minutes. I was going to get around to > investigating this further & submitting a formal report, but it seems to > have come up anyway :) > > I also seem to remember something about the redial timeout not quite > working as it is documented in the manpages.. > > Kris I'm afraid nothing'll get fixed unless your problem is nailed down a bit more firmly. Are you saying that ``set timeout 0'' followed by ``show bundle'' suggests that the idle timer is still around ? And when the connection is up (after ``set timeout 0''), does ``show timers'' show an idle timer ? Try putting ``set log command phase ipcp'' as the first statement in your default section and sending me the output if ppp is timing out after the ``set timeout 0''. Cheers. -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 16:27:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14590 for freebsd-current-outgoing; Tue, 28 Jul 1998 16:27:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14535 for ; Tue, 28 Jul 1998 16:27:00 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id XAA22123; Tue, 28 Jul 1998 23:42:43 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807282242.XAA22123@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: ben@rosengart.com cc: "Jan B. Koum " , current@FreeBSD.ORG Subject: Re: ppp driving me nuts In-reply-to: Your message of "Tue, 28 Jul 1998 01:23:46 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 23:42:42 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > PPP ON narcissus> show timeout > Warning: show timeout: Invalid command > Warning: show timeout: Failed 1 A quick look at the SETTING THE IDLE TIMER section of the man page reveals that ``show timeout'' has been rolled into the ``show bundle'' command. Most of the low-output ``show'' commands are now less specific than they used to be. > Ben > > "You have your mind on computers, it seems." -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 17:40:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25666 for freebsd-current-outgoing; Tue, 28 Jul 1998 17:40:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pat.idi.ntnu.no (0@pat.idi.ntnu.no [129.241.103.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25557 for ; Tue, 28 Jul 1998 17:39:03 -0700 (PDT) (envelope-from Tor.Egge@fast.no) From: Tor.Egge@fast.no Received: from idi.ntnu.no (tegge@ikke.idi.ntnu.no [129.241.111.65]) by pat.idi.ntnu.no (8.8.8/8.8.8) with ESMTP id CAA29832; Wed, 29 Jul 1998 02:38:13 +0200 (MET DST) Message-Id: <199807290038.CAA29832@pat.idi.ntnu.no> To: tlambert@primenet.com Cc: karl@mcs.net, current@FreeBSD.ORG Subject: Re: Serious Dump problems In-Reply-To: Your message of "Tue, 28 Jul 1998 22:09:34 +0000 (GMT)" References: <199807282209.PAA19411@usr04.primenet.com> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 29 Jul 1998 02:38:13 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is a very good catch. I looked at this problem when it was > originally reported several months ago, and it seemed to me that > the only way it could happen were if there actually were a hole > in the map. The only thing I could conclude was that there was > "something wrong with the data". I had help (a very useful message posted to -stable). I also had the opportunity to reproduce the problem, and the inclination to fix it (since I could become a victim myself). > Is it sufficient to change restore? Yes. > Or is this patch going to result in part of the dumped data > being inaccessable? No. > Is a change to dump *also* necessary? IMO, not as long as we only want to use FreeBSD restore. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 17:48:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27171 for freebsd-current-outgoing; Tue, 28 Jul 1998 17:48:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26986 for ; Tue, 28 Jul 1998 17:47:14 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id KAA12635; Wed, 29 Jul 1998 10:16:24 +0930 (CST) Received: by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA27017; Wed, 29 Jul 1998 10:16:21 +0930 Date: Wed, 29 Jul 1998 10:16:21 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@mercury To: Brian Somers Cc: ben@rosengart.com, "Jan B. Koum " , current@FreeBSD.ORG Subject: Re: ppp driving me nuts In-Reply-To: <199807282250.XAA22161@awfulhak.org> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Jul 1998, Brian Somers wrote: > I'm afraid nothing'll get fixed unless your problem is nailed down a > bit more firmly. Yup, as I said I was gonna look into identifying the problems more thoroughly..I just mentioned it since others also said they were having trouble. > Are you saying that ``set timeout 0'' followed by ``show bundle'' > suggests that the idle timer is still around ? And when the > connection is up (after ``set timeout 0''), does ``show timers'' show > an idle timer ? > > Try putting ``set log command phase ipcp'' as the first statement in > your default section and sending me the output if ppp is timing out > after the ``set timeout 0''. Okay, I'll try those & see what I can find out. Thanks for the response, Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 18:30:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06878 for freebsd-current-outgoing; Tue, 28 Jul 1998 18:30:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06766 for ; Tue, 28 Jul 1998 18:29:50 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id VAA12513; Tue, 28 Jul 1998 21:29:11 -0400 (EDT) Date: Tue, 28 Jul 1998 21:29:11 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Doug White cc: current@FreeBSD.ORG Subject: Re: more PPP weirdness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Jul 1998, Doug White wrote: > Now that's wierd: ppp showing routes that netstat -rn doesn't. :-/ But netstat -ran does. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 19:28:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15686 for freebsd-current-outgoing; Tue, 28 Jul 1998 19:28:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA15609 for ; Tue, 28 Jul 1998 19:28:01 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z1Lxh-0002am-00; Tue, 28 Jul 1998 20:27:29 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id UAA28016; Tue, 28 Jul 1998 20:31:15 -0600 (MDT) Message-Id: <199807290231.UAA28016@harmony.village.org> To: Karl Denninger Subject: Re: Serious Dump problems Cc: Tor.Egge@fast.no, current@FreeBSD.ORG In-reply-to: Your message of "Tue, 28 Jul 1998 14:06:15 CDT." <19980728140615.27193@mcs.net> References: <19980728140615.27193@mcs.net> <199807281519.RAA12042@pat.idi.ntnu.no> <19980728073523.02311@mcs.net> <199807281519.RAA12042@pat.idi.ntnu.no> <199807281858.MAA16754@harmony.village.org> Date: Tue, 28 Jul 1998 20:31:15 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980728140615.27193@mcs.net> Karl Denninger writes: : I tried a restore from a tape which had formerly been unreadable (without : the patch) and it was fine. : : I know that's not a LOT of testing, but its some, and it definitely starts : up and "plays nice" as best as I can determine. OK. Sounds good. I'll wait a couple of days to backport it to -stable. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 21:50:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08035 for freebsd-current-outgoing; Tue, 28 Jul 1998 21:50:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (root@mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08030 for ; Tue, 28 Jul 1998 21:50:18 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from support1.cybcon.com (william@support1.cybcon.com [205.147.76.99]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id VAA05003 for ; Tue, 28 Jul 1998 21:49:35 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 28 Jul 1998 21:48:57 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: current@FreeBSD.ORG Subject: Latest 3.0 -snap Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whats with this....... /usr/src/Makefile" , Line 369: Malformed conditional ($(MACHINE_ARCH0 == "i386") /usr/src/Makefile" , Line 369: Need an operator /usr/src/Makefile" , Line 604: Malformed conditional ($(MACHINE_ARCH0 == "i386") /usr/src/Makefile" , Line 604: Need an operator /usr/src/Makefile" , Line 614: if-less endif /usr/src/Makefile" , Line 864: if-less endif /usr/src/Makefile" , Line 864: Need an operator make: fatal errors encountered -- cannont continue ---------------------------------- William Woods --> FreeBSD 2.2.7 <-- Date: 28-Jul-98 Time: 21:43:25 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 21:54:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08651 for freebsd-current-outgoing; Tue, 28 Jul 1998 21:54:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA08636 for ; Tue, 28 Jul 1998 21:54:39 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1650 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Wed, 29 Jul 1998 06:53:49 +0200 (METDST) (Smail-3.2.0.101 1997-Dec-17 #2 built 1998-Jun-26) Received: by hcswork.hcs.de (Smail3.1.29.0 #12) id m0z1OHb-0000f3C; Wed, 29 Jul 98 06:56 METDST Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: Re: something new in current, that might create a leased line ? In-Reply-To: <19980728230947.A3455@klemm.gtn.com> from Andreas Klemm at "Jul 28, 98 11:09:47 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Wed, 29 Jul 1998 06:56:11 +0200 (METDST) Cc: current@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From the keyboard of Andreas Klemm: > The name server requests doesn't stop, so the ISDN line stays up. > Look at the bad cksum lines ... > Current / make world from yesterday ... > > 23:06:24.775498 pppak04.gtn.com.1048 > a.root-servers.net.domain: 23139 (45) > (ttl 64, id 2698) > 23:06:25.232311 248.17.235.100 > a.root-servers.net: (frag 17664:-27@1272) > [tos 0x3] (ttl 146, bad cksum 4000!, optlen=40[|ip]) You didn't switch on VJ compression (link0) by accident ? hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm@hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 23:06:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18059 for freebsd-current-outgoing; Tue, 28 Jul 1998 23:06:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA18039 for ; Tue, 28 Jul 1998 23:06:36 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id IAA05446; Wed, 29 Jul 1998 08:00:11 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id HAA02105; Wed, 29 Jul 1998 07:58:43 +0200 (CEST) (envelope-from andreas) Message-ID: <19980729075843.A2098@klemm.gtn.com> Date: Wed, 29 Jul 1998 07:58:43 +0200 From: Andreas Klemm To: hm@hcs.de Cc: current@FreeBSD.ORG Subject: Re: something new in current, that might create a leased line ? References: <19980728230947.A3455@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from Hellmuth Michaelis on Wed, Jul 29, 1998 at 06:56:11AM +0200 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 29, 1998 at 06:56:11AM +0200, Hellmuth Michaelis wrote: BTW; seemed to be something like a race condition, since after rebooting this morning, i4b hangs up without problems ... And yesterday evening was the first time I experienced that trouble. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 23:06:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18114 for freebsd-current-outgoing; Tue, 28 Jul 1998 23:06:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA18084 for ; Tue, 28 Jul 1998 23:06:44 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id IAA05445; Wed, 29 Jul 1998 08:00:06 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id HAA02093; Wed, 29 Jul 1998 07:57:30 +0200 (CEST) (envelope-from andreas) Message-ID: <19980729075730.A1480@klemm.gtn.com> Date: Wed, 29 Jul 1998 07:57:30 +0200 From: Andreas Klemm To: hm@hcs.de Cc: current@FreeBSD.ORG Subject: Re: something new in current, that might create a leased line ? References: <19980728230947.A3455@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from Hellmuth Michaelis on Wed, Jul 29, 1998 at 06:56:11AM +0200 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 29, 1998 at 06:56:11AM +0200, Hellmuth Michaelis wrote: > >From the keyboard of Andreas Klemm: > > > The name server requests doesn't stop, so the ISDN line stays up. > > Look at the bad cksum lines ... > > Current / make world from yesterday ... > > > > 23:06:24.775498 pppak04.gtn.com.1048 > a.root-servers.net.domain: 23139 (45) > > (ttl 64, id 2698) > > 23:06:25.232311 248.17.235.100 > a.root-servers.net: (frag 17664:-27@1272) > > [tos 0x3] (ttl 146, bad cksum 4000!, optlen=40[|ip]) > > You didn't switch on VJ compression (link0) by accident ? No. isppp0: flags=2851 mtu 1500 inet 194.231.123.169 --> 194.231.123.161 netmask Btw, I got a reply from Stefan Schmidt indicating an "off-by-4 error in i4b_isppp.c around line 600. I don't know which changes he made exactly, but he told me, that after the change the errors went away. And these are my kernel settings: # # ISDN kernel # machine "i386" cpu "I686_CPU" ident ISDNSMP # rse's recommendations for heavily users apache servers maxusers 256 #options SOMAXCONN="256" #options "NMBCLUSTER=4096" #options "CHILD_MAX=512" #options "OPEN_MAX=512" # Options for the VM subsystem #options PQ_NOOPT # No coloring #options PQ_LARGECACHE # color for 512k/16k cache options PQ_HUGECACHE # color for 1024k/16k cache options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O options INCLUDE_CONFIG_FILE # Include this file in kernel #options USERCONFIG #boot -c editor #options VISUAL_USERCONFIG #visual boot -c editor options DDB options KTRACE #kernel tracing options SHOW_BUSYBUFS # busy buffers on shutdown ? options INET #InterNETworking options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about dropped packets options "IPFIREWALL_VERBOSE_LIMIT=500" #limit verbosity options IPDIVERT #divert sockets #options IPFILTER #kernel ipfilter support #options IPFILTER_LOG #ipfilter logging options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" options FFS #Berkeley Fast Filesystem #options NFS #Network File System options MFS #Memory File System #options UNION #Union filesystem options "CD9660" #ISO 9660 filesystem options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options NSWAPDEV=3 #Allow this many swap-devices. #options QUOTA #enable disk quotas options SOFTUPDATES #Kirk McKusick's code # DEVFS and SLICE are experimental but work. # SLICE disables too much old code so enabling it in LINT would be bad #options DEVFS #devices filesystem #options SLICE #devfs based disk handling # misc options options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options SYSVSHM,SYSVSEM,SYSVMSG #shared memory (X11) options COMPAT_LINUX # Linux Binary compatibility #options USER_LDT # for Wine options "MD5" #options "VM86" config kernel root on sd1 # ISA and PCI BUS support controller isa0 controller pci0 # Floppy Disk Controller controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 # SCSI Devices # AHA 2940U controller ahc0 controller scbus0 at ahc0 disk sd0 at scbus0 target 0 unit 0 disk sd3 at scbus0 target 1 unit 0 tape st0 at scbus0 target 4 device worm0 at scbus0 target 5 device cd0 at scbus0 target 6 # AHA 2940 controller ahc1 controller scbus1 at ahc1 disk sd1 at scbus1 target 1 unit 0 disk sd2 at scbus1 target 2 unit 0 device pt0 at scbus1 target 6 unit 0 options SCSI_DELAY=15 # Be pessimistic about Joe SCSI device options "CD9660_ROOTDELAY=8" options AHC_TAGENABLE # tagged command queueing options AHC_ALLOW_MEMIO options AHC_SCBPAGING_ENABLE options SCSI_REPORT_GEOMETRY # SCO compatible system console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options MAXCONS=4 # number of virtual consoles options SC_HISTORY_SIZE=200 # number of history buffer lines # The pcvt console driver (vt220 compatible). #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options XSERVER # support for running an X server. #options FAT_CURSOR # start with block cursor # floating point unit device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr # serial devices on mainboard # `flags' for serial drivers that support consoles (only for sio now): # 0x10 enable console support for this unit. The other console flags # are ignored unless this is set. Enabling console support does # not make the unit the preferred console - boot with -h or set # the 0x20 flag for that. Currently, at most one unit can have # console support; the first one (in config file order) with # this flag set is preferred. Setting this flag for sio0 gives # the old behaviour. # 0x20 force this unit to be the console (unless there is another # higher priority console). This replaces the COMCONSOLE option. # 0x40 reserve this unit for low level console operations. Do not # device sio0 at isa? port "IO_COM1" tty irq 4 flags 0x20 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes to DDB, #if available. options CONSPEED=38400 #default speed for serial console #(default 9600) # parallel device on mainboard device lpt0 at isa? port? tty irq 7 vector lptintr # PS/2 mouse on mainboard device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr options "PSM_ACCEL=1" # PS/2 mouse acceleration # Joystick #device joy0 at isa? port "IO_GAME" # Network 3COM PCI device vx0 #device ed0 at isa? port 0x280 net irq 10 iomem 0xd0000 vector edintr # Soundblaster 16 # SoundBlaster DSP driver - for SB, SB Pro, SB16, PAS(emulating SB) # SoundBlaster 16 DSP driver - for SB16 - requires sb0 device # SoundBlaster 16 MIDI - for SB16 - requires sb0 device # Yamaha OPL-2/OPL-3 FM - for SB, SB Pro, SB16, PAS # controller snd0 # device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr # device sbxvi0 at isa? port? irq? drq 5 conflicts # device sbmidi0 at isa? port 0x330 irq? conflicts # device opl0 at isa? port 0x388 conflicts # pcm: PCM audio through various sound cards. # New Sound code device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x15 vector pcmintr # Pseudo devices pseudo-device loop #Network loopback device pseudo-device ether #Generic Ethernet pseudo-device vn 1 #Vnode driver (turns a file into a dev.) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device disc #Discard device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device pty 16 #Pseudo ttys - can go as high as 256 pseudo-device gzip # Exec gzipped a.out's pseudo-device ccd 4 #Concatenated disk driver pseudo-device tun 1 #Tunnel driver (user process ppp(8)) #pseudo-device ppp 1 #Point-to-point protocol #options PPP_BSDCOMP #PPP BSD-compress support #options PPP_DEFLATE #PPP zlib/deflate/gzip support #options PPP_FILTER #enable bpf filtering (needs bpfilter) # Size of the kernel message buffer. Should be N * pagesize. options "MSGBUF_SIZE=40960" ## BISDN #options IPI_VJ # Van Jacobsen header compression support ##options "IPI_DIPA=3" # send ip accounting packets every 3 seconds #options TELES_HAS_MEMCPYB # bisdn 0.97 # ## Teles S0/16.3 ################################################### IRQ 9 ## #controller tel0 at isa? port 0xd80 net irq 9 vector telintr #pseudo-device disdn #pseudo-device isdn #pseudo-device ipi 4 #pseudo-device ispy 4 #pseudo-device itel 1 options "I4B_SMP_WORKAROUND" # i4b passive ISDN cards support (isic - I4b Siemens Isdn Chipset driver) # Teles S0/16.3 options "TEL_S0_16_3" device isic0 at isa? port 0xd80 net irq 9 flags 0x04 vector isicintr # i4b passive cards D channel handling # Q.921 pseudo-device "i4bq921" # Q.931 pseudo-device "i4bq931" # common passive and active layer 4 # layer 4 pseudo-device "i4b" # userland driver to do ISDN tracing (for passive cards oly) pseudo-device "i4btrc" 4 # userland driver to control the whole thing pseudo-device "i4bctl" # userland driver for access to raw B channel pseudo-device "i4brbch" 4 # userland driver for telephony pseudo-device "i4btel" 2 # network driver for IP over raw HDLC ISDN pseudo-device "i4bipr" 4 # enable VJ header compression detection for ipr i/f options IPR_VJ # network driver for sync PPP over ISDN pseudo-device "i4bisppp" 4 pseudo-device sppp 4 -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 23:15:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19649 for freebsd-current-outgoing; Tue, 28 Jul 1998 23:15:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19642 for ; Tue, 28 Jul 1998 23:15:56 -0700 (PDT) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id PAA10591; Wed, 29 Jul 1998 15:44:56 +0930 (CST) Received: from eddie.dsto.defence.gov.au ([131.185.2.111]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id PMP5XGLT; Wed, 29 Jul 1998 15:45:16 +0930 Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id PAA00511; Wed, 29 Jul 1998 15:45:19 +0930 (CST) Message-ID: <35BEBDF4.4431DED0@dsto.defence.gov.au> Date: Wed, 29 Jul 1998 15:45:16 +0930 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Kris Kennaway CC: FreeBSD CURRENT Subject: Re: ppp driving me nuts References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I use usermode ppp as "ppp target" where my target does the dial (after setting authkey etc). If the first dial fails (say due to the number being busy) typing 'dial' at the 'ppp' prompt makes ppp do nothing until the original dial timeout has elapsed (at least that's how it appears to me). So rather than waiting 40 seconds or so (my dial timeout is 120 sec) I quit ppp and just type "ppp target" again. This is nothing to do with redial timeouts I think its the original dial timeout that is still ticking away for some reason even though ppp has already told me that the first dial has failed. Kris Kennaway wrote: > > On Tue, 28 Jul 1998, Snob Art Genre wrote: > > > On Tue, 28 Jul 1998, Kris Kennaway wrote: > > > > > I seem to recall that theres a 3 minute idle timeout which cannot be > > > overridden if you start the ppp session from interactive mode. I often > > > > Why wouldn't "set timeout 0" override? I load my provider profile with > > a "load" directive in the conf file, and just log in as ppp with ppp as > > my shell and type "dial", btw. And a "show timers" doesn't show any > > idle timer running. > > I just know that doing that never seemed to prevent the session from > timing out after 3 minutes. I was going to get around to > investigating this further & submitting a formal report, but it seems to > have come up anyway :) > > I also seem to remember something about the redial timeout not quite > working as it is documented in the manpages.. > > Kris > > > > > > > Ben > > > > "You have your mind on computers, it seems." > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 28 23:26:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21361 for freebsd-current-outgoing; Tue, 28 Jul 1998 23:26:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA21325 for ; Tue, 28 Jul 1998 23:26:31 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1535 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Wed, 29 Jul 1998 08:25:43 +0200 (METDST) (Smail-3.2.0.101 1997-Dec-17 #2 built 1998-Jun-26) Received: by hcswork.hcs.de (Smail3.1.29.0 #12) id m0z1PiX-0000f3C; Wed, 29 Jul 98 08:28 METDST Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: Re: something new in current, that might create a leased line ? In-Reply-To: <19980729075730.A1480@klemm.gtn.com> from Andreas Klemm at "Jul 29, 98 07:57:30 am" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Wed, 29 Jul 1998 08:28:05 +0200 (METDST) Cc: hm@hcs.de, current@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From the keyboard of Andreas Klemm: > Btw, I got a reply from > Stefan Schmidt > indicating an "off-by-4 error in i4b_isppp.c around line 600. > I don't know which changes he made exactly, but he told me, that > after the change the errors went away. Now it would be nice to know what he did exactly .... hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm@hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 00:11:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29642 for freebsd-current-outgoing; Wed, 29 Jul 1998 00:11:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29628 for ; Wed, 29 Jul 1998 00:11:26 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id IAA10327; Wed, 29 Jul 1998 08:06:21 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807290706.IAA10327@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Thyer cc: Kris Kennaway , FreeBSD CURRENT Subject: Re: ppp driving me nuts In-reply-to: Your message of "Wed, 29 Jul 1998 15:45:16 +0930." <35BEBDF4.4431DED0@dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 08:06:21 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm, I guess the ``dial'' command should nuke the redial timer if it exists. This is a bug. The redial timer is used by the datalink state machine to honour your ``set redial''. I'll fix it. > I use usermode ppp as "ppp target" where my target does the > dial (after setting authkey etc). > > If the first dial fails (say due to the number being busy) typing > 'dial' at the 'ppp' prompt makes ppp do nothing until the original > dial timeout has elapsed (at least that's how it appears to me). > > So rather than waiting 40 seconds or so (my dial timeout is 120 sec) > I quit ppp and just type "ppp target" again. > > This is nothing to do with redial timeouts I think its the original > dial timeout that is still ticking away for some reason even though > ppp has already told me that the first dial has failed. > > > Kris Kennaway wrote: > > > > On Tue, 28 Jul 1998, Snob Art Genre wrote: > > > > > On Tue, 28 Jul 1998, Kris Kennaway wrote: > > > > > > > I seem to recall that theres a 3 minute idle timeout which cannot be > > > > overridden if you start the ppp session from interactive mode. I often > > > > > > Why wouldn't "set timeout 0" override? I load my provider profile with > > > a "load" directive in the conf file, and just log in as ppp with ppp as > > > my shell and type "dial", btw. And a "show timers" doesn't show any > > > idle timer running. > > > > I just know that doing that never seemed to prevent the session from > > timing out after 3 minutes. I was going to get around to > > investigating this further & submitting a formal report, but it seems to > > have come up anyway :) > > > > I also seem to remember something about the redial timeout not quite > > working as it is documented in the manpages.. > > > > Kris > > > > > > > > > > > Ben > > > > > > "You have your mind on computers, it seems." > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- > Matthew Thyer Phone: +61 8 8259 7249 > Corporate Information Systems Fax: +61 8 8259 5537 > Defence Science and Technology Organisation, Salisbury > PO Box 1500 Salisbury South Australia 5108 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 01:04:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA07323 for freebsd-current-outgoing; Wed, 29 Jul 1998 01:04:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tuminfo2.informatik.tu-muenchen.de (root@tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA07305 for ; Wed, 29 Jul 1998 01:04:14 -0700 (PDT) (envelope-from sts@mediaintegration.com) Received: from hphalle0.informatik.tu-muenchen.de ([131.159.4.1] EHLO hphalle0.informatik.tu-muenchen.de ident: root [port 4629]) by tuminfo2.informatik.tu-muenchen.de with ESMTP id <110811-2855>; Wed, 29 Jul 1998 10:03:04 +0000 Received: from IDENT-NOT-QUERIED@schmidts.modem.informatik.tu-muenchen.de (port 1028 [172.16.0.35]) by hphalle0.informatik.tu-muenchen.de with SMTP id <1156-4296>; Wed, 29 Jul 1998 10:02:43 +0000 Date: Wed, 29 Jul 1998 10:04:07 +0200 (CEST) From: Stefan Schmidt To: Hellmuth Michaelis cc: Andreas Klemm , current@FreeBSD.ORG Subject: Re: something new in current, that might create a leased line ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > Stefan Schmidt > > indicating an "off-by-4 error in i4b_isppp.c around line 600. > > I don't know which changes he made exactly, but he told me, that > > after the change the errors went away. > > Now it would be nice to know what he did exactly .... in i4b/driver/i4b_isppp.c, around line 600, there's some code to prepend the address family as a four byte field. this seems to be unnecessary for -CURRENT. bpf_mtap( &sc->sc_if, m) works for me. stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 01:18:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09073 for freebsd-current-outgoing; Wed, 29 Jul 1998 01:18:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (root@mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09068 for ; Wed, 29 Jul 1998 01:18:57 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from support1.cybcon.com (william@support1.cybcon.com [205.147.76.99]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id BAA11113 for ; Wed, 29 Jul 1998 01:18:25 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 29 Jul 1998 01:17:53 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: current@FreeBSD.ORG Subject: Upgrading from 2.2.7 to Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a FAQ somewhere that deals with the steps nessary to upgrade from 2.2.7-STABLE to -CURRENT? ---------------------------------- William Woods --> FreeBSD 2.2.7 <-- Date: 29-Jul-98 Time: 01:16:53 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 01:36:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11951 for freebsd-current-outgoing; Wed, 29 Jul 1998 01:36:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11944 for ; Wed, 29 Jul 1998 01:36:22 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id KAA02474 ; Wed, 29 Jul 1998 10:34:36 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id KAA29383; Wed, 29 Jul 1998 10:34:34 +0200 To: Doug White Cc: =?X-UNKNOWN?Q?Dag-Erling_Coidan_Sm=F8rgrav?= , Hostas Red , current@FreeBSD.ORG Subject: Re: Strange idle times References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 29 Jul 1998 10:34:34 +0200 In-Reply-To: Doug White's message of Tue, 28 Jul 1998 11:34:27 -0700 (PDT) Message-ID: Lines: 15 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White writes: > On 28 Jul 1998, Dag-Erling Coidan Smørgrav wrote: > > I checked, and I have the same problem on my -current box. All my vtys > > and ptys show up with as much idle time as the machine's uptime. I ssh > > a lot öut"from this box, but very little *into* it, so the fubared > > ptys are mostly xterms. > There's a known bug in xterm. The bugfixed version doesn't use utmp > (which I don't like), but it stops the corruption. Hmmm... I run XFree86 3.3.2 patchlevel 2, which I suppose has the bugfixed xterm. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 01:38:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12375 for freebsd-current-outgoing; Wed, 29 Jul 1998 01:38:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12364 for ; Wed, 29 Jul 1998 01:38:26 -0700 (PDT) (envelope-from ehritz@dbai.tuwien.ac.at) Received: from arcturus.dbai.tuwien.ac.at (arcturus.dbai.tuwien.ac.at [128.130.111.20]) by vexpert.dbai.tuwien.ac.at (8.8.8/8.8.8) with ESMTP id KAA20962 for ; Wed, 29 Jul 1998 10:37:51 +0200 (MET-DST) From: Gerald Ehritz Received: (from ehritz@localhost) by arcturus.dbai.tuwien.ac.at (8.8.5/8.8.5) id KAA11970 for freebsd-current@freebsd.org; Wed, 29 Jul 1998 10:37:49 +0200 (MET DST) Date: Wed, 29 Jul 1998 10:37:49 +0200 (MET DST) Message-Id: <199807290837.KAA11970@arcturus.dbai.tuwien.ac.at> To: freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 completely X-Sun-Charset: US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi to all who contributed to this, I made a test with pine 4.02 today, and it also locks up the machine completely. So i want to clear up what was gouing on till now: 1.) We used a FreeBSD 2.2 box for modem login since 2 years. In June i upgraded to 3.0 snap and everything works except pine locks up the pc. 2.) We allways had NFS mounted mail- and user- dirs! ( and it worked). No changes on the server (SunOS 4.1.3_U1). 3.) All versions of pine (2.2.6 code, 3.0 code, version 3.96, 4.0 and 4.02) kill the machine IF i write out an attachment ( may be > 100k size) to the home dir (NFS mounted), works if write it to /tmp! 4.) Pine works IF i only read and write mails (mail NFS mounted)! Next week i have a chance to upgrade to a newer version of 3.0, but i am asking me if it really stop pine from crashing. May be it's a problem with mmap, but how can i check it? Was my old FreeBSD without mmap? regards, Gerald ________________________________________________________ Gerald Ehritz ehritz@dbai.tuwien.ac.at Institut f. Informationssysteme Technische Universitaet Wien ________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 01:49:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14074 for freebsd-current-outgoing; Wed, 29 Jul 1998 01:49:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tyree.iii.co.uk (tyree.iii.co.uk [195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14066 for ; Wed, 29 Jul 1998 01:49:35 -0700 (PDT) (envelope-from nik@iii.co.uk) From: nik@iii.co.uk Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id JAA04261; Wed, 29 Jul 1998 09:48:55 +0100 (BST) Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.8/8.8.7) id JAA09492; Wed, 29 Jul 1998 09:48:50 +0100 (BST) Message-ID: <19980729094849.A9484@iii.co.uk> Date: Wed, 29 Jul 1998 09:48:49 +0100 To: wwoods@cybcon.com, current@FreeBSD.ORG Subject: Re: Upgrading from 2.2.7 to Current References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from William Woods on Wed, Jul 29, 1998 at 01:17:53AM -0700 Organization: interactive investor Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 29, 1998 at 01:17:53AM -0700, William Woods wrote: > Is there a FAQ somewhere that deals with the steps nessary to upgrade from > 2.2.7-STABLE to -CURRENT? If you're planning on doing this by installing the sources and running 'make world' then see section 18.4 of the Handbook before you start. If I understand correctly there is currently an issue with bootstrapping the build, and commands like # make buildworld will need to have the flag "-m /usr/src/sys/mk" passed, like # make -m /usr/src/sys/mk buildworld so. Other than that, it's believed to work fine. N -- "Last night I had a dream. I found myself in a desert called Cyberland. It was hot, my canteen had sprung a leak and I was thirsty. Out of the abyss walked a cow, Elsie. I asked if she had anything to drink. She said `I'm forbidden to produce milk. In Cyberland we only drink. . . Diet Coke.'" -- Maureen, _Rent_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 01:51:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14533 for freebsd-current-outgoing; Wed, 29 Jul 1998 01:51:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14508 for ; Wed, 29 Jul 1998 01:51:31 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id JAA02530; Wed, 29 Jul 1998 09:50:51 +0100 (BST) Message-ID: <35BEE26B.4DB6542@tdx.co.uk> Date: Wed, 29 Jul 1998 09:50:51 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.5b1 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Karl Denninger CC: current@FreeBSD.ORG Subject: Re: Serious Dump problems References: <19980728073523.02311@mcs.net> <199807281519.RAA12042@pat.idi.ntnu.no> <19980728102807.42807@mcs.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Denninger wrote: > > On Tue, Jul 28, 1998 at 05:19:47PM +0200, Tor.Egge@fast.no wrote: > > > Hi folks, > > > > > > I have an interesting one here... > > > > > > I have a dump tape which is intact, yet restore complains about "hole in > > > map" and segv's when attempting to start up in interactive mode. > > > > Philip Inglesant gave a good description of this > > problem on the -stable list. > > > > You probably had more than 4 million inodes on the file system. Thus > > the bitmaps uses more than 512 KB(i.e. more than 512 tape blocks). This may be completely unconnected - but didn't someone mention a while ago - similar problems when backing up a filesystem that isn't consistent (i.e. would fail or need an fsck run on it)? Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 03:07:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24210 for freebsd-current-outgoing; Wed, 29 Jul 1998 03:07:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ady.warpnet.ro (ady.warpnet.ro [193.230.201.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA24181 for ; Wed, 29 Jul 1998 03:07:11 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.8.8/8.8.8) with SMTP id NAA05988; Wed, 29 Jul 1998 13:05:19 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Wed, 29 Jul 1998 13:05:18 +0300 (EEST) From: Adrian Penisoara To: Gerald Ehritz cc: freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 completely In-Reply-To: <199807290837.KAA11970@arcturus.dbai.tuwien.ac.at> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Wed, 29 Jul 1998, Gerald Ehritz wrote: > Hi to all who contributed to this, > > I made a test with pine 4.02 today, and it also locks up the machine >completely. Hmmm, so no luck even with the latest... > > So i want to clear up what was gouing on till now: > > 1.) We used a FreeBSD 2.2 box for modem login since 2 years. In June i >upgraded to 3.0 snap and everything works except pine locks up the pc. > > 2.) We allways had NFS mounted mail- and user- dirs! ( and it worked). >No changes on the server (SunOS 4.1.3_U1). Changes have been made on the client side anyway; maybe this is all about it... > > 3.) All versions of pine (2.2.6 code, 3.0 code, version 3.96, 4.0 and >4.02) kill the machine IF i write out an attachment ( may be > 100k size) >to the home dir (NFS mounted), works if write it to /tmp! This (almost) excludes Pine from being guilty... > > 4.) Pine works IF i only read and write mails (mail NFS mounted)! > > > Next week i have a chance to upgrade to a newer version of 3.0, but i >am asking me if it really stop pine from crashing. How are you upgrading ? make world/installing from zero ? If you were making world you might want to try reinstalling from scratch... there might have been some leftover pieces (?!?) from the previous version (possibly 2.2.6 ?)... > > May be it's a problem with mmap, but how can i check it? > Was my old FreeBSD without mmap? > > regards, > Gerald > ________________________________________________________ > Gerald Ehritz ehritz@dbai.tuwien.ac.at > Institut f. Informationssysteme > Technische Universitaet Wien > ________________________________________________________ > Just my $0.02, Ady (@freebsd.ady.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 05:00:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09124 for freebsd-current-outgoing; Wed, 29 Jul 1998 05:00:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09116 for ; Wed, 29 Jul 1998 05:00:19 -0700 (PDT) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-4-07.camtech.net.au [203.28.0.135]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id VAA26054; Wed, 29 Jul 1998 21:24:33 +0930 (CST) Message-ID: <35BF0D79.8D8194E@camtech.net.au> Date: Wed, 29 Jul 1998 21:24:33 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Brian Somers CC: Matthew Thyer , Kris Kennaway , FreeBSD CURRENT Subject: Re: ppp driving me nuts References: <199807290706.IAA10327@awfulhak.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I dont know what you mean by my use of "set redial". Here's my ppp.conf: default: set log chat connect phase set device /dev/cuaa1 set speed 115200 deny lqr deny pap set timeout 0 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT OK-AT-OK ATE1Q0L0 OK \\dATDT\\T TIMEOUT 120 CONNECT" set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 target: set phone set login set authname set authkey dial Brian Somers wrote: > > Hmm, > > I guess the ``dial'' command should nuke the redial timer if it > exists. This is a bug. The redial timer is used by the datalink > state machine to honour your ``set redial''. > > I'll fix it. > > > I use usermode ppp as "ppp target" where my target does the > > dial (after setting authkey etc). > > > > If the first dial fails (say due to the number being busy) typing > > 'dial' at the 'ppp' prompt makes ppp do nothing until the original > > dial timeout has elapsed (at least that's how it appears to me). > > > > So rather than waiting 40 seconds or so (my dial timeout is 120 sec) > > I quit ppp and just type "ppp target" again. > > > > This is nothing to do with redial timeouts I think its the original > > dial timeout that is still ticking away for some reason even though > > ppp has already told me that the first dial has failed. > > > > > > Kris Kennaway wrote: > > > > > > On Tue, 28 Jul 1998, Snob Art Genre wrote: > > > > > > > On Tue, 28 Jul 1998, Kris Kennaway wrote: > > > > > > > > > I seem to recall that theres a 3 minute idle timeout which cannot be > > > > > overridden if you start the ppp session from interactive mode. I often > > > > > > > > Why wouldn't "set timeout 0" override? I load my provider profile with > > > > a "load" directive in the conf file, and just log in as ppp with ppp as > > > > my shell and type "dial", btw. And a "show timers" doesn't show any > > > > idle timer running. > > > > > > I just know that doing that never seemed to prevent the session from > > > timing out after 3 minutes. I was going to get around to > > > investigating this further & submitting a formal report, but it seems to > > > have come up anyway :) > > > > > > I also seem to remember something about the redial timeout not quite > > > working as it is documented in the manpages.. > > > > > > Kris -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 05:28:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13246 for freebsd-current-outgoing; Wed, 29 Jul 1998 05:28:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from donny.ida.net (mail.ida.net [204.228.203.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA13214 for ; Wed, 29 Jul 1998 05:27:56 -0700 (PDT) (envelope-from muck@ida.net) Received: from falcon.hinterlands.com ([208.141.165.125]) by donny.ida.net (8.8.7/8.8.7) with SMTP id GAA15691; Wed, 29 Jul 1998 06:27:39 -0600 (MDT) Date: Wed, 29 Jul 1998 06:27:23 -0600 (MDT) From: Mike X-Sender: muck@falcon.hinterlands.com To: nik@iii.co.uk cc: wwoods@cybcon.com, current@FreeBSD.ORG Subject: Re: Upgrading from 2.2.7 to Current In-Reply-To: <19980729094849.A9484@iii.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Jul 1998 nik@iii.co.uk wrote: > On Wed, Jul 29, 1998 at 01:17:53AM -0700, William Woods wrote: > > Is there a FAQ somewhere that deals with the steps nessary to upgrade from > > 2.2.7-STABLE to -CURRENT? > > If you're planning on doing this by installing the sources and running > 'make world' then see section 18.4 of the Handbook before you start. > > If I understand correctly there is currently an issue with bootstrapping > the build, and commands like > > # make buildworld > > will need to have the flag "-m /usr/src/sys/mk" passed, like > > # make -m /usr/src/sys/mk buildworld > I thought it was "make -m /usr/src/share/mk buildworld"? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 06:38:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23968 for freebsd-current-outgoing; Wed, 29 Jul 1998 06:38:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de ([139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23934 for ; Wed, 29 Jul 1998 06:38:10 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.8/8.7.3) id PAA06279; Wed, 29 Jul 1998 15:34:59 +0200 (CEST) From: Holm Tiffe Message-Id: <199807291334.PAA06279@magnet.geophysik.tu-freiberg.de> Subject: Re: Answering myself, was: URGENT! ASUS P2B/LS supported ? In-Reply-To: <19980728120553.A22817@net.ohio-state.edu> from Mark Fullmer at "Jul 28, 98 12:05:53 pm" To: maf@net.ohio-state.edu (Mark Fullmer) Date: Wed, 29 Jul 1998 15:34:59 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG Reply-To: freebsd@magnet.geophysik.tu-freiberg.de X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, Jul 28, 1998 at 01:08:58PM +0200, Holm Tiffe wrote: [..] > > This is -stable around the 2.2.7 branch, not current. The pci code > has changed quite a bit in -current. > > chip2 rev 2 on pci0:4:0 > chip3 rev 1 on pci0:4:1 > chip4 rev 1 int d irq 12 on pci0:4:2 > chip5 rev 2 on pci0:4:3 > ahc0 rev 0 int a irq 12 on pci0:6:0 > pci_map_mem failed: bad memory type=0xfffff004 > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 32/255 SCBs > fxp0 rev 5 int a irq 10 on pci0:7:0 > avail memory = 259104768 (253032K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 chip3: rev 0x01 int d irq 255 on pci0.4.2 chip4: rev 0x02 on pci0.4.3 ahc0: rev 0x00 int a irq 15 on pci0.6.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 32/255 SCBs fxp0: rev 0x05 int a irq 10 on pci0.7.0 fxp0: Ethernet address 00:e0:18:90:2b:8f This is from my dmesg output. You are sure, that you have used the cam-drivers? [yeah, I know, a stupid question] (I've never tryed to use the old drivers) Have we the same revision of the host to pci bridge ? Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 06:54:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27228 for freebsd-current-outgoing; Wed, 29 Jul 1998 06:54:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26992 for ; Wed, 29 Jul 1998 06:53:54 -0700 (PDT) (envelope-from ehritz@dbai.tuwien.ac.at) Received: from arcturus.dbai.tuwien.ac.at (arcturus.dbai.tuwien.ac.at [128.130.111.20]) by vexpert.dbai.tuwien.ac.at (8.8.8/8.8.8) with ESMTP id PAA24414; Wed, 29 Jul 1998 15:53:02 +0200 (MET-DST) From: Gerald Ehritz Received: (from ehritz@localhost) by arcturus.dbai.tuwien.ac.at (8.8.5/8.8.5) id PAA12273; Wed, 29 Jul 1998 15:53:00 +0200 (MET DST) Date: Wed, 29 Jul 1998 15:53:00 +0200 (MET DST) Message-Id: <199807291353.PAA12273@arcturus.dbai.tuwien.ac.at> To: ady@warpnet.ro Subject: Re: pine 3.96 locks 3.0-980621 completely Cc: freebsd-current@FreeBSD.ORG X-Sun-Charset: US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > On Wed, 29 Jul 1998, Gerald Ehritz wrote: > > > Hi to all who contributed to this, > > > > I made a test with pine 4.02 today, and it also locks up the machine > >completely. > > Hmmm, so no luck even with the latest... > > > > > So i want to clear up what was gouing on till now: > > > > 1.) We used a FreeBSD 2.2 box for modem login since 2 years. In June i > >upgraded to 3.0 snap and everything works except pine locks up the pc. > > > > 2.) We allways had NFS mounted mail- and user- dirs! ( and it worked). > >No changes on the server (SunOS 4.1.3_U1). > > Changes have been made on the client side anyway; maybe this is all > about it... > > > > > 3.) All versions of pine (2.2.6 code, 3.0 code, version 3.96, 4.0 and > >4.02) kill the machine IF i write out an attachment ( may be > 100k size) > >to the home dir (NFS mounted), works if write it to /tmp! > > This (almost) excludes Pine from being guilty... I also think pine is not the real problem. > > > > > 4.) Pine works IF i only read and write mails (mail NFS mounted)! > > > > > > Next week i have a chance to upgrade to a newer version of 3.0, but i > >am asking me if it really stop pine from crashing. > > How are you upgrading ? make world/installing from zero ? If you were > making world you might want to try reinstalling from scratch... there > might have been some leftover pieces (?!?) from the previous version > (possibly 2.2.6 ?)... > Upgrade from 2.2 to 3.0 was a complete new installation (even changed from IDE to SCSI). Upgrading to a new 3.0 version should be a upgrade installation. regards, Gerald To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 06:58:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28462 for freebsd-current-outgoing; Wed, 29 Jul 1998 06:58:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28346 for ; Wed, 29 Jul 1998 06:58:08 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id IAA10970; Wed, 29 Jul 1998 08:57:35 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id IAA03319; Wed, 29 Jul 1998 08:57:35 -0500 (CDT) Message-ID: <19980729085735.28841@mcs.net> Date: Wed, 29 Jul 1998 08:57:35 -0500 From: Karl Denninger To: Karl Pielorz Cc: current@FreeBSD.ORG Subject: Re: Serious Dump problems References: <19980728073523.02311@mcs.net> <199807281519.RAA12042@pat.idi.ntnu.no> <19980728102807.42807@mcs.net> <35BEE26B.4DB6542@tdx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <35BEE26B.4DB6542@tdx.co.uk>; from Karl Pielorz on Wed, Jul 29, 1998 at 09:50:51AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 29, 1998 at 09:50:51AM +0100, Karl Pielorz wrote: > Karl Denninger wrote: > > > > On Tue, Jul 28, 1998 at 05:19:47PM +0200, Tor.Egge@fast.no wrote: > > > > Hi folks, > > > > > > > > I have an interesting one here... > > > > > > > > I have a dump tape which is intact, yet restore complains about "hole in > > > > map" and segv's when attempting to start up in interactive mode. > > > > > > Philip Inglesant gave a good description of this > > > problem on the -stable list. > > > > > > You probably had more than 4 million inodes on the file system. Thus > > > the bitmaps uses more than 512 KB(i.e. more than 512 tape blocks). > > This may be completely unconnected - but didn't someone mention a while ago - >similar problems when backing up a filesystem that isn't consistent (i.e. would > fail or need an fsck run on it)? > > Regards, > > Karl I EXPECT that to fail using Dump due to the way dump operates! :-) -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 07:11:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01826 for freebsd-current-outgoing; Wed, 29 Jul 1998 07:11:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01821 for ; Wed, 29 Jul 1998 07:11:29 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id KAA26624; Wed, 29 Jul 1998 10:12:12 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Wed, 29 Jul 1998 10:12:12 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: William Woods cc: current@FreeBSD.ORG Subject: Re: Upgrading from 2.2.7 to Current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://www.cs.sunyit.edu/~perlsta -> freebsd it's a _bit_ outdated, but should still be relevant. if anyone wants to review those pages... could i get some web space on www.freebsd.org? or perhaps just a link? thank you, -Alfred On Wed, 29 Jul 1998, William Woods wrote: > Is there a FAQ somewhere that deals with the steps nessary to upgrade from > 2.2.7-STABLE to -CURRENT? > > ---------------------------------- > William Woods > --> FreeBSD 2.2.7 <-- > Date: 29-Jul-98 > Time: 01:16:53 > ---------------------------------- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 07:25:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04335 for freebsd-current-outgoing; Wed, 29 Jul 1998 07:25:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04328 for ; Wed, 29 Jul 1998 07:25:06 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id QAA18434 ; Wed, 29 Jul 1998 16:22:46 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id QAA00130; Wed, 29 Jul 1998 16:22:44 +0200 To: Mike Cc: nik@iii.co.uk, wwoods@cybcon.com, current@FreeBSD.ORG Subject: Re: Upgrading from 2.2.7 to Current References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 29 Jul 1998 16:22:43 +0200 In-Reply-To: Mike's message of Wed, 29 Jul 1998 06:27:23 -0600 (MDT) Message-ID: Lines: 14 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike writes: > On Wed, 29 Jul 1998 nik@iii.co.uk wrote: > > On Wed, Jul 29, 1998 at 01:17:53AM -0700, William Woods wrote: > > # make -m /usr/src/sys/mk buildworld > I thought it was "make -m /usr/src/share/mk buildworld"? Indeedeedoo. BTW, I can confirm that this works perfectly in the other direction, too; I've upgraded my scratch box from 3.0-SNAP-980222 to 3.0-CURRENT and "downgraded" it back to 2.2.7-STABLE with absolutely no sign of trouble. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 09:14:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23856 for freebsd-current-outgoing; Wed, 29 Jul 1998 09:14:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23787 for ; Wed, 29 Jul 1998 09:14:41 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.HIP.Berkeley.EDU (sji-ca7-55.ix.netcom.com [209.109.235.55]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id JAA22744; Wed, 29 Jul 1998 09:13:44 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id JAA02200; Wed, 29 Jul 1998 09:13:39 -0700 (PDT) Date: Wed, 29 Jul 1998 09:13:39 -0700 (PDT) Message-Id: <199807291613.JAA02200@silvia.HIP.Berkeley.EDU> To: smoergrd@oslo.geco-prakla.slb.com CC: muck@ida.net, nik@iii.co.uk, wwoods@cybcon.com, current@FreeBSD.ORG In-reply-to: (smoergrd@oslo.geco-prakla.slb.com) Subject: Re: Upgrading from 2.2.7 to Current From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Indeedeedoo. BTW, I can confirm that this works perfectly in the other * direction, too; I've upgraded my scratch box from 3.0-SNAP-980222 to * 3.0-CURRENT and "downgraded" it back to 2.2.7-STABLE with absolutely * no sign of trouble. Be careful though. I don't remember if there are currently any shared library version differences between 2.2.7 and 3.0 (which of course will cause your newly build 2.2.7 libraries to be very effectively ignored), but some things in /usr/include that only exist in 3.0 will cause some ports to mistake your OS version and blow up. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 11:03:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16393 for freebsd-current-outgoing; Wed, 29 Jul 1998 11:03:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from att.com (kcgw1.att.com [192.128.133.151]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA16374 for ; Wed, 29 Jul 1998 11:03:42 -0700 (PDT) (envelope-from jwb@homer.att.com) Received: from kcig1.att.att.com by kcgw1.att.com (AT&T/UPAS) for freebsd.org!freebsd-current sender homer.att.com!jwb (homer.att.com!jwb); Wed Jul 29 13:03 CDT 1998 Received: from ulysses.homer.att.com (ulysses.homer.att.com [135.205.212.4]) by kcig1.att.att.com (AT&T/GW-1.0) with ESMTP id NAA22197 for ; Wed, 29 Jul 1998 13:02:56 -0500 (CDT) Received: from akiva.homer.att.com (akiva.homer.att.com [135.205.213.77]) by ulysses.homer.att.com (8.8.8/8.8.8) with SMTP id OAA02773 for ; Wed, 29 Jul 1998 14:02:54 -0400 (EDT) Received: by akiva.homer.att.com (4.1) id AA12382; Wed, 29 Jul 98 14:02:55 EDT Message-Id: <9807291802.AA12382@akiva.homer.att.com> Received: from localhost.homer.att.com [127.0.0.1] by akiva; Wed Jul 29 14:02:55 EDT 1998 X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: install with adaptec aic-78xx PCI Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 14:02:54 -0400 From: "J. W. Ballantine" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have an AT&T Globalyst 630 with a adaptec aic-78xx PCI that is running NT and had current on it. Due to several things, I had to reload FBSD. When I tried to load from the 3.0-YYMMDD-SNAP boot(980426 or 980520), it would not consisently install, in fact it generally locked up the SD0 drive at either prior to the install menu being displayed or when it when to update the SD0 label. Yet when I loaded from 2.2.6(or7)-RELEASE boot floppy I had no problem with it. Has the driver for the adaptec aic-78xx PCI SCSI controller changed to cause this problem or is it something else?? (At one point Doug White thought it might be memory problems, but it doesn't appear to be the problem.) Jim Ballantine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 11:11:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18495 for freebsd-current-outgoing; Wed, 29 Jul 1998 11:11:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from walker.reston.va.us (amanda@walker.reston.va.us [149.52.7.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18412 for ; Wed, 29 Jul 1998 11:11:20 -0700 (PDT) (envelope-from amanda@walker.reston.va.us) Received: (from amanda@localhost) by walker.reston.va.us (8.7.5/8.7.3) id NAA12067 for current@freebsd.org; Wed, 29 Jul 1998 13:11:22 -0400 Date: Wed, 29 Jul 1998 13:11:22 -0400 From: Amanda Walker Message-Id: <199807291711.NAA12067@walker.reston.va.us> To: current@FreeBSD.ORG Subject: Looking for PCMCIA stuff in 3.0... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm running 3.0-19980722-SNAP on several machines with excellent results so far, except for my laptop. Does anyone have a pointer to any of the following things: - a version of the if_sn.c (SMC 9xxx Ethernet) driver that runs in 3.0 - newer PCMCIA and/or CardBus support? I'll dive into at least updating Gardner Buchanan's sn driver myself this weekend (so that I can use my Megahertz CC10BT/2 Ethernet card) if no one else has looked at it, but I'd hate to reinvent the wheel (especially if the PAO folks are already working on 3.0--they've done a great job in 2.2). Thanks, Amanda Walker To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 12:08:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04615 for freebsd-current-outgoing; Wed, 29 Jul 1998 12:08:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04504 for ; Wed, 29 Jul 1998 12:07:57 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id UAA14174 for ; Wed, 29 Jul 1998 20:09:12 +0100 (BST) Date: Wed, 29 Jul 1998 20:09:12 +0100 (BST) From: Doug Rabson To: current@FreeBSD.ORG Subject: Proposed syscall changes for 64bit platforms Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want to make the following changes to syscall arguments to support 64bit platforms. The changes are just to convert some u_int arguments to size_t and should be cosmetic for i386. Does anyone have any objections/comments? Index: syscalls.master =================================================================== RCS file: /home/ncvs/src/sys/kern/syscalls.master,v retrieving revision 1.52 diff -u -r1.52 syscalls.master --- syscalls.master 1998/06/07 17:11:40 1.52 +++ syscalls.master 1998/07/20 12:36:40 @@ -37,8 +37,8 @@ 0 STD NOHIDE { int nosys(void); } syscall nosys_args int 1 STD NOHIDE { void exit(int rval); } exit rexit_args void 2 STD POSIX { int fork(void); } -3 STD POSIX { int read(int fd, char *buf, u_int nbyte); } -4 STD POSIX { int write(int fd, char *buf, u_int nbyte); } +3 STD POSIX { int read(int fd, char *buf, size_t nbyte); } +4 STD POSIX { int write(int fd, char *buf, size_t nbyte); } 5 STD POSIX { int open(char *path, int flags, int mode); } ; XXX should be { int open(const char *path, int flags, ...); } ; but we're not ready for `const' or varargs. @@ -88,8 +88,8 @@ 41 STD POSIX { int dup(u_int fd); } 42 STD POSIX { int pipe(void); } 43 STD POSIX { gid_t getegid(void); } -44 STD BSD { int profil(caddr_t samples, u_int size, \ - u_int offset, u_int scale); } +44 STD BSD { int profil(caddr_t samples, size_t size, \ + size_t offset, u_int scale); } 45 STD BSD { int ktrace(char *fname, int ops, int facs, \ int pid); } 46 STD POSIX { int sigaction(int signum, struct sigaction *nsa, \ @@ -114,7 +114,7 @@ 60 STD POSIX { int umask(int newmask); } umask umask_args int 61 STD BSD { int chroot(char *path); } 62 COMPAT POSIX { int fstat(int fd, struct ostat *sb); } -63 COMPAT BSD { int getkerninfo(int op, char *where, int *size, \ +63 COMPAT BSD { int getkerninfo(int op, char *where, size_t *size, \ int arg); } getkerninfo getkerninfo_args int 64 COMPAT BSD { int getpagesize(void); } \ getpagesize getpagesize_args int @@ -143,9 +143,9 @@ 84 COMPAT BSD { int wait(void); } 85 STD BSD { int swapon(char *name); } 86 STD BSD { int getitimer(u_int which, struct itimerval *itv); } -87 COMPAT BSD { int gethostname(char *hostname, u_int len); } \ +87 COMPAT BSD { int gethostname(char *hostname, size_t len); } \ gethostname gethostname_args int -88 COMPAT BSD { int sethostname(char *hostname, u_int len); } \ +88 COMPAT BSD { int sethostname(char *hostname, size_t len); } \ sethostname sethostname_args int 89 STD BSD { int getdtablesize(void); } 90 STD POSIX { int dup2(u_int from, u_int to); } -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 12:14:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06445 for freebsd-current-outgoing; Wed, 29 Jul 1998 12:14:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA06387 for ; Wed, 29 Jul 1998 12:13:52 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z1bf3-00031a-00; Wed, 29 Jul 1998 13:13:17 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id NAA10036; Wed, 29 Jul 1998 13:17:15 -0600 (MDT) Message-Id: <199807291917.NAA10036@harmony.village.org> To: wwoods@cybcon.com Subject: Re: Latest 3.0 -snap Cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 28 Jul 1998 21:48:57 PDT." References: Date: Wed, 29 Jul 1998 13:17:14 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message William Woods writes: : Whats with this....... : : /usr/src/Makefile" , Line 369: Malformed conditional ($(MACHINE_ARCH0 == "i386") It means that you are using the old sys.mk files to build the tree. If you have not already done so, please apply the following patch and see if that solves your problem w/o introducing new ones. make buildworld is what you'll want to do. I think this will return the new -current to a buildable state from 2.0.x forward, but have no systems to test that out on... Warner P.S. Yes, I know that there is some extra nits in this patch (white space differences and the like). I'll clean it up before hitting the tree with it. P.P.S. I've been building world past the point where things traditionally barf on a old system (but this build is on a new system). Index: Makefile =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/Makefile,v retrieving revision 1.205 diff -u -r1.205 Makefile --- Makefile 1998/07/07 09:59:48 1.205 +++ Makefile 1998/07/29 18:37:26 @@ -39,9 +39,11 @@ # obj depend all install clean cleandepend cleanobj .if (!make(world)) && (!make(buildworld)) && (!make(installworld)) -.MAKEFLAGS:= -m ${.CURDIR}/share/mk ${.MAKEFLAGS} +.MAKEFLAGS:= -m ${.CURDIR}/share/mk ${.MAKEFLAGS} .endif +MACHINE_ARC?=${MACHINE} + # Put initial settings here. SUBDIR= @@ -220,7 +222,7 @@ MAKETMP= ${WORLDTMP}/make IBMAKE= ${BMAKEENV} MAKEOBJDIR=${MAKETMP} ${MAKE} DESTDIR=${WORLDTMP} # bootstrap make -BMAKE= ${BMAKEENV} ${WORLDTMP}/usr/bin/make DESTDIR=${WORLDTMP} +BMAKE= ${BMAKEENV} ${WORLDTMP}/usr/bin/make -m ${.CURDIR}/share/mk DESTDIR=${WORLDTMP} # cross make used for compilation XMAKE= ${XMAKEENV} ${WORLDTMP}/usr/bin/make DESTDIR=${WORLDTMP} # cross make used for final installation To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 12:17:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07542 for freebsd-current-outgoing; Wed, 29 Jul 1998 12:17:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA07529 for ; Wed, 29 Jul 1998 12:17:29 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z1bia-00031j-00; Wed, 29 Jul 1998 13:16:56 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id NAA12977; Wed, 29 Jul 1998 13:20:47 -0600 (MDT) Message-Id: <199807291920.NAA12977@harmony.village.org> To: nik@iii.co.uk Subject: Re: Upgrading from 2.2.7 to Current Cc: wwoods@cybcon.com, current@FreeBSD.ORG In-reply-to: Your message of "Wed, 29 Jul 1998 09:48:49 BST." <19980729094849.A9484@iii.co.uk> References: <19980729094849.A9484@iii.co.uk> Date: Wed, 29 Jul 1998 13:20:46 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980729094849.A9484@iii.co.uk> nik@iii.co.uk writes: : # make buildworld This should be all that is needed, the -m xxxx stuff is a workaround for a bug in Makefile. If there are people out there with 2.2.x or 2.1.x systems that have -current trees laying around, can you please take a look at the patch that I've attached to this message and see if it restores the ability to go from 2.x -> -current? I think, but am not sure, that the XMAKE variable doesn't need to be tweaked. I could be wrong, however. Thanks Much Warner Index: Makefile =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/Makefile,v retrieving revision 1.205 diff -u -r1.205 Makefile --- Makefile 1998/07/07 09:59:48 1.205 +++ Makefile 1998/07/29 18:37:26 @@ -39,9 +39,11 @@ # obj depend all install clean cleandepend cleanobj .if (!make(world)) && (!make(buildworld)) && (!make(installworld)) -.MAKEFLAGS:= -m ${.CURDIR}/share/mk ${.MAKEFLAGS} +.MAKEFLAGS:= -m ${.CURDIR}/share/mk ${.MAKEFLAGS} .endif +MACHINE_ARC?=${MACHINE} + # Put initial settings here. SUBDIR= @@ -220,7 +222,7 @@ MAKETMP= ${WORLDTMP}/make IBMAKE= ${BMAKEENV} MAKEOBJDIR=${MAKETMP} ${MAKE} DESTDIR=${WORLDTMP} # bootstrap make -BMAKE= ${BMAKEENV} ${WORLDTMP}/usr/bin/make DESTDIR=${WORLDTMP} +BMAKE= ${BMAKEENV} ${WORLDTMP}/usr/bin/make -m ${.CURDIR}/share/mk DESTDIR=${WORLDTMP} # cross make used for compilation XMAKE= ${XMAKEENV} ${WORLDTMP}/usr/bin/make DESTDIR=${WORLDTMP} # cross make used for final installation To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 12:18:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07736 for freebsd-current-outgoing; Wed, 29 Jul 1998 12:18:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA07660 for ; Wed, 29 Jul 1998 12:17:58 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z1bj3-00031l-00; Wed, 29 Jul 1998 13:17:25 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id NAA13343; Wed, 29 Jul 1998 13:21:24 -0600 (MDT) Message-Id: <199807291921.NAA13343@harmony.village.org> To: Mike Subject: Re: Upgrading from 2.2.7 to Current Cc: nik@iii.co.uk, wwoods@cybcon.com, current@FreeBSD.ORG In-reply-to: Your message of "Wed, 29 Jul 1998 06:27:23 MDT." References: Date: Wed, 29 Jul 1998 13:21:23 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Mike writes: : I thought it was "make -m /usr/src/share/mk buildworld"? It is. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 12:43:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12688 for freebsd-current-outgoing; Wed, 29 Jul 1998 12:43:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12678 for ; Wed, 29 Jul 1998 12:43:39 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id UAA04429; Wed, 29 Jul 1998 20:42:20 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807291942.UAA04429@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Thyer cc: Brian Somers , Matthew Thyer , Kris Kennaway , FreeBSD CURRENT Subject: Re: ppp driving me nuts In-reply-to: Your message of "Wed, 29 Jul 1998 21:24:33 +0930." <35BF0D79.8D8194E@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 20:42:19 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The default redial period is 30 seconds. Ppp will not reopen the modem until this time has elapsed. I've made some modifications so that you can now ``open!'' or ``dial!'' to ignore the redial timer. > I dont know what you mean by my use of "set redial". > > Here's my ppp.conf: > > > > default: > set log chat connect phase > set device /dev/cuaa1 > set speed 115200 > deny lqr > deny pap > set timeout 0 > set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT OK-AT-OK ATE1Q0L0 OK \\dATDT\\T TIMEOUT 120 CONNECT" > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 > > target: > set phone > set login > set authname > set authkey > dial > > Brian Somers wrote: > > > > Hmm, > > > > I guess the ``dial'' command should nuke the redial timer if it > > exists. This is a bug. The redial timer is used by the datalink > > state machine to honour your ``set redial''. > > > > I'll fix it. > > > > > I use usermode ppp as "ppp target" where my target does the > > > dial (after setting authkey etc). > > > > > > If the first dial fails (say due to the number being busy) typing > > > 'dial' at the 'ppp' prompt makes ppp do nothing until the original > > > dial timeout has elapsed (at least that's how it appears to me). > > > > > > So rather than waiting 40 seconds or so (my dial timeout is 120 sec) > > > I quit ppp and just type "ppp target" again. > > > > > > This is nothing to do with redial timeouts I think its the original > > > dial timeout that is still ticking away for some reason even though > > > ppp has already told me that the first dial has failed. > > > > > > > > > Kris Kennaway wrote: > > > > > > > > On Tue, 28 Jul 1998, Snob Art Genre wrote: > > > > > > > > > On Tue, 28 Jul 1998, Kris Kennaway wrote: > > > > > > > > > > > I seem to recall that theres a 3 minute idle timeout which cannot be > > > > > > overridden if you start the ppp session from interactive mode. I often > > > > > > > > > > Why wouldn't "set timeout 0" override? I load my provider profile with > > > > > a "load" directive in the conf file, and just log in as ppp with ppp as > > > > > my shell and type "dial", btw. And a "show timers" doesn't show any > > > > > idle timer running. > > > > > > > > I just know that doing that never seemed to prevent the session from > > > > timing out after 3 minutes. I was going to get around to > > > > investigating this further & submitting a formal report, but it seems to > > > > have come up anyway :) > > > > > > > > I also seem to remember something about the redial timeout not quite > > > > working as it is documented in the manpages.. > > > > > > > > Kris > > -- > /=====================================================================\ > |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| > \=====================================================================/ > "If it is true that our Universe has a zero net value for all conserved > quantities, then it may simply be a fluctuation of the vacuum of some > larger space in which our Universe is imbedded. In answer to the > question of why it happened, I offer the modest proposal that our > Universe is simply one of those things which happen from time to time." > E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 > -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 13:18:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18241 for freebsd-current-outgoing; Wed, 29 Jul 1998 13:18:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18231 for ; Wed, 29 Jul 1998 13:18:18 -0700 (PDT) (envelope-from bartol@salk.edu) Received: from cole.salk.edu (cole [198.202.70.113]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id NAA19967 for ; Wed, 29 Jul 1998 13:17:15 -0700 (PDT) Date: Wed, 29 Jul 1998 13:17:12 -0700 (PDT) From: Tom Bartol To: current@FreeBSD.ORG Subject: make world failure in -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Just got this failure in a make world of -current cvsupped moments ago. I'm making on a 3.0-19980711-SNAP system with SMP enabled. I take it that no one else is seeing this problem so there must be something wrong on my end but I can't figure out what it is. Anyone have any tips on what I should to to fix it? Thanks, Tom ===> strip cc -O2 -m486 -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/strip I/usr/src/gnu/usr.bin/binutils/strip/../libbfd/i386 -I/usr/src/gnu/usr.bin/bin ils/strip/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils trip/../libbinutils -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/ nutils/binutils -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/b utils/strip/../../../../contrib/binutils/binutils/objcopy.c cc -O2 -m486 -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/strip I/usr/src/gnu/usr.bin/binutils/strip/../libbfd/i386 -I/usr/src/gnu/usr.bin/bin ils/strip/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils trip/../libbinutils -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/ nutils/binutils -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/b utils/strip/../../../../contrib/binutils/binutils/is-strip.c cc -O2 -m486 -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/strip I/usr/src/gnu/usr.bin/binutils/strip/../libbfd/i386 -I/usr/src/gnu/usr.bin/bin ils/strip/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils trip/../libbinutils -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/ nutils/binutils -I/usr/obj/usr/src/tmp/usr/include -static -o strip objcopy is-strip.o -L../libbinutils -lbinutils -L../libbfd -lbfd -L../libiberty -lib ty cp strip maybe_stripped strip maybe_stripped strip: maybe_stripped: File format not recognized *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 14:47:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07879 for freebsd-current-outgoing; Wed, 29 Jul 1998 14:47:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07869 for ; Wed, 29 Jul 1998 14:47:27 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id OAA04943; Wed, 29 Jul 1998 14:45:51 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 29 Jul 1998 14:45:51 -0700 (PDT) From: Doug White To: Dermot McNally cc: freebsd-current@FreeBSD.ORG Subject: Re: Problems with ed driver (PCI) In-Reply-To: <35c03c26.2700750@mail.compuserve.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Jul 1998, Dermot McNally wrote: > The card is actually sold under the name "Micronet" although it is > recognised as a Realtek chipset. Its little green light goes on, indicating > that it sees the network OK and the corresponding little green light on the > hub comes on too. Windows reports all PCI NE2000s as RealTeks. Can you see what chip is on it? > There is one unusual, and possibly significant issue here - I also have a > 3Com network card (calls itself an Etherlink XL, uses the vx driver). If I > fit this card, and there's a driver for it in the kernel, the machine hangs > after finding the card. The same kernel on a different machine will boot no > problem with this card. I haven't yet tried the other machine with the > NE2000 - it's a 100% NT machine anyway, so it won't help me much, but it's > a useful test. That machine normally runs correctly with the 3Com card. > Very strange. What model 3com? A new driver for the 3com PCI cards was released the other day, you can try it at http://www.freebsd.org/~wpaul/3Com/. > The spec of the machine that's causing this trouble is now as follows: > > Intel LX chipset, a PII 300MHz, made by Gateway 2000 > NE2000 PCI network card (Realtek via Micronet) > Adaptec UW 2900 SCSI contoller (card, not on board) > One US SCSI HD, 1 SCSI CDROM drive > STP AGP graphics card (Riva 128 chipset) > > That's the lot - I pulled the sound card in case it was a factor. The > problem occurs with kernels from the 5/24/98 snap as well as from (I think) > a 20/7/98 snap I found on ftp.de.freebsd.org but which doesn't seem to be > on the main site. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 16:46:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03651 for freebsd-current-outgoing; Wed, 29 Jul 1998 16:46:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (garbanzo@libya-193.ppp.hooked.net [206.169.227.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03606 for ; Wed, 29 Jul 1998 16:46:33 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with SMTP id QAA01051 for ; Wed, 29 Jul 1998 16:47:19 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Wed, 29 Jul 1998 16:47:18 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: current Subject: listen() and SOMAXCONN? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Welp, the subject of where to get the value for the maximum number of sockets listen() can handle safely. On most other systems SOMAXCONN is defined in sys/socket.h. A quick check of the man page informs me that I should use the MIB kern.somaxconn. Well, I checked the header files, and SOMAXCONN is defined to 128 in sys/socket.h, and there is no kern.somaxconn MIB. Any thoughts? - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 20:43:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21409 for freebsd-current-outgoing; Wed, 29 Jul 1998 20:43:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21403 for ; Wed, 29 Jul 1998 20:43:52 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA16293; Wed, 29 Jul 1998 20:35:39 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdx16288; Thu Jul 30 03:35:30 1998 Date: Wed, 29 Jul 1998 20:35:27 -0700 (PDT) From: Julian Elischer To: Garrett Wollman cc: current@FreeBSD.ORG Subject: Re: SMP kernels... how many processes can be in ? In-Reply-To: <199807281441.KAA19062@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is effectlively what Luigi did with his 'flow pointer' however it probably should be an extensible scheme so that new 'hacks' can be added to the system and make use of it. the trouble with just using a pointer to something is that the something needs to be freed some time. and it may need to be allocated at unknown spl etc. Luigi found that there were a lot of places tha had to be hackedto know about the new pointer. julian On Tue, 28 Jul 1998, Garrett Wollman wrote: > < said: > > > trouble is that there needs to be some place to store data > > on a 'packet by packet' basis, The data is generated at one point in > > processing and needed at another.. > > Stick it in the (mbuf) packet header. If it's too big, stick a > pointer to it in the packet header. > > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > wollman@lcs.mit.edu | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 22:00:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA00156 for freebsd-current-outgoing; Wed, 29 Jul 1998 22:00:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.lbfe.org.tw ([210.63.26.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00148 for ; Wed, 29 Jul 1998 22:00:06 -0700 (PDT) (envelope-from jonahk@mail.lbfe.org.tw) Received: from mail.lbfe.org.tw ([210.63.26.198]) by mail.lbfe.org.tw (Netscape Messaging Server 3.01) with ESMTP id AAA51ED for ; Thu, 30 Jul 1998 12:37:30 +0800 Message-ID: <35BFF3F5.AC77BC4@mail.lbfe.org.tw> Date: Thu, 30 Jul 1998 12:17:57 +0800 From: Jonah Kuo X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: buildworld failures on same problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello there, I cvsuped 3.0-current and did several time make buildworld, but all failed on same problem: -------------------------------------------------------------- Rebuilding tools needed to build libraries -------------------------------------------------------------- cd /usr/src; PATH=/usr/obj/usr/src/tmp/sbin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/local/bin:/usr/bin:/usr/games:/usr/local/sbin:/usr/X11R6/bin:/home/jonah/bin:/usr/local/pgsql/bin BISON_SIMPLE=/usr/obj/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib NOEXTRADEPEND=t OBJFORMAT_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/libexec /usr/obj/usr/src/tmp/usr/bin/make DESTDIR=/usr/obj/usr/src/tmp lib-tools cd /usr/src/gnu/usr.bin/gperf; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPROFILE -DNOSHARED -B cleandir obj rm -f .depend /usr/obj/usr/src/gnu/usr.bin/gperf/GRTAGS /usr/obj/usr/src/gnu/usr.bin/gperf/GSYMS /usr/obj/usr/src/gnu/usr.bin/gperf/GTAGS ===> doc cc -O2 -m486 -pipe -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/options.c cc -O2 -m486 -pipe -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/iterator.c cc -O2 -m486 -pipe -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/main.c cc -O2 -m486 -pipe -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/perfect.c cc -O2 -m486 -pipe -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/keylist.c cc -O2 -m486 -pipe -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/listnode.c cc -O2 -m486 -pipe -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/xmalloc.c cc -O2 -m486 -pipe -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/hashtable.c cc -O2 -m486 -pipe -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/boolarray.c cc -O2 -m486 -pipe -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/readline.c cc -O2 -m486 -pipe -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/stderr.c cc -O2 -m486 -pipe -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/version.c cc -O2 -m486 -pipe -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/getopt.c cc -O2 -m486 -pipe -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS -I/usr/obj/usr/src/tmp/usr/include -static -o gperf options.o iterator.o main.o perfect.o keylist.o listnode.o xmalloc.o hashtable.o boolarray.o readline.o stderr.o version.o getopt.o stderr.o: Undefined symbol `___error' referenced from text segment stderr.o: Undefined symbol `___error' referenced from text segment stderr.o: Undefined symbol `___error' referenced from text segment *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Any help? Jonah Kuo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 29 22:19:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02792 for freebsd-current-outgoing; Wed, 29 Jul 1998 22:19:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chen.ml.org (luoqi.watermarkgroup.com [207.202.73.170]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02783 for ; Wed, 29 Jul 1998 22:19:50 -0700 (PDT) (envelope-from luoqi@chen.ml.org) Received: (from luoqi@localhost) by chen.ml.org (8.8.8/8.8.8) id BAA03131 for current@freebsd.org; Thu, 30 Jul 1998 01:19:38 -0400 (EDT) (envelope-from luoqi) Date: Thu, 30 Jul 1998 01:19:38 -0400 (EDT) From: Luoqi Chen Message-Id: <199807300519.BAA03131@chen.ml.org> To: current@FreeBSD.ORG Subject: using vm_page.h in userland program Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Recent change (addition of cache coloring) to vm/vm_page.h has made it impossible to use this header file in a userland program. It tries to include "opt_vmpage.h" unconditionally. IMO, "opt_vmpage.h" should only be included when KERNEL is defined. Would someone please make the change? Thanks -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 30 00:02:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17019 for freebsd-current-outgoing; Thu, 30 Jul 1998 00:02:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles237.castles.com [208.214.165.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16986 for ; Thu, 30 Jul 1998 00:02:40 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00317; Wed, 29 Jul 1998 23:05:23 -0700 (PDT) Message-Id: <199807300605.XAA00317@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Julian Elischer cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: SMP kernels... how many processes can be in ? In-reply-to: Your message of "Wed, 29 Jul 1998 20:35:27 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 23:05:22 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is effectlively what Luigi did with his 'flow pointer' > however it probably should be an extensible scheme > so that new 'hacks' can be added to the system and make use of it. > the trouble with just using a pointer to something is that the something > needs to be freed some time. and it may need to be allocated at unknown > spl etc. > > Luigi found that there were a lot of places tha had to be hackedto know > about the new pointer. Don't point to it from the mbuf, put it in the mbuf. Use a cluster if you like. Call it "in-band signalling". 8) > julian > > > > On Tue, 28 Jul 1998, Garrett Wollman wrote: > > > < said: > > > > > trouble is that there needs to be some place to store data > > > on a 'packet by packet' basis, The data is generated at one point in > > > processing and needed at another.. > > > > Stick it in the (mbuf) packet header. If it's too big, stick a > > pointer to it in the packet header. > > > > -GAWollman > > > > -- > > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > > wollman@lcs.mit.edu | O Siem / The fires of freedom > > Opinions not those of| Dance in the burning flame > > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 30 00:41:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22007 for freebsd-current-outgoing; Thu, 30 Jul 1998 00:41:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21998; Thu, 30 Jul 1998 00:41:27 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id JAA10656 ; Thu, 30 Jul 1998 09:40:07 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id JAA00737; Thu, 30 Jul 1998 09:40:05 +0200 To: asami@FreeBSD.ORG (Satoshi Asami) Cc: muck@ida.net, nik@iii.co.uk, wwoods@cybcon.com, current@FreeBSD.ORG Subject: Re: Upgrading from 2.2.7 to Current References: <199807291613.JAA02200@silvia.HIP.Berkeley.EDU> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 30 Jul 1998 09:40:03 +0200 In-Reply-To: asami@freebsd.org's message of Wed, 29 Jul 1998 09:13:39 -0700 (PDT) Message-ID: Lines: 41 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG asami@freebsd.org (Satoshi Asami) writes: > * Indeedeedoo. BTW, I can confirm that this works perfectly in the other > * direction, too; I've upgraded my scratch box from 3.0-SNAP-980222 to > * 3.0-CURRENT and "downgraded" it back to 2.2.7-STABLE with absolutely > * no sign of trouble. > Be careful though. I don't remember if there are currently any shared > library version differences between 2.2.7 and 3.0 (which of course > will cause your newly build 2.2.7 libraries to be very effectively > ignored), but some things in /usr/include that only exist in 3.0 will > cause some ports to mistake your OS version and blow up. Don't worry, I thought of that :) Considering that I built 2.2.7 twelve days after my last 3.0 build: for dir in / /var /usr ; do find $dir -xdev -mtime 12 -print | xargs rm -rf done and a second make installworld just to be sure I hadn't removed anything useful. Libraries were slightly hairier than that because there were links in /usr/lib/compat that had to be removed, but nothing too challenging. And of course, I rebuilt all my ports - which wasn't much (bash2, less, lynx, ncftp2) since this is a scratch box. /etc is a whole other story. From memory: # cd / # pax -rwpe etc /var/tmp # rm -rf etc # mkdir etc etc/kerberos etc/ppp etc/mtree (and possibly a few others) # cd /var/tmp/etc # cp *passwd *pwd* group /etc # cd /usr/src/etc # make distribution DESTDIR=/ # newaliases # cd /var/tmp/etc # cp *passwd *pwd* group hosts host.conf resolv.conf rc.conf.local fstab /etc DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 30 00:42:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22218 for freebsd-current-outgoing; Thu, 30 Jul 1998 00:42:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22199 for ; Thu, 30 Jul 1998 00:42:04 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA02646; Thu, 30 Jul 1998 17:42:00 +1000 Date: Thu, 30 Jul 1998 17:42:00 +1000 From: Bruce Evans Message-Id: <199807300742.RAA02646@godzilla.zeta.org.au> To: current@FreeBSD.ORG, dfr@nlsystems.com Subject: Re: Proposed syscall changes for 64bit platforms Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >-3 STD POSIX { int read(int fd, char *buf, u_int nbyte); } >-4 STD POSIX { int write(int fd, char *buf, u_int nbyte); } >+3 STD POSIX { int read(int fd, char *buf, size_t nbyte); } >+4 STD POSIX { int write(int fd, char *buf, size_t nbyte); } See if you can change these to `ssize_t ... void *buf ...' so that they actually match their application interface. Changing the return type seems to be hard - it seems to require changing all syscalls to return (signed) register_t. >-63 COMPAT BSD { int getkerninfo(int op, char *where, int *size, \ >+63 COMPAT BSD { int getkerninfo(int op, char *where, size_t *size, \ > int arg); } getkerninfo getkerninfo_args int Probably shouldn't be supported on new arches. >-87 COMPAT BSD { int gethostname(char *hostname, u_int len); } \ >+87 COMPAT BSD { int gethostname(char *hostname, size_t len); } \ > gethostname gethostname_args int >-88 COMPAT BSD { int sethostname(char *hostname, u_int len); } \ >+88 COMPAT BSD { int sethostname(char *hostname, size_t len); } \ > sethostname sethostname_args int Certainly shouldn't be supported on new arches (were superseded by sysctls). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 30 01:04:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25924 for freebsd-current-outgoing; Thu, 30 Jul 1998 01:04:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25914 for ; Thu, 30 Jul 1998 01:04:17 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id JAA23548; Thu, 30 Jul 1998 09:04:19 +0100 (BST) Date: Thu, 30 Jul 1998 09:04:19 +0100 (BST) From: Doug Rabson To: Bruce Evans cc: current@FreeBSD.ORG Subject: Re: Proposed syscall changes for 64bit platforms In-Reply-To: <199807300742.RAA02646@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Jul 1998, Bruce Evans wrote: > >-3 STD POSIX { int read(int fd, char *buf, u_int nbyte); } > >-4 STD POSIX { int write(int fd, char *buf, u_int nbyte); } > >+3 STD POSIX { int read(int fd, char *buf, size_t nbyte); } > >+4 STD POSIX { int write(int fd, char *buf, size_t nbyte); } > > See if you can change these to `ssize_t ... void *buf ...' so that they > actually match their application interface. Changing the return type > seems to be hard - it seems to require changing all syscalls to return > (signed) register_t. I'll try. The return type shouldn't be a problem due to the way that return values are handled for syscalls. > > >-63 COMPAT BSD { int getkerninfo(int op, char *where, int *size, \ > >+63 COMPAT BSD { int getkerninfo(int op, char *where, size_t *size, \ > > int arg); } getkerninfo getkerninfo_args int > > Probably shouldn't be supported on new arches. Ok. > > >-87 COMPAT BSD { int gethostname(char *hostname, u_int len); } \ > >+87 COMPAT BSD { int gethostname(char *hostname, size_t len); } \ > > gethostname gethostname_args int > >-88 COMPAT BSD { int sethostname(char *hostname, u_int len); } \ > >+88 COMPAT BSD { int sethostname(char *hostname, size_t len); } \ > > sethostname sethostname_args int > > Certainly shouldn't be supported on new arches (were superseded by sysctls). These last two ones don't matter practically. I will backout that part. Actually the only one which really needed to change was sysctl since that passes a pointer to a length variable. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 30 01:33:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00467 for freebsd-current-outgoing; Thu, 30 Jul 1998 01:33:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00458 for ; Thu, 30 Jul 1998 01:33:50 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA05989; Thu, 30 Jul 1998 18:33:38 +1000 Date: Thu, 30 Jul 1998 18:33:38 +1000 From: Bruce Evans Message-Id: <199807300833.SAA05989@godzilla.zeta.org.au> To: current@FreeBSD.ORG, luoqi@chen.ml.org Subject: Re: using vm_page.h in userland program Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Recent change (addition of cache coloring) to vm/vm_page.h has made it >impossible to use this header file in a userland program. It tries to >include "opt_vmpage.h" unconditionally. IMO, "opt_vmpage.h" should only >be included when KERNEL is defined. Would someone please make the change? Cache coloring isn't recent, but new-style options for it are recent. The options should not have been made new-style, since including options headers in other headers doesn't work well. Of course, old-style options in headers don't work well either - there is no way to tell if the ifdefed options in the header were actually used. I looked at moving the options to vm_page.c. IIRC, the only problem was that a couple of extern arrays have size depending on the options. Perhaps these arrays can be declared without a size. The cache coloring options should be dynamic anyway. I have tried a few different values on various machines but didn't notice much difference and didn't have time to do careful comparisons. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 30 04:07:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19661 for freebsd-current-outgoing; Thu, 30 Jul 1998 04:07:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19656 for ; Thu, 30 Jul 1998 04:07:40 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id NAA21147 ; Thu, 30 Jul 1998 13:07:36 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id NAA01125; Thu, 30 Jul 1998 13:07:35 +0200 To: Jonah Kuo Cc: current@FreeBSD.ORG Subject: Re: buildworld failures on same problem References: <35BFF3F5.AC77BC4@mail.lbfe.org.tw> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 30 Jul 1998 13:07:34 +0200 In-Reply-To: Jonah Kuo's message of Thu, 30 Jul 1998 12:17:57 +0800 Message-ID: Lines: 15 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonah Kuo writes: > I cvsuped 3.0-current and did several time make buildworld, > but all failed on same problem: *sigh* When will people learn to read the bloody FAQ and search the bloody archives before asking the same bloody question as umpteen zillion others before them? # cd /usr/src ; make -m /usr/src/share/mk world DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 30 04:27:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA22240 for freebsd-current-outgoing; Thu, 30 Jul 1998 04:27:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA22218 for ; Thu, 30 Jul 1998 04:27:49 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.8/8.7.3) id NAA08944 for freebsd-current@freebsd.org; Thu, 30 Jul 1998 13:27:41 +0200 (CEST) From: Holm Tiffe Message-Id: <199807301127.NAA08944@magnet.geophysik.tu-freiberg.de> Subject: No More CTM Deltas on ftp.freebsd.org ? To: freebsd-current@FreeBSD.ORG Date: Thu, 30 Jul 1998 13:27:41 +0200 (CEST) Reply-To: freebsd@magnet.geophysik.tu-freiberg.de X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, The Subject say it all. We have no actual cvs-cur deltas on ftp://ftp.freebsd.org/pub/CTM/cvs-cur , the last delta is from Jul,8 1998. Why ? -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 30 04:39:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23858 for freebsd-current-outgoing; Thu, 30 Jul 1998 04:39:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA23852 for ; Thu, 30 Jul 1998 04:39:34 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id MAA01094 for ; Thu, 30 Jul 1998 12:39:40 +0100 (BST) Message-ID: <35C05B72.45BE3601@tdx.co.uk> Date: Thu, 30 Jul 1998 12:39:30 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.5b1 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Newly made world - and kern_securelevel Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've just rebuilt the world on my system as of 30/7/98, 12pm(BST) - all went well (as it fortunately usually does!). The system now raises the kernel's security level at the end of rc - This caught me out at one point while trying to install a new kernel in a multi-user system (chflags failed)... Is there anywhere I can get more info about the security levels etc. - and what they effect? (something not too technical would be nice) - I track -current, though I don't remember seeing it being discussed much... Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 30 04:55:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26509 for freebsd-current-outgoing; Thu, 30 Jul 1998 04:55:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA26484 for ; Thu, 30 Jul 1998 04:54:59 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z1rI6-0003Rb-00; Thu, 30 Jul 1998 05:54:38 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id FAA07585; Thu, 30 Jul 1998 05:58:45 -0600 (MDT) Message-Id: <199807301158.FAA07585@harmony.village.org> To: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Sm rgrav) Subject: Re: buildworld failures on same problem Cc: Jonah Kuo , current@FreeBSD.ORG In-reply-to: Your message of "30 Jul 1998 13:07:34 +0200." References: <35BFF3F5.AC77BC4@mail.lbfe.org.tw> Date: Thu, 30 Jul 1998 05:58:45 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Dag-Erling Coidan Sm rgrav writes: : When will people learn to read the bloody FAQ and search the bloody : archives before asking the same bloody question as umpteen zillion : others before them? : : # cd /usr/src ; make -m /usr/src/share/mk world Unless someone objects, I'll commit the changes that I believe obviates the need for -m /usr/src/share/mk that I posted yesterday. There is no need to require those args... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 30 12:15:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28251 for freebsd-current-outgoing; Thu, 30 Jul 1998 12:15:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28118 for ; Thu, 30 Jul 1998 12:15:21 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id VAA20413; Thu, 30 Jul 1998 21:01:48 +0200 (SAT) From: John Hay Message-Id: <199807301901.VAA20413@zibbi.mikom.csir.co.za> Subject: Re: Digiboard SYNC/570i PCI In-Reply-To: <35BE0439.DDB768AB@pipeline.ch> from IBS / Andre Oppermann at "Jul 28, 98 07:02:49 pm" To: andre@pipeline.ch (IBS / Andre Oppermann) Date: Thu, 30 Jul 1998 21:01:48 +0200 (SAT) Cc: krassi@bulinfo.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Krassimir Slavchev wrote: > > > > Thanks for the answer, > > > > but I don't know how to confiigure it, because it's a PCI card. > > in LINT there's an example for ISA card. > > Can you send me an example line for the kernel configuration for a PCI > > bus. > > No idea, we have only ISA cards. Maybe John Hay, the author of the > driver > has some thoughts on it? > Sorry to only get back to you now, but this week has been a very busy and I'm only know starting to work through my email. There isn't support for the PCI version yet, but I did get hold of a card and as soon as I have time I will look at it. It does look similar to the ISA card so I expect that it won't be too much work. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 30 13:08:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12412 for freebsd-current-outgoing; Thu, 30 Jul 1998 13:08:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12399 for ; Thu, 30 Jul 1998 13:08:06 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id WAA22110 for freebsd-current@FreeBSD.ORG; Thu, 30 Jul 1998 22:08:01 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 1426D3CEC; Thu, 30 Jul 1998 21:59:55 +0200 (CEST) Message-ID: <19980730215955.A10932@keltia.freenix.fr> Date: Thu, 30 Jul 1998 21:59:55 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: No More CTM Deltas on ftp.freebsd.org ? Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199807301127.NAA08944@magnet.geophysik.tu-freiberg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199807301127.NAA08944@magnet.geophysik.tu-freiberg.de>; from Holm Tiffe on Thu, Jul 30, 1998 at 01:27:41PM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4503 AMD-K6 MMX @ 233 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Holm Tiffe: > We have no actual cvs-cur deltas on ftp://ftp.freebsd.org/pub/CTM/cvs-cur , > the last delta is from Jul,8 1998. I don't know why but I know I always go to the following site to get missings deltas: -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #62: Mon Jul 27 20:47:08 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 30 21:29:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27707 for freebsd-current-outgoing; Thu, 30 Jul 1998 21:29:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27702 for ; Thu, 30 Jul 1998 21:29:11 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id VAA01919; Thu, 30 Jul 1998 21:29:04 -0700 (PDT) (envelope-from jdp) Message-Id: <199807310429.VAA01919@austin.polstra.com> To: chuckr@glue.umd.edu Subject: Re: /usr/lib/aout In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 30 Jul 1998 21:29:04 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Chuck Robey wrote: > That approach would undoubtedly work, but when things move over to elf, > I hope important stuff like ssh doesn't do straight down the tubes. I > can't figure out why it wants /usr/lib/libc, but I can sure verify that > it does. I've never seen this. I just now built the ssh port on a -current system from July 24, without any problems at all. There is nothing in /usr/lib except the "aout" and "compat" subdirectories. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 30 21:49:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29682 for freebsd-current-outgoing; Thu, 30 Jul 1998 21:49:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29673 for ; Thu, 30 Jul 1998 21:49:08 -0700 (PDT) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.8.8/8.8.7) id AAA15722 for current@freebsd.org; Fri, 31 Jul 1998 00:49:00 -0400 (EDT) (envelope-from lee) Message-ID: <19980731004859.A15715@st-lcremean.tidalwave.net> Date: Fri, 31 Jul 1998 00:48:59 -0400 From: Lee Cremeans To: current@FreeBSD.ORG Subject: Identd problems on -current of 980724 Reply-To: lcremean@tidalwave.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running -cuurent CVSup'd the night of 7/24, with the user-ppp it came with, and I've noticed that my identd has stopped working for remote hosts. What is causing this? PS: Predictor-1 was broken in that snap; I was noticing strage connection hangs to some sites. They went away when I disabled it. -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 30 22:04:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01277 for freebsd-current-outgoing; Thu, 30 Jul 1998 22:04:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01272 for ; Thu, 30 Jul 1998 22:04:22 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: from aura.rice.edu (aura.rice.edu [192.136.146.26]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id AAA24159; Fri, 31 Jul 1998 00:04:16 -0500 (CDT) Received: from aura.rice.edu (localhost [127.0.0.1]) by aura.rice.edu (8.8.8/8.7.3) with ESMTP id AAA01896; Fri, 31 Jul 1998 00:04:16 -0500 (CDT) Message-Id: <199807310504.AAA01896@aura.rice.edu> To: bde@zeta.org.au cc: current@FreeBSD.ORG Subject: Re: using vm_page.h in userland program Date: Fri, 31 Jul 1998 00:04:15 -0500 From: Alan Cox Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -------- > The cache coloring options should be dynamic anyway. I have tried a few > different values on various machines but didn't notice much difference > and didn't have time to do careful comparisons. Its main effect is to reduce the variation in execution time between one run and another because all of the runs will experience (almost) the same set of conflict misses. To actually see the effects, try running the lmbench memory read latency test. With appropriate page coloring, you get a nice step function as you fall out of L1 cache into L2 cache and then main memory. Without the correct page coloring you get spikes where there shouldn't be. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 30 22:27:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03685 for freebsd-current-outgoing; Thu, 30 Jul 1998 22:27:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03674 for ; Thu, 30 Jul 1998 22:26:56 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id AAA26521; Fri, 31 Jul 1998 00:26:28 -0500 (EST) (envelope-from toor) Message-Id: <199807310526.AAA26521@dyson.iquest.net> Subject: Re: using vm_page.h in userland program In-Reply-To: <199807300833.SAA05989@godzilla.zeta.org.au> from Bruce Evans at "Jul 30, 98 06:33:38 pm" To: bde@zeta.org.au (Bruce Evans) Date: Fri, 31 Jul 1998 00:26:28 -0500 (EST) Cc: current@FreeBSD.ORG, luoqi@chen.ml.org From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans said: > >Recent change (addition of cache coloring) to vm/vm_page.h has made it > >impossible to use this header file in a userland program. It tries to > >include "opt_vmpage.h" unconditionally. IMO, "opt_vmpage.h" should only > >be included when KERNEL is defined. Would someone please make the change? > .... > > > The cache coloring options should be dynamic anyway. I have tried a few > different values on various machines but didn't notice much difference > and didn't have time to do careful comparisons. > The cache coloring tuning itself was on my list, and not really hard to do. It should also have a machine dependent component, and also query the processor, if it can, for info. The work to make the coloring dynamic is just a coding effort. The biggest issue (AFAIR) is that the current code is fairly efficient because of the inline usage of nice, power of two values. By making things dynamic, it is tricky to keep efficiency high. The additional overhead of doing the coloring might make it undesirable. It isn't necessary for the coloring to be "perfect" either, so it is okay to color a 256K cache system as if it is a 512K cache machine. Some coloring algorithms would become less efficient, but the FreeBSD one is okay with it. The coloring scheme that I chose for FreeBSD doesn't have the disadvantage of other, typical algorithms by being inflexible when memory of a certain color isn't available. Note that the micro-level coloring is really good, but the macro-level coloring could use some work. (The choice of the color for each object should be revisited.) Page coloring is awfully hard to benchmark. The only "quick" benchmark that I had was lmbench, lat_mem_rd. Page coloring mostly helps the system avoid "worst case" behavior, but to gain a sustained significant performance improvement is not likely. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 00:58:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19016 for freebsd-current-outgoing; Fri, 31 Jul 1998 00:58:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA19011 for ; Fri, 31 Jul 1998 00:58:48 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id KAA01426; Fri, 31 Jul 1998 10:00:42 +0200 (CEST) (envelope-from regnauld@deepo.prosa.dk) X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id KAA24320; Fri, 31 Jul 1998 10:03:08 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id KAA09821; Fri, 31 Jul 1998 10:00:28 +0200 (CEST) Message-ID: <19980731100027.62584@deepo.prosa.dk> Date: Fri, 31 Jul 1998 10:00:27 +0200 From: Philippe Regnauld To: Dermot McNally Cc: freebsd-current@FreeBSD.ORG Subject: Re: Problems with ed driver (PCI) References: <35bcb5ac.2742218@mail.compuserve.com> <35c03c26.2700750@mail.compuserve.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <35c03c26.2700750@mail.compuserve.com>; from Dermot McNally on Tue, Jul 28, 1998 at 09:13:31PM +0000 X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dermot McNally writes: > On Mon, 27 Jul 1998 17:41:15 GMT, you wrote: > > >However, this doesn't help, because after boot time, any attempt to > >configure the interface leads to the error: > > > >interface ed0 does not exist > > OK, There have been a few suggestions so far, none of which hits the > problem. I'd better give a few more details. > > The card is actually sold under the name "Micronet" although it is > recognised as a Realtek chipset. Its little green light goes on, indicating > that it sees the network OK and the corresponding little green light on the > hub comes on too. Ok, I've had this problem too -- I was at the ISOC Workshops in Geneva, and we wanted to install FreeBSD on the machines we had there (P200 HP Vectra ?L) -- the cards available were all 3c905, and a few spare Realtek chipset-based PCI ed's. FreeBSD 2.2.6 _with this machine_ has the exact same symptom: - probe find the card (as ed1) - ifconfig sees _no_ ed1. What bugs me is the _same_ card on another 2.2.6, this one ASUS TX-97 based, works fine. I even copied and pasted the relevant lines from the kernel config file... Could it be a PCI chipset bogosity ? -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 05:21:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17499 for freebsd-current-outgoing; Fri, 31 Jul 1998 05:21:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de ([139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17490 for ; Fri, 31 Jul 1998 05:20:59 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.8/8.7.3) id OAA00750 for freebsd-current@freebsd.org; Fri, 31 Jul 1998 14:20:15 +0200 (CEST) From: Holm Tiffe Message-Id: <199807311220.OAA00750@magnet.geophysik.tu-freiberg.de> Subject: Re: No More CTM Deltas on ftp.freebsd.org ? To: freebsd-current@FreeBSD.ORG Date: Fri, 31 Jul 1998 14:20:15 +0200 (CEST) Reply-To: freebsd@magnet.geophysik.tu-freiberg.de X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Holm Tiffe: > We have no actual cvs-cur deltas on ftp://ftp.freebsd.org/pub/CTM/cvs-cur , > the last delta is from Jul,8 1998. I don't know why but I know I always go to the following site to get missings deltas: Yes I know, I've got the latest deltas from there, but ftp.freebsd.org is FreeBSD's mastersite. I think, we should have actual deltas there, right ? This is a form of Linuxism, or Microsoft ? < Were do you want to get the deltas today ?> Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 06:16:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22673 for freebsd-current-outgoing; Fri, 31 Jul 1998 06:16:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22628 for ; Fri, 31 Jul 1998 06:16:45 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.8/8.7.3) id PAA00916 for freebsd-current@freebsd.org; Fri, 31 Jul 1998 15:16:30 +0200 (CEST) From: Holm Tiffe Message-Id: <199807311316.PAA00916@magnet.geophysik.tu-freiberg.de> Subject: Re: No More CTM Deltas on ftp.freebsd.org ? To: freebsd-current@FreeBSD.ORG Date: Fri, 31 Jul 1998 15:16:30 +0200 (CEST) Reply-To: freebsd@magnet.geophysik.tu-freiberg.de X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > I also noticed the problem. And found deltas at ftp://ctm.freebsd.org. > Try there. ...which is in the real life rzbsdi01.uni-trier.de. OK, I am a German, and in the DFN - Net too, but on the FreeBSD mastersite no Readme, but en existing cvs-cur that is outdatet several weeks. I think we shouldn't do such things, the FreeBSD CTM service has moved from on site to another several times, now this is enough. Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* ----- End of forwarded message from Mail Delivery Subsystem ----- -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 09:44:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17498 for freebsd-current-outgoing; Fri, 31 Jul 1998 09:44:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17493 for ; Fri, 31 Jul 1998 09:44:12 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id JAA24019; Fri, 31 Jul 1998 09:42:48 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: freebsd@magnet.geophysik.tu-freiberg.de cc: freebsd-current@FreeBSD.ORG Subject: Re: No More CTM Deltas on ftp.freebsd.org ? In-reply-to: Your message of "Fri, 31 Jul 1998 15:16:30 +0200." <199807311316.PAA00916@magnet.geophysik.tu-freiberg.de> Date: Fri, 31 Jul 1998 09:42:47 -0700 Message-ID: <24015.901903367@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OK, I am a German, and in the DFN - Net too, but on the FreeBSD > mastersite no Readme, but en existing cvs-cur that is outdatet > several weeks. CTM is currently and orphan and looking for a new home. I think Mark Murray was going to take it over, but I haven't heard anything about it. Ulf was also running it for awhile but that appears to have stopped - he might have more to say about it. > I think we shouldn't do such things, the FreeBSD CTM service > has moved from on site to another several times, now this is > enough. I think you're missing something fairly fundamental about free software projects here - this happens, especially with CTM, and there's no sense in saying "we shouldn't do such things" if such things are happening whether we like it or not. Are you volunteering to take over CTM generation? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 13:27:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19076 for freebsd-current-outgoing; Fri, 31 Jul 1998 13:27:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19062 for ; Fri, 31 Jul 1998 13:27:51 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id NAA26338; Fri, 31 Jul 1998 13:27:35 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 31 Jul 1998 13:27:35 -0700 (PDT) From: Doug White To: Philippe Regnauld cc: Dermot McNally , freebsd-current@FreeBSD.ORG Subject: Re: Problems with ed driver (PCI) In-Reply-To: <19980731100027.62584@deepo.prosa.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 31 Jul 1998, Philippe Regnauld wrote: > Dermot McNally writes: > > On Mon, 27 Jul 1998 17:41:15 GMT, you wrote: > > > > >However, this doesn't help, because after boot time, any attempt to > > >configure the interface leads to the error: > > > > > >interface ed0 does not exist > > > > OK, There have been a few suggestions so far, none of which hits the > > problem. I'd better give a few more details. > > > > The card is actually sold under the name "Micronet" although it is > > recognised as a Realtek chipset. Its little green light goes on, indicating > > that it sees the network OK and the corresponding little green light on the > > hub comes on too. > > Ok, I've had this problem too -- I was at the ISOC Workshops in > Geneva, and we wanted to install FreeBSD on the machines we had > there (P200 HP Vectra ?L) -- the cards available were all > 3c905, and a few spare Realtek chipset-based PCI ed's. > > FreeBSD 2.2.6 _with this machine_ has the exact same symptom: > > - probe find the card (as ed1) > - ifconfig sees _no_ ed1. > > What bugs me is the _same_ card on another 2.2.6, this > one ASUS TX-97 based, works fine. I even copied > and pasted the relevant lines from the kernel config file... Curiosity kills, what does `ifconfig -l' report on machines exhibiting this problem? Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 17:05:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28449 for freebsd-current-outgoing; Fri, 31 Jul 1998 17:05:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.baldcom.net (zone.BALDCOM.NET [205.232.46.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28444 for ; Fri, 31 Jul 1998 17:05:46 -0700 (PDT) (envelope-from green@zone.baldcom.net) Received: from localhost (green@localhost) by zone.baldcom.net (8.8.8/8.8.7) with SMTP id UAA25722 for ; Fri, 31 Jul 1998 20:05:19 -0400 (EDT) Date: Fri, 31 Jul 1998 20:05:19 -0400 (EDT) From: Brian Feldman To: freebsd-current@FreeBSD.ORG Subject: flock(2) problem & fix Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1425645226-901929919=:25645" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1425645226-901929919=:25645 Content-Type: TEXT/PLAIN; charset=US-ASCII Our flock(2) doesn't seem to do the right thing all the time. It seems that any user with read access to a file is allowed exclusive locking of it, which I think is wrong (does everyone agree?), and that a shared lock should be used, because the user does not own the file, and has no write permission, therefore no need for an exclusive lock. I raise the question as to whether it should matter if the lock is non-blocking or not, and that should be considered I suppose, as to assure the Right Thing will happen. Attached is a patch to sys/kern/kern_descrip.c which should fix the problem but is untested. Cheers, Brian Feldman green@unixhelp.org --- kern_descrip.c.old Fri Jul 31 18:28:30 1998 +++ kern_descrip.c Fri Jul 31 19:31:26 1998 @@ -986,6 +986,9 @@ register struct file *fp; struct vnode *vp; struct flock lf; + struct stat fst; + short gr; + boolean_t ok = 0; if ((unsigned)uap->fd >= fdp->fd_nfiles || (fp = fdp->fd_ofiles[uap->fd]) == NULL) @@ -1007,10 +1010,27 @@ lf.l_type = F_RDLCK; else return (EBADF); + vn_stat((struct vnode *)fp->f_data, &fst, p); + if (uap->how & LOCK_EX && p->p_cred->pc_ucred->cr_uid != 0 && + fp->f_cred->cr_uid != p->p_cred->pc_ucred->cr_uid && + !(fst.st_mode & S_IWOTH) && !(fst.st_mode & S_IWGRP)) + return (EPERM); + if (!(fst.st_mode & S_IWGRP)) + ok = 1; + else { + for (gr = 0; gr < p->p_cred->pc_ucred->cr_ngroups; gr++) + if (p->p_cred->pc_ucred->cr_groups[gr - 1] == fst.st_gid) { + ok = 1; + break; + } + } + if (ok) { fp->f_flag |= FHASLOCK; if (uap->how & LOCK_NB) return (VOP_ADVLOCK(vp, (caddr_t)fp, F_SETLK, &lf, F_FLOCK)); return (VOP_ADVLOCK(vp, (caddr_t)fp, F_SETLK, &lf, F_FLOCK|F_WAIT)); + } else + return (EPERM); } /* --0-1425645226-901929919=:25645 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="flock.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="flock.diff" LS0tIGtlcm5fZGVzY3JpcC5jLm9sZAlGcmkgSnVsIDMxIDE4OjI4OjMwIDE5 OTgNCisrKyBrZXJuX2Rlc2NyaXAuYwlGcmkgSnVsIDMxIDE5OjMxOjI2IDE5 OTgNCkBAIC05ODYsNiArOTg2LDkgQEANCiAJcmVnaXN0ZXIgc3RydWN0IGZp bGUgKmZwOw0KIAlzdHJ1Y3Qgdm5vZGUgKnZwOw0KIAlzdHJ1Y3QgZmxvY2sg bGY7DQorCXN0cnVjdCBzdGF0IGZzdDsNCisJc2hvcnQgZ3I7DQorCWJvb2xl YW5fdCBvayA9IDA7DQogDQogCWlmICgodW5zaWduZWQpdWFwLT5mZCA+PSBm ZHAtPmZkX25maWxlcyB8fA0KIAkgICAgKGZwID0gZmRwLT5mZF9vZmlsZXNb dWFwLT5mZF0pID09IE5VTEwpDQpAQCAtMTAwNywxMCArMTAxMCwyNyBAQA0K IAkJbGYubF90eXBlID0gRl9SRExDSzsNCiAJZWxzZQ0KIAkJcmV0dXJuIChF QkFERik7DQorCXZuX3N0YXQoKHN0cnVjdCB2bm9kZSAqKWZwLT5mX2RhdGEs ICZmc3QsIHApOw0KKwlpZiAodWFwLT5ob3cgJiBMT0NLX0VYICYmIHAtPnBf Y3JlZC0+cGNfdWNyZWQtPmNyX3VpZCAhPSAwICYmDQorCQlmcC0+Zl9jcmVk LT5jcl91aWQgIT0gcC0+cF9jcmVkLT5wY191Y3JlZC0+Y3JfdWlkICYmDQor CQkhKGZzdC5zdF9tb2RlICYgU19JV09USCkgJiYgIShmc3Quc3RfbW9kZSAm IFNfSVdHUlApKQ0KKwkJcmV0dXJuIChFUEVSTSk7DQorCWlmICghKGZzdC5z dF9tb2RlICYgU19JV0dSUCkpDQorCQlvayA9IDE7DQorCWVsc2Ugew0KKwlm b3IgKGdyID0gMDsgZ3IgPCBwLT5wX2NyZWQtPnBjX3VjcmVkLT5jcl9uZ3Jv dXBzOyBncisrKQ0KKwkJaWYgKHAtPnBfY3JlZC0+cGNfdWNyZWQtPmNyX2dy b3Vwc1tnciAtIDFdID09IGZzdC5zdF9naWQpIHsNCisJCQlvayA9IDE7DQor CQkJYnJlYWs7DQorCQl9CQ0KKwl9DQorCWlmIChvaykgew0KIAlmcC0+Zl9m bGFnIHw9IEZIQVNMT0NLOw0KIAlpZiAodWFwLT5ob3cgJiBMT0NLX05CKQ0K IAkJcmV0dXJuIChWT1BfQURWTE9DSyh2cCwgKGNhZGRyX3QpZnAsIEZfU0VU TEssICZsZiwgRl9GTE9DSykpOw0KIAlyZXR1cm4gKFZPUF9BRFZMT0NLKHZw LCAoY2FkZHJfdClmcCwgRl9TRVRMSywgJmxmLCBGX0ZMT0NLfEZfV0FJVCkp Ow0KKwl9IGVsc2UNCisJCXJldHVybiAoRVBFUk0pOw0KIH0NCiANCiAvKg0K --0-1425645226-901929919=:25645-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 17:15:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29724 for freebsd-current-outgoing; Fri, 31 Jul 1998 17:15:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29719 for ; Fri, 31 Jul 1998 17:15:33 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA01387; Fri, 31 Jul 1998 17:14:26 -0700 (PDT) Message-Id: <199808010014.RAA01387@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brian Feldman cc: freebsd-current@FreeBSD.ORG Subject: Re: flock(2) problem & fix In-reply-to: Your message of "Fri, 31 Jul 1998 20:05:19 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Jul 1998 17:14:26 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Our flock(2) doesn't seem to do the right thing all the time. It seems > that any user with read access to a file is allowed exclusive locking of > it, which I think is wrong (does everyone agree?), and that a shared lock > should be used, because the user does not own the file, and has no write > permission, therefore no need for an exclusive lock. I raise the question > as to whether it should matter if the lock is non-blocking or not, and > that should be considered I suppose, as to assure the Right Thing will > happen. Attached is a patch to sys/kern/kern_descrip.c which should fix > the problem but is untested. Sorry, I think you mistyped that last bit. Shouldn't it read "the tested patch is contained in PR kern/XXXX" ? 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 17:34:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01867 for freebsd-current-outgoing; Fri, 31 Jul 1998 17:34:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA01862 for ; Fri, 31 Jul 1998 17:34:34 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z2Pcw-00036s-00; Fri, 31 Jul 1998 17:34:26 -0700 Date: Fri, 31 Jul 1998 17:34:24 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Brian Feldman cc: freebsd-current@FreeBSD.ORG Subject: Re: flock(2) problem & fix In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-247509216-901931664=:29794" Content-ID: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-247509216-901931664=:29794 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: On Fri, 31 Jul 1998, Brian Feldman wrote: > Our flock(2) doesn't seem to do the right thing all the time. It seems > that any user with read access to a file is allowed exclusive locking of > it, which I think is wrong (does everyone agree?), and that a shared lock I disagree. The flock() method is advisory anyway. In fact, the file may exist for the sole purpose of flock'ing it. I know several programs that use lock files (which are always zero length) for locking purposes. Also, silently converting a exclusive lock request to a non-exclusive lock is VERY bad. Many programs will break. Tom --0-247509216-901931664=:29794 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="flock.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: LS0tIGtlcm5fZGVzY3JpcC5jLm9sZAlGcmkgSnVsIDMxIDE4OjI4OjMwIDE5 OTgNCisrKyBrZXJuX2Rlc2NyaXAuYwlGcmkgSnVsIDMxIDE5OjMxOjI2IDE5 OTgNCkBAIC05ODYsNiArOTg2LDkgQEANCiAJcmVnaXN0ZXIgc3RydWN0IGZp bGUgKmZwOw0KIAlzdHJ1Y3Qgdm5vZGUgKnZwOw0KIAlzdHJ1Y3QgZmxvY2sg bGY7DQorCXN0cnVjdCBzdGF0IGZzdDsNCisJc2hvcnQgZ3I7DQorCWJvb2xl YW5fdCBvayA9IDA7DQogDQogCWlmICgodW5zaWduZWQpdWFwLT5mZCA+PSBm ZHAtPmZkX25maWxlcyB8fA0KIAkgICAgKGZwID0gZmRwLT5mZF9vZmlsZXNb dWFwLT5mZF0pID09IE5VTEwpDQpAQCAtMTAwNywxMCArMTAxMCwyNyBAQA0K IAkJbGYubF90eXBlID0gRl9SRExDSzsNCiAJZWxzZQ0KIAkJcmV0dXJuIChF QkFERik7DQorCXZuX3N0YXQoKHN0cnVjdCB2bm9kZSAqKWZwLT5mX2RhdGEs ICZmc3QsIHApOw0KKwlpZiAodWFwLT5ob3cgJiBMT0NLX0VYICYmIHAtPnBf Y3JlZC0+cGNfdWNyZWQtPmNyX3VpZCAhPSAwICYmDQorCQlmcC0+Zl9jcmVk LT5jcl91aWQgIT0gcC0+cF9jcmVkLT5wY191Y3JlZC0+Y3JfdWlkICYmDQor CQkhKGZzdC5zdF9tb2RlICYgU19JV09USCkgJiYgIShmc3Quc3RfbW9kZSAm IFNfSVdHUlApKQ0KKwkJcmV0dXJuIChFUEVSTSk7DQorCWlmICghKGZzdC5z dF9tb2RlICYgU19JV0dSUCkpDQorCQlvayA9IDE7DQorCWVsc2Ugew0KKwlm b3IgKGdyID0gMDsgZ3IgPCBwLT5wX2NyZWQtPnBjX3VjcmVkLT5jcl9uZ3Jv dXBzOyBncisrKQ0KKwkJaWYgKHAtPnBfY3JlZC0+cGNfdWNyZWQtPmNyX2dy b3Vwc1tnciAtIDFdID09IGZzdC5zdF9naWQpIHsNCisJCQlvayA9IDE7DQor CQkJYnJlYWs7DQorCQl9CQ0KKwl9DQorCWlmIChvaykgew0KIAlmcC0+Zl9m bGFnIHw9IEZIQVNMT0NLOw0KIAlpZiAodWFwLT5ob3cgJiBMT0NLX05CKQ0K IAkJcmV0dXJuIChWT1BfQURWTE9DSyh2cCwgKGNhZGRyX3QpZnAsIEZfU0VU TEssICZsZiwgRl9GTE9DSykpOw0KIAlyZXR1cm4gKFZPUF9BRFZMT0NLKHZw LCAoY2FkZHJfdClmcCwgRl9TRVRMSywgJmxmLCBGX0ZMT0NLfEZfV0FJVCkp Ow0KKwl9IGVsc2UNCisJCXJldHVybiAoRVBFUk0pOw0KIH0NCiANCiAvKg0K --0-247509216-901931664=:29794-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 18:01:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05834 for freebsd-current-outgoing; Fri, 31 Jul 1998 18:01:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05820 for ; Fri, 31 Jul 1998 18:01:15 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA12454; Fri, 31 Jul 1998 22:34:08 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807312134.WAA12454@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: lcremean@tidalwave.net cc: current@FreeBSD.ORG Subject: Re: Identd problems on -current of 980724 In-reply-to: Your message of "Fri, 31 Jul 1998 00:48:59 EDT." <19980731004859.A15715@st-lcremean.tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Jul 1998 22:34:07 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm running -cuurent CVSup'd the night of 7/24, with the user-ppp it came > with, and I've noticed that my identd has stopped working for remote hosts. > What is causing this? Just identd broke ? > PS: Predictor-1 was broken in that snap; I was noticing strage connection > hangs to some sites. They went away when I disabled it. Predictor-1 compression hasn't changed. Have you tried disabling TCP extensions ? If this doesn't work, you'll need to supply some more information. Also, what were you cvsup'ing from ? Is this your first experience of the new (2.0) version of ppp ? > -- > Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) > A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did > $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net > FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) > My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 18:08:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07547 for freebsd-current-outgoing; Fri, 31 Jul 1998 18:08:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.baldcom.net (zone.BALDCOM.NET [205.232.46.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07530 for ; Fri, 31 Jul 1998 18:08:42 -0700 (PDT) (envelope-from green@zone.baldcom.net) Received: from localhost (green@localhost) by zone.baldcom.net (8.8.8/8.8.7) with SMTP id VAA26305; Fri, 31 Jul 1998 21:08:09 -0400 (EDT) Date: Fri, 31 Jul 1998 21:08:09 -0400 (EDT) From: Brian Feldman To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: flock(2) problem & fix In-Reply-To: <199808010014.RAA01387@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whoops, I suppose you're right, I think I'll start testing it out =) With respect to Tom's comment, this won't cnvert an exclusive to a non-exclusive lock, it will return EPERM; also, the program SHOULDn't be using an exclusive lock, it should be using a shared lock. Cheers, Brian Feldman green@unixhelp.org On Fri, 31 Jul 1998, Mike Smith wrote: > > > > Our flock(2) doesn't seem to do the right thing all the time. It seems > > that any user with read access to a file is allowed exclusive locking of > > it, which I think is wrong (does everyone agree?), and that a shared lock > > should be used, because the user does not own the file, and has no write > > permission, therefore no need for an exclusive lock. I raise the question > > as to whether it should matter if the lock is non-blocking or not, and > > that should be considered I suppose, as to assure the Right Thing will > > happen. Attached is a patch to sys/kern/kern_descrip.c which should fix > > the problem but is untested. > > Sorry, I think you mistyped that last bit. Shouldn't it read "the > tested patch is contained in PR kern/XXXX" ? > > 8) > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 18:38:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10673 for freebsd-current-outgoing; Fri, 31 Jul 1998 18:38:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10668 for ; Fri, 31 Jul 1998 18:38:12 -0700 (PDT) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.8.8/8.8.7) id VAA00304; Fri, 31 Jul 1998 21:35:33 -0400 (EDT) (envelope-from lee) Message-ID: <19980731213532.A270@st-lcremean.tidalwave.net> Date: Fri, 31 Jul 1998 21:35:32 -0400 From: Lee Cremeans To: Brian Somers Cc: current@FreeBSD.ORG Subject: Re: Identd problems on -current of 980724 Reply-To: lcremean@tidalwave.net References: <19980731004859.A15715@st-lcremean.tidalwave.net> <199807312134.WAA12454@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199807312134.WAA12454@awfulhak.org>; from Brian Somers on Fri, Jul 31, 1998 at 10:34:07PM +0100 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 31, 1998 at 10:34:07PM +0100, Brian Somers wrote: > > I'm running -cuurent CVSup'd the night of 7/24, with the user-ppp it came > > with, and I've noticed that my identd has stopped working for remote hosts. > > What is causing this? > > Just identd broke ? As far as I can tell, yes. > > PS: Predictor-1 was broken in that snap; I was noticing strage connection > > hangs to some sites. They went away when I disabled it. > > Predictor-1 compression hasn't changed. Have you tried disabling TCP > extensions ? If this doesn't work, you'll need to supply some more > information. Well, identd was broken even before I disabled Predictor-1....and disabling TCP extensions does not fix it. FWIW< disabling TCP extensions didn't help the connection hangs either...disabling Pred-1 did. -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 19:28:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15582 for freebsd-current-outgoing; Fri, 31 Jul 1998 19:28:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15577 for ; Fri, 31 Jul 1998 19:28:28 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id WAA21993; Fri, 31 Jul 1998 22:18:38 -0400 (EDT) Date: Fri, 31 Jul 1998 22:26:35 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: lcremean@tidalwave.net cc: Brian Somers , current@FreeBSD.ORG Subject: Re: Identd problems on -current of 980724 In-Reply-To: <19980731213532.A270@st-lcremean.tidalwave.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 31 Jul 1998, Lee Cremeans wrote: > As far as I can tell, yes. I made a post about this to the security list a few days ago with very little response. pidentd out of ports is not working. It works fine for all LOCAL tests, but remote lookups fail with NO-USER for me. I don't know what's broke but something is. Chris -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." -Wes Peters ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.7 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 19:44:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17312 for freebsd-current-outgoing; Fri, 31 Jul 1998 19:44:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17283 for ; Fri, 31 Jul 1998 19:43:56 -0700 (PDT) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.8.8/8.8.7) id WAA00456; Fri, 31 Jul 1998 22:40:58 -0400 (EDT) (envelope-from lee) Message-ID: <19980731224058.A449@st-lcremean.tidalwave.net> Date: Fri, 31 Jul 1998 22:40:58 -0400 From: Lee Cremeans To: Open Systems Networking , lcremean@tidalwave.net Cc: Brian Somers , current@FreeBSD.ORG Subject: Re: Identd problems on -current of 980724 Reply-To: lcremean@tidalwave.net References: <19980731213532.A270@st-lcremean.tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from Open Systems Networking on Fri, Jul 31, 1998 at 10:26:35PM -0400 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 31, 1998 at 10:26:35PM -0400, Open Systems Networking wrote: > On Fri, 31 Jul 1998, Lee Cremeans wrote: > > > As far as I can tell, yes. > > I made a post about this to the security list a few days ago with very > little response. pidentd out of ports is not working. It works fine for > all LOCAL tests, but remote lookups fail with NO-USER for me. > I don't know what's broke but something is. Exactly the same problem I'm having. I should note that it did work in 2.2.x, but as soon as I went to -current, it broke. Any input form anyone as to why this would happen? I get the feeling that changes in the 3.0 networking code broke it. -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 20:03:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19569 for freebsd-current-outgoing; Fri, 31 Jul 1998 20:03:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19561 for ; Fri, 31 Jul 1998 20:03:22 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id UAA16008; Fri, 31 Jul 1998 20:03:12 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpd015971; Fri Jul 31 20:03:04 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id UAA06065; Fri, 31 Jul 1998 20:02:55 -0700 (MST) From: Terry Lambert Message-Id: <199808010302.UAA06065@usr06.primenet.com> Subject: Re: flock(2) problem & fix To: green@zone.baldcom.net (Brian Feldman) Date: Sat, 1 Aug 1998 03:02:55 +0000 (GMT) Cc: mike@smith.net.au, freebsd-current@FreeBSD.ORG In-Reply-To: from "Brian Feldman" at Jul 31, 98 09:08:09 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Whoops, I suppose you're right, I think I'll start testing it out =) With > respect to Tom's comment, this won't cnvert an exclusive to a > non-exclusive lock, it will return EPERM; also, the program SHOULDn't be > using an exclusive lock, it should be using a shared lock. What if they are using it as a semaphore, and could care less whether they were reading or writing the file? I could see a case where a program opend a file for read only to run an image of a program from a foreign architecture, for instance, and would want to use read to ensure that the "swap store" was not accidently corrupted by the simulator. They would want exclude modification of the image they intend only to *read* out from under them. In other words, they want to simulate VEXEC for a read-only mapped executable in user space. A secondard situation would be a set of non-work-to-do processing engines working on a source data set. Program one opens the file, writes new data, closes it, and signals program two. Program two uses the file and the output of program one to do work, and then requests the original program to interpolate new data bsed on its results, and the process repeats. Once could see this happening, for example, in a pseudo realtime data analysis tool that could only accept new data on soft boundries, but had two programs, one optimized for Fourier analysis, the other for Gaussian reduction (maybe the Fourier analysis program was seperate because it runs on a DSP and not on the main processor, and the DSP is not part of the acquisition channel). You could use such a system for all sorts of biometric regconitions (speech, speaker, retinal scanning, finger print, etc.). One could even envision a "frozen" back propagation neural networking program that had to be reset each time it was run because the outputs were no longer being clamped by a human giving it feedback. Anyway, suffice to say, I think exclusive locking a file without the intention *or possibility* of writing is an "ok thing to do". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 20:05:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19853 for freebsd-current-outgoing; Fri, 31 Jul 1998 20:05:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19847 for ; Fri, 31 Jul 1998 20:05:38 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id UAA16060; Fri, 31 Jul 1998 20:05:34 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp02.primenet.com, id smtpd016030; Fri Jul 31 20:05:30 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id UAA06227; Fri, 31 Jul 1998 20:05:28 -0700 (MST) From: Terry Lambert Message-Id: <199808010305.UAA06227@usr06.primenet.com> Subject: Re: Identd problems on -current of 980724 To: lcremean@tidalwave.net Date: Sat, 1 Aug 1998 03:05:28 +0000 (GMT) Cc: brian@Awfulhak.org, current@FreeBSD.ORG In-Reply-To: <19980731213532.A270@st-lcremean.tidalwave.net> from "Lee Cremeans" at Jul 31, 98 09:35:32 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Just identd broke ? > > As far as I can tell, yes. > > > > PS: Predictor-1 was broken in that snap; I was noticing strage connection > > > hangs to some sites. They went away when I disabled it. > > > > Predictor-1 compression hasn't changed. Have you tried disabling TCP > > extensions ? If this doesn't work, you'll need to supply some more > > information. > > Well, identd was broken even before I disabled Predictor-1....and disabling > TCP extensions does not fix it. FWIW< disabling TCP extensions didn't help > the connection hangs either...disabling Pred-1 did. Did you recompile libkvm, reinstall it, and then recompile and install the identd? The identd relies on kernel structures; specifically,it relies on being able to access the system open file table and traverse it to identify the socket connected to the remote host, then looks up the credential based on the contents of teh cred, before passing it back to the requesting system. You may also want to make sure it is running as root. If not, it will not be able to get a reserved port. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 20:18:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20970 for freebsd-current-outgoing; Fri, 31 Jul 1998 20:18:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20957 for ; Fri, 31 Jul 1998 20:18:18 -0700 (PDT) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.8.8/8.8.7) id XAA00552; Fri, 31 Jul 1998 23:15:53 -0400 (EDT) (envelope-from lee) Message-ID: <19980731231553.A545@st-lcremean.tidalwave.net> Date: Fri, 31 Jul 1998 23:15:53 -0400 From: Lee Cremeans To: Terry Lambert , lcremean@tidalwave.net Cc: brian@Awfulhak.org, current@FreeBSD.ORG Subject: Re: Identd problems on -current of 980724 Reply-To: lcremean@tidalwave.net References: <19980731213532.A270@st-lcremean.tidalwave.net> <199808010305.UAA06227@usr06.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808010305.UAA06227@usr06.primenet.com>; from Terry Lambert on Sat, Aug 01, 1998 at 03:05:28AM +0000 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Aug 01, 1998 at 03:05:28AM +0000, Terry Lambert wrote: > > > Just identd broke ? > > > > As far as I can tell, yes. > > > > > > PS: Predictor-1 was broken in that snap; I was noticing strage connection > > > > hangs to some sites. They went away when I disabled it. > > > > > > Predictor-1 compression hasn't changed. Have you tried disabling TCP > > > extensions ? If this doesn't work, you'll need to supply some more > > > information. > > > > Well, identd was broken even before I disabled Predictor-1....and disabling > > TCP extensions does not fix it. FWIW< disabling TCP extensions didn't help > > the connection hangs either...disabling Pred-1 did. > > Did you recompile libkvm, reinstall it, and then recompile and install > the identd? This was after a make world upgrade, so yes, libkvm should ahve updated. And yes, I did recompile pidentd. > You may also want to make sure it is running as root. If not, it will > not be able to get a reserved port. It's running from inetd. -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 20:41:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23616 for freebsd-current-outgoing; Fri, 31 Jul 1998 20:41:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23611 for ; Fri, 31 Jul 1998 20:41:51 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id UAA26788; Fri, 31 Jul 1998 20:39:16 -0700 (PDT) Message-Id: <199808010339.UAA26788@implode.root.com> To: Terry Lambert cc: green@zone.baldcom.net (Brian Feldman), mike@smith.net.au, freebsd-current@FreeBSD.ORG Subject: Re: flock(2) problem & fix In-reply-to: Your message of "Sat, 01 Aug 1998 03:02:55 -0000." <199808010302.UAA06065@usr06.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 31 Jul 1998 20:39:15 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Anyway, suffice to say, I think exclusive locking a file without the >intention *or possibility* of writing is an "ok thing to do". For what it's worth, I agree. I also asked Kirk McKusick, the author of the advisory locking code, and he thinks similarly. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 21:01:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25649 for freebsd-current-outgoing; Fri, 31 Jul 1998 21:01:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25608 for ; Fri, 31 Jul 1998 21:01:31 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id DAA23266; Sat, 1 Aug 1998 03:19:07 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199808010219.DAA23266@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: lcremean@tidalwave.net cc: Brian Somers , current@FreeBSD.ORG Subject: Re: Identd problems on -current of 980724 In-reply-to: Your message of "Fri, 31 Jul 1998 21:35:32 EDT." <19980731213532.A270@st-lcremean.tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Aug 1998 03:19:06 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Jul 31, 1998 at 10:34:07PM +0100, Brian Somers wrote: > > > I'm running -cuurent CVSup'd the night of 7/24, with the user-ppp it came > > > with, and I've noticed that my identd has stopped working for remote hosts. > > > What is causing this? > > > > Just identd broke ? > > As far as I can tell, yes. > > > > PS: Predictor-1 was broken in that snap; I was noticing strage connection > > > hangs to some sites. They went away when I disabled it. > > > > Predictor-1 compression hasn't changed. Have you tried disabling TCP > > extensions ? If this doesn't work, you'll need to supply some more > > information. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ What's on the other side of the link ? What do your logs say ? What do your config files look like ? How are you starting ppp ? Are the ``connection hangs'' consistent (always when downloading specific data) ? Is ppp sending & receiving information while the hang happens ? Is it possible to talk to other machines or is ppp dead after this happens ? Have you got any ipfw filters ? > Well, identd was broken even before I disabled Predictor-1....and disabling > TCP extensions does not fix it. FWIW< disabling TCP extensions didn't help > the connection hangs either...disabling Pred-1 did. > > -- > Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) > A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did > $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net > FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) > My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 21:11:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26666 for freebsd-current-outgoing; Fri, 31 Jul 1998 21:11:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pobox.com (jaresh-5.mdm.mke.execpc.com [169.207.81.133]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA26659 for ; Fri, 31 Jul 1998 21:11:07 -0700 (PDT) (envelope-from hamilton@pobox.com) Message-Id: <199808010411.VAA26659@hub.freebsd.org> Received: (qmail 10118 invoked from network); 31 Jul 1998 23:14:06 -0500 Received: from localhost (HELO pobox.com) (127.0.0.1) by localhost with SMTP; 31 Jul 1998 23:14:06 -0500 To: lcremean@tidalwave.net Cc: current@FreeBSD.ORG Subject: Re: Identd problems on -current of 980724 In-reply-to: Your message of "Fri, 31 Jul 1998 23:15:53 EDT." <19980731231553.A545@st-lcremean.tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Jul 1998 23:14:06 -0500 From: Jon Hamilton Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG } > Did you recompile libkvm, reinstall it, and then recompile and install } > the identd? } } This was after a make world upgrade, so yes, libkvm should ahve updated. And } yes, I did recompile pidentd. You didn't explicitly say; did you also build a new kernel and reboot after that? } > You may also want to make sure it is running as root. If not, it will } > not be able to get a reserved port. } } It's running from inetd. As root? Inetd can start processes as any user, but if it worked before and you didn't change the configuration, it must have been set up to start as root. -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 21:30:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28226 for freebsd-current-outgoing; Fri, 31 Jul 1998 21:30:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28212 for ; Fri, 31 Jul 1998 21:30:11 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id AAA11287; Sat, 1 Aug 1998 00:22:28 -0400 (EDT) Date: Sat, 1 Aug 1998 00:30:19 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Jon Hamilton cc: lcremean@tidalwave.net, current@FreeBSD.ORG Subject: Re: Identd problems on -current of 980724 In-Reply-To: <199808010411.VAA26659@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 31 Jul 1998, Jon Hamilton wrote: > As root? Inetd can start processes as any user, but if it worked before > and you didn't change the configuration, it must have been set up to start > as root. It runs as root by default in inetd.conf unless someone changes it. Im gonna rebuild libkvm right now and build a new kernel, reboot then rebuild pidentd from ports. If it still doesnt work then I can say with alot more accuracy that something is scrogged in the -current code. Ill post my findings in a few minutes. Chris -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." -Wes Peters ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.7 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 21:42:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29301 for freebsd-current-outgoing; Fri, 31 Jul 1998 21:42:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29201 for ; Fri, 31 Jul 1998 21:42:00 -0700 (PDT) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.8.8/8.8.7) id AAA00833; Sat, 1 Aug 1998 00:41:45 -0400 (EDT) (envelope-from lee) Message-ID: <19980801004145.B790@st-lcremean.tidalwave.net> Date: Sat, 1 Aug 1998 00:41:45 -0400 From: Lee Cremeans To: Jon Hamilton , lcremean@tidalwave.net Cc: current@FreeBSD.ORG Subject: Re: Identd problems on -current of 980724 Reply-To: lcremean@tidalwave.net References: <19980731231553.A545@st-lcremean.tidalwave.net> <199808010411.VAA26659@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808010411.VAA26659@hub.freebsd.org>; from Jon Hamilton on Fri, Jul 31, 1998 at 11:14:06PM -0500 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 31, 1998 at 11:14:06PM -0500, Jon Hamilton wrote: > > > } > Did you recompile libkvm, reinstall it, and then recompile and install > } > the identd? > } > } This was after a make world upgrade, so yes, libkvm should ahve updated. And > } yes, I did recompile pidentd. > > You didn't explicitly say; did you also build a new kernel and reboot after > that? Yes. > > } > You may also want to make sure it is running as root. If not, it will > } > not be able to get a reserved port. > } > } It's running from inetd. > > As root? Inetd can start processes as any user, but if it worked before > and you didn't change the configuration, it must have been set up to start > as root. I double-checked, and it is running as root. -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 21:42:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29371 for freebsd-current-outgoing; Fri, 31 Jul 1998 21:42:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29356 for ; Fri, 31 Jul 1998 21:42:21 -0700 (PDT) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.8.8/8.8.7) id AAA00815; Sat, 1 Aug 1998 00:40:39 -0400 (EDT) (envelope-from lee) Message-ID: <19980801004039.A790@st-lcremean.tidalwave.net> Date: Sat, 1 Aug 1998 00:40:39 -0400 From: Lee Cremeans To: Brian Somers , lcremean@tidalwave.net Cc: current@FreeBSD.ORG Subject: Re: Identd problems on -current of 980724 Reply-To: lcremean@tidalwave.net References: <19980731213532.A270@st-lcremean.tidalwave.net> <199808010219.DAA23266@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808010219.DAA23266@awfulhak.org>; from Brian Somers on Sat, Aug 01, 1998 at 03:19:06AM +0100 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Aug 01, 1998 at 03:19:06AM +0100, Brian Somers wrote: > > On Fri, Jul 31, 1998 at 10:34:07PM +0100, Brian Somers wrote: > > > > I'm running -cuurent CVSup'd the night of 7/24, with the user-ppp it came > > > > with, and I've noticed that my identd has stopped working for remote hosts. > > > > What is causing this? > > > > > > Just identd broke ? > > > > As far as I can tell, yes. > > > > > > PS: Predictor-1 was broken in that snap; I was noticing strage connection > > > > hangs to some sites. They went away when I disabled it. > > > > > > Predictor-1 compression hasn't changed. Have you tried disabling TCP > > > extensions ? If this doesn't work, you'll need to supply some more > > > information. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > What's on the other side of the link ? What do your logs say ? What > do your config files look like ? How are you starting ppp ? Are the > ``connection hangs'' consistent (always when downloading specific > data) ? It only happened while hitting certain sites, I notice. www.freebsd.org, slashdot.org, and www.m-w.com were doing it, as was using the command-line whois (which hung after "Registrant:"). No other sites were afffected, to my knowledge... As for my config, here goes: default: set speed 115200 set device /dev/cuaa1 set ctsrts on alias enable yes alias unregistered_only yes set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATZ OK-AT-OK \\dATDT\\T TIMEOUT 40 CONNECT" set timeout 0 set redial 30 disable lqr deny lqr disable pred1 deny pred1 #disable vjcomp #deny vjcomp set log Phase Chat Connect Link LCP IPCP CCP tun tidalwave: set mtu 576 set phone "690-0006|392-0477:758-8993" set login "TIMEOUT 30 ogin:-\\r-ogin: lcremean word: " set ifaddr 0 208.0.0.0/8 -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 21:51:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00607 for freebsd-current-outgoing; Fri, 31 Jul 1998 21:51:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00599 for ; Fri, 31 Jul 1998 21:51:19 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id AAA14007; Sat, 1 Aug 1998 00:43:37 -0400 (EDT) Date: Sat, 1 Aug 1998 00:51:33 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Jon Hamilton cc: lcremean@tidalwave.net, current@FreeBSD.ORG Subject: Re: Identd problems on -current of 980724 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ill post my findings in a few minutes. Ok I just: cvsup'd latest current rebuilt libkvm rebuilt a new kernel deinstalled pidentd rebooted rebuilt pidentd HUP'd inetd And it still keeps failing on non-local lookups with NO-USER. I cant grawk why it's doing this. Chris -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." -Wes Peters ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.7 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 22:09:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02501 for freebsd-current-outgoing; Fri, 31 Jul 1998 22:09:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02492 for ; Fri, 31 Jul 1998 22:09:54 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA31372; Sat, 1 Aug 1998 15:09:46 +1000 Date: Sat, 1 Aug 1998 15:09:46 +1000 From: Bruce Evans Message-Id: <199808010509.PAA31372@godzilla.zeta.org.au> To: freebsd@magnet.geophysik.tu-freiberg.de, jkh@time.cdrom.com Subject: Re: No More CTM Deltas on ftp.freebsd.org ? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >CTM is currently and orphan and looking for a new home. I think Mark >Murray was going to take it over, but I haven't heard anything about >it. Ulf was also running it for awhile but that appears to have >stopped - he might have more to say about it. CTM generation has been working perfectly lately. The freebsd.org mirror just seems to have forgotten about it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 22:29:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03840 for freebsd-current-outgoing; Fri, 31 Jul 1998 22:29:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles361.castles.com [208.214.167.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03835 for ; Fri, 31 Jul 1998 22:29:23 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA00378; Fri, 31 Jul 1998 22:28:28 -0700 (PDT) Message-Id: <199808010528.WAA00378@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Philippe Regnauld cc: Dermot McNally , freebsd-current@FreeBSD.ORG Subject: Re: Problems with ed driver (PCI) In-reply-to: Your message of "Fri, 31 Jul 1998 10:00:27 +0200." <19980731100027.62584@deepo.prosa.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Jul 1998 22:28:28 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Dermot McNally writes: > > On Mon, 27 Jul 1998 17:41:15 GMT, you wrote: > > > > >However, this doesn't help, because after boot time, any attempt to > > >configure the interface leads to the error: > > > > > >interface ed0 does not exist > > > > OK, There have been a few suggestions so far, none of which hits the > > problem. I'd better give a few more details. > > > > The card is actually sold under the name "Micronet" although it is > > recognised as a Realtek chipset. Its little green light goes on, indicating > > that it sees the network OK and the corresponding little green light on the > > hub comes on too. > > Ok, I've had this problem too -- I was at the ISOC Workshops in > Geneva, and we wanted to install FreeBSD on the machines we had > there (P200 HP Vectra ?L) -- the cards available were all > 3c905, and a few spare Realtek chipset-based PCI ed's. > > FreeBSD 2.2.6 _with this machine_ has the exact same symptom: > > - probe find the card (as ed1) > - ifconfig sees _no_ ed1. No, this is PCI probe detects card, 'ed' probe does *not* find it. > What bugs me is the _same_ card on another 2.2.6, this > one ASUS TX-97 based, works fine. I even copied > and pasted the relevant lines from the kernel config file... > > Could it be a PCI chipset bogosity ? Sounds more like a BIOS issue. Try altering the "PnP OS installed" setting and see what happens. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 22:55:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06025 for freebsd-current-outgoing; Fri, 31 Jul 1998 22:55:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06019 for ; Fri, 31 Jul 1998 22:55:36 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id WAA00630; Fri, 31 Jul 1998 22:53:57 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Bruce Evans cc: freebsd@magnet.geophysik.tu-freiberg.de, freebsd-current@FreeBSD.ORG Subject: Re: No More CTM Deltas on ftp.freebsd.org ? In-reply-to: Your message of "Sat, 01 Aug 1998 15:09:46 +1000." <199808010509.PAA31372@godzilla.zeta.org.au> Date: Fri, 31 Jul 1998 22:53:57 -0700 Message-ID: <627.901950837@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm. I don't even remember where it is anymore - anyone got an FTP URL for me to mirror? - Jordan > >CTM is currently and orphan and looking for a new home. I think Mark > >Murray was going to take it over, but I haven't heard anything about > >it. Ulf was also running it for awhile but that appears to have > >stopped - he might have more to say about it. > > CTM generation has been working perfectly lately. The freebsd.org > mirror just seems to have forgotten about it. > > Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 23:22:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08078 for freebsd-current-outgoing; Fri, 31 Jul 1998 23:22:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08070 for ; Fri, 31 Jul 1998 23:22:39 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id IAA02246; Sat, 1 Aug 1998 08:18:56 +0200 (CEST) To: dg@root.com cc: Terry Lambert , green@zone.baldcom.net (Brian Feldman), mike@smith.net.au, freebsd-current@FreeBSD.ORG Subject: Re: flock(2) problem & fix In-reply-to: Your message of "Fri, 31 Jul 1998 20:39:15 PDT." <199808010339.UAA26788@implode.root.com> Date: Sat, 01 Aug 1998 08:18:54 +0200 Message-ID: <2244.901952334@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199808010339.UAA26788@implode.root.com>, David Greenman writes: >>Anyway, suffice to say, I think exclusive locking a file without the >>intention *or possibility* of writing is an "ok thing to do". > > For what it's worth, I agree. I also asked Kirk McKusick, the author of >the advisory locking code, and he thinks similarly. I agree, it means "I need a consistent view of this file, don't mess with it." Which is a legitimate thing to ask for. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 23:26:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08427 for freebsd-current-outgoing; Fri, 31 Jul 1998 23:26:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08421 for ; Fri, 31 Jul 1998 23:26:14 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id XAA23445; Fri, 31 Jul 1998 23:26:04 -0700 (PDT) Message-ID: <19980731232604.F17037@Alameda.net> Date: Fri, 31 Jul 1998 23:26:04 -0700 From: Ulf Zimmermann To: "Jordan K. Hubbard" , Bruce Evans Cc: freebsd@magnet.geophysik.tu-freiberg.de, freebsd-current@FreeBSD.ORG Subject: Re: No More CTM Deltas on ftp.freebsd.org ? Reply-To: ulf@Alameda.net References: <199808010509.PAA31372@godzilla.zeta.org.au> <627.901950837@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <627.901950837@time.cdrom.com>; from Jordan K. Hubbard on Fri, Jul 31, 1998 at 10:53:57PM -0700 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 31, 1998 at 10:53:57PM -0700, Jordan K. Hubbard wrote: > Hmmm. I don't even remember where it is anymore - anyone got > an FTP URL for me to mirror? Wasn't that the reason you gave Markm the rights on wcarchive ? > > - Jordan > > > >CTM is currently and orphan and looking for a new home. I think Mark > > >Murray was going to take it over, but I haven't heard anything about > > >it. Ulf was also running it for awhile but that appears to have > > >stopped - he might have more to say about it. > > > > CTM generation has been working perfectly lately. The freebsd.org > > mirror just seems to have forgotten about it. > > > > Bruce > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 31 23:37:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09362 for freebsd-current-outgoing; Fri, 31 Jul 1998 23:37:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09355 for ; Fri, 31 Jul 1998 23:37:46 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id XAA00768; Fri, 31 Jul 1998 23:36:18 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: ulf@Alameda.net cc: Bruce Evans , freebsd@magnet.geophysik.tu-freiberg.de, freebsd-current@FreeBSD.ORG Subject: Re: No More CTM Deltas on ftp.freebsd.org ? In-reply-to: Your message of "Fri, 31 Jul 1998 23:26:04 PDT." <19980731232604.F17037@Alameda.net> Date: Fri, 31 Jul 1998 23:36:18 -0700 Message-ID: <764.901953378@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh, right. Mumble. I'll ask Mark what's going on - I even chowned the CTM directory to him. - Jordan > On Fri, Jul 31, 1998 at 10:53:57PM -0700, Jordan K. Hubbard wrote: > > Hmmm. I don't even remember where it is anymore - anyone got > > an FTP URL for me to mirror? > > Wasn't that the reason you gave Markm the rights on wcarchive ? > > > > > - Jordan > > > > > >CTM is currently and orphan and looking for a new home. I think Mark > > > >Murray was going to take it over, but I haven't heard anything about > > > >it. Ulf was also running it for awhile but that appears to have > > > >stopped - he might have more to say about it. > > > > > > CTM generation has been working perfectly lately. The freebsd.org > > > mirror just seems to have forgotten about it. > > > > > > Bruce > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- > Regards, Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 1 03:02:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25730 for freebsd-current-outgoing; Sat, 1 Aug 1998 03:02:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA25725 for ; Sat, 1 Aug 1998 03:02:56 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id DAA00472; Sat, 1 Aug 1998 03:02:51 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd000459; Sat Aug 1 03:02:45 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id DAA02146; Sat, 1 Aug 1998 03:02:41 -0700 (MST) From: Terry Lambert Message-Id: <199808011002.DAA02146@usr08.primenet.com> Subject: Re: Identd problems on -current of 980724 To: opsys@mail.webspan.net (Open Systems Networking) Date: Sat, 1 Aug 1998 10:02:41 +0000 (GMT) Cc: hamilton@pobox.com, lcremean@tidalwave.net, current@FreeBSD.ORG In-Reply-To: from "Open Systems Networking" at Aug 1, 98 00:51:33 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Ill post my findings in a few minutes. > > Ok I just: > > cvsup'd latest current > rebuilt libkvm > rebuilt a new kernel > deinstalled pidentd > rebooted > rebuilt pidentd > HUP'd inetd > > And it still keeps failing on non-local lookups with NO-USER. > I cant grawk why it's doing this. Time to break out "TCPdump" on both the client and the server, and see if the packets are getting through in both directions, and what their contents are cmpared to the RFC for the protocol. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 1 06:47:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13564 for freebsd-current-outgoing; Sat, 1 Aug 1998 06:47:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13558 for ; Sat, 1 Aug 1998 06:47:25 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id NAA15775; Sat, 1 Aug 1998 13:30:03 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199808011230.NAA15775@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: lcremean@tidalwave.net cc: Brian Somers , current@FreeBSD.ORG Subject: Re: Identd problems on -current of 980724 In-reply-to: Your message of "Sat, 01 Aug 1998 00:40:39 EDT." <19980801004039.A790@st-lcremean.tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Aug 1998 13:30:00 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does it make any difference if you remove the ``set mtu'' ? > On Sat, Aug 01, 1998 at 03:19:06AM +0100, Brian Somers wrote: > > > On Fri, Jul 31, 1998 at 10:34:07PM +0100, Brian Somers wrote: > > > > > I'm running -cuurent CVSup'd the night of 7/24, with the user-ppp it came > > > > > with, and I've noticed that my identd has stopped working for remote hosts. > > > > > What is causing this? > > > > > > > > Just identd broke ? > > > > > > As far as I can tell, yes. > > > > > > > > PS: Predictor-1 was broken in that snap; I was noticing strage connection > > > > > hangs to some sites. They went away when I disabled it. > > > > > > > > Predictor-1 compression hasn't changed. Have you tried disabling TCP > > > > extensions ? If this doesn't work, you'll need to supply some more > > > > information. > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > What's on the other side of the link ? What do your logs say ? What > > do your config files look like ? How are you starting ppp ? Are the > > ``connection hangs'' consistent (always when downloading specific > > data) ? > > It only happened while hitting certain sites, I notice. www.freebsd.org, > slashdot.org, and www.m-w.com were doing it, as was using the command-line > whois (which hung after "Registrant:"). No other sites were afffected, to my > knowledge... > > As for my config, here goes: > > default: > set speed 115200 > set device /dev/cuaa1 > set ctsrts on > alias enable yes > alias unregistered_only yes > set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATZ OK-AT-OK \\dATDT\\T TIMEOUT 40 CONNECT" > set timeout 0 > set redial 30 > disable lqr > deny lqr > disable pred1 > deny pred1 > #disable vjcomp > #deny vjcomp > set log Phase Chat Connect Link LCP IPCP CCP tun > tidalwave: > set mtu 576 > set phone "690-0006|392-0477:758-8993" > set login "TIMEOUT 30 ogin:-\\r-ogin: lcremean word: " > set ifaddr 0 208.0.0.0/8 > > > -- > Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) > A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did > $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net > FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) > My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code > -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 1 07:50:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17541 for freebsd-current-outgoing; Sat, 1 Aug 1998 07:50:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from NIH2WAAE (smtp5.site1.csi.com [149.174.183.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17536 for ; Sat, 1 Aug 1998 07:50:54 -0700 (PDT) (envelope-from derm@iol.ie) Received: from mail pickup service by csi.com with Microsoft SMTPSVC; Sat, 1 Aug 1998 10:50:47 -0400 Received: from md26-243.mun.compuserve.com (md26-243.mun.compuserve.com [195.232.45.243]) by hil-img-ims-1.compuserve.com (8.8.6/8.8.6/IMS-1.4) with SMTP id KAA17390; Sat, 1 Aug 1998 10:50:09 -0400 (EDT) From: derm@iol.ie (Dermot McNally) To: freebsd-current@FreeBSD.ORG Cc: Mike Smith Subject: Re: Problems with ed driver (PCI) Date: Sat, 01 Aug 1998 14:50:08 GMT Organization: My House Message-ID: <35c32aa4.2583703@mail.compuserve.com> References: <199808010528.WAA00378@antipodes.cdrom.com> In-Reply-To: <199808010528.WAA00378@antipodes.cdrom.com> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id HAA17537 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 31 Jul 1998 22:28:28 -0700, Mike Smith wrote: >Sounds more like a BIOS issue. Try altering the "PnP OS installed" >setting and see what happens. Well, that cured it. Funny, I could have sworn I'd tried that too... Thanks for the help, guys, it all works fine now. Dermot ----------------------------------------------------------- Dermot McNally, derm@iol.ie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 1 10:29:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00533 for freebsd-current-outgoing; Sat, 1 Aug 1998 10:29:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00526 for ; Sat, 1 Aug 1998 10:29:39 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id MAA06329; Sat, 1 Aug 1998 12:27:20 -0400 (EDT) Date: Sat, 1 Aug 1998 12:27:20 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: John Polstra cc: current@FreeBSD.ORG Subject: Re: /usr/lib/aout In-Reply-To: <199807310429.VAA01919@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Jul 1998, John Polstra wrote: > In article , > Chuck Robey wrote: > > > That approach would undoubtedly work, but when things move over to elf, > > I hope important stuff like ssh doesn't do straight down the tubes. I > > can't figure out why it wants /usr/lib/libc, but I can sure verify that > > it does. > > I've never seen this. I just now built the ssh port on a -current > system from July 24, without any problems at all. There is nothing in > /usr/lib except the "aout" and "compat" subdirectories. I wasn't suggesting it's a bug (I didn't track it down well enough when I experienced it), I was saying that trying to solve it by bogusly copying libs around would mean that you'd be more likely to get bitten by the still-existing problem on your system, when we moved to elf. That'd be because the libs in /usr/lib would then be elf, and ssh would still be trying to use the aout libs (unless you freshly recompiled it). The fix would be really making it look at /usr/lib/aout for libc (which mine does), not copying the up to date libc from /usr/lib/aout to /usr/lib. In other words, find the real problem, don't mask it. > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 1 11:35:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06909 for freebsd-current-outgoing; Sat, 1 Aug 1998 11:35:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-asfm08--190.sirius.net [205.134.241.190]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06902 for ; Sat, 1 Aug 1998 11:35:12 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.8.8/8.8.8) with ESMTP id LAA00561 for ; Sat, 1 Aug 1998 11:35:04 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199808011835.LAA00561@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Netatalk name-registering problem with -current X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Aug 1998 11:35:04 -0700 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having some trouble with netatalk which works fine under -stable but appears to not work correctly under -current (at least for me). I recently added a second PII processor and another 128Mb RAM (total 256Mb), and upgraded to -current so I could turn on SMP and softupdates. This much went fine, and most of the old binaries work too. (I had to rebuild some ports that accessed /var/run/utmp but otherwise the machine is running fine.) The machine has one SMC DEC ethernet card. Anyway, I rebuilt and reinstalled netatalk just to be sure. I also made sure I have the latest sources for both -current and netatalk (as well as its port) as of last night (July 31). atalkd runs and appears to be happy. I verified that the patches for -current (mentioned earlier on the mailing list) were indeed installed correctly. For some reason no servers appear to be able to register any names: $ nbprgstr -p 4 pinhead:Workstation nbp_rgstr: Operation timed out Can't register pinhead:Workstation@* $ nbplkup HP LaserJet 5P:SNMP Agent 65281.245:8 HP LaserJet 5P:LaserWriter 65281.245:158 $ That's all that's on my local network right now as the Macs are turned off. The afpd and papd daemons also get timeouts trying to register and fail to start up. nbplkup works though, and netstat shows this, if it helps: AppleTalk: Destination Gateway Flags Refs Use Netif Expire 0 0.0 U 0 0 lo0 => 0-32767 65280.253 U 0 0 de0 32768-49151 65280.253 U 0 0 de0 49152-57343 65280.253 U 0 0 de0 57344-61439 65280.253 U 0 0 de0 61440-63487 65280.253 U 0 0 de0 63488-64511 65280.253 U 0 0 de0 64512-65023 65280.253 U 0 0 de0 65024-65279 65280.253 U 0 0 de0 65280-65407 65280.253 U 0 0 de0 65280.253 0.0 UH 0 0 de0 65408-65471 65280.253 U 0 0 de0 65472-65503 65280.253 U 0 0 de0 65504-65519 65280.253 U 0 0 de0 65520-65527 65280.253 U 0 0 de0 65528-65531 65280.253 U 0 0 de0 65532-65533 65280.253 U 0 0 de0 I would like to know if anyone is running netatalk on the latest -current and if anyone has seen a problem like this, or if I'm on the bleeding edge and get to debug it myself. I don't think it's a configuration problem since I blew away the auto-created /usr/local/etc/atalk.conf, but it didn't make any difference. Thanks in advance! (dmesg output appended below if it is of any help) -- Parag Patel Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #5: Fri Jul 31 23:06:22 PDT 1998 root@pinhead.parag.codegen.com:/usr/src/sys/compile/PINHEAD Timecounter "i8254" frequency 1193182 Hz cost 3044 ns CPU: Pentium II (686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80fbff real memory = 268435456 (262144K bytes) avail memory = 258527232 (252468K bytes) FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x01 on pci0.4.0 ide_pci0: rev 0x01 on pci0.4.1 chip3: rev 0x01 int d irq 12 on pci0.4.2 chip4: rev 0x01 on pci0.4.3 ahc0: rev 0x00 int a irq 19 on pci0.6.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 4134MB (8467200 512 byte sectors) ahc0:A:1: refuses WIDE negotiation. Using 8bit transfers sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 3067MB (6281856 512 byte sectors) de0: rev 0x12 int a irq 17 on pci0.11.0 de0: SMC 9332DST 21140 [10-100Mb/s] pass 1.2 de0: address 00:00:c0:7e:df:e4 de0: enabling 10baseT port Probing for devices on PCI bus 1: vga0: rev 0x00 int a irq 16 on pci1.0.0 Probing for PnP devices: CSN 1 Vendor ID: CTL00e4 [0xe4008c0e] Serial 0x08de2f0a pcm1 (SB16pnp sn 0x08de2f0a) at 0x220-0x22f irq 10 drq 1 flags 0x15 on isa Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> pcm0 not probed due to drq conflict with pcm1 at 1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 5 on isa sio2: type 16550A sio3 at 0x2e8-0x2ef irq 9 on isa sio3: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 at 0x278-0x27f on isa psm0 not found at 0x60 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (atapi): , removable, accel, ovlap, dma, iordis wcd0: 5512Kb/sec, 256Kb cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked joy0 at 0x201 on isa joy0: joystick joy1 not probed due to I/O address conflict with joy0 at 0x201 npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 changing root device to sd0s2a SMP: AP CPU #1 Launched! ffs_mountfs: superblock updated ffs_mountfs: superblock updated To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 1 11:49:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08249 for freebsd-current-outgoing; Sat, 1 Aug 1998 11:49:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08242 for ; Sat, 1 Aug 1998 11:49:03 -0700 (PDT) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.8.8/8.8.7) id OAA05372; Sat, 1 Aug 1998 14:45:55 -0400 (EDT) (envelope-from lee) Message-ID: <19980801144555.A5316@st-lcremean.tidalwave.net> Date: Sat, 1 Aug 1998 14:45:55 -0400 From: Lee Cremeans To: Brian Somers , lcremean@tidalwave.net Cc: current@FreeBSD.ORG Subject: Re: Identd problems on -current of 980724 Reply-To: lcremean@tidalwave.net References: <19980801004039.A790@st-lcremean.tidalwave.net> <199808011230.NAA15775@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199808011230.NAA15775@awfulhak.org>; from Brian Somers on Sat, Aug 01, 1998 at 01:30:00PM +0100 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Aug 01, 1998 at 01:30:00PM +0100, Brian Somers wrote: > Does it make any difference if you remove the ``set mtu'' ? Yes, it does. Removing all refs to "set mtu" and "pred1" make things work. I wonder why that is... -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 1 13:03:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17089 for freebsd-current-outgoing; Sat, 1 Aug 1998 13:03:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17084 for ; Sat, 1 Aug 1998 13:03:21 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA28569; Sat, 1 Aug 1998 13:01:50 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdB28566; Sat Aug 1 20:01:40 1998 Date: Sat, 1 Aug 1998 13:01:38 -0700 (PDT) From: Julian Elischer To: Parag Patel cc: current@FreeBSD.ORG Subject: Re: Netatalk name-registering problem with -current In-Reply-To: <199808011835.LAA00561@pinhead.parag.codegen.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG yes there is a problem with -current and netatalk name registration. it's on my list of things to look at.. there are two suspicious areas.. loopback of ddp packets and loopback of ddp mulitcast packets. both these areas were hacked in -current and the associated changes in netatalk were not really tested fully. julian On Sat, 1 Aug 1998, Parag Patel wrote: > > I'm having some trouble with netatalk which works fine under -stable but appears to not work correctly under -current (at least for me). > > I recently added a second PII processor and another 128Mb RAM (total 256Mb), and upgraded to -current so I could turn on SMP and softupdates. This much went fine, and most of the old binaries work too. (I had to rebuild some ports that accessed /var/run/utmp but otherwise the machine is running fine.) The machine has one SMC DEC ethernet card. > > Anyway, I rebuilt and reinstalled netatalk just to be sure. I also made sure I have the latest sources for both -current and netatalk (as well as its port) as of last night (July 31). > > atalkd runs and appears to be happy. I verified that the patches for -current (mentioned earlier on the mailing list) were indeed installed correctly. For some reason no servers appear to be able to register any names: > > $ nbprgstr -p 4 pinhead:Workstation > nbp_rgstr: Operation timed out > Can't register pinhead:Workstation@* > $ nbplkup > HP LaserJet 5P:SNMP Agent 65281.245:8 > HP LaserJet 5P:LaserWriter 65281.245:158 > $ > > That's all that's on my local network right now as the Macs are turned off. > > The afpd and papd daemons also get timeouts trying to register and fail to start up. nbplkup works though, and netstat shows this, if it helps: > > AppleTalk: > Destination Gateway Flags Refs Use Netif Expire > 0 0.0 U 0 0 lo0 => > 0-32767 65280.253 U 0 0 de0 > 32768-49151 65280.253 U 0 0 de0 > 49152-57343 65280.253 U 0 0 de0 > 57344-61439 65280.253 U 0 0 de0 > 61440-63487 65280.253 U 0 0 de0 > 63488-64511 65280.253 U 0 0 de0 > 64512-65023 65280.253 U 0 0 de0 > 65024-65279 65280.253 U 0 0 de0 > 65280-65407 65280.253 U 0 0 de0 > 65280.253 0.0 UH 0 0 de0 > 65408-65471 65280.253 U 0 0 de0 > 65472-65503 65280.253 U 0 0 de0 > 65504-65519 65280.253 U 0 0 de0 > 65520-65527 65280.253 U 0 0 de0 > 65528-65531 65280.253 U 0 0 de0 > 65532-65533 65280.253 U 0 0 de0 > > > I would like to know if anyone is running netatalk on the latest -current and if anyone has seen a problem like this, or if I'm on the bleeding edge and get to debug it myself. I don't think it's a configuration problem since I blew away the auto-created /usr/local/etc/atalk.conf, but it didn't make any difference. > > Thanks in advance! (dmesg output appended below if it is of any help) > > > -- Parag Patel > > > Copyright (c) 1992-1998 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.0-CURRENT #5: Fri Jul 31 23:06:22 PDT 1998 > root@pinhead.parag.codegen.com:/usr/src/sys/compile/PINHEAD > Timecounter "i8254" frequency 1193182 Hz cost 3044 ns > CPU: Pentium II (686-class CPU) > Origin = "GenuineIntel" Id = 0x634 Stepping=4 > Features=0x80fbff > real memory = 268435456 (262144K bytes) > avail memory = 258527232 (252468K bytes) > FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 > cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > Probing for devices on PCI bus 0: > chip0: rev 0x03 on pci0.0.0 > chip1: rev 0x03 on pci0.1.0 > chip2: rev 0x01 on pci0.4.0 > ide_pci0: rev 0x01 on pci0.4.1 > chip3: rev 0x01 int d irq 12 on pci0.4.2 > chip4: rev 0x01 on pci0.4.3 > ahc0: rev 0x00 int a irq 19 on pci0.6.0 > ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs > ahc0: waiting for scsi devices to settle > scbus0 at ahc0 bus 0 > sd0 at scbus0 target 0 lun 0 > sd0: type 0 fixed SCSI 2 > sd0: Direct-Access 4134MB (8467200 512 byte sectors) > ahc0:A:1: refuses WIDE negotiation. Using 8bit transfers > sd1 at scbus0 target 1 lun 0 > sd1: type 0 fixed SCSI 2 > sd1: Direct-Access 3067MB (6281856 512 byte sectors) > de0: rev 0x12 int a irq 17 on pci0.11.0 > de0: SMC 9332DST 21140 [10-100Mb/s] pass 1.2 > de0: address 00:00:c0:7e:df:e4 > de0: enabling 10baseT port > Probing for devices on PCI bus 1: > vga0: rev 0x00 int a irq 16 on pci1.0.0 > Probing for PnP devices: > CSN 1 Vendor ID: CTL00e4 [0xe4008c0e] Serial 0x08de2f0a > pcm1 (SB16pnp sn 0x08de2f0a) at 0x220-0x22f irq 10 drq 1 flags 0x15 on isa > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > pcm0 not probed due to drq conflict with pcm1 at 1 > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > sio2 at 0x3e8-0x3ef irq 5 on isa > sio2: type 16550A > sio3 at 0x2e8-0x2ef irq 9 on isa > sio3: type 16550A > lpt0 at 0x378-0x37f irq 7 on isa > lpt0: Interrupt-driven port > lp0: TCP/IP capable interface > lpt1 at 0x278-0x27f on isa > psm0 not found at 0x60 > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (atapi): , removable, accel, ovlap, dma, iordis > wcd0: 5512Kb/sec, 256Kb cache, audio play, 255 volume levels, ejectable tray > wcd0: no disc inside, unlocked > joy0 at 0x201 on isa > joy0: joystick > joy1 not probed due to I/O address conflict with joy0 at 0x201 > npx0 on motherboard > npx0: INT 16 interface > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: routing 8254 via pin 2 > changing root device to sd0s2a > SMP: AP CPU #1 Launched! > ffs_mountfs: superblock updated > ffs_mountfs: superblock updated > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 1 14:35:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23928 for freebsd-current-outgoing; Sat, 1 Aug 1998 14:35:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23913 for ; Sat, 1 Aug 1998 14:34:58 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA07345; Sat, 1 Aug 1998 14:34:44 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd007312; Sat Aug 1 14:34:38 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id OAA25705; Sat, 1 Aug 1998 14:34:34 -0700 (MST) From: Terry Lambert Message-Id: <199808012134.OAA25705@usr07.primenet.com> Subject: Re: flock(2) problem & fix To: green@zone.syracuse.NET (Brian Feldman) Date: Sat, 1 Aug 1998 21:34:33 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, freebsd-current@FreeBSD.ORG In-Reply-To: from "Brian Feldman" at Aug 1, 98 01:37:40 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think you're right, if nothing than for the fact that it's already the > norm. This is the first time I've ever done kernel hacking, but I've > tested the patch and made a final version of it, a correction of syntax, > but it shouldn't be used because it breaks what you think it would, like > apache, which have been using flocking wrong since the very beginning. But > anyway, I'll post the correct patch, just because I don't want my > dain-bramaged code floating around ;) I've corrected code that didn't do what was supposed to be done simply to have it out there as a corrected reference, too. 8-). The real issue here is not brain damage on your part. It's more like POSIX/UNIX lawyering. A long time ago, before people had source code to kernels, writing application software was very much like team ice-fishing. You'd go to the thickly iced-over lake (the kernel/user system call barrier) and saw holes at the thinnest spots (the system calls themselves). Then you would drop a fishing line down the most likely hole, and using boathooks in all of the remaining holes, you'd try to move the hook around until it was in front of the fish. The point is that what a kernel's system call interface strictly provides, and what an apllication needs from a kernel in order to do what it has to do, are frequently very different things, and in the end, the kernel is there to serve application requests. This is, perhaps, the most important thing about Open Source Software today: until now, application vendors have been fairly restricted in what they could ask a kernel to do on their behalf. No more; for a dire need, the applicaiton developer can change the kernel. For a much less dire need, an application developer of an embedded application can blur the line between the kernel and the application, as necessary, to get an efficient soloution. This is probably why the Windows platforms have taken off. The use of DLL's and VxD's allow the application programmer to treat the OS as if it were an embedded system, whose only purpose is to do whatever is necessary on behalf of supporting their application. The downside is that you get bad interactions if people are allowed to change interfaces at will. Harmonics. Welcome to Tacoma Narrows. To get back to ice fishing, it's like having a lake where you can make as many holes as you want without regulation, but where you have to use the same hole someone else is using if you want to catch the same type of fish they just caught. It's very easy for your line to become tangled in another if everyone fishes in the same hole at the same time. I guess what you did was build an ice fishing shack over a hole, open the door to go inside and start fishing, only to find an old fart already in there, who says "Hey, didn't you see me standing here with this boat hook?". He then gestures to several nearby holes, where there are other guys with boat hooks, and one guy with a fishing rod and complains, "Me and my buddies are fishing!". If nothing else, this should give you a better understanding when us old farts point at a new hole someone is cutting and say "You don't need to do that. See those four holes? Take your fishing rod over to that one, there, then take three boat hooks to the others, then all's ya gotta do...". 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 1 16:11:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01846 for freebsd-current-outgoing; Sat, 1 Aug 1998 16:11:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01833 for ; Sat, 1 Aug 1998 16:11:43 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id BAA09748 for ; Sun, 2 Aug 1998 01:16:24 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sun, 2 Aug 1998 01:16:24 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: DEVFS and console Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm unable to log in on console when I use DEVFS-enabled kernel. syslog says: LOGIN root REFUSED (NOROOT) ON TTY vga I always thought 'vga' is an output device... :-)). Anyway, adding a line: vga none cons25 off secure to /etc/ttys helps to get around this... Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 1 17:21:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08144 for freebsd-current-outgoing; Sat, 1 Aug 1998 17:21:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay1.aha.ru (relay1.aha.ru [195.2.83.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08139 for ; Sat, 1 Aug 1998 17:21:32 -0700 (PDT) (envelope-from osa@serv.etrust.ru) Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112]) by relay1.aha.ru (8.9.1/aha-r/0.04B) with ESMTP id EAA21715 for ; Sun, 2 Aug 1998 04:21:19 +0400 (MSD) Received: by sunny.aha.ru id EAA01630; (8.8.8/vak/1.9) Sun, 2 Aug 1998 04:20:19 +0400 (MSD) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma001604; Sun Aug 2 04:19:59 1998 Received: by serv.etrust.ru id EAA18943; (8.9.1/vak/1.9) Sun, 2 Aug 1998 04:22:59 +0400 (MSD) Date: Sun, 2 Aug 1998 04:22:59 +0400 (MSD) From: osa@serv.etrust.ru (Sergey A. Osokin) Message-Id: <199808020022.EAA18943@serv.etrust.ru> To: current@FreeBSD.ORG Subject: Sendmail-8.9.1 in -current & in 3.0-RELEASE??? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Does sendmail-8.9.1 containes in last -current version or in feature 3.0-RELEASE ? Rgdz, oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 1 17:53:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10685 for freebsd-current-outgoing; Sat, 1 Aug 1998 17:53:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10678 for ; Sat, 1 Aug 1998 17:53:26 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA05190; Sat, 1 Aug 1998 17:51:10 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdOv5188; Sun Aug 2 00:51:05 1998 Date: Sat, 1 Aug 1998 17:51:02 -0700 (PDT) From: Julian Elischer To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG Subject: Re: DEVFS and console In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG this is because vga is a link to ttyv0 and it comes first in the device database or whatever 'tty' uses to figure out what you are on.. I'm not sure who added it, but it gets me here too. Ohowever my ttys has a line for iI think I must have added it and since forgotten that I did it. not sure what teh answer is, but the same would happen without devfs if vga was a link to ttyv0. On Sun, 2 Aug 1998, Andrzej Bialecki wrote: > Hi, > > I'm unable to log in on console when I use DEVFS-enabled kernel. syslog > says: > > LOGIN root REFUSED (NOROOT) ON TTY vga > > I always thought 'vga' is an output device... :-)). Anyway, adding a line: > > vga none cons25 off secure > > to /etc/ttys helps to get around this... > > > Andrzej Bialecki > > +---------------------+------------------------+--------------------------+ > | | When in problem or in | if(halt_per_mth > 0) { | > | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | > | Network in Poland | scream and shout. | } | > + --------------------+------------------------+--------------------------+ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 1 18:49:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15529 for freebsd-current-outgoing; Sat, 1 Aug 1998 18:49:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15522 for ; Sat, 1 Aug 1998 18:49:17 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id DAA18103; Sun, 2 Aug 1998 03:53:52 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sun, 2 Aug 1998 03:53:52 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Julian Elischer cc: freebsd-current@FreeBSD.ORG Subject: Re: DEVFS and console In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 1 Aug 1998, Julian Elischer wrote: > this is because vga is a link to ttyv0 > and it comes first in the device database or whatever 'tty' uses to > figure out what you are on.. > > I'm not sure who added it, but it gets me here too. > Ohowever my ttys has a line for iI think I must have added it and since > forgotten that I did it. > > not sure what teh answer is, but the same would happen without devfs > if vga was a link to ttyv0. As I wrote, I kind of worked around it, but it looks stupid when it says that I'm logged in on 'vga'... Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 1 21:18:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28318 for freebsd-current-outgoing; Sat, 1 Aug 1998 21:18:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28312 for ; Sat, 1 Aug 1998 21:18:45 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id MAA21585; Sun, 2 Aug 1998 12:18:17 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199808020418.MAA21585@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: osa@serv.etrust.ru (Sergey A. Osokin) cc: current@FreeBSD.ORG Subject: Re: Sendmail-8.9.1 in -current & in 3.0-RELEASE??? In-reply-to: Your message of "Sun, 02 Aug 1998 04:22:59 +0400." <199808020022.EAA18943@serv.etrust.ru> Date: Sun, 02 Aug 1998 12:18:16 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sergey A. Osokin wrote: > Hello! > Does sendmail-8.9.1 containes in last -current version or in > feature 3.0-RELEASE ? > > Rgdz, > oZZ, > osa@etrust.ru Yes, It will be imported within the next 12 hours. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message