From owner-freebsd-current Sun Feb 28 1:20:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id DD2D4151FE for ; Sun, 28 Feb 1999 01:20:16 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id BAA18967 for freebsd-current@FreeBSD.ORG; Sun, 28 Feb 1999 01:20:00 -0800 (PST) (envelope-from obrien) Date: Sun, 28 Feb 1999 01:20:00 -0800 From: "David O'Brien" To: freebsd-current@FreeBSD.ORG Subject: Re: gcc Message-ID: <19990228012000.A84165@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19877.920165128@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19877.920165128@zippy.cdrom.com>; from Jordan K. Hubbard on Sat, Feb 27, 1999 at 05:25:28PM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Peter was working on it, but I strongly suspect he won't have time to > even think about this in the very near future Personally, I'm slowly working on putting the FreeBSD GCC changes into EGCS 1.1.1 so it can compile our sources. I've got the compiler contribed and am working on the contrib of libstdc++. I will share my local CVS tree with anyone that wants to help out. > It would probably be cool to find out what the last set of issues he > identified and/or fixed with this was though. Agreed. Peter is being quite quiet on this subject. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 1:33:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 46AC8151E5 for ; Sun, 28 Feb 1999 01:33:52 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA47143; Sun, 28 Feb 1999 09:32:51 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 28 Feb 1999 09:32:51 +0000 (GMT) From: Doug Rabson To: "Jordan K. Hubbard" Cc: Warner Losh , Chuck Robey , freebsd-current@freebsd.org Subject: Re: gcc In-Reply-To: <20655.920182749@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 27 Feb 1999, Jordan K. Hubbard wrote: > > I for one would love to see 2.8.1 or newer in the tree for my own, > > selfish reasons. Many ports (new architectures) would benefit from > > this. > > Is that to say that you prefer it over egcs 1.1.1? If so, why? I have found egcs to be slightly better at C++ code (for my own projects anyway). I believe that it may produce better code too but I don't have any real evidence. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 2:50: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id B33CC151EE for ; Sun, 28 Feb 1999 02:49:55 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:VozRfACkxHAXDyoQrtL5HqLiaoOjT9cS@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id MAA63242; Sun, 28 Feb 1999 12:49:33 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:a0up3BpgvBieK7mIjZvIo1tWffEw+NfV@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id MAA33965; Sun, 28 Feb 1999 12:49:31 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199902281049.MAA33965@greenpeace.grondar.za> To: obrien@NUXI.com Cc: freebsd-current@freebsd.org Subject: Re: gcc In-Reply-To: Your message of " Sun, 28 Feb 1999 01:20:00 PST." <19990228012000.A84165@relay.nuxi.com> References: <19877.920165128@zippy.cdrom.com> <19990228012000.A84165@relay.nuxi.com> Date: Sun, 28 Feb 1999 12:49:29 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" wrote: > > Peter was working on it, but I strongly suspect he won't have time to > > even think about this in the very near future > > Personally, I'm slowly working on putting the FreeBSD GCC changes into > EGCS 1.1.1 so it can compile our sources. Hmm... Does it not make more sense to slowly remove the FreeBSD'ism that require that we futz with the compiler? > I've got the compiler contribed and am working on the contrib of > libstdc++. I will share my local CVS tree with anyone that wants to help > out. Me, please! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 2:54:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8B40514ED2 for ; Sun, 28 Feb 1999 02:54:55 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id CAA04737; Sun, 28 Feb 1999 02:53:06 -0800 (PST) (envelope-from obrien) Date: Sun, 28 Feb 1999 02:53:06 -0800 From: "David O'Brien" To: Mark Murray Cc: freebsd-current@freebsd.org Subject: Re: gcc Message-ID: <19990228025306.A4140@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19877.920165128@zippy.cdrom.com> <19990228012000.A84165@relay.nuxi.com> <199902281049.MAA33965@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199902281049.MAA33965@greenpeace.grondar.za>; from Mark Murray on Sun, Feb 28, 1999 at 12:49:29PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm... Does it not make more sense to slowly remove the FreeBSD'ism > that require that we futz with the compiler? I don't think bde, et. al. is going to let -fformat-extensions go away. :-) -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 3:19:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 4DFE8152AC for ; Sun, 28 Feb 1999 03:18:32 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:jAF5ZicbAoMNrcf6eQc9yk0vOJQL+VEb@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id NAA63290; Sun, 28 Feb 1999 13:18:10 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:8GAqmm7BIvM016l2i0c7ZpQ1t1/qQSdC@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id NAA34426; Sun, 28 Feb 1999 13:17:52 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199902281117.NAA34426@greenpeace.grondar.za> To: obrien@NUXI.com Cc: freebsd-current@freebsd.org Subject: Re: gcc In-Reply-To: Your message of " Sun, 28 Feb 1999 02:53:06 PST." <19990228025306.A4140@relay.nuxi.com> References: <19877.920165128@zippy.cdrom.com> <19990228012000.A84165@relay.nuxi.com> <199902281049.MAA33965@greenpeace.grondar.za> <19990228025306.A4140@relay.nuxi.com> Date: Sun, 28 Feb 1999 13:17:42 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" wrote: > > Hmm... Does it not make more sense to slowly remove the FreeBSD'ism > > that require that we futz with the compiler? > > I don't think bde, et. al. is going to let -fformat-extensions go away. :-) Then can't we get that put into "mainstream" gcc/egcs? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 3:36:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 8B4C515208 for ; Sun, 28 Feb 1999 03:36:41 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id GAA75321; Sun, 28 Feb 1999 06:34:46 -0500 (EST) Date: Sun, 28 Feb 1999 06:34:46 -0500 (EST) From: Chuck Robey To: "Jordan K. Hubbard" Cc: Warner Losh , freebsd-current@FreeBSD.ORG Subject: Re: gcc In-Reply-To: <20655.920182749@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 27 Feb 1999, Jordan K. Hubbard wrote: > > I for one would love to see 2.8.1 or newer in the tree for my own, > > selfish reasons. Many ports (new architectures) would benefit from > > this. > > Is that to say that you prefer it over egcs 1.1.1? If so, why? I was a little surprised at the egcs thing myself. While I (along with probably everyone else) thinks that egcs is more advanced, it's also had the bugs that go along with being leading edge. Since FreeBSD's extremely conservative attitude towards changing our compiler is very nearly legendary, well, to be willing to jump towards the bleeding edge suprised me. If there really exists the political will to move us to egcs, this might be a good thing. The code is very definitely better, and moving us towards egcs will make a later upgrade to an even newer egcs somewhat easier, perhaps. More importantly, it's going to make the egcs writers take notice, and have a bit more receptive attitude towards accepting patches from us for the "FreeBSD" port ... possibly REALLY easing the upgrade path. My own personal experience is that the egcs people read and react to trouble reports ... I've sent them in to the gcc authors in the past, but never seen any changes from them, like I did from egcs. ----------------------------+----------------------------------------------- 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 picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 3:37: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 3E9DC15211 for ; Sun, 28 Feb 1999 03:36:56 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id WAA20392; Sun, 28 Feb 1999 22:36:38 +1100 Date: Sun, 28 Feb 1999 22:36:38 +1100 From: Bruce Evans Message-Id: <199902281136.WAA20392@godzilla.zeta.org.au> To: mark@grondar.za, obrien@NUXI.com Subject: Re: gcc Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > Hmm... Does it not make more sense to slowly remove the FreeBSD'ism >> > that require that we futz with the compiler? >> >> I don't think bde, et. al. is going to let -fformat-extensions go away. :-) > >Then can't we get that put into "mainstream" gcc/egcs? Because extensions are extensions of the mainstream gcc/egcs, by definition. Format extensions that belong in the mainstream version aren't controlled by -fformat-extensions. E.g., the __printf0__ attribute. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 4:14: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id EFD75151F0 for ; Sun, 28 Feb 1999 04:13:55 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA22562 for current@freebsd.org; Sun, 28 Feb 1999 23:13:37 +1100 Date: Sun, 28 Feb 1999 23:13:37 +1100 From: Bruce Evans Message-Id: <199902281213.XAA22562@godzilla.zeta.org.au> To: current@freebsd.org Subject: tail /proc/map/* Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG tail(1) assumes that mmap(2) works on works on regular files. mmap(2) on the irregular regular files /proc/*/map returns success but doesn't work. The first access to the mmapped memory usually causes the kernel to printf messages like the following: vnode_pager: *** WARNING *** stale FS getpages No strategy for buffer at 0xf12828e8 : 0xf3877800: type VREG, usecount 4, writecount 0, refcount 0, flags (VOBJBUF) tag VT_PROCFS, type 11, pid 591, mode 124, flags 0 : 0xf3877800: type VREG, usecount 4, writecount 0, refcount 0, flags (VOBJBUF) tag VT_PROCFS, type 11, pid 591, mode 124, flags 0 vnode_pager_getpages: I/O read error vm_fault: pager read error, pid 2023 (tail) pid 2023 (tail), uid 15: exited on signal 11 Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 4:30:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 0833915207 for ; Sun, 28 Feb 1999 04:29:51 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id NAA10222 for freebsd-current@FreeBSD.ORG; Sun, 28 Feb 1999 13:29:34 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 59B518704; Sun, 28 Feb 1999 13:00:13 +0100 (CET) Date: Sun, 28 Feb 1999 13:00:13 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: gcc Message-ID: <19990228130013.A8223@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: ; from Chuck Robey on Sat, Feb 27, 1999 at 08:13:00PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5098 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Chuck Robey: > I know that, back when we ran aout, our gcc was a long way changed from > the stock gnu gcc ... I'm wondering how much our gcc is changed, now, > from the gcc that is the regular GNU distribution? gcc was not that different, it was mostly the binutils chain (as, ld and all that stuff) because a.out was not supported anymore by modern versions. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 4:53:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 81AC014ED2 for ; Sun, 28 Feb 1999 04:53:15 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA24877; Sun, 28 Feb 1999 23:52:57 +1100 Date: Sun, 28 Feb 1999 23:52:57 +1100 From: Bruce Evans Message-Id: <199902281252.XAA24877@godzilla.zeta.org.au> To: current@FreeBSD.ORG, pangolin@home.com Subject: Re: lockmgr panic with mmap() Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The attached program sometimes causes a lockmgr panic. I do not think is always >did. I am running 4.0-CURRENT form Feb 19. > >The trace is: > panic lockmgr: locking against self > lockmgr > mv_map_growstack > grow_stack > trap_pfault > trap > calltrap > subyte > syscall > ... > >A command on a running image such as this usually does it, though I do not know what >conditions are neccessary: > > fincore /usr/local/netscape-4.5/communicator-4.5.bin Here is a simpler example. --- #include #include #include #include #define SIZE (32 * 1024 * 1024) int main(void) { void *p; char vec[SIZE / PAGE_SIZE]; p = malloc(SIZE); if (mincore(p, SIZE, vec) != 0) err(1, "mincore"); return (0); } --- mincore() locks the vmspace map, and initialises vec[] a byte at a time using subyte(). When vec[] is sufficiently large, it is not all in core initially and a page fault occurs in subyte(). The new stack growing code locks the vmspace map early and panics. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 7:27: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9]) by hub.freebsd.org (Postfix) with ESMTP id C300615251 for ; Sun, 28 Feb 1999 07:27:05 -0800 (PST) (envelope-from gaspode.franken.de!tanis@maulwurf.franken.de) Received: by maulwurf.franken.de via rmail with stdio id for freebsd-current@FreeBSD.ORG; Sun, 28 Feb 1999 16:26:46 +0100 (MET) (Smail-3.2 1996-Jul-4 #1 built DST-May-30) Received: (from tanis@localhost) by gaspode.franken.de (8.9.2/8.8.8) id MAA05603; Sun, 28 Feb 1999 12:31:01 +0100 (CET) (envelope-from tanis) Message-ID: <19990228123101.A5311@gaspode.franken.de> Date: Sun, 28 Feb 1999 12:31:01 +0100 From: German Tischler To: Doug Rabson Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc References: <20655.920182749@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Doug Rabson on Sun, Feb 28, 1999 at 09:32:51AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 28, 1999 at 09:32:51AM +0000, Doug Rabson wrote: > On Sat, 27 Feb 1999, Jordan K. Hubbard wrote: > > > > I for one would love to see 2.8.1 or newer in the tree for my own, > > > selfish reasons. Many ports (new architectures) would benefit from > > > this. > > > > Is that to say that you prefer it over egcs 1.1.1? If so, why? > > I have found egcs to be slightly better at C++ code (for my own projects > anyway). I believe that it may produce better code too but I don't have > any real evidence. egcs is much closer to ISO-14882 (ISO C++), that was finished AFTER gcc2.8.1 was released. So if one wants to do standard conform C++ programing, egcs is the choice at the time being. (though it also doens't implement all features of the standard yet). -- German Tischler tanis@gaspode.franken.de Apple eaten (core dumped) tanis@cip.informatik.uni-wuerzburg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 8:11: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from psf.Pinyon.ORG (ip-17-214.prc.primenet.com [207.218.17.214]) by hub.freebsd.org (Postfix) with ESMTP id C651114F00 for ; Sun, 28 Feb 1999 08:11:00 -0800 (PST) (envelope-from rcarter@psf.Pinyon.ORG) Received: from psf.Pinyon.ORG (localhost [127.0.0.1]) by psf.Pinyon.ORG (8.9.3/8.9.2) with ESMTP id JAA34678 for ; Sun, 28 Feb 1999 09:07:12 -0700 (MST) (envelope-from rcarter@psf.Pinyon.ORG) Message-Id: <199902281607.JAA34678@psf.Pinyon.ORG> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: Re: gcc In-reply-to: Your message of "Sun, 28 Feb 1999 09:32:51 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Feb 1999 09:07:12 -0700 From: "Russell L. Carter" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG %On Sat, 27 Feb 1999, Jordan K. Hubbard wrote: % %> > I for one would love to see 2.8.1 or newer in the tree for my own, %> > selfish reasons. Many ports (new architectures) would benefit from %> > this. %> %> Is that to say that you prefer it over egcs 1.1.1? If so, why? % %I have found egcs to be slightly better at C++ code (for my own projects %anyway). I believe that it may produce better code too but I don't have %any real evidence. The ACE people recommend egcs. Taken directly from ~ace/ACE-INSTALL.html: "ACE/TAO don't seem to build well with g++ 2.8.1. We routinely use g++ 2.7.2.3, egcs 1.0.2, and egcs 1.0.3, and recommend those versions. egcs 1.1.1 is reported to be OK, as well." TAO is quite an exercise for a C++ compiler, and I build it just fine on -current with the egcs in ports. Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 8:16: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 941811523C for ; Sun, 28 Feb 1999 08:15:46 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id TAA16421; Sun, 28 Feb 1999 19:06:21 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.3/8.9.1) with ESMTP id TAA00795; Sun, 28 Feb 1999 19:02:52 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199902281602.TAA00795@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: tail /proc/map/* In-reply-to: Your message of "Sun, 28 Feb 1999 23:13:37 +1100." <199902281213.XAA22562@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Feb 1999 19:02:52 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > tail(1) assumes that mmap(2) works on works on regular files. mmap(2) on > the irregular regular files /proc/*/map returns success but doesn't work. IMO, it ought to work. There should be no reason why regular files on procfs are more "irregular" than regular files on NFS. > The first access to the mmapped memory usually causes the kernel to > printf messages like the following: > > vnode_pager: *** WARNING *** stale FS getpages (Still no such messages here. I still don't run the Terry's submission that just introduced the message and spread a lot of same trivial getpages/putpages routines over the kernel... I hope to clean out all this junk some day, (when everyone will finally forget that matter ;-) The message is not quite relevant to the problem, though.) > No strategy for buffer at 0xf12828e8 > : 0xf3877800: type VREG, usecount 4, writecount 0, refcount 0, flags (VOBJBUF) > tag VT_PROCFS, type 11, pid 591, mode 124, flags 0 > : 0xf3877800: type VREG, usecount 4, writecount 0, refcount 0, flags (VOBJBUF) > tag VT_PROCFS, type 11, pid 591, mode 124, flags 0 > vnode_pager_getpages: I/O read error That is because procfs define a bogus BMAP operation, but don't define a STRATEGY operation. The BMAP operation apparently only useful to break mmap(2). After the BMAP code removed, another procfs bugs become apparent. procfs claim that /proc/*/map files are all sizeof(struct regs)( == 76) bytes length (:-|), but don't allow read only 76 bytes from the 'map' file. It confuse the vm code that conver mmap to read, but it also may confuse other things. If I change the size of the 'map' file to something larger, tail /proc/*/map output something quite reasonable. I think procfs_domap should do what requested, and should not try to guarantee "atomicity", as now: anyhow, any file may change it content between reads, not just under procfs. Also, procfs could compute 'map' file size more accurately. Apparently, such a mmap implementation has coherency problems. But I don't think that they are more difficult to solve (or more serious) than in NFS case. Dima P.S. This is the changes that allow me to see a reasonable good result from 'tail /proc/*/map'. --- procfs_vnops.c Sun Feb 28 15:33:52 1999 +++ procfs_vnops.c Sun Feb 28 17:29:22 1999 @@ -560,6 +560,12 @@ case Ptype: case Pmap: + vap->va_bytes = vap->va_size = 4096; + vap->va_nlink = 1; + vap->va_uid = procp->p_ucred->cr_uid; + vap->va_gid = procp->p_ucred->cr_gid; + break; + case Pregs: vap->va_bytes = vap->va_size = sizeof(struct reg); vap->va_nlink = 1; @@ -982,7 +988,7 @@ { &vop_abortop_desc, (vop_t *) procfs_abortop }, { &vop_access_desc, (vop_t *) procfs_access }, { &vop_advlock_desc, (vop_t *) procfs_badop }, - { &vop_bmap_desc, (vop_t *) procfs_bmap }, + /*{ &vop_bmap_desc, (vop_t *) procfs_bmap },*/ { &vop_close_desc, (vop_t *) procfs_close }, { &vop_create_desc, (vop_t *) procfs_badop }, { &vop_getattr_desc, (vop_t *) procfs_getattr }, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 8:34:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from k6n1.znh.org (unknown [207.109.235.39]) by hub.freebsd.org (Postfix) with ESMTP id C8A3D15250 for ; Sun, 28 Feb 1999 08:34:20 -0800 (PST) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.3/8.9.1) id QAA37144 for current@freebsd.org; Sun, 28 Feb 1999 16:33:15 GMT (envelope-from zach) Message-ID: <19990228103315.A37048@znh.org> Date: Sun, 28 Feb 1999 10:33:15 -0600 From: Zach Heilig To: current@freebsd.org Subject: Some (a.out) world breakage... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Make world (with no -DNOAOUT or whatever that switch is), ends up like this: -------------------------------------------------------------- >>> Building legacy libraries -------------------------------------------------------------- .... (echo '#define LENGTH 20'; sed -e 's/mdX/sha/g' -e 's/MDX/SHA_/g' -e 's/SHA__/SHA_/g' /usr/src/lib/libmd/mdXhl.c) > sha0hl.c cc -O -pipe -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF -I/usr/obj/aout/usr/src/tmp/usr/include -c sha0hl.c -o sha0hl.o cc -O -pipe -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/lib/libmd/sha1c.c -o sha1c.o (echo '#define LENGTH 20'; sed -e 's/mdX/sha/g' -e 's/MDX/SHA1_/g' -e 's/SHA1__/SHA1_/g' /usr/src/lib/libmd/mdXhl.c) > sha1hl.c cc -O -pipe -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF -I/usr/obj/aout/usr/src/tmp/usr/include -c sha1hl.c -o sha1hl.o cc -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/lib/libmd/i386/sha.S -o sha.o sha1-586.s: Assembler messages: sha1-586.s:56: Error: Alignment too large: 15. assumed. *** Error code 1 Stop. Quite obviously defining ELF for the entire legacy library build, but waiting to really break in 'libmd'. I did look in the "broken" file, and noted that ALIGN was defined as 16 in the 'ELF' case, and 4 in the 'OUT' case. It looks impossible (to me) for 'OUT' to be defined while compiling that file (/usr/src/lib/libmd/i386/sha.S). I guess it's time to quit building a.out? :-) -- Zach Heilig "Americans are sensitive about their money, and since this was the first major change in the greenback in nearly 70 years, a radical redesign might have been too much for consumers to comprehend" -- John Iddings [COINage, Feb. 1999]. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 8:40: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 75C061525E for ; Sun, 28 Feb 1999 08:40:05 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id IAA09725 for ; Sun, 28 Feb 1999 08:39:46 -0800 Date: Sun, 28 Feb 1999 08:39:46 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: freebsd-current@freebsd.org Subject: still having buildworld trouble for libmd 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 cc -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/lib/libmd/i386/sha.S -o sha.o sha1-586.s: Assembler messages: sha1-586.s:56: Error: Alignment too large: 15. assumed. *** Error code 1 I have an elf i386. The build seems broken. What's up? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 8:48:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0DA1D15244 for ; Sun, 28 Feb 1999 08:48:15 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id QAA23596; Sun, 28 Feb 1999 16:47:58 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA80190; Sun, 28 Feb 1999 09:48:35 -0700 (MST) Message-Id: <199902281648.JAA80190@harmony.village.org> To: "Jordan K. Hubbard" Subject: Re: gcc Cc: Chuck Robey , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 27 Feb 1999 22:19:09 PST." <20655.920182749@zippy.cdrom.com> References: <20655.920182749@zippy.cdrom.com> Date: Sun, 28 Feb 1999 09:48:35 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20655.920182749@zippy.cdrom.com> "Jordan K. Hubbard" writes: : > I for one would love to see 2.8.1 or newer in the tree for my own, : > selfish reasons. Many ports (new architectures) would benefit from : > this. : : Is that to say that you prefer it over egcs 1.1.1? If so, why? No. I'd love to see 2.8.1 or newer. egcs 1.1.1 is newer. I'd prefer egcs, for a variety of reasons... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 8:50:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from k6n1.znh.org (unknown [207.109.235.39]) by hub.freebsd.org (Postfix) with ESMTP id 048FC152B8 for ; Sun, 28 Feb 1999 08:50:20 -0800 (PST) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.3/8.9.1) id QAA37285; Sun, 28 Feb 1999 16:48:58 GMT (envelope-from zach) Message-ID: <19990228104858.A37278@znh.org> Date: Sun, 28 Feb 1999 10:48:58 -0600 From: Zach Heilig To: mjacob@feral.com, freebsd-current@FreeBSD.ORG Subject: Re: still having buildworld trouble for libmd References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Matthew Jacob on Sun, Feb 28, 1999 at 08:39:46AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 28, 1999 at 08:39:46AM -0800, Matthew Jacob wrote: > cc -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF > -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/lib/libmd/i386/sha.S > -o sha.o > sha1-586.s: Assembler messages: > sha1-586.s:56: Error: Alignment too large: 15. assumed. > *** Error code 1 > I have an elf i386. The build seems broken. What's up? The '-DELF' bit on the command line (it's building a.out libraries). It looks to be a problem with building all "legacy" libraries (-DELF is there for the entire a.out library build). libmd specifically does not have any way of building a.out (the makefile will not add '-DOUT' to the command line). -- Zach Heilig "Americans are sensitive about their money, and since this was the first major change in the greenback in nearly 70 years, a radical redesign might have been too much for consumers to comprehend" -- John Iddings [COINage, Feb. 1999]. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 9: 0:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id BDE841501F for ; Sun, 28 Feb 1999 09:00:15 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id LAA83715; Sun, 28 Feb 1999 11:58:13 -0500 (EST) Date: Sun, 28 Feb 1999 11:58:12 -0500 (EST) From: Chuck Robey To: Matthew Jacob Cc: freebsd-current@FreeBSD.ORG Subject: Re: still having buildworld trouble for libmd 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, 28 Feb 1999, Matthew Jacob wrote: > > > cc -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF > -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/lib/libmd/i386/sha.S > -o sha.o > sha1-586.s: Assembler messages: > sha1-586.s:56: Error: Alignment too large: 15. assumed. > *** Error code 1 > > I have an elf i386. The build seems broken. What's up? I guessed from commit logs that maybe Garrett had something to do with it, and talking with him last night, I disabled the build of two assembler files via the libmd Makefile: .if (${OBJFORMAT} == "elf") <-- NEW .if exists(${MACHINE_ARCH}/sha.S) SRCS+= sha.S CFLAGS+= -DSHA1_ASM -DELF .endif .if exists(${MACHINE_ARCH}/rmd160.S) SRCS+= rmd160.S CFLAGS+= -DRMD160_ASM -DELF .endif .endif <-- NEW When this fixed things, I asked Garrett about it, because I know nothing at all about libmd or what uses libmd, but he didn't get back to me. That does fix all the rest of the buildworld. Does anyone know if this fix, only active really in the legacy build, would have negative effects? I want to do the installworld, but I'm nervous about this (I don't like doing things by accident!) ----------------------------+----------------------------------------------- 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 picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 9: 9: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 418E315268 for ; Sun, 28 Feb 1999 09:08:31 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id BAA63212; Mon, 1 Mar 1999 01:07:46 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199902281707.BAA63212@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh Cc: "Jordan K. Hubbard" , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: gcc In-reply-to: Your message of "Sun, 28 Feb 1999 09:48:35 MST." <199902281648.JAA80190@harmony.village.org> Date: Mon, 01 Mar 1999 01:07:46 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <20655.920182749@zippy.cdrom.com> "Jordan K. Hubbard" writes: > : > I for one would love to see 2.8.1 or newer in the tree for my own, > : > selfish reasons. Many ports (new architectures) would benefit from > : > this. > : > : Is that to say that you prefer it over egcs 1.1.1? If so, why? > > No. I'd love to see 2.8.1 or newer. egcs 1.1.1 is newer. I'd prefer > egcs, for a variety of reasons... > > Warner A fair bit of work as been done on getting our stuff and egcs 1.1.1 merged and into shape. I see egcs 1.1.2 appears to be on the horizon, that won't be much problem when it arrives as I expect it's pretty close to the 1.1.1 layout. The main holdups have been getting the native egcs build to do something more sensible with regards to -aout/-elf, and, if things work out, a bit better cross-compile support. (Note, the cross compile stuff doesn't work too happily with the existing bmake glue and hacks in the code.) I think I've got the threaded vs setjump/longjump exception stuff sorted out and runtime switchable based on -thread etc. I suspect libg++ is approaching "delete" material. libstdc++ comes with egcs, and a hacked up libg++ is floating around that we can probably use, but I wonder if it's time to loose it and keep just libstdc++. libg++ on it's own isn't all that useful, and would probably be better as a port for the few (if any) things that actually uses it's (non-standard) class libraries. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 9:14:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 458A715167 for ; Sun, 28 Feb 1999 09:14:52 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id JAA09837; Sun, 28 Feb 1999 09:14:31 -0800 Date: Sun, 28 Feb 1999 09:14:31 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Chuck Robey Cc: freebsd-current@FreeBSD.ORG Subject: Re: still having buildworld trouble for libmd 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 Hmm! Yes, I guess we'll wait on Garrett, but I too need to do an installworld so gratefully have borrowed your change! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 9:41:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7C4DB1526F for ; Sun, 28 Feb 1999 09:41:34 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA17134; Sun, 28 Feb 1999 09:41:17 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id JAA11998; Sun, 28 Feb 1999 09:41:16 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 28 Feb 1999 09:41:16 -0800 (PST) Message-Id: <199902281741.JAA11998@vashon.polstra.com> To: zach@uffdaonline.net Subject: Re: Some (a.out) world breakage... In-Reply-To: <19990228103315.A37048@znh.org> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990228103315.A37048@znh.org>, Zach Heilig wrote: > Make world (with no -DNOAOUT or whatever that switch is), ends up like this: > > -------------------------------------------------------------- > >>> Building legacy libraries > -------------------------------------------------------------- > > .... > > (echo '#define LENGTH 20'; sed -e 's/mdX/sha/g' -e 's/MDX/SHA_/g' -e 's/SHA__/SHA_/g' /usr/src/lib/libmd/mdXhl.c) > sha0hl.c > cc -O -pipe -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF -I/usr/obj/aout/usr/src/tmp/usr/include -c sha0hl.c -o sha0hl.o > cc -O -pipe -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/lib/libmd/sha1c.c -o sha1c.o > (echo '#define LENGTH 20'; sed -e 's/mdX/sha/g' -e 's/MDX/SHA1_/g' -e 's/SHA1__/SHA1_/g' /usr/src/lib/libmd/mdXhl.c) > sha1hl.c > cc -O -pipe -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF -I/usr/obj/aout/usr/src/tmp/usr/include -c sha1hl.c -o sha1hl.o > cc -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/lib/libmd/i386/sha.S -o sha.o > sha1-586.s: Assembler messages: > sha1-586.s:56: Error: Alignment too large: 15. assumed. > *** Error code 1 > > Stop. > > Quite obviously defining ELF for the entire legacy library build, but > waiting to really break in 'libmd'. > > I did look in the "broken" file, and noted that ALIGN was defined as 16 > in the 'ELF' case, and 4 in the 'OUT' case. It looks impossible (to me) > for 'OUT' to be defined while compiling that file > (/usr/src/lib/libmd/i386/sha.S). > > I guess it's time to quit building a.out? :-) This problem can be solved easily. Instead of ".align" the code should use ".p2align 4", which behaves the same for a.out as it does for ELF. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 10:21:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 65A611526F for ; Sun, 28 Feb 1999 10:21:29 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id NAA85646; Sun, 28 Feb 1999 13:18:50 -0500 (EST) Date: Sun, 28 Feb 1999 13:18:50 -0500 (EST) From: Chuck Robey To: John Polstra Cc: zach@uffdaonline.net, current@FreeBSD.ORG Subject: Re: Some (a.out) world breakage... In-Reply-To: <199902281741.JAA11998@vashon.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 Sun, 28 Feb 1999, John Polstra wrote: > > I did look in the "broken" file, and noted that ALIGN was defined as 16 > > in the 'ELF' case, and 4 in the 'OUT' case. It looks impossible (to me) > > for 'OUT' to be defined while compiling that file > > (/usr/src/lib/libmd/i386/sha.S). > > > > I guess it's time to quit building a.out? :-) > > This problem can be solved easily. Instead of ".align" the code > should use ".p2align 4", which behaves the same for a.out as it does > for ELF. In test, this didn't work, so I misunderstood something. I'm going to show a segment of file /usr/src/lib/libmd/i386/sha.S: gcc2_compiled.: .text .align ALIGN .globl sha1_block_x86 TYPE(sha1_block_x86,@function) sha1_block_x86: I tried changing the ".align" to ".p2align", and got this error: cc -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF -c /usr/src/lib/libmd/i386/sha.S -o sha.o /usr/tmp/ccx85357.s: Assembler messages: /usr/tmp/ccx85357.s:57: Error: Alignment too large: 15 assumed *** Error code 1 I tried changing ".align" instead to ".p2align" (in case I didn't read you literally enough) and it complained of extra arguments. BTW, in the code, ALIGN is defined earlier to be 4. Last notes: It used to break before this, only in the aout setting. Now it breaks for elf and aout. Also, the other file in ./i386, rmd160.S, has an identical problem. All this is done with the libmd Makefile as original (the fix I worked out with Garrett, to take the assembler files completely out of the aout build, I removed for this test). ----------------------------+----------------------------------------------- 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 picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 10:26:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from k6n1.znh.org (unknown [207.109.235.24]) by hub.freebsd.org (Postfix) with ESMTP id AD31615272 for ; Sun, 28 Feb 1999 10:26:48 -0800 (PST) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.3/8.9.1) id SAA36325; Sun, 28 Feb 1999 18:25:17 GMT (envelope-from zach) Message-ID: <19990228122517.A34089@znh.org> Date: Sun, 28 Feb 1999 12:25:17 -0600 From: Zach Heilig To: Chuck Robey , John Polstra Cc: zach@uffdaonline.net, current@FreeBSD.ORG Subject: Re: Some (a.out) world breakage... References: <199902281741.JAA11998@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Chuck Robey on Sun, Feb 28, 1999 at 01:18:50PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 28, 1999 at 01:18:50PM -0500, Chuck Robey wrote: > cc -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF -c > /usr/src/lib/libmd/i386/sha.S -o sha.o > /usr/tmp/ccx85357.s: Assembler messages: > /usr/tmp/ccx85357.s:57: Error: Alignment too large: 15 assumed > *** Error code 1 ... > BTW, in the code, ALIGN is defined earlier to be 4. No, because of the '-DELF', ALIGN is defined to be 16. -- Zach Heilig "Americans are sensitive about their money, and since this was the first major change in the greenback in nearly 70 years, a radical redesign might have been too much for consumers to comprehend" -- John Iddings [COINage, Feb. 1999]. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 10:27:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 0071915272 for ; Sun, 28 Feb 1999 10:27:51 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id KAA17279; Sun, 28 Feb 1999 10:27:34 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id KAA12204; Sun, 28 Feb 1999 10:27:34 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 28 Feb 1999 10:27:34 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Chuck Robey Subject: Re: Some (a.out) world breakage... Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: >> >> This problem can be solved easily. Instead of ".align" the code >> should use ".p2align 4", which behaves the same for a.out as it does >> for ELF. > > In test, this didn't work, so I misunderstood something. Yes, you did. :-) Get rid of ALIGN entirely. Change all instances of ".align ALIGN" to ".p2align 4". John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 10:57: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B306F152A2 for ; Sun, 28 Feb 1999 10:57:07 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id SAA23896; Sun, 28 Feb 1999 18:56:49 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA80787; Sun, 28 Feb 1999 11:57:05 -0700 (MST) Message-Id: <199902281857.LAA80787@harmony.village.org> To: Peter Wemm Subject: Re: gcc Cc: "Jordan K. Hubbard" , Chuck Robey , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 01 Mar 1999 01:07:46 +0800." <199902281707.BAA63212@spinner.netplex.com.au> References: <199902281707.BAA63212@spinner.netplex.com.au> Date: Sun, 28 Feb 1999 11:57:05 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199902281707.BAA63212@spinner.netplex.com.au> Peter Wemm writes: : better cross-compile support. (Note, the cross compile stuff doesn't work : too happily with the existing bmake glue and hacks in the code.) Yes. That's one of the big reasons that I'd like to see a more modern compiler. I'd love to have the ability to cross compile the entire world, and right now the main hold up is gcc. I'll be happy to work with whoever to make sure that this functionality works. Would that be you Peter? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 11: 8:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from bolero-x.rahul.net (bolero.rahul.net [192.160.13.1]) by hub.freebsd.org (Postfix) with SMTP id AFE1715272 for ; Sun, 28 Feb 1999 11:08:49 -0800 (PST) (envelope-from dhesi@rahul.net) Received: from waltz.rahul.net by bolero-x.rahul.net with SMTP id AA23100 (5.67b8/IDA-1.5 for ); Sun, 28 Feb 1999 11:08:32 -0800 Received: by waltz.rahul.net (5.67b8/jive-a2i-1.0) id AA09561; Sun, 28 Feb 1999 11:08:29 -0800 Message-Id: <199902281908.AA09561@waltz.rahul.net> To: current@FreeBSD.ORG Subject: Re: lockmgr panic with mmap() In-Reply-To: Message from Bruce Evans of Sun, 28 Feb 99 23:52:57 +1100 Date: Sun, 28 Feb 99 11:08:29 -0800 From: Rahul Dhesi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please forgive me if this is a silly question. Since bugs do happen, deadlock can occur in the kernel. Is it not possible in such cases to simply detect the deadlock, and kill one of the user processes involved in the deadlock, thus releasing one of the resources involved in the deadlock? Then you would log diagnostic information and let the system continue normally. If a user deliberately does something to deadlock the kernel, his process just gets killed and a denial-of-service attack has been averted. As I vaguely recall, VAX/VMS used to do soemthing like this if a deadlock was detected. Rahul > Date: Sun, 28 Feb 99 23:52:57 +1100 > From: Bruce Evans > To: current@FreeBSD.ORG, pangolin@home.com > Message-Id: <199902281252.XAA24877@godzilla.zeta.org.au> > Subject: Re: lockmgr panic with mmap() > >The attached program sometimes causes a lockmgr panic. I do not think is always > >did. I am running 4.0-CURRENT form Feb 19. > > > >The trace is: > > panic lockmgr: locking against self > > lockmgr > > mv_map_growstack > > grow_stack > > trap_pfault > > trap > > calltrap > > subyte > > syscall > > ... > > > >A command on a running image such as this usually does it, though I do not know what > >conditions are neccessary: > > > > fincore /usr/local/netscape-4.5/communicator-4.5.bin > > Here is a simpler example. > > --- > #include > #include > > #include > #include > > #define SIZE (32 * 1024 * 1024) > > int > main(void) > { > void *p; > char vec[SIZE / PAGE_SIZE]; > > p = malloc(SIZE); > if (mincore(p, SIZE, vec) != 0) > err(1, "mincore"); > return (0); > } > --- > > mincore() locks the vmspace map, and initialises vec[] a byte at a time > using subyte(). When vec[] is sufficiently large, it is not all in core > initially and a page fault occurs in subyte(). The new stack growing > code locks the vmspace map early and panics. > > Bruce > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 11: 9:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.atl.bellsouth.net (mail1.atl.bellsouth.net [205.152.0.28]) by hub.freebsd.org (Postfix) with ESMTP id 0F68C15272 for ; Sun, 28 Feb 1999 11:09:16 -0800 (PST) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-76-54.atl.bellsouth.net [209.214.76.54]) by mail1.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id OAA25812 for ; Sun, 28 Feb 1999 14:08:17 -0500 (EST) Received: from wghicks (localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id NAA69147 for ; Sun, 28 Feb 1999 13:58:52 -0500 (EST) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199902281858.NAA69147@bellsouth.net> To: freebsd-current@freebsd.org Subject: Re: gcc Date: Sun, 28 Feb 1999 13:58:52 -0500 From: W Gerald Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [fwd to -current] > Hi Chuck, > > I must agree with your concerns about the bleeding-edge nature of > EGCS. At Glenayre we've tried several times to move "up" to EGCS > for our embedded development efforts, only to beat a hasty retreat > back to GCC because of code generation and execution bugs in the > compiler. > > Things are improving but I'd be extremely wary of a wholesale shift > to EGCS just now. > > As an interesting side note, Joel Sherrill of the RTEMS project is a > director of the EGCS project; Even RTEMS patches the EGCS distribution (!) > > Since RTEMS is using networking code from FreeBSD, perhaps he might > be a good contact for those maintaining the FreeBSD compiler? Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 12:40:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id C81C1152D8 for ; Sun, 28 Feb 1999 12:40:36 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA39025; Sun, 28 Feb 1999 12:40:18 -0800 (PST) (envelope-from dillon) Date: Sun, 28 Feb 1999 12:40:18 -0800 (PST) From: Matthew Dillon Message-Id: <199902282040.MAA39025@apollo.backplane.com> To: Rahul Dhesi Cc: current@FreeBSD.ORG Subject: Re: lockmgr panic with mmap() References: <199902281908.AA09561@waltz.rahul.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Please forgive me if this is a silly question. : :Since bugs do happen, deadlock can occur in the kernel. : :Is it not possible in such cases to simply detect the deadlock, and kill :one of the user processes involved in the deadlock, thus releasing one :of the resources involved in the deadlock? Then you would log :diagnostic information and let the system continue normally. If a user :deliberately does something to deadlock the kernel, his process just :gets killed and a denial-of-service attack has been averted. : :As I vaguely recall, VAX/VMS used to do soemthing like this if a :deadlock was detected. : :Rahul Well, the lockmgr panic with mmap() is something that ought to be easily fixable ( by whoever did the stack changes ). There are also deadlock problems when read()ing or write()ing a file-backed mmap()'d area. Most of the deadlocks remaining in the kernel are more complex and often cannot be detected without significant new work. For example, there is no tracking of the PIDs holding shared locks, only exclusive locks. Deadlocks can occur due to chains of locks across multiple processes ( e.g. 5 or 6 or more ) that loop back in on themselves. Detecting the loop is the hard part. This is known as 'deadlock detection'. It's the same sort of deadlock detection commercial SQL databases use to implement transactions and rollback. In FreeBSD's case, the issue is somewhat more complex due to things that are not strictly locks causing deadlocks - such as a low memory condition causing a process holding an inode lock to block and then the syncer blocking on the same inode. The syncer is thus unable to run and thus unable to sync the dirty buffers clogging memory to disk. Things like that. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 13: 8:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 5A459152D4 for ; Sun, 28 Feb 1999 13:08:24 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id QAA17057 for ; Sun, 28 Feb 1999 16:06:40 -0500 (EST) Date: Sun, 28 Feb 1999 16:06:39 -0500 (EST) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: mtree stuff? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While doing yet another buildworld to check my libmd changes, I saw that a couple of odd new components seem to be added to the build, at the start of the buildworld, and also near the start of the legacy tools build. I'm not sure what's happening, but it *looks* like every target in the whole tree is being scanned, *twice*. I know that Jordan's been at mtree, and there have been some other changes ... I don't have more time right now to give, but something unusual is suddenly going on in the buildworlds. ----------------------------+----------------------------------------------- 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 picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 13:16:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 6116D152C2 for ; Sun, 28 Feb 1999 13:15:36 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA01839; Sun, 28 Feb 1999 13:15:04 -0800 (PST) (envelope-from obrien) Date: Sun, 28 Feb 1999 13:15:03 -0800 From: "David O'Brien" To: Peter Wemm Cc: Warner Losh , "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: gcc Message-ID: <19990228131503.A1563@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199902281648.JAA80190@harmony.village.org> <199902281707.BAA63212@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199902281707.BAA63212@spinner.netplex.com.au>; from Peter Wemm on Mon, Mar 01, 1999 at 01:07:46AM +0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The main holdups have been getting the native egcs build to do something > more sensible with regards to -aout/-elf, and, if things work out, a bit Work might go a bit faster if the work that has been done already would be posted somewhere. Having such an important issue being responsible on a single over-worked person is not productive. ***Like Jordan said, we get NO new install and package utils until EGCS is in the tree.*** Possibly people don't realize how much the public is interested in improved install and package tools. At a recent FreeBSD users's group meeting in San Francisco, Jordan spoke of the new progress on the new tools. I'd guess between his speal and the tons of interest and questions that came up, that the topic was discussed well over an hour. At a minium the stuff that has already been done should be added to the port. ALSO, don't forget that just getting a FreeBSD'ized EGCS is just the first step. We will have to test ``build world'' many times and I'm sure we will have to change base code to compile as we like with EGCS. The more people that are allowed to get involved with this the faster things will go. In addition, at schools it is getting harder and harder to convince people to try FreeBSD when we have a broken C++ compiler in the base system. In case some aren't aware, C++ is now part of the standard CS curriculum these days. > I suspect libg++ is approaching "delete" material. libstdc++ comes > with egcs, and a hacked up libg++ is floating around that we can > probably use, but I wonder if it's time to loose it and keep just > libstdc++. It is time to dump libg++. Once EGCS is in the tree, I'll make a port of the libg++ meant for post g++ 2.8 compilers. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 13:19:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D6623152D4 for ; Sun, 28 Feb 1999 13:19:17 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id VAA24316; Sun, 28 Feb 1999 21:19:00 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA81564; Sun, 28 Feb 1999 14:19:39 -0700 (MST) Message-Id: <199902282119.OAA81564@harmony.village.org> To: obrien@NUXI.com Subject: Re: gcc Cc: Peter Wemm , "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 28 Feb 1999 13:15:03 PST." <19990228131503.A1563@relay.nuxi.com> References: <19990228131503.A1563@relay.nuxi.com> <199902281648.JAA80190@harmony.village.org> <199902281707.BAA63212@spinner.netplex.com.au> Date: Sun, 28 Feb 1999 14:19:39 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990228131503.A1563@relay.nuxi.com> "David O'Brien" writes: : ALSO, don't forget that just getting a FreeBSD'ized EGCS is just the : first step. We will have to test ``build world'' many times and I'm sure : we will have to change base code to compile as we like with EGCS. The : more people that are allowed to get involved with this the faster things : will go. I really want to be involved in this. I'm quite keen on having a newer, cross-compile friendlier compiler in the tree. Point me at something, and I'll test it. BTW, do we need to update binutils? Or are they new enough? I know that my needs for binutils are covered by the missing bits in the current version we have in the tree. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 13:23:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (Postfix) with ESMTP id BAA8415321 for ; Sun, 28 Feb 1999 13:23:26 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.3/8.9.3) id PAA00692; Sun, 28 Feb 1999 15:23:00 -0600 (CST) (envelope-from dick) Date: Sun, 28 Feb 1999 15:23:00 -0600 From: "Richard Seaman, Jr." To: Bruce Evans Cc: current@FreeBSD.ORG, pangolin@home.com, Julian Elischer Subject: Re: lockmgr panic with mmap() Message-ID: <19990228152300.A467@tar.com> References: <199902281252.XAA24877@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=sm4nu43k4a2Rpi4c X-Mailer: Mutt 0.95.1i In-Reply-To: <199902281252.XAA24877@godzilla.zeta.org.au>; from Bruce Evans on Sun, Feb 28, 1999 at 11:52:57PM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii On Sun, Feb 28, 1999 at 11:52:57PM +1100, Bruce Evans wrote: [snip] > Here is a simpler example. > > --- > #include > #include > > #include > #include > > #define SIZE (32 * 1024 * 1024) > > int > main(void) > { > void *p; > char vec[SIZE / PAGE_SIZE]; > > p = malloc(SIZE); > if (mincore(p, SIZE, vec) != 0) > err(1, "mincore"); > return (0); > } > --- > > mincore() locks the vmspace map, and initialises vec[] a byte at a time > using subyte(). When vec[] is sufficiently large, it is not all in core > initially and a page fault occurs in subyte(). The new stack growing > code locks the vmspace map early and panics. It appears to me the potential for deadlock exists in the old grow code too, but is less likely. I've attached a patch that addresses the issue, though there is a question if this is the best solution. With the old grow code, if the map lock is already held, one of the following will be true a) the grow code doesn't get executed because the va is not in the stack region, which is equivalent to grow returning success b) the grow code returns success because there's no need to grow the region because the va is aready in the mapped region. c) the grow code returns false if the va is within the stack region and there's no room left, which normally will result in a SIGSEGV d) the grow code attempts to grow the stack via vm_map_find and will then deadlock at the vm_map_lock call With this patch, if the map lock is already held, by always returning success, cases a) and b) will be the same as before. For case c) the code will attempt to continue to execute, generally calling vm_fault, which should, I think, generate a SIGSEGV, essentially the same result as the old code, but via a different path. Case d) will now continue executing in a manner equivalent to the new case c). The question is whether there is a way to do the autogrow function if the map lock is already held. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5850 --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=vmfix Index: vm_map.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_map.c,v retrieving revision 1.152 diff -c -r1.152 vm_map.c *** vm_map.c 1999/02/24 21:26:25 1.152 --- vm_map.c 1999/02/28 20:41:25 *************** *** 663,668 **** --- 663,674 ---- int rv; int is_procstack = 0; + + #define vm_map_locked(map) lockstatus(&(map)->lock) + + if (vm_map_locked(map)) + return (KERN_SUCCESS); + vm_map_lock(map); /* If addr is already in the entry range, no need to grow.*/ --sm4nu43k4a2Rpi4c-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 13:29:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 9DA3A152CB for ; Sun, 28 Feb 1999 13:28:58 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id NAA18055; Sun, 28 Feb 1999 13:28:38 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id NAA12818; Sun, 28 Feb 1999 13:28:38 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 28 Feb 1999 13:28:38 -0800 (PST) Message-Id: <199902282128.NAA12818@vashon.polstra.com> To: imp@harmony.village.org Subject: Re: gcc In-Reply-To: <199902282119.OAA81564@harmony.village.org> References: <19990228131503.A1563@relay.nuxi.com> <199902281648.JAA80190@harmony.village.org> <199902281707.BAA63212@spinner.netplex.com.au> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199902282119.OAA81564@harmony.village.org>, Warner Losh wrote: > > BTW, do we need to update binutils? Or are they new enough? I know > that my needs for binutils are covered by the missing bits in the > current version we have in the tree. I'm pretty sure our existing binutils are fine. They're the newest GNU version, and they work OK with the egcs and gcc-2.8.1 ports. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 13:33:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat193.154.mpoweredpc.net [142.177.193.154]) by hub.freebsd.org (Postfix) with ESMTP id E24951529A for ; Sun, 28 Feb 1999 13:33:22 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.2/8.9.1) with ESMTP id RAA27086; Sun, 28 Feb 1999 17:32:08 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 28 Feb 1999 17:32:07 -0400 (AST) From: The Hermit Hacker To: "David O'Brien" Cc: Peter Wemm , Warner Losh , "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: gcc In-Reply-To: <19990228131503.A1563@relay.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Feb 1999, David O'Brien wrote: > In addition, at schools it is getting harder and harder to convince people > to try FreeBSD when we have a broken C++ compiler in the base system. In > case some aren't aware, C++ is now part of the standard CS curriculum > these days. I work as System Administrator at a Canadian University that is *totally* wired. All new students get a laptop as part of their tuition, and profs make heavy use of it. The Computer Science department's "template" is a Win95/Linux mix...and the reason has nothing to do with C++. Most of the reason revolves around hardware support...the laptops are all IBM thinkpads, and the Linux kernel is barely able to drive the ethernet card used, as well as graphics...FreeBSD didn't even stand a chance :( It should be too easy to replace the compiler after the system is installed...and shouldn't be seen as a major "hindrance"... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 13:37:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id CE0CA152C0 for ; Sun, 28 Feb 1999 13:37:14 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA01999; Sun, 28 Feb 1999 13:36:52 -0800 (PST) (envelope-from obrien) Date: Sun, 28 Feb 1999 13:36:52 -0800 From: "David O'Brien" To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc Message-ID: <19990228133652.B475@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990228131503.A1563@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from The Hermit Hacker on Sun, Feb 28, 1999 at 05:32:07PM -0400 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It should be too easy to replace the compiler after the system is > installed...and shouldn't be seen as a major "hindrance"... But as Micro$hit knows, being able to check off feature boxes is important. Here, the CS dept encourages people that own a PC to install a Unix at home (we are still 100% Unix based for classes). When I push FreeBSD, I get asked if EGCS comes with it. I say no not by default, but we have a very easy to add version of it. They say, why go through the trouble if Linux already has it by default. Same for our support people. They are the laziest and most non-computer enthusiast group I've ever seen. Path of least effort is what wins with them. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 14:19: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id DD9E5152D7 for ; Sun, 28 Feb 1999 14:18:58 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id RAA00996; Sun, 28 Feb 1999 17:17:12 -0500 (EST) Date: Sun, 28 Feb 1999 17:17:12 -0500 (EST) From: Chuck Robey To: "David O'Brien" Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc In-Reply-To: <19990228133652.B475@relay.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Feb 1999, David O'Brien wrote: > > It should be too easy to replace the compiler after the system is > > installed...and shouldn't be seen as a major "hindrance"... > > But as Micro$hit knows, being able to check off feature boxes is > important. Here, the CS dept encourages people that own a PC to install > a Unix at home (we are still 100% Unix based for classes). When I push > FreeBSD, I get asked if EGCS comes with it. I say no not by default, but > we have a very easy to add version of it. They say, why go through the > trouble if Linux already has it by default. Same for our support > people. They are the laziest and most non-computer enthusiast group I've > ever seen. Path of least effort is what wins with them. Please keep in mind that if, in our haste, we import a compiler that puts instability into FreeBSD, then we've drunk poison. The feature list won't matter, the fact that we're up to date won't matter, the fact that FreeBSD suddenly, out of the blue, became unstable is the only thing that anyone will remember. I'm not against egcs if it can be shown to be stable. I'm completely against it if it exposes FreeBSD to bugs outside our control. That's my only argument in favor of gcc28, but *please* don't disregard it. I am in CS classes too, and David's points are precisely correct, but they *aren't* the number one concern, even for a student who would *love* to have the latest compiler. Maintaining FreeBSD's exemplary reputation is my number one concern here. If it means asking certain folks (like me!) to install a port to get a particular compiler, that's then something we should view separately (not less, but separately). If David comes up with a test compiler, I want to install it, and test it myself for at least 20 buildworld/installworld&kernel/cvsup cycles. I would want at least several others to report their results too. We need to move forward *quickly* to either gcc28 or egcs, but please, don't be willing to sacrifice stability. I can do that testing with automated scripts, so it wouldn't need lots of my time, and I would do that happily. ----------------------------+----------------------------------------------- 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 picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 14:20:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from dyn02.trafford.dementia.org (dyn02.trafford.dementia.org [204.29.154.130]) by hub.freebsd.org (Postfix) with ESMTP id 1A5B5153AA; Sun, 28 Feb 1999 14:20:48 -0800 (PST) (envelope-from assar@sics.se) Received: (from assar@localhost) by dyn02.trafford.dementia.org (8.9.1/8.7.3) id XAA52722; Sun, 28 Feb 1999 23:22:37 +0100 (CET) To: Eivind Eklund Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free References: <19990223094120.A97001@hal.mpn.cp.philips.com> <199902230909.MAA01169@tejblum.dnttm.rssi.ru> <19990223105939.D97001@hal.mpn.cp.philips.com> <19990223161625.B10845@bitbox.follo.net> Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 28 Feb 1999 23:22:35 +0100 In-Reply-To: Eivind Eklund's message of "Tue, 23 Feb 1999 16:16:26 +0100" Message-ID: <5lemnaxj6c.fsf@mg.trafford.dementia.org> Lines: 21 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund writes: > > > That is, INVARIANTS in kernel incompatible with dynamic loading. > > > > Somehow this strikes me as a Bad Thing... > > It _is_ a bad thing. I've been pondering what to do with the > intrusive invariant checks - make them dependent on > INTRUSIVE_INVARIANTS, perhaps? That would still make some KLDs > incompatible with INTRUSIVE_INVARIANTS, but that is probably the best > we can do. I think that the goal should be to make KLDs work with all kinds of kernels. And the only place where this seems to be a problem is with zalloc and zfree. So it seems to me that one of the following could be done to solve it: a. make zalloc and zfree non-inline b. call zalloci and zfreei in code that can end up in KLDs c. call zalloci and zfreei everywhere where it's not performance-critical /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 14:41: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id C95E8152E2 for ; Sun, 28 Feb 1999 14:41:06 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA31126; Sun, 28 Feb 1999 14:40:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Peter Wemm Cc: Warner Losh , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: gcc In-reply-to: Your message of "Mon, 01 Mar 1999 01:07:46 +0800." <199902281707.BAA63212@spinner.netplex.com.au> Date: Sun, 28 Feb 1999 14:40:40 -0800 Message-ID: <31122.920241640@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The main holdups have been getting the native egcs build to do something > more sensible with regards to -aout/-elf, and, if things work out, a bit > better cross-compile support. (Note, the cross compile stuff doesn't work > too happily with the existing bmake glue and hacks in the code.) I think > I've got the threaded vs setjump/longjump exception stuff sorted out and > runtime switchable based on -thread etc. I'd personally be happy with an egcs that just did sensible things with ELF, though I guess a.out is a bonus(?) of sorts. Still, I just tweaked the egcs 1.1.1 configure script to replace my system compiler entirely and then built the world and kernel from it - the resulting system appears to work, provided that you comment out the compiler from the build so that it doesn't clobber itself. I think we really are probably holding this up a bit too much on the small points rather than the big ones. :) > I suspect libg++ is approaching "delete" material. libstdc++ comes with > egcs, and a hacked up libg++ is floating around that we can probably use, > but I wonder if it's time to loose it and keep just libstdc++. libg++ on I agree. I've done that here as well. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 14:47:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id EBD81152F2 for ; Sun, 28 Feb 1999 14:46:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA31150; Sun, 28 Feb 1999 14:45:25 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@NUXI.com Cc: Peter Wemm , Warner Losh , freebsd-current@FreeBSD.ORG Subject: Re: gcc In-reply-to: Your message of "Sun, 28 Feb 1999 13:15:03 PST." <19990228131503.A1563@relay.nuxi.com> Date: Sun, 28 Feb 1999 14:45:25 -0800 Message-ID: <31146.920241925@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Work might go a bit faster if the work that has been done already would > be posted somewhere. Having such an important issue being responsible on > a single over-worked person is not productive. ***Like Jordan said, we > get NO new install and package utils until EGCS is in the tree.*** Would you like to sort of be egcs czar for awhile and coordinate this with the other volunteers? No slight to Peter intended, who's sort of been doing that up to now, but he's just too damn busy to be principal contact for this I think. Unless we bust soemthing loose here, we're going to be discussing egcs and a possible upgrade to it at this time next year. > At a minium the stuff that has already been done should be added to the > port. Can you chase Peter around until he provides at least that much? :) > It is time to dump libg++. Once EGCS is in the tree, I'll make a port of > the libg++ meant for post g++ 2.8 compilers. What's the exact division between libg++ and libstdc++? I'm sure I'm not the only person confused by this one. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 14:50:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 293E5152FE for ; Sun, 28 Feb 1999 14:50:10 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA31174; Sun, 28 Feb 1999 14:49:57 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Chuck Robey Cc: "David O'Brien" , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc In-reply-to: Your message of "Sun, 28 Feb 1999 17:17:12 EST." Date: Sun, 28 Feb 1999 14:49:57 -0800 Message-ID: <31170.920242197@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Please keep in mind that if, in our haste, we import a compiler that > puts instability into FreeBSD, then we've drunk poison. The feature A legit concern, but also realize that all of us are talking about 4.0 here - the new compiler would be an issue we'd have up to a full year on before the product it's in goes mainstream. If that's not enough time to work out the compiler issues after switching, I can't imagine when we WILL have a better time to try and do this then. Progress entails some pain, and if we're unwilling to suffer any at all then progress ceases entirely. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 14:59:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (Postfix) with ESMTP id 3D47C15337 for ; Sun, 28 Feb 1999 14:59:07 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.8.7) with ESMTP id RAA00408; Sun, 28 Feb 1999 17:59:09 -0500 (EST) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Sun, 28 Feb 1999 17:59:08 -0500 (EST) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: "Jordan K. Hubbard" Cc: Chuck Robey , "David O'Brien" , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc In-Reply-To: <31170.920242197@zippy.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 > A legit concern, but also realize that all of us are talking about > 4.0 here - the new compiler would be an issue we'd have up to a full > year on before the product it's in goes mainstream. If that's not enough > time to work out the compiler issues after switching, I can't imagine > when we WILL have a better time to try and do this then. Progress > entails some pain, and if we're unwilling to suffer any at all then > progress ceases entirely. This is interesting, what makes egcs better than gcc? just a dumb question. I agree with Jordan though: no pain no gain. :-) Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 15: 6:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 6507714BE2 for ; Sun, 28 Feb 1999 15:06:28 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id SAA47256; Sun, 28 Feb 1999 18:04:41 -0500 (EST) Date: Sun, 28 Feb 1999 18:04:41 -0500 (EST) From: Chuck Robey To: "Jordan K. Hubbard" Cc: "David O'Brien" , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc In-Reply-To: <31170.920242197@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Feb 1999, Jordan K. Hubbard wrote: > > Please keep in mind that if, in our haste, we import a compiler that > > puts instability into FreeBSD, then we've drunk poison. The feature > > A legit concern, but also realize that all of us are talking about > 4.0 here - the new compiler would be an issue we'd have up to a full > year on before the product it's in goes mainstream. If that's not enough > time to work out the compiler issues after switching, I can't imagine > when we WILL have a better time to try and do this then. Progress > entails some pain, and if we're unwilling to suffer any at all then > progress ceases entirely. I keep on hearing about how we're losing because we don't have the 3 month old latest feature, and I want to show that we're equally concerned with stability, that's all. I want forward movement too, but every time I see something one-sided, like the comments about the CS courses (and that being in itself enough reason to move forward), I have to bring this up. I want us to go to egcs just as much as you do, but I don't want us to give an obvious show of abandoning our previous professional approach to things. Every time I see a post that is one-sidedly aimed towards the latest untested thing, with not one word about making certain it *works*, I want to tell folks that going that way, there be dragons. Yes, let's try egcs. I want to do buildworlds/installworlds/new kernel builds here with it for a while. Do you have the Makefiles you used to cut it out of your build? Could I install egcs out of ports, and do that testing? I want to do that, if it would contribute. Lots of it. I want to show that it's TESTED. TESTED. TESTED. ----------------------------+----------------------------------------------- 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 picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 15:18:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 5EC6014FD5 for ; Sun, 28 Feb 1999 15:16:54 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id PAA02404; Sun, 28 Feb 1999 15:16:36 -0800 (PST) (envelope-from obrien) Date: Sun, 28 Feb 1999 15:16:36 -0800 From: "David O'Brien" To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc Message-ID: <19990228151636.C2170@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <31170.920242197@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Kenneth Wayne Culver on Sun, Feb 28, 1999 at 05:59:08PM -0500 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 28, 1999 at 05:59:08PM -0500, Kenneth Wayne Culver wrote: > > This is interesting, what makes egcs better than gcc? just a dumb > question. I agree with Jordan though: no pain no gain. :-) IMHO, maintence. EGCS is actively being developed. Gcc 2.8.x might be, but it is hard to see. Also Jeff Law of the EGCS steering committee, has said that FSF is heavily leaning on GNU GCC 2.9 (or 2.8.2) being some branch along the EGCS tree. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 15:20:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id CDF2714F1F for ; Sun, 28 Feb 1999 15:20:19 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40427>; Mon, 1 Mar 1999 10:08:39 +1100 Date: Mon, 1 Mar 1999 10:19:45 +1100 From: Peter Jeremy Subject: Re: gcc To: jkh@zippy.cdrom.com Cc: current@FreeBSD.ORG Message-Id: <99Mar1.100839est.40427@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > Please keep in mind that if, in our haste, we import a compiler that > puts instability into FreeBSD, then we've drunk poison. I agree that -STABLE _must_ remain stable. That said, I believe that we _do_ need to move forward. I'd like to see either EGCS or gcc-2.8.1 (and the former seems to be better supported at present) brought into -current as soon as practical. "Jordan K. Hubbard" wrote: >A legit concern, but also realize that all of us are talking about >4.0 here - the new compiler would be an issue we'd have up to a full >year on before the product it's in goes mainstream. I'd like to see it merged back into the 3.x tree earlier than this. The general complaining about compiler related issues (C++ and FORTRAN-77 being the two most recent issues) will continue until the compiler makes it into a release. I think we should be able to easily validate the compiler in time for the 3.x.y release due around October (assuming the 4-monthly releases continue) - maybe even the June release. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 15:28:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat193.154.mpoweredpc.net [142.177.193.154]) by hub.freebsd.org (Postfix) with ESMTP id B7E2A153EF for ; Sun, 28 Feb 1999 15:28:29 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.2/8.9.1) with ESMTP id TAA28233; Sun, 28 Feb 1999 19:27:38 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 28 Feb 1999 19:27:38 -0400 (AST) From: The Hermit Hacker To: Chuck Robey Cc: "David O'Brien" , freebsd-current@FreeBSD.ORG Subject: Re: gcc 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, 28 Feb 1999, Chuck Robey wrote: > On Sun, 28 Feb 1999, David O'Brien wrote: > > > > It should be too easy to replace the compiler after the system is > > > installed...and shouldn't be seen as a major "hindrance"... > > > > But as Micro$hit knows, being able to check off feature boxes is > > important. Here, the CS dept encourages people that own a PC to install > > a Unix at home (we are still 100% Unix based for classes). When I push > > FreeBSD, I get asked if EGCS comes with it. I say no not by default, but > > we have a very easy to add version of it. They say, why go through the > > trouble if Linux already has it by default. Same for our support > > people. They are the laziest and most non-computer enthusiast group I've > > ever seen. Path of least effort is what wins with them. > > Please keep in mind that if, in our haste, we import a compiler that > puts instability into FreeBSD, then we've drunk poison. The feature > list won't matter, the fact that we're up to date won't matter, the fact > that FreeBSD suddenly, out of the blue, became unstable is the only > thing that anyone will remember. Last I heard, that was what the -current source tree was for...has that changed recently? Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 15:29:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id BBB421542D for ; Sun, 28 Feb 1999 15:29:29 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id PAA02498; Sun, 28 Feb 1999 15:29:09 -0800 (PST) (envelope-from obrien) Date: Sun, 28 Feb 1999 15:29:09 -0800 From: "David O'Brien" To: Chuck Robey Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc Message-ID: <19990228152909.E2170@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <31170.920242197@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Chuck Robey on Sun, Feb 28, 1999 at 06:04:41PM -0500 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I keep on hearing about how we're losing because we don't have the 3 > month old latest feature With EGCS the issue isn't having the latest 3 mo. feature, but we have a totally BROKEN C++ compiler. The STL with it is broken, and it is so far from the ISO C++ standard, it really can't be called C++ any longer. > Every time I see a post that is one-sidedly aimed towards the latest > untested thing I'm working on the egcs 1.1.x branch. I wouldn't go near their HEAD branch for FreeBSD use. I distrust that code more than I do Micro$oft's. > Yes, let's try egcs. I want to do buildworlds/installworlds/new kernel > builds here with it for a while. What I have won't build kernels yet. I could hack our system Makefiles to use different compile options, but I don't like that approach. So I'm working on adding our compiler flags and such. > Could I install egcs out of ports, and do that testing? I want to do > that, if it would contribute. Last I tried, no. IMHO, we are a ways off, but we need to at least be working on it. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 15:33: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat193.154.mpoweredpc.net [142.177.193.154]) by hub.freebsd.org (Postfix) with ESMTP id 180A615316 for ; Sun, 28 Feb 1999 15:32:55 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.2/8.9.1) with ESMTP id TAA28257; Sun, 28 Feb 1999 19:32:16 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 28 Feb 1999 19:32:16 -0400 (AST) From: The Hermit Hacker To: "Jordan K. Hubbard" Cc: Chuck Robey , "David O'Brien" , freebsd-current@FreeBSD.ORG Subject: Re: gcc In-Reply-To: <31170.920242197@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Feb 1999, Jordan K. Hubbard wrote: > > Please keep in mind that if, in our haste, we import a compiler that > > puts instability into FreeBSD, then we've drunk poison. The feature > > A legit concern, but also realize that all of us are talking about > 4.0 here - the new compiler would be an issue we'd have up to a full > year on before the product it's in goes mainstream. If that's not enough > time to work out the compiler issues after switching, I can't imagine > when we WILL have a better time to try and do this then. Progress > entails some pain, and if we're unwilling to suffer any at all then > progress ceases entirely. My 2cents...waiting a year before it goes mainstream is really going to hurt things. There appear to be more and more projects coming out that are relying on features existent in the C++ in egcs that gcc can't support. MICO (corba) is one of them...KDE appears to be more towards it with some of its applications... Bringing it into 4.0-CURRENT is great, and debugging it there, but getting it rolled into the 3.x tree should, IMHO, be considered long before 4.x gets released... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 15:38:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat193.154.mpoweredpc.net [142.177.193.154]) by hub.freebsd.org (Postfix) with ESMTP id 2498F15318 for ; Sun, 28 Feb 1999 15:37:30 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.2/8.9.1) with ESMTP id TAA28339; Sun, 28 Feb 1999 19:36:29 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 28 Feb 1999 19:36:29 -0400 (AST) From: The Hermit Hacker To: Kenneth Wayne Culver Cc: "Jordan K. Hubbard" , Chuck Robey , "David O'Brien" , freebsd-current@FreeBSD.ORG Subject: Re: gcc 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, 28 Feb 1999, Kenneth Wayne Culver wrote: > > A legit concern, but also realize that all of us are talking about > > 4.0 here - the new compiler would be an issue we'd have up to a full > > year on before the product it's in goes mainstream. If that's not enough > > time to work out the compiler issues after switching, I can't imagine > > when we WILL have a better time to try and do this then. Progress > > entails some pain, and if we're unwilling to suffer any at all then > > progress ceases entirely. > > This is interesting, what makes egcs better than gcc? just a dumb > question. I agree with Jordan though: no pain no gain. :-) For those doing, or using, C++ related projects, the current gcc is BROKEN...egcs, with its faster development cycle (kinda like ours) tends to be working harder on C++ spec compliance... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 15:46:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles234.castles.com [208.214.165.234]) by hub.freebsd.org (Postfix) with ESMTP id 0360415386 for ; Sun, 28 Feb 1999 15:46:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA14855; Sun, 28 Feb 1999 15:37:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902282337.PAA14855@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@NUXI.com Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc In-reply-to: Your message of "Sun, 28 Feb 1999 13:36:52 PST." <19990228133652.B475@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Feb 1999 15:37:08 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It should be too easy to replace the compiler after the system is > > installed...and shouldn't be seen as a major "hindrance"... > > But as Micro$hit knows, being able to check off feature boxes is > important. Here, the CS dept encourages people that own a PC to install > a Unix at home (we are still 100% Unix based for classes). When I push > FreeBSD, I get asked if EGCS comes with it. I say no not by default, but > we have a very easy to add version of it. It does come by default. You have to install it, yes, but then you have to install the compiler with Linux as well. Big hairy deal. > They say, why go through the > trouble if Linux already has it by default. Same for our support > people. They are the laziest and most non-computer enthusiast group I've > ever seen. Path of least effort is what wins with them. Order the systems with FreeBSD preinstalled from Gateway. 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 Sun Feb 28 15:53:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 90969153C6 for ; Sun, 28 Feb 1999 15:52:46 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id SAA47350; Sun, 28 Feb 1999 18:51:11 -0500 (EST) Date: Sun, 28 Feb 1999 18:51:10 -0500 (EST) From: Chuck Robey To: The Hermit Hacker Cc: "David O'Brien" , freebsd-current@FreeBSD.ORG Subject: Re: gcc 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, 28 Feb 1999, The Hermit Hacker wrote: > On Sun, 28 Feb 1999, Chuck Robey wrote: > > > On Sun, 28 Feb 1999, David O'Brien wrote: > > > > > > It should be too easy to replace the compiler after the system is > > > > installed...and shouldn't be seen as a major "hindrance"... > > > > > > But as Micro$hit knows, being able to check off feature boxes is > > > important. Here, the CS dept encourages people that own a PC to install > > > a Unix at home (we are still 100% Unix based for classes). When I push > > > FreeBSD, I get asked if EGCS comes with it. I say no not by default, but > > > we have a very easy to add version of it. They say, why go through the > > > trouble if Linux already has it by default. Same for our support > > > people. They are the laziest and most non-computer enthusiast group I've > > > ever seen. Path of least effort is what wins with them. > > > > Please keep in mind that if, in our haste, we import a compiler that > > puts instability into FreeBSD, then we've drunk poison. The feature > > list won't matter, the fact that we're up to date won't matter, the fact > > that FreeBSD suddenly, out of the blue, became unstable is the only > > thing that anyone will remember. > > Last I heard, that was what the -current source tree was for...has that > changed recently? Go looking in the archives, moving our base compiler has come up about 3-4 times a year on hackers since the 386BSD patchkit days. The argument hasn't changed, that stability in our base compiler was worth far more than destabilizing FreeBSD. Current is for experimentation ONLY when it doesn't break the buildworld. Try that, even for a few hours, and you already know what will happen. I'm FOR bringing in egcs, but ONLY if it gets a fair testing, which isn't done in 24 hours, or by one single person. This affects everyone, in as major a way as it's possible to get. This can easily become out of control. Notice how much work and testing went into the aout to elf move? Well, this requires the same thing, as far as testing goes. The very first rule is, the system compiler MUST be stable. If we can prove (and I think we can) that egcs can do that, fine. If we can't prove it (either because it's not true, or because it's just left to chance) then we shouldn't move to egcs. Your argument about CS students needing the better compiler was true, but totally ignored the fact that getting the CS students their compiler IS NOT the top priority, especially since ports can do it (did for me). That's not an argument against it, it's an argument against single-topic myopia. First, consider IF egcs can do the job of being the FreeBSD system compiler (which means building our kernel without any surprises whatsoever), because that's the number 1 requirement. If that's proven, then prove that the userland code and libraries remain similarly stable. After that, then your argument begins to take force, but until that point, it's not germane. ----------------------------+----------------------------------------------- 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 picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 16: 0:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 886E71534C for ; Sun, 28 Feb 1999 15:59:43 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id IAA13987; Mon, 1 Mar 1999 08:59:28 +0900 (JST) Message-ID: <36D9D7E6.71B976A2@newsguy.com> Date: Mon, 01 Mar 1999 08:57:26 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Peter Jeremy Cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: gcc References: <99Mar1.100839est.40427@border.alcanet.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: > > I'd like to see it merged back into the 3.x tree earlier than this. > The general complaining about compiler related issues (C++ and > FORTRAN-77 being the two most recent issues) will continue until the > compiler makes it into a release. I think we should be able to easily > validate the compiler in time for the 3.x.y release due around October > (assuming the 4-monthly releases continue) - maybe even the June > release. We can easily validate the compiler till then assuming when for the import into the -current tree? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "To make it absolutely clear: you stand on the wrong end of my blasters, so you better get lost before I start target practice!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 16:21:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 97B4F15396 for ; Sun, 28 Feb 1999 16:21:06 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA15369; Sun, 28 Feb 1999 19:20:21 -0500 (EST) Date: Sun, 28 Feb 1999 19:20:17 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Chuck Robey Cc: The Hermit Hacker , "David O'Brien" , freebsd-current@FreeBSD.ORG Subject: Re: gcc 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 How about this, which noone has suggested: Why don't we, for now, import EGCS and libstdc++, getting those working? Of course, here's the trick; let's keep /usr/bin/gcc and /usr/bin/cc as 2.7.2.x like they are now. But for /usr/bin/c++ and /usr/bin/g++, let's have EGCS overwrite the 2.7.2.x ones. As far as I see, EGCS doesn't gain anything for C, and only has gains for C++. Why not switch over partially? We can have 2.7.2.1 not build cc1plus, only cc1 and cc1obj, and have EGCS 1.1.1 build only cc1plus. With this, we get two advantages over the current system. Not only do we get a working, actively supported, C++ compiler, but also we get to keep (for now) the stable, reliable, C compiler we've been depending on for years. Noone can complain that the compiler is destabilizing the system, as all "system" utilities are in C, not C++, and noone can complain that we're behind the times with C++, since we have the latest C++ compiler and libstdc++. Of course, in the long run, once stability is proven, switching to entirely EGCS would make sense. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 16:25:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 0A7F715018; Sun, 28 Feb 1999 16:25:24 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id QAA17791; Sun, 28 Feb 1999 16:24:33 -0800 (PST) From: Archie Cobbs Message-Id: <199903010024.QAA17791@bubba.whistle.com> Subject: Re: panic: zone: entry not free In-Reply-To: <5lemnaxj6c.fsf@mg.trafford.dementia.org> from Assar Westerlund at "Feb 28, 99 11:22:35 pm" To: assar@sics.se (Assar Westerlund) Date: Sun, 28 Feb 1999 16:24:33 -0800 (PST) Cc: eivind@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Assar Westerlund writes: > I think that the goal should be to make KLDs work with all kinds of > kernels. I've been thinking about this too... Certainly, for each kernel config option FOO we could have a symbol in the kernel that a KLD could examine: static const u_char kernlel_option_FOO = 1; But what to do about KLD's that want to link against kernel symbols that may or may not exist? For example, some KLD's that present interfaces would like to know if BPF is in the kernel, and if so to support it .. but this means linking with bpfattach(), etc.. Would it be possible to permit 'partial' linking of a KLD, so that the following code would work no matter what kernel was used? int xyz_attach() { ... if (kernlel_option_BPF > 0) bpf_attach(..); /* "bpf_attach" only gets resolved if it exists * in the kernel; otherwise, it remains NULL but * that's OK because in that case we don't call it */ ... } Maybe this would require something like this in the KLD.. MODULE_BREAKABLE_LINKS(xyz) { "bpfattach", "bpf_mtap" }; A fair bit of hackery, but probably worth it... -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 16:34:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id F1E4215337 for ; Sun, 28 Feb 1999 16:34:20 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA31622; Sun, 28 Feb 1999 16:32:45 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Brian Feldman Cc: Chuck Robey , The Hermit Hacker , "David O'Brien" , freebsd-current@FreeBSD.ORG Subject: Re: gcc In-reply-to: Your message of "Sun, 28 Feb 1999 19:20:17 EST." Date: Sun, 28 Feb 1999 16:32:44 -0800 Message-ID: <31618.920248364@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sounds like an absolute nightmare. Needless to say, I loath this idea. :) > How about this, which noone has suggested: > Why don't we, for now, import EGCS and libstdc++, getting those working ? > Of course, here's the trick; let's keep /usr/bin/gcc and /usr/bin/cc as 2.7.2 .x > like they are now. But for /usr/bin/c++ and /usr/bin/g++, let's have EGCS > overwrite the 2.7.2.x ones. As far as I see, EGCS doesn't gain anything for C , > and only has gains for C++. Why not switch over partially? We can have > 2.7.2.1 not build cc1plus, only cc1 and cc1obj, and have EGCS 1.1.1 build onl y > cc1plus. > With this, we get two advantages over the current system. Not only do > we get a working, actively supported, C++ compiler, but also we get to keep > (for now) the stable, reliable, C compiler we've been depending on for years. > Noone can complain that the compiler is destabilizing the system, as all > "system" utilities are in C, not C++, and noone can complain that we're behin d > the times with C++, since we have the latest C++ compiler and libstdc++. Of > course, in the long run, once stability is proven, switching to entirely EGCS > would make sense. > > Brian Feldman _ __ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > > 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 Feb 28 16:38:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 8B6E515005 for ; Sun, 28 Feb 1999 16:37:00 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40420>; Mon, 1 Mar 1999 11:25:18 +1100 Date: Mon, 1 Mar 1999 11:36:28 +1100 From: Peter Jeremy Subject: Re: gcc To: green@unixhelp.org Cc: current@FreeBSD.ORG Message-Id: <99Mar1.112518est.40420@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: [use cc1-2.7.2.1 and ECGS cc1plus] > we get to keep >(for now) the stable, reliable, C compiler we've been depending on for years. With all the well-known idiosyncrasies that we've been working around for years. > Of >course, in the long run, once stability is proven, switching to entirely EGCS >would make sense. There's a catch-22 here: We can't prove the stability of EGCS until we start using it. Even if we don't make EGCS the base compiler, we need a standard documented mechanism for doing `make world' with EGCS as well as agreement that bug reports using ECGS will be considered. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 16:39:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat193.154.mpoweredpc.net [142.177.193.154]) by hub.freebsd.org (Postfix) with ESMTP id F2D1D15370 for ; Sun, 28 Feb 1999 16:39:17 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.2/8.9.1) with ESMTP id UAA28965; Sun, 28 Feb 1999 20:38:49 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 28 Feb 1999 20:38:49 -0400 (AST) From: The Hermit Hacker To: Chuck Robey Cc: "David O'Brien" , freebsd-current@FreeBSD.ORG Subject: Re: gcc 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, 28 Feb 1999, Chuck Robey wrote: > Your argument about CS students needing the better compiler was true, > but totally ignored the fact that getting the CS students their compiler > IS NOT the top priority, especially since ports can do it (did for me). Ummmm, you mis-quoted. I agree with your above, and my statement had to do with an inability of FreeBSD to run on the hardware that we have (IBM thinkpad laptops) then anything software related (other then kernel/driver)... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 16:52:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-47.ppp.wenet.net [206.15.85.47]) by hub.freebsd.org (Postfix) with ESMTP id 9E5601535F for ; Sun, 28 Feb 1999 16:51:34 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.2/8.9.1) with ESMTP id QAA42774; Sun, 28 Feb 1999 16:50:57 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sun, 28 Feb 1999 16:50:57 -0800 (PST) From: Alex Zepeda To: Brian Feldman Cc: Chuck Robey , The Hermit Hacker , "David O'Brien" , freebsd-current@FreeBSD.ORG Subject: Re: gcc 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, 28 Feb 1999, Brian Feldman wrote: > How about this, which noone has suggested: > Why don't we, for now, import EGCS and libstdc++, getting those working? > Of course, here's the trick; let's keep /usr/bin/gcc and /usr/bin/cc as 2.7.2.x > like they are now. But for /usr/bin/c++ and /usr/bin/g++, let's have EGCS > overwrite the 2.7.2.x ones. As far as I see, EGCS doesn't gain anything for C, > and only has gains for C++. Why not switch over partially? We can have > 2.7.2.1 not build cc1plus, only cc1 and cc1obj, and have EGCS 1.1.1 build only > cc1plus. Perhaps on face value it's an interesting idea. Debian does something similar. But egcs post 1.1 (or is it 1.1.1) use binary incompatable exception handling.. as in it's not compatable with gcc 2.8.x. But then you also get to keep two versions of gcc in the CVS tree. Plus egcs also supports more optimizations than our gcc does. Why not rip the compiler out completely and let the user drop in their favorite compiler (egcs, tcc, etc, etc)? ;-) - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 17: 6:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 98AD3153E4 for ; Sun, 28 Feb 1999 17:06:08 -0800 (PST) (envelope-from bright@cygnus.rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id UAA22010 for ; Sun, 28 Feb 1999 20:06:35 -0500 (EST) Date: Sun, 28 Feb 1999 20:06:33 -0500 (EST) From: Alfred Perlstein To: current@freebsd.org Subject: make world broken for a day. some NFS stuff as well. 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 Sorry if this is the result of work in progress, but i've been unable to make world since saturday night. It happens during the build of libskey. -- cc -fpic -DPIC -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/usr/src/lib/libskey -W -Wall -Werror -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libskey/skey_g etpass.c -o skey_getpass.So cc1: warnings being treated as errors cc1: warnings being treated as errors cc1: warnings being treated as errors /usr/obj/usr/src/tmp/usr/include/stdio.h:354: warning: `__sputc' defined but not used /usr/obj/usr/src/tmp/usr/include/stdio.h:354: warning: `__sputc' defined but not used /usr/obj/usr/src/tmp/usr/include/stdio.h:354: warning: `__sputc' defined but not used *** Error code 1 ** ..... I'm also noticing that 4.0-current defualt NFS mounts are hanging the client nfsiod gets wedged in "sbwait" state. I'm able to reproduce it locally by building and installing ssh2 from ports, it hangs during the install phase. The rest of the machine is ok, but i cannot umount -f the NFS mount from the client. I'm going to see if i can do anything to track this down, my goal is that umount -f on NFS should never, EVER not work. It seems that while it's wegded it sends data back and forth (tcpdump) i'm going to look into this, if you have any tests or programs i can run to track it down please tell me. ..... Lastly i'm interested in writing a man page for kernel.conf i know how to submit diffs, but what about totally new files? just send-pr with it attached? or a url? thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 17:12: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 4D69D154CD for ; Sun, 28 Feb 1999 17:12:05 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id UAA21076; Sun, 28 Feb 1999 20:11:50 -0500 (EST) Date: Sun, 28 Feb 1999 20:11:50 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: gcc In-Reply-To: <99Mar1.112526est.40386@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Mar 1999, Peter Jeremy wrote: > Brian Feldman wrote: > [use cc1-2.7.2.1 and ECGS cc1plus] > > > we get to keep > >(for now) the stable, reliable, C compiler we've been depending on for years. > > With all the well-known idiosyncrasies that we've been working around > for years. > > > Of > >course, in the long run, once stability is proven, switching to entirely EGCS > >would make sense. > > There's a catch-22 here: We can't prove the stability of EGCS until we > start using it. Even if we don't make EGCS the base compiler, we need > a standard documented mechanism for doing `make world' with EGCS as well > as agreement that bug reports using ECGS will be considered. All gcc/cc do is act as a front-end to cc1/cc1obj/cc1plus. Hence, a second cc for egcs could be used, or maybe using a cc -egcs flag, etc. > > Peter > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 17:14:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from ianai.BlackSun.org (Ianai.blacksun.org [168.100.186.33]) by hub.freebsd.org (Postfix) with ESMTP id E8384154A4 for ; Sun, 28 Feb 1999 17:13:54 -0800 (PST) (envelope-from tugrul@ianai.BlackSun.org) Received: from localhost (tugrul@localhost) by ianai.BlackSun.org (8.8.8/8.8.7) with SMTP id UAA23286 for ; Sun, 28 Feb 1999 20:09:19 -0500 (EST) (envelope-from tugrul@ianai.BlackSun.org) Date: Sun, 28 Feb 1999 20:09:19 -0500 (EST) From: Tugrul To: current@freebsd.org Subject: Re: gcc In-Reply-To: <99Mar1.112518est.40420@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Mar 1999, Peter Jeremy wrote: > There's a catch-22 here: We can't prove the stability of EGCS until we > start using it. Even if we don't make EGCS the base compiler, we need > a standard documented mechanism for doing `make world' with EGCS as well > as agreement that bug reports using ECGS will be considered. > I'd personally love an option for make world to use egcs installed from the port tree. And perhaps a new mailing list just for throwing random egcs complaints at. Right now I'm manually building the source tree with egcs to see how I fair. Any failures I get from building thus far are replicable with the built in gcc, so egcs doesn't seem to choke on the code all too much. The kernel code is a slightly different matter. I get the following errors: [20:10]galatalt@callisto:/usr/src/sys/compile/CALLISTO# make CC=egcc -k egcc -c -O3 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../i386/i386/identcpu.c ../../i386/i386/identcpu.c: In function `printcpuinfo': ../../i386/i386/identcpu.c:558: warning: unknown conversion type character `b' in format ../../i386/i386/identcpu.c:558: warning: too many arguments for format ../../i386/i386/identcpu.c: In function `print_AMD_info': ../../i386/i386/identcpu.c:902: internal error--insn does not satisfy its constraints: (insn:HI 278 454 279 (set (reg:SI 2 %ecx) (subreg:SI (lshiftrt:DI (reg:DI 1 %edx) (const_int 22)) 0)) 250 {lshrdi3_const_int_subreg} (nil) (expr_list:REG_DEAD (reg:SI 1 %edx) (nil))) toplev.c:1431: Internal compiler error in function fatal_insn *** Error code 1 (continuing) egcc -c -O3 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../i386/i386/pmap.c ../../i386/i386/pmap.c: In function `pmap_setdevram': ../../i386/i386/pmap.c:555: internal error--insn does not satisfy its constraints: (insn:HI 107 330 109 (set (reg:SI 1 %edx) (subreg:SI (lshiftrt:DI (reg:DI 0 %eax) (const_int 12)) 0)) 250 {lshrdi3_const_int_subreg} (nil) (expr_list:REG_DEAD (reg:SI 0 %eax) (nil))) toplev.c:1431: Internal compiler error in function fatal_insn *** Error code 1 (continuing) `kernel' not remade because of errors. [20:10]galatalt@callisto:/usr/src/sys/compile/CALLISTO# Fun fun fun :-) I built those two files with gcc and rebooted with the output. Seemed fine. Tugrul Galatali To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 17:44:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 2192415185 for ; Sun, 28 Feb 1999 17:44:45 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40436>; Mon, 1 Mar 1999 12:33:03 +1100 Date: Mon, 1 Mar 1999 12:44:15 +1100 From: Peter Jeremy Subject: Re: gcc To: tugrul@ianai.BlackSun.org Cc: current@FreeBSD.ORG Message-Id: <99Mar1.123303est.40436@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tugrul wrote: > Right now I'm manually building the source >tree with egcs to see how I fair. I tried this with 2.x and gcc-2.8.1, but was never successful - I never managed to stop it building the base compiler and not complain that it hadn't built the base compiler. I didn't spend much effort on it. > The kernel code is a slightly different matter. I get the >following errors: FWIW, I've had very few problems building 2.x kernels using gcc-2.8.1. (I did find some problems and have previously described fixes or work- arounds for them all). I haven't yet built an ELF gcc or EGCS, so I'm not sure whether there are problems with -current. If the compiler is reporting "insn does not satisfy its constraints", then it's probably a compiler bug. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 18: 4:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 46693151C3 for ; Sun, 28 Feb 1999 18:04:30 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA17496; Mon, 1 Mar 1999 12:34:11 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA15598; Mon, 1 Mar 1999 12:34:06 +1030 (CST) Message-ID: <19990301123406.Y7279@lemis.com> Date: Mon, 1 Mar 1999 12:34:06 +1030 From: Greg Lehey To: Tugrul , freebsd-current@FreeBSD.ORG Subject: Re: SiS 5591 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Tugrul on Sun, Feb 28, 1999 at 01:51:45AM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 28 February 1999 at 1:51:45 -0500, Tugrul wrote: > > Seems to work alright here. dmesg and dd tests follow. > > [before] > mercury# dd if=/dev/zero of=/tmp/zero bs=1024k count=32 > 32+0 records in > 32+0 records out > 33554432 bytes transferred in 6.013635 secs (5579725 bytes/sec) > mercury# > > [after] > mercury# dd if=/dev/zero of=/tmp/zero bs=1024k count=32 > 32+0 records in > 32+0 records out > 33554432 bytes transferred in 5.892770 secs (5634706 bytes/sec) > mercury# > > Not much gain with this drive :/ You shouldn't use files to this kind of test. The buffer cache will falsify the results, especially on relatively small transfers. Try a dd to (or from :-) the raw device. The other thing is, of course, that you can't transfer faster than the disk will allow. If you can do that in PIO mode, you won't get any speed improvement with DMA. What you *will* get is a significant drop in CPU load. > Copyright (c) 1992-1999 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.1-STABLE #0: Sun Feb 28 01:32:47 EST 1999 > galatalt@mercury.novastar.com:/usr/src/sys/compile/MERCURY > Timecounter "i8254" frequency 1193225 Hz > CPU: Pentium/P55C (166.45-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x543 Stepping=3 > Features=0x8001bf Could you send me the output of a verbose boot, please? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 18:59: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 253D314F68 for ; Sun, 28 Feb 1999 18:58:58 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA27076; Sat, 27 Feb 1999 06:02:28 +0100 From: Luigi Rizzo Message-Id: <199902270502.GAA27076@labinfo.iet.unipi.it> Subject: Re: mount -o union broken recently? To: dot@dotat.at (Tony Finch) Date: Sat, 27 Feb 1999 06:02:28 +0100 (MET) Cc: current@FreeBSD.ORG In-Reply-To: from "Tony Finch" at Feb 27, 99 02:48:29 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 447 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >i just experienced the above today while trying diskless, and while > >ls only seems to return the entries for the topmost directory, files > >are accessible if you know the name. no idea if this is of any help. > > This is exactly the right pointer, thanks! The problem appears to be great -- will try this later today! so... should i bug someone to have this committed back to the tree (or ask permission to do it myself) ? cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 19: 9:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.eecis.udel.edu (louie.udel.edu [128.175.7.39]) by hub.freebsd.org (Postfix) with SMTP id C4C2314F68 for ; Sun, 28 Feb 1999 19:08:53 -0800 (PST) (envelope-from alexandr@mail.eecis.udel.edu) Received: from ren.eecis.udel.edu by mail.eecis.udel.edu id aa04295; 28 Feb 1999 22:08 EST To: The Hermit Hacker Cc: Chuck Robey , David O'Brien , freebsd-current@freebsd.org Subject: RE: gcc Organization: Mos Eisley Candy Store Reply-To: alexandr@mail.eecis.udel.edu Message-Id: <19990301030911.C4C2314F68@hub.freebsd.org> Date: Sun, 28 Feb 1999 19:09:11 -0800 (PST) From: alexandr@mail.eecis.udel.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Reply to Your Message of Sun, 28 Feb 1999 20: 38:49 -0400 Date: Sun, 28 Feb 1999 22:08:14 -0500 From: Jerry Alexandratos Message-ID: <199902282208.aa04295@mail.eecis.udel.edu> The Hermit Hacker says: : On Sun, 28 Feb 1999, Chuck Robey wrote: : : > Your argument about CS students needing the better compiler was true, : > but totally ignored the fact that getting the CS students their compiler : > IS NOT the top priority, especially since ports can do it (did for me). : : Ummmm, you mis-quoted. I agree with your above, and my statement had to : do with an inability of FreeBSD to run on the hardware that we have (IBM : thinkpad laptops) then anything software related (other then : kernel/driver)... I think I take offense to this statement. I've been running FreeBSD on various models of StinkPads for the past two+ years. The combo works (mostly) like a charm too. --Jerry 8) Jerry Alexandratos % - % "Nothing inhabits my (8 8) alexandr@louie.udel.edu % - % thoughts, and oblivion (8 8) darkstar@strauss.udel.edu % - % drives my desires." (8 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 19:19: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from ianai.BlackSun.org (Ianai.blacksun.org [168.100.186.33]) by hub.freebsd.org (Postfix) with ESMTP id D37FB15253 for ; Sun, 28 Feb 1999 19:19:06 -0800 (PST) (envelope-from tugrul@ianai.BlackSun.org) Received: from localhost (tugrul@localhost) by ianai.BlackSun.org (8.8.8/8.8.7) with SMTP id WAA23493 for ; Sun, 28 Feb 1999 22:14:30 -0500 (EST) (envelope-from tugrul@ianai.BlackSun.org) Date: Sun, 28 Feb 1999 22:14:30 -0500 (EST) From: Tugrul To: current@FreeBSD.ORG Subject: Re: gcc 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, 28 Feb 1999, Tugrul wrote: > > [20:10]galatalt@callisto:/usr/src/sys/compile/CALLISTO# make CC=egcc -k [...errors...] > [20:10]galatalt@callisto:/usr/src/sys/compile/CALLISTO# > Never mind, those errors are not faults in EGCS it seems. PGCC introduces those problems. I built my kernel with plain old egcs 1.1.1 and its just fine. When I get home tomorrow I should have a completely EGCS compiled system. So far so good. Tugrul Galatali To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 19:20:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat193.154.mpoweredpc.net [142.177.193.154]) by hub.freebsd.org (Postfix) with ESMTP id A88E6151A8 for ; Sun, 28 Feb 1999 19:20:46 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.2/8.9.1) with ESMTP id XAA30242; Sun, 28 Feb 1999 23:20:02 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 28 Feb 1999 23:20:02 -0400 (AST) From: The Hermit Hacker To: alexandr@mail.eecis.udel.edu Cc: Chuck Robey , "David O'Brien" , freebsd-current@freebsd.org Subject: RE: gcc In-Reply-To: <199903010308.WAA36829@hub.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 Sun, 28 Feb 1999 alexandr@mail.eecis.udel.edu wrote: > In Reply to Your Message of Sun, 28 Feb 1999 20: 38:49 -0400 > Date: Sun, 28 Feb 1999 22:08:14 -0500 > From: Jerry Alexandratos > Message-ID: <199902282208.aa04295@mail.eecis.udel.edu> > > The Hermit Hacker says: > : On Sun, 28 Feb 1999, Chuck Robey wrote: > : > : > Your argument about CS students needing the better compiler was true, > : > but totally ignored the fact that getting the CS students their compiler > : > IS NOT the top priority, especially since ports can do it (did for me). > : > : Ummmm, you mis-quoted. I agree with your above, and my statement had to > : do with an inability of FreeBSD to run on the hardware that we have (IBM > : thinkpad laptops) then anything software related (other then > : kernel/driver)... > > I think I take offense to this statement. I've been running FreeBSD on > various models of StinkPads for the past two+ years. The combo works > (mostly) like a charm too. You are most welcome to take offense to that statement, especially considering you obviously have no idea what you are taking offesnse at... Yes, FreeBSD installs on these things, but the network card in them are not supported by FreeBSD, which defeats the purpose of a "Networked Campus"... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 20:12: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 01E041532A for ; Sun, 28 Feb 1999 20:12:03 -0800 (PST) (envelope-from bright@cygnus.rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id XAA29433; Sun, 28 Feb 1999 23:12:30 -0500 (EST) Date: Sun, 28 Feb 1999 23:12:28 -0500 (EST) From: Alfred Perlstein To: The Hermit Hacker Cc: alexandr@mail.eecis.udel.edu, Chuck Robey , "David O'Brien" , freebsd-current@FreeBSD.ORG Subject: RE: gcc 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, 28 Feb 1999, The Hermit Hacker wrote: > > The Hermit Hacker says: > > : On Sun, 28 Feb 1999, Chuck Robey wrote: > > : > > : > Your argument about CS students needing the better compiler was true, > > : > but totally ignored the fact that getting the CS students their compiler > > : > IS NOT the top priority, especially since ports can do it (did for me). > > : > > : Ummmm, you mis-quoted. I agree with your above, and my statement had to > > : do with an inability of FreeBSD to run on the hardware that we have (IBM > > : thinkpad laptops) then anything software related (other then > > : kernel/driver)... > > > > I think I take offense to this statement. I've been running FreeBSD on > > various models of StinkPads for the past two+ years. The combo works > > (mostly) like a charm too. > > You are most welcome to take offense to that statement, especially > considering you obviously have no idea what you are taking offesnse at... > > Yes, FreeBSD installs on these things, but the network card in them are > not supported by FreeBSD, which defeats the purpose of a "Networked > Campus"... What are the most commonly found chipsets in these thinkpads? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 22:58:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 2BB8515228 for ; Sun, 28 Feb 1999 22:58:13 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id WAA04314; Sun, 28 Feb 1999 22:57:39 -0800 (PST) (envelope-from obrien) Date: Sun, 28 Feb 1999 22:57:39 -0800 From: "David O'Brien" To: "Jordan K. Hubbard" Cc: current@freebsd.org Subject: Re: gcc Message-ID: <19990228225739.F3380@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990228131503.A1563@relay.nuxi.com> <31146.920241925@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <31146.920241925@zippy.cdrom.com>; from Jordan K. Hubbard on Sun, Feb 28, 1999 at 02:45:25PM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It is time to dump libg++. Once EGCS is in the tree, I'll make a port of > > the libg++ meant for post g++ 2.8 compilers. > > What's the exact division between libg++ and libstdc++? I'm sure > I'm not the only person confused by this one. :) libg++ was a set of "standard" classes for strings, lists, etc. created by FSF to help others from inventing the wheel. Stroustrup has commented that one of his bigger mistakes was releasing C++ on the world w/o a standard set of classes. (where as Eiffel, et. al. did) The ISO C++ standards committee realized this and decided to come up with a standard set of basic C++ data structures. AT&T's iostream and HP Labs' STL (standard templet library) ended up becoming part of this standard set. Thus libg++ classes are a purely FSF class library that shouldn't be used for any new code development. The current libg++ only contains what was left after the ISO stdlibc++ stuff was gutted. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 23:17: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 79CA91521F; Sun, 28 Feb 1999 23:16:08 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA14759; Mon, 1 Mar 1999 18:15:42 +1100 Date: Mon, 1 Mar 1999 18:15:42 +1100 From: Bruce Evans Message-Id: <199903010715.SAA14759@godzilla.zeta.org.au> To: assar@sics.se, eivind@FreeBSD.ORG Subject: Re: panic: zone: entry not free Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I think that the goal should be to make KLDs work with all kinds of >kernels. And the only place where this seems to be a problem is with >zalloc and zfree. So it seems to me that one of the following could >be done to solve it: > >a. make zalloc and zfree non-inline >b. call zalloci and zfreei in code that can end up in KLDs >c. call zalloci and zfreei everywhere where it's not performance-critical There are many potential problems with SMP kernels. Many of the inline functions in depend on SMP. We've already pessimised the usual (non-SMP) case by uninlining a few too many spl-related functions. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 23:32:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 964BB15219 for ; Sun, 28 Feb 1999 23:32:48 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA32640; Sun, 28 Feb 1999 23:32:37 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@NUXI.com Cc: current@freebsd.org Subject: Re: gcc In-reply-to: Your message of "Sun, 28 Feb 1999 22:57:39 PST." <19990228225739.F3380@relay.nuxi.com> Date: Sun, 28 Feb 1999 23:32:37 -0800 Message-ID: <32636.920273557@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thus libg++ classes are a purely FSF class library that shouldn't be used > for any new code development. The current libg++ only contains what was > left after the ISO stdlibc++ stuff was gutted. Thanks for the explanation - that makes things much clearer. So, I guess we shoot for libstdc++ as the "minimum requirements" and perhaps provide libg++ as well (not necessarily initially) just for the convenience of those porting code from environments where the GNU library functions were used. I've just built the world and kernel from egcs-2.91.62 and it seems to work pretty well. I haven't really stress the system all that much yet, but it hasn't misbehaved in any way yet. - Jrodan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 23:36: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8AE6315219 for ; Sun, 28 Feb 1999 23:35:59 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id XAA04465 for current@freebsd.org; Sun, 28 Feb 1999 23:35:42 -0800 (PST) (envelope-from obrien) Date: Sun, 28 Feb 1999 23:35:42 -0800 From: "David O'Brien" To: current@freebsd.org Subject: Re: gcc Message-ID: <19990228233542.A4444@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990228225739.F3380@relay.nuxi.com> <32636.920273557@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <32636.920273557@zippy.cdrom.com>; from Jordan K. Hubbard on Sun, Feb 28, 1999 at 11:32:37PM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > guess we shoot for libstdc++ as the "minimum requirements" and perhaps > provide libg++ as well (not necessarily initially) just for the Just make libg++ a port. :-) -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 23:41:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from dyn02.trafford.dementia.org (dyn02.trafford.dementia.org [204.29.154.130]) by hub.freebsd.org (Postfix) with ESMTP id 25E7015212; Sun, 28 Feb 1999 23:41:04 -0800 (PST) (envelope-from assar@sics.se) Received: (from assar@localhost) by dyn02.trafford.dementia.org (8.9.1/8.7.3) id IAA56007; Mon, 1 Mar 1999 08:42:55 +0100 (CET) To: Bruce Evans Cc: eivind@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: panic: zone: entry not free References: <199903010715.SAA14759@godzilla.zeta.org.au> Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 01 Mar 1999 08:42:53 +0100 In-Reply-To: Bruce Evans's message of "Mon, 1 Mar 1999 18:15:42 +1100" Message-ID: <5lzp5xmz9e.fsf@mg.trafford.dementia.org> Lines: 22 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > >I think that the goal should be to make KLDs work with all kinds of > >kernels. And the only place where this seems to be a problem is with > >zalloc and zfree. So it seems to me that one of the following could > >be done to solve it: > > > >a. make zalloc and zfree non-inline > >b. call zalloci and zfreei in code that can end up in KLDs > >c. call zalloci and zfreei everywhere where it's not performance-critical > > There are many potential problems with SMP kernels. Many of the inline > functions in depend on SMP. We've already pessimised > the usual (non-SMP) case by uninlining a few too many spl-related > functions. So you think it would be bad to have zalloc and zfree as non-inline functions? That would mean that KLDs would be different depending on the options used to build the kernel and that KLDs would need some way of figuring out the these options. How should that be done? By installing opt_global.h after building the kernel? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 28 23:49:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 654FD15208 for ; Sun, 28 Feb 1999 23:49:19 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id TAA08885; Mon, 1 Mar 1999 19:00:12 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199903010800.TAA08885@cimlogic.com.au> Subject: Re: gcc In-Reply-To: <32636.920273557@zippy.cdrom.com> from "Jordan K. Hubbard" at "Feb 28, 1999 11:32:37 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Mon, 1 Mar 1999 19:00:12 +1100 (EST) Cc: obrien@NUXI.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Jordan K. Hubbard wrote: > I've just built the world and kernel from egcs-2.91.62 and it > seems to work pretty well. I haven't really stress the system > all that much yet, but it hasn't misbehaved in any way yet. > > - Jrodan Since 4.0 was only recently branched, now seems like a good time to start using egcs as the system compiler, even if things are a bit bumpy for a while. Many people who started using -current during the 2.X vs 3.0 time can use 3.X-stable without losing much, if anything. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 0:32:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id DB08E15185; Mon, 1 Mar 1999 00:32:43 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA21134; Mon, 1 Mar 1999 19:32:19 +1100 Date: Mon, 1 Mar 1999 19:32:19 +1100 From: Bruce Evans Message-Id: <199903010832.TAA21134@godzilla.zeta.org.au> To: assar@sics.se, bde@zeta.org.au Subject: Re: panic: zone: entry not free Cc: eivind@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> There are many potential problems with SMP kernels. Many of the inline >> functions in depend on SMP. We've already pessimised >> the usual (non-SMP) case by uninlining a few too many spl-related >> functions. > >So you think it would be bad to have zalloc and zfree as non-inline >functions? That would mean that KLDs would be different depending on >the options used to build the kernel and that KLDs would need some way >of figuring out the these options. How should that be done? By >installing opt_global.h after building the kernel? I think global options should be avoided if possible. When they can't be avoided, KLDs should probably extern versions of some functions that are normally static inline, and whatever else it takes for them to be to be independent of kernel options. The kernel proper must provide the uninlined versions (compiled with its options). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 1:33:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 10EA01530A for ; Mon, 1 Mar 1999 01:33:18 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10HP4A-0009qL-00; Mon, 1 Mar 1999 11:32:46 +0200 From: Sheldon Hearn To: Alfred Perlstein Cc: current@freebsd.org Subject: Re: make world broken for a day. some NFS stuff as well. In-reply-to: Your message of "Sun, 28 Feb 1999 20:06:33 EST." Date: Mon, 01 Mar 1999 11:32:46 +0200 Message-ID: <37840.920280766@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Feb 1999 20:06:33 EST, Alfred Perlstein wrote: > Lastly i'm interested in writing a man page for kernel.conf i know > how to submit diffs, but what about totally new files? just send-pr > with it attached? or a url? Send-pr(1). For new files, see the diff(1) manpage description of the -N command-line option. If you're submitting diffs against a CVS repo, do cvs -qR diff -udRN :-) Later, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 6:56:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id D6B5F15006 for ; Mon, 1 Mar 1999 06:56:42 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id BAA18860; Tue, 2 Mar 1999 01:56:19 +1100 Date: Tue, 2 Mar 1999 01:56:19 +1100 From: Bruce Evans Message-Id: <199903011456.BAA18860@godzilla.zeta.org.au> To: bde@zeta.org.au, dick@tar.com Subject: Re: lockmgr panic with mmap() Cc: current@FreeBSD.ORG, julian@whistle.com, pangolin@home.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> mincore() locks the vmspace map, and initialises vec[] a byte at a time >> using subyte(). When vec[] is sufficiently large, it is not all in core >> initially and a page fault occurs in subyte(). The new stack growing >> code locks the vmspace map early and panics. > >It appears to me the potential for deadlock exists in the old grow code >too, but is less likely. > >I've attached a patch that addresses the issue, though there is a >question if this is the best solution. > >With the old grow code, if the map lock is already held, one of the >following will be true >a) the grow code doesn't get executed because the va is not > in the stack region, which is equivalent to grow returning > success >b) the grow code returns success because there's no need to > grow the region because the va is aready in the mapped region. >c) the grow code returns false if the va is within the stack > region and there's no room left, which normally will result > in a SIGSEGV >d) the grow code attempts to grow the stack via vm_map_find and > will then deadlock at the vm_map_lock call > >With this patch, if the map lock is already held, by always returning >success, cases a) and b) will be the same as before. For case c) >the code will attempt to continue to execute, generally calling >vm_fault, which should, I think, generate a SIGSEGV, essentially >the same result as the old code, but via a different path. Case d) >will now continue executing in a manner equivalent to the new case c). > >The question is whether there is a way to do the autogrow function if >the map lock is already held. I think it shouldn't work. Copying to and from user space must not generate SIGSEGV if the application could access its memory directly. The easiest way to implement this is to never lock maps before accessing user memory. Atomic copies won't get any easier to do after you've backed out of a deadlock. I think mincore() should just unlock the map while calling subyte() and restart if the map changes significantly underneath it. Some critical examples: 1. mincore(addr, 0xfffffff0, vec) at rtprio 0 (in only process with this priority). vec[] only needs to have size 1MB (for 4K pages). It's barely reasonable for the application to expect vec[] to be all mapped and to perfectly represent the current state. To implement this, mincore() would have to prefault vec[] (or backtrack to give the equivalent) so that it doesn't block. 2. mincore(vec, len, vec). This is quite likely to change the incore'ness of vec[]. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 8:33:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id C0B6B15247 for ; Mon, 1 Mar 1999 08:33:35 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA16808; Mon, 1 Mar 1999 11:33:06 -0500 (EST) (envelope-from wollman) Date: Mon, 1 Mar 1999 11:33:06 -0500 (EST) From: Garrett Wollman Message-Id: <199903011633.LAA16808@khavrinen.lcs.mit.edu> To: Bill Paul Cc: current@FreeBSD.ORG Subject: Request for review: changes to if_vlan.c In-Reply-To: <199902280437.XAA26179@skynet.ctr.columbia.edu> References: <199902280437.XAA26179@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Interested persons should review the diffs and pipe up if they have > some passionate argument argument against them. Patches look mostly fine. > Also, I should point out that while if_vlan provides the necessary > kernel hackery to implement VLANs, there isn't any user space utility > for configuring vlan interfaces (ifconfig doesn't seem to have any > vlan-specific code that I could see, and is no vlanconfig). I stopped development on vlan(4) when the switch we had that spoke 802.1Q was returned to the vendor at the end of our demo period. I have 28 on order right now, and should resume work on the driver after I get those switches deployed. For interfaces like yours, I would have preferred a subinterface mechanism, but I never had the time to implement that. Care to implement GVRP while you're at it? > There also is no vlan(4) man page. See above. > otherwise I'm going to take it upon myself to hack up ifconfig and > write the man pages myself. I believe ifconfig is the wrong program for the task. There should be a separate vlanconfig program. (I wrote one, but it's on my laptop where I can't conveniently get to it right now.) There are a couple of areas where vlan(4) needs to get some help from the underlying driver: - Promiscuous mode doesn't work at all. It ought to be possible to put just a specific VLAN into promiscuous mode, without affecting all the others. This probably involves repeating all of the BPF does-this-packet-look-like-mine? gluck from the physical interface drivers. - Multicast is similarly broken (and a more serious weakness). There needs to be a mechanism to pass multicast group membership down to the underlying driver. It may also be necessary to do duplicate suppression, which is a real challenge. > + * XXX It's incorrect to assume that we must always kludge up > + * headers on the physical device's behalf: some devices support > + * VLAN tag insersion and extraction in firmware. My theory, as explained above, was that such devices would implement subinterfaces. > ! * If the LINK1 flag is set, it means the underlying interface > ! * can do VLAN tag insertion itself and doesn't require us to > ! * create a special header for it. In this case, we just pass Are we certain that all drivers are now doing if_media and no longer using IFF_LINK1 for that purpose? > /* > * Set up our ``Ethernet address'' to reflect the underlying > ! * physical interface's. > */ > ifa1 = ifnet_addrs[ifv->ifv_if.if_index - 1]; > ifa2 = ifnet_addrs[p->if_index - 1]; > --- 315,321 ---- > /* > * Set up our ``Ethernet address'' to reflect the underlying > ! * physical interfaces. > */ Grammar fault -- core dumped. (The wording was correct as it was.) > * Set the interface MTU. > + * This is bogus. The underlying interface might support > + * jumbo frames. > */ > if (ifr->ifr_mtu > ETHERMTU) { > error = EINVAL; I belong to the religion which as that if the interface is doing ``jumbo frames'' than it's not doing ``Ethernet''. There are all sorts of crocks which were perpretrated to allow bridging of FDDI and Ethernet, and I have no intention of supporting the same crocks here. -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 Mar 1 8:47:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from finsco.com (unknown [216.0.231.2]) by hub.freebsd.org (Postfix) with SMTP id 6CE3E152FB for ; Mon, 1 Mar 1999 08:47:19 -0800 (PST) (envelope-from billh@finsco.com) Received: from finsco.com by finsco.com (SMI-8.6/SMI-SVR4) id KAA01834; Mon, 1 Mar 1999 10:42:39 -0600 Message-ID: <36DAC3BD.2BA748A3@finsco.com> Date: Mon, 01 Mar 1999 10:43:41 -0600 From: Bill Hamilton X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: John Irwin , freebsd-current@freebsd.org Subject: Re: 3.1 upgrade problems References: <36DAACE3.E851C1FA@finsco.com> <36DABF0B.B44712D0@ninthwave.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is 3.0-RELEASE I'm coming from. I have elf binaries (except some ports?). The kernel is aout. If I rebuild the kernel with the new sources without doing a "make upgrade", won't something break? Would I set KERNELFORMAT=elf in make.conf first? John Irwin wrote: > > Bill Hamilton wrote: > > > I have tried 3 times to "make upgrade" from 3.0-RELEASE to 3.1-CURRENT. > > The first time it coredumped while working on the lex stuff. > > The next 2 times it died in libexec someplace at roughly the same spot. > > Below is the result of make upgrade 2> filename on Sunday pm and Monday > > I had similiar problems. (Non-overclocked machine) > > What eventually worked was: > -- rebuild kernel and install it, reboot > -- 'make most' and 'make installmost' at the top level > -- go into gnu/usr.bin/cc, 'make', 'make install' > > After that I was able to 'make world' just fine. > > Of course you have aout binaries, so that may make the whole thing a lot harder. > Good luck. > > -- John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 9:10:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id E7D6115031 for ; Mon, 1 Mar 1999 09:10:15 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA22654; Mon, 1 Mar 1999 09:09:58 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id JAA48942; Mon, 1 Mar 1999 09:09:57 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 1 Mar 1999 09:09:57 -0800 (PST) Message-Id: <199903011709.JAA48942@vashon.polstra.com> To: jkh@zippy.cdrom.com Subject: Re: gcc In-Reply-To: <31122.920241640@zippy.cdrom.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <31122.920241640@zippy.cdrom.com>, Jordan K. Hubbard wrote: > > I'd personally be happy with an egcs that just did sensible things > with ELF, Me too. We _must_ not let a.out become a ball and chain. We have stressed over and over all along that we were not going to become a dual-object-format OS. That means we _must_ be willing to abandon a.out support for new code. We will keep the legacy a.out libraries for old applications to link against, but we don't have to keep the ability to generate new ones. To do so would hold us back (_is_ holding us back) with very little to show for it. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 9:15:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 9186A15408 for ; Mon, 1 Mar 1999 09:15:21 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA22689; Mon, 1 Mar 1999 09:15:04 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id JAA48969; Mon, 1 Mar 1999 09:15:03 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 1 Mar 1999 09:15:03 -0800 (PST) Message-Id: <199903011715.JAA48969@vashon.polstra.com> To: obrien@NUXI.com Subject: Re: gcc In-Reply-To: <19990228152909.E2170@relay.nuxi.com> References: <31170.920242197@zippy.cdrom.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990228152909.E2170@relay.nuxi.com>, David O'Brien wrote: > > I keep on hearing about how we're losing because we don't have the 3 > > month old latest feature > > With EGCS the issue isn't having the latest 3 mo. feature, but we have a > totally BROKEN C++ compiler. Yes. We desperately need to upgrade our compiler, and egcs looks like it's definitely the way to go. > What I have won't build kernels yet. I could hack our system Makefiles > to use different compile options, but I don't like that approach. So > I'm working on adding our compiler flags and such. Hang on. Others have reported success building kernels with egcs. But even if there are problems, don't jump to the conclusion that they are caused by compiler bugs. Linux also had problems building working kernels at first, but the problems turned out to be caused by incorrect clobber specs in "asm" statements. Such errors have also been found in the FreeBSD kernel. Some of them have been fixed, but maybe not all of them. In any case, the problems should be fixed at their source, not kludged around in the compiler. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 9:16:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 132D2154CA for ; Mon, 1 Mar 1999 09:16:33 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA22701; Mon, 1 Mar 1999 09:16:17 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id JAA48986; Mon, 1 Mar 1999 09:16:16 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 1 Mar 1999 09:16:16 -0800 (PST) Message-Id: <199903011716.JAA48986@vashon.polstra.com> To: green@unixhelp.org Subject: Re: gcc In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Brian Feldman wrote: > How about this, which noone has suggested: Why don't we, for now, > import EGCS and libstdc++, getting those working? Of course, here's > the trick; let's keep /usr/bin/gcc and /usr/bin/cc as 2.7.2.x like > they are now. Ick! No way! John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 9:18: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 17CC5154A2 for ; Mon, 1 Mar 1999 09:17:39 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id SAA22914; Mon, 1 Mar 1999 18:17:21 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id SAA15361; Mon, 1 Mar 1999 18:17:13 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: gcc In-reply-to: Your message of "Mon, 01 Mar 1999 09:09:57 PST." <199903011709.JAA48942@vashon.polstra.com> Date: Mon, 01 Mar 1999 18:17:13 +0100 Message-ID: <15359.920308633@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199903011709.JAA48942@vashon.polstra.com>, John Polstra writes: >In article <31122.920241640@zippy.cdrom.com>, >Jordan K. Hubbard wrote: >> >> I'd personally be happy with an egcs that just did sensible things >> with ELF, > >Me too. We _must_ not let a.out become a ball and chain. We have >stressed over and over all along that we were not going to become a >dual-object-format OS. That means we _must_ be willing to abandon >a.out support for new code. We will keep the legacy a.out libraries >for old applications to link against, but we don't have to keep the >ability to generate new ones. To do so would hold us back (_is_ >holding us back) with very little to show for it. Wouldn't the first logical step be to stop generating the a.out libs in make world, and check in the "final version" like with the rest of the compat libs ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 9:20:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 1B83815517 for ; Mon, 1 Mar 1999 09:20:23 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA22745; Mon, 1 Mar 1999 09:20:06 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id JAA49016; Mon, 1 Mar 1999 09:20:06 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 1 Mar 1999 09:20:06 -0800 (PST) Message-Id: <199903011720.JAA49016@vashon.polstra.com> To: obrien@NUXI.com Subject: Re: gcc In-Reply-To: <19990228233542.A4444@relay.nuxi.com> References: <19990228225739.F3380@relay.nuxi.com> <32636.920273557@zippy.cdrom.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990228233542.A4444@relay.nuxi.com>, David O'Brien wrote: > > guess we shoot for libstdc++ as the "minimum requirements" and perhaps > > provide libg++ as well (not necessarily initially) just for the > > Just make libg++ a port. :-) Yes, or abandon it entirely. We surely don't need it in our base system. Even for ports, I'd be surprised to find anything useful that still relied on libg++. Any software that still uses libg++ is almost certainly unmaintained, and uncompilable with modern C++ compilers. (I.e., it does not conform to the C++ standard.) Libg++ is _ancient_. It pre-dated templates even. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 9:20:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id C18CC15591 for ; Mon, 1 Mar 1999 09:20:29 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id MAA22053; Mon, 1 Mar 1999 12:19:28 -0500 (EST) (envelope-from luoqi) Date: Mon, 1 Mar 1999 12:19:28 -0500 (EST) From: Luoqi Chen Message-Id: <199903011719.MAA22053@lor.watermarkgroup.com> To: bde@zeta.org.au, dick@tar.com Subject: Re: lockmgr panic with mmap() Cc: current@FreeBSD.ORG, julian@whistle.com, pangolin@home.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The question is whether there is a way to do the autogrow function if > the map lock is already held. > Allow lock recurse? -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 9:24:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 30A0C155E4 for ; Mon, 1 Mar 1999 09:24:43 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA22786; Mon, 1 Mar 1999 09:24:24 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id JAA49030; Mon, 1 Mar 1999 09:24:24 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15359.920308633@critter.freebsd.dk> Date: Mon, 01 Mar 1999 09:24:23 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Poul-Henning Kamp Subject: Re: gcc Cc: current@FreeBSD.ORG, jkh@zippy.cdrom.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > Wouldn't the first logical step be to stop generating the a.out libs > in make world, and check in the "final version" like with the rest > of the compat libs ? Yes! And it is long past the time when we should have done exactly that. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 9:52:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 312BC15374 for ; Mon, 1 Mar 1999 09:51:53 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA24895; Mon, 1 Mar 1999 10:51:24 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA03774; Mon, 1 Mar 1999 10:51:15 -0700 Date: Mon, 1 Mar 1999 10:51:15 -0700 Message-Id: <199903011751.KAA03774@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Garrett Wollman Cc: Bill Paul , current@FreeBSD.ORG Subject: Re: Request for review: changes to if_vlan.c In-Reply-To: <199903011633.LAA16808@khavrinen.lcs.mit.edu> References: <199902280437.XAA26179@skynet.ctr.columbia.edu> <199903011633.LAA16808@khavrinen.lcs.mit.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ! * If the LINK1 flag is set, it means the underlying interface > > ! * can do VLAN tag insertion itself and doesn't require us to > > ! * create a special header for it. In this case, we just pass > > Are we certain that all drivers are now doing if_media and no longer > using IFF_LINK1 for that purpose? I believe the old isa devices do not use if_media, but I could be wrong. (if_ep comes to mind....) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 10: 7:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 0205415483 for ; Mon, 1 Mar 1999 10:06:30 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id TAA23141; Mon, 1 Mar 1999 19:06:13 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id TAA18614; Mon, 1 Mar 1999 19:06:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Nate Williams Cc: Garrett Wollman , Bill Paul , current@FreeBSD.ORG Subject: Re: Request for review: changes to if_vlan.c In-reply-to: Your message of "Mon, 01 Mar 1999 10:51:15 MST." <199903011751.KAA03774@mt.sri.com> Date: Mon, 01 Mar 1999 19:06:09 +0100 Message-ID: <18612.920311569@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199903011751.KAA03774@mt.sri.com>, Nate Williams writes: >> > ! * If the LINK1 flag is set, it means the underlying interface >> > ! * can do VLAN tag insertion itself and doesn't require us to >> > ! * create a special header for it. In this case, we just pass >> >> Are we certain that all drivers are now doing if_media and no longer >> using IFF_LINK1 for that purpose? > >I believe the old isa devices do not use if_media, but I could be >wrong. (if_ep comes to mind....) And some new PCI devices doesn't either because if_media is hopelessly narrowtrack for real world devices :-( -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 10: 7:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa15-25.ix.netcom.com [207.93.148.25]) by hub.freebsd.org (Postfix) with ESMTP id 709C3154EA for ; Mon, 1 Mar 1999 10:07:14 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id KAA56314; Mon, 1 Mar 1999 10:06:58 -0800 (PST) (envelope-from tomdean) Date: Mon, 1 Mar 1999 10:06:58 -0800 (PST) Message-Id: <199903011806.KAA56314@ix.netcom.com> From: Thomas Dean To: freebsd-current@freebsd.org Subject: egcs and gcc Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I installed egcs from the port. eg++ produces larger binaries than g++. From this trivial example, I would expect these files to be very similar in size. obj_size exe_size strip_exe_size -------- -------- -------------- g++ 972 7150 5464 eg++ 1188 299547 76792 eg++ seems to produce faster executables. tomdean == the code ========================================== #! /bin/sh doit() { echo "# $1" $1 } == the output ========================================== # g++ --version 2.7.2.1 # g++ -m486 -O2 -c hello.cc # ls -l hello.o -rw-r--r-- 1 tomdean users 972 Mar 1 09:33 hello.o # g++ -m486 -O2 hello.cc -o hello # ls -l hello -rwxr-xr-x 1 tomdean users 7150 Mar 1 09:33 hello # file hello hello: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), \ dynamically linked, not stripped # strip hello # ls -l hello -rwxr-xr-x 1 tomdean users 5464 Mar 1 10:02 hello # file hello hello: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), \ dynamically linked, stripped # time hello Hello, world. 0.07 real 0.05 user 0.02 sys # eg++ --version egcs-2.91.60 # eg++ -m486 -O2 -c hello.cc # ls -l hello.o -rw-r--r-- 1 tomdean users 1188 Mar 1 09:33 hello.o # eg++ -m486 -O2 hello.cc -o hello # ls -l hello -rwxr-xr-x 1 tomdean users 299547 Mar 1 09:33 hello # file hello hello: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), \ dynamically linked, not stripped # strip hello # ls -l hello -rwxr-xr-x 1 tomdean users 76792 Mar 1 10:02 hello # file hello hello: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), \ dynamically linked, stripped # time hello Hello, world. 0.02 real 0.00 user 0.02 sys To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 10:39:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 8517A15632 for ; Mon, 1 Mar 1999 10:39:28 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id MAA04049; Mon, 1 Mar 1999 12:39:06 -0600 (CST) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id MAA89683; Mon, 1 Mar 1999 12:39:06 -0600 (CST) Date: Mon, 1 Mar 1999 12:39:06 -0600 From: Alan Cox To: "Richard Seaman, Jr." Cc: current@freebsd.org Subject: Re: lockmgr panic with mmap() Message-ID: <19990301123906.B89033@nonpc.cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Until you modify the map, an exclusive lock on the map is overkill. Try using read locks. (See vm_map_lookup.) In the meantime, I can't see any reason why mincore acquires an exclusive lock either. (It never modifies the map.) I'm going to remedy that. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 11: 5:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (Postfix) with ESMTP id BBA38153F2 for ; Mon, 1 Mar 1999 11:04:47 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id OAA15263; Mon, 1 Mar 1999 14:00:05 -0500 (EST) Date: Mon, 1 Mar 1999 14:00:05 -0500 (EST) From: "Matthew N. Dodd" To: Poul-Henning Kamp Cc: Nate Williams , Garrett Wollman , Bill Paul , current@FreeBSD.ORG Subject: Re: Request for review: changes to if_vlan.c In-Reply-To: <18612.920311569@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Mar 1999, Poul-Henning Kamp wrote: > In message <199903011751.KAA03774@mt.sri.com>, Nate Williams writes: > >> > ! * If the LINK1 flag is set, it means the underlying interface > >> > ! * can do VLAN tag insertion itself and doesn't require us to > >> > ! * create a special header for it. In this case, we just pass > >> > >> Are we certain that all drivers are now doing if_media and no longer > >> using IFF_LINK1 for that purpose? > > > >I believe the old isa devices do not use if_media, but I could be > >wrong. (if_ep comes to mind....) > > And some new PCI devices doesn't either because if_media is hopelessly > narrowtrack for real world devices :-( As much as if_media sucks, it does have the ability to be extended in a fariety of useful ways. I'm fairly sure that once you get over the grotty mess of code needed to use it in a given driver it will offer a much better solution than the IFF_LINK[0-2] in terms of interface media selection. The fact that ifconfig can present a standard interface to the user without them having to reference manual pages to determine the semantics of the various link flags in the context of each different driver is an obvious win. From looking at the code I can't see how sys/net/if_vlan.c's use of LINK1 in any way impacts other code (in other drivers) that uses LINK1. (I can't see how its use of LINK1 as is accomplishes Bill's stated goals but still.) Might a new flag be used (I note that 0x0020 is unused) to indicate this information? What is the impact of increasing the width of if_flags from a short to an int? Files using IFF_LINK[0-2] and # of times present. dev/pdq/pdq_ifsubr.c:1 dev/ppbus/if_plip.c:2 dev/vx/if_vx.c:5 i386/isa/if_ar.c:1 i386/isa/if_ep.c:3 i386/isa/if_sr.c:3 i386/isa/if_wl.c:1 i386/isa/if_zp.c:3 net/if.h:4 net/if_slvar.h:3 net/if_spppsubr.c:2 net/if_vlan.c:2 net/bridge.c:1 net/bridge.h:1 net/if_vlan.c.orig:1 pc98/pc98/lpt.c:2 pci/if_de.c:4 pci/if_tx.c:13 i4b/driver/i4b_ipr.c:2 -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 11:11:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 214E815560 for ; Mon, 1 Mar 1999 11:11:06 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id LAA06645; Mon, 1 Mar 1999 11:10:47 -0800 (PST) (envelope-from obrien) Date: Mon, 1 Mar 1999 11:10:47 -0800 From: "David O'Brien" To: John Polstra Cc: current@freebsd.org Subject: Re: gcc Message-ID: <19990301111047.L3380@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <31170.920242197@zippy.cdrom.com> <19990228152909.E2170@relay.nuxi.com> <199903011715.JAA48969@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199903011715.JAA48969@vashon.polstra.com>; from John Polstra on Mon, Mar 01, 1999 at 09:15:03AM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What I have won't build kernels yet. I could hack our system Makefiles > > to use different compile options, but I don't like that approach. So > > I'm working on adding our compiler flags and such. > > Hang on. Others have reported success building kernels with egcs. > But even if there are problems, don't jump to the conclusion that > they are caused by compiler bugs. I hope I wasn't giving the impression there were compiler bugs. I was trying to say, I don't know what we'll find. The EGCS gcc I was working on would't compile src/bin/cat due to printf0 issues, and wouldn't compile a kernel due to -fformat-extension. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 11:11:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id A9BEE1560F for ; Mon, 1 Mar 1999 11:11:41 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:TwORiVoYGiqjPpbNqt/cBKJ1Hcb8lOCu@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id VAA66679; Mon, 1 Mar 1999 21:11:22 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:P4ShJpWOa2W5WyWx10z5TJoX21lrM4Ef@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id VAA64865; Mon, 1 Mar 1999 21:11:21 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199903011911.VAA64865@greenpeace.grondar.za> To: Thomas Dean Cc: freebsd-current@freebsd.org Subject: Re: egcs and gcc In-Reply-To: Your message of " Mon, 01 Mar 1999 10:06:58 PST." <199903011806.KAA56314@ix.netcom.com> References: <199903011806.KAA56314@ix.netcom.com> Date: Mon, 01 Mar 1999 21:11:20 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Dean wrote: > # file hello > hello: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), \ > dynamically linked, stripped > # time hello > Hello, world. > 0.02 real 0.00 user 0.02 sys Please add to that list the output of "ldd " for each executable. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 11:18: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9019615399 for ; Mon, 1 Mar 1999 11:18:01 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id LAA15360 for ; Mon, 1 Mar 1999 11:17:41 -0800 Date: Mon, 1 Mar 1999 11:17:40 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: freebsd-current@freebsd.org Subject: mangled top? 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 mean, I *did* do a complete world build but I still get: last pid: 409; load averages: 0.00, 0.00, 0.00 up 0+01:37:10 11:16:54 6 processes: 1 running CPU states: % user, % nice, % system, % interrupt, % idle Mem: 7344K Active, 33M Inact, 22M Wired, 5795K Buf, 61M Free Swap: 99M Total, 99M Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 65280 /+'+(0.+ -22 -52 1863M 528K ? -64 0 0:00 82292418.16% 82292418.16% -170012768 operator -22 -52 0K 1052K ? -120 0 0:00 9709.72% 1354.00% <> 409 100 88 63126 3944M 28K CPU0 0 0:00 3.00% 0.15% rpreter 0 40 -22 61505 0K 44K ? 96 0 0:00 0.00% 0.00% <> 1852400240 /*'''0/) -22 65556 3850M *)''*00*,K ? 24 0 0:00 0.00% 20141420 1 daemon -22 -52 0K 23148K ? -120 0 0:00 0.00% 196979612.50% <> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 11:35:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 0005615399 for ; Mon, 1 Mar 1999 11:35:19 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id UAA23546; Mon, 1 Mar 1999 20:34:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id UAA18963; Mon, 1 Mar 1999 20:34:37 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Matthew N. Dodd" Cc: Nate Williams , Garrett Wollman , Bill Paul , current@FreeBSD.ORG Subject: Re: Request for review: changes to if_vlan.c In-reply-to: Your message of "Mon, 01 Mar 1999 14:00:05 EST." Date: Mon, 01 Mar 1999 20:34:37 +0100 Message-ID: <18961.920316877@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "Matthe w N. Dodd" writes: >On Mon, 1 Mar 1999, Poul-Henning Kamp wrote: >> >> And some new PCI devices doesn't either because if_media is hopelessly >> narrowtrack for real world devices :-( > >As much as if_media sucks, it does have the ability to be extended in a >fariety of useful ways. Yes, but considering the low age of the interface, the fact that it was made so narrow-scope is a disgrace. Try to implement a E1 line with the full complement of options, including international bits and crc4 and what have you :-( It should have been done with a simple ascii string instead. The drivers are much better at chewing on it than the "generic" code, it would be simpler to understand, simpler to implement, you wouldn't need to rebuild ifconfig all the time and it would be vastly more flexible. Anyone who thinks this sounds like a replay from when I stuck my fingers in sysctl some years back are right. For some reason, some people around our camp-fire, have a hard time understanding that compiletime enumeration of potential options is a concept that died with the "VAX Handbook 1978 edition". Poul-Henning -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 11:51: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 62D0115422 for ; Mon, 1 Mar 1999 11:50:54 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id OAA29166; Mon, 1 Mar 1999 14:57:17 -0500 From: Bill Paul Message-Id: <199903011957.OAA29166@skynet.ctr.columbia.edu> Subject: Re: Request for review: changes to if_vlan.c To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Mon, 1 Mar 1999 14:57:16 -0500 (EST) Cc: current@FreeBSD.ORG In-Reply-To: <199903011633.LAA16808@khavrinen.lcs.mit.edu> from "Garrett Wollman" at Mar 1, 99 11:33:06 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 6692 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Garrett Wollman had to walk into mine and say: > < said: > > > Interested persons should review the diffs and pipe up if they have > > some passionate argument argument against them. > > Patches look mostly fine. Okay. I noticed one other thing while playing around today: when calling SIOCSETVLAN to disassociate a vlan interface with a real interface, the code should probably be removing the MAC address in addition to everything else. (The parent interface's address is added when the association is made, but not removed when the association is broken.) > > Also, I should point out that while if_vlan provides the necessary > > kernel hackery to implement VLANs, there isn't any user space utility > > for configuring vlan interfaces (ifconfig doesn't seem to have any > > vlan-specific code that I could see, and is no vlanconfig). > > I stopped development on vlan(4) when the switch we had that spoke > 802.1Q was returned to the vendor at the end of our demo period. I > have 28 on order right now, and should resume work on the driver after > I get those switches deployed. For interfaces like yours, I would > have preferred a subinterface mechanism, but I never had the time to > implement that. Well... correct me if I'm wrong, but the current code looks like it does implement "subinterfaces" of a fashion. I could hack the driver to do what if_vlan.c does, but why do that if if_vlan.c already exists and does almost exactly what I need it to do. > Care to implement GVRP while you're at it? Care to tell me what that is? :) (No, I don't really want to do it now, whatever it is.) > > There also is no vlan(4) man page. > > See above. I could probably write them myself, if you like. > > otherwise I'm going to take it upon myself to hack up ifconfig and > > write the man pages myself. > > I believe ifconfig is the wrong program for the task. There should be > a separate vlanconfig program. (I wrote one, but it's on my > laptop where I can't conveniently get to it right now.) I don't know about that. It seems to me ifconfig is precisely the right program to use for this task. I already hacked up a local copy of ifconfig to support it: router3# ./ifconfig vlan0 vlan 1234 vlandev ti0 router3# ./ifconfig vlan0 vlan0: flags=1843 mtu 1496 ether 00:60:08:21:53:6c vlan: 1234 parent interface: ti0 Took me only about an hour or so to do it (and I was watching TV at the time). Tell me why a separate program is preferable. > There are a couple of areas where vlan(4) needs to get some help from > the underlying driver: > > - Promiscuous mode doesn't work at all. It ought to be possible to > put just a specific VLAN into promiscuous mode, without affecting all > the others. This probably involves repeating all of the BPF > does-this-packet-look-like-mine? gluck from the physical interface > drivers. Hm. Well, it seems to me that the real problem is that to get promiscuous mode for the vlan interface, you have to put the parent in promiscuous mode too. You can do that, but then the parent interface driver gets hit with extra traffic that it doesn't want. > - Multicast is similarly broken (and a more serious weakness). There > needs to be a mechanism to pass multicast group membership down to the > underlying driver. It may also be necessary to do duplicate > suppression, which is a real challenge. It may not be that hard. I could probably do it, if you wanted me to. I wouldn't enjoy it, but I could do it. > > ! * If the LINK1 flag is set, it means the underlying interface > > ! * can do VLAN tag insertion itself and doesn't require us to > > ! * create a special header for it. In this case, we just pass > > Are we certain that all drivers are now doing if_media and no longer > using IFF_LINK1 for that purpose? I think you may have missed the point (or maybe I didn't explain it well). I want to set the LINK1 bit on the _VLAN_ interface (vlan0, etc...), _NOT_ the parent interface. The problem is that the parent doesn't want packets with the ethernet vlan header on them, and we need some way to tell the vlan intertface "Don't bother with rewriting the packet header; the parent interface will do it for you." Using the LINK1 (actually, I probably should have said LINK0; LINK1 was just the first thing that popped into my mind last night). The vlan interfaces don't use ifmedia so there is no conflict. The idea is, the user (er, admin) knows that he's going to be attaching to a parent device that can handle vlan header mangling internally, so he configures the vlan interfaces attached to this particular parent with a LINK flag that tells it "skip the header mangling". Nothing gets changed on the parent interface. > Grammar fault -- core dumped. > > (The wording was correct as it was.) That's why I didn't commit anything yet. > > * Set the interface MTU. > > + * This is bogus. The underlying interface might support > > + * jumbo frames. > > */ > > if (ifr->ifr_mtu > ETHERMTU) { > > error = EINVAL; > > I belong to the religion which as that if the interface is doing > ``jumbo frames'' than it's not doing ``Ethernet''. There are all > sorts of crocks which were perpretrated to allow bridging of FDDI and > Ethernet, and I have no intention of supporting the same crocks here. Well I belong to the religion that doesn't like to hear people whine and complain that "Linux supports this, why don't you?" This isn't to say that we should pay attention to everybody who complains since some of them are just out and out crackpots, but I happen to think the jumbo frame support is a big win (based on the performance stats I've seen). Maybe we can add another IFT type like IFT_JUMBOETHER and allow setting of larger MTUs only for IFT_JUMBOETHER interfaces. Hm, no wait... that won't work. A lot of code in /sys/net explicitly wants IFT_ETHER. I could change it to accept IFT_ETHER || IFT_JUMBOETHER though. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 11:58:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (Postfix) with ESMTP id 52C2115470 for ; Mon, 1 Mar 1999 11:58:22 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id OAA16064; Mon, 1 Mar 1999 14:54:09 -0500 (EST) Date: Mon, 1 Mar 1999 14:54:09 -0500 (EST) From: "Matthew N. Dodd" To: Poul-Henning Kamp Cc: Nate Williams , Garrett Wollman , Bill Paul , current@FreeBSD.ORG Subject: Re: Request for review: changes to if_vlan.c In-Reply-To: <18961.920316877@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Mar 1999, Poul-Henning Kamp wrote: > Yes, but considering the low age of the interface, the fact that it > was made so narrow-scope is a disgrace. True. It appears that it was a fairly focused solution for a very specific case of problem. (as you said) > Try to implement a E1 line with the full complement of options, > including international bits and crc4 and what have you :-( True, but try restricting yourself to using only the permutations available with IFF_LINK[0-2]. I'm sure that your E1 line driver will have a subset of options that are valid in the context if ifconfig. Other options are probably not necessary to present to the user via ifconfig and should be presented via some other means (sysctl?). > It should have been done with a simple ascii string instead. The > drivers are much better at chewing on it than the "generic" code, > it would be simpler to understand, simpler to implement, you wouldn't > need to rebuild ifconfig all the time and it would be vastly more > flexible. Indeed. My initial reply was rebuting your implied 'if_media sucks so we shouldn't attempt to convert the legacy code that uses IFF_LINK[0-2] to if_media'. While your are correct in your analysis of the shortcomings of if_media, shooting down this idea on those merits is not productive. Until a better solution for if_media is available, the if_media code does work and is a viable solution for a fairly specific class of problems. IFF_LINK[0-2] is even more broken than if_media. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 12:48:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 92234153C0 for ; Mon, 1 Mar 1999 12:48:26 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 23737 invoked from network); 1 Mar 1999 20:47:49 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by 209.43.20.203 with SMTP; 1 Mar 1999 20:47:49 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id PAA24587; Mon, 1 Mar 1999 15:46:25 -0500 (EST) Message-Id: <199903012046.PAA24587@y.dyson.net> Subject: Re: gcc In-Reply-To: <199903011715.JAA48969@vashon.polstra.com> from John Polstra at "Mar 1, 99 09:15:03 am" To: jdp@polstra.com (John Polstra) Date: Mon, 1 Mar 1999 15:46:25 -0500 (EST) Cc: obrien@NUXI.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 John Polstra said: > In article <19990228152909.E2170@relay.nuxi.com>, > David O'Brien wrote: > > > I keep on hearing about how we're losing because we don't have the 3 > > > month old latest feature > > > > With EGCS the issue isn't having the latest 3 mo. feature, but we have a > > totally BROKEN C++ compiler. > > Yes. We desperately need to upgrade our compiler, and egcs looks > like it's definitely the way to go. > > > What I have won't build kernels yet. I could hack our system Makefiles > > to use different compile options, but I don't like that approach. So > > I'm working on adding our compiler flags and such. > > Hang on. Others have reported success building kernels with egcs. > But even if there are problems, don't jump to the conclusion that > they are caused by compiler bugs. Linux also had problems building > working kernels at first, but the problems turned out to be caused by > incorrect clobber specs in "asm" statements. Such errors have also > been found in the FreeBSD kernel. Some of them have been fixed, but > maybe not all of them. In any case, the problems should be fixed at > their source, not kludged around in the compiler. > I can generally build a kernel with EGCS, if I change how the .text and .data are laid out for initialized data. It seems that the initialization code makes assumptions about the order or layout of the initialization data. Once the stuff is made to act more like the version of GCC that FreeBSD uses, the kernel will most often build and work. -- 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 Mar 1 13: 0:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id D861015403 for ; Mon, 1 Mar 1999 13:00:36 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id PAA52675; Mon, 1 Mar 1999 15:58:29 -0500 (EST) Date: Mon, 1 Mar 1999 15:58:29 -0500 (EST) From: Chuck Robey To: "John S. Dyson" Cc: John Polstra , obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: gcc In-Reply-To: <199903012046.PAA24587@y.dyson.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 Mon, 1 Mar 1999, John S. Dyson wrote: > I can generally build a kernel with EGCS, if I change how the .text and > .data are laid out for initialized data. It seems that the initialization > code makes assumptions about the order or layout of the initialization > data. Once the stuff is made to act more like the version of GCC that > FreeBSD uses, the kernel will most often build and work. I'd like to experiment ... Next time you go to the trouble of making a kernel with egcs, could you make a few notes on those changes, and post them? Thanks. ----------------------------+----------------------------------------------- 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 picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 13: 2:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id DDCC814FF4 for ; Mon, 1 Mar 1999 13:02:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA34732; Mon, 1 Mar 1999 12:58:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Poul-Henning Kamp Cc: John Polstra , current@FreeBSD.ORG Subject: Re: gcc In-reply-to: Your message of "Mon, 01 Mar 1999 18:17:13 +0100." <15359.920308633@critter.freebsd.dk> Date: Mon, 01 Mar 1999 12:58:31 -0800 Message-ID: <34728.920321911@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Wouldn't the first logical step be to stop generating the a.out libs > in make world, and check in the "final version" like with the rest > of the compat libs ? Yes, I was sort of hoping that the same person who did the other compat* dists would jump in with that, but he's ignored my broad hints on this topic so far and what I ended up releasing as compat22 was just a snapshot of hub's a.out libraries. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 13:21:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B4D1215463 for ; Mon, 1 Mar 1999 13:21:28 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id WAA82163 for current@freebsd.org; Mon, 1 Mar 1999 22:21:05 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903012121.WAA82163@freebsd.dk> Subject: CALL FOR TESTERS of new ATA/ATAPI driver.. To: current@freebsd.org Date: Mon, 1 Mar 1999 22:21:05 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Finally!! The much roumored replacement for our current IDE/ATA/ATAPI is materialising in the CVS repositories around the globe. So what does this bring us: A new reengineered ATA/ATAPI subsystem, that tries to overcome most of the deficiencies with the current drivers. It supports PCI as well as ISA devices without all the hackery in ide_pci.c to make PCI devices look like ISA counterparts. It doesn't have the excessive wait problem on probe, in fact you shouldn't notice any delay when your devices are getting probed. Probing and attaching of devices are postponed until interrupts are enabled (well almost, not finished yet for disks), making things alot cleaner. Improved performance, although DMA support is still WIP and not in this pre alpha release, worldstone is faster with the new driver compared to the old even with DMA. So what does it take away: There is NO support for old MFM/RLL/ESDI disks. There is NO support for bad144, if your disk is bad, ditch it, it has already outgrown its internal spare sectors, and is dying. For you to try this out, you will have to modify your kernel config file to use the "ata" controller instead of all wdc? entries. example: # for a PCI only system (most modern machines) controller ata0 device atadisk0 # ATA disks device atapicd0 # ATAPI CDROM's device atapist0 # ATAPI tapes #You should add the following on ISA systems: controller ata1 at isa? port "IO_WD1" bio irq 14 controller ata2 at isa? port "IO_WD2" bio irq 15 You can leave it all in there, the system knows how to manage. For now this driver reuses the device entries from the old system (that will probably change later), but remember that disks are now numbered in the sequence they are found (like the SCSI system) not as absolute positions as the old system. Although I have tested this on all the systems I can get my hands on, there might very well be gremlins in there, so use AT YOU OWN RISK!! This is still WIP, so there are lots of rough edges and unfinished things in there, and what I have in my lab might look very different from whats in CVS at any given time. So please have all eventual changes go through me, or chances are they just dissapears... I would very much like to hear from you, both good and bad news are very welcome. Enjoy!! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 13:29: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 8AE27154B1 for ; Mon, 1 Mar 1999 13:28:52 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA34883; Mon, 1 Mar 1999 13:28:36 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: dyson@iquest.net Cc: jdp@polstra.com (John Polstra), obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: gcc In-reply-to: Your message of "Mon, 01 Mar 1999 15:46:25 EST." <199903012046.PAA24587@y.dyson.net> Date: Mon, 01 Mar 1999 13:28:36 -0800 Message-ID: <34879.920323716@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I can generally build a kernel with EGCS, if I change how the .text and > .data are laid out for initialized data. It seems that the initialization > code makes assumptions about the order or layout of the initialization > data. Once the stuff is made to act more like the version of GCC that > FreeBSD uses, the kernel will most often build and work. It really does appear to be a simple matter of first making egcs "take over" the system compiler: # cd /usr/ports/lang/egcs # make all install PREFIX=/usr # ln -fs /usr/bin/eg++ /usr/bin/c++ # ln -fs /usr/bin/egcc /usr/bin/cc # cd /usr/src remove cc from /usr/src/gnu/usr.bin/Makefile SUBDIR list remove libstdc++ and libobjc from /usr/src/gnu/lib/Makefile SUBDIR list Then make the world and the kernel. I also haven't noticed that the executables are any smaller or larger either way, and I've captured a fair amount of "cc -v" output to ensure that egcs is, in fact, the compiler being used. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 13:37:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 735F0153A0 for ; Mon, 1 Mar 1999 13:37:09 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA07508 for current@FreeBSD.ORG; Mon, 1 Mar 1999 13:36:52 -0800 (PST) (envelope-from obrien) Date: Mon, 1 Mar 1999 13:36:52 -0800 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: gcc Message-ID: <19990301133652.A7483@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199903012046.PAA24587@y.dyson.net> <34879.920323716@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <34879.920323716@zippy.cdrom.com>; from Jordan K. Hubbard on Mon, Mar 01, 1999 at 01:28:36PM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > data. Once the stuff is made to act more like the version of GCC that > > FreeBSD uses, the kernel will most often build and work. > > It really does appear to be a simple matter of first making egcs "take over" > the system compiler: I have the bmake framework that will allow us to properly drop-in egcs. I expect to put it up for FTP this evening. (libstdc++ still needs a little bit more work) -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 13:51:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 5318715446 for ; Mon, 1 Mar 1999 13:50:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA34998; Mon, 1 Mar 1999 13:49:45 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@NUXI.com Cc: current@FreeBSD.ORG Subject: Re: gcc In-reply-to: Your message of "Mon, 01 Mar 1999 13:36:52 PST." <19990301133652.A7483@relay.nuxi.com> Date: Mon, 01 Mar 1999 13:49:45 -0800 Message-ID: <34995.920324985@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have the bmake framework that will allow us to properly drop-in egcs. > I expect to put it up for FTP this evening. > (libstdc++ still needs a little bit more work) VERY useful! Thanks, I look forward to seeing that. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 13:57:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 1C354153B6 for ; Mon, 1 Mar 1999 13:57:41 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 12841 invoked from network); 1 Mar 1999 21:57:23 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 1 Mar 1999 21:57:23 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id QAA24740; Mon, 1 Mar 1999 16:57:20 -0500 (EST) Message-Id: <199903012157.QAA24740@y.dyson.net> Subject: Re: gcc In-Reply-To: <34879.920323716@zippy.cdrom.com> from "Jordan K. Hubbard" at "Mar 1, 99 01:28:36 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Mon, 1 Mar 1999 16:57:20 -0500 (EST) Cc: dyson@iquest.net, jdp@polstra.com, obrien@NUXI.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 Jordan K. Hubbard said: > > I can generally build a kernel with EGCS, if I change how the .text and > > .data are laid out for initialized data. It seems that the initialization > > code makes assumptions about the order or layout of the initialization > > data. Once the stuff is made to act more like the version of GCC that > > FreeBSD uses, the kernel will most often build and work. > > It really does appear to be a simple matter of first making egcs "take over" > the system compiler: > Okay, I guess I have been missing something :-). -- 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 Mar 1 14:11: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 12F9314EA2 for ; Mon, 1 Mar 1999 14:10:59 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id OAA24321; Mon, 1 Mar 1999 14:10:38 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id OAA49598; Mon, 1 Mar 1999 14:10:37 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199903012157.QAA24740@y.dyson.net> Date: Mon, 01 Mar 1999 14:10:37 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: "John S. Dyson" Subject: Re: gcc Cc: current@FreeBSD.ORG, obrien@NUXI.com, (Jordan K. Hubbard) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John S. Dyson wrote: > Jordan K. Hubbard said: >> > I can generally build a kernel with EGCS, if I change how the .text and >> > .data are laid out for initialized data. It seems that the initialization >> > code makes assumptions about the order or layout of the initialization >> > data. Once the stuff is made to act more like the version of GCC that >> > FreeBSD uses, the kernel will most often build and work. >> >> It really does appear to be a simple matter of first making egcs "take over" >> the system compiler: >> > Okay, I guess I have been missing something :-). Keep in mind that a whole bunch of stuff connected with kernel initialization has been changed lately. It may be simply that you're dealing with an older vintage kernel. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 14:16:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id D3BF6154D8 for ; Mon, 1 Mar 1999 14:16:48 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 2740 invoked from network); 1 Mar 1999 22:15:21 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 1 Mar 1999 22:15:21 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id RAA24795; Mon, 1 Mar 1999 17:15:19 -0500 (EST) Message-Id: <199903012215.RAA24795@y.dyson.net> Subject: Re: gcc In-Reply-To: from Chuck Robey at "Mar 1, 99 03:58:29 pm" To: chuckr@mat.net (Chuck Robey) Date: Mon, 1 Mar 1999 17:15:19 -0500 (EST) Cc: dyson@iquest.net, jdp@polstra.com, obrien@NUXI.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 Chuck Robey said: > On Mon, 1 Mar 1999, John S. Dyson wrote: > > > I can generally build a kernel with EGCS, if I change how the .text and > > .data are laid out for initialized data. It seems that the initialization > > code makes assumptions about the order or layout of the initialization > > data. Once the stuff is made to act more like the version of GCC that > > FreeBSD uses, the kernel will most often build and work. > > I'd like to experiment ... Next time you go to the trouble of making a > kernel with egcs, could you make a few notes on those changes, and post > them? > Okay, but JKH isn't having troubles... Hmmm... I do work with the latest CVS checkout on egcs, so there could be a minor difference there. I might play with it tonight, and I do have a generally working copy of egcs-current right now... If it isn't tonight, will be tomorrow. -- 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 Mar 1 14:19:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id A50A8154D7 for ; Mon, 1 Mar 1999 14:19:24 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 6000 invoked from network); 1 Mar 1999 22:18:37 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 1 Mar 1999 22:18:37 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id RAA24825; Mon, 1 Mar 1999 17:18:35 -0500 (EST) Message-Id: <199903012218.RAA24825@y.dyson.net> Subject: Re: gcc In-Reply-To: from John Polstra at "Mar 1, 99 02:10:37 pm" To: jdp@polstra.com (John Polstra) Date: Mon, 1 Mar 1999 17:18:35 -0500 (EST) Cc: dyson@iquest.net, current@FreeBSD.ORG, obrien@NUXI.com, jkh@zippy.cdrom.com From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra said: > John S. Dyson wrote: > > Jordan K. Hubbard said: > >> > I can generally build a kernel with EGCS, if I change how the .text and > >> > .data are laid out for initialized data. It seems that the initialization > >> > code makes assumptions about the order or layout of the initialization > >> > data. Once the stuff is made to act more like the version of GCC that > >> > FreeBSD uses, the kernel will most often build and work. > >> > >> It really does appear to be a simple matter of first making egcs "take over" > >> the system compiler: > >> > > Okay, I guess I have been missing something :-). > > Keep in mind that a whole bunch of stuff connected with kernel > initialization has been changed lately. It may be simply that you're > dealing with an older vintage kernel. > Ahhaaa... That must be it -- I have a parallel track VM system project going. -- 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 Mar 1 14:46:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (Postfix) with ESMTP id 1413B15457 for ; Mon, 1 Mar 1999 14:46:05 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id QAA15321 for ; Mon, 1 Mar 1999 16:45:45 -0600 (CST) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.6.13/8.6.4) with ESMTP id QAA11269 for ; Mon, 1 Mar 1999 16:41:30 -0600 Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id QAA24387; Mon, 1 Mar 1999 16:45:13 -0600 (CST) Date: Mon, 1 Mar 1999 16:45:13 -0600 (CST) From: Jonathan Lemon Message-Id: <199903012245.QAA24387@free.pcs> To: freebsd-current@freebsd.org Subject: Re: gcc X-Newsgroups: local.mail.freebsd-current In-Reply-To: References: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >In message <199903011709.JAA48942@vashon.polstra.com>, John Polstra writes: >>In article <31122.920241640@zippy.cdrom.com>, >>Jordan K. Hubbard wrote: >>> >>> I'd personally be happy with an egcs that just did sensible things >>> with ELF, >> >>Me too. We _must_ not let a.out become a ball and chain. We have >>stressed over and over all along that we were not going to become a >>dual-object-format OS. That means we _must_ be willing to abandon >>a.out support for new code. We will keep the legacy a.out libraries >>for old applications to link against, but we don't have to keep the >>ability to generate new ones. To do so would hold us back (_is_ >>holding us back) with very little to show for it. > >Wouldn't the first logical step be to stop generating the a.out libs >in make world, and check in the "final version" like with the rest >of the compat libs ? How about getting profiling working for ELF kernels before before completely abandoning a.out? -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 14:56: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 67DA815588 for ; Mon, 1 Mar 1999 14:55:30 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id RAA65139; Mon, 1 Mar 1999 17:53:51 -0500 (EST) Date: Mon, 1 Mar 1999 17:53:50 -0500 (EST) From: Chuck Robey To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: gcc In-Reply-To: <34879.920323716@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Mar 1999, Jordan K. Hubbard wrote: > > I can generally build a kernel with EGCS, if I change how the .text and > > .data are laid out for initialized data. It seems that the initialization > > code makes assumptions about the order or layout of the initialization > > data. Once the stuff is made to act more like the version of GCC that > > FreeBSD uses, the kernel will most often build and work. > > It really does appear to be a simple matter of first making egcs "take over" > the system compiler: > > # cd /usr/ports/lang/egcs > # make all install PREFIX=/usr > # ln -fs /usr/bin/eg++ /usr/bin/c++ > # ln -fs /usr/bin/egcc /usr/bin/cc > # cd /usr/src > remove cc from /usr/src/gnu/usr.bin/Makefile SUBDIR list > remove libstdc++ and libobjc from /usr/src/gnu/lib/Makefile SUBDIR list > > Then make the world and the kernel. I also haven't noticed that the > executables are any smaller or larger either way, and I've captured a > fair amount of "cc -v" output to ensure that egcs is, in fact, the > compiler being used. :) Didn't realize that was all there was. Thanks a lot, Jordan, I will start doing egcs testing tonight, and from now on, using the latest egcs port (fetching now). ----------------------------+----------------------------------------------- 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 picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 15: 9:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id BF7C9153ED for ; Mon, 1 Mar 1999 15:09:19 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id JAA02491; Tue, 2 Mar 1999 09:38:01 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 02 Mar 1999 09:38:01 +1030 (CST) From: "Daniel O'Connor" To: Matthew Jacob Subject: RE: mangled top? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 01-Mar-99 Matthew Jacob wrote: > I mean, I *did* do a complete world build but I still get: Your kernel is old? ie a new world and an old kernel give the same weirdness as an old world and a new kernel :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 15:11:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from bolero-x.rahul.net (bolero.rahul.net [192.160.13.1]) by hub.freebsd.org (Postfix) with SMTP id 02E6A1549F for ; Mon, 1 Mar 1999 15:10:44 -0800 (PST) (envelope-from dhesi@rahul.net) Received: from waltz.rahul.net by bolero-x.rahul.net with SMTP id AA16241 (5.67b8/IDA-1.5 for ); Mon, 1 Mar 1999 15:10:27 -0800 Received: by waltz.rahul.net (5.67b8/jive-a2i-1.0) id AA22894; Mon, 1 Mar 1999 15:10:21 -0800 Message-Id: <199903012310.AA22894@waltz.rahul.net> To: current@FreeBSD.ORG Subject: Re: lockmgr panic with mmap() In-Reply-To: Message from Matthew Dillon of Sun, 28 Feb 99 12:40:18 -0800 Date: Mon, 01 Mar 99 15:10:21 -0800 From: Rahul Dhesi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Admittedly detecting deadlock is not trivial in general. But if we are about to panic because of deadlock, then we have already detected something. The question now is: Do we crash the whole system, or just one or two user processes? Rahul > :Since bugs do happen, deadlock can occur in the kernel. > : > :Is it not possible in such cases to simply detect the deadlock, and kill > :one of the user processes involved in the deadlock, thus releasing one > :of the resources involved in the deadlock? Then you would log > :diagnostic information and let the system continue normally.... > Most of the deadlocks remaining in the kernel are more complex and often > cannot be detected without significant new work.... > Detecting the loop is the hard part. This is known as 'deadlock > detection'... ... > In FreeBSD's case, the issue is somewhat more complex due to things > that are not strictly locks causing deadlocks - such as a low memory > condition causing a process holding an inode lock to block and then the > syncer blocking on the same inode. The syncer is thus unable to run and > thus unable to sync the dirty buffers clogging memory to disk. Things > like that. > > -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 16: 4: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id C46381548A for ; Mon, 1 Mar 1999 16:03:44 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.3/8.9.1) with ESMTP id DAA02449; Tue, 2 Mar 1999 03:01:22 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Tue, 2 Mar 1999 03:01:22 +0300 (MSK) From: oZZ!!! To: =?KOI8-R?Q?S=F8ren_Schmidt?= Cc: current@FreeBSD.ORG Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-Reply-To: <199903012121.WAA82163@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 > controller ata0 > device atadisk0 # ATA disks > device atapicd0 # ATAPI CDROM's > After (fastest(!!!)) boot: $ dmesg ...... chip1: rev 0x01 on pci0.7.0 ata-pci0: rev 0x01 on pci0.7.1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ............... ad0: ATA-3 disk at ata0 as master ad0: 2503MB (5126964 sectors), 5086 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue ad1: ATA-? disk at ata1 as master ^^^^^ ???? ad1: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue acd0: CDROM drive at ata1 as slave acd0: drive speed 689KB/sec, 128KB cache acd0: supported read types: CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked changing root device to ad0s1a ......... ATA-? ??? ^^^^^ Does it right? How i can create ad0s1a & etc. slises? i can't find anythink in /usr/src/etc/etc.i386/MAKEDEV... Rgdz, Sergey A. Osokin, 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 Mon Mar 1 16:44:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa15-25.ix.netcom.com [207.93.148.25]) by hub.freebsd.org (Postfix) with ESMTP id 9CF8615450 for ; Mon, 1 Mar 1999 16:43:18 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id QAA57349; Mon, 1 Mar 1999 16:42:43 -0800 (PST) (envelope-from tomdean) Date: Mon, 1 Mar 1999 16:42:43 -0800 (PST) Message-Id: <199903020042.QAA57349@ix.netcom.com> From: Thomas Dean To: mark@grondar.za Cc: freebsd-current@freebsd.org In-reply-to: <199903011911.VAA64865@greenpeace.grondar.za> (message from Mark Murray on Mon, 01 Mar 1999 21:11:20 +0200) Subject: Re: egcs and gcc Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As suspected, eg++ is using libstdc++.a, not libstdc++.so.2, as it should. How does this get fixed? tomdean ============================================== # g++ -m486 -O2 hello.cc -o hello # ldd hello hello: libg++.so.4 => /usr/lib/libg++.so.4 (0x28051000) libstdc++.so.2 => /usr/lib/libstdc++.so.2 (0x28093000) libm.so.2 => /usr/lib/libm.so.2 (0x280ce000) libc.so.3 => /usr/lib/libc.so.3 (0x280e9000) # eg++ -m486 -O2 hello.cc -o hello # ldd hello hello: libm.so.2 => /usr/lib/libm.so.2 (0x2805e000) libc.so.3 => /usr/lib/libc.so.3 (0x28079000) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 16:55:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 7F204154CB for ; Mon, 1 Mar 1999 16:55:27 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id TAA04502; Mon, 1 Mar 1999 19:53:07 -0500 (EST) Date: Mon, 1 Mar 1999 19:53:07 -0500 (EST) From: Chuck Robey To: Thomas Dean Cc: mark@grondar.za, freebsd-current@FreeBSD.ORG Subject: Re: egcs and gcc In-Reply-To: <199903020042.QAA57349@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 On Mon, 1 Mar 1999, Thomas Dean wrote: > As suspected, eg++ is using libstdc++.a, not libstdc++.so.2, as it > should. > > How does this get fixed? I just noticed that the egcs Makefile has a buried: .if defined(WANT_SHAREDLIBS) CONFIGURE_ARGS+= --enable-shared .endif in it. That's not particularly friendly, I wonder why it was put in there, unless the feature is somehow broken? I'm trying to rebuild it now to see what it then installs. > > tomdean > > ============================================== > > # g++ -m486 -O2 hello.cc -o hello > # ldd hello > hello: > libg++.so.4 => /usr/lib/libg++.so.4 (0x28051000) > libstdc++.so.2 => /usr/lib/libstdc++.so.2 (0x28093000) > libm.so.2 => /usr/lib/libm.so.2 (0x280ce000) > libc.so.3 => /usr/lib/libc.so.3 (0x280e9000) > > # eg++ -m486 -O2 hello.cc -o hello > # ldd hello > hello: > libm.so.2 => /usr/lib/libm.so.2 (0x2805e000) > libc.so.3 => /usr/lib/libc.so.3 (0x28079000) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 17:54:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163]) by hub.freebsd.org (Postfix) with SMTP id 374C4153B2 for ; Mon, 1 Mar 1999 17:54:05 -0800 (PST) (envelope-from tr49986@rcc.on.ca) Received: from a35 ([207.164.233.121]) by speed.rcc.on.ca (8.6.12/8.6.9) with SMTP id WAA32221 for ; Mon, 1 Mar 1999 22:07:41 -0500 Message-ID: <004f01be644f$239ae3e0$2300000a@a35.my.intranet> From: "RT" To: Subject: Still NFS Problems Date: Mon, 1 Mar 1999 20:51:05 -0500 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.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the past 3 weeks I've upgraded from 3.0-release, to 3-stable to 4-current (as of 4 days ago). I've tried nfs v2 and nfs v3. In all of those circumstances I end up with programs locking due to write problems. I'm no good a debugging, so if someone could hold my hand through this one... Basic problem. .nfs798798 files appearing on server, program on client locks up in STAT 'D' according to top. The problem only occurs on read / write mounts (duh..). I only have my home partition writable as of right now. The easiest way to replicate it is to compile something large. i.e. make world from the client machine. Soon I'll just make my home directory read only too :) Any ideas? fixes? things I can show you? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 18: 4: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa15-25.ix.netcom.com [207.93.148.25]) by hub.freebsd.org (Postfix) with ESMTP id 6D68215400 for ; Mon, 1 Mar 1999 18:03:57 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id SAA57649; Mon, 1 Mar 1999 18:03:32 -0800 (PST) (envelope-from tomdean) Date: Mon, 1 Mar 1999 18:03:32 -0800 (PST) Message-Id: <199903020203.SAA57649@ix.netcom.com> From: Thomas Dean To: chuckr@mat.net Cc: mark@grondar.za, freebsd-current@FreeBSD.ORG In-reply-to: (message from Chuck Robey on Mon, 1 Mar 1999 19:53:07 -0500 (EST)) Subject: Re: egcs and gcc Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG # pwd; ls /usr/local/lib/gcc-lib/i386-unknown-freebsd4.0/egcs-2.91.60 SYSCALLS.c.X collect2* crtend.o libg2c.a libstdc++.a cc1* cpp* crtendS.o libgcc.a specs cc1obj* crtbegin.o f771* libiberty.a cc1plus* crtbeginS.o include/ libobjc.a No shared libs! My Makefile has 'enable_shared = no' From the docs (/usr/ports/lang/egcs/work/egcs-1.1.1/INSTALL) CONFIGURE * --enable-shared -- Build shared versions of the C++ runtime libraries if supported --disable-shared is the default. Looks like the port needs to be patched to enable shared, run configure with --enable-shared. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 18:11:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7412C153F2 for ; Mon, 1 Mar 1999 18:11:38 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id SAA11595; Mon, 1 Mar 1999 18:10:54 -0800 (PST) (envelope-from obrien) Date: Mon, 1 Mar 1999 18:10:53 -0800 From: "David O'Brien" To: Chuck Robey Cc: Thomas Dean , mark@grondar.za, freebsd-current@FreeBSD.ORG Subject: Re: egcs and gcc Message-ID: <19990301181053.A11564@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199903020042.QAA57349@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Chuck Robey on Mon, Mar 01, 1999 at 07:53:07PM -0500 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > .if defined(WANT_SHAREDLIBS) > CONFIGURE_ARGS+= --enable-shared > .endif > > in it. That's not particularly friendly, I wonder why it was put in > there, unless the feature is somehow broken? I'm trying to rebuild it > now to see what it then installs. Because people like a previous poster thinks that eg++ should like against /usr/lib/libstdc++.so.2 which is plain WRONG. eg++ is totally incompatable with g++ 2.7.x. So what happens when you move an eg++ produced binary to a machine that doesn't have EGCS installed? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 18:12:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id DFD3C14C18 for ; Mon, 1 Mar 1999 18:12:51 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id SAA11610; Mon, 1 Mar 1999 18:12:27 -0800 (PST) (envelope-from obrien) Date: Mon, 1 Mar 1999 18:12:24 -0800 From: "David O'Brien" To: Thomas Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: egcs and gcc Message-ID: <19990301181224.B11564@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199903011911.VAA64865@greenpeace.grondar.za> <199903020042.QAA57349@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199903020042.QAA57349@ix.netcom.com>; from Thomas Dean on Mon, Mar 01, 1999 at 04:42:43PM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As suspected, eg++ is using libstdc++.a, not libstdc++.so.2, as it > should. NO it should NOT! libstdc++.so.2 is matched to g++ 2.7.2.x, NOT egcs. This point is why I won't make the EGCS port have a shared libstdc++ by default. What happens when you move an eg++ produced binary to a machine w/o EGCS installed? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 18:33:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa15-25.ix.netcom.com [207.93.148.25]) by hub.freebsd.org (Postfix) with ESMTP id A2B1B14C34 for ; Mon, 1 Mar 1999 18:32:16 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id SAA57747; Mon, 1 Mar 1999 18:31:51 -0800 (PST) (envelope-from tomdean) Date: Mon, 1 Mar 1999 18:31:51 -0800 (PST) Message-Id: <199903020231.SAA57747@ix.netcom.com> From: Thomas Dean To: obrien@NUXI.com Cc: freebsd-current@FreeBSD.ORG In-reply-to: <19990301181053.A11564@relay.nuxi.com> (obrien@NUXI.com) Subject: Re: egcs and gcc Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... > eg++ is totally incompatable with g++ 2.7.x. ... > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) Aha! Thanks, tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 18:37:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 27823154EE for ; Mon, 1 Mar 1999 18:37:32 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id SAA17096; Mon, 1 Mar 1999 18:37:04 -0800 Date: Mon, 1 Mar 1999 18:37:03 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Daniel O'Connor" Cc: freebsd-current@FreeBSD.ORG Subject: RE: mangled top? 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 Nope, new kernel. On Tue, 2 Mar 1999, Daniel O'Connor wrote: > > On 01-Mar-99 Matthew Jacob wrote: > > I mean, I *did* do a complete world build but I still get: > Your kernel is old? > ie a new world and an old kernel give the same weirdness as an old world and a new kernel > :) > > --- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 18:41:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 0FAB614C5A for ; Mon, 1 Mar 1999 18:40:58 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-15-244.dialup.HiWAAY.net [216.180.15.244]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id UAA10503; Mon, 1 Mar 1999 20:40:40 -0600 (CST) Received: from nospam.hiwaay.net (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.2/8.9.2) with ESMTP id UAA02018; Mon, 1 Mar 1999 20:40:37 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199903020240.UAA02018@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: S ren Schmidt Cc: current@FreeBSD.ORG From: David Kelly Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-reply-to: Message from S ren Schmidt of "Mon, 01 Mar 1999 22:21:05 +0100." <199903012121.WAA82163@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 01 Mar 1999 20:40:37 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG S ren Schmidt writes: > There is NO support for bad144, if your disk is bad, ditch it, it has > already outgrown its internal spare sectors, and is dying. Speaking of which, is there any portable way to monitor bad block lists = on ATA drives? And the S.M.A.R.T. stuff that some vendors advertise? -- David Kelly N4HHE, dkelly@nospam.hiwaay.net =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 19:12:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 2135F14C35 for ; Mon, 1 Mar 1999 19:12:38 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id WAA12125; Mon, 1 Mar 1999 22:10:55 -0500 (EST) Date: Mon, 1 Mar 1999 22:10:54 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= Cc: current@FreeBSD.ORG Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-Reply-To: <199903012121.WAA82163@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 Do you have any plans to move the wfd(4) driver to the new ATA framework? I'd be glad to test it all out, as long as I don't lose my LS-120's functionality. Thanks in advance! Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 19:13: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id A4B4615402 for ; Mon, 1 Mar 1999 19:13:04 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id WAA00438; Mon, 1 Mar 1999 22:10:34 -0500 (EST) Date: Mon, 1 Mar 1999 22:10:34 -0500 (EST) From: Chuck Robey To: "David O'Brien" Cc: Thomas Dean , mark@grondar.za, freebsd-current@FreeBSD.ORG Subject: Re: egcs and gcc In-Reply-To: <19990301181053.A11564@relay.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Mar 1999, David O'Brien wrote: > > .if defined(WANT_SHAREDLIBS) > > CONFIGURE_ARGS+= --enable-shared > > .endif > > > > in it. That's not particularly friendly, I wonder why it was put in > > there, unless the feature is somehow broken? I'm trying to rebuild it > > now to see what it then installs. > > Because people like a previous poster thinks that eg++ should like > against /usr/lib/libstdc++.so.2 which is plain WRONG. eg++ is totally > incompatable with g++ 2.7.x. So what happens when you move an eg++ > produced binary to a machine that doesn't have EGCS installed? OK, but listing from my gcc-lib/i386-unknown-freebsd4.0/egcs-2.91.62 gives: SYSCALLS.c.X crtbeginS.o libiberty.a cc1* crtend.o libobjc.a cc1obj* crtendS.o libstdc++.a cc1plus* f771* libstdc++.so@ collect2* include/ libstdc++.so.2.9@ cpp* libg2c.a libstdc++.so.2.9.0* crtbegin.o libgcc.a specs (I compiled this with the WANT_SHAREDLIBS on). It seems to make a libstdc++.so.2.9 .... my first guess is, we'd want to bump the number so that it fits the form for our loader (one rev number, not two) and use it like the old one. It's the new form, done for egcs, it should work, right? If you move it to a machine without version 3 installed, it'll complain, right? I'm learning here, don't get upset if I'm all wet. Another thing I note is that, unlike all the rest of the snapshots of egcs, the pre-release version (and seemingly only the prerelease version) that the port uses has gcj, the java tool, cut out. That seems kind of a shame, doesn't it? I tried taking the gcj part out of the latest egcs snap, and dropping it inplace in the prerelease version. Cygnus supplies the tarball for the gcc/java directory separately (if you want it), bless them! It configures ok (I *think*) with --enable-java, but it won't finish compiling. It's Makefile isn't correct, doesn't have a rule for an object file gcj needs (lost the error listing, I just had a freezeup). I'm out of time tonight. I think you're telling me to redo my egcs install with the WANT_SHAREDLIBS off, right? And you're going to have the libstdc++ ported (I read that, right?) so I should just maybe be patient? ----------------------------+----------------------------------------------- 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 picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 19:22:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8E7CB154B0 for ; Mon, 1 Mar 1999 19:22:29 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id TAA12491; Mon, 1 Mar 1999 19:22:10 -0800 (PST) (envelope-from obrien) Date: Mon, 1 Mar 1999 19:22:10 -0800 From: "David O'Brien" To: Chuck Robey Cc: freebsd-current@FreeBSD.ORG Subject: Re: egcs and gcc Message-ID: <19990301192210.A12466@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990301181053.A11564@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Chuck Robey on Mon, Mar 01, 1999 at 10:10:34PM -0500 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 01, 1999 at 10:10:34PM -0500, Chuck Robey wrote: > I tried taking the gcj part out of the latest egcs snap, and dropping it > inplace in the prerelease version. Grab ftp://ftp.nuxi.com/pub/FreeBSD/egcs-devel-port-990228.tar.gz if you want a portball for the latest snapshot of EGCS. I peroidically make a egcs-devel port just to keep up on things and see what changes I've submitted have made it into their tree. > I'm out of time tonight. I think you're telling me to redo my egcs > install with the WANT_SHAREDLIBS off, right? Either way should be ok for testing. > And you're going to have the libstdc++ ported (I read that, right?) so > I should just maybe be patient? Yep. :-) -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 19:26:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 530CE14C0F for ; Mon, 1 Mar 1999 19:26:28 -0800 (PST) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id TAA62512; Mon, 1 Mar 1999 19:25:32 -0800 (PST) (envelope-from mantar@pacbell.net) Message-Id: <4.2.0.25.19990301191722.00a50100@216.101.162.50> X-Sender: null@216.101.162.50 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.25 (Beta) Date: Mon, 01 Mar 1999 19:25:32 -0800 To: "Jordan K. Hubbard" , dyson@iquest.net From: Manfred Antar Subject: Re: gcc Cc: jdp@polstra.com (John Polstra), obrien@NUXI.com, current@FreeBSD.ORG In-Reply-To: <34879.920323716@zippy.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:28 PM 3/1/99 -0800, Jordan K. Hubbard wrote: >> I can generally build a kernel with EGCS, if I change how the .text and >> .data are laid out for initialized data. It seems that the initialization >> code makes assumptions about the order or layout of the initialization >> data. Once the stuff is made to act more like the version of GCC that >> FreeBSD uses, the kernel will most often build and work. > >It really does appear to be a simple matter of first making egcs "take over" >the system compiler: > ># cd /usr/ports/lang/egcs ># make all install PREFIX=/usr ># ln -fs /usr/bin/eg++ /usr/bin/c++ ># ln -fs /usr/bin/egcc /usr/bin/cc ># cd /usr/src >remove cc from /usr/src/gnu/usr.bin/Makefile SUBDIR list >remove libstdc++ and libobjc from /usr/src/gnu/lib/Makefile SUBDIR list > >Then make the world and the kernel. I also haven't noticed that the >executables are any smaller or larger either way, and I've captured a >fair amount of "cc -v" output to ensure that egcs is, in fact, the >compiler being used. :) > >- Jordan Doesn't this just rebuild the standard gcc compiler in /usr/obj/usr/tmp/bin as part of the tools build, then use that compiler to build world. The first builds are done with egcs then it moves over to gcc to build the world. by removing the above from the Makfiles just prevents them from getting built and installed in the final build. when I do /usr/obj/usr/src/tmp/bin/cc --version it comes out gcc 2.7.2.1 Or am I missing something here ?? ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 19:48:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from ianai.BlackSun.org (Ianai.blacksun.org [168.100.186.33]) by hub.freebsd.org (Postfix) with ESMTP id 3DF5A14D14 for ; Mon, 1 Mar 1999 19:46:46 -0800 (PST) (envelope-from tugrul@ianai.BlackSun.org) Received: from localhost (tugrul@localhost) by ianai.BlackSun.org (8.8.8/8.8.7) with SMTP id WAA25540; Mon, 1 Mar 1999 22:39:52 -0500 (EST) (envelope-from tugrul@ianai.BlackSun.org) Date: Mon, 1 Mar 1999 22:39:52 -0500 (EST) From: Tugrul To: Søren Schmidt Cc: current@FreeBSD.ORG Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-Reply-To: <199903012121.WAA82163@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 The new driver fails to build when devfs is also in the config. I made a simple change of "static void *devfs_token" to "void *devfs_token" on line 183 in ata-all.h and all seems good. Good work, no more stinky delay :-) Tugrul Galatali To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 19:51:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id C7D3815572 for ; Mon, 1 Mar 1999 19:51:24 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id WAA14630; Mon, 1 Mar 1999 22:50:39 -0500 (EST) Date: Mon, 1 Mar 1999 22:50:39 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Chuck Robey Cc: "David O'Brien" , Thomas Dean , mark@grondar.za, freebsd-current@FreeBSD.ORG Subject: Re: egcs and gcc 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, 1 Mar 1999, Chuck Robey wrote: > On Mon, 1 Mar 1999, David O'Brien wrote: > > > > .if defined(WANT_SHAREDLIBS) > > > CONFIGURE_ARGS+= --enable-shared > > > .endif > > > > > > in it. That's not particularly friendly, I wonder why it was put in > > > there, unless the feature is somehow broken? I'm trying to rebuild it > > > now to see what it then installs. > > > > Because people like a previous poster thinks that eg++ should like > > against /usr/lib/libstdc++.so.2 which is plain WRONG. eg++ is totally > > incompatable with g++ 2.7.x. So what happens when you move an eg++ > > produced binary to a machine that doesn't have EGCS installed? > > OK, but listing from my gcc-lib/i386-unknown-freebsd4.0/egcs-2.91.62 > gives: > > SYSCALLS.c.X crtbeginS.o libiberty.a > cc1* crtend.o libobjc.a > cc1obj* crtendS.o libstdc++.a > cc1plus* f771* libstdc++.so@ > collect2* include/ libstdc++.so.2.9@ > cpp* libg2c.a libstdc++.so.2.9.0* > crtbegin.o libgcc.a specs > > (I compiled this with the WANT_SHAREDLIBS on). It seems to make a > libstdc++.so.2.9 .... my first guess is, we'd want to bump the number so > that it fits the form for our loader (one rev number, not two) and use > it like the old one. It's the new form, done for egcs, it should work, > right? If you move it to a machine without version 3 installed, it'll > complain, right? > > I'm learning here, don't get upset if I'm all wet. Another thing I note > is that, unlike all the rest of the snapshots of egcs, the pre-release > version (and seemingly only the prerelease version) that the port uses > has gcj, the java tool, cut out. That seems kind of a shame, doesn't > it? > > I tried taking the gcj part out of the latest egcs snap, and dropping it > inplace in the prerelease version. Cygnus supplies the tarball for the > gcc/java directory separately (if you want it), bless them! It > configures ok (I *think*) with --enable-java, but it won't finish > compiling. It's Makefile isn't correct, doesn't have a rule for an > object file gcj needs (lost the error listing, I just had a freezeup). You're not concerned about the freezeup? > > I'm out of time tonight. I think you're telling me to redo my egcs > install with the WANT_SHAREDLIBS off, right? And you're going to have > the libstdc++ ported (I read that, right?) so I should just maybe be > patient? > > ----------------------------+----------------------------------------------- > 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 picnic (FreeBSD-current) > (301) 220-2114 | and jaunt (Solaris7). > ----------------------------+----------------------------------------------- > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 19:57:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 023DA155EB for ; Mon, 1 Mar 1999 19:56:46 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id WAA12001; Mon, 1 Mar 1999 22:54:27 -0500 (EST) Date: Mon, 1 Mar 1999 22:54:26 -0500 (EST) From: Chuck Robey To: Brian Feldman Cc: "David O'Brien" , Thomas Dean , mark@grondar.za, freebsd-current@FreeBSD.ORG Subject: Re: egcs and gcc 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, 1 Mar 1999, Brian Feldman wrote: > You're not concerned about the freezeup? The freezeup had nothign whatsoever to do with the subject at hand. I'm concerned, but this is the *wrong* time to raise it. I am not running a new kernel, not doing any egcs testing at all yet, still in tool-building phase. I want to continue to deal with that privately. I don't have enough data yet (it doesn't panic, it stops dead in the water about once every month for 2 months now). ----------------------------+----------------------------------------------- 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 picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 20: 5:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 922F3155CC for ; Mon, 1 Mar 1999 20:05:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA50086; Mon, 1 Mar 1999 20:05:07 -0800 (PST) (envelope-from dillon) Date: Mon, 1 Mar 1999 20:05:07 -0800 (PST) From: Matthew Dillon Message-Id: <199903020405.UAA50086@apollo.backplane.com> To: "RT" Cc: Subject: Re: Still NFS Problems References: <004f01be644f$239ae3e0$2300000a@a35.my.intranet> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In the past 3 weeks I've upgraded from 3.0-release, to 3-stable to 4-current :(as of 4 days ago). I've tried nfs v2 and nfs v3. In all of those :circumstances I end up with programs locking due to write problems. : :I'm no good a debugging, so if someone could hold my hand through this :one... : :Basic problem. .nfs798798 files appearing on server, program on client :locks up in STAT 'D' according to top. The problem only occurs on read / :write mounts (duh..). I only have my home partition writable as of right :now. : :The easiest way to replicate it is to compile something large. i.e. make :world from the client machine. Soon I'll just make my home directory read :only too :) Any ideas? fixes? things I can show you? When this happens, run 'dmesg' on the client. Does it report any problems near the end of the system messages? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 20:15:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id B253A14C95 for ; Mon, 1 Mar 1999 20:15:02 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id XAA15871 for ; Mon, 1 Mar 1999 23:14:52 -0500 (EST) Date: Mon, 1 Mar 1999 23:14:52 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@freebsd.org Subject: vm_mmap.c change gives strange behavior 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 With the latest change of sys/vm/vm_mmap.c, the behavior of that lovely fincore.c program changes to a lockmgr panic to a "thrd_sleep", which never is woken up, in the fincore process. I'm just making sure that this is now known... Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 20:42:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 8728B14C1C for ; Mon, 1 Mar 1999 20:42:14 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA35972; Mon, 1 Mar 1999 20:42:02 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Manfred Antar Cc: dyson@iquest.net, jdp@polstra.com (John Polstra), obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: gcc In-reply-to: Your message of "Mon, 01 Mar 1999 19:25:32 PST." <4.2.0.25.19990301191722.00a50100@216.101.162.50> Date: Mon, 01 Mar 1999 20:42:02 -0800 Message-ID: <35968.920349722@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Doesn't this just rebuild the standard gcc compiler in /usr/obj/usr/tmp/bin a s > part of the tools build, then use that compiler to build world. Hmmm. You may have an embarassing point here; I was wondering how/if the native compiler got used during the build process if you commented it out of the make world, but nothing I could *obviously* see suggested that any magic like this was happening. If I have missed the obvious somewhere, mea culpa - I'll add some -v's to my CFLAGS and see what sort of compiler version output I get! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 20:52:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 5E51B14C93 for ; Mon, 1 Mar 1999 20:50:56 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id PAA01084; Tue, 2 Mar 1999 15:20:19 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA02135; Tue, 2 Mar 1999 15:19:48 +1030 Date: Tue, 2 Mar 1999 15:19:48 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: John Polstra Cc: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: gcc In-Reply-To: <199903011715.JAA48969@vashon.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 Mon, 1 Mar 1999, John Polstra wrote: > Hang on. Others have reported success building kernels with egcs. Count me among that list - although last time I tried was about 6 months ago. The only problem I noticed was the format extensions, although admittedly I didn't run with the kernel for long. Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 20:53:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id F149214C93 for ; Mon, 1 Mar 1999 20:53:39 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id UAA13273 for current@FreeBSD.ORG; Mon, 1 Mar 1999 20:53:23 -0800 (PST) (envelope-from obrien) Date: Mon, 1 Mar 1999 20:53:23 -0800 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: gcc Message-ID: <19990301205323.A13227@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199903011715.JAA48969@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Kris Kennaway on Tue, Mar 02, 1999 at 03:19:48PM +1030 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Count me among that list - although last time I tried was about 6 months ago. > The only problem I noticed was the format extensions, although admittedly I I'm running a kernel built with my contrib'ifed EGCS. Format extensions and all. libstdc++ is still a problem though. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 20:54:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137]) by hub.freebsd.org (Postfix) with ESMTP id 5992A154AE for ; Mon, 1 Mar 1999 20:54:18 -0800 (PST) (envelope-from entropy@compufit.at) Received: from uvo-109.univie.ac.at ([131.130.230.109]) by darkstar.psa.at with smtp (Exim 2.10 #2) id 10HhX9-0006b1-00; Tue, 2 Mar 1999 06:15:56 +0100 Date: Tue, 2 Mar 1999 05:50:40 +0100 From: Alexander Sanda X-Mailer: Becky! 1.23 Organization: Intentionally left blank X-Priority: 3 (Normal) Message-ID: <18243.990302@psa.at> To: John Polstra Cc: current@freebsd.org Subject: Re: gcc References: <199903011720.JAA49016@vashon.polstra.com> 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 Monday, March 01, 1999, 6:20:06 PM, you wrote: >> Just make libg++ a port. :-) > Yes, or abandon it entirely. We surely don't need it in our base > system. Even for ports, I'd be surprised to find anything useful that > still relied on libg++. Any software that still uses libg++ is almost > certainly unmaintained, and uncompilable with modern C++ compilers. > (I.e., it does not conform to the C++ standard.) Libg++ is _ancient_. > It pre-dated templates even. Netscape still uses libg++ /usr/local/netscape/netscape: [...] -lg++.4 => /usr/lib/aout/libg++.so.4.0 (0x10c5c000) -lm.2 => /usr/lib/aout/libm.so.2.0 (0x10c98000) -lstdc++.2 => /usr/lib/aout/libstdc++.so.2.0 (0x10cb2000) -lc.3 => /usr/lib/aout/libc.so.3.1 (0x10ce8000) And most will imho agree on the fact, that Netscape is in some ways useful :) -- # /AS/ as@psa.at / PGP key available on request and from keys.pgp.com # # If jesus was never born, we would not have a Y2K problem. # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 20:57: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id C7B5814C87 for ; Mon, 1 Mar 1999 20:57:08 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id UAA13303; Mon, 1 Mar 1999 20:56:50 -0800 (PST) (envelope-from obrien) Date: Mon, 1 Mar 1999 20:56:50 -0800 From: "David O'Brien" To: Chuck Robey Cc: freebsd-current@FreeBSD.ORG Subject: Re: egcs and gcc Message-ID: <19990301205650.B13227@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990301181053.A11564@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Chuck Robey on Mon, Mar 01, 1999 at 10:10:34PM -0500 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm learning here, don't get upset if I'm all wet. Another thing I note > is that, unlike all the rest of the snapshots of egcs, the pre-release > version (and seemingly only the prerelease version) that the port uses > has gcj, the java tool, cut out. egcs-1.{0,1}.x never had the java bits. For a while the port was based on the EGCS devel tree so you would have seen the java bits in the past, but not in a while. When a released version came out, so I changed the port to use that one. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 21: 1: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from dyn02.trafford.dementia.org (dyn02.trafford.dementia.org [204.29.154.130]) by hub.freebsd.org (Postfix) with ESMTP id 4F0E814C18 for ; Mon, 1 Mar 1999 21:01:00 -0800 (PST) (envelope-from assar@sics.se) Received: (from assar@localhost) by dyn02.trafford.dementia.org (8.9.1/8.7.3) id GAA58094; Tue, 2 Mar 1999 06:02:40 +0100 (CET) To: Jonathan Lemon Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc References: <199903012245.QAA24387@free.pcs> Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 02 Mar 1999 06:02:37 +0100 In-Reply-To: Jonathan Lemon's message of "Mon, 1 Mar 1999 16:45:13 -0600 (CST)" Message-ID: <5lsoboiivm.fsf@mg.trafford.dementia.org> Lines: 8 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan Lemon writes: > How about getting profiling working for ELF kernels before > before completely abandoning a.out? There are patches for that in kern/9413 but I haven't got any feedback on them at all. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 21: 3:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (Postfix) with ESMTP id A1AD114C1D for ; Mon, 1 Mar 1999 21:03:20 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id XAA16340; Mon, 1 Mar 1999 23:03:02 -0600 (CST) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id WAA06840; Mon, 1 Mar 1999 22:58:47 -0600 Message-ID: <19990301225847.27864@right.PCS> Date: Mon, 1 Mar 1999 22:58:47 -0600 From: Jonathan Lemon To: Assar Westerlund Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc References: <199903012245.QAA24387@free.pcs> <5lsoboiivm.fsf@mg.trafford.dementia.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <5lsoboiivm.fsf@mg.trafford.dementia.org>; from Assar Westerlund on Mar 03, 1999 at 06:02:37AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mar 03, 1999 at 06:02:37AM +0100, Assar Westerlund wrote: > Jonathan Lemon writes: > > How about getting profiling working for ELF kernels before > > before completely abandoning a.out? > > There are patches for that in kern/9413 but I haven't got any feedback > on them at all. I did try them, they allow the kernel to compile, but they don't seem to work. In particular, the entries made in the flat profile section are all out of whack. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 21:18:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (unknown [142.177.193.154]) by hub.freebsd.org (Postfix) with ESMTP id A007614C87 for ; Mon, 1 Mar 1999 21:16:11 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.2/8.9.1) with ESMTP id BAA67272 for ; Tue, 2 Mar 1999 01:15:54 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 2 Mar 1999 01:15:54 -0400 (AST) From: The Hermit Hacker To: freebsd-current@freebsd.org Subject: 3.0-STABLE -> 4.x ... 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 Trying to get upgraded, especially with all this talk of moving to egcs, and trying to compile the kernel, at the load stage, I get: loading kernel lpt.o: In function `lpt_request_ppbus': /usr/src/sys/compile/thelab/../../dev/ppbus/lpt.c(.text+0x1c): undefined reference to `ppb_request_bus' lpt.o: In function `lpt_release_ppbus': /usr/src/sys/compile/thelab/../../dev/ppbus/lpt.c(.text+0x3c): undefined reference to `ppb_release_bus' lpt.o: In function `lptread': /usr/src/sys/compile/thelab/../../dev/ppbus/lpt.c(.text+0x6b6): undefined reference to `ppb_1284_negociate' /usr/src/sys/compile/thelab/../../dev/ppbus/lpt.c(.text+0x6f0): undefined reference to `ppb_1284_read' /usr/src/sys/compile/thelab/../../dev/ppbus/lpt.c(.text+0x726): undefined reference to `ppb_1284_terminate' lpt.o: In function `lptwrite': /usr/src/sys/compile/thelab/../../dev/ppbus/lpt.c(.text+0x7bb): undefined reference to `ppb_write' ioconf.o(.data+0x2ac): undefined reference to `lptdriver' *** Error code 1 1 error first thought was newer version of 'config', but results are the same... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 21:28:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (unknown [142.177.193.154]) by hub.freebsd.org (Postfix) with ESMTP id 8CBB214C82 for ; Mon, 1 Mar 1999 21:27:30 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.2/8.9.1) with ESMTP id BAA68397 for ; Tue, 2 Mar 1999 01:27:10 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 2 Mar 1999 01:27:10 -0400 (AST) From: The Hermit Hacker To: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-STABLE -> 4.x ... 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 Ignore, sorry...started scanning through the GENERIC file and found hte missing ppbus stuff that didn't exist in 3.x :( On Tue, 2 Mar 1999, The Hermit Hacker wrote: > > Trying to get upgraded, especially with all this talk of moving to egcs, > and trying to compile the kernel, at the load stage, I get: > > loading kernel > lpt.o: In function `lpt_request_ppbus': > /usr/src/sys/compile/thelab/../../dev/ppbus/lpt.c(.text+0x1c): undefined reference to `ppb_request_bus' > lpt.o: In function `lpt_release_ppbus': > /usr/src/sys/compile/thelab/../../dev/ppbus/lpt.c(.text+0x3c): undefined reference to `ppb_release_bus' > lpt.o: In function `lptread': > /usr/src/sys/compile/thelab/../../dev/ppbus/lpt.c(.text+0x6b6): undefined reference to `ppb_1284_negociate' > /usr/src/sys/compile/thelab/../../dev/ppbus/lpt.c(.text+0x6f0): undefined reference to `ppb_1284_read' > /usr/src/sys/compile/thelab/../../dev/ppbus/lpt.c(.text+0x726): undefined reference to `ppb_1284_terminate' > lpt.o: In function `lptwrite': > /usr/src/sys/compile/thelab/../../dev/ppbus/lpt.c(.text+0x7bb): undefined reference to `ppb_write' > ioconf.o(.data+0x2ac): undefined reference to `lptdriver' > *** Error code 1 > 1 error > > first thought was newer version of 'config', but results are the same... > > > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 21:43:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (unknown [142.177.193.154]) by hub.freebsd.org (Postfix) with ESMTP id AFB2214D21 for ; Mon, 1 Mar 1999 21:42:17 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.2/8.9.1) with ESMTP id BAA71054 for ; Tue, 2 Mar 1999 01:42:00 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 2 Mar 1999 01:42:00 -0400 (AST) From: The Hermit Hacker To: freebsd-current@freebsd.org Subject: lptdriver undefined in kernel compile... 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 one I *can't* seem to figure out...looked through GENERIC and swear I've added everything I need: cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf vers.c loading kernel ioconf.o(.data+0x2f0): undefined reference to `lptdriver' *** Error code 1 Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 22:13:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id AEFD914BFD for ; Mon, 1 Mar 1999 22:13:46 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id WAA13616; Mon, 1 Mar 1999 22:13:21 -0800 (PST) (envelope-from obrien) Date: Mon, 1 Mar 1999 22:13:21 -0800 From: "David O'Brien" To: Alexander Sanda Cc: current@freebsd.org Subject: Re: gcc Message-ID: <19990301221320.A13579@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199903011720.JAA49016@vashon.polstra.com> <18243.990302@psa.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <18243.990302@psa.at>; from Alexander Sanda on Tue, Mar 02, 1999 at 05:50:40AM +0100 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Just make libg++ a port. :-) > > Yes, or abandon it entirely. We surely don't need it in our base ... > Netscape still uses libg++ ... > And most will imho agree on the fact, that Netscape is in some ways useful :) > -lg++.4 => /usr/lib/aout/libg++.so.4.0 (0x10c5c000) ^^^^^^ Netscape uses a *A.OUT* libg++. We are an *ELF* system now. If you want to run Netscape (also a piece of a.out code) you would install the compat22 distribution bits. What we are talking about here has nothing to do with Netscape. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 22:14:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from nomad.dataplex.net (nomad.dataplex.net [208.2.87.8]) by hub.freebsd.org (Postfix) with ESMTP id 437B014C1F for ; Mon, 1 Mar 1999 22:14:46 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.2/8.9.2) with ESMTP id AAA03886; Tue, 2 Mar 1999 00:12:48 -0600 (CST) (envelope-from rkw@dataplex.net) X-Authentication-Warning: nomad.dataplex.net: rkw owned process doing -bs Date: Tue, 2 Mar 1999 00:12:48 -0600 (CST) From: Richard Wackerbarth Reply-To: rkw@dataplex.net To: Manfred Antar Cc: "Jordan K. Hubbard" , dyson@iquest.net, John Polstra , obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: gcc In-Reply-To: <4.2.0.25.19990301191722.00a50100@216.101.162.50> 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 > At 01:28 PM 3/1/99 -0800, Jordan K. Hubbard wrote: > >It really does appear to be a simple matter of first making egcs "take over" > >the system compiler: > > > ># cd /usr/ports/lang/egcs > ># make all install PREFIX=/usr > ># ln -fs /usr/bin/eg++ /usr/bin/c++ > ># ln -fs /usr/bin/egcc /usr/bin/cc > ># cd /usr/src > >remove cc from /usr/src/gnu/usr.bin/Makefile SUBDIR list > >remove libstdc++ and libobjc from /usr/src/gnu/lib/Makefile SUBDIR list Although this approach works, IMHO, the more appropriate approach would be to use "${CC}" rather than "cc" in ALL the makefiles and then define "CC=/usr/bin/egcc" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 22:21:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 3349A14C87 for ; Mon, 1 Mar 1999 22:21:53 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id WAA13678; Mon, 1 Mar 1999 22:21:33 -0800 (PST) (envelope-from obrien) Date: Mon, 1 Mar 1999 22:21:33 -0800 From: "David O'Brien" To: Richard Wackerbarth Cc: current@FreeBSD.ORG Subject: Re: gcc Message-ID: <19990301222133.A13655@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <4.2.0.25.19990301191722.00a50100@216.101.162.50> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Richard Wackerbarth on Tue, Mar 02, 1999 at 12:12:48AM -0600 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Although this approach works, IMHO, the more appropriate approach > would be to use "${CC}" rather than "cc" in ALL the makefiles and then > define "CC=/usr/bin/egcc" There will be troubles compling C++ code (groff) if our Makefiles add -I/usr/include/g++ to CXXFLAGS, which I'll bet it does. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 22:53:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 2A9001549B for ; Mon, 1 Mar 1999 22:53:05 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id RAA19881; Tue, 2 Mar 1999 17:22:01 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 02 Mar 1999 17:22:01 +1030 (CST) From: "Daniel O'Connor" To: Richard Wackerbarth Subject: Re: gcc Cc: current@FreeBSD.ORG, obrien@NUXI.com, John Polstra , dyson@iquest.net, "Jordan K. Hubbard" , Manfred Antar Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-Mar-99 Richard Wackerbarth wrote: > > >remove cc from /usr/src/gnu/usr.bin/Makefile SUBDIR list > > >remove libstdc++ and libobjc from /usr/src/gnu/lib/Makefile SUBDIR list > Although this approach works, IMHO, the more appropriate approach > would be to use "${CC}" rather than "cc" in ALL the makefiles and then > define "CC=/usr/bin/egcc" I did this for a make buildworld, ie make CC=egcc "CFLAGS=-nostdinc -I/usr/include" buildworld Which worked, but blew up doing ld :-/ [ ... ] printf '#include "SYS.h"\nRSYSCALL(clock_gettime)\n' > clock_gettime.S egcc -I/usr/include -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 -I/usr/src/lib/libc/i386 -c clock_gettime.S -o clock_gettime.o printf '#include "SYS.h"\nRSYSCALL(clock_settime)\n' > clock_settime.S /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldlang.c:1215: `FNM_FILE_NAME' undeclared (first use this function)/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldlang.c:1215: (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldlang.c:1215: for each function it appears in.)*** Error code 1Stop. *** Error code 1 Stop. etc I haven't looked at it any further though. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 23: 7:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (Postfix) with ESMTP id 196F215BB6 for ; Mon, 1 Mar 1999 23:04:53 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.8.7) with ESMTP id CAA00257 for ; Tue, 2 Mar 1999 02:05:08 -0500 (EST) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Tue, 2 Mar 1999 02:05:08 -0500 (EST) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: freebsd-current@freebsd.org Subject: the current kernel 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 with the latest kernel, I have had some problems: The first occured when I tried to use the arla AFS client. Everything loads ok, but then after it is loaded, if I try to use it, the system crashes. Second occured when I tried to start x11amp. The system crashed when I did that. I have no idea what caused the crashes, but they don't happen with my 3 day old kernel, and they happen with my 5 minute old kernel. Thanks Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 23:23: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id AAA9814D05 for ; Mon, 1 Mar 1999 23:22:22 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA83467; Tue, 2 Mar 1999 08:21:50 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903020721.IAA83467@freebsd.dk> Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-Reply-To: from ! at "Mar 2, 1999 3: 1:22 am" To: osa@etrust.ru Date: Tue, 2 Mar 1999 08:21:50 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems oZZ!!! wrote: > > > controller ata0 > > device atadisk0 # ATA disks > > device atapicd0 # ATAPI CDROM's > > > After (fastest(!!!)) boot: > $ dmesg > ...... > chip1: rev 0x01 on pci0.7.0 > ata-pci0: rev 0x01 on pci0.7.1 > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > ............... > > ad0: ATA-3 disk at ata0 as master > ad0: 2503MB (5126964 sectors), 5086 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 0 depth queue > ad1: ATA-? disk at ata1 as master > ^^^^^ ???? > ad1: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S > ad1: 16 secs/int, 0 depth queue > acd0: CDROM drive at ata1 as slave > acd0: drive speed 689KB/sec, 128KB cache > acd0: supported read types: CD-DA > acd0: Audio: play, 256 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: CD-ROM 120mm data disc loaded, unlocked > changing root device to ad0s1a > ......... > > ATA-? ??? > ^^^^^ > Does it right? Yup, that because the drive doesn't report what version the of the ATA spec its conformant to. > How i can create ad0s1a & etc. slises? i can't find anythink in > /usr/src/etc/etc.i386/MAKEDEV... Thats because the are not there yet, just use wd0 wd1 etc etc that will work fine , and makes it easier fot people to test the new setup without too much changing around. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 23:24:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id AD22C14C29 for ; Mon, 1 Mar 1999 23:23:25 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA83473; Tue, 2 Mar 1999 08:23:00 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903020723.IAA83473@freebsd.dk> Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-Reply-To: <199903020240.UAA02018@nospam.hiwaay.net> from David Kelly at "Mar 1, 1999 8:40:37 pm" To: dkelly@hiwaay.net (David Kelly) Date: Tue, 2 Mar 1999 08:23:00 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems David Kelly wrote: > S ren Schmidt writes: > > There is NO support for bad144, if your disk is bad, ditch it, it has > > already outgrown its internal spare sectors, and is dying. > > Speaking of which, is there any portable way to monitor bad block lists > on ATA drives? And the S.M.A.R.T. stuff that some vendors advertise? There is work underways to standardise a log function on ATA drives, I'm not sure if any has it yet. I plan to support some of what all this gives you. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 23:25: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 497AC14D6C for ; Mon, 1 Mar 1999 23:25:06 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA83484; Tue, 2 Mar 1999 08:24:47 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903020724.IAA83484@freebsd.dk> Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-Reply-To: from Brian Feldman at "Mar 1, 1999 10:10:54 pm" To: green@unixhelp.org (Brian Feldman) Date: Tue, 2 Mar 1999 08:24:47 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Brian Feldman wrote: > Do you have any plans to move the wfd(4) driver to the new ATA framework? I'd > be glad to test it all out, as long as I don't lose my LS-120's functionality. > Thanks in advance! I'm, waiting for my ZIP drive to arrive, then there will be an atapi-fd driver as well.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 1 23:26:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 0453914EF6 for ; Mon, 1 Mar 1999 23:26:15 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA83494; Tue, 2 Mar 1999 08:25:44 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903020725.IAA83494@freebsd.dk> Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-Reply-To: from Tugrul at "Mar 1, 1999 10:39:52 pm" To: tugrul@ianai.BlackSun.org (Tugrul) Date: Tue, 2 Mar 1999 08:25:44 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Tugrul wrote: > > The new driver fails to build when devfs is also in the config. I > made a simple change of "static void *devfs_token" to "void *devfs_token" > on line 183 in ata-all.h and all seems good. I know, I was thi close to ripping all the devfs stuff out, but... > Good work, no more stinky delay :-) Thanks!, and I hate delays too :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 0:34:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 9B82314CA6 for ; Tue, 2 Mar 1999 00:33:02 -0800 (PST) (envelope-from geoff@rucus.ru.ac.za) Received: (qmail 74057 invoked by uid 268); 2 Mar 1999 10:34:04 -0000 Message-ID: <19990302103404.74054.qmail@rucus.ru.ac.za> Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-Reply-To: <199903020725.IAA83494@freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "Mar 2, 1999 8:25:44 am" To: sos@freebsd.dk (=?ISO-8859-1?Q?S=F8ren?= Schmidt) Date: Tue, 2 Mar 1999 10:34:04 +0000 (GMT) Cc: current@freebsd.org Reply-To: "Geoff Rehmet" From: "Geoff Rehmet" X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Søren Schmidt writes : > > > Good work, no more stinky delay :-) > > Thanks!, and I hate delays too :) It works beautifully for me. I can imagine that the people with UDMA drives can't wait for DMA support in it. :-) I've run some tests with Bonnie. Need to still reboot with my old kernel, and run the same test to see what it did. Geoff. -- Geoff Rehmet, The Internet Solution geoffr@is.co.za; geoff@rucus.ru.ac.za; csgr@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 1: 4: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E0B9314C49 for ; Tue, 2 Mar 1999 01:04:04 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA83711; Tue, 2 Mar 1999 10:03:26 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903020903.KAA83711@freebsd.dk> Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-Reply-To: <19990302103404.74054.qmail@rucus.ru.ac.za> from Geoff Rehmet at "Mar 2, 1999 10:34: 4 am" To: geoffr@is.co.za Date: Tue, 2 Mar 1999 10:03:26 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Geoff Rehmet wrote: > Søren Schmidt writes : > > > > > Good work, no more stinky delay :-) > > > > Thanks!, and I hate delays too :) > > It works beautifully for me. I can imagine that the people > with UDMA drives can't wait for DMA support in it. :-) Its in the works, together with the tagged queuing some of the newer drives supports. > I've run some tests with Bonnie. Need to still reboot with > my old kernel, and run the same test to see what it did. Let me know how that works out. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 1: 6:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-spool.is.co.za (mail-spool.is.co.za [196.4.160.4]) by hub.freebsd.org (Postfix) with ESMTP id 3F05514CE6; Tue, 2 Mar 1999 01:06:33 -0800 (PST) (envelope-from geoff@hangdog.is.co.za) Received: from admin.is.co.za (admin.is.co.za [196.23.0.9]) by mail-spool.is.co.za (8.8.8/IShub#3) with ESMTP id LAA07818; Tue, 2 Mar 1999 11:06:45 +0200 Received: from hangdog.is.co.za (hangdog.is.co.za [196.26.1.216]) by admin.is.co.za (8.8.6/8.7.3/ISsubsidiary#1) with ESMTP id LAA16546; Tue, 2 Mar 1999 11:06:13 +0200 (GMT) Received: (from geoff@localhost) by hangdog.is.co.za (8.9.2/8.9.2) id LAA00297; Tue, 2 Mar 1999 11:06:13 +0200 (SAST) (envelope-from geoff) From: Geoff Rehmet Message-Id: <199903020906.LAA00297@hangdog.is.co.za> Subject: ATA driver To: sos@freebsd.org, current@freebsd.org Date: Tue, 2 Mar 1999 11:06:13 +0200 (SAST) Reply-To: "Geoff Rehmet" X-Mailer: ELM [version 2.4ME+ PL43 (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 Just some results of testing the comparison of wd and ata: Both bonnie tests were run on a freshly booted machine, P133, 64M RAM, running X and netscape, but only Bonnie active: -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ATA 64 3237 69.0 2913 14.0 1409 9.4 2951 59.3 3043 11.6 55.9 2.4 WD 64 2556 54.5 2902 13.3 1457 9.7 1987 40.3 3082 13.2 59.1 2.0 It may be worth testing with a larger file, freshly booted, with no X running. For reference, here is output of dmesg from my system: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Mar 2 08:26:46 SAST 1999 geoff@hangdog.is.co.za:/usr/src/sys/compile/HANGDOG.ata Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 133269971 Hz CPU: Pentium/P54C (133.27-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 63021056 (61544K bytes) Preloaded elf kernel "kernel" at 0xf023d000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ata-pci0: rev 0x00 on pci0.7.1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 vga0: rev 0x00 int a irq 11 on pci0.11.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in ata-isa1: already registered as ata0 ata1 not found at 0x1f0 ata-isa2: already registered as ata1 ata2 not found at 0x170 ppc0 at 0x378 irq 7 on isa ppc0: W83877F chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/utp/bnc[*UTP*] address 00:60:97:3d:ff:fc vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface ata1: unwanted interrupt ata1: unwanted interrupt Intel Pentium detected, installing workaround for F00F bug ep0 XXX: driver didn't set ifq_maxlen ad0: ATA-? disk at ata0 as master ad0: 1036MB (2122780 sectors), 2105 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue ad1: ATA-? disk at ata0 as slave ad1: 812MB (1664583 sectors), 1651 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue acd0: CDROM drive at ata1 as master acd0: drive speed 687 - 5500KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked changing root device to ad0s1a ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates Geoff. -- Geoff Rehmet, The Internet Solution - Infrastructure tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: geoffr@is.co.za URL: http://www.is.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 1:14:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 61D7C14C41; Tue, 2 Mar 1999 01:13:40 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA83744; Tue, 2 Mar 1999 10:13:13 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903020913.KAA83744@freebsd.dk> Subject: Re: ATA driver In-Reply-To: <199903020906.LAA00297@hangdog.is.co.za> from Geoff Rehmet at "Mar 2, 1999 11: 6:13 am" To: geoffr@is.co.za Date: Tue, 2 Mar 1999 10:13:13 +0100 (CET) Cc: sos@freebsd.org, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Geoff Rehmet wrote: Interesting, what flags did you use with the old driver (wd) ?? > Just some results of testing the comparison of wd and ata: > > Both bonnie tests were run on a freshly booted machine, P133, > 64M RAM, running X and netscape, but only Bonnie active: > > > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > ATA 64 3237 69.0 2913 14.0 1409 9.4 2951 59.3 3043 11.6 55.9 2.4 > WD 64 2556 54.5 2902 13.3 1457 9.7 1987 40.3 3082 13.2 59.1 2.0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 1:21:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 954E914C0F; Tue, 2 Mar 1999 01:21:09 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA04173; Tue, 2 Mar 1999 08:12:17 +0100 From: Luigi Rizzo Message-Id: <199903020712.IAA04173@labinfo.iet.unipi.it> Subject: Re: ATA driver To: geoffr@is.co.za Date: Tue, 2 Mar 1999 08:12:17 +0100 (MET) Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199903020906.LAA00297@hangdog.is.co.za> from "Geoff Rehmet" at Mar 2, 99 11:05:54 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1089 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just some results of testing the comparison of wd and ata: ... > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- >Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU >ATA 64 3237 69.0 2913 14.0 1409 9.4 2951 59.3 3043 11.6 55.9 2.4 >WD 64 2556 54.5 2902 13.3 1457 9.7 1987 40.3 3082 13.2 59.1 2.0 > > It may be worth testing with a larger file, freshly booted, with no X > running. or a newer disk:) i use to see much better performance -- say 5MB/s even without DMA - on modern (say 3GB or greater) disks even on 133MHz machines. (on a PPro200 i think my 6.4GB IBM disk runs close to 10MB/s... cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 1:23:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 59ECA14CF4 for ; Tue, 2 Mar 1999 01:23:43 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA83477; Tue, 2 Mar 1999 09:22:25 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 2 Mar 1999 09:22:25 +0000 (GMT) From: Doug Rabson To: Chuck Robey Cc: Thomas Dean , mark@grondar.za, freebsd-current@freebsd.org Subject: Re: egcs and gcc 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, 1 Mar 1999, Chuck Robey wrote: > On Mon, 1 Mar 1999, Thomas Dean wrote: > > > As suspected, eg++ is using libstdc++.a, not libstdc++.so.2, as it > > should. > > > > How does this get fixed? > > I just noticed that the egcs Makefile has a buried: > > .if defined(WANT_SHAREDLIBS) > CONFIGURE_ARGS+= --enable-shared > .endif > > in it. That's not particularly friendly, I wonder why it was put in > there, unless the feature is somehow broken? I'm trying to rebuild it > now to see what it then installs. That was put in extremely recently. The reason it doesn't build a shared library by default is to avoid potential conflict with the system libstdc++. If you enable it, the port will install the shared lib in /usr/lib/gcc-lib/.../libstdc++.so. You may need to add a runpath option to your link to point the executable at the directory. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 1:28:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id B643414C1F for ; Tue, 2 Mar 1999 01:28:01 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10HlSY-0003Eo-00; Tue, 2 Mar 1999 11:27:26 +0200 From: Sheldon Hearn To: The Hermit Hacker Cc: freebsd-current@freebsd.org Subject: Re: lptdriver undefined in kernel compile... In-reply-to: Your message of "Tue, 02 Mar 1999 01:42:00 -0400." Date: Tue, 02 Mar 1999 11:27:26 +0200 Message-ID: <12449.920366846@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 02 Mar 1999 01:42:00 -0400, The Hermit Hacker wrote: > this one I *can't* seem to figure out...looked through GENERIC and swear > I've added everything I need: Have you checked src/UPDATING and what it has to say about the nlpt->lpt driver changes? Have you made sure your KERNEL config file matches LINT's lpt stuff? If you're still stuck, someone will need to see your KERNEL config file. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 1:41: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 091E514D21; Tue, 2 Mar 1999 01:40:34 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10Hlez-0003PT-00; Tue, 2 Mar 1999 11:40:17 +0200 From: Sheldon Hearn To: Søren Schmidt Cc: current@freebsd.org Subject: ATAPI and ATAPI_STATIC with the new ATA* driver? In-reply-to: Your message of "Mon, 01 Mar 1999 13:19:20 PST." <199903012119.NAA73559@freefall.freebsd.org> Date: Tue, 02 Mar 1999 11:40:17 +0200 Message-ID: <13110.920367617@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 01 Mar 1999 13:19:20 PST, Søren Schmidt wrote: > # for a PCI only system (most modern machines) > controller ata0 > device atadisk0 # ATA disks > device atapicd0 # ATAPI CDROM's > device atapist0 # ATAPI tapes Hi Soren, Am I correct in assuming that we can toast ATAPI and ATAPI_STATIC in our kernel configs if we're using your new driver? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 1:51: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 54D5514C28; Tue, 2 Mar 1999 01:49:59 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA83835; Tue, 2 Mar 1999 10:49:17 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903020949.KAA83835@freebsd.dk> Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-Reply-To: <13110.920367617@axl.noc.iafrica.com> from Sheldon Hearn at "Mar 2, 1999 11:40:17 am" To: sheldonh@iafrica.com (Sheldon Hearn) Date: Tue, 2 Mar 1999 10:49:17 +0100 (CET) Cc: sos@FreeBSD.org, current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Sheldon Hearn wrote: > > > On Mon, 01 Mar 1999 13:19:20 PST, Søren Schmidt wrote: > > > # for a PCI only system (most modern machines) > > controller ata0 > > device atadisk0 # ATA disks > > device atapicd0 # ATAPI CDROM's > > device atapist0 # ATAPI tapes > > Hi Soren, > > Am I correct in assuming that we can toast ATAPI and ATAPI_STATIC in our > kernel configs if we're using your new driver? Yes, they are not used by the new driver, it only needs the above lines in config, depending on how many subdrivers you want of cause. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 2:13:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 4B57315520; Tue, 2 Mar 1999 02:13:44 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10Hm8s-00006Z-00; Tue, 2 Mar 1999 12:11:10 +0200 From: Sheldon Hearn To: Søren Schmidt Cc: sos@FreeBSD.org, current@FreeBSD.org Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-reply-to: Your message of "Tue, 02 Mar 1999 10:49:17 +0100." <199903020949.KAA83835@freebsd.dk> Date: Tue, 02 Mar 1999 12:11:10 +0200 Message-ID: <406.920369470@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 02 Mar 1999 10:49:17 +0100, Søren Schmidt wrote: > Yes, they are not used by the new driver, it only needs the above lines > in config, depending on how many subdrivers you want of cause. Excellent. :-) The only thing that bit me was that I used wd0 and wd2 with the older driver, whereas the newer driver automatically decided to use ad0 and ad1. This is "expected" behaviour, but it's something for other weenies to watch out for. :-) Sadly, cdcontrol still doesn't work with the newer driver and my braindead Creative Labs Infra36 CDROM drive. My older quad speed HITACHI still works. I noticed that the error message has changed, though. I used to get cdcontrol> play cdcontrol: Input/output error Now I get cdcontrol> play cdcontrol: Unknown error: 84 I guess no amount of programmer cleverness is going to get around crap hardware. Still, if you want me to try things with the hardware I've got, I'm happy to try. I'd offer you shell access, but South African connectivity isn't the best. :-) acd1: CDROM drive at ata1 as slave acd1: drive speed 112 - 4133KB/sec, 240KB cache acd1: supported read types: CD-DA acd1: Audio: play, 255 volume levels acd1: Mechanism: ejectable tray acd1: Medium: no/blank disc inside, unlocked Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 2:25:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7BE0E14C36 for ; Tue, 2 Mar 1999 02:25:13 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id LAA83946; Tue, 2 Mar 1999 11:24:43 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903021024.LAA83946@freebsd.dk> Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-Reply-To: <406.920369470@axl.noc.iafrica.com> from Sheldon Hearn at "Mar 2, 1999 12:11:10 pm" To: sheldonh@iafrica.com (Sheldon Hearn) Date: Tue, 2 Mar 1999 11:24:43 +0100 (CET) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Sheldon Hearn wrote: > > The only thing that bit me was that I used wd0 and wd2 with the older > driver, whereas the newer driver automatically decided to use ad0 and > ad1. This is "expected" behaviour, but it's something for other weenies > to watch out for. :-) I warned about that in the anounce :) > Sadly, cdcontrol still doesn't work with the newer driver and my > braindead Creative Labs Infra36 CDROM drive. My older quad speed HITACHI > still works. I noticed that the error message has changed, though. I > used to get > > cdcontrol> play > cdcontrol: Input/output error > > Now I get > > cdcontrol> play > cdcontrol: Unknown error: 84 Hmm, you could try to enable the debug in atapi-all.c & atapi-cd.c and mail me the output of that. The unknown error is because the new driver doesn't translate the atapi errors to errno errors yet. > I guess no amount of programmer cleverness is going to get around crap > hardware. Still, if you want me to try things with the hardware I've > got, I'm happy to try. I'd offer you shell access, but South African > connectivity isn't the best. :-) :) lets see what we can do before that, I still have alot of little things I need to get in there, this is just to get people banging on the driver to get feedback early in the development cycle. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 2:33: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 9B3CA14C58 for ; Tue, 2 Mar 1999 02:31:42 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA29033; Tue, 2 Mar 1999 21:31:08 +1100 Date: Tue, 2 Mar 1999 21:31:08 +1100 From: Bruce Evans Message-Id: <199903021031.VAA29033@godzilla.zeta.org.au> To: assar@sics.se, jlemon@americantv.com Subject: Re: gcc Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > How about getting profiling working for ELF kernels before >> > before completely abandoning a.out? >> >> There are patches for that in kern/9413 but I haven't got any feedback >> on them at all. > >I did try them, they allow the kernel to compile, but they >don't seem to work. In particular, the entries made in the >flat profile section are all out of whack. Also, all local assembler names are wrong (gprof -u doesn't hide them), and high resolution profiling (config -pp) is completely broken (i386/prof_machdep.c doesn't even compile). I should make it the default so that it gets maintained. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 2:54:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 59C9B14CCB for ; Tue, 2 Mar 1999 02:53:32 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10Hmjy-0000zW-00; Tue, 2 Mar 1999 12:49:30 +0200 From: Sheldon Hearn To: Bruce Evans Cc: dcs@newsguy.com, sos@freebsd.dk, beyssac@enst.fr, freebsd-current@FreeBSD.ORG, grog@lemis.com Subject: Re: IDE CDROM not found with PIIX4 chipset, -current kernel In-reply-to: Your message of "Sat, 27 Feb 1999 19:20:34 +1100." <199902270820.TAA24763@godzilla.zeta.org.au> Date: Tue, 02 Mar 1999 12:49:30 +0200 Message-ID: <3813.920371770@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 27 Feb 1999 19:20:34 +1100, Bruce Evans wrote: > I sent this in for review a year or so ago, but received no reply. > The main points are that it honours ATA timing in atapi_wait() and > checks for ARS_BUSY in atapi_wait(). I guess we'll need to wait and see whether this is still an issue with Soren's new driver. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 2:59:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 2528E14CBA for ; Tue, 2 Mar 1999 02:56:17 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id CAA27203 for current@freebsd.org; Tue, 2 Mar 1999 02:56:00 -0800 (PST) (envelope-from obrien) Date: Tue, 2 Mar 1999 02:56:00 -0800 From: "David O'Brien" To: current@freebsd.org Subject: bmake/contrib framework for egcs Message-ID: <19990302025600.F13655@relay.nuxi.com> Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've put the bmake & contrib framework for EGCS at ftp://ftp.nuxi.com/pub/FreeBSD/egcs (ftp://ftp.nuxi.com/pub/FreeBSD/egcs/cvs is all you really need) This is very rough work, but should help us towards our goal. In there you will find a CVS tree under ``cvs''. This CVS tree corresponds to /usr/src in that you will find "src/gnu/usr.bin/cc", "src/gnu/lib/libstdc++", and "src/contrib/egcs". Currently everything under src/gnu/usr.bin/cc builds and installs fine. I've tested the resulting ``cc'' by building working kernels and large parts of /usr/src. I have not yet tested a ``make world''. Everything I've done is w/in the source tree building components. ``cc -elf'' works, ``cc -aout'' doesn't due at least to a path problem finding crt0.o. c++ builds, but is getting segfaults right now. I'll be looking into that. src/gnu/lib/libstdc++ almost builds with ``make CXX=eg++'' where ``eg++'' is from the EGCS port. Please remember to backup your existing: /usr/bin/cc /usr/libexec/ /usr/lib/libgcc* /usr/lib/libg++* /usr/lib/libstdc++* /usr/include/g++/ If you play with ``make world'', you will probably want to disconnect groff from the build until the c++ compiler is working properly. I'll continue to update this cvs tree, so `ncftp3' with recursive get (and only for changed files) is your friend. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 3:27:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 1711B14CCA; Tue, 2 Mar 1999 03:27:10 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id WAA01709; Tue, 2 Mar 1999 22:26:50 +1100 Date: Tue, 2 Mar 1999 22:26:50 +1100 From: Bruce Evans Message-Id: <199903021126.WAA01709@godzilla.zeta.org.au> To: sheldonh@iafrica.com, sos@freebsd.dk Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? Cc: current@FreeBSD.ORG, sos@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The only thing that bit me was that I used wd0 and wd2 with the older >driver, whereas the newer driver automatically decided to use ad0 and >ad1. This is "expected" behaviour, but it's something for other weenies >to watch out for. :-) This breakage was announced :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 3:42:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id BBB9A14CCB for ; Tue, 2 Mar 1999 03:42:22 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id WAA03136; Tue, 2 Mar 1999 22:41:46 +1100 Date: Tue, 2 Mar 1999 22:41:46 +1100 From: Bruce Evans Message-Id: <199903021141.WAA03136@godzilla.zeta.org.au> To: alc@cs.rice.edu, dick@tar.com Subject: Re: lockmgr panic with mmap() Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Until you modify the map, an exclusive lock on the map is overkill. Try >using read locks. (See vm_map_lookup.) > >In the meantime, I can't see any reason why mincore acquires an >exclusive lock either. (It never modifies the map.) I'm going >to remedy that. Doesn't it modify the map indirectly vi subyte()? I think it wants to prevent modifications, but this is impossible. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 3:49:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 45C5614BDC for ; Tue, 2 Mar 1999 03:49:45 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 23812 invoked by uid 1001); 2 Mar 1999 11:49:27 +0000 (GMT) To: sos@freebsd.org Cc: current@freebsd.org Subject: Re: ATA driver From: sthaug@nethelp.no In-Reply-To: Your message of "Tue, 2 Mar 1999 11:06:13 +0200 (SAST)" References: <199903020906.LAA00297@hangdog.is.co.za> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 02 Mar 1999 12:49:27 +0100 Message-ID: <23810.920375367@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just some results of testing the comparison of wd and ata: > > Both bonnie tests were run on a freshly booted machine, P133, > 64M RAM, running X and netscape, but only Bonnie active: > > > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > ATA 64 3237 69.0 2913 14.0 1409 9.4 2951 59.3 3043 11.6 55.9 2.4 > WD 64 2556 54.5 2902 13.3 1457 9.7 1987 40.3 3082 13.2 59.1 2.0 Some results from a Celeron 300A with 66 Mhz bus OC to 75 Mhz (ie. processor running at 337 MHz), 256 MB memory. The disk is a 10 GB IBM Deskstar-16GP, one of the better 5400 RPM disks IMO. With only a 64 MB test, you can clearly see memory caching - for instance the insane numbers for seeks: WD 64 12030 62.4 11295 15.6 12118 29.5 18309 100.0 103363 99.9 1254.2 12.1 ATA 64 5803 37.3 7346 18.7 7127 22.5 18220 99.0 102285 99.5 1384.2 13.8 Here's a test with 512 MB, which is bigger than physical memory. Considerably more realistic numbers: WD 512 10480 53.8 10333 14.6 3645 7.3 12121 69.6 12133 15.1 129.5 1.8 ATA 512 5745 38.0 7120 17.6 2745 6.6 5475 32.4 7292 10.0 123.2 2.8 I'm using DMA for the WD driver: wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S Bootup messages for the ATA driver: ata-pci0: rev 0x01 on pci0.4.1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... ad0: ATA-4 disk at ata0 as master ad0: 9671MB (19807200 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 31 depth queue acd0: CDROM drive at ata1 as slave acd0: drive speed 0 - 6875KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked The CDROM player seems to work - I can play CDs and get sound trough the sound card. Eject works. Haven't tried CD-DA yet. On the first track I played, I got atapi: error = 20 acd0: read_toc failed atapi: error = 20 but this didn't happen for subsequent tracks. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 3:57:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id B8C7214CE9; Tue, 2 Mar 1999 03:56:39 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10HnlT-00006T-00; Tue, 2 Mar 1999 13:55:07 +0200 From: Sheldon Hearn To: Bruce Evans Cc: current@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-reply-to: Your message of "Tue, 02 Mar 1999 22:26:50 +1100." <199903021126.WAA01709@godzilla.zeta.org.au> Date: Tue, 02 Mar 1999 13:55:07 +0200 Message-ID: <400.920375707@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 02 Mar 1999 22:26:50 +1100, Bruce Evans wrote: > This breakage was announced :-). My only defense is my use of the phrase "other weenies" in my original mail. ;-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 4:10:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from daytona.hkstar.com (daytona.hkstar.com [202.82.3.25]) by hub.freebsd.org (Postfix) with ESMTP id EFB0F14CB8 for ; Tue, 2 Mar 1999 04:10:17 -0800 (PST) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by daytona.hkstar.com (8.9.1/8.9.1) with ESMTP id UAA19750 for ; Tue, 2 Mar 1999 20:09:59 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id UAA16465 for freebsd-current@freebsd.org; Tue, 2 Mar 1999 20:09:53 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199903021209.UAA16465@b1.hkstar.com> Subject: anyone knows what does it mean To: freebsd-current@freebsd.org Date: Tue, 2 Mar 1999 20:09:52 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] 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 Hello, I recently compile the egcs-1.1.1 and the system report to me that the ahc0:A:0 refuses tagged commands performance non-tagged I/O. The transfer speed drop from 20.00M/s to 3.3 M/s. Is there anyone have the same problem ? Cheers Clarence ======= Part of the dmesg ======= da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 3.300MB/s transfers, Tagged Queueing Enabled ^^^^^ poor performance drop from 20.00 to 3.3 da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da2 at ahc0 bus 0 target 2 lun 0 da2: Removable Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 10) da2: 508MB (1041500 512 byte sectors: 64H 32S/T 508C) cd0 at ahc0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) ahc0:A:0: refuses tagged commands. Performing non-tagged I/O ======= Part of the dmesg ======= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 4:47:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from amethyst.bsdx.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id DA40514D41 for ; Tue, 2 Mar 1999 04:46:56 -0800 (PST) (envelope-from bsdx@spawnet.com) Received: from spawnet.com (localhost [127.0.0.1]) by amethyst.bsdx.net (8.9.3/8.9.1) with ESMTP id HAA02537 for ; Tue, 2 Mar 1999 07:46:39 -0500 (EST) (envelope-from bsdx@spawnet.com) Message-ID: <36DBDDAE.8FB65C3D@spawnet.com> Date: Tue, 02 Mar 1999 07:46:38 -0500 From: Adam McDougall X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? References: <406.920369470@axl.noc.iafrica.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Tue, 02 Mar 1999 10:49:17 +0100, Søren Schmidt wrote: > > > Yes, they are not used by the new driver, it only needs the above lines > > in config, depending on how many subdrivers you want of cause. > > Excellent. :-) > > The only thing that bit me was that I used wd0 and wd2 with the older > driver, whereas the newer driver automatically decided to use ad0 and > ad1. This is "expected" behaviour, but it's something for other weenies > to watch out for. :-) Is/will there be a way to wire the devices down like you can with SCSI devices? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 6: 5:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (Postfix) with ESMTP id 8440814D3B for ; Tue, 2 Mar 1999 06:05:53 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id IAA07324; Tue, 2 Mar 1999 08:02:47 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id IAA07320; Tue, 2 Mar 1999 08:02:47 -0600 (CST) Message-ID: <007a01be64b5$63f0dba0$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "FreeBSD-Current" , "=?iso-8859-1?Q?S=F8ren_Schmidt?=" Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. Date: Tue, 2 Mar 1999 08:03:03 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will the new ATAPI drivers still work with wormcontrol for ATAPI CD Writers? Since it is a WIP, will it support it if it doesn't? Tom Veldhouse veldy@visi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 6:57:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137]) by hub.freebsd.org (Postfix) with ESMTP id 3BC0214D45 for ; Tue, 2 Mar 1999 06:57:11 -0800 (PST) (envelope-from entropy@compufit.at) Received: from unet4-31.univie.ac.at ([131.130.233.31]) by darkstar.psa.at with smtp (Exim 2.10 #2) id 10Hqwo-0006mU-00; Tue, 2 Mar 1999 16:19:03 +0100 Date: Tue, 2 Mar 1999 15:25:20 +0100 From: Alexander Sanda X-Mailer: Becky! 1.23 Reply-To: Alexander Sanda Organization: Organized, me ? X-Priority: 3 (Normal) Message-ID: <3642.990302@compufit.at> To: David O'Brien , current@freebsd.org Subject: Re: gcc References: <19990301221320.A13579@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dienstag, Dienstag, 02. März 1999, you wrote: DOB> Netscape uses a *A.OUT* libg++. We are an *ELF* system now. If you want DOB> to run Netscape (also a piece of a.out code) you would install the DOB> compat22 distribution bits. Then I probably misinterpreted the term "abandon it entirely". DOB> What we are talking about here has nothing to do with Netscape. Maybe. But what if Netscape decides to make the next fbsd release ELF (and still keeps linking with libg++) ? What about Mozilla ? Is it libg++ - free ? I agree that libg++ is (almost) useless today, but dropping it from the source and making it a port shouldn't disturb anyone. -- Alexander To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 7:17: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id D91E614D77 for ; Tue, 2 Mar 1999 07:15:14 -0800 (PST) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.9.3/8.9.3) id RAA38647; Tue, 2 Mar 1999 17:13:25 +0200 (SAT) (envelope-from reg) Date: Tue, 2 Mar 1999 17:13:25 +0200 From: Jeremy Lea To: Alexander Sanda Cc: "David O'Brien" , current@FreeBSD.ORG Subject: Re: gcc Message-ID: <19990302171325.B303@shale.csir.co.za> References: <19990301221320.A13579@relay.nuxi.com> <3642.990302@compufit.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <3642.990302@compufit.at>; from Alexander Sanda on Tue, Mar 02, 1999 at 03:25:20PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Tue, Mar 02, 1999 at 03:25:20PM +0100, Alexander Sanda wrote: > Maybe. But what if Netscape decides to make the next fbsd release ELF > (and still keeps linking with libg++) ? > > What about Mozilla ? Is it libg++ - free ? > > I agree that libg++ is (almost) useless today, but dropping it from the > source and making it a port shouldn't disturb anyone. Mozilla will only be ELF, since it is very likely that the minumum compiler will be egcs. It will also need GTK+, not Motif. I'm surprised the old Netscape needed libg++... Regards, -Jeremy -- | "Come home my prodigal son, come home and lets be one, --+-- don't want to see you cry, don't make me tell you why, | you've lived in a house with me, my blood has set you free, | in the world you'll surely die, nothing else will satisfy." -MIC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 7:25:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 8358014BE6 for ; Tue, 2 Mar 1999 07:25:11 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id IAA04334; Tue, 2 Mar 1999 08:24:52 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id IAA09156; Tue, 2 Mar 1999 08:24:43 -0700 Date: Tue, 2 Mar 1999 08:24:43 -0700 Message-Id: <199903021524.IAA09156@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Chuck Robey Cc: "David O'Brien" , freebsd-current@FreeBSD.org Subject: gcj (was Re: egcs and gcc) In-Reply-To: References: <19990301181053.A11564@relay.nuxi.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm learning here, don't get upset if I'm all wet. Another thing I note > is that, unlike all the rest of the snapshots of egcs, the pre-release > version (and seemingly only the prerelease version) that the port uses > has gcj, the java tool, cut out. That seems kind of a shame, doesn't > it? Actually no, since the libthreads library is not 'yet released', so the java compiler is kind of useless since you can't build stand-alone executables with the compiler, which is the point of gcj. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 8:39:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 1762A14D93 for ; Tue, 2 Mar 1999 08:39:25 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA18656; Wed, 3 Mar 1999 01:36:05 +0900 (JST) Message-ID: <36DC0981.5366E29A@newsguy.com> Date: Wed, 03 Mar 1999 00:53:37 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Bruce Evans Cc: sheldonh@iafrica.com, sos@freebsd.dk, current@FreeBSD.ORG Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? References: <199903021126.WAA01709@godzilla.zeta.org.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > > >The only thing that bit me was that I used wd0 and wd2 with the older > >driver, whereas the newer driver automatically decided to use ad0 and > >ad1. This is "expected" behaviour, but it's something for other weenies > >to watch out for. :-) > > This breakage was announced :-). Besides, it is not even a breakage. It finally got _unbroken_. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 8:47: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id CC8F714CA8 for ; Tue, 2 Mar 1999 08:47:00 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA26990; Wed, 3 Mar 1999 03:46:34 +1100 Date: Wed, 3 Mar 1999 03:46:34 +1100 From: Bruce Evans Message-Id: <199903021646.DAA26990@godzilla.zeta.org.au> To: bde@zeta.org.au, dcs@newsguy.com Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? Cc: current@FreeBSD.ORG, sheldonh@iafrica.com, sos@freebsd.dk Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >The only thing that bit me was that I used wd0 and wd2 with the older >> >driver, whereas the newer driver automatically decided to use ad0 and >> >ad1. This is "expected" behaviour, but it's something for other weenies >> >to watch out for. :-) >> >> This breakage was announced :-). > >Besides, it is not even a breakage. It finally got _unbroken_. :-) It is breakage, and should be fixed. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 9: 0:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 3F84414CB6 for ; Tue, 2 Mar 1999 08:59:49 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10HsSp-0000OK-00; Tue, 2 Mar 1999 18:56:11 +0200 From: Sheldon Hearn To: "Daniel C. Sobral" Cc: Bruce Evans , sos@freebsd.dk, current@FreeBSD.ORG Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-reply-to: Your message of "Wed, 03 Mar 1999 00:53:37 +0900." <36DC0981.5366E29A@newsguy.com> Date: Tue, 02 Mar 1999 18:56:11 +0200 Message-ID: <1507.920393771@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 03 Mar 1999 00:53:37 +0900, "Daniel C. Sobral" wrote: > > The only thing that bit me was that I used wd0 and wd2 with the older > > driver, whereas the newer driver automatically decided to use ad0 and > > ad1. [...] > Besides, it is not even a breakage. It finally got _unbroken_. :-) All I'm trying to say (and I agree that I really should learn to say exactly what I mean on this mailing list) is that this is something about which much song and dance will need to be made when the driver makes it into STABLE. I didn't read the announcement carefully enough. Nevertheless, I think it'll be useful for any future announcement to STABLE to say something like: Remember that disks are now numbered in the sequence in which they are found (as under the SCSI system), not in absolute positions as they were with the old system. For example, if you had wd0 and wd2 but no wd1, you'll now have wd0 and wd1. Watch out for this, because you may need to change your /etc/fstab and create appropriate entriess in /dev/ before booting your new kernel. I think that Soren's announcement was perfectly adequate for the intended audience, but I do believe that something like the suggestion above will help "other weenies like me" even more. :-) Ciao, Sheldon. Microsoft Windows NT - now sporting cutting-edge features cribbed from operating systems that only introduced them 20 years ago. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 9:37:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 8543D14D79 for ; Tue, 2 Mar 1999 09:37:23 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id LAA00057; Tue, 2 Mar 1999 11:37:04 -0600 (CST) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id LAA90896; Tue, 2 Mar 1999 11:37:04 -0600 (CST) Date: Tue, 2 Mar 1999 11:37:04 -0600 From: Alan Cox To: Bruce Evans Cc: current@freebsd.org Subject: Re: lockmgr panic with mmap() Message-ID: <19990302113704.B90473@nonpc.cs.rice.edu> References: <199903021141.WAA03136@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199903021141.WAA03136@godzilla.zeta.org.au>; from Bruce Evans on Tue, Mar 02, 1999 at 10:41:46PM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 02, 1999 at 10:41:46PM +1100, Bruce Evans wrote: > > Doesn't it modify the map indirectly vi subyte()? I think it wants > to prevent modifications, but this is impossible. > Bear with me, I'll have to split some hairs... We're only interested in whether mincore directly changes the vm_map, literally modifying a vm_map_entry, etc. subyte is writing to memory, not a vm_map_entry. subyte is only indirectly changing the map because a page fault occurs. That page fault *is* (frequently) changing the map, and we're deadlocking when it attempts to acquire the write lock on the map. Basically, what I believe that you suggested yesterday, that mincore release the lock around the subyte is correct. Code will appear shortly... Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 9:44:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id B852615450 for ; Tue, 2 Mar 1999 09:44:14 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id SAA28815; Tue, 2 Mar 1999 18:42:43 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id SAA22900; Tue, 2 Mar 1999 18:42:37 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: dcs@newsguy.com, current@FreeBSD.ORG, sheldonh@iafrica.com, sos@freebsd.dk Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-reply-to: Your message of "Wed, 03 Mar 1999 03:46:34 +1100." <199903021646.DAA26990@godzilla.zeta.org.au> Date: Tue, 02 Mar 1999 18:42:36 +0100 Message-ID: <22898.920396556@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199903021646.DAA26990@godzilla.zeta.org.au>, Bruce Evans writes: >>> >The only thing that bit me was that I used wd0 and wd2 with the older >>> >driver, whereas the newer driver automatically decided to use ad0 and >>> >ad1. This is "expected" behaviour, but it's something for other weenies >>> >to watch out for. :-) >>> >>> This breakage was announced :-). >> >>Besides, it is not even a breakage. It finally got _unbroken_. :-) > >It is breakage, and should be fixed. It isn't breakage when everybody else assigns identities to ATA disks sequentially, irespective of how much other gunk (Ie: CD, Tape) is present on the busses. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 10:13: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 305D015565 for ; Tue, 2 Mar 1999 10:12:49 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id FAA32656; Wed, 3 Mar 1999 05:12:30 +1100 Date: Wed, 3 Mar 1999 05:12:30 +1100 From: Bruce Evans Message-Id: <199903021812.FAA32656@godzilla.zeta.org.au> To: bde@zeta.org.au, phk@critter.freebsd.dk Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? Cc: current@FreeBSD.ORG, dcs@newsguy.com, sheldonh@iafrica.com, sos@freebsd.dk Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>> This breakage was announced :-). >>> >>>Besides, it is not even a breakage. It finally got _unbroken_. :-) >> >>It is breakage, and should be fixed. > >It isn't breakage when everybody else assigns identities to ATA disks >sequentially, irespective of how much other gunk (Ie: CD, Tape) is >present on the busses. Linux doesn't. It IDE cdroms to IDE drive minor numbers, e.g., hda = 1st controller, IDE drive hdb = 1st controller, IDE cdrom hdc = 2nd controller, IDE drive The sequencing of controllers isn't unique, so the breakage doesn't even work around the problem of mapping BIOS drive numbers to FreeBSD device names except in simple cases. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 10:16:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 31A411561F for ; Tue, 2 Mar 1999 10:16:32 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id TAA28930; Tue, 2 Mar 1999 19:14:17 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id TAA22989; Tue, 2 Mar 1999 19:14:13 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: current@FreeBSD.ORG, dcs@newsguy.com, sheldonh@iafrica.com, sos@freebsd.dk Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-reply-to: Your message of "Wed, 03 Mar 1999 05:12:30 +1100." <199903021812.FAA32656@godzilla.zeta.org.au> Date: Tue, 02 Mar 1999 19:14:13 +0100 Message-ID: <22987.920398453@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199903021812.FAA32656@godzilla.zeta.org.au>, Bruce Evans writes: >>>>> This breakage was announced :-). >>>> >>>>Besides, it is not even a breakage. It finally got _unbroken_. :-) >>> >>>It is breakage, and should be fixed. >> >>It isn't breakage when everybody else assigns identities to ATA disks >>sequentially, irespective of how much other gunk (Ie: CD, Tape) is >>present on the busses. > >Linux doesn't. Linux isn't "everybody else". -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 10:25:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 523DD14D4A for ; Tue, 2 Mar 1999 10:25:45 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id FAA00771; Wed, 3 Mar 1999 05:25:27 +1100 Date: Wed, 3 Mar 1999 05:25:27 +1100 From: Bruce Evans Message-Id: <199903021825.FAA00771@godzilla.zeta.org.au> To: bde@zeta.org.au, phk@critter.freebsd.dk Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? Cc: current@FreeBSD.ORG, dcs@newsguy.com, sheldonh@iafrica.com, sos@freebsd.dk Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>It isn't breakage when everybody else assigns identities to ATA disks >>>sequentially, irespective of how much other gunk (Ie: CD, Tape) is >>>present on the busses. >> >>Linux doesn't. > >Linux isn't "everybody else". Neither is { everybody else } - { linux }. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 12:42:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 646E414D5A for ; Tue, 2 Mar 1999 12:39:35 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id UAA04343; Tue, 2 Mar 1999 20:38:18 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id LAA00456; Tue, 2 Mar 1999 11:01:35 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199903021101.LAA00456@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: S ren Schmidt Cc: current@FreeBSD.ORG Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-reply-to: Your message of "Mon, 01 Mar 1999 22:21:05 +0100." <199903012121.WAA82163@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Tue, 02 Mar 1999 11:01:34 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > I would very much like to hear from you, both good and bad news > are very welcome. [.....] Looks good on my laptop ! ad0: ATA-3 disk at ata0 as master ad0: 3909MB (8007552 sectors), 7944 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue = acd0: CDROM drive at ata1 as master acd0: drive speed 4134KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked changing root device to ad0s1a It seems stable too (I haven't done any speed tests). Good work, and thanks. -- = 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 Mar 2 13:12:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 84B9414E68 for ; Tue, 2 Mar 1999 13:12:31 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id WAA85119; Tue, 2 Mar 1999 22:12:11 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903022112.WAA85119@freebsd.dk> Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-Reply-To: <007a01be64b5$63f0dba0$236319ac@w142844.carlson.com> from "Thomas T. Veldhouse" at "Mar 2, 1999 8: 3: 3 am" To: veldy@visi.com (Thomas T. Veldhouse) Date: Tue, 2 Mar 1999 22:12:11 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Thomas T. Veldhouse wrote: > Will the new ATAPI drivers still work with wormcontrol for ATAPI CD Writers? > Since it is a WIP, will it support it if it doesn't? It should, but i just found out that it somehow fails, I'm bughunting... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 13:12:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (Postfix) with ESMTP id 696F814DC9 for ; Tue, 2 Mar 1999 13:11:34 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.3/8.9.3) id PAA15864 for current@freebsd.org; Tue, 2 Mar 1999 15:11:17 -0600 (CST) (envelope-from dick) Date: Tue, 2 Mar 1999 15:11:17 -0600 From: "Richard Seaman, Jr." To: current@freebsd.org Subject: Heads up: Linux Thread "port" changes. Message-ID: <19990302151117.A764@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A number of people have downloaded the linux threads "port" located at http://lt.tar.com . It has been updated today, with minor bug fixes, and a change to make it compatible with kernel patches committed yesterday to both -current and -stable. While I haven't actually tested it, I would expect problems using post-March 1 kernels with the older "port", and vice-versa. If you are experimenting with this "port", you should update the "port" when you update your kernel. *NOTE* This port has nothing to do with linux threads running in linux emulation mode. If you're only running linux apps in emulation mode you don't have to worry about this. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 13:40:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from cepheus.hkstar.com (cepheus.hkstar.com [202.82.3.12]) by hub.freebsd.org (Postfix) with ESMTP id 725F114FAD for ; Tue, 2 Mar 1999 13:39:25 -0800 (PST) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by cepheus.hkstar.com (8.9.0/8.9.0) with ESMTP id FAA20767 for ; Wed, 3 Mar 1999 05:39:07 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id FAA11655 for freebsd-current@freebsd.org; Wed, 3 Mar 1999 05:39:05 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199903022139.FAA11655@b1.hkstar.com> Subject: compiler egcs 1.1.1 error To: freebsd-current@freebsd.org Date: Wed, 3 Mar 1999 05:39:04 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] 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 Hello, I tried to compile the egcs 1.1.1 yesterday and encountered the following error. Can anyone show me hoe to solve it. Thanks. Clarence ======= Error ======= ===> Generating temporary packing list ln -f /usr/bin/gcc /usr/bin/egcc ln -f /usr/bin/g++ /usr/bin/eg++ /bin/mv /usr/lib/libiberty.a /usr/lib/gcc-lib/i386-unknown-freebsd4.0/egcs-2.9 1.60 /bin/mv -f /usr/lib/libstdc++.a /usr/lib/gcc-lib/i386-unknown-freebsd4.0/egcs- 2.91.60/libstdc++.a if [ ! -f /usr/info/dir ]; then /usr/bin/sed -ne '1,/Menu:/p' /usr/share/info/d ir > /usr/info/dir; fi install-info /usr/info/cpp.info /usr/info/dir install-info: Undefined error: 0 for /usr/info/dir *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. ======= Error ======= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 14:57:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from thorium.uunet.be (thorium.uunet.be [194.7.15.88]) by hub.freebsd.org (Postfix) with ESMTP id DDE1914D26 for ; Tue, 2 Mar 1999 14:57:33 -0800 (PST) (envelope-from wim.debby@village.uunet.be) Received: from be002181 (pool02b-194-7-79-189.uunet.be [194.7.79.189]) by thorium.uunet.be (8.9.1/8.9.1) with SMTP id XAA20346 for ; Tue, 2 Mar 1999 23:57:13 +0100 (CET) Message-ID: <000201be64ff$fe324ce0$bd4f07c2@be002181> From: "Wim en Debby" To: "freebsd" Subject: fdimage.exe Date: Tue, 2 Mar 1999 23:46:27 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi to all, Can anyone tell me where l can find this fdimage.exe on the ftp-server? I looked in the tools/ directory but l didnt find it. Please a detailed address:-) Thanks, Wim Vermeyen wim.vermeyen@advalvas.be To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 15:11:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (m1-11-dbn.dial-up.net [196.34.155.11]) by hub.freebsd.org (Postfix) with ESMTP id 100B814E6D; Tue, 2 Mar 1999 15:10:02 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id BAA01120; Wed, 3 Mar 1999 01:09:15 +0200 (SAT) From: Robert Nordier Message-Id: <199903022309.BAA01120@ceia.nordier.com> Subject: Re: fdimage.exe In-Reply-To: <000201be64ff$fe324ce0$bd4f07c2@be002181> from Wim en Debby at "Mar 2, 99 11:46:27 pm" To: wim.debby@village.uunet.be (Wim en Debby) Date: Wed, 3 Mar 1999 01:09:13 +0200 (SAT) Cc: freebsd-questions@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Moved to -questions] Wim en Debby wrote: > Can anyone tell me where l can find this fdimage.exe on the ftp-server? I > looked in the tools/ directory but l didnt find it. Please a detailed > address:-) ftp://ftp.freebsd.org/pub/FreeBSD/tools/fdimage.exe There's an out-of-date version at some mirror sites, so best fetch it as above. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 15:17:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 92EE81507B for ; Tue, 2 Mar 1999 15:17:25 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id SAA09424; Tue, 2 Mar 1999 18:16:50 -0500 (EST) Date: Tue, 2 Mar 1999 18:16:50 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Alan Cox Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: lockmgr panic with mmap() In-Reply-To: <19990302113704.B90473@nonpc.cs.rice.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Mar 1999, Alan Cox wrote: > On Tue, Mar 02, 1999 at 10:41:46PM +1100, Bruce Evans wrote: > > > > Doesn't it modify the map indirectly vi subyte()? I think it wants > > to prevent modifications, but this is impossible. > > > > Bear with me, I'll have to split some hairs... > > We're only interested in whether mincore directly changes the vm_map, > literally modifying a vm_map_entry, etc. subyte is writing to memory, > not a vm_map_entry. subyte is only indirectly changing the map > because a page fault occurs. That page fault *is* (frequently) changing > the map, and we're deadlocking when it attempts to acquire the write lock > on the map. > > Basically, what I believe that you suggested yesterday, that mincore > release the lock around the subyte is correct. Code will > appear shortly... Where exactly does thrd_sleep come in, since that's where the program locks up now? Can't be killed, of course... > > Alan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 15:23:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id EE29714E0D for ; Tue, 2 Mar 1999 15:22:01 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id JAA25040; Wed, 3 Mar 1999 09:49:01 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199903020903.KAA83711@freebsd.dk> Date: Wed, 03 Mar 1999 09:49:01 +1030 (CST) From: "Daniel O'Connor" To: SXren Schmidt Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. Cc: current@FreeBSD.ORG, geoffr@is.co.za Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-Mar-99 SXren Schmidt wrote: > Its in the works, together with the tagged queuing some of the > newer drives supports. Wow! :) Is there any chance od adding the ability to 'wire' devices a la SCSI? :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 15:29: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 6982114E6D for ; Tue, 2 Mar 1999 15:28:32 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id RAA12990; Tue, 2 Mar 1999 17:28:14 -0600 (CST) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id RAA32070; Tue, 2 Mar 1999 17:28:14 -0600 (CST) Date: Tue, 2 Mar 1999 17:28:13 -0600 From: Alan Cox To: Brian Feldman Cc: current@freebsd.org Subject: Re: lockmgr panic with mmap() Message-ID: <19990302172813.A91146@nonpc.cs.rice.edu> References: <19990302113704.B90473@nonpc.cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Brian Feldman on Tue, Mar 02, 1999 at 06:16:50PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 02, 1999 at 06:16:50PM -0500, Brian Feldman wrote: > > Where exactly does thrd_sleep come in, since that's where the program locks > up now? Can't be killed, of course... > The lock manager isn't bright enough to detect that the process already holds a read lock when it attempts to get the write lock. Thus, you get the "thrd_sleep" instead of a panic. In short, same bug, different symptoms. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 15:29:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 0C38914E1E for ; Tue, 2 Mar 1999 15:29:44 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id SAA10270; Tue, 2 Mar 1999 18:29:32 -0500 (EST) Date: Tue, 2 Mar 1999 18:29:31 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Alan Cox Cc: current@freebsd.org Subject: Re: lockmgr panic with mmap() In-Reply-To: <19990302172813.A91146@nonpc.cs.rice.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Mar 1999, Alan Cox wrote: > On Tue, Mar 02, 1999 at 06:16:50PM -0500, Brian Feldman wrote: > > > > Where exactly does thrd_sleep come in, since that's where the program locks > > up now? Can't be killed, of course... > > > > The lock manager isn't bright enough to detect that the process > already holds a read lock when it attempts to get the write lock. > Thus, you get the "thrd_sleep" instead of a panic. > > In short, same bug, different symptoms. > Ahh, makes sense. Quick question: how in the heck did you learn this whole VM system? Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 16: 2:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163]) by hub.freebsd.org (Postfix) with SMTP id 9878814E01 for ; Tue, 2 Mar 1999 16:02:17 -0800 (PST) (envelope-from idiotswitch@beer.com) Received: from a35 ([207.164.233.115]) by speed.rcc.on.ca (8.6.12/8.6.9) with SMTP id UAA02681; Tue, 2 Mar 1999 20:16:00 -0500 Message-ID: <000601be6508$9d784040$2300000a@a35.my.intranet> Reply-To: "IdiotSwitch Editor" From: "IdiotSwitch Editor" To: , "Sheldon Hearn" Subject: ATAPI Drive & Naming System Date: Tue, 2 Mar 1999 18:58:46 -0500 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.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Remember that disks are now numbered in the sequence in which > they are found (as under the SCSI system), not in absolute > positions as they were with the old system. For example, if you > had wd0 and wd2 but no wd1, you'll now have wd0 and wd1. Watch > out for this, because you may need to change your /etc/fstab and > create appropriate entriess in /dev/ before booting your new kernel. This may make a flame war, but why not give SCSI & ide devices the SAME device names? Ie. drv0 == first ide controller (harddisk) drv1 == first ide controller (CD-ROM) drv2 == scsi harddrive drv3 == scsi tape backup In my example, I booted from the ide controller (so it started looking there first). If I booted from the scsi harddrive, the 2 scsi drives would be 'found' first? This would simplify (or possibly mutilate) the current naming system for drives. However, is there anyway I can make drv1 (or at3) remain drv1 or at3 when I add more devices? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 17:34:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186]) by hub.freebsd.org (Postfix) with ESMTP id 06D4714DDB; Tue, 2 Mar 1999 17:34:31 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.2/8.9.2) id UAA65281; Tue, 2 Mar 1999 20:34:11 -0500 (EST) (envelope-from lee) Message-ID: <19990302203405.A65277@tidalwave.net> Date: Tue, 2 Mar 1999 20:34:05 -0500 From: Lee Cremeans To: sos@freebsd.org, current@freebsd.org Subject: New driver and ATAPI DMA? Reply-To: lcremean@tidalwave.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-OS: FreeBSD 3.0-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will this new ATA driver finally support DMA correctly on ATAPI devices (as opposed to pure ATA disk devices)? This is a feature that could really come in handy for me (as well as a reason to migrate back to -current from 3.1 :) -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 19: 9:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id DFDEF14E23 for ; Tue, 2 Mar 1999 19:09:24 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id WAA80990; Tue, 2 Mar 1999 22:06:12 -0500 (EST) Date: Tue, 2 Mar 1999 22:06:12 -0500 (EST) From: Chuck Robey To: Doug Rabson Cc: Thomas Dean , mark@grondar.za, freebsd-current@freebsd.org Subject: Re: egcs and gcc 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, 2 Mar 1999, Doug Rabson wrote: > That was put in extremely recently. The reason it doesn't build a shared > library by default is to avoid potential conflict with the system > libstdc++. > > If you enable it, the port will install the shared lib in > /usr/lib/gcc-lib/.../libstdc++.so. You may need to add a runpath option > to your link to point the executable at the directory. Doug, my egcs (when I tell it to --enable-shared) installs: libstdc++.so libstdc++.so.2.9 and libstdc++.so.2.9.0 How about I just keep the first one, kill the middle one, and make the real file libstdc++.so.3 (so it keeps our numbering). I'm not sure about the rules for this, since elf ... will stuff looking for libstdc++.so.2 find my new libstdc++.so.3, or will the new one (with it's incompatible format, like you said) be safe? ----------------------------+----------------------------------------------- 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 picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 22:20:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from regret.globalserve.net (regret.globalserve.net [209.90.144.72]) by hub.freebsd.org (Postfix) with ESMTP id 2744414E99; Tue, 2 Mar 1999 22:20:40 -0800 (PST) (envelope-from dm@regret.globalserve.net) Received: (from dm@localhost) by regret.globalserve.net (8.9.3/8.9.1) id CAA79950; Wed, 3 Mar 1999 02:32:22 GMT (envelope-from dm) Message-ID: <19990303023222.A79938@globalserve.net> Date: Wed, 3 Mar 1999 02:32:22 +0000 From: "Dan - Sr. Admin" To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: cvsup.ca.freebsd.org available again. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, Just a quick note to let everyone know that cvsup.ca.freebsd.org is available again. Regards, -- Dan Moschuk (TFreak!dm@globalserve.net) Senior Systems/Network Administrator Globalserve Communications Inc., a Primus Canada Company "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 23: 0:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id 0DB0214EC8 for ; Tue, 2 Mar 1999 23:00:31 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id IAA17393; Wed, 3 Mar 1999 08:00:11 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id HAA27961; Wed, 3 Mar 1999 07:58:28 +0100 (CET) (envelope-from andreas) Date: Wed, 3 Mar 1999 07:58:28 +0100 From: Andreas Klemm To: Chan Yiu Wah Cc: freebsd-current@FreeBSD.ORG Subject: Re: compiler egcs 1.1.1 error Message-ID: <19990303075828.A27941@titan.klemm.gtn.com> References: <199903022139.FAA11655@b1.hkstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199903022139.FAA11655@b1.hkstar.com>; from Chan Yiu Wah on Wed, Mar 03, 1999 at 05:39:04AM +0800 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.1-STABLE SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 03, 1999 at 05:39:04AM +0800, Chan Yiu Wah wrote: > Hello, > > I tried to compile the egcs 1.1.1 yesterday and encountered the following > error. Can anyone show me hoe to solve it. Thanks. > > Clarence JFYI, the port is now at: egcs-1.1.2-pre2 Maybe upgrading the port might help. It compiled and installed fine on 3.1-STABLE, but I didn't get a make world through ... fails at the very beginning when building make. -- 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 Mar 2 23:30:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4573314E99; Tue, 2 Mar 1999 23:30:14 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA86193; Wed, 3 Mar 1999 08:29:55 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903030729.IAA86193@freebsd.dk> Subject: Re: New driver and ATAPI DMA? In-Reply-To: <19990302203405.A65277@tidalwave.net> from Lee Cremeans at "Mar 2, 1999 8:34: 5 pm" To: lcremean@tidalwave.net Date: Wed, 3 Mar 1999 08:29:55 +0100 (CET) Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Lee Cremeans wrote: > Will this new ATA driver finally support DMA correctly on ATAPI devices (as > opposed to pure ATA disk devices)? This is a feature that could really come > in handy for me (as well as a reason to migrate back to -current from 3.1 :) Its on my list of wanted items, so there :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 23:32:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 0808114E2F for ; Tue, 2 Mar 1999 23:32:25 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA86207; Wed, 3 Mar 1999 08:31:47 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903030731.IAA86207@freebsd.dk> Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-Reply-To: from "Daniel O'Connor" at "Mar 3, 1999 9:49: 1 am" To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Wed, 3 Mar 1999 08:31:47 +0100 (CET) Cc: current@FreeBSD.ORG, geoffr@is.co.za X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Daniel O'Connor wrote: > > On 02-Mar-99 SXren Schmidt wrote: > > Its in the works, together with the tagged queuing some of the > > newer drives supports. > Wow! :) > > Is there any chance od adding the ability to 'wire' devices a la SCSI? :) I'll think about it, but lots of things has higher priority... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 23:38:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa15-25.ix.netcom.com [207.93.148.25]) by hub.freebsd.org (Postfix) with ESMTP id 7EE4F14E3D for ; Tue, 2 Mar 1999 23:35:25 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id XAA65447; Tue, 2 Mar 1999 23:32:51 -0800 (PST) (envelope-from tomdean) Date: Tue, 2 Mar 1999 23:32:51 -0800 (PST) Message-Id: <199903030732.XAA65447@ix.netcom.com> From: Thomas Dean To: freebsd-current@freebsd.org Subject: Printing is vvveeerrryyy slow Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running smp, 4.0-current, as of Mon Feb 15 03:34:29 PST 1999. Printing is very slow. I have a HP LaserJet III attached to lpt0. Printing in the pcl, text, mode is slower than I expect. Printing in the postscipt mode is extremely slow. A 30K postscript file has been OVER 5 minutes and is not finished! From dmesg: ... Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A ppc0 at 0x378 irq 7 on isa ppc0: PC87334 chipset (PS2/NIBBLE) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa ... tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 2 23:53:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-spool.is.co.za (mail-spool.is.co.za [196.4.160.4]) by hub.freebsd.org (Postfix) with ESMTP id 54DC114EBC for ; Tue, 2 Mar 1999 23:53:05 -0800 (PST) (envelope-from geoffr@is.co.za) Received: from admin.is.co.za (admin.is.co.za [196.23.0.9]) by mail-spool.is.co.za (8.8.8/IShub#3) with ESMTP id JAA09881; Wed, 3 Mar 1999 09:53:19 +0200 Received: from isjhbex01.is.co.za (isjhbex01.is.co.za [196.26.1.16]) by admin.is.co.za (8.8.6/8.7.3/ISsubsidiary#1) with ESMTP id JAA10316; Wed, 3 Mar 1999 09:52:46 +0200 (GMT) Received: by isjhbex01.is.co.za with Internet Mail Service (5.5.2232.9) id <100PSPJ4>; Wed, 3 Mar 1999 09:47:19 +0200 Message-ID: <3D5EC7D2992BD211A95600A0C9CE047F017E22DA@isjhbex01.is.co.za> From: Geoff Rehmet To: =?iso-8859-1?Q?=27S=F8ren_Schmidt=27?= Cc: "'current@freebsd.org'" Subject: RE: CALL FOR TESTERS of new ATA/ATAPI driver.. Date: Wed, 3 Mar 1999 09:47:16 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 02-Mar-99 SXren Schmidt wrote: > > > Its in the works, together with the tagged queuing some of the > > > newer drives supports. > > Wow! :) > >=20 > > Is there any chance od adding the ability to 'wire' devices=20 > a la SCSI? :) >=20 > I'll think about it, but lots of things has higher priority... >=20 > -S=F8ren I just repeated the Bonnie tests without X running, on a freshly booted machine. (WD is still with X and netscape.) As I said, I am not = running any flags on WD, but asl Luigi pointed out, I could probably do with some newer hard drives! Geoff. -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU = /sec %CPU ATA+X+Nets 64 3237 69.0 2913 14.0 1409 9.4 2951 59.3 3043 11.6 = 55.9 2.4 WD+X+Netsc 64 2556 54.5 2902 13.3 1457 9.7 1987 40.3 3082 13.2 = 59.1 2.0 ATA-noX 64 3340 69.7 2984 11.9 1400 8.6 3135 62.4 3182 9.4 = 135.3 4.4 ATA-noX1 128 3221 68.5 2860 13.4 1169 7.6 2961 58.4 3038 12.2 = 54.2 2.3 Geoff. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 0:27:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 73ACB14BD8 for ; Wed, 3 Mar 1999 00:27:27 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.1) with ESMTP id JAA08963; Wed, 3 Mar 1999 09:17:48 +0100 (CET) (envelope-from leifn@swimsuit.internet.dk) Date: Wed, 3 Mar 1999 09:17:47 +0100 (CET) From: Leif Neland X-Sender: leifn@arnold.neland.dk To: Thomas Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: Printing is vvveeerrryyy slow In-Reply-To: <199903030732.XAA65447@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 On Tue, 2 Mar 1999, Thomas Dean wrote: > I am running smp, 4.0-current, as of Mon Feb 15 03:34:29 PST 1999. > > Printing is very slow. I have a HP LaserJet III attached to lpt0. > Printing in the pcl, text, mode is slower than I expect. Printing in > the postscipt mode is extremely slow. A 30K postscript file has been > OVER 5 minutes and is not finished! > > >From dmesg: > ... > ppc0 at 0x378 irq 7 on isa > ppc0: PC87334 chipset (PS2/NIBBLE) in COMPATIBLE mode > lpt0: on ppbus 0 > lpt0: Interrupt-driven port I have the same problem. The simple answer is that interrupt-driven printing doesn't work for you, and you have to switch to polled printing: lptcontrol -p But this leads to the question why it doesn't work for you and me, and how to debug it. Is it printer, cable, port, or freebsd-config, which is to blame? I don't know how to proceed either... Leif Neland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 0:30:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 1513814BD8 for ; Wed, 3 Mar 1999 00:30:37 -0800 (PST) (envelope-from bright@cygnus.rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id DAA25951; Wed, 3 Mar 1999 03:30:38 -0500 (EST) Date: Wed, 3 Mar 1999 03:30:34 -0500 (EST) From: Alfred Perlstein To: Thomas Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: Printing is vvveeerrryyy slow In-Reply-To: <199903030732.XAA65447@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 On Tue, 2 Mar 1999, Thomas Dean wrote: > I am running smp, 4.0-current, as of Mon Feb 15 03:34:29 PST 1999. > > Printing is very slow. I have a HP LaserJet III attached to lpt0. > Printing in the pcl, text, mode is slower than I expect. Printing in > the postscipt mode is extremely slow. A 30K postscript file has been > OVER 5 minutes and is not finished! have you tried: lptcontrol -p I remeber the friendlies on #freebsd suggesting this to me when i had similar symptoms last year. (try other lptcontrol settings as well) -Alfred > tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 1: 1:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 8B9CF14BEA for ; Wed, 3 Mar 1999 01:01:28 -0800 (PST) (envelope-from geoff@rucus.ru.ac.za) Received: (qmail 12460 invoked by uid 268); 3 Mar 1999 11:02:50 -0000 Message-ID: <19990303110250.12459.qmail@rucus.ru.ac.za> Subject: Re: Printing is vvveeerrryyy slow In-Reply-To: from Alfred Perlstein at "Mar 3, 1999 3:30:34 am" To: bright@cygnus.rush.net (Alfred Perlstein) Date: Wed, 3 Mar 1999 11:02:50 +0000 (GMT) Cc: current@freebsd.org Reply-To: "Geoff Rehmet" From: "Geoff Rehmet" X-Mailer: ELM [version 2.4ME+ PL43 (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 Alfred Perlstein writes : > > Printing is very slow. I have a HP LaserJet III attached to lpt0. > > Printing in the pcl, text, mode is slower than I expect. Printing in > > the postscipt mode is extremely slow. A 30K postscript file has been > > OVER 5 minutes and is not finished! > > have you tried: > lptcontrol -p > > I remeber the friendlies on #freebsd suggesting this > to me when i had similar symptoms last year. It's a long long time since I was working on the lpt driver. This kind of symptom was a common problem during its development. I haveen't been able to really appreciate the code for the nltp driver, so I also can't really see if there is a problem. Biggest problem when I was hacking on the lpt driver was that interrupts tended to get lost sometimes. I seem to recall, that there were some problems with slow printing that just could not be fixed. Going into polled mode (lptcotnrol -p) is probably your best bet at the moment. Geoff. -- Geoff Rehmet, The Internet Solution geoffr@is.co.za; geoff@rucus.ru.ac.za; csgr@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 1: 7:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 6C3E214BEA for ; Wed, 3 Mar 1999 01:07:38 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 18969 invoked from network); 3 Mar 1999 09:07:19 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 3 Mar 1999 09:07:19 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id EAA00298; Wed, 3 Mar 1999 04:07:14 -0500 (EST) Message-Id: <199903030907.EAA00298@y.dyson.net> Subject: Re: lockmgr panic with mmap() In-Reply-To: from Brian Feldman at "Mar 2, 99 06:29:31 pm" To: green@unixhelp.org (Brian Feldman) Date: Wed, 3 Mar 1999 04:07:14 -0500 (EST) Cc: alc@cs.rice.edu, 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 Brian Feldman said: > > > > The lock manager isn't bright enough to detect that the process > > already holds a read lock when it attempts to get the write lock. > > Thus, you get the "thrd_sleep" instead of a panic. > > > > In short, same bug, different symptoms. > > > Ahh, makes sense. > > Quick question: how in the heck did you learn this whole VM system? > Alan has had a history helping on the VM code for quite a while, and has contributed some really good ideas. Frankly, he appears to understand the code as well as anyone does. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 1:18: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 67BC114F7F for ; Wed, 3 Mar 1999 01:16:57 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA87214; Wed, 3 Mar 1999 09:15:58 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 3 Mar 1999 09:15:58 +0000 (GMT) From: Doug Rabson To: Chuck Robey Cc: Thomas Dean , mark@grondar.za, freebsd-current@freebsd.org Subject: Re: egcs and gcc 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, 2 Mar 1999, Chuck Robey wrote: > On Tue, 2 Mar 1999, Doug Rabson wrote: > > > That was put in extremely recently. The reason it doesn't build a shared > > library by default is to avoid potential conflict with the system > > libstdc++. > > > > If you enable it, the port will install the shared lib in > > /usr/lib/gcc-lib/.../libstdc++.so. You may need to add a runpath option > > to your link to point the executable at the directory. > > Doug, my egcs (when I tell it to --enable-shared) installs: > > libstdc++.so > libstdc++.so.2.9 and > libstdc++.so.2.9.0 > > How about I just keep the first one, kill the middle one, and make the > real file libstdc++.so.3 (so it keeps our numbering). I'm not sure > about the rules for this, since elf ... will stuff looking for > libstdc++.so.2 find my new libstdc++.so.3, or will the new one (with > it's incompatible format, like you said) be safe? It depends on the SONAME field inside the shared library. The full name of the lib needs to match the SONAME I think (which is libstdc++.so.2.9 in my build). I realise that the naming doesn't follow the ports tree rules for shared libs but it shouldn't cause conflicts if you use runpaths to point at its location. I use '-Wl,-rpath=/usr/local/lib/gcc-lib/...' when I link stuff that I want to use the shared lib. Hopefully, this is only a short term measure until we get the beast properly integrated into the build. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 2:34:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id E4EEF15370 for ; Wed, 3 Mar 1999 02:34:24 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.1) with ESMTP id LAA44051; Wed, 3 Mar 1999 11:26:50 +0100 (CET) (envelope-from leifn@swimsuit.internet.dk) Date: Wed, 3 Mar 1999 11:26:41 +0100 (CET) From: Leif Neland X-Sender: leifn@arnold.neland.dk To: Geoff Rehmet Cc: current@FreeBSD.ORG Subject: Re: Printing is vvveeerrryyy slow In-Reply-To: <19990303110250.12459.qmail@rucus.ru.ac.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's a long long time since I was working on the lpt driver. This > kind of symptom was a common problem during its development. I > haveen't been able to really appreciate the code for the nltp > driver, so I also can't really see if there is a problem. > Biggest problem when I was hacking on the lpt driver was that > interrupts tended to get lost sometimes. I seem to recall, that > there were some problems with slow printing that just could not > be fixed. Is there a way to test if interrupts are getting serviced? A counter of interrupts? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 2:41:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-spool.is.co.za (mail-spool.is.co.za [196.4.160.4]) by hub.freebsd.org (Postfix) with ESMTP id ACEDE14DEA for ; Wed, 3 Mar 1999 02:37:42 -0800 (PST) (envelope-from geoffr@is.co.za) Received: from admin.is.co.za (admin.is.co.za [196.23.0.9]) by mail-spool.is.co.za (8.8.8/IShub#3) with ESMTP id MAA25642; Wed, 3 Mar 1999 12:37:02 +0200 Received: from isjhbex01.is.co.za (isjhbex01.is.co.za [196.26.1.16]) by admin.is.co.za (8.8.6/8.7.3/ISsubsidiary#1) with ESMTP id MAA15690; Wed, 3 Mar 1999 12:36:19 +0200 (GMT) Received: by isjhbex01.is.co.za with Internet Mail Service (5.5.2232.9) id <100PSRNH>; Wed, 3 Mar 1999 12:30:53 +0200 Message-ID: <3D5EC7D2992BD211A95600A0C9CE047F017E22E3@isjhbex01.is.co.za> From: Geoff Rehmet To: "'Leif Neland'" Cc: current@FreeBSD.ORG Subject: RE: Printing is vvveeerrryyy slow Date: Wed, 3 Mar 1999 12:30:44 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From what I recall, (and a very brief look at the code again), you would have to look at when lptintr() gets called. There is (I don't recall) any counter. I didn't go grovelling anywhere outside the lpt code when I was working on it. You may have to add some debug code to diagnose what is happening. Geoff. > -----Original Message----- > From: Leif Neland [mailto:leifn@neland.dk] > Sent: 03 March 1999 12:27 > To: Geoff Rehmet > Cc: current@FreeBSD.ORG > Subject: Re: Printing is vvveeerrryyy slow > > > > It's a long long time since I was working on the lpt driver. This > > kind of symptom was a common problem during its development. I > > haveen't been able to really appreciate the code for the nltp > > driver, so I also can't really see if there is a problem. > > Biggest problem when I was hacking on the lpt driver was that > > interrupts tended to get lost sometimes. I seem to recall, that > > there were some problems with slow printing that just could not > > be fixed. > > Is there a way to test if interrupts are getting serviced? A > counter of > interrupts? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 3:26:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8A06E1507B for ; Wed, 3 Mar 1999 03:26:08 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id DAA39951; Wed, 3 Mar 1999 03:25:39 -0800 (PST) (envelope-from obrien) Date: Wed, 3 Mar 1999 03:25:39 -0800 From: "David O'Brien" To: Chan Yiu Wah Cc: freebsd-current@FreeBSD.ORG Subject: Re: compiler egcs 1.1.1 error Message-ID: <19990303032539.B39899@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199903022139.FAA11655@b1.hkstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199903022139.FAA11655@b1.hkstar.com>; from Chan Yiu Wah on Wed, Mar 03, 1999 at 05:39:04AM +0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ir > /usr/info/dir; fi > install-info /usr/info/cpp.info /usr/info/dir > install-info: Undefined error: 0 for /usr/info/dir > *** Error code 1 This is a known problem. Sometimes it occurs, sometimes it doesn't. I don't use info files, so I know zero about them or what this error is about. If any GNU info experts out there can lend a hand, I'm all ears. -- -- David (obrien@NUXI.com -or- obrien@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 Mar 3 4:15:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id D4519155CB for ; Wed, 3 Mar 1999 04:15:18 -0800 (PST) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.3/8.9.3) with ESMTP id NAA57320; Wed, 3 Mar 1999 13:13:19 +0100 (CET) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.9.2/8.9.2) id NAA23816; Wed, 3 Mar 1999 13:13:11 +0100 (CET) From: Cejka Rudolf Message-Id: <199903031213.NAA23816@kazi.dcse.fee.vutbr.cz> Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? To: freebsd-current@freebsd.org (freebsd-current@freebsd.org) Date: Wed, 3 Mar 1999 13:13:10 +0100 (CET) Cc: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>> >The only thing that bit me was that I used wd0 and wd2 with the older >>>> >driver, whereas the newer driver automatically decided to use ad0 and >>>> >ad1. This is "expected" behaviour, but it's something for other weenies >>>> >to watch out for. :-) >>>> >>>> This breakage was announced :-). >>> >>>Besides, it is not even a breakage. It finally got _unbroken_. :-) >> >>It is breakage, and should be fixed. > >It isn't breakage when everybody else assigns identities to ATA disks >sequentially, irespective of how much other gunk (Ie: CD, Tape) is >present on the busses. From my point of view - it is breakage. And I'm afraid to use new ATA driver. Why? Because sometimes I'm booting my FreeBSD box with/without one additional drive. With old driver I knew exact wd* numbering from positions on the busses. How can I determine ad* numbering now? How can I ensure stable number for other drives and another stable number for additional "portable" drive? It's really frustrating if I add new drive (anywhere on the busses) and other drives change their numbers - it's good base for big troubles (infinite changing /etc/fstab and so on). Or is there any solution with new ATA driver? What was bad with old static drive numbering? --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Technical University of Brno, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 4:28:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailin.hkstar.com (cygnus.hkstar.com [202.82.3.13]) by hub.freebsd.org (Postfix) with ESMTP id 31B35154D5 for ; Wed, 3 Mar 1999 04:28:31 -0800 (PST) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by mailin.hkstar.com (8.8.8/8.8.5) with ESMTP id UAA14806 for ; Wed, 3 Mar 1999 20:28:13 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id UAA25257 for freebsd-current@freebsd.org; Wed, 3 Mar 1999 20:28:10 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199903031228.UAA25257@b1.hkstar.com> Subject: Is there exist CJK code for supporting multi languages To: freebsd-current@freebsd.org Date: Wed, 3 Mar 1999 20:28:10 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] 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 Hello, I would like to know if there exist CJK code for freebsd-current. If so, please show me the ftp or url. Thanks. Clarence To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 4:41:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id BCC9414BD4 for ; Wed, 3 Mar 1999 04:40:56 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10IAwI-000KbJ-00; Wed, 3 Mar 1999 14:39:50 +0200 From: Sheldon Hearn To: Cejka Rudolf Cc: freebsd-current@freebsd.org (freebsd-current@freebsd.org), sos@freebsd.dk Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-reply-to: Your message of "Wed, 03 Mar 1999 13:13:10 +0100." <199903031213.NAA23816@kazi.dcse.fee.vutbr.cz> Date: Wed, 03 Mar 1999 14:39:50 +0200 Message-ID: <79192.920464790@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 03 Mar 1999 13:13:10 +0100, Cejka Rudolf wrote: > It's really frustrating if I add new drive (anywhere on the busses) and > other drives change their numbers - it's good base for big troubles > (infinite changing /etc/fstab and so on). Fair enough. But in real life, you don't add a new drive "anywhere on the busses". You know _exactly_ which controller you're attaching the drive to, and you know whether the drive is the master or the slave. This information is enough for you to figure out _exactly_ where in the probing the drive will be "spotted" and numbered. I'm not sure I understand what real-world frustrations people are having here. Is this thread the product of reactionary criticism, or are there real examples of situations in which there are serious disadvantages to the way Soren has things working? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 5:10: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (unknown [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 6A28914F28 for ; Wed, 3 Mar 1999 05:10:03 -0800 (PST) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Wed, 3 Mar 1999 14:12:00 +0100 Message-ID: <97A8CA5BF490D211A94F0000F6C2E55D097552@s-lmh-wi-900.corpnet.at> From: Ladavac Marino To: 'Sheldon Hearn' , Cejka Rudolf Cc: freebsd-current@freebsd.org, sos@freebsd.dk Subject: RE: ATAPI and ATAPI_STATIC with the new ATA* driver? Date: Wed, 3 Mar 1999 14:07:22 +0100 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Sheldon Hearn [SMTP:sheldonh@iafrica.com] > Sent: Wednesday, March 03, 1999 1:40 PM > To: Cejka Rudolf > Cc: freebsd-current@freebsd.org; sos@freebsd.dk > Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? > I'm not sure I understand what real-world frustrations people are > having > here. Is this thread the product of reactionary criticism, or are > there > real examples of situations in which there are serious disadvantages > to > the way Soren has things working? > [ML] Well, it's for those people who plug a drive occasionally into a computer. They don't want other drives moved around. This is the situation that the external SCSI disc case owners live with for years now, and was the reason device wiring was introduced for SCSI devices. Soeren said that the same mechanism could be added for atapi devices as well (yet better, extended to include the atapi devices as well). He just doesn't currently have time to do it right now. /Marino > Ciao, > Sheldon. > > > 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 Mar 3 5:20:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id E4BA91549B for ; Wed, 3 Mar 1999 05:19:53 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10IBXV-0002kp-00; Wed, 3 Mar 1999 15:18:17 +0200 From: Sheldon Hearn To: Ladavac Marino Cc: Cejka Rudolf , freebsd-current@freebsd.org, sos@freebsd.dk Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-reply-to: Your message of "Wed, 03 Mar 1999 14:07:22 +0100." <97A8CA5BF490D211A94F0000F6C2E55D097552@s-lmh-wi-900.corpnet.at> Date: Wed, 03 Mar 1999 15:18:17 +0200 Message-ID: <10590.920467097@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 03 Mar 1999 14:07:22 +0100, Ladavac Marino wrote: > [ML] Well, it's for those people who plug a drive occasionally > into a computer. They don't want other drives moved around. Thanks for the feedback. Jeremy Lea also provided in private mail quite a detailed example of why device wiring for the ATA* driver is desirable. Guess the answer for now is that people who can't live without statically numbered drives continue to use the older IDE driver or mail Soren diffs for adding device wiring support. :-) Thanks again, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 5:22:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id CF59114E93 for ; Wed, 3 Mar 1999 05:22:08 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id IAA82252; Wed, 3 Mar 1999 08:18:59 -0500 (EST) Date: Wed, 3 Mar 1999 08:18:59 -0500 (EST) From: Chuck Robey To: Geoff Rehmet Cc: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: Printing is vvveeerrryyy slow In-Reply-To: <19990303110250.12459.qmail@rucus.ru.ac.za> 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, 3 Mar 1999, Geoff Rehmet wrote: > Alfred Perlstein writes : > > > Printing is very slow. I have a HP LaserJet III attached to lpt0. > > > Printing in the pcl, text, mode is slower than I expect. Printing in > > > the postscipt mode is extremely slow. A 30K postscript file has been > > > OVER 5 minutes and is not finished! > > > > have you tried: > > lptcontrol -p > > > > I remeber the friendlies on #freebsd suggesting this > > to me when i had similar symptoms last year. > It's a long long time since I was working on the lpt driver. This > kind of symptom was a common problem during its development. I > haveen't been able to really appreciate the code for the nltp > driver, so I also can't really see if there is a problem. > Biggest problem when I was hacking on the lpt driver was that > interrupts tended to get lost sometimes. I seem to recall, that > there were some problems with slow printing that just could not > be fixed. > Going into polled mode (lptcotnrol -p) is probably your best bet > at the moment. Geoff, isn't it true that the largest fraction of folks having this problem simply have got their interrupts in their machines set in such a way that there are 2 (or more) devices on IRQ 7? It's almost always a music card doing it, too (although I saw one network card that defaulted to IRQ 7 on install also). People refuse to believe that they can't have more than one card using an IRQ, and so they have this problem. To be honest, although I'm sure that *some* folks having the slow printing problem don't have IRQ 7 mis-set, I haven't seen one real case where it wasn't that, yet. I've followed a good number of those to resolution, guys from freebsd-questions list. ----------------------------+----------------------------------------------- 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 picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 5:28:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 68F6514F42 for ; Wed, 3 Mar 1999 05:28:29 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id OAA86894; Wed, 3 Mar 1999 14:27:20 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903031327.OAA86894@freebsd.dk> Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-Reply-To: <10590.920467097@axl.noc.iafrica.com> from Sheldon Hearn at "Mar 3, 1999 3:18:17 pm" To: sheldonh@iafrica.com (Sheldon Hearn) Date: Wed, 3 Mar 1999 14:27:20 +0100 (CET) Cc: mladavac@metropolitan.at, cejkar@dcse.fee.vutbr.cz, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Sheldon Hearn wrote: > Guess the answer for now is that people who can't live without > statically numbered drives continue to use the older IDE driver or mail > Soren diffs for adding device wiring support. :-) Well, well, don't panic :) I'll provide an option in the next commit round that gives the same numbering as the old driver... This will have to do for now, as getting ATAPI drives fixed also is a bit more tricky (hint changer devices). If all goes well, it will be there tonight (CET), as I also have a LS120/ZIP driver ready, plus alot of other little fixes... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 6:18:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 2CF4B154FB for ; Wed, 3 Mar 1999 06:17:41 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega. (async2-02.iptelecom.net.ua [212.42.68.130]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id QAA22397; Wed, 3 Mar 1999 16:17:27 +0200 (EET) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id QAA10632; Wed, 3 Mar 1999 16:17:16 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <36DD4451.C74DCA90@altavista.net> Date: Wed, 03 Mar 1999 16:16:49 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: =?x-user-defined?Q?S=F8ren?= Schmidt Cc: current@FreeBSD.ORG Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. References: <199903012121.WAA82163@freebsd.dk> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is results of testing my machine (Toshiba Satellite Pro 445CDX notebook). Shows not very huge improvement yet ;) wd driver:               -------Sequential Output-------- ---Sequential Input-- --Random--               -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine    MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU  /sec %CPU                   100  3318 63.9  3260 12.1  1331  8.1  3361 56.8  3397 13.7  59.2  2.8 ata driver:               -------Sequential Output-------- ---Sequential Input-- --Random--               -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine    MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU  /sec %CPU                   100  3322 63.2  3244 11.9  1233  7.7  3374 55.4  3398 13.4  60.4  2.8 dmesg-ata: CPU: Pentium/P55C (132.63-MHz 586-class CPU)   Origin = "GenuineIntel"  Id = 0x543  Stepping=3   Features=0x8001bf avail memory = 30302208 (29592K bytes) ata0 at 0x1f0-0x1f7 irq 14 on isa ad0: ATA-? disk at ata0 as master ad0: 1376MB (2818368 sectors), 2796 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue ad0s2: type 0xa5, start 63, end = 1433375, size 1433313 ad0s2: C/H/S end 1023/11/63 (967490) != end 1433375: invalid ad0s3: type 0xa5, start 1433376, end = 2732939, size 1299564 : OK ad0s4: type 0x6, start 2732940, end = 2817989, size 85050 : OK dmesg-wd: CPU: Pentium/P55C (132.63-MHz 586-class CPU)   Origin = "GenuineIntel"  Id = 0x543  Stepping=3   Features=0x8001bf avail memory = 30289920 (29580K bytes) wdc0 at 0x1f0-0x1f7 irq 14 flags 0xffffffff on isa wdc0: unit 0 (wd0): , LBA, 32-bit, multi-block-16, sleep-hack wd0: 1376MB (2818368 sectors), 2982 cyls, 15 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 wd0s2: type 0xa5, start 63, end = 1433375, size 1433313 wd0s2: C/H/S end 1023/11/63 (967490) != end 1433375: invalid wd0s3: type 0xa5, start 1433376, end = 2732939, size 1299564 : OK wd0s4: type 0x6, start 2732940, end = 2817989, size 85050 : OK     To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 7: 8:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (Postfix) with ESMTP id 178AF14E97 for ; Wed, 3 Mar 1999 07:07:34 -0800 (PST) (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 KAA27508; Wed, 3 Mar 1999 10:04:59 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Wed, 3 Mar 1999 10:04:59 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: SXren Schmidt Cc: "Daniel O'Connor" , current@FreeBSD.ORG, geoffr@is.co.za Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-Reply-To: <199903030731.IAA86207@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Mar 1999, SXren Schmidt wrote: > It seems Daniel O'Connor wrote: > > > > On 02-Mar-99 SXren Schmidt wrote: > > > Its in the works, together with the tagged queuing some of the > > > newer drives supports. > > Wow! :) > > > > Is there any chance od adding the ability to 'wire' devices a la SCSI? :) > > I'll think about it, but lots of things has higher priority... So, one of my great FreeBSD experiences was when one of the three IDE drives in my server died, yet the system was able to survive its automated weekly boot ten minutes later, and I could restore from a tape backup to another drive. The great thing about this was that I was over 500 miles away logged in via the network performing this recovery. Having the drives automatically renumber themselves on the complete failure of one drive (and it was fairly complete) would have been a disaster. This is especially true when one partition is used as a /tmp partition, and is automatically cleaned at boot :-(. Wiring devices introduce stability by not causing unexpected behavior in the event of failure: rather than having the mounting of partitions occur incorrectly, it merely doesn't mount the failed partitions. In general, I do not like the devices-allocated-in-probe-order behavior: it doesn't take much to reorder two SCSI controllers in a kernel, especially if we start using an automated admin tool to configure kernels at some point. I just don't like that failures can result in very situation-dependent behavior. Inserting a new CDROM device should not renumber my existing devices. This presumably becomes more pressing when one starts doing hot-swap pccard-style devices. If you leave the device plugged in across a reboot, its device name may have changed :-(, or might have gotten stuck ahead of the boot device in the kernel probes. Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 7:12:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from yyy.or.jp (host03.interwave.or.jp [202.214.252.3]) by hub.freebsd.org (Postfix) with SMTP id BD87914FE8 for ; Wed, 3 Mar 1999 07:12:17 -0800 (PST) (envelope-from hnokubi@yyy.or.jp) Received: (qmail 7067 invoked from network); 4 Mar 1999 00:11:58 +0900 Received: from urayasu110.interwave.or.jp (HELO ppp-client.yyy.or.jp) (210.138.157.146) by mail.yyy.or.jp with SMTP; 4 Mar 1999 00:11:58 +0900 Received: from sassaby.nokubi.or.jp (sassaby.nokubi.or.jp [192.168.9.3]) by ppp-client.yyy.or.jp (8.9.1/3.5Wpl7-ppp) with ESMTP id AAA04278 for ; Thu, 4 Mar 1999 00:15:38 +0900 (JST) Received: from sassaby.nokubi.or.jp (localhost.nokubi.or.jp [127.0.0.1]) by sassaby.nokubi.or.jp (8.9.2/3.5Wpl7-glove) with ESMTP id AAA00678 for ; Thu, 4 Mar 1999 00:11:15 +0900 (JST) To: current@FreeBSD.ORG Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-reply-to: Your message of "Tue, 02 Mar 99 00:34:16 PST." From: hnokubi@yyy.or.jp Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Thu, 04 Mar 1999 00:11:14 +0900 Message-Id: <19990303151218.BD87914FE8@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do you have any plans to support OPTICAL device? I want to use my PD drive (NEC ODX654P), and some other people want to use ATAPI MO. I've already made patch for PD/CD drive, and registered it as PR kern/10116. But it's not so good patch, because my PD drive has 2 LUN's. LUN0 is CD-ROM and LUN1 is PD. If new driver supports multiple LUN ATAPI device, PD drive support becomes to be easy, I believe. Thanks in advance. NOKUBI Hirotaka To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 7:19:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from yip.org (yip.org [142.154.6.140]) by hub.freebsd.org (Postfix) with ESMTP id 1811814DAB for ; Wed, 3 Mar 1999 07:19:52 -0800 (PST) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by yip.org (8.8.8/8.8.8) with SMTP id KAA00902 for ; Wed, 3 Mar 1999 10:19:58 -0500 (EST) (envelope-from melange@yip.org) Date: Wed, 3 Mar 1999 10:19:57 -0500 (EST) From: Bob K To: current@FreeBSD.ORG Subject: Re: New driver and ATAPI DMA? In-Reply-To: <19990302203405.A65277@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 Tue, 2 Mar 1999, Lee Cremeans wrote: > Will this new ATA driver finally support DMA correctly on ATAPI devices (as > opposed to pure ATA disk devices)? This is a feature that could really come > in handy for me (as well as a reason to migrate back to -current from 3.1 :) Which brings up a question I've been wondering for a bit. Will it be backported to 3.1-stable, or will there be patches? I'd be willing to test 'em... melange@yip.org - Shave A Tree Today! (TM) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 7:44: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa15-40.ix.netcom.com [207.93.148.40]) by hub.freebsd.org (Postfix) with ESMTP id 1727014EAC for ; Wed, 3 Mar 1999 07:43:00 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id HAA00622; Wed, 3 Mar 1999 07:42:35 -0800 (PST) (envelope-from tomdean) Date: Wed, 3 Mar 1999 07:42:35 -0800 (PST) Message-Id: <199903031542.HAA00622@ix.netcom.com> From: Thomas Dean To: chuckr@mat.net Cc: geoffr@is.co.za, bright@cygnus.rush.net, current@FreeBSD.ORG In-reply-to: (message from Chuck Robey on Wed, 3 Mar 1999 08:18:59 -0500 (EST)) Subject: Re: Printing is vvveeerrryyy slow Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My machine is a DEC Celebris 5133DP. The only device added since purchase was de0. This is a recent problem, within the past few months. Or, was I running polled before that? I used the default. From an old config, I see: device lpt0 at isa? port? tty irq 7 vector lptintr dmesg: ncr0: rev 0x02 int a irq 11 on pci0.1.0 vga0: rev 0x01 int a irq 9 on pci0.6.0 de0: rev 0x11 int a irq 10 on pci0.8.0 atkbd0 irq 1 on isa psm0 irq 12 on isa sio0 at 0x3f8-0x3ff irq 4 on isa sio1 at 0x2f8-0x2ff irq 3 on isa ppc0 at 0x378 irq 7 on isa fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa config: controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr controller ppc0 at isa? port ? tty irq 7 I think this accounts for everything. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 7:47:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 7B320154A4 for ; Wed, 3 Mar 1999 07:47:19 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id KAA19897; Wed, 3 Mar 1999 10:44:09 -0500 (EST) Date: Wed, 3 Mar 1999 10:44:09 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= Cc: Sheldon Hearn , mladavac@metropolitan.at, cejkar@dcse.fee.vutbr.cz, freebsd-current@FreeBSD.ORG Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-Reply-To: <199903031327.OAA86894@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Mar 1999, S=F8ren Schmidt wrote: > It seems Sheldon Hearn wrote: > > Guess the answer for now is that people who can't live without > > statically numbered drives continue to use the older IDE driver or mail > > Soren diffs for adding device wiring support. :-) >=20 > Well, well, don't panic :) >=20 > I'll provide an option in the next commit round that gives the same > numbering as the old driver... >=20 > This will have to do for now, as getting ATAPI drives fixed also > is a bit more tricky (hint changer devices). >=20 > If all goes well, it will be there tonight (CET), as I also have a > LS120/ZIP driver ready, plus alot of other little fixes... Yahoo!! Whoopeeee!! Go Soren, go! >=20 > -S=F8ren >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 Brian Feldman=09=09=09=09=09 _ __ ___ ___ ___ =20 green@unixhelp.org=09=09=09 _ __ ___ | _ ) __| \=20 =09 http://www.freebsd.org/=09 _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve!=09 _ __ ___ ____ _____ |___/___/___/=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 7:59:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (Postfix) with SMTP id 1F5F214F43; Wed, 3 Mar 1999 07:58:56 -0800 (PST) (envelope-from alk@avalon.East.Sun.COM) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id HAA03087; Wed, 3 Mar 1999 07:58:06 -0800 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id KAA11598; Wed, 3 Mar 1999 10:57:41 -0500 Received: from avalon.east.sun.com (hobo124 [129.148.7.124]) by suneast.East.Sun.COM (8.9.1b+Sun/8.8.8) with ESMTP id KAA00907; Wed, 3 Mar 1999 10:57:25 -0500 (EST) Received: (from alk@localhost) by avalon.east.sun.com (8.9.2/8.9.1) id JAA08534; Wed, 3 Mar 1999 09:56:19 -0600 (CST) (envelope-from alk) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 3 Mar 1999 09:56:19 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: sos@freebsd.dk Cc: hardware@freebsd.org Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14045.23386.325036.709568@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Its in the works, together with the tagged queuing some of the > newer drives supports. Whoa! What drives?!?! I want a dozen! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 8: 5:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa15-40.ix.netcom.com [207.93.148.40]) by hub.freebsd.org (Postfix) with ESMTP id 25BD81556D for ; Wed, 3 Mar 1999 08:05:21 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id IAA00695; Wed, 3 Mar 1999 08:04:54 -0800 (PST) (envelope-from tomdean) Date: Wed, 3 Mar 1999 08:04:54 -0800 (PST) Message-Id: <199903031604.IAA00695@ix.netcom.com> From: Thomas Dean To: chuckr@mat.net Cc: geoffr@is.co.za, bright@cygnus.rush.net, current@FreeBSD.ORG In-reply-to: (message from Chuck Robey on Wed, 3 Mar 1999 08:18:59 -0500 (EST)) Subject: Re: Printing is vvveeerrryyy slow Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Changing to polled improved things, somewhat. Printing a 30k postscript file takes 2 minutes. Sending an 9368 byte binary, printer control and setup file takes approximately 1 minute. This is very slow. I will try to setup a DOS or WINNT machine to duplicate this. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 8:44:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from h24-64-221-247.gv.wave.shaw.ca (24.64.221.247.bc.wave.home.com [24.64.221.247]) by hub.freebsd.org (Postfix) with ESMTP id 4688515011 for ; Wed, 3 Mar 1999 08:43:02 -0800 (PST) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Received: from h24-64-221-247.gv.wave.shaw.ca (localhost [127.0.0.1]) by h24-64-221-247.gv.wave.shaw.ca (8.9.3/8.9.2) with ESMTP id IAA01124 for ; Wed, 3 Mar 1999 08:42:37 -0800 (PST) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Message-Id: <199903031642.IAA01124@h24-64-221-247.gv.wave.shaw.ca> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-reply-to: Your message of "Thu, 04 Mar 1999 00:11:14 +0900." <19990303151218.BD87914FE8@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Mar 1999 08:42:37 -0800 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm curious how the new driver handles numbering. You said in your first mail that drives are numbered by probe order? I have two 4 gig IDE drives, both single masters on separate channels. I'm only booting from the first one, so that's not a problem, but the first is called wd0 and the second wd2. My kernel config is as follows: controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff disk wd0 at wdc0 drive 0 controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xa0ffa0ff disk wd2 at wdc1 drive 0 This way I can stick a slave on the first controller and it won't change the numbering. I may be missing something though. anyway, what will the new driver call my second hard drive? and can I wire it down to be wd2? Would this be all I add to my kernel config? controller ata0 device atadisk0 # ATA disks or do I need a device for each drive? I'm also assuming that this thing will work fine with Vinum? Thank you. -- obfuscate v.t. darken; obscure; bewilder. int i;main(){for(;i["]; Wed, 3 Mar 1999 08:57:23 -0800 (PST) (envelope-from jkb@shell6.ba.best.com) Received: (from jkb@localhost) by shell6.ba.best.com (8.9.3/8.9.2/best.sh) id IAA22659 for current@freebsd.org; Wed, 3 Mar 1999 08:57:06 -0800 (PST) Message-ID: <19990303085705.B18330@best.com> Date: Wed, 3 Mar 1999 08:57:05 -0800 From: "Jan B. Koum " To: current@freebsd.org Subject: /usr/bin/lock is broken in 3.0 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, but I just could not track down the problem myself :( With 2.2 box you get: shell6: {104} lock -np lock: /dev/ttyp8 on shell6.ba.best.com. no timeout time now is Wed Mar 3 08:52:55 PST 1999 Key: And on 3.x/4.x you get: nautilus% ls -l /usr/bin/lock -r-sr-xr-x 1 root wheel 5636 Feb 3 21:06 /usr/bin/lock nautilus% lock -np nautilus% Can someone tell me what is going on? -- Yan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 9: 7: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 776B014F73 for ; Wed, 3 Mar 1999 09:06:53 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10IF6H-0005dF-00; Wed, 3 Mar 1999 19:06:25 +0200 From: Sheldon Hearn To: "Jan B. Koum " Cc: current@freebsd.org Subject: Re: /usr/bin/lock is broken in 3.0 In-reply-to: Your message of "Wed, 03 Mar 1999 08:57:05 PST." <19990303085705.B18330@best.com> Date: Wed, 03 Mar 1999 19:06:25 +0200 Message-ID: <21648.920480785@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 03 Mar 1999 08:57:05 PST, "Jan B. Koum " wrote: > nautilus% ls -l /usr/bin/lock > -r-sr-xr-x 1 root wheel 5636 Feb 3 21:06 /usr/bin/lock > nautilus% lock -np > nautilus% > > Can someone tell me what is going on? Works for me. $ uname -a FreeBSD axl.noc.iafrica.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Mar 2 16:15:30 SAST 1999 toor@axl.noc.iafrica.com:/usr/src/sys/compile/AXL i386 [sheldonh@axl] ~gnats $ tty /dev/ttyp2 [sheldonh@axl] ~gnats $ lock -np lock: /dev/ttyp2 on axl.noc.iafrica.com. no timeout time now is Wed Mar 3 19:05:16 SAST 1999 You're not using PAM, perhaps? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 9:16:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from holly.dyndns.org (ip90.houston2.tx.pub-ip.psi.net [38.11.201.90]) by hub.freebsd.org (Postfix) with ESMTP id CE9B014EDA for ; Wed, 3 Mar 1999 09:16:34 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id LAA44518; Wed, 3 Mar 1999 11:17:03 -0600 (CST) (envelope-from chris) Date: Wed, 3 Mar 1999 11:17:02 -0600 From: Chris Costello To: "Jan B. Koum " Cc: current@FreeBSD.ORG Subject: Re: /usr/bin/lock is broken in 3.0 Message-ID: <19990303111702.A44474@holly.dyndns.org> Reply-To: chris@calldei.com References: <19990303085705.B18330@best.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3us In-Reply-To: <19990303085705.B18330@best.com>; from Jan B. Koum on Wed, Mar 03, 1999 at 08:57:05AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 3, 1999, Jan B. Koum put this into my mailbox: > Sorry, but I just could not track down the problem myself :( > > With 2.2 box you get: > > shell6: {104} lock -np > lock: /dev/ttyp8 on shell6.ba.best.com. no timeout > time now is Wed Mar 3 08:52:55 PST 1999 > Key: > > And on 3.x/4.x you get: > > nautilus% ls -l /usr/bin/lock > -r-sr-xr-x 1 root wheel 5636 Feb 3 21:06 /usr/bin/lock > nautilus% lock -np > nautilus% > > Can someone tell me what is going on? I don't get this problem. When did you CVSup to -STABLE/-CURRENT? (chris@holly) ~-> lock -pn lock: /dev/ttyp4 on holly.dyndns.org. no timeout time now is Wed Mar 3 11:15:20 CST 1999 Key: (chris@holly) ~-> uname -v FreeBSD 4.0-CURRENT #1: Mon Mar 1 09:37:59 CST 1999 chris@holly.dyndns.org:/usr/src/sys/compile/Holly (New line in uname -v output is coincidental, it's due to my line-wrapping.) > > -- Yan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -Chris -- Powered by FreeBSD 4.0-CURRENT. "The Power to Serve!" int main(int m){main(!main(0));} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 9:18:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 4C0C114F77 for ; Wed, 3 Mar 1999 09:17:04 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10IFGF-0006UU-00 for current@freebsd.org; Wed, 3 Mar 1999 19:16:43 +0200 From: Sheldon Hearn To: current@freebsd.org Subject: Re: /usr/bin/lock is broken in 3.0 In-reply-to: Your message of "Wed, 03 Mar 1999 19:06:25 +0200." <21648.920480785@axl.noc.iafrica.com> Date: Wed, 03 Mar 1999 19:16:43 +0200 Message-ID: <24953.920481403@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 03 Mar 1999 19:06:25 +0200, Sheldon Hearn wrote: > You're not using PAM, perhaps? I'd greatly appreciate it if everyone would ignore that comment. Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 10: 2: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id AA83D14F92 for ; Wed, 3 Mar 1999 10:01:18 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA19942; Thu, 4 Mar 1999 03:01:06 +0900 (JST) Message-ID: <36DD7705.D2D087FC@newsguy.com> Date: Thu, 04 Mar 1999 02:53:09 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Cejka Rudolf Cc: "freebsd-current@freebsd.org" , sos@freebsd.dk Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? References: <199903031213.NAA23816@kazi.dcse.fee.vutbr.cz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cejka Rudolf wrote: > > What was bad with old static drive numbering? Irrespective of all the valid reasons to allow for wiring (but not mandate), static drive numbering is not BIOS compatible (thus, not DOS compatible). This violates POLA. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 10: 2: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id C5A5214FAC for ; Wed, 3 Mar 1999 10:01:35 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id MAA83372; Wed, 3 Mar 1999 12:58:41 -0500 (EST) Date: Wed, 3 Mar 1999 12:58:41 -0500 (EST) From: Chuck Robey To: Thomas Dean Cc: geoffr@is.co.za, bright@cygnus.rush.net, current@FreeBSD.ORG Subject: Re: Printing is vvveeerrryyy slow In-Reply-To: <199903031604.IAA00695@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 On Wed, 3 Mar 1999, Thomas Dean wrote: > Changing to polled improved things, somewhat. > > Printing a 30k postscript file takes 2 minutes. > > Sending an 9368 byte binary, printer control and setup file takes > approximately 1 minute. > > This is very slow. I will try to setup a DOS or WINNT machine to > duplicate this. The thing I posted about IRQs, it isn't dealing with what you have in your kernel, so posting your config wasn't a help; it has solely to do with what is physically existing in your computer. You have to go through your system and do a careful census of exactly what cards you have installed and what irq's they're using. This cannot ignore peripherals installed from your motherboard, either (if you have a bios setting putting something extra on IRQ 7, it's going to cause it just as surely as having a Soundblaster on it will). ----------------------------+----------------------------------------------- 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 picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 10: 2: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id BF65814FA9 for ; Wed, 3 Mar 1999 10:01:28 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA19907; Thu, 4 Mar 1999 03:00:58 +0900 (JST) Message-ID: <36DD73FE.AD07A592@newsguy.com> Date: Thu, 04 Mar 1999 02:40:14 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: dyson@iquest.net Cc: Brian Feldman , alc@cs.rice.edu, current@FreeBSD.ORG Subject: Re: lockmgr panic with mmap() References: <199903030907.EAA00298@y.dyson.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John S. Dyson" wrote: > > Brian Feldman said: > > > > Quick question: how in the heck did you learn this whole VM system? > Alan has had a history helping on the VM code for quite a while, and > has contributed some really good ideas. Frankly, he appears to > understand the code as well as anyone does. And the question is how he managed to. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 10:12:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 5F86114F3A for ; Wed, 3 Mar 1999 10:12:39 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id UAA71493; Wed, 3 Mar 1999 20:12:16 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id UAA80419; Wed, 3 Mar 1999 20:12:10 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199903031812.UAA80419@greenpeace.grondar.za> To: obrien@NUXI.com Cc: current@freebsd.org Subject: Re: bmake/contrib framework for egcs In-Reply-To: Your message of " Tue, 02 Mar 1999 02:56:00 PST." <19990302025600.F13655@relay.nuxi.com> References: <19990302025600.F13655@relay.nuxi.com> Date: Wed, 03 Mar 1999 20:12:06 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" wrote: > I've put the bmake & contrib framework for EGCS at > ftp://ftp.nuxi.com/pub/FreeBSD/egcs > (ftp://ftp.nuxi.com/pub/FreeBSD/egcs/cvs is all you really need) > This is very rough work, but should help us towards our goal. > > In there you will find a CVS tree under ``cvs''. This CVS tree > corresponds to /usr/src in that you will find "src/gnu/usr.bin/cc", > "src/gnu/lib/libstdc++", and "src/contrib/egcs". It would help a lot if you could make it CVSUPpable :-). Those of us in the third world would greatly appreciate that! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 10:14:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id BB667154BB for ; Wed, 3 Mar 1999 10:14:09 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id UAA71497; Wed, 3 Mar 1999 20:13:50 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id UAA80442; Wed, 3 Mar 1999 20:13:49 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199903031813.UAA80442@greenpeace.grondar.za> To: obrien@NUXI.com Cc: Chan Yiu Wah , freebsd-current@freebsd.org Subject: Re: compiler egcs 1.1.1 error In-Reply-To: Your message of " Wed, 03 Mar 1999 03:25:39 PST." <19990303032539.B39899@relay.nuxi.com> References: <199903022139.FAA11655@b1.hkstar.com> <19990303032539.B39899@relay.nuxi.com> Date: Wed, 03 Mar 1999 20:13:48 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" wrote: > > ir > /usr/info/dir; fi > > install-info /usr/info/cpp.info /usr/info/dir > > install-info: Undefined error: 0 for /usr/info/dir > > *** Error code 1 > > This is a known problem. Sometimes it occurs, sometimes it doesn't. I > don't use info files, so I know zero about them or what this error is > about. Look at his paths; /usr/info/dir does not exist. *Sheesh* ;-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 10:28:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id 9B1C914F87 for ; Wed, 3 Mar 1999 10:27:14 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id KAA98780 for freebsd-current@freebsd.org; Wed, 3 Mar 1999 10:26:57 -0800 (PST) Date: Wed, 3 Mar 1999 10:26:57 -0800 (PST) From: David Wolfskill Message-Id: <199903031826.KAA98780@pau-amma.whistle.com> To: freebsd-current@freebsd.org Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-Reply-To: <36DD7705.D2D087FC@newsguy.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Thu, 04 Mar 1999 02:53:09 +0900 >From: "Daniel C. Sobral" >Irrespective of all the valid reasons to allow for wiring (but not >mandate), static drive numbering is not BIOS compatible (thus, not >DOS compatible). This violates POLA. I'm at least as much against POLA violations as anyone... but the real POLA violation I see is the apparent dependence on the BIOS, since it is "controlled" by a process external to the UNIX environment. "DOS compatability" is not one of my concerns; I have difficulty imagining a universe in which it would become one. Indeed, if someone were to claim "DOS compatibility" for something, I would have no way of knowing what that was supposed to imply, since I'm nearly completely unfamiliar with DOS. (The few times I've tried to use it, I would get different results from the same actions on my part, so I gave up.) And yes, I realize that neither my experiences nor perspective may be representative of anyone else. david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 10:33:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 0D39814ED0 for ; Wed, 3 Mar 1999 10:33:04 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id MAA02918; Wed, 3 Mar 1999 12:32:42 -0600 (CST) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id MAA33162; Wed, 3 Mar 1999 12:32:42 -0600 (CST) Date: Wed, 3 Mar 1999 12:32:42 -0600 From: Alan Cox To: "Daniel C. Sobral" Cc: Brian Feldman , current@freebsd.org Subject: Re: lockmgr panic with mmap() Message-ID: <19990303123242.A32461@nonpc.cs.rice.edu> References: <199903030907.EAA00298@y.dyson.net> <36DD73FE.AD07A592@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <36DD73FE.AD07A592@newsguy.com>; from Daniel C. Sobral on Thu, Mar 04, 1999 at 02:40:14AM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 04, 1999 at 02:40:14AM +0900, Daniel C. Sobral wrote: > > And the question is how he managed to. :-) > I graduated from CMU in 1986. While there, I worked part-time on the Mach project. Later, I used the Mach VM code as infrastructure for my Ph.D. thesis on automatic data placement for NUMA multiprocessors. That's probably not what you wanted to hear. :-) In any case, if you and Brian (and others) want to learn more, so that you can contribute, I'll gladly help you. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 11:51:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 7D16B14F88; Wed, 3 Mar 1999 11:50:49 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.1/8.9.1) id OAA19405; Wed, 3 Mar 1999 14:50:31 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <199903031950.OAA19405@misha.cisco.com> Subject: aic0 and CAM To: current@freebsd.org Date: Wed, 3 Mar 1999 14:50:31 -0500 (EST) Cc: nate@freebsd.org, gconnor@cisco.com Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (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 What's the chance the Adaptec-152x controller (aic0) will soon work with 3.1-STABLE? It has pretty horrible performance problems on 2.2.8-STABLE, even when using DMA: [...] 4.4%Sys 91.9%Intr 3.7%User 0.0%Nice 0.0%Idl 4244 inact 204 pci irq9 | | | | | | | | | | 5288 cache 105 aic0 irq11 ==++++++++++++++++++++++++++++++++++++++++++++++ 248 free 104 wdc0 irq14 [...] (which may, of course, be due to the poor design of the board) and we were wondering if upgrading to 3.1-STABLE will help us in the foreseeable future? Thanks! -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 11:57:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 6193C150AA for ; Wed, 3 Mar 1999 11:57:53 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA05332; Wed, 3 Mar 1999 11:57:36 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id LAA78943; Wed, 3 Mar 1999 11:57:35 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 3 Mar 1999 11:57:35 -0800 (PST) Message-Id: <199903031957.LAA78943@vashon.polstra.com> To: phk@critter.freebsd.dk Subject: Re: Request for review: changes to if_vlan.c In-Reply-To: <18961.920316877@critter.freebsd.dk> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <18961.920316877@critter.freebsd.dk>, Poul-Henning Kamp wrote: > > It should have been done with a simple ascii string instead. The > drivers are much better at chewing on it than the "generic" code, > it would be simpler to understand, simpler to implement, you wouldn't > need to rebuild ifconfig all the time and it would be vastly more > flexible. > > Anyone who thinks this sounds like a replay from when I stuck my > fingers in sysctl some years back are right. > > > For some reason, some people around our camp-fire, have a hard time > understanding that compiletime enumeration of potential options > is a concept that died with the "VAX Handbook 1978 edition". > Amen, brother! Get it said! People who claim that strings are "too slow" would benefit greatly from spending a few days with the profiler. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 12: 0:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 6925415052 for ; Wed, 3 Mar 1999 12:00:27 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id PAA22364 for ; Wed, 3 Mar 1999 15:00:09 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA27777; Wed, 3 Mar 1999 15:00:08 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id PAA57784 for freebsd-current@freebsd.org; Wed, 3 Mar 1999 15:00:08 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199903032000.PAA57784@bb01f39.unx.sas.com> Subject: Fatal trap on install w/ 4.0-19990303-SNAP To: freebsd-current@freebsd.org Date: Wed, 3 Mar 1999 15:00:08 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (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, We are attempting to load 4.0-19990303-SNAP on a Dell machine: Optiplex XMT 5120 (120Mhz,48Meg) w/ adaptec 2940 controller &1gig drive. The dual floppy boot process works fine until it changes to the root device. This occurs even after going into config and deleting all unneeded devices. Any comments on how i can help debug this? Thanks! John changing root device to fd0c rootfs is 2880 Kbyte compiled in MFS Fatal trap 9: general protection fault while in kernel mode Instruction pointer = 0x8:0xf021c64f stack pointer = 0x10:0xf3d52e7c frame pointer = 0x10:0xf3d52e7c code segment = bsae 0x0, limit 0xfffff , type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = Interupt enabled, resume, IOPL=0 current process = 2(pagedaemon) interupt mask = net tty bio cam trap number = 9 panic: general protection fault syncing disks.... done To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 12:19:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A2A6D14F89 for ; Wed, 3 Mar 1999 12:17:37 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id MAA25493; Wed, 3 Mar 1999 12:16:20 -0800 Date: Wed, 3 Mar 1999 12:16:20 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: John Polstra Cc: phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: Request for review: changes to if_vlan.c In-Reply-To: <199903031957.LAA78943@vashon.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 > > Amen, brother! Get it said! People who claim that strings are > "too slow" would benefit greatly from spending a few days with the > profiler. Now I'll stir the other pot and say that performance isn't the issue- the issue is that there's nothing that says that strings and identifiers are always easier to use and/or understand than numbers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 12:22:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 11E561517B for ; Wed, 3 Mar 1999 12:22:45 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id VAA05785; Wed, 3 Mar 1999 21:22:24 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id VAA01849; Wed, 3 Mar 1999 21:22:22 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: John Polstra , current@FreeBSD.ORG Subject: Re: Request for review: changes to if_vlan.c In-reply-to: Your message of "Wed, 03 Mar 1999 12:16:20 PST." Date: Wed, 03 Mar 1999 21:22:22 +0100 Message-ID: <1847.920492542@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob w rites: >> >> Amen, brother! Get it said! People who claim that strings are >> "too slow" would benefit greatly from spending a few days with the >> profiler. > >Now I'll stir the other pot and say that performance isn't the issue- the >issue is that there's nothing that says that strings and identifiers are >always easier to use and/or understand than numbers. This is entirely besides the point. We're talking about the cases where people are going trough several layers of topological excercise to pack strings into integer and bit fields rather than to pass them directly. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 12:23:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8E7A215514 for ; Wed, 3 Mar 1999 12:23:53 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id MAA05437; Wed, 3 Mar 1999 12:23:35 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id MAA78979; Wed, 3 Mar 1999 12:23:35 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 03 Mar 1999 12:23:35 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Matthew Jacob Subject: Re: Request for review: changes to if_vlan.c Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > Now I'll stir the other pot and say that performance isn't the > issue- the issue is that there's nothing that says that strings and > identifiers are always easier to use and/or understand than numbers. They are a lot more extensible, though. With strings, you generally have to modify and recompile only the portion of the code that implements new functionality. The client code doesn't have to be modified or even relinked. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 12:34:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 3C5F714FFF for ; Wed, 3 Mar 1999 12:34:05 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.1/8.9.1) id PAA19606 for current@freebsd.org; Wed, 3 Mar 1999 15:33:48 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <199903032033.PAA19606@misha.cisco.com> Subject: Re: Request for review: changes to if_vlan.c In-Reply-To: from John Polstra at "Mar 3, 1999 12:23:35 pm" To: current@freebsd.org Date: Wed, 3 Mar 1999 15:33:48 -0500 (EST) Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (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 > > Now I'll stir the other pot and say that performance isn't the > > issue- the issue is that there's nothing that says that strings and > > identifiers are always easier to use and/or understand than numbers. > They are a lot more extensible, though. With strings, you generally > have to modify and recompile only the portion of the code that > implements new functionality. The client code doesn't have to be > modified or even relinked. May the strerror(3) be a good example of how to deal with numbers AND strings? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 12:37:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from ianai.BlackSun.org (Ianai.blacksun.org [168.100.186.33]) by hub.freebsd.org (Postfix) with ESMTP id 09E9A14ED0 for ; Wed, 3 Mar 1999 12:37:33 -0800 (PST) (envelope-from tugrul@ianai.BlackSun.org) Received: from localhost (tugrul@localhost) by ianai.BlackSun.org (8.8.8/8.8.7) with SMTP id PAA02115 for ; Wed, 3 Mar 1999 15:36:05 -0500 (EST) (envelope-from tugrul@ianai.BlackSun.org) Date: Wed, 3 Mar 1999 15:36:05 -0500 (EST) From: Tugrul To: current@freebsd.org Subject: New ata driver failure on a ISA machine. 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 deleted the annoucement email, but looking over LINT, the following lines seemed appropiate for my 486: controller ata0 at isa? port "IO_WD1" bio irq 14 device atadisk0 First problem I had was that the kernel would not link without defining: controller pci0 Second, at boot: [...] ata0 at 0x1f0-0x1f7 irq 14 on isa [...] ad0: ATA-? disk at ata0 as master ad0: 0MB (0 sectors), 723 cyls, 13 heads, 51 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue changing root device to ad0a error 22: panic cannot mount root (2) Here is what happens on the old driver: [...] wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , multi-block-8 wd0: 234MB (479349 sectors), 723 cyls, 13 heads, 51 S/T, 512 B/S [...] Did I miss something? Either you can provide tips or I can provide debug info :-) Tugrul Galatali To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 12:41:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 17B1714F9D for ; Wed, 3 Mar 1999 12:41:28 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA18102; Wed, 3 Mar 1999 12:26:48 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdF18084; Wed Mar 3 20:26:33 1999 Date: Wed, 3 Mar 1999 12:26:25 -0800 (PST) From: Julian Elischer To: John Polstra Cc: phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: Request for review: changes to if_vlan.c In-Reply-To: <199903031957.LAA78943@vashon.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 Wed, 3 Mar 1999, John Polstra wrote: > In article <18961.920316877@critter.freebsd.dk>, > Poul-Henning Kamp wrote: > > > > > > For some reason, some people around our camp-fire, have a hard time > > understanding that compiletime enumeration of potential options > > is a concept that died with the "VAX Handbook 1978 edition". > > > > Amen, brother! Get it said! People who claim that strings are > "too slow" would benefit greatly from spending a few days with the > profiler. yep To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 12:51:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id DB88C15240; Wed, 3 Mar 1999 12:51:04 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id NAA86828; Wed, 3 Mar 1999 13:50:38 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903032050.NAA86828@panzer.plutotech.com> Subject: Re: aic0 and CAM In-Reply-To: <199903031950.OAA19405@misha.cisco.com> from Mikhail Teterin at "Mar 3, 1999 2:50:31 pm" To: mi@aldan.algebra.com Date: Wed, 3 Mar 1999 13:50:38 -0700 (MST) Cc: current@FreeBSD.ORG, nate@FreeBSD.ORG, gconnor@cisco.com X-Mailer: ELM [version 2.4ME+ PL43 (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 Mikhail Teterin wrote... > What's the chance the Adaptec-152x controller (aic0) will soon work > with 3.1-STABLE? I think the chances are very slim that it will work soon with 3.x or 4.x. It may get done at some point, but I don't think anyone is actively working on it at the moment. > It has pretty horrible performance problems on 2.2.8-STABLE, even when > using DMA: > > [...] > 4.4%Sys 91.9%Intr 3.7%User 0.0%Nice 0.0%Idl 4244 inact 204 pci irq9 > | | | | | | | | | | 5288 cache 105 aic0 irq11 > ==++++++++++++++++++++++++++++++++++++++++++++++ 248 free 104 wdc0 irq14 > [...] > > (which may, of course, be due to the poor design of the board) and > we were wondering if upgrading to 3.1-STABLE will help us in the > foreseeable future? The 152x boards are programmed I/O only, I believe. They don't do DMA. So it won't matter if the driver is rewritten for CAM, you'll still get lousy performance from the board. If you need a supported ISA controller, the Adaptec 154x controllers are supported, as are the Advansys ISA controllers. Both support DMA, and should give you much better performance. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 12:54:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C4E5E15606 for ; Wed, 3 Mar 1999 12:53:59 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id VAA87665; Wed, 3 Mar 1999 21:53:31 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903032053.VAA87665@freebsd.dk> Subject: Re: New driver and ATAPI DMA? In-Reply-To: from Bob K at "Mar 3, 1999 10:19:57 am" To: melange@yip.org (Bob K) Date: Wed, 3 Mar 1999 21:53:31 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Bob K wrote: > On Tue, 2 Mar 1999, Lee Cremeans wrote: > > > Will this new ATA driver finally support DMA correctly on ATAPI devices (as > > opposed to pure ATA disk devices)? This is a feature that could really come > > in handy for me (as well as a reason to migrate back to -current from 3.1 :) > > Which brings up a question I've been wondering for a bit. Will it be > backported to 3.1-stable, or will there be patches? I'd be willing to > test 'em... I think you can take the /sys/dev/ata dir and copy it verbatim to 3.1. Remember to add the files in /sys/i386/conf/files.i386 too. The only problem is the devstat calls, just save of the last parameter... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 12:58:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D14EE14F3A for ; Wed, 3 Mar 1999 12:55:49 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id VAA87674; Wed, 3 Mar 1999 21:55:21 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903032055.VAA87674@freebsd.dk> Subject: Re: New ata driver failure on a ISA machine. In-Reply-To: from Tugrul at "Mar 3, 1999 3:36: 5 pm" To: tugrul@ianai.BlackSun.org (Tugrul) Date: Wed, 3 Mar 1999 21:55:21 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Tugrul wrote: > I deleted the annoucement email, but looking over LINT, the > following lines seemed appropiate for my 486: > > controller ata0 at isa? port "IO_WD1" bio irq 14 > device atadisk0 Correct. > First problem I had was that the kernel would not link without > defining: > > controller pci0 Yup I know.. > Second, at boot: > > [...] > ata0 at 0x1f0-0x1f7 irq 14 on isa > [...] > ad0: ATA-? disk at ata0 as master > ad0: 0MB (0 sectors), 723 cyls, 13 heads, 51 S/T, 512 B/S > ad0: 16 secs/int, 0 depth queue > changing root device to ad0a > error 22: panic cannot mount root (2) That is allready fixed also. Wait until I commit the first update in an hour or so, then it should work... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 12:58:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (Postfix) with ESMTP id E1BBC1568C; Wed, 3 Mar 1999 12:58:36 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell2.aracnet.com (IDENT:1728@shell2.aracnet.com [205.159.88.20]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with ESMTP id MAA11370; Wed, 3 Mar 1999 12:58:12 -0800 Received: from localhost by shell2.aracnet.com (8.8.7) id MAA11058; Wed, 3 Mar 1999 12:58:13 -0800 X-Authentication-Warning: shell2.aracnet.com: beattie owned process doing -bs Date: Wed, 3 Mar 1999 12:58:13 -0800 (PST) From: Brian Beattie To: mi@aldan.algebra.com Cc: current@FreeBSD.ORG, nate@FreeBSD.ORG, gconnor@cisco.com Subject: Re: aic0 and CAM In-Reply-To: <199903031950.OAA19405@misha.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Mar 1999, Mikhail Teterin wrote: > What's the chance the Adaptec-152x controller (aic0) will soon work > with 3.1-STABLE? > > It has pretty horrible performance problems on 2.2.8-STABLE, even when > using DMA: > > [...] > 4.4%Sys 91.9%Intr 3.7%User 0.0%Nice 0.0%Idl 4244 inact 204 pci irq9 > | | | | | | | | | | 5288 cache 105 aic0 irq11 > ==++++++++++++++++++++++++++++++++++++++++++++++ 248 free 104 wdc0 irq14 > [...] > > (which may, of course, be due to the poor design of the board) and > we were wondering if upgrading to 3.1-STABLE will help us in the > foreseeable future? > I am working on a driver for the 152x and other cards based on the aic6360/6260 chip, and actually making some progress. As to performance I would expect it to be pretty horrible even if I were to get DMA working. The problem is that the aic6360 chip is pretty primative, requireing the CPU to manage much of the SCSI bus signaling. I would not use this type of card for disk if I could avoid it, and probably not for tape either, I have a scanner I plan to use with it. Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 13:11:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7FA4A14E0E for ; Wed, 3 Mar 1999 13:11:24 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id WAA87731 for current@freebsd.org; Wed, 3 Mar 1999 22:11:06 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903032111.WAA87731@freebsd.dk> Subject: UPDATE: ATA/ATAPI driver new version available. To: current@freebsd.org Date: Wed, 3 Mar 1999 22:11:06 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First update to the new ATA/ATAPI driver: Added driver to support ATAPI floppies ie LS-120 & ZIP drives. I'm not too sure of this 2 hour job, I cannot get writeprotect disabled on the only ZIP medium I just got, but I can read the disk. Reports are welcome on LS-120 drives too, they are very hard to come by here, apparently rare items. Added "options ATA_STATIC_ID" that wires ATA disks like the old wd driver. That should shut up the complainers for now :) Fixed problems: Dont use more sectors/intr than the drive supports. This hanged a couble of systems with older disks. Fix announce of > 8.4G disks. More or less cosmetics, but it was forgotten. Dont call ad_interrupt/ad_transfer when no disks config'd. If only ATAPI devices config'd the kernel can now link. Use the right page# for CDR write mode params. This prevented the burner support from working, its now as functional as under the old system. Implement DEVFS stuff. Well.... Fixed breakage when no PCI support in kernel. It was not possible to make a kernel with ata but no PCI. There has also been a lot of general code clenaups, it should be more readable now. As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. But please tell me how it works for you! Enjoy! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 13:12:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 98136156EC for ; Wed, 3 Mar 1999 13:12:16 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40347>; Thu, 4 Mar 1999 08:00:25 +1100 Date: Thu, 4 Mar 1999 08:11:49 +1100 From: Peter Jeremy Subject: Re: Printing is vvveeerrryyy slow To: leifn@neland.dk Cc: current@FreeBSD.ORG Message-Id: <99Mar4.080025est.40347@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland wrote: >Is there a way to test if interrupts are getting serviced? A counter of >interrupts? vmstat -i Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 13:13:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id C595715703 for ; Wed, 3 Mar 1999 13:12:44 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.1/8.9.1) id QAA19717 for current@freebsd.org; Wed, 3 Mar 1999 16:12:27 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <199903032112.QAA19717@misha.cisco.com> Subject: Re: aic0 and CAM In-Reply-To: from Brian Beattie at "Mar 3, 1999 12:58:13 pm" To: current@freebsd.org Date: Wed, 3 Mar 1999 16:12:27 -0500 (EST) Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It has pretty horrible performance problems on 2.2.8-STABLE, even when > > using DMA: > > [...] > > 4.4%Sys 91.9%Intr 3.7%User 0.0%Nice 0.0%Idl 4244 inact 204 pci irq9 > > | | | | | | | | | | 5288 cache 105 aic0 irq11 > > ==++++++++++++++++++++++++++++++++++++++++++++++ 248 free 104 wdc0 irq14 > > [...] > I would not use this type of card for disk if I could avoid it, and > probably not for tape either, I have a scanner I plan to use with it. Yes, tape is the only target on this bus here... From reading the 2.2.8's driver's source I see the DMA is not "yet supported", although the card supports it and lets me choose the drq. Still, the amount of CPU it takes to process an interrupt (CyrixInstead 8x86 at over 200MHz) does not look right.... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 13:26:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id 6F74714FB4 for ; Wed, 3 Mar 1999 13:26:13 -0800 (PST) (envelope-from nsouch@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id WAA04609; Wed, 3 Mar 1999 22:25:41 +0100 (MET) Received: (from nsouch@localhost) by teaser.fr (8.9.2/8.9.1) id VAA01105; Wed, 3 Mar 1999 21:50:34 +0100 (CET) (envelope-from nsouch) Message-ID: <19990303215033.47794@breizh.teaser.fr> Date: Wed, 3 Mar 1999 21:50:33 +0100 From: Nicolas Souchu To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: current@FreeBSD.ORG Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. References: <199903012121.WAA82163@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.81e In-Reply-To: =?iso-8859-1?Q?=3C199903012121=2EWAA82163=40freebsd=2Edk=3E=3B_from_S=F8?= =?iso-8859-1?Q?ren_Schmidt_on_Mon=2C_Mar_01=2C_1999_at_10=3A21=3A05PM_+0?= =?iso-8859-1?Q?100?= X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 01, 1999 at 10:21:05PM +0100, Søren Schmidt wrote: > > >Finally!! > >The much roumored replacement for our current IDE/ATA/ATAPI is >materialising in the CVS repositories around the globe. > >So what does this bring us: > >A new reengineered ATA/ATAPI subsystem, that tries to overcome >most of the deficiencies with the current drivers. > >It supports PCI as well as ISA devices without all the hackery >in ide_pci.c to make PCI devices look like ISA counterparts. What would you think of parallel port devices? Would it be easy to make the new ATAPI stuff work with ppbus? I especially think about the HP7200 CD-RW which has certainly hard real-time constraints to burn a CD. > >It doesn't have the excessive wait problem on probe, in fact you >shouldn't notice any delay when your devices are getting probed. > >Probing and attaching of devices are postponed until interrupts >are enabled (well almost, not finished yet for disks), making >things alot cleaner. Really good work. I'll give it a try this week-end. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Mar 3 13:26:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id 41A031502E for ; Wed, 3 Mar 1999 13:26:29 -0800 (PST) (envelope-from nsouch@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id WAA12882; Wed, 3 Mar 1999 22:25:53 +0100 (MET) Received: (from nsouch@localhost) by teaser.fr (8.9.2/8.9.1) id WAA01143; Wed, 3 Mar 1999 22:14:22 +0100 (CET) (envelope-from nsouch) Message-ID: <19990303221422.04546@breizh.teaser.fr> Date: Wed, 3 Mar 1999 22:14:22 +0100 From: Nicolas Souchu To: Thomas Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: Printing is vvveeerrryyy slow References: <199903030732.XAA65447@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199903030732.XAA65447@ix.netcom.com>; from Thomas Dean on Tue, Mar 02, 1999 at 11:32:51PM -0800 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 02, 1999 at 11:32:51PM -0800, Thomas Dean wrote: > >I am running smp, 4.0-current, as of Mon Feb 15 03:34:29 PST 1999. > >Printing is very slow. I have a HP LaserJet III attached to lpt0. >Printing in the pcl, text, mode is slower than I expect. Printing in >the postscipt mode is extremely slow. A 30K postscript file has been >OVER 5 minutes and is not finished! > >>From dmesg: >.... >Probing for devices on the ISA bus: >sc0 on isa >sc0: VGA color <16 virtual consoles, flags=0x0> >atkbdc0 at 0x60-0x6f on motherboard >atkbd0 irq 1 on isa >psm0 irq 12 on isa >psm0: model Generic PS/2 mouse, device ID 0 >sio0 at 0x3f8-0x3ff irq 4 on isa >sio0: type 16550A >sio1 at 0x2f8-0x2ff irq 3 on isa >sio1: type 16550A >ppc0 at 0x378 irq 7 on isa >ppc0: PC87334 chipset (PS2/NIBBLE) in COMPATIBLE mode >lpt0: on ppbus 0 >lpt0: Interrupt-driven port >fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa >.... Another clue: The National Semiconductors are tricky to configure and your parallel port chipset is one of them (moreover a recent one). Compare the boot detection (PS2/NIBBLE) with your BIOS settings. Try to change your BIOS settings and dump me your dmesg (with verbose output). You may also try to force the operating mode with ppc boot flags. See ppc(4) for more info about this. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Mar 3 13:32:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa15-54.ix.netcom.com [207.93.148.54]) by hub.freebsd.org (Postfix) with ESMTP id 3C571150AC for ; Wed, 3 Mar 1999 13:32:11 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id NAA00386; Wed, 3 Mar 1999 13:31:22 -0800 (PST) (envelope-from tomdean) Date: Wed, 3 Mar 1999 13:31:22 -0800 (PST) Message-Id: <199903032131.NAA00386@ix.netcom.com> From: Thomas Dean To: chuckr@mat.net Cc: geoffr@is.co.za, bright@cygnus.rush.net, current@FreeBSD.ORG In-reply-to: (message from Chuck Robey on Wed, 3 Mar 1999 12:58:41 -0500 (EST)) Subject: Re: Printing is vvveeerrryyy slow Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just to be clear, when I said the values from dmesg and config covered everything, I mean all the physical and/or BIOS devices are included in the list. There are TWO cards plugged into the MB, other than the CPU's. These are de0 and the vga. The on-mother-board devices are all in dmesg. There are no irq's in BIOS, other than some of those in dmesg, parallel, serial, and, PS/2. There are no other devices. tomdean === all of dmesg ================================================ Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #4: Mon Feb 15 03:34:29 PST 1999 tomdean@celebris:/usr/src/sys/compile/CELEBRIS-SMP Timecounter-tdd "i8254" frequency 1193026 Hz cost 2540 ns CPU: Pentium/P54C (586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x3bf real memory = 100663296 (98304K bytes) avail memory = 95055872 (92828K bytes) Programming 16 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xf02b0000. Probing for devices on PCI bus 0: chip0: \ rev 0x11 on pci0.0.0 ncr0: rev 0x02 int a irq 11 on pci0.1.0 chip1: rev 0x88 on pci0.2.0 vga0: rev 0x01 int a irq 9 on pci0.6.0 de0: rev 0x11 int a irq 10 on pci0.8.0 de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 de0: address 00:00:f8:02:76:db Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A ppc0 at 0x378 irq 7 on isa ppc0: PC87334 chipset (PS2/NIBBLE) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 de0 XXX: driver didn't set ifq_maxlen lo0 XXX: driver didn't set ifq_maxlen Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.0MB/s transfers (10.0MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C) da2 at ncr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled da2: 1029MB (2109376 512 byte sectors: 255H 63S/T 131C) da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled da1: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C) changing root device to da1s1a cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present (da1:ncr0:0:1:0): tagged openings now 8 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 13:39:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3B7CC14F6F for ; Wed, 3 Mar 1999 13:39:37 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id WAA87802; Wed, 3 Mar 1999 22:39:01 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903032139.WAA87802@freebsd.dk> Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-Reply-To: <19990303215033.47794@breizh.teaser.fr> from Nicolas Souchu at "Mar 3, 1999 9:50:33 pm" To: nsouch@teaser.fr (Nicolas Souchu) Date: Wed, 3 Mar 1999 22:39:01 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Nicolas Souchu wrote: > > What would you think of parallel port devices? Would it be easy > to make the new ATAPI stuff work with ppbus? I especially think > about the HP7200 CD-RW which has certainly hard real-time constraints > to burn a CD. Hmm, you have any docs on how to talk to such a beast ?? Does it use the "tailgate" protocol I've seen references to ?? It should be possible to make the system support multiple HW interface backends, although it will have some major impact on the current code, I think it could be worth it if there is a standard to follow. > >It doesn't have the excessive wait problem on probe, in fact you > >shouldn't notice any delay when your devices are getting probed. > > > >Probing and attaching of devices are postponed until interrupts > >are enabled (well almost, not finished yet for disks), making > >things alot cleaner. > > Really good work. I'll give it a try this week-end. Thanks, and let me now how it works out.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 14: 6:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from holly.dyndns.org (ip108.houston13.tx.pub-ip.psi.net [38.27.213.108]) by hub.freebsd.org (Postfix) with ESMTP id D260415652 for ; Wed, 3 Mar 1999 14:05:34 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id QAA00738 for freebsd-current@freebsd.org; Wed, 3 Mar 1999 16:06:22 -0600 (CST) (envelope-from chris) Date: Wed, 3 Mar 1999 16:06:19 -0600 From: Chris Costello To: freebsd-current@freebsd.org Subject: ata1: unwanted interrupt Message-ID: <19990303160619.A705@holly.dyndns.org> Reply-To: chris@calldei.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3us Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After having CVSupped to the latest 4.0-CURRENT tree (just now), I noticed the amazing speed of the new ATA driver. BUT I noticed something in dmesg... ata1: unwanted interrupt ad0: ATA-3 disk at ata0 as master ad0: 3090MB (6330240 sectors), 6280 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue acd0: CDROM drive at ata1 as master acd0: drive speed 2062KB/sec, 240KB cache acd0: supported read types: CD-R, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked What exactly is 'unwanted interrupt' supposed to mean, and is it likely to be a problem in my kernel configuration? (I can send a copy of it on request...) Thanks! Chris -- Powered by FreeBSD 4.0-CURRENT. "The Power to Serve!" int main(int m){main(!main(0));} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 14:22: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 27A4014EC5 for ; Wed, 3 Mar 1999 14:20:43 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id OAA32833; Wed, 3 Mar 1999 14:15:51 -0800 (PST) From: Archie Cobbs Message-Id: <199903032215.OAA32833@bubba.whistle.com> Subject: Re: Request for review: changes to if_vlan.c In-Reply-To: from Matthew Jacob at "Mar 3, 99 12:16:20 pm" To: mjacob@feral.com Date: Wed, 3 Mar 1999 14:15:51 -0800 (PST) Cc: jdp@polstra.com, phk@critter.freebsd.dk, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob writes: > > Amen, brother! Get it said! People who claim that strings are > > "too slow" would benefit greatly from spending a few days with the > > profiler. > > Now I'll stir the other pot and say that performance isn't the issue- the > issue is that there's nothing that says that strings and identifiers are > always easier to use and/or understand than numbers. OK. I say that strings and identifiers are (virtually) always easier to use and/or understand than numbers. And I'm something. :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 14:25:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 3222514DD2 for ; Wed, 3 Mar 1999 14:24:22 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10IK3M-000J5s-00; Thu, 4 Mar 1999 00:23:44 +0200 From: Sheldon Hearn To: chris@calldei.com Cc: freebsd-current@freebsd.org Subject: Re: ata1: unwanted interrupt In-reply-to: Your message of "Wed, 03 Mar 1999 16:06:19 CST." <19990303160619.A705@holly.dyndns.org> Date: Thu, 04 Mar 1999 00:23:44 +0200 Message-ID: <73399.920499824@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 03 Mar 1999 16:06:19 CST, Chris Costello wrote: > After having CVSupped to the latest 4.0-CURRENT tree > (just now), I noticed the amazing speed of the new ATA driver. The amazing speed of the new ATA driver? Were you using 32 bit transfers and multi-sector IO with the older driver? I assumed from the benchmarks posted that I had no reason to feel alarmed about the fact that the new driver offered no tangible performance increase. My understanding was that we'd "feel it" when DMA transfers were enabled for those drives that support them. Am I confused (yet again)? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 14:29:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from holly.dyndns.org (ip108.houston13.tx.pub-ip.psi.net [38.27.213.108]) by hub.freebsd.org (Postfix) with ESMTP id E585E14E95 for ; Wed, 3 Mar 1999 14:29:38 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id QAA00953; Wed, 3 Mar 1999 16:30:16 -0600 (CST) (envelope-from chris) Date: Wed, 3 Mar 1999 16:30:15 -0600 From: Chris Costello To: Sheldon Hearn Cc: freebsd-current@freebsd.org Subject: Re: ata1: unwanted interrupt Message-ID: <19990303163015.A930@holly.dyndns.org> Reply-To: chris@calldei.com References: <19990303160619.A705@holly.dyndns.org> <73399.920499824@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3us In-Reply-To: <73399.920499824@axl.noc.iafrica.com>; from Sheldon Hearn on Thu, Mar 04, 1999 at 12:23:44AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 3, 1999, Sheldon Hearn put this into my mailbox: > > > On Wed, 03 Mar 1999 16:06:19 CST, Chris Costello wrote: > > > After having CVSupped to the latest 4.0-CURRENT tree > > (just now), I noticed the amazing speed of the new ATA driver. > > The amazing speed of the new ATA driver? Were you using 32 bit transfers > and multi-sector IO with the older driver? > > I assumed from the benchmarks posted that I had no reason to feel > alarmed about the fact that the new driver offered no tangible > performance increase. > > My understanding was that we'd "feel it" when DMA transfers were enabled > for those drives that support them. > > Am I confused (yet again)? Yes ;-) I mean the time it takes to actually detect the drive. I haven't really tested out the driver for actual seek/read/write speed yet (but it might be a fun thing to try out one of these days). > > Ciao, > Sheldon. > -Chris -- Powered by FreeBSD 4.0-CURRENT. "The Power to Serve!" int main(int m){main(!main(0));} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 14:34:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 6E3CB14C21 for ; Wed, 3 Mar 1999 14:34:24 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id HAA01869; Thu, 4 Mar 1999 07:34:01 +0900 (JST) Message-ID: <36DDA9D8.C3A1EA65@newsguy.com> Date: Thu, 04 Mar 1999 06:30:00 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Geoff Rehmet Cc: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: Printing is vvveeerrryyy slow References: <19990303110250.12459.qmail@rucus.ru.ac.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Geoff Rehmet wrote: > > Alfred Perlstein writes : > > > Printing is very slow. I have a HP LaserJet III attached to lpt0. > > > Printing in the pcl, text, mode is slower than I expect. Printing in > > > the postscipt mode is extremely slow. A 30K postscript file has been > > > OVER 5 minutes and is not finished! > > > > have you tried: > > lptcontrol -p > > > > I remeber the friendlies on #freebsd suggesting this > > to me when i had similar symptoms last year. > It's a long long time since I was working on the lpt driver. This > kind of symptom was a common problem during its development. I > haveen't been able to really appreciate the code for the nltp > driver, so I also can't really see if there is a problem. > Biggest problem when I was hacking on the lpt driver was that > interrupts tended to get lost sometimes. I seem to recall, that > there were some problems with slow printing that just could not > be fixed. > Going into polled mode (lptcotnrol -p) is probably your best bet > at the moment. I suspect changing the interrupt mask might also have an impact. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 14:34:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id CB0B415619 for ; Wed, 3 Mar 1999 14:34:48 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id HAA01938; Thu, 4 Mar 1999 07:34:41 +0900 (JST) Message-ID: <36DDB40D.BC694111@newsguy.com> Date: Thu, 04 Mar 1999 07:13:33 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: David Wolfskill Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? References: <199903031826.KAA98780@pau-amma.whistle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Wolfskill wrote: > > >Irrespective of all the valid reasons to allow for wiring (but not > >mandate), static drive numbering is not BIOS compatible (thus, not > >DOS compatible). This violates POLA. > > I'm at least as much against POLA violations as anyone... but the real > POLA violation I see is the apparent dependence on the BIOS, since it is > "controlled" by a process external to the UNIX environment. It is not a matter of dependence (which, obviously, does not exist). Is a matter of: 1) Doing the same as "everyone else" (meaning, here, the most common background for newbies; if one is not a newbie, POLA doesn't comes into play for this particular issue). 2) Having the OS see disks in the same way/ordering as the program that boot it does, *unless explicitly instructed otherwise*. > "DOS compatability" is not one of my concerns; I have difficulty imagining > a universe in which it would become one. Indeed, if someone were to > claim "DOS compatibility" for something, I would have no way of knowing > what that was supposed to imply, since I'm nearly completely unfamiliar > with DOS. (The few times I've tried to use it, I would get different > results from the same actions on my part, so I gave up.) :-) > And yes, I realize that neither my experiences nor perspective may be > representative of anyone else. Which, unfortunately, plays a part in POLA. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 14:35: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 26C7915610; Wed, 3 Mar 1999 14:34:57 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id HAA01958; Thu, 4 Mar 1999 07:34:48 +0900 (JST) Message-ID: <36DDB780.80BBEF99@newsguy.com> Date: Thu, 04 Mar 1999 07:28:16 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: mi@aldan.algebra.com Cc: current@FreeBSD.ORG, nate@FreeBSD.ORG, gconnor@cisco.com Subject: Re: aic0 and CAM References: <199903031950.OAA19405@misha.cisco.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > > What's the chance the Adaptec-152x controller (aic0) will soon work > with 3.1-STABLE? I just wish it was soon. I *so* wanted to be able to access external hd on my notebook and keep a local CVS tree (not to mention install X)... > It has pretty horrible performance problems on 2.2.8-STABLE, even when > using DMA: That, I think, is unlikely to change. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 14:35: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 246481562B for ; Wed, 3 Mar 1999 14:34:59 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id HAA01876; Thu, 4 Mar 1999 07:34:04 +0900 (JST) Message-ID: <36DDAA99.E79CCC4E@newsguy.com> Date: Thu, 04 Mar 1999 06:33:13 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Thomas Dean Cc: chuckr@mat.net, geoffr@is.co.za, bright@cygnus.rush.net, current@FreeBSD.ORG Subject: Re: Printing is vvveeerrryyy slow References: <199903031542.HAA00622@ix.netcom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Dean wrote: > > My machine is a DEC Celebris 5133DP. The only device added since > purchase was de0. Regardless of the devices configured in the kernel, does the *computer* have other *physical* devices, such as sound cards (builtin or not)? Also, I seem recall discussions suggesting that using different interrupt masks make a difference, in some cases. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 14:36: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 2CA7A15664 for ; Wed, 3 Mar 1999 14:35:22 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id HAA01864; Thu, 4 Mar 1999 07:33:58 +0900 (JST) Message-ID: <36DDA984.39F336B4@newsguy.com> Date: Thu, 04 Mar 1999 06:28:36 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Leif Neland , freebsd-current@freebsd.org Subject: Re: Printing is vvveeerrryyy slow References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland wrote: > > Is it printer, cable, port, or freebsd-config, which is to blame? I don't > know how to proceed either... BIOS settings? Have you tried changing BIOS settings such as EPP? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 14:36:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id 8F7C1156F6 for ; Wed, 3 Mar 1999 14:36:22 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.3/8.9.1) with ESMTP id BAA01221; Thu, 4 Mar 1999 01:34:09 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Thu, 4 Mar 1999 01:34:09 +0300 (MSK) From: oZZ!!! To: chris@calldei.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: ata1: unwanted interrupt In-Reply-To: <19990303160619.A705@holly.dyndns.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 Wed, 3 Mar 1999, Chris Costello wrote: > After having CVSupped to the latest 4.0-CURRENT tree > (just now), I noticed the amazing speed of the new ATA driver. > > BUT > > I noticed something in dmesg... > > ata1: unwanted interrupt > ad0: ATA-3 disk at ata0 as master > ad0: 3090MB (6330240 sectors), 6280 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 0 depth queue > acd0: CDROM drive at ata1 as master > acd0: drive speed 2062KB/sec, 240KB cache > acd0: supported read types: CD-R, CD-DA > acd0: Audio: play, 255 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: CD-ROM 120mm data disc loaded, unlocked > > What exactly is 'unwanted interrupt' supposed to mean, and is it > likely to be a problem in my kernel configuration? (I can send a copy > of it on request...) i think it tell you about not used 2nd IDE controller... > > Thanks! > Chris > > -- > Powered by FreeBSD 4.0-CURRENT. "The Power to Serve!" > > int main(int m){main(!main(0));} > Rgdz, Sergey A. Osokin aka 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 Wed Mar 3 14:39:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id 6AB681566F for ; Wed, 3 Mar 1999 14:36:22 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.3/8.9.1) with ESMTP id BAA01219; Thu, 4 Mar 1999 01:32:41 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Thu, 4 Mar 1999 01:32:41 +0300 (MSK) From: oZZ!!! To: =?KOI8-R?Q?S=F8ren_Schmidt?= Cc: current@FreeBSD.ORG Subject: Re: UPDATE: ATA/ATAPI driver new version available. In-Reply-To: <199903032111.WAA87731@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 > First update to the new ATA/ATAPI driver: > > Added driver to support ATAPI floppies ie LS-120 & ZIP drives. > I'm not too sure of this 2 hour job, I cannot get writeprotect > disabled on the only ZIP medium I just got, but I can read the > disk. Reports are welcome on LS-120 drives too, they are very > hard to come by here, apparently rare items. > > Added "options ATA_STATIC_ID" that wires ATA disks like the old wd driver. > That should shut up the complainers for now :) > > Fixed problems: > > Dont use more sectors/intr than the drive supports. > This hanged a couble of systems with older disks. > > Fix announce of > 8.4G disks. > More or less cosmetics, but it was forgotten. > > Dont call ad_interrupt/ad_transfer when no disks config'd. > If only ATAPI devices config'd the kernel can now link. > > Use the right page# for CDR write mode params. > This prevented the burner support from working, its now > as functional as under the old system. > > Implement DEVFS stuff. > Well.... > > Fixed breakage when no PCI support in kernel. > It was not possible to make a kernel with ata but no PCI. > ......... ata-pci0: rev 0x01 on pci0.7.1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ......... ata1: unwanted interrupt ......... ad0: ATA-3 disk at ata0 as master ad0: 2503MB (5126964 sectors), 5086 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue ad1: ATA-? disk at ata0 as slave ad1: 1277MB (2616240 sectors), 2595 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue acd0: CDROM drive at ata1 as slave acd0: drive speed 0KB/secacd0: supported read types: ^^^^^ ???? acd0: Mechanism: caddy acd0: Medium: CD-ROM unknown medium ........ hmmm Does it right? Rgdz, Sergey A. Osokin aka 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 Wed Mar 3 14:48:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-16.ppp.wenet.net [206.15.85.16]) by hub.freebsd.org (Postfix) with ESMTP id A42731575E; Wed, 3 Mar 1999 14:47:56 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.2/8.9.1) with ESMTP id OAA01656; Wed, 3 Mar 1999 14:47:02 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Wed, 3 Mar 1999 14:47:02 -0800 (PST) From: Alex Zepeda To: Geoff Rehmet Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: ATA driver In-Reply-To: <199903020906.LAA00297@hangdog.is.co.za> 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, 2 Mar 1999, Geoff Rehmet wrote: > Just some results of testing the comparison of wd and ata: > > Both bonnie tests were run on a freshly booted machine, P133, > 64M RAM, running X and netscape, but only Bonnie active: Odd. My (crapy?) WD drive is much faster with DMA (not UDMA AFAIK), so the ATA driver is a loss according to bonnie. I tried a bunch of different settings for the wd driver, and here's the result for posterity (do with it what you will): -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU WD+SU+ND 256 6234 32.8 7294 11.6 3263 5.7 6048 27.8 7730 6.9 126.6 2.4 WD+SU+AL 256 11405 49.1 11036 16.6 3678 7.3 11284 51.4 11434 13.3 123.6 1.7 WD+SU+AL 256 11150 48.1 11026 16.9 3735 7.4 11295 51.3 11428 13.1 140.1 1.8 WD+SU+DM 256 11420 48.7 10965 16.5 3729 7.4 11349 51.4 11379 13.1 140.3 1.8 WD+SU+32 256 5073 22.5 5580 9.2 2657 5.2 4879 23.6 5985 5.4 128.8 1.5 WD+SU+MB 256 3739 24.6 4047 7.7 1950 3.9 3817 17.5 4354 5.0 118.2 3.4 WD+SU 256 3288 14.8 3478 6.1 1744 3.1 3312 15.8 3752 3.8 120.9 1.1 ATA 256 6313 33.8 7407 12.5 2557 4.8 6124 26.9 7874 6.0 128.6 2.4 ATA = ata driver, soft updates WD+SU = wd driver, soft updates WD+SU+ND= wd driver, soft updates, 32 bit, multiblock-16 WD+SU+AL= wd driver, soft updates, dma, 32 bit, multiblock-16 (after shutting down X, then after a fresh reboot) WD+SU+DM= wd driver, soft updates, dma WD+SU+32= wd driver, soft updates, 32 bit WD+SU+MB= wd driver, soft updates, multiblock-16 And the dmesg output (It's a PII not a Celeron or Xeon): Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Wed Mar 3 01:33:41 PST 1999 root@zippy.dyn.ml.org:/usr/src/sys/compile/ATA Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (448.97-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff real memory = 134217728 (131072K bytes) avail memory = 127893504 (124896K bytes) Preloaded elf kernel "kenrel.z" at 0xf02ab000. Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ata-pci0: rev 0x01 on pci0.7.1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 intpm0: rev 0x02 on pci0.7.3 intpm0: I/O mapped 7000 ALLOCED IRQ 0 intr IRQ 9 enabled revision 0 intsmb0: smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 8000 Probing for devices on PCI bus 1: vga0: rev 0x04 int a irq 9 on pci1.0.0 Probing for PnP devices: CSN 1 Vendor ID: CTL00e4 [0xe4008c0e] Serial 0x1cbc4202 Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp sn 0x1cbc4202) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa CSN 2 Vendor ID: CRD0001 [0x0100440e] Serial 0x00416288 Comp ID: @@@0000 [0x00000000] Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard ppc0 at 0x378 irq 7 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 lppps0: on ppbus 0 atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model MouseMan+, device ID 0 pcm0 not probed due to drq conflict with pcm1 at 1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in apm0 on isa apm: found APM BIOS version 1.2 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface ata1: unwanted interrupt ad0: ATA-4 disk at ata0 as master ad0: 12416MB (25429824 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue acd0: CDROM drive at ata1 as master acd0: drive speed 2928 - 6890KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked atapi: floppy device at ata1 as slave - NO DRIVER! changing root device to ad0s2a ffs_mountfs: superblock updated for soft updates - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 14:49:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from holly.dyndns.org (ip108.houston13.tx.pub-ip.psi.net [38.27.213.108]) by hub.freebsd.org (Postfix) with ESMTP id 401A514F9D for ; Wed, 3 Mar 1999 14:49:20 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id QAA01019; Wed, 3 Mar 1999 16:42:13 -0600 (CST) (envelope-from chris) Date: Wed, 3 Mar 1999 16:42:12 -0600 From: Chris Costello To: oZZ!!! Cc: chris@calldei.com, freebsd-current@FreeBSD.ORG Subject: Re: ata1: unwanted interrupt Message-ID: <19990303164212.B930@holly.dyndns.org> Reply-To: chris@calldei.com References: <19990303160619.A705@holly.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3us In-Reply-To: ; from oZZ!!! on Thu, Mar 04, 1999 at 01:34:09AM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 3, 1999, oZZ!!! put this into my mailbox: > i think it tell you about not used 2nd IDE controller... Nope, my CD ROM is on the second IDE controller ... -Chris -- Powered by FreeBSD 4.0-CURRENT. "The Power to Serve!" int main(int m){main(!main(0));} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 14:58:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-16.ppp.wenet.net [206.15.85.16]) by hub.freebsd.org (Postfix) with ESMTP id F1FFD15794 for ; Wed, 3 Mar 1999 14:58:29 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.2/8.9.1) with ESMTP id OAA01724; Wed, 3 Mar 1999 14:57:50 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Wed, 3 Mar 1999 14:57:50 -0800 (PST) From: Alex Zepeda To: oZZ!!! Cc: chris@calldei.com, freebsd-current@FreeBSD.ORG Subject: Re: ata1: unwanted interrupt In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 4 Mar 1999, oZZ!!! wrote: > > What exactly is 'unwanted interrupt' supposed to mean, and is it > > likely to be a problem in my kernel configuration? (I can send a copy > > of it on request...) > i think it tell you about not used 2nd IDE controller... Nope. I've got three IDE/ATAPI devices, primary master, secondary master+slave, and I still get it. I've got a PIIX4 controller. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 15:10: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id B2B7B157B6; Wed, 3 Mar 1999 15:10:01 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id IAA03774; Thu, 4 Mar 1999 08:09:47 +0900 (JST) Message-ID: <36DDBE51.CF8FAB28@newsguy.com> Date: Thu, 04 Mar 1999 07:57:21 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: mi@aldan.algebra.com, current@FreeBSD.ORG, nate@FreeBSD.ORG, gconnor@cisco.com Subject: Re: aic0 and CAM References: <199903032050.NAA86828@panzer.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kenneth D. Merry" wrote: > > I think the chances are very slim that it will work soon with 3.x or 4.x. > It may get done at some point, but I don't think anyone is actively working > on it at the moment. Someone is reportedly "working" on it. Whether that is "actively" or not, I don't know... :-( > If you need a supported ISA controller, the Adaptec 154x controllers are > supported, as are the Advansys ISA controllers. Both support DMA, and should > give you much better performance. I'd be happy with a supported PCMCIA controller... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 15:10:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from dfw-ix14.ix.netcom.com (dfw-ix14.ix.netcom.com [206.214.98.14]) by hub.freebsd.org (Postfix) with ESMTP id EC98D157D4 for ; Wed, 3 Mar 1999 15:10:24 -0800 (PST) (envelope-from asami@silvia.hip.berkeley.edu) Received: (from smap@localhost) by dfw-ix14.ix.netcom.com (8.8.4/8.8.4) id RAA02419; Wed, 3 Mar 1999 17:01:27 -0600 (CST) Received: from sji-ca7-236.ix.netcom.com(209.109.235.236) by dfw-ix14.ix.netcom.com via smap (V1.3) id rma002200; Wed Mar 3 17:00:11 1999 Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id OAA61888; Wed, 3 Mar 1999 14:59:49 -0800 (PST) Date: Wed, 3 Mar 1999 14:59:49 -0800 (PST) Message-Id: <199903032259.OAA61888@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@silvia.hip.berkeley.edu using -f To: robert+freebsd@cyrus.watson.org Cc: sos@freebsd.dk, doconnor@gsoft.com.au, current@FreeBSD.ORG, geoffr@is.co.za In-reply-to: (message from Robert Watson on Wed, 3 Mar 1999 10:04:59 -0500 (EST)) Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. From: asami@FreeBSD.ORG (Satoshi Asami) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Robert Watson * away logged in via the network performing this recovery. Having the * drives automatically renumber themselves on the complete failure of one * drive (and it was fairly complete) would have been a disaster. This is Or just think "ccd". There are people building disk servers out of IDE drives these days, and having the ccd configured in a wrong order could be disastrous. I have been running a SCSI server systems for a couple of years now and would have lost several 100GB volumes by now if the devices weren't wired down. (Sometimes the drives just won't show up at boot -- a power cycle usually cures that.) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 15:14:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 3E2FC15711 for ; Wed, 3 Mar 1999 15:14:51 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id IAA03763; Thu, 4 Mar 1999 08:09:42 +0900 (JST) Message-ID: <36DDBB67.851B5D43@newsguy.com> Date: Thu, 04 Mar 1999 07:44:55 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: mjacob@feral.com Cc: John Polstra , phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: Request for review: changes to if_vlan.c References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > > > > Amen, brother! Get it said! People who claim that strings are > > "too slow" would benefit greatly from spending a few days with the > > profiler. > > Now I'll stir the other pot and say that performance isn't the issue- the > issue is that there's nothing that says that strings and identifiers are > always easier to use and/or understand than numbers. Well, maybe. I'll like to propose the following test. It doesn't really prove anything, and even statistical results would be pretty much meaningless in direct answer to your question (ie, it would not show that strings and identifiers are always easier to understand, but would show that that is the case for most people). Here is the test. Please identify the action of the following signals. They are listed here first by numbers, then by identifiers. I have taken the liberty to change the ordering of the identifiers, so you can't claim the numbers helped you identifying them. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 SIGIO SIGXCPU SIGXFSZ SIGVTALRM SIGPROF SIGWINCH SIGINFO SIGUSR1 SIGUSR2 SIGHUP SIGINT SIGQUIT SIGILL SIGTRAP SIGABRT SIGALRM SIGTERM SIGURG SIGSTOP SIGTSTP SIGCONT SIGCHLD SIGTTIN SIGTTOU SIGIOT SIGEMT SIGFPE SIGKILL SIGBUS SIGSEGV SIGSYS SIGPIPE Send the results to your conscience. ;-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 15:42:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 7DFAC14D9C for ; Wed, 3 Mar 1999 15:41:23 -0800 (PST) (envelope-from rock@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999020800) with ESMTP id AAA08403 for ; Thu, 4 Mar 1999 00:40:55 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999020800) with ESMTP id AAA04656 for ; Thu, 4 Mar 1999 00:40:55 +0100 (CET) Received: from vodix.aremorika (vodix [134.96.247.43]) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) with ESMTP id AAA28416 for ; Thu, 4 Mar 1999 00:40:54 +0100 (CET) From: "D. Rock" Received: by vodix.aremorika; Thu, 4 Mar 1999 00:40:54 +0100 (MET) Date: Thu, 4 Mar 1999 00:40:54 +0100 (MET) Message-Id: <199903032340.AAA06675@vodix.aremorika> To: freebsd-current@FreeBSD.ORG Subject: Re: ata1: unwanted interrupt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > After having CVSupped to the latest 4.0-CURRENT tree > > (just now), I noticed the amazing speed of the new ATA driver. > > The amazing speed of the new ATA driver? Were you using 32 bit transfers > and multi-sector IO with the older driver? > > I assumed from the benchmarks posted that I had no reason to feel > alarmed about the fact that the new driver offered no tangible > performance increase. > > My understanding was that we'd "feel it" when DMA transfers were enabled > for those drives that support them. I also tried the new ata code and wasn't impressed by the speed: With the old driver I achieved 12 MB/s with almost no CPU load on my ST34321A drive. The new driver works flawless in my configuration (I only have a single IDE drive attached, the rest is SCSI. Chipset is Ali Aladdin), but I only get about 7MB/s from the drive while having 70% irq load. (I have done the tests with dd from the raw device and a block size of 1MB) So I didn't notice any problems with the new code, but we'll have to wait until DMA is supported to get a really decent performance. Just to be complete. Here are the relevant portions of dmesg output for just another working configuration: ata-pci0: rev 0xc1 int a irq 0 on pci0.15.0 ata0 at 0x01f0 irq 14 on ata-pci0 [...] ad0: ATA-4 disk at ata0 as master ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 15:48: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id C66EA14DEA for ; Wed, 3 Mar 1999 15:47:49 -0800 (PST) (envelope-from rock@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999020800) with ESMTP id AAA08413 for ; Thu, 4 Mar 1999 00:47:32 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999020800) with ESMTP id AAA04740 for ; Thu, 4 Mar 1999 00:47:31 +0100 (CET) Received: from vodix.aremorika (vodix [134.96.247.43]) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) with ESMTP id AAA28640 for ; Thu, 4 Mar 1999 00:47:30 +0100 (CET) From: "D. Rock" Received: by vodix.aremorika; Thu, 4 Mar 1999 00:47:30 +0100 (MET) Date: Thu, 4 Mar 1999 00:47:30 +0100 (MET) Message-Id: <199903032347.AAA06682@vodix.aremorika> To: freebsd-current@FreeBSD.ORG Subject: Re: ata1: unwanted interrupt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Am I confused (yet again)? > > Yes ;-) > > I mean the time it takes to actually detect the drive. I recently added options IDE_DELAY=2000 on all IDE kernels I managed. The only problem with this short delay so far was an undetected drive in an unusual configuration: The jumper block was defective and the drive could only be jumpered as slave. A 2s delay was too short to detect this drive without a master drive attached at the same bus. So in my case, there isn't even a speed improvement during boot. But I will soon test the new code on my laptop: The drive has problem if DMA is enabled. I hope the new code will give me some speed improvement in this case. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 16: 4:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from coleridge.kublai.com (coleridge.kublai.com [207.96.1.116]) by hub.freebsd.org (Postfix) with ESMTP id 631C914FB6 for ; Wed, 3 Mar 1999 16:04:25 -0800 (PST) (envelope-from shmit@coleridge.kublai.com) Received: (from shmit@localhost) by coleridge.kublai.com (8.9.2/8.9.1) id SAA02590; Wed, 3 Mar 1999 18:58:32 -0500 (EST) Date: Wed, 3 Mar 1999 18:58:32 -0500 From: Brian Cully To: Matthew Jacob Cc: John Polstra , phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: Request for review: changes to if_vlan.c Message-ID: <19990303185832.A193@kublai.com> Reply-To: shmit@kublai.com References: <199903031957.LAA78943@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1us In-Reply-To: ; from Matthew Jacob on Wed, Mar 03, 1999 at 12:16:20PM -0800 X-Sender: If your mailer pays attention to this, it's broken. X-PGP-Info: finger shmit@kublai.com for my public key. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 03, 1999 at 12:16:20PM -0800, Matthew Jacob wrote: > Now I'll stir the other pot and say that performance isn't the issue- the > issue is that there's nothing that says that strings and identifiers are > always easier to use and/or understand than numbers. From `The Elements of Programming Style' Second Edition, by Kernighan and Plauger: The other, more general, failing is the use of numeric codes (floating point at that) to name the metals. (Was floating point used because all the metals had names that were ``floating point'' variables in Fortran? What if we added LEAD, NICKEL, and IRON?) The point should be clear, using proper string identifiers would make your program easier to understand and modify, as well as allow for greater extensibility. Of course, you can pick bad strings, too, but you still wouldn't lose of numbers. -bjc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 16:24:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1E5DC150CB for ; Wed, 3 Mar 1999 16:24:14 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id QAA26609; Wed, 3 Mar 1999 16:23:20 -0800 Date: Wed, 3 Mar 1999 16:23:20 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Brian Cully Cc: John Polstra , phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: Request for review: changes to if_vlan.c In-Reply-To: <19990303185832.A193@kublai.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 I was not responding to this for a while because Poul quite correctly thwapped me for not being on point, but I couldn't let this go. > The point should be clear, using proper string identifiers would > make your program easier to understand and modify, as well as > allow for greater extensibility. By this measure, nearly all of the code available to the WindowsNT DDK is "easier to understand and modify" as well as allow[ing] for greater flexibility". My only point here is that both numbers and strings are identifiers, and it is not always obvious but it *is* context (observer context) sensitive as which is, in fact, easier to use or manipulate or remember. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 16:28:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 823DF14DEA for ; Wed, 3 Mar 1999 16:28:44 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA26200; Thu, 4 Mar 1999 10:55:27 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <79192.920464790@axl.noc.iafrica.com> Date: Thu, 04 Mar 1999 10:55:27 +1030 (CST) From: "Daniel O'Connor" To: Sheldon Hearn Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? Cc: sos@freebsd.dk, (freebsd-current@freebsd.org) , Cejka Rudolf Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Mar-99 Sheldon Hearn wrote: > I'm not sure I understand what real-world frustrations people are having > here. Is this thread the product of reactionary criticism, or are there > real examples of situations in which there are serious disadvantages to > the way Soren has things working? I don't think its too terrible to have devices made in probe order, but it would be *nice* to have it if you are fiddling and removing/inserting a device and rebooting (I've done this debugging stuff) and IMHO it would suck having to edit fstab everytime. OK, so its not gonna happen very often, *but* it would be nice to have :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 17:11:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id B5B6315194 for ; Wed, 3 Mar 1999 17:10:44 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id UAA25300 for ; Wed, 3 Mar 1999 20:10:33 -0500 (EST) Date: Wed, 3 Mar 1999 20:10:33 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@freebsd.org Subject: ATA success story 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 Great job, Soren! The ATA drivers work great for me. I see no speed change in transfer rate, and an increase in interrupts, but I expect better performance when DMA has been implemented. Boot time has decreased from about 40 seconds to about 7 seconds as well, something I've long wanted! You seem to have forgotten to update files.i386 and sys/conf/options for atapi-fd and for ATA_STATIC_ID, but that's not too bad, and easily fixed on my side. Guess what, though? afd0: rewriteable drive at ata1 as master afd0: 120MB (246528 sectors), 963 cyls, 8 heads, 32 S/T, 512 B/S And read/write work both flawlessly! Thanks for all your work! Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 17:18: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from psf.Pinyon.ORG (ip-17-114.prc.primenet.com [207.218.17.114]) by hub.freebsd.org (Postfix) with ESMTP id 63A581511D for ; Wed, 3 Mar 1999 17:17:07 -0800 (PST) (envelope-from rcarter@psf.Pinyon.ORG) Received: from psf.Pinyon.ORG (localhost [127.0.0.1]) by psf.Pinyon.ORG (8.9.3/8.9.2) with ESMTP id SAA17500 for ; Wed, 3 Mar 1999 18:13:43 -0700 (MST) (envelope-from rcarter@psf.Pinyon.ORG) Message-Id: <199903040113.SAA17500@psf.Pinyon.ORG> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: SMP and SO5.0 In-reply-to: Your message of "Wed, 17 Feb 1999 14:40:38 EST." <199902171940.OAA69973@y.dyson.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Mar 1999 18:13:43 -0700 From: "Russell L. Carter" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Dyson extemporised: %Julian Elischer said: %> %> %> On Tue, 16 Feb 1999, Luoqi Chen wrote: %> > You may try my patch at http://www.freebsd.org/~luoqi, which would allow %> > linux threads to run on SMP. %> %> I've gone through these patches and I can see that they are really needed %> for SMP where address spaces are shared. %> %I agree -- a per-cpu page directory per multithreaded process is the way that %I had implemented. Excellent!!! % So I tried these out. The examples work in the linuxthreads dir but many other things do not. For instance, Built debug ACE+TAO with egcs-2.91.62, March 2 -current, newest LinuxThreads port. Uniprocessor has no errors. SMP fails, for instance: rcarter@mazatzal:~/ace/ACE_wrappers/tests [82] ./TSS_Test TSS_Test in malloc(): warning: recursive call. TSS_Test in malloc(): warning: recursive call. Abort trap (core dumped) rcarter@mazatzal:~/ace/ACE_wrappers/tests [83] gdb TSS_Test -core TSS_Test.coreGDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... Core was generated by `TSS_Test'. Program terminated with signal 6, Abort trap. Reading symbols from /home/rcarter/ace/ACE_wrappers/ace/libACE.so...done. Reading symbols from /usr/local/lib/liblthread.so.0...done. Reading symbols from /usr/lib/libm.so.2...done. Reading symbols from /usr/lib/libc.so.3...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. #0 0x18243bf4 in sched_yield () (gdb) where #0 0x18243bf4 in sched_yield () #1 0x181eb051 in sched_yield () at sched.c:58 #2 0x181eac79 in _spinlock (lck=0x18281738) at spinlock.c:88 #3 0x18278a02 in free () #4 0x181a8765 in __builtin_delete (ptr=0x8054170) #5 0x804ada5 in worker (c=0x64) at TSS_Test.cpp:222 #6 0x180fc4e2 in ACE_Thread_Adapter::invoke (this=0x8051540) at OS.cpp:2075 #7 0x180fc556 in ace_thread_adapter (args=0x8051540) at OS.cpp:2194 #8 0x181ebe8c in pthread_start_thread (arg=0xeb5ffd04) at manager.c:160 #9 0x181ec49d in _clone () at clone.S:1 #10 0xffffffff in ?? () #11 0x1805ec5c in .curbrk () Cannot access memory at address 0xf9dc. (gdb) Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 18:45:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 84B0815014; Wed, 3 Mar 1999 18:45:00 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA04341; Thu, 4 Mar 1999 13:13:27 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA10797; Thu, 4 Mar 1999 13:13:00 +1030 (CST) Message-ID: <19990304131300.C441@lemis.com> Date: Thu, 4 Mar 1999 13:13:00 +1030 From: Greg Lehey To: Satoshi Asami , robert+freebsd@cyrus.watson.org Cc: sos@freebsd.dk, doconnor@gsoft.com.au, current@FreeBSD.ORG, geoffr@is.co.za Subject: ccd/vinum (was: CALL FOR TESTERS of new ATA/ATAPI driver..) References: <199903032259.OAA61888@silvia.hip.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903032259.OAA61888@silvia.hip.berkeley.edu>; from Satoshi Asami on Wed, Mar 03, 1999 at 02:59:49PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 3 March 1999 at 14:59:49 -0800, Satoshi Asami wrote: > * From: Robert Watson > > * away logged in via the network performing this recovery. Having the > * drives automatically renumber themselves on the complete failure of one > * drive (and it was fairly complete) would have been a disaster. This is > > Or just think "ccd". There are people building disk servers out of > IDE drives these days, and having the ccd configured in a wrong order > could be disastrous. BTW, vinum doesn't have this problem. It has a unique ID for each vinum drive, so you can swap them and it will still configure correctly. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 19:46:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from Vorlon.odc.net (Vorlon.odc.net [207.137.42.6]) by hub.freebsd.org (Postfix) with ESMTP id 7AF5A15083; Wed, 3 Mar 1999 19:45:23 -0800 (PST) (envelope-from nwestfal@Vorlon.odc.net) Received: from localhost (nwestfal@localhost) by Vorlon.odc.net (8.8.7/8.8.7) with ESMTP id TAA30118; Wed, 3 Mar 1999 19:44:31 -0800 Date: Wed, 3 Mar 1999 19:44:31 -0800 (PST) From: Neal Westfall To: "Daniel C. Sobral" Cc: mi@aldan.algebra.com, current@FreeBSD.ORG, nate@FreeBSD.ORG, gconnor@cisco.com Subject: Re: aic0 and CAM In-Reply-To: <36DDB780.80BBEF99@newsguy.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 Not that I have one of these controllers, but I just received my 3.1 cd set in the mail today, and happened to notice that the Adaptec 152x controller is listed on the back as supported, along with the Tekram DC390 (and other AMD 53c974 based boards). I was sure that these were both still unsupported under CAM. If I missed something along the way, I apologize for bringing it up... On Thu, 4 Mar 1999, Daniel C. Sobral wrote: > Mikhail Teterin wrote: > > > > What's the chance the Adaptec-152x controller (aic0) will soon work > > with 3.1-STABLE? > > I just wish it was soon. I *so* wanted to be able to access external > hd on my notebook and keep a local CVS tree (not to mention install > X)... > > > It has pretty horrible performance problems on 2.2.8-STABLE, even when > > using DMA: > > That, I think, is unlikely to change. > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "FreeBSD is Yoda, Linux is Luke Skywalker." > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Neal Westfall mailto:nwestfal@odc.net http://www.odc.net/~nwestfal/ FreeBSD: The Power To Serve! http://www.freebsd.org/ $Id: dot.signature,v 1.2 1998/12/30 08:23:13 nwestfal Exp nwestfal $ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 21:41:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from zone.syracuse.net (zone.syracuse.net [209.2.141.6]) by hub.freebsd.org (Postfix) with ESMTP id 207F914D55 for ; Wed, 3 Mar 1999 21:41:18 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.9.2/8.9.2) with ESMTP id FAA28314 for ; Thu, 4 Mar 1999 05:41:02 GMT (envelope-from green@zone.syracuse.net) Date: Thu, 4 Mar 1999 05:41:02 +0000 (GMT) From: Brian Feldman To: current@freebsd.org Subject: ATA not quite peachy Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After testing out the new ATA drivers, I've only got a single problem. My box locked up while accessing the LS-120 (and, seemingly, swapping): Mar 4 00:20:02 green /kernel: atapi_transfer: bad command phase Mar 4 00:20:33 green /kernel: swap_pager: indefinite wait buffer: device: 0x20019, blkno: 2800, size: 8192 I think what was going on was a second read transfer was trying to occur while one was already going, and something wrong happened with the code or bus, with the drive light staying on, so the swapper timed out trying to access the hdd. Hope someone can help with this; for now I'm using the old wd/wfd/acd. The current system: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #65: Wed Mar 3 19:31:00 EST 1999 green@green.dyn.ez-ip.net:/usr/src/sys/compile/FELDMAN Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping=12 Features=0x8021bf real memory = 67108864 (65536K bytes) avail memory = 62337024 (60876K bytes) Bad DMI table checksum! Preloaded elf kernel "kernel" at 0xf02b2000. Probing for devices on PCI bus 0: chip0: rev 0x04 on pci0.0.0 chip1: rev 0x04 on pci0.1.0 ohci0: rev 0x03 int a irq 10 on pci0.2.0 usb0: OHCI version 1.0, legacy support alpm0: rev 0x00 on pci0.3.0 chip2: rev 0xb4 on pci0.7.0 ata-pci0: rev 0x20 int a irq 0 on pci0.15.0 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 vga0: rev 0x01 int a irq 0 on pci0.18.0 Probing for devices on PCI bus 1: Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A ppc0 at 0x378 irq 7 drq 3 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/1 bytes threshold plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 lppps0: on ppbus 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at drq 6 on isa snd0: sbmidi0 at 0x330 on isa snd0: opl0 at 0x388 on isa snd0: joy0 at 0x201 on isa joy0: joystick vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.2 usb0: uhub0 at usb0 uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered alsmb0: smbus0: on alsmb0 smb0: on smbus0 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging disabled DUMMYNET initialized (980901) -- size dn_pkt 48 ad0: ATA-? disk at ata0 as master ad0: 1554MB (3184170 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue ad3: ATA-? disk at ata1 as slave ad3: 1554MB (3184170 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S ad3: 16 secs/int, 0 depth queue acd0: CDROM drive at ata0 as slave acd0: drive speed 2067KB/sec, 128KB cache acd0: supported read types: CD-R, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked afd0: rewriteable drive at ata1 as master afd0: 120MB (246528 sectors), 963 cyls, 8 heads, 32 S/T, 512 B/S afd0: Unknown media (0x0) changing root device to ad0s1a WARNING: / was not properly dismounted ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 21:58:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id DD44514D95; Wed, 3 Mar 1999 21:58:45 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id WAA91892; Wed, 3 Mar 1999 22:58:11 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903040558.WAA91892@panzer.plutotech.com> Subject: Re: aic0 and CAM In-Reply-To: from Neal Westfall at "Mar 3, 1999 7:44:31 pm" To: nwestfal@Vorlon.odc.net (Neal Westfall) Date: Wed, 3 Mar 1999 22:58:11 -0700 (MST) Cc: dcs@newsguy.com, mi@aldan.algebra.com, current@FreeBSD.ORG, nate@FreeBSD.ORG, gconnor@cisco.com X-Mailer: ELM [version 2.4ME+ PL43 (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 Neal Westfall wrote... > Not that I have one of these controllers, but I just received my 3.1 > cd set in the mail today, and happened to notice that the Adaptec > 152x controller is listed on the back as supported, along with the > Tekram DC390 (and other AMD 53c974 based boards). I was sure that > these were both still unsupported under CAM. If I missed something > along the way, I apologize for bringing it up... They're both still unsupported, although we've got a driver for the AMD chips from Tekram that we're testing now. I suppose Walnut Creek made a mistake. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 22: 8:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [205.159.88.46]) by hub.freebsd.org (Postfix) with ESMTP id 3A1CD14D5F for ; Wed, 3 Mar 1999 22:08:48 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell2.aracnet.com (IDENT:1728@shell2.aracnet.com [205.159.88.20]) by mail4.aracnet.com (8.9.1/8.9.0) with ESMTP id WAA03872; Wed, 3 Mar 1999 22:08:15 -0800 Received: from localhost by shell2.aracnet.com (8.8.7) id WAA11188; Wed, 3 Mar 1999 22:08:17 -0800 X-Authentication-Warning: shell2.aracnet.com: beattie owned process doing -bs Date: Wed, 3 Mar 1999 22:08:17 -0800 (PST) From: Brian Beattie To: mi@aldan.algebra.com Cc: current@FreeBSD.ORG Subject: Re: aic0 and CAM In-Reply-To: <199903032112.QAA19717@misha.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Mar 1999, Mikhail Teterin wrote: > > > It has pretty horrible performance problems on 2.2.8-STABLE, even when > > > using DMA: > > > > [...] > > > 4.4%Sys 91.9%Intr 3.7%User 0.0%Nice 0.0%Idl 4244 inact 204 pci irq9 > > > | | | | | | | | | | 5288 cache 105 aic0 irq11 > > > ==++++++++++++++++++++++++++++++++++++++++++++++ 248 free 104 wdc0 irq14 > > > [...] > > > I would not use this type of card for disk if I could avoid it, and > > probably not for tape either, I have a scanner I plan to use with it. > > Yes, tape is the only target on this bus here... From reading the 2.2.8's > driver's source I see the DMA is not "yet supported", although the card > supports it and lets me choose the drq. Still, the amount of CPU it takes > to process an interrupt (CyrixInstead 8x86 at over 200MHz) does not look > right.... > Unless it is a really slow tape drive, I'd get a better adapter. In any case, As I said much of the protocol must be implemented by the CPU, most of this happens in the interrupt routine. Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 22:43:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id EDEDA14E12; Wed, 3 Mar 1999 22:43:03 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id GAA36272; Thu, 4 Mar 1999 06:42:43 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA27813; Wed, 3 Mar 1999 23:44:02 -0700 (MST) Message-Id: <199903040644.XAA27813@harmony.village.org> To: "Kenneth D. Merry" Subject: Re: aic0 and CAM Cc: mi@aldan.algebra.com, current@FreeBSD.ORG, nate@FreeBSD.ORG, gconnor@cisco.com In-reply-to: Your message of "Wed, 03 Mar 1999 13:50:38 MST." <199903032050.NAA86828@panzer.plutotech.com> References: <199903032050.NAA86828@panzer.plutotech.com> Date: Wed, 03 Mar 1999 23:44:02 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199903032050.NAA86828@panzer.plutotech.com> "Kenneth D. Merry" writes: : The 152x boards are programmed I/O only, I believe. They don't do DMA. : So it won't matter if the driver is rewritten for CAM, you'll still get : lousy performance from the board. They can do DMA, but I don't think there is a good way to know if you have a board that supports DMA and it is enabled. Even with DMA, you are limited to horrible perfomance :-( Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 22:47: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id F103414D20 for ; Wed, 3 Mar 1999 22:47:05 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id AAA83347; Thu, 4 Mar 1999 00:44:51 -0600 (CST) Date: Thu, 4 Mar 1999 00:44:51 -0600 From: Dan Nelson To: =?unknown-8bit?Q?S=F8ren_Schmidt?= Cc: Tugrul , current@FreeBSD.ORG Subject: Re: New ata driver failure on a ISA machine. Message-ID: <19990304004451.A82372@dan.emsphone.com> References: <199903032055.VAA87674@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.3i In-Reply-To: =?unknown-8bit?Q?=3C199903032055=2EVAA87674=40freebsd=2Edk=3E=3B_from_?= =?unknown-8bit?Q?=22S=F8ren_Schmidt=22_on_Wed_Mar__3_21:55:21_GMT_1999?= X-OS: FreeBSD 3.1-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Mar 03), Søren Schmidt said: > It seems Tugrul wrote: > > Second, at boot: > > > > [...] > > ata0 at 0x1f0-0x1f7 irq 14 on isa > > [...] > > ad0: ATA-? disk at ata0 as master > > ad0: 0MB (0 sectors), 723 cyls, 13 heads, 51 S/T, 512 B/S > > ad0: 16 secs/int, 0 depth queue > > changing root device to ad0a > > error 22: panic cannot mount root (2) > > That is allready fixed also. > > Wait until I commit the first update in an hour or so, then it > should work... Ok; now I have a similar failure case for you (using your updated code): Compaq LTE Elite laptop. Working wd0 probe strings: wdc0: unit 0 (wd0): , multi-block-4, sleep-hack wd0: 328MB (672525 sectors), 915 cyls, 15 heads, 49 S/T, 512 B/S ad0 probe output: ad0: ATA-? disk at ata0 as master ad0: 549280MB (1124925450 sectors), 915 cyls, 15 heads, 49 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue ... Considering FFS root fs. changing root device to ad0s1a ad0: invalid primary partition table: no magic changing root device to ad0a ad0: invalid primary partition table: no magic error 22: panic: cannot mount root (2) What I find fascinating is the LBAsize for the total # of sectors reported by the new driver code. 1124925450 is 0x430D000A. The correct amount, 672525, is 0x000A430D. Sounds like a word-swapping problem somewhere. Maybe LBAsize should only be used if necessary? -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 23: 9:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id AEF5C14CA3 for ; Wed, 3 Mar 1999 23:09:41 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id BAA18175 for ; Thu, 4 Mar 1999 01:09:23 -0600 (CST) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id BAA33855 for current@freebsd.org; Thu, 4 Mar 1999 01:09:23 -0600 (CST) Date: Thu, 4 Mar 1999 01:09:23 -0600 From: Alan Cox To: current@freebsd.org Subject: SMP users please read Message-ID: <19990304010923.A33835@nonpc.cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is an SMP-specific bug in pmap_remove_all. Specifically, it may fail to perform a TLB invalidation on the other processor(s) when one is in fact necessary. I don't have an SMP to test this, so would some of you with SMPs please do a sanity test on this patch? In effect, the patch disables an optimization for uniprocessors that doesn't work under our current SMP code. I will commit it as soon as I hear a few positive reports. Thanks, Alan Index: pmap.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/pmap.c,v retrieving revision 1.223 diff -c -r1.223 pmap.c *** pmap.c 1999/02/19 14:25:33 1.223 --- pmap.c 1999/03/04 06:52:21 *************** *** 1991,2001 **** --- 1991,2005 ---- if (pmap_track_modified(pv->pv_va)) vm_page_dirty(ppv->pv_vm_page); } + #ifdef SMP + update_needed = 1; + #else if (!update_needed && ((!curproc || (vmspace_pmap(curproc->p_vmspace) == pv->pv_pmap)) || (pv->pv_pmap == kernel_pmap))) { update_needed = 1; } + #endif TAILQ_REMOVE(&pv->pv_pmap->pm_pvlist, pv, pv_plist); TAILQ_REMOVE(&ppv->pv_list, pv, pv_list); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 23:13:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from ixion.honeywell.com (ixion.honeywell.com [129.30.4.80]) by hub.freebsd.org (Postfix) with ESMTP id 192C314D29 for ; Wed, 3 Mar 1999 23:13:25 -0800 (PST) (envelope-from sleas@ixion.honeywell.com) Received: by ixion.honeywell.com (1.40.112.8/16.2) id AA129711588; Thu, 4 Mar 1999 01:13:08 -0600 Date: Thu, 4 Mar 1999 01:13:08 -0600 From: Shawn Leas To: freebsd-current@freebsd.org Subject: Device FS? Message-Id: <19990304011308.A12664@ixion.honeywell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I heard (or thought so) a long time ago that FreeBSD had a devfs like filesystem. Now I remember, here's where I found it mentioned in respect to FreeBeasty... http://www.cs.uml.edu/~acahalan/linux/devfs.html Is this still experimental? Oh, and has anyone heard of any LFS projects on freebsd, and/or maybe LVM? I'm trying to think of reasons to switch over from Linux 2.2.2-ac7-lvm0.6-devfs to -current, or maybe stable, depending on what I feel like... -- Shawn <=========== America Held Hostage ===========> Day 2233 for the poor and the middle class. Day 2252 for the rich and the dead. 689 days remaining in the Raw Deal. <============================================> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 23:19:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 2881214D49; Wed, 3 Mar 1999 23:19:56 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id QAA28888; Thu, 4 Mar 1999 16:19:49 +0900 (JST) Message-ID: <36DE33CE.45C27088@newsguy.com> Date: Thu, 04 Mar 1999 16:18:38 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Satoshi Asami Cc: robert+freebsd@cyrus.watson.org, sos@freebsd.dk, doconnor@gsoft.com.au, current@FreeBSD.ORG, geoffr@is.co.za Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. References: <199903032259.OAA61888@silvia.hip.berkeley.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Satoshi Asami wrote: > > * From: Robert Watson > > * away logged in via the network performing this recovery. Having the > * drives automatically renumber themselves on the complete failure of one > * drive (and it was fairly complete) would have been a disaster. This is > > Or just think "ccd". There are people building disk servers out of > IDE drives these days, and having the ccd configured in a wrong order > could be disastrous. Think "vinum" then... ;-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 23:25:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from ixion.honeywell.com (ixion.honeywell.com [129.30.4.80]) by hub.freebsd.org (Postfix) with ESMTP id 062FD14DA6 for ; Wed, 3 Mar 1999 23:25:52 -0800 (PST) (envelope-from sleas@ixion.honeywell.com) Received: by ixion.honeywell.com (1.40.112.8/16.2) id AA142142335; Thu, 4 Mar 1999 01:25:35 -0600 Date: Thu, 4 Mar 1999 01:25:35 -0600 From: Shawn Leas To: freebsd-current@FreeBSD.ORG Subject: Re: Device FS? Message-Id: <19990304012535.B12979@ixion.honeywell.com> References: <19990304011308.A12664@ixion.honeywell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990304011308.A12664@ixion.honeywell.com>; from Shawn Leas on Thu, Mar 04, 1999 at 01:13:08AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 04, 1999 at 01:13:08AM -0600, Shawn Leas wrote: > I heard (or thought so) a long time ago that FreeBSD > had a devfs like filesystem. > > Now I remember, here's where I found it mentioned in > respect to FreeBeasty... > http://www.cs.uml.edu/~acahalan/linux/devfs.html Forget this question, I found it on the projects page. The link is broke, though. At least the guy no longer has devfs right out front. > Is this still experimental? Oh, and has anyone heard > of any LFS projects on freebsd, and/or maybe LVM? I found Vinum. Looks DAMN NICE!!! > I'm trying to think of reasons to switch over from > Linux 2.2.2-ac7-lvm0.6-devfs to -current, or maybe > stable, depending on what I feel like... I still wanna know about LFSes or Journaling FSes if anyonbe knows NEthing... -- Shawn <=========== America Held Hostage ===========> Day 2233 for the poor and the middle class. Day 2252 for the rich and the dead. 689 days remaining in the Raw Deal. <============================================> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 23:39:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id C327014DBC for ; Wed, 3 Mar 1999 23:39:43 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id XAA60233; Wed, 3 Mar 1999 23:38:51 -0800 (PST) (envelope-from obrien) Date: Wed, 3 Mar 1999 23:38:51 -0800 From: "David O'Brien" To: Mark Murray Cc: current@freebsd.org Subject: Re: bmake/contrib framework for egcs Message-ID: <19990303233851.A59466@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990302025600.F13655@relay.nuxi.com> <199903031812.UAA80419@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199903031812.UAA80419@greenpeace.grondar.za>; from Mark Murray on Wed, Mar 03, 1999 at 08:12:06PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It would help a lot if you could make it CVSUPpable :-). Those of us > in the third world would greatly appreciate that! You talked me into it :-) distributions are "egcs" (or broken into "bmake-egcs" and "contrib-egcs") *default host=relay.nuxi.com *default base=. *default release=cvs *default delete use-rel-suffix egcs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 3 23:49:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 71D4714D5F for ; Wed, 3 Mar 1999 23:49:29 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA16519; Wed, 3 Mar 1999 23:40:43 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpds16517; Thu Mar 4 07:40:39 1999 Date: Wed, 3 Mar 1999 23:40:20 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: Brian Feldman Cc: current@FreeBSD.ORG Subject: Re: ATA not quite peachy 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 Oi! If you have softupdates on the LS120 drive, be aware that soft updates has been known to have odd behaviour with some drive types (e.g. IDE drives in 1-(non-multiblock) block mode, and floppy drives. I wouldn't be surprised if LS120 drives had the capacity to confuse softupdates.. julian On Thu, 4 Mar 1999, Brian Feldman wrote: > After testing out the new ATA drivers, I've only got a single problem. My > box locked up while accessing the LS-120 (and, seemingly, swapping): > > Mar 4 00:20:02 green /kernel: atapi_transfer: bad command phase > Mar 4 00:20:33 green /kernel: swap_pager: indefinite wait buffer: device: > 0x20019, blkno: 2800, size: 8192 > > I think what was going on was a second read transfer was trying to occur > while one was already going, and something wrong happened with the code or > bus, with the drive light staying on, so the swapper timed out trying to > access the hdd. > > Hope someone can help with this; for now I'm using the old wd/wfd/acd. > > The current system: > Copyright (c) 1992-1999 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-CURRENT #65: Wed Mar 3 19:31:00 EST 1999 > green@green.dyn.ez-ip.net:/usr/src/sys/compile/FELDMAN > Timecounter "i8254" frequency 1193182 Hz > CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x58c Stepping=12 > Features=0x8021bf > real memory = 67108864 (65536K bytes) > avail memory = 62337024 (60876K bytes) > Bad DMI table checksum! > Preloaded elf kernel "kernel" at 0xf02b2000. > Probing for devices on PCI bus 0: > chip0: rev 0x04 on pci0.0.0 > chip1: rev 0x04 on pci0.1.0 > ohci0: rev 0x03 int a irq > 10 on > pci0.2.0 > usb0: OHCI version 1.0, legacy support > alpm0: rev 0x00 on pci0.3.0 > chip2: rev 0xb4 on pci0.7.0 > ata-pci0: rev 0x20 int a irq 0 on > pci0.15.0 > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > vga0: rev 0x01 int a irq 0 on > pci0.18.0 > Probing for devices on PCI bus 1: > Probing for PnP devices: > Probing for devices on the ISA bus: > sc0 on isa > sc0: VGA color <16 virtual consoles, flags=0x0> > atkbdc0 at 0x60-0x6f on motherboard > atkbd0 irq 1 on isa > psm0 irq 12 on isa > psm0: model Generic PS/2 mouse, device ID 0 > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > ppc0 at 0x378 irq 7 drq 3 on isa > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/1 bytes threshold > plip0: on ppbus 0 > lpt0: on ppbus 0 > lpt0: Interrupt-driven port > ppi0: on ppbus 0 > lppps0: on ppbus 0 > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > sb0 at 0x220 irq 5 drq 1 on isa > snd0: > sbxvi0 at drq 6 on isa > snd0: > sbmidi0 at 0x330 on isa > snd0: > opl0 at 0x388 on isa > snd0: > joy0 at 0x201 on isa > joy0: joystick > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > npx0 on motherboard > npx0: INT 16 interface > apm0 on isa > apm: found APM BIOS version 1.2 > usb0: > uhub0 at usb0 > uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > alsmb0: > smbus0: on alsmb0 > smb0: on smbus0 > IP packet filtering initialized, divert enabled, rule-based forwarding > enabled, > default to accept, logging disabled > DUMMYNET initialized (980901) -- size dn_pkt 48 > ad0: ATA-? disk at ata0 as master > ad0: 1554MB (3184170 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 0 depth queue > ad3: ATA-? disk at ata1 as slave > ad3: 1554MB (3184170 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S > ad3: 16 secs/int, 0 depth queue > acd0: CDROM drive at ata0 as slave > acd0: drive speed 2067KB/sec, 128KB cache > acd0: supported read types: CD-R, CD-DA > acd0: Audio: play, 16 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: no/blank disc inside, unlocked > afd0: rewriteable drive at ata1 as > master > afd0: 120MB (246528 sectors), 963 cyls, 8 heads, 32 S/T, 512 B/S > afd0: Unknown media (0x0) > changing root device to ad0s1a > WARNING: / was not properly dismounted > ffs_mountfs: superblock updated for soft updates > ffs_mountfs: superblock updated for soft updates > ffs_mountfs: superblock updated for soft updates > > Brian Feldman _ __ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > > 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 Mar 3 23:59:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id C3DD614DA5 for ; Wed, 3 Mar 1999 23:59:28 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA16759; Wed, 3 Mar 1999 23:57:34 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpdX16757; Thu Mar 4 07:57:23 1999 Date: Wed, 3 Mar 1999 23:57:03 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: Shawn Leas Cc: freebsd-current@FreeBSD.ORG Subject: Re: Device FS? In-Reply-To: <19990304011308.A12664@ixion.honeywell.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 FreeBSD has had a devfs that is not genrally useful for over 2 years. The code to make it useful was removed from the tree due to various reasons that can be argued ither way. I haven't had the inspiration to re-write it as it needs to be changed to take into account some new developments in FreeBSD (e.g. CAM based SCSI) The DEVFS on FreeBSD is bot similar and different from the DEVFS im linux in htat the LINUX devfs can have devices in the DEVFS that are not physically present, in order to preserve the ownership information (It's not persistant across reboot, bot one can do a mknod, to create a device, and assign it ownerships and permissions, in th ehope that at some time on the future, a device of that name will turn up. The FreeBSD DEVFS only creates a node in /dev when the associated hardware is actually found, and hte node is not permitted to exist in any other case. Even though I wrrote DEVFS I see a severe limitiation to its usefulness due to a number of factors (including the fact that some people have hundreds of dev directories in hundreds of chroot trees). THese are surmountable, but I have a different idea I'm ruminating on that might make a DEVFS look a bit old-fashionned. On Thu, 4 Mar 1999, Shawn Leas wrote: > I heard (or thought so) a long time ago that FreeBSD > had a devfs like filesystem. yes it does.. the original.. > > Now I remember, here's where I found it mentioned in > respect to FreeBeasty... > http://www.cs.uml.edu/~acahalan/linux/devfs.html > > Is this still experimental? Oh, and has anyone heard > of any LFS projects on freebsd, and/or maybe LVM? > LFS suffered a severe disilussionment problem when it was found that it didn't seem to give the promised performance. It's present;y not in the tree (only in the CVS attic) because no-one wanted to work on it any more. We have a LVM called vinum ("vinum veritas" being the latin quote) > I'm trying to think of reasons to switch over from > Linux 2.2.2-ac7-lvm0.6-devfs to -current, or maybe > stable, depending on what I feel like... if you've got a few hundred MB free, give 3.1 a try (I mean... It's free) > > -- Shawn > <=========== America Held Hostage ===========> > Day 2233 for the poor and the middle class. > Day 2252 for the rich and the dead. > 689 days remaining in the Raw Deal. > <============================================> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 0: 9:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id CAB7814EB5 for ; Thu, 4 Mar 1999 00:09:30 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id AAA16865; Thu, 4 Mar 1999 00:03:44 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpdY16863; Thu Mar 4 08:03:34 1999 Date: Thu, 4 Mar 1999 00:03:14 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: Shawn Leas Cc: freebsd-current@FreeBSD.ORG Subject: Re: Device FS? In-Reply-To: <19990304012535.B12979@ixion.honeywell.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 oh yeah.. also check out SOFT UPDATES http://www.freebsd.org/cgi/cvsweb.cgi/src/contrib/sys/softupdates/ On Thu, 4 Mar 1999, Shawn Leas wrote: > On Thu, Mar 04, 1999 at 01:13:08AM -0600, Shawn Leas wrote: > > I heard (or thought so) a long time ago that FreeBSD > > had a devfs like filesystem. > > > > Now I remember, here's where I found it mentioned in > > respect to FreeBeasty... > > http://www.cs.uml.edu/~acahalan/linux/devfs.html > > Forget this question, I found it on the projects page. > The link is broke, though. At least the guy no longer > has devfs right out front. No, I still have it on the burner though I took it off the page.. > > > Is this still experimental? Oh, and has anyone heard > > of any LFS projects on freebsd, and/or maybe LVM? > > I found Vinum. Looks DAMN NICE!!! > > > I'm trying to think of reasons to switch over from > > Linux 2.2.2-ac7-lvm0.6-devfs to -current, or maybe > > stable, depending on what I feel like... > > I still wanna know about LFSes or Journaling FSes if > anyonbe knows NEthing... > > -- Shawn > <=========== America Held Hostage ===========> > Day 2233 for the poor and the middle class. > Day 2252 for the rich and the dead. > 689 days remaining in the Raw Deal. > <============================================> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 0:48:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id EDE3114E25 for ; Thu, 4 Mar 1999 00:48:21 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id RAA10132; Thu, 4 Mar 1999 17:48:13 +0900 (JST) Message-ID: <36DE464E.6F7989B7@newsguy.com> Date: Thu, 04 Mar 1999 17:37:34 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Shawn Leas Cc: freebsd-current@FreeBSD.ORG Subject: Re: Device FS? References: <19990304011308.A12664@ixion.honeywell.com> <19990304012535.B12979@ixion.honeywell.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Shawn Leas wrote: > > I still wanna know about LFSes or Journaling FSes if > anyonbe knows NEthing... You are likely to get the same benefits you'd normally get if you use softupdates instead. LFS/JFS will hardly give you any sizable advantage unless: 1) It exports a transaction interface *AND* 2) The application uses that interface. Anyone wanting to correct me on this, please feel free to do so. I haven't read this particular thread for a while now, and my archives are stored someone among my backup cds. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 1: 1:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4350F14DD0 for ; Thu, 4 Mar 1999 01:01:18 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA89001; Thu, 4 Mar 1999 10:00:54 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903040900.KAA89001@freebsd.dk> Subject: Re: ATA not quite peachy In-Reply-To: from Brian Feldman at "Mar 4, 1999 5:41: 2 am" To: green@zone.syracuse.net (Brian Feldman) Date: Thu, 4 Mar 1999 10:00:54 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Brian Feldman wrote: > After testing out the new ATA drivers, I've only got a single problem. My > box locked up while accessing the LS-120 (and, seemingly, swapping): > > Mar 4 00:20:02 green /kernel: atapi_transfer: bad command phase > Mar 4 00:20:33 green /kernel: swap_pager: indefinite wait buffer: device: > 0x20019, blkno: 2800, size: 8192 > > I think what was going on was a second read transfer was trying to occur > while one was already going, and something wrong happened with the code or > bus, with the drive light staying on, so the swapper timed out trying to > access the hdd. Hmm, I'm not sure the afd driver is working yet, but thanks for the input. I'll fix it as soon as I get a writeable ZIP medium... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 1: 6:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id A915C14E20 for ; Thu, 4 Mar 1999 01:06:02 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA89031; Thu, 4 Mar 1999 10:05:17 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903040905.KAA89031@freebsd.dk> Subject: Re: ata1: unwanted interrupt In-Reply-To: from Alex Zepeda at "Mar 3, 1999 2:57:50 pm" To: garbanzo@hooked.net (Alex Zepeda) Date: Thu, 4 Mar 1999 10:05:17 +0100 (CET) Cc: osa@etrust.ru, chris@calldei.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Alex Zepeda wrote: > On Thu, 4 Mar 1999, oZZ!!! wrote: > > > What exactly is 'unwanted interrupt' supposed to mean, and is it > > > likely to be a problem in my kernel configuration? (I can send a copy > > > of it on request...) > > i think it tell you about not used 2nd IDE controller... > > Nope. I've got three IDE/ATAPI devices, primary master, secondary > master+slave, and I still get it. I've got a PIIX4 controller. Its an artifact from the probes, it will go away as soon as I get the last bits of that running when interrupts are enabled. No need to worry about it though. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 1:13:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 689E714DCB for ; Thu, 4 Mar 1999 01:13:46 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA89063; Thu, 4 Mar 1999 10:13:24 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903040913.KAA89063@freebsd.dk> Subject: Re: UPDATE: ATA/ATAPI driver new version available. In-Reply-To: from ! at "Mar 4, 1999 1:32:41 am" To: osa@etrust.ru Date: Thu, 4 Mar 1999 10:13:24 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems oZZ!!! wrote: > ad0: ATA-3 disk at ata0 as master > ad0: 2503MB (5126964 sectors), 5086 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 0 depth queue > ad1: ATA-? disk at ata0 as slave > ad1: 1277MB (2616240 sectors), 2595 cyls, 16 heads, 63 S/T, 512 B/S > ad1: 16 secs/int, 0 depth queue > acd0: CDROM drive at ata1 as slave > acd0: drive speed 0KB/secacd0: supported read types: > ^^^^^ ???? > acd0: Mechanism: caddy > acd0: Medium: CD-ROM unknown medium That looks wierd, does it work with the old driver ?? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 1:24:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B7D2014E79 for ; Thu, 4 Mar 1999 01:24:30 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA89095; Thu, 4 Mar 1999 10:24:07 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903040924.KAA89095@freebsd.dk> Subject: Re: New ata driver failure on a ISA machine. In-Reply-To: <19990304004451.A82372@dan.emsphone.com> from Dan Nelson at "Mar 4, 1999 0:44:51 am" To: dnelson@emsphone.com (Dan Nelson) Date: Thu, 4 Mar 1999 10:24:06 +0100 (CET) Cc: tugrul@ianai.BlackSun.org, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Dan Nelson wrote: > wdc0: unit 0 (wd0): , multi-block-4, sleep-hack > wd0: 328MB (672525 sectors), 915 cyls, 15 heads, 49 S/T, 512 B/S >ad0 probe output: > > ad0: ATA-? disk at ata0 as master > ad0: 549280MB (1124925450 sectors), 915 cyls, 15 heads, 49 S/T, 512 B/S > ad0: 16 secs/int, 0 depth queue >What I find fascinating is the LBAsize for the total # of sectors >reported by the new driver code. 1124925450 is 0x430D000A. The >correct amount, 672525, is 0x000A430D. Sounds like a word-swapping >problem somewhere. Maybe LBAsize should only be used if necessary? I see two problems here, one is that unless it was you that specified 4 secs/intr in the wd case (what flags do you use), there is something fishy there. There is is just wonderfull, why complain about that :) Seriouly thats a bug, fix is in next update... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 1:33:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 8FB8714E9E; Thu, 4 Mar 1999 01:33:12 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA43793; Thu, 4 Mar 1999 01:32:46 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Kenneth D. Merry" Cc: nwestfal@Vorlon.odc.net (Neal Westfall), dcs@newsguy.com, mi@aldan.algebra.com, current@FreeBSD.ORG, nate@FreeBSD.ORG, gconnor@cisco.com Subject: Re: aic0 and CAM In-reply-to: Your message of "Wed, 03 Mar 1999 22:58:11 MST." <199903040558.WAA91892@panzer.plutotech.com> Date: Thu, 04 Mar 1999 01:32:46 -0800 Message-ID: <43790.920539966@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We did. > Neal Westfall wrote... > > Not that I have one of these controllers, but I just received my 3.1 > > cd set in the mail today, and happened to notice that the Adaptec > > 152x controller is listed on the back as supported, along with the > > Tekram DC390 (and other AMD 53c974 based boards). I was sure that > > these were both still unsupported under CAM. If I missed something > > along the way, I apologize for bringing it up... > > They're both still unsupported, although we've got a driver for the AMD > chips from Tekram that we're testing now. I suppose Walnut Creek made a > mistake. > > Ken > -- > Kenneth Merry > ken@plutotech.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 Thu Mar 4 1:50:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from aire.open.ac.uk (aire.open.ac.uk [137.108.40.21]) by hub.freebsd.org (Postfix) with ESMTP id 0D2E414DBC for ; Thu, 4 Mar 1999 01:50:45 -0800 (PST) (envelope-from A.M.Zanker@open.ac.uk) Received: from mallard.open.ac.uk ([137.108.40.50] helo=mallard) by aire.open.ac.uk with smtp (Exim 2.12 #1) id 10IUlt-00017v-00 for current@freebsd.org; Thu, 4 Mar 1999 09:50:25 +0000 Message-Id: <4.1.19990304094805.00c037f0@aire.open.ac.uk> X-Sender: mikez@aire.open.ac.uk X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 04 Mar 1999 09:50:24 +0000 To: current@freebsd.org From: Mike Zanker Subject: Typo in new atapi-all.c Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My kernel is failing at the "make depend" stage owing to typos in the new ATA code. It seems that atapi-all.c is trying to include "atapifd.h" when the file is actually called "atapi-fd.h". The same may apply to other included files. Regards, Mike -- Mike Zanker | Email: A.M.Zanker@open.ac.uk Network and Computer Services Group | Tel : +44 1908 652726 The Open University | Fax : +44 1908 652193 Milton Keynes, UK | PGP public key available To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 1:55:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8CA6B14ECC for ; Thu, 4 Mar 1999 01:54:08 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA89160; Thu, 4 Mar 1999 10:53:47 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903040953.KAA89160@freebsd.dk> Subject: Re: Typo in new atapi-all.c In-Reply-To: <4.1.19990304094805.00c037f0@aire.open.ac.uk> from Mike Zanker at "Mar 4, 1999 9:50:24 am" To: A.M.Zanker@open.ac.uk (Mike Zanker) Date: Thu, 4 Mar 1999 10:53:47 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Mike Zanker wrote: > My kernel is failing at the "make depend" stage owing to typos in the new > ATA code. It seems that atapi-all.c is trying to include "atapifd.h" when > the file is actually called "atapi-fd.h". The same may apply to other > included files. No it was because I forgot to add the driver to files.i386, just fixed. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 2: 0:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id BD66B150C4 for ; Thu, 4 Mar 1999 02:00:47 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10IUvC-0008fj-00; Thu, 4 Mar 1999 12:00:02 +0200 From: Sheldon Hearn To: Mike Zanker Cc: current@freebsd.org Subject: Re: Typo in new atapi-all.c In-reply-to: Your message of "Thu, 04 Mar 1999 09:50:24 GMT." <4.1.19990304094805.00c037f0@aire.open.ac.uk> Date: Thu, 04 Mar 1999 12:00:02 +0200 Message-ID: <33338.920541602@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 04 Mar 1999 09:50:24 GMT, Mike Zanker wrote: > My kernel is failing at the "make depend" stage owing to typos in the new > ATA code. It seems that atapi-all.c is trying to include "atapifd.h" when > the file is actually called "atapi-fd.h". The same may apply to other > included files. Are you sure it isn't because atapi-fd.c is missing from your sys/i386/conf/files.i386 ? Check for a line like this: dev/ata/atapi-fd.c optional atapifd device-driver This is an oversight in the last commit and should be fixed RSN. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 2: 4: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 18B0714EF0 for ; Thu, 4 Mar 1999 02:03:53 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10IUyG-0008z9-00; Thu, 4 Mar 1999 12:03:12 +0200 From: Sheldon Hearn Cc: Mike Zanker , current@freebsd.org Subject: Re: Typo in new atapi-all.c In-reply-to: Your message of "Thu, 04 Mar 1999 12:00:02 +0200." <33338.920541602@axl.noc.iafrica.com> Date: Thu, 04 Mar 1999 12:03:12 +0200 Message-ID: <34529.920541792@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 04 Mar 1999 12:00:02 +0200, Sheldon Hearn wrote: > This is an oversight in the last commit and should be fixed RSN. I'm living in the past again. Fixed in rev1.225 of files.i386 . Update your src/sys/i386/conf, since LINT has been updated as well. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 2: 8:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from aire.open.ac.uk (aire.open.ac.uk [137.108.40.21]) by hub.freebsd.org (Postfix) with ESMTP id 01D8915136 for ; Thu, 4 Mar 1999 02:07:54 -0800 (PST) (envelope-from A.M.Zanker@open.ac.uk) Received: from mallard.open.ac.uk ([137.108.40.50] helo=mallard) by aire.open.ac.uk with smtp (Exim 2.12 #1) id 10IV1w-00018s-00; Thu, 4 Mar 1999 10:07:00 +0000 Message-Id: <4.1.19990304100505.00bd9650@aire.open.ac.uk> X-Sender: mikez@aire.open.ac.uk X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 04 Mar 1999 10:07:00 +0000 To: Sheldon Hearn From: Mike Zanker Subject: Re: Typo in new atapi-all.c Cc: current@freebsd.org In-Reply-To: <33338.920541602@axl.noc.iafrica.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:00 04/03/99 , Sheldon Hearn wrote: >Are you sure it isn't because atapi-fd.c is missing from your >sys/i386/conf/files.i386 ? Yes, that's the reason - I guess I shouldn't speculate when I don't know how it all gels together! Thanks, Mike -- Mike Zanker | Email: A.M.Zanker@open.ac.uk Network and Computer Services Group | Tel : +44 1908 652726 The Open University | Fax : +44 1908 652193 Milton Keynes, UK | PGP public key available To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 2:10:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from aire.open.ac.uk (aire.open.ac.uk [137.108.40.21]) by hub.freebsd.org (Postfix) with ESMTP id C978514F1E for ; Thu, 4 Mar 1999 02:10:30 -0800 (PST) (envelope-from A.M.Zanker@open.ac.uk) Received: from mallard.open.ac.uk ([137.108.40.50] helo=mallard) by aire.open.ac.uk with smtp (Exim 2.12 #1) id 10IV42-000197-00; Thu, 4 Mar 1999 10:09:10 +0000 Message-Id: <4.1.19990304100812.00cb03e0@aire.open.ac.uk> X-Sender: mikez@aire.open.ac.uk X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 04 Mar 1999 10:09:10 +0000 To: Sheldon Hearn From: Mike Zanker Subject: Re: Typo in new atapi-all.c Cc: current@freebsd.org In-Reply-To: <34529.920541792@axl.noc.iafrica.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:03 04/03/99 , Sheldon Hearn wrote: >I'm living in the past again. Fixed in rev1.225 of files.i386 . Update >your src/sys/i386/conf, since LINT has been updated as well. Hmm, I just did but via cvsup.uk.freebsd.org. Maybe the fix hasn't propagated to there yet. Thanks, Mike -- Mike Zanker | Email: A.M.Zanker@open.ac.uk Network and Computer Services Group | Tel : +44 1908 652726 The Open University | Fax : +44 1908 652193 Milton Keynes, UK | PGP public key available To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 2:48:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from bart.esiee.fr (bart.esiee.fr [147.215.1.20]) by hub.freebsd.org (Postfix) with ESMTP id A789B14E6D for ; Thu, 4 Mar 1999 02:47:36 -0800 (PST) (envelope-from bonnetf@bart.esiee.fr) Received: (from bonnetf@localhost) by bart.esiee.fr (8.9.1a/8.9.1) id LAA14075 for freebsd-current@FreeBSD.ORG; Thu, 4 Mar 1999 11:47:17 +0100 (MET) From: Frank Bonnet Message-Id: <199903041047.LAA14075@bart.esiee.fr> Subject: NFS problem To: freebsd-current@FreeBSD.ORG Date: Thu, 04 Mar 1999 11:47:17 MET X-Mailer: Elm [revision: 112.7] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I run a mailhub at 3.1 The problem is the /var/mail directory is NFS mounted with HPUX 10.20 clients there is a file locking problem due to the HPUX /bin/mail command which try to create a user.lock file in the NFS mounted /var/mail directory ... Is there a NFS workaround or do I have to give up now ? TIA -- Frank Bonnet Groupe ESIEE Paris http://www.esiee.fr/~bonnetf/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 3: 8:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (Postfix) with SMTP id 8F47514E85 for ; Thu, 4 Mar 1999 03:08:34 -0800 (PST) (envelope-from will@ns.oeno.com) Received: (qmail 23583 invoked by uid 1001); 4 Mar 1999 11:08:16 -0000 To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? References: <79192.920464790@axl.noc.iafrica.com.newsgate.clinet.fi> From: Ville-Pertti Keinonen Date: 04 Mar 1999 13:05:39 +0200 In-Reply-To: Sheldon Hearn's message of "3 Mar 1999 15:12:04 +0200" Message-ID: <86iuchms58.fsf@not.oeno.com> Lines: 38 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn writes: > I'm not sure I understand what real-world frustrations people are having > here. Is this thread the product of reactionary criticism, or are there > real examples of situations in which there are serious disadvantages to > the way Soren has things working? So far, you seem to have received replies arguing for "convenience", which isn't the only valid reason for static device numbering. When a boot fails with something like /dev/rwd2s1g: Device not configured, how long will it take you to figure out that it was actually wd1 that didn't probe and what is now visible as wd1 is what you used to know as wd2? If the disks are identical, you have to look carefully at the boot messages. If that isn't a POLA violation, what is? What about if your /etc/fstab only checks/mounts partitions on wd0/wd1, and /etc/rc doesn't fail because of the missing wd2? Instead, you have partitions in unexpected places... Oh and of course if you aren't pedantic about partitioning conventions and have a non-'b' swap partition or a 'b'-partition used as a filesystem, you might be swapping onto a filesystem...even if the fsck fails and drops you into single user mode. Disks can fail to probe, even when they aren't permanently broken, e.g. because of failure to spin up. Fixed numbering isn't merely a convenience for those who add and remove devices routinely. Changing the default behavior from a safer alternative to a more dangerous one might not be a good thing. Of course dangerous numbering is the default for SCSI devices, as well... Perhaps it's reasonable to expect people who don't know what they're doing to only have one or two disks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 4:14:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.atl.bellsouth.net (mail1.atl.bellsouth.net [205.152.0.28]) by hub.freebsd.org (Postfix) with ESMTP id C01A914F03 for ; Thu, 4 Mar 1999 04:14:09 -0800 (PST) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-73-127.atl.bellsouth.net [209.214.73.127]) by mail1.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id HAA03599; Thu, 4 Mar 1999 07:13:19 -0500 (EST) Received: from wghicks (localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id HAA13751; Thu, 4 Mar 1999 07:04:08 -0500 (EST) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199903041204.HAA13751@bellsouth.net> To: Shawn Leas Cc: freebsd-current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: Device FS? In-reply-to: Your message of "Thu, 04 Mar 1999 01:13:08 CST." <19990304011308.A12664@ixion.honeywell.com> Date: Thu, 04 Mar 1999 07:04:08 -0500 From: W Gerald Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I heard (or thought so) a long time ago that FreeBSD > had a devfs like filesystem. > > Now I remember, here's where I found it mentioned in > respect to FreeBeasty... > http://www.cs.uml.edu/~acahalan/linux/devfs.html Har. That's good (not) old Albert Cahalan. Troll of the Year (97-98). I though he was a 'ps' guru... Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 4:28:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from zone.syracuse.net (zone.syracuse.net [209.2.141.6]) by hub.freebsd.org (Postfix) with ESMTP id 56E0814EEA for ; Thu, 4 Mar 1999 04:28:48 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.9.2/8.9.2) with ESMTP id MAA29400; Thu, 4 Mar 1999 12:28:31 GMT (envelope-from green@zone.syracuse.net) Date: Thu, 4 Mar 1999 12:28:31 +0000 (GMT) From: Brian Feldman To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: ATA not quite peachy 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 SoftUpdates on my LS-120? I'm not a masochist!! Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ On Wed, 3 Mar 1999, Julian Elischer wrote: > Oi! If you have softupdates on the LS120 drive, be aware that soft updates > has been known to have odd behaviour with some drive types (e.g. IDE > drives in 1-(non-multiblock) block mode, and floppy drives. I wouldn't be > surprised if LS120 drives had the capacity to confuse softupdates.. > > julian > > > On Thu, 4 Mar 1999, Brian Feldman wrote: > > > After testing out the new ATA drivers, I've only got a single problem. My > > box locked up while accessing the LS-120 (and, seemingly, swapping): > > > > Mar 4 00:20:02 green /kernel: atapi_transfer: bad command phase > > Mar 4 00:20:33 green /kernel: swap_pager: indefinite wait buffer: device: > > 0x20019, blkno: 2800, size: 8192 > > > > I think what was going on was a second read transfer was trying to occur > > while one was already going, and something wrong happened with the code or > > bus, with the drive light staying on, so the swapper timed out trying to > > access the hdd. > > > > Hope someone can help with this; for now I'm using the old wd/wfd/acd. > > > > The current system: > > Copyright (c) 1992-1999 FreeBSD Inc. > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > > The Regents of the University of California. All rights reserved. > > FreeBSD 4.0-CURRENT #65: Wed Mar 3 19:31:00 EST 1999 > > green@green.dyn.ez-ip.net:/usr/src/sys/compile/FELDMAN > > Timecounter "i8254" frequency 1193182 Hz > > CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) > > Origin = "AuthenticAMD" Id = 0x58c Stepping=12 > > Features=0x8021bf > > real memory = 67108864 (65536K bytes) > > avail memory = 62337024 (60876K bytes) > > Bad DMI table checksum! > > Preloaded elf kernel "kernel" at 0xf02b2000. > > Probing for devices on PCI bus 0: > > chip0: rev 0x04 on pci0.0.0 > > chip1: rev 0x04 on pci0.1.0 > > ohci0: rev 0x03 int a irq > > 10 on > > pci0.2.0 > > usb0: OHCI version 1.0, legacy support > > alpm0: rev 0x00 on pci0.3.0 > > chip2: rev 0xb4 on pci0.7.0 > > ata-pci0: rev 0x20 int a irq 0 on > > pci0.15.0 > > ata0 at 0x01f0 irq 14 on ata-pci0 > > ata1 at 0x0170 irq 15 on ata-pci0 > > vga0: rev 0x01 int a irq 0 on > > pci0.18.0 > > Probing for devices on PCI bus 1: > > Probing for PnP devices: > > Probing for devices on the ISA bus: > > sc0 on isa > > sc0: VGA color <16 virtual consoles, flags=0x0> > > atkbdc0 at 0x60-0x6f on motherboard > > atkbd0 irq 1 on isa > > psm0 irq 12 on isa > > psm0: model Generic PS/2 mouse, device ID 0 > > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > > sio0: type 16550A > > sio1 at 0x2f8-0x2ff irq 3 on isa > > sio1: type 16550A > > ppc0 at 0x378 irq 7 drq 3 on isa > > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > > ppc0: FIFO with 16/16/1 bytes threshold > > plip0: on ppbus 0 > > lpt0: on ppbus 0 > > lpt0: Interrupt-driven port > > ppi0: on ppbus 0 > > lppps0: on ppbus 0 > > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > > sb0 at 0x220 irq 5 drq 1 on isa > > snd0: > > sbxvi0 at drq 6 on isa > > snd0: > > sbmidi0 at 0x330 on isa > > snd0: > > opl0 at 0x388 on isa > > snd0: > > joy0 at 0x201 on isa > > joy0: joystick > > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > > npx0 on motherboard > > npx0: INT 16 interface > > apm0 on isa > > apm: found APM BIOS version 1.2 > > usb0: > > uhub0 at usb0 > > uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub0: 2 ports with 2 removable, self powered > > alsmb0: > > smbus0: on alsmb0 > > smb0: on smbus0 > > IP packet filtering initialized, divert enabled, rule-based forwarding > > enabled, > > default to accept, logging disabled > > DUMMYNET initialized (980901) -- size dn_pkt 48 > > ad0: ATA-? disk at ata0 as master > > ad0: 1554MB (3184170 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S > > ad0: 16 secs/int, 0 depth queue > > ad3: ATA-? disk at ata1 as slave > > ad3: 1554MB (3184170 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S > > ad3: 16 secs/int, 0 depth queue > > acd0: CDROM drive at ata0 as slave > > acd0: drive speed 2067KB/sec, 128KB cache > > acd0: supported read types: CD-R, CD-DA > > acd0: Audio: play, 16 volume levels > > acd0: Mechanism: ejectable tray > > acd0: Medium: no/blank disc inside, unlocked > > afd0: rewriteable drive at ata1 as > > master > > afd0: 120MB (246528 sectors), 963 cyls, 8 heads, 32 S/T, 512 B/S > > afd0: Unknown media (0x0) > > changing root device to ad0s1a > > WARNING: / was not properly dismounted > > ffs_mountfs: superblock updated for soft updates > > ffs_mountfs: superblock updated for soft updates > > ffs_mountfs: superblock updated for soft updates > > > > Brian Feldman _ __ ___ ___ ___ > > green@unixhelp.org _ __ ___ | _ ) __| \ > > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 4:29:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from sand2.sentex.ca (sand2.sentex.ca [209.167.248.3]) by hub.freebsd.org (Postfix) with ESMTP id 07C4B14EB5 for ; Thu, 4 Mar 1999 04:29:41 -0800 (PST) (envelope-from mike@sentex.net) Received: from gravel (ospf-wat.sentex.net [209.167.248.81]) by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id HAA18607 for ; Thu, 4 Mar 1999 07:29:23 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.1.19990304073656.084804e0@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 04 Mar 1999 07:38:43 -0500 To: current@freebsd.org From: Mike Tancsa Subject: Simple DOS against 3.x locks box solid Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way to stop what is below ? As posted by yk@dgtu.donetsk.ua > >This script freeze my 3.1-RELEASE box. >I can't make any connection with my box, also from console. > >-------- cut here --- >#! /bin/sh > >for j in 1 2 3 4 5 6 7 8 9 10 >do >echo -n $j >nohup sh -c 'while :; do find / -type file |xargs fgrep fticom; done' >/dev/null 2>&1 & >echo >done >--------- cut here ---- > >-- >Yury V. Yaroshevsky | Donetsk State Technical University >YY18-RIPE | (380 622) 356455 yk@dgtu.donetsk.ua > ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 6: 5:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from osiris.kuniv.edu.kw (unknown [139.141.220.26]) by hub.freebsd.org (Postfix) with ESMTP id 8CB2814EEB for ; Thu, 4 Mar 1999 06:04:56 -0800 (PST) (envelope-from root@isis.dynip.com) Received: from localhost (root@localhost.kuniv.edu.kw [127.0.0.1]) by osiris.kuniv.edu.kw (8.9.3/8.9.1) with ESMTP id RAA12576 for ; Thu, 4 Mar 1999 17:04:33 +0300 (AST) (envelope-from root@isis.dynip.com) Date: Thu, 4 Mar 1999 17:04:27 +0300 (AST) From: Joss Roots Reply-To: root@isis.dynip.com To: freebsd-current@freebsd.org Subject: -Current /ports/sysutils/CD-Write HELP 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 thre I'm running -current (since about one month), and can't get cd-write to compile due to failure of the Tix port, anyone haas got the cd-write binary ? and will it run with out the Tix libraries installed. How are you people making CDs anyway. I just want to make my own cdrom for installations purposes, and to backup the 1.2 Gigs of /ports/distfiles. By the way any hint why the make release is broken at: can't cd to /ports/textproc/docproj If I set NODOCS, NOPORTS make release is ok, if not set, the ports will break at the above stage. Any help is highly appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 6:24:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.WorldMediaCo.com (unknown [207.252.121.17]) by hub.freebsd.org (Postfix) with ESMTP id 3821214C49 for ; Thu, 4 Mar 1999 06:24:27 -0800 (PST) (envelope-from opsys@omaha.com) Received: from freebsd.omaha.com ([207.252.122.220]) by mail1.WorldMediaCo.com (Post.Office MTA v3.5.3 release 223 ID# 0-55573U2500L250S0V35) with SMTP id com for ; Thu, 4 Mar 1999 08:16:06 -0600 Date: Thu, 4 Mar 1999 08:24:07 -0600 (CST) From: opsys@omaha.com (opsys) To: freebsd-current@freebsd.org Subject: My current box is borked. 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 A co-worker decided to "fix" my current machine yesterday. I had built a new kernel without building world yet and he was getting the usual ps, w, stuff not working with a proc size mismatch. I just hadnt built world yet. Well he decides to build /usr/src/lib and install them. Now everything is borked. Then he cp's /usr/src/share/mk to /usr/share/mk. This is all he says he did trying to fix the proc size mismatch stuff. I'm trying to build world but now to fix all this and I just get this: cc -O -pipe -I/usr/src/usr.bin/make -I/usr/obj/usr/src/tmp/usr/include -c /usr /src/usr.bin/make/arch.c arch.o: File truncateded {standard input}: Assembler messages: {standard input}:1280: FATAL: Can't write arch.o: File truncated *** Error code 1 I get that same error on everything I try compiling. Usually I can fix stuff but without the compiler I can't get anything rebuilt. Is there a way to fix this or do I just need to do a binary install of a current snap from the 1st and over write the current binaries and reboot/pray? -- The cow-orker has been shot. And all access revoked. Chris cwatson@worldmediaco.com opsys@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 Thu Mar 4 6:54:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from jfh00.fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by hub.freebsd.org (Postfix) with ESMTP id 4A08314FC1 for ; Thu, 4 Mar 1999 06:54:11 -0800 (PST) (envelope-from jfh@jfh00.fernuni-hagen.de) Received: (from jfh@localhost) by jfh00.fernuni-hagen.de (8.9.2/8.9.2) id PAA00422; Thu, 4 Mar 1999 15:53:53 +0100 (CET) (envelope-from jfh) To: current@FreeBSD.ORG Subject: Getting closer to use ATAPI-ZIP drives MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: Fritz Heinrichmeyer Date: 04 Mar 1999 15:53:53 +0100 Message-ID: <86lnhds3um.fsf@jfh00.fernuni-hagen.de> Lines: 36 User-Agent: Gnus/5.070079 (Pterodactyl Gnus v0.79) Emacs/20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now in the first time there happens something with my ZIP-Drive. Here something from dmesg: ata-pci0: rev 0x00 on pci0.7.1 ata0 at 0x01f0 irq 14 on ata-pci0 .. .. ata0: unwanted interrupt ata0: unwanted interrupt afd0: rewriteable drive at ata0 as master afd0: 96MB (196608 sectors), 32 cyls, 64 heads, 96 S/T, 512 B/S afd0: Unknown media (0x0) Here something from my config file: controller ata0 device atadisk0 # ATA disk drives device atapifd0 # my extrapolation! after trying to mount with mount_msdos /dev/wfd0s4 /mnt i get mountmsdosfs(): bad bpb is this a completely different problem (a msdosfs problem)? -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG Elektronische Schaltungen, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://ES-i2.fernuni-hagen.de/~jfh PGP fingerprint (mail for key): 160BDF84 3F2F63C0 5CA20D31 3E42D116 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 7: 3:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 9715914F30 for ; Thu, 4 Mar 1999 07:03:26 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10IZdz-00095x-00; Thu, 4 Mar 1999 17:02:35 +0200 From: Sheldon Hearn To: opsys@omaha.com (opsys) Cc: freebsd-current@freebsd.org Subject: Re: My current box is borked. In-reply-to: Your message of "Thu, 04 Mar 1999 08:24:07 CST." Date: Thu, 04 Mar 1999 17:02:35 +0200 Message-ID: <34964.920559755@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 04 Mar 1999 08:24:07 CST, opsys wrote: > cc -O -pipe -I/usr/src/usr.bin/make -I/usr/obj/usr/src/tmp/usr/include > -c /usr > /src/usr.bin/make/arch.c > arch.o: File truncateded > {standard input}: Assembler messages: > {standard input}:1280: FATAL: Can't write arch.o: File truncated > *** Error code 1 You sure you're starting your build off with a clean obj tree? Do this as root: cd /usr rm -rf obj chflags -R noschg obj rm -rf obj mkdir obj cd src make cleandir make cleandir The two ``make cleandir'' commands are deliberate. Then try your make world again. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 7: 9:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (Postfix) with ESMTP id 0378514FCA for ; Thu, 4 Mar 1999 07:09:46 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.3/8.9.3) id JAA04934; Thu, 4 Mar 1999 09:09:25 -0600 (CST) (envelope-from dick) Date: Thu, 4 Mar 1999 09:09:25 -0600 From: "Richard Seaman, Jr." To: "Russell L. Carter" Cc: current@FreeBSD.ORG Subject: SMP Threads (was: Re: SMP and SO5.0) Message-ID: <19990304090925.B441@tar.com> References: <199902171940.OAA69973@y.dyson.net> <199903040113.SAA17500@psf.Pinyon.ORG> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199903040113.SAA17500@psf.Pinyon.ORG>; from Russell L. Carter on Wed, Mar 03, 1999 at 06:13:43PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 03, 1999 at 06:13:43PM -0700, Russell L. Carter wrote: > > John Dyson extemporised: > > %Julian Elischer said: > %> > %> > %> On Tue, 16 Feb 1999, Luoqi Chen wrote: > %> > You may try my patch at http://www.freebsd.org/~luoqi, which would allow > %> > linux threads to run on SMP. > %> > %> I've gone through these patches and I can see that they are really needed > %> for SMP where address spaces are shared. > %> > %I agree -- a per-cpu page directory per multithreaded process is the way that > %I had implemented. Excellent!!! > % > > So I tried these out. The examples work in the linuxthreads dir but many > other things do not. For instance, > > Built debug ACE+TAO with egcs-2.91.62, March 2 -current, newest > LinuxThreads port. Uniprocessor has no errors. SMP fails, for instance: > > rcarter@mazatzal:~/ace/ACE_wrappers/tests [82] ./TSS_Test > TSS_Test in malloc(): warning: recursive call. > TSS_Test in malloc(): warning: recursive call. > Abort trap (core dumped) > rcarter@mazatzal:~/ace/ACE_wrappers/tests [83] gdb TSS_Test -core > TSS_Test.coreGDB is free software and you are welcome to distribute copies of > it > under certain conditions; type "show copying" to see the conditions. > There is absolutely no warranty for GDB; type "show warranty" for details. > GDB 4.16 (i386-unknown-freebsd), > Copyright 1996 Free Software Foundation, Inc... > Core was generated by `TSS_Test'. > Program terminated with signal 6, Abort trap. > Reading symbols from /home/rcarter/ace/ACE_wrappers/ace/libACE.so...done. > Reading symbols from /usr/local/lib/liblthread.so.0...done. > Reading symbols from /usr/lib/libm.so.2...done. > Reading symbols from /usr/lib/libc.so.3...done. > Reading symbols from /usr/libexec/ld-elf.so.1...done. > #0 0x18243bf4 in sched_yield () > (gdb) where > #0 0x18243bf4 in sched_yield () > #1 0x181eb051 in sched_yield () at sched.c:58 > #2 0x181eac79 in _spinlock (lck=0x18281738) at spinlock.c:88 > #3 0x18278a02 in free () > #4 0x181a8765 in __builtin_delete (ptr=0x8054170) > #5 0x804ada5 in worker (c=0x64) at TSS_Test.cpp:222 > #6 0x180fc4e2 in ACE_Thread_Adapter::invoke (this=0x8051540) at OS.cpp:2075 > #7 0x180fc556 in ace_thread_adapter (args=0x8051540) at OS.cpp:2194 > #8 0x181ebe8c in pthread_start_thread (arg=0xeb5ffd04) at manager.c:160 > #9 0x181ec49d in _clone () at clone.S:1 > #10 0xffffffff in ?? () > #11 0x1805ec5c in .curbrk () > Cannot access memory at address 0xf9dc. Comments (but no solution): 1) gdb is tricky to use with threads. What you see is not always where you are. It doesn't always follow the threads very well, if at all. 2) AFAIK, there are only two reasons you should ever see the "malloc(): warning: recursive call" message. One reason is that the libc global variable __isthreaded is not set. I don't think this is the case here, since the gdb trace seems to show _spinlock being called within free(). This would not happen if __isthreaded is not set. 3) The other reason for the warning is that malloc/free have been called recursively within the same thread. AFAIK, this can only happen if malloc/free are called within a signal handler (which is an error), and one of malloc/free is interrupted by a signal. Looking briefly at the ACE TSS_Test code, I suspect that the signal handler calls free(). 4) I'm not sure what the real problem is, whether it is a bad signal handler, or more likely, the real problem is whatever generated the signal within malloc/free, and the bad signal handler is a misdirect. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 7:44:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 4B88015055 for ; Thu, 4 Mar 1999 07:44:18 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10IaHs-00099T-00; Thu, 4 Mar 1999 17:43:48 +0200 From: Sheldon Hearn To: opsys@omaha.com (opsys) Cc: current@freebsd.org Subject: Re: My current box is borked. In-reply-to: Your message of "Thu, 04 Mar 1999 09:35:49 CST." Date: Thu, 04 Mar 1999 17:43:48 +0200 Message-ID: <35182.920562228@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 04 Mar 1999 09:35:49 CST, opsys wrote: > I still get the same error. [...] > Got any other ideas? Nope, but I've cc'd the list again so that others know your problem's not solved. You've tried updating your source tree and trying again, yes? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 8:41:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 11F591505C for ; Thu, 4 Mar 1999 08:41:21 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id JAA94741; Thu, 4 Mar 1999 09:40:17 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903041640.JAA94741@panzer.plutotech.com> Subject: Re: -Current /ports/sysutils/CD-Write HELP In-Reply-To: from Joss Roots at "Mar 4, 1999 5: 4:27 pm" To: root@isis.dynip.com Date: Thu, 4 Mar 1999 09:40:17 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Joss Roots wrote... > Hi thre > > I'm running -current (since about one month), and can't > get cd-write to compile due to failure of the Tix > port, anyone haas got the cd-write binary ? > > and will it run with out the Tix libraries installed. > > How are you people making CDs anyway. > I just want to make my own cdrom for installations > purposes, and to backup the 1.2 Gigs of > /ports/distfiles. > > By the way any hint why the make release is broken at: > > can't cd to /ports/textproc/docproj > > If I set NODOCS, NOPORTS make release is ok, if not > set, the ports will break at the above stage. > > Any help is highly appreciated. The officially supported way to burn CDs with 3.0 and newer versions of FreeBSD is cdrecord. /usr/ports/sysutils/cdrecord Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 9: 2:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5C25215064 for ; Thu, 4 Mar 1999 09:02:06 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id RAA37634; Thu, 4 Mar 1999 17:01:44 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA03727; Thu, 4 Mar 1999 10:01:39 -0700 (MST) Message-Id: <199903041701.KAA03727@harmony.village.org> To: Fritz Heinrichmeyer Subject: Re: Getting closer to use ATAPI-ZIP drives Cc: current@FreeBSD.ORG In-reply-to: Your message of "04 Mar 1999 15:53:53 +0100." <86lnhds3um.fsf@jfh00.fernuni-hagen.de> References: <86lnhds3um.fsf@jfh00.fernuni-hagen.de> Date: Thu, 04 Mar 1999 10:01:38 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <86lnhds3um.fsf@jfh00.fernuni-hagen.de> Fritz Heinrichmeyer writes: : mountmsdosfs(): bad bpb : is this a completely different problem (a msdosfs problem)? I've had to, in the past, slightly tweak the mount code for msdosfs to get stuff to mount. It would be interesting to see if this is a data corruption problem (in which case the diagnostic is good) or a slightly oddball dos disk. mtools might be useful in tracking things down. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 9:10:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id CBCE114FE4 for ; Thu, 4 Mar 1999 09:09:28 -0800 (PST) (envelope-from rock@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999020800) with ESMTP id SAA11421 for ; Thu, 4 Mar 1999 18:09:07 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999020800) with ESMTP id SAA13132 for ; Thu, 4 Mar 1999 18:09:07 +0100 (CET) Received: from vodix.aremorika (vodix [134.96.247.43]) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) with ESMTP id SAA20808 for ; Thu, 4 Mar 1999 18:09:06 +0100 (CET) From: "D. Rock" Received: by vodix.aremorika; Thu, 4 Mar 1999 18:09:05 +0100 (MET) Date: Thu, 4 Mar 1999 18:09:05 +0100 (MET) Message-Id: <199903041709.SAA01412@vodix.aremorika> To: current@freebsd.org Subject: New ata driver gets intr statistics wrong Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Interrupts don't get accounted right. Instead of adding them to irq14/irq15 they always seem to be added to irq0. Here is a sample output of systat (I have "options HZ=1000" in my kernel config, so 1000 should be normal) 3 users Load 1.21 1.05 1.01 Do 4 Mär 02:04 Mem:KB REAL VIRTUAL VN PAGER SWAP PAGER Tot Share Tot Share Free in out in out Act 10308 2060 20764 3856 8408 count 5 All 58796 2792 1127196 5784 pages 31 688 zfod Interrupts Proc:r p d s w Csw Trp Sys Int Sof Flt 195 cow 1333 total 1 4 11 459 973 5233 1333 252 920 23068 wire 1125 clk0 irq0 13528 act 128 rtc0 irq8 24.5%Sys 1.6%Intr 46.7%User 0.0%Nice 27.3%Idl 16524 inact pci irq11 | | | | | | | | | | 5456 cache 24 pci irq15 ============+>>>>>>>>>>>>>>>>>>>>>>> 2952 free pci irq9 daefr fdc0 irq6 Namei Name-cache Dir-cache prcfr 24 atkbd0 irq Calls hits % hits % 2 react 32 psm0 irq12 8739 8440 97 31 0 pdwak sio0 irq4 pdpgs sio1 irq3 Discs ad0 da0 da1 da2 cd0 fd0 pass0 intrn ppc0 irq7 KB/t 8.09 0.00 9.29 0.00 0.00 0.00 0.00 5518 buf isic0 irq1 tps 124 0 23 0 0 0 0 4039 desir esb0 irq5 MB/s 0.98 0.00 0.21 0.00 0.00 0.00 0.00 11444 numvnodes 7994 freevnodes During probe I also noticed this message: ata-pci0: rev 0xc1 int a irq 0 on pci0.15.0 ^^^^^ ata0 at 0x01f0 irq 14 on ata-pci0 On another machine with VIA chipset I don't see any "int a irq X", but the interrupts get still accounted for irq0 instead of irq14 This isn't a big deal for me, PCMCIA interrupts do have the same problem. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 9:22:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.nerds4rent.com (ns2.freedomnet.com [198.240.104.10]) by hub.freebsd.org (Postfix) with ESMTP id 32F1015097 for ; Thu, 4 Mar 1999 09:22:28 -0800 (PST) (envelope-from kbyanc@freedomnet.com) Received: from tech (tech.nerds4rent.com [198.240.104.20]) by mail.nerds4rent.com (8.8.8/8.8.8/antispam) with SMTP id MAA16933 for ; Thu, 4 Mar 1999 12:37:06 -0500 (EST) X-Envelope-To: From: "Kelly Yancey" To: Subject: RE: ATAPI and ATAPI_STATIC with the new ATA* driver? Date: Thu, 4 Mar 1999 12:23:29 -0500 Message-ID: <000001be6663$b897bca0$1468f0c6@tech.freedomnet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It's really frustrating if I add new drive (anywhere on the busses) and > > other drives change their numbers - it's good base for big troubles > > (infinite changing /etc/fstab and so on). > Fair enough. But in real life, you don't add a new drive "anywhere on > the busses". You know _exactly_ which controller you're attaching the > drive to, and you know whether the drive is the master or the slave. > This information is enough for you to figure out _exactly_ where in the > probing the drive will be "spotted" and numbered. > I'm not sure I understand what real-world frustrations people are having > here. Is this thread the product of reactionary criticism, or are there > real examples of situations in which there are serious disadvantages to > the way Soren has things working? > Ciao, > Sheldon. I think you are absolutely right. On all of our servers here, all running various versions of FreeBSD, we've been using SCSI drives for years, which as we all know have the same "problem" that ATA drives have now. The only difference is that with SCSI devices, a mechanism exists to wire-down device names to devices. The only real problem that exists with the new ATA driver is that it doesn't support the same wiring-down for ATA devices. I don't remember who suggested it a couple of days ago, but I thought it was a good idea: to simply extend the wiring-down scheme that we already have to support ATA devices too. He also suggested a more universal device name like drv0, drv1, drv2, etc rather than deliniating between whether the drive is ATA or SCSI...I also think that is a good idea as I don't see any good reason an application should care whether the drive is ATA or SCSI, as long as the functionality is provided does it matter how? Great job Soren, the new drivers are great (although DMA support would make them extra cool :) ) Kelly ~kbyanc@posi.net~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 9:39:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 248F8150EF for ; Thu, 4 Mar 1999 09:39:25 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 4716 invoked by uid 1001); 4 Mar 1999 17:39:04 +0000 (GMT) To: kbyanc@freedomnet.com Cc: current@FreeBSD.ORG Subject: RE: ATAPI and ATAPI_STATIC with the new ATA* driver? From: sthaug@nethelp.no In-Reply-To: Your message of "Thu, 4 Mar 1999 12:23:29 -0500" References: <000001be6663$b897bca0$1468f0c6@tech.freedomnet.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 04 Mar 1999 18:39:03 +0100 Message-ID: <4714.920569143@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't remember who suggested it a couple of days ago, but I thought it > was a good idea: to simply extend the wiring-down scheme that we already > have to support ATA devices too. He also suggested a more universal device > name like drv0, drv1, drv2, etc rather than deliniating between whether the > drive is ATA or SCSI...I also think that is a good idea as I don't see any > good reason an application should care whether the drive is ATA or SCSI, as > long as the functionality is provided does it matter how? Agreed. I had always assumed that this was part of the reason for the name change sd -> da, namely that da would (eventually) cover ATA disks also. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 9:47:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from interjet.reinelinjer.no (4pogc-gw.online.no [194.248.199.142]) by hub.freebsd.org (Postfix) with ESMTP id 85B8D150AD for ; Thu, 4 Mar 1999 09:47:07 -0800 (PST) (envelope-from erik@habatech.no) Received: (from daemon@localhost) by interjet.reinelinjer.no (8.8.5/8.8.5) id GAA17797 for ; Thu, 4 Mar 1999 06:41:43 +0100 (CET) Received: from UNKNOWN(62.92.133.2), claiming to be "haba.reinelinjer.no" via SMTP by interjet.reinelinjer.no, id smtpdP17795; Thu Mar 4 05:41:36 1999 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-10 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Date: Thu, 04 Mar 1999 18:43:34 +0100 (CET) Organization: Habatech AS From: "Erik H. Bakke" To: current@freebsd.org Subject: Tape problems with new ATAPI driver Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After switching to the new ATAPI drivers my system locks up every time I try to do a backup, only the mouse seems to be in action (So it seems that things are not quite lost... :) This did not happen before the switch. Anyone else experiencing this? *** Relevant parts of my dmesg output *** CPU: AMD-K6(tm) 3D processor (333.39-MHz 586-class CPU) real memory =3D 134217728 (131072K bytes) avail memory =3D 128045056 (125044K bytes) ata-pci0: rev 0x06 on pci0.7.1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ad0: ATA-? disk at ata0 as master ad0: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S ad0: 8 secs/int, 0 depth queue=20 ad1: ATA-4 disk at ata1 as master ad1: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue=20 ast0: tape drive at ata0 as slave=20 ast0: Travan 4 (4 Gbyte) media, reverse, qfa, ecc, 512b ast0: Max speed=3D600Kb/s, Transfer limit=3D52 blocks, Buffer size=3D728 bl= ocks changing root device to ad0s1a *** Relevant parts of my config file *** controller ata0 device atadisk0 device atapicd0 device atapist0 device atapifd0 options ATAPI options ATAPI_STATIC -- Erik H. Bakke | To be or not to be | CGI, konsulenttjenester, Habatech AS | is simply a question | hardware, software, erik@habatech.no | about binary logic | l=F8sninger. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 10: 5: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id BF23B150C0 for ; Thu, 4 Mar 1999 10:04:20 -0800 (PST) (envelope-from tim@scratch.demon.co.uk) Received: from [212.228.22.156] (helo=franklin.matlink) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 10IcTZ-000Q0Q-00 for freebsd-current@freebsd.org; Thu, 4 Mar 1999 18:04:01 +0000 Received: (from tim@localhost) by franklin.matlink (8.9.3/8.9.3) id WAA98152 for freebsd-current@freebsd.org; Tue, 2 Mar 1999 22:54:28 GMT (envelope-from tim) Message-Id: <199903022254.WAA98152@franklin.matlink> Date: Tue, 2 Mar 1999 22:54:06 +0000 (GMT) From: tim@scratch.demon.co.uk Subject: vinum To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Help.. ======= vinum - is this volume management such like vold in solaris ? am I correct in assuming that the initial boot device cannot be a part of a vinum volume ? If this is the case then I would need my vinum information on the initial disk, and can move information from one disk to another, create a vinum disk and move the information back again ? Is it advantageous to be running vinum ? Is there any documentation other than the manpages on this, i.e html. ? Thanks for the help Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 11:10:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 9E0D915077 for ; Thu, 4 Mar 1999 11:10:28 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id NAA00423; Thu, 4 Mar 1999 13:10:10 -0600 (CST) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id NAA34559; Thu, 4 Mar 1999 13:10:10 -0600 (CST) Date: Thu, 4 Mar 1999 13:10:10 -0600 From: Alan Cox To: John Capo Cc: current@freebsd.org Subject: Re: SMP users please read Message-ID: <19990304131010.A34495@nonpc.cs.rice.edu> References: <19990304010923.A33835@nonpc.cs.rice.edu> <19990304134649.01830@irbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990304134649.01830@irbs.com>; from John Capo on Thu, Mar 04, 1999 at 01:46:49PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 04, 1999 at 01:46:49PM -0500, John Capo wrote: > Is this valid for 3.1 or just -current? > Yes. The same bug exists in 3.1. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 12:53:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (Postfix) with ESMTP id A1B0F14F32 for ; Thu, 4 Mar 1999 12:53:09 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m10If6n-000I5qC; Thu, 4 Mar 1999 15:52:41 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: 3COM 3c509 (ep driver) To: current@freebsd.org Date: Thu, 4 Mar 1999 15:52:41 -0500 (EST) Cc: tom@tomqnx.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM920580761-851-0_ Content-Transfer-Encoding: 7bit Content-Length: 3928 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM920580761-851-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit According to the dmesg output attached, there is a problem with this driver. In practise, it does seem to work. This is a test kernel compiled for me by Matt Jacob. Cheers, Tom --ELM920580761-851-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=dmesg Content-Description: dmesg Content-Transfer-Encoding: 7bit Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Mar 2 09:16:31 PST 1999 mjacob@quarm.feral.com:/usr/src/sys/compile/DARKSTAR Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 200455564 Hz CPU: Pentium/P55C (200.46-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x544 Stepping=4 Features=0x8001bf real memory = 67108864 (65536K bytes) avail memory = 62701568 (61232K bytes) Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x01 on pci0.1.0 ide_pci0: rev 0x01 on pci0.1.1 chip2: rev 0x01 on pci0.1.3 ncr0: rev 0x03 int a irq 9 on pci0.10.0 vga0: rev 0x01 int a irq 11 on pci0.11.0 Probing for PnP devices: CSN 1 Vendor ID: CTL00c1 [0xc1008c0e] Serial 0x1641e094 Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp sn 0x1641e094) at 0x220-0x22f irq 10 drq 3 flags 0x15 on isa Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> pcm0 not probed due to drq conflict with pcm1 at 3 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A ppc0 at 0x378 irq 7 on isa ppc0: W83877AF chipset (NIBBLE-only) in COMPATIBLE mode ppb0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: PRINTER BJ,LQ,BJL,BJRaster,BSCC plip0: on ppbus 0 ppi0: on ppbus 0 lppps0: on ppbus 0 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 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 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0x80ff80ff on isa wdc1: unit 0 (atapi): , removable, intr, iordy acd0: drive speed 689KB/sec, 256KB cache acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked 1 3C5x9 board(s) on ISA found at 0x210 ep0 at 0x210-0x21f irq 5 on isa ep0: aui/bnc[*BNC*] address 00:60:8c:62:a5:65 npx0 on motherboard npx0: INT 16 interface vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa Intel Pentium detected, installing workaround for F00F bug ep0 XXX: driver didn't set ifq_maxlen Waiting 15 seconds for SCSI devices to settle sa0 at ncr0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) changing root device to da0s2a cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [253970 x 2048 byte records] WARNING: / was not properly dismounted --ELM920580761-851-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 13:53:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id A7CC014D88 for ; Thu, 4 Mar 1999 13:52:55 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.8.8) with ESMTP id VAA34494; Thu, 4 Mar 1999 21:40:10 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA01097; Thu, 4 Mar 1999 21:39:45 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199903042139.VAA01097@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Leif Neland Cc: Brian Somers , current@FreeBSD.ORG Subject: Re: PPP (userland) troubles ? In-reply-to: Your message of "Fri, 29 Jan 1999 00:16:39 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Mar 1999 21:39:45 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Would it be possible to add an exponential delay when connecting fails for > either reason? > > I just received my specified phone-bill. It filled 42 pages, with hundreds > of calls with a duration of 17 seconds. (Because my modem needs to be > software-reset; I have mentioned this before). > > Each call costs a few cents; I'm billed both for each connect, and for > connect time. It all adds up. And I'm connected to the other modem, even > if the handshake doesn't work. Hi, Ppp now can now do an incremental redial timeout. Check the ``set redial'' command description in the man page in -current or from http://www.Awfulhak.org/ppp.html. > Leif -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 13:53:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from holly.dyndns.org (ip152.houston13.tx.pub-ip.psi.net [38.27.213.152]) by hub.freebsd.org (Postfix) with ESMTP id 7C05114F2A for ; Thu, 4 Mar 1999 13:53:21 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id PAA05778; Thu, 4 Mar 1999 15:54:02 -0600 (CST) (envelope-from chris) Date: Thu, 4 Mar 1999 15:54:01 -0600 From: Chris Costello To: Mike Tancsa Cc: current@FreeBSD.ORG Subject: Re: Simple DOS against 3.x locks box solid Message-ID: <19990304155401.A5710@holly.dyndns.org> Reply-To: chris@calldei.com References: <4.1.19990304073656.084804e0@granite.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3us In-Reply-To: <4.1.19990304073656.084804e0@granite.sentex.ca>; from Mike Tancsa on Thu, Mar 04, 1999 at 07:38:43AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 4, 1999, Mike Tancsa put this into my mailbox: > > Is there any way to stop what is below ? Yep. Don't do it! Seriously, though, that puts a major load on the system. You have 10 process all telling the drivers to keep seeking about through the disks. Add /etc/login.conf restrictions if you don't want your users to do that. > > > > As posted by yk@dgtu.donetsk.ua > > > >This script freeze my 3.1-RELEASE box. > >I can't make any connection with my box, also from console. > > > >-------- cut here --- > >#! /bin/sh > > > >for j in 1 2 3 4 5 6 7 8 9 10 > >do > >echo -n $j > >nohup sh -c 'while :; do find / -type file |xargs fgrep fticom; done' > >/dev/null 2>&1 & > >echo > >done > >--------- cut here ---- > > > >-- > >Yury V. Yaroshevsky | Donetsk State Technical University > >YY18-RIPE | (380 622) 356455 yk@dgtu.donetsk.ua > > > ********************************************************************** > Mike Tancsa, Network Admin * mike@sentex.net > Sentex Communications Corp, * http://www.sentex.net/mike > Cambridge, Ontario * 01.519.651.3400 > Canada * > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Powered by FreeBSD 4.0-CURRENT. "The Power to Serve!" int main(int m){main(!main(0));} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 16:22:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 5DE66150C0 for ; Thu, 4 Mar 1999 16:22:38 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA32802; Thu, 4 Mar 1999 16:22:19 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Mar 1999 16:22:19 -0800 (PST) From: Matthew Dillon Message-Id: <199903050022.QAA32802@apollo.backplane.com> To: Chris Costello Cc: Mike Tancsa , current@FreeBSD.ORG Subject: Re: Simple DOS against 3.x locks box solid References: <4.1.19990304073656.084804e0@granite.sentex.ca> <19990304155401.A5710@holly.dyndns.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, 10 processes doing a find are not supposed to lockup a machine. However, there is another potential problem with the script below ... if the script is run as root, the find will cross mount points including the /proc mount point. Now running xargs and random process's memory spaces *could* certainly lockup a machine. /proc does has reentrancy issue with multiple processes accessing it at the same time. Try changing the 'find' to 'find -x'. If this still locks up the machine we will have to then determine whether it occurs under 4.x as well, or if it only occurs under 3.x. -Matt Matthew Dillon :On Thu, Mar 4, 1999, Mike Tancsa put this into my mailbox: :> :> Is there any way to stop what is below ? : : Yep. Don't do it! : : Seriously, though, that puts a major load on the system. : : You have 10 process all telling the drivers to keep seeking :about through the disks. : : Add /etc/login.conf restrictions if you don't want your users :to do that. : :> :> :> :> As posted by yk@dgtu.donetsk.ua :> > :> >This script freeze my 3.1-RELEASE box. :> >I can't make any connection with my box, also from console. :> > :> >-------- cut here --- :> >#! /bin/sh :> > :> >for j in 1 2 3 4 5 6 7 8 9 10 :> >do :> >echo -n $j :> >nohup sh -c 'while :; do find / -type file |xargs fgrep fticom; done' :> >/dev/null 2>&1 & :> >echo :> >done :> >--------- cut here ---- :> > :> >-- :> >Yury V. Yaroshevsky | Donetsk State Technical University :> >YY18-RIPE | (380 622) 356455 yk@dgtu.donetsk.ua :> > :> ********************************************************************** :> Mike Tancsa, Network Admin * mike@sentex.net :> Sentex Communications Corp, * http://www.sentex.net/mike :> Cambridge, Ontario * 01.519.651.3400 :> Canada * :> :> :> To Unsubscribe: send mail to majordomo@FreeBSD.org :> with "unsubscribe freebsd-current" in the body of the message :> : :-- :Powered by FreeBSD 4.0-CURRENT. "The Power to Serve!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 16:26:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-44.ppp.wenet.net [206.15.85.44]) by hub.freebsd.org (Postfix) with ESMTP id 60B2B150CF for ; Thu, 4 Mar 1999 16:25:38 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.2/8.9.1) with ESMTP id QAA01979; Thu, 4 Mar 1999 16:24:57 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Thu, 4 Mar 1999 16:24:57 -0800 (PST) From: Alex Zepeda To: Warner Losh Cc: Fritz Heinrichmeyer , current@FreeBSD.ORG Subject: Re: Getting closer to use ATAPI-ZIP drives In-Reply-To: <199903041701.KAA03727@harmony.village.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 Thu, 4 Mar 1999, Warner Losh wrote: > I've had to, in the past, slightly tweak the mount code for msdosfs to > get stuff to mount. It would be interesting to see if this is a data > corruption problem (in which case the diagnostic is good) or a > slightly oddball dos disk. mtools might be useful in tracking things > down. I'd say this is a deficiency with the msdosfs code. I've created some "partitions" with bochs (installed Win95 OSR2.. disk image was like 500mb.. not fat32), and after I vnconfig'd it, I could not mount -t msdos it because of the same error (bad bpb). Win95 sure grok'd it. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 16:35:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 639D7150B9 for ; Thu, 4 Mar 1999 16:35:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA33521; Thu, 4 Mar 1999 16:35:14 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Mar 1999 16:35:14 -0800 (PST) From: Matthew Dillon Message-Id: <199903050035.QAA33521@apollo.backplane.com> To: Chris Costello , Mike Tancsa , current@FreeBSD.ORG Subject: Re: Simple DOS against 3.x locks box solid References: <4.1.19990304073656.084804e0@granite.sentex.ca> <19990304155401.A5710@holly.dyndns.org> <199903050022.QAA32802@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, this was easy to duplicate. I'll try to track it down. It seems to occur under -4.x as well as -3.x. Definitely an inode deadlock of some kind. -Matt : Try changing the 'find' to 'find -x'. If this still locks up the machine : we will have to then determine whether it occurs under 4.x as well, or : if it only occurs under 3.x. : -Matt : ::> As posted by yk@dgtu.donetsk.ua ::> > ::> >This script freeze my 3.1-RELEASE box. ::> >I can't make any connection with my box, also from console. ::> > ::> >-------- cut here --- ::> >#! /bin/sh ::> > ::> >for j in 1 2 3 4 5 6 7 8 9 10 ::> >do ::> >echo -n $j ::> >nohup sh -c 'while :; do find / -type file |xargs fgrep fticom; done' ::> >/dev/null 2>&1 & ::> >echo ::> >done ::> >--------- cut here ---- ::> > ::> >-- ::> >Yury V. Yaroshevsky | Donetsk State Technical University ::> >YY18-RIPE | (380 622) 356455 yk@dgtu.donetsk.ua To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 17:32:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from sand2.sentex.ca (sand2.sentex.ca [209.167.248.3]) by hub.freebsd.org (Postfix) with ESMTP id F0A0F150F8 for ; Thu, 4 Mar 1999 17:31:16 -0800 (PST) (envelope-from mike@sentex.net) Received: from gravel (ospf-wat.sentex.net [209.167.248.81]) by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id UAA08535; Thu, 4 Mar 1999 20:30:55 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.1.19990304193540.08483b10@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 04 Mar 1999 20:40:20 -0500 To: Matthew Dillon , Chris Costello From: Mike Tancsa Subject: Re: Simple DOS against 3.x locks box solid Cc: current@FreeBSD.ORG In-Reply-To: <199903050022.QAA32802@apollo.backplane.com> References: <4.1.19990304073656.084804e0@granite.sentex.ca> <19990304155401.A5710@holly.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 07:22 PM 3/4/99 , Matthew Dillon wrote: > Well, 10 processes doing a find are not supposed to lockup a machine. > > However, there is another potential problem with the script below ... if > the script is run as root, the find will cross mount points including > the /proc mount point. Now running xargs and random process's memory > spaces *could* certainly lockup a machine. /proc does has reentrancy > issue with multiple processes accessing it at the same time. > > Try changing the 'find' to 'find -x'. If this still locks up the machine > we will have to then determine whether it occurs under 4.x as well, or > if it only occurs under 3.x. Interesting... I thought there was something else going on, because when I walk back to the machine, the drive is not even spinning. I will have to wait until I go to the office to try it, as I need to physically reboot the unit if it 'works'... If it is the /proc issue, what would be the safest way to proctect against it ? Also, it does not take many iterations to lock up the machine. Three will do it. To limit that via login.access would hose most users. ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 18:24:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 128C715074 for ; Thu, 4 Mar 1999 18:24:33 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA35868; Thu, 4 Mar 1999 18:24:13 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Mar 1999 18:24:13 -0800 (PST) From: Matthew Dillon Message-Id: <199903050224.SAA35868@apollo.backplane.com> To: Mike Tancsa Cc: Chris Costello , current@FreeBSD.ORG Subject: Re: Simple DOS against 3.x locks box solid References: <4.1.19990304073656.084804e0@granite.sentex.ca> <19990304155401.A5710@holly.dyndns.org> <4.1.19990304193540.08483b10@granite.sentex.ca> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem is a deadlock caused by the fgrep. The fgrep is mmap()ing the file, but then it does some really weird crap when dealing with larger files. It's the most idiotic code I've ever seen. The code uses a PRIVATE+RW mmap() until it gets to odd point in the file, at which point it read()'s additional information from the file into the mapped space ( that might contain a previous mmap'd portion of the file ). So what happens is this: * read() call * shared lock obtained on vnode ( some other process attempts to get shared lock on vnode and succeeds... for example, a namei operation is attempted by another grep ) * access MMAP'd area * exclusive lock attempt obtained on same vnode. This blocks because some other process has a shared lock on the vnode. ( the other process then attempts to get an exclusive lock on the vnode this blocks. Deadlock. Even worse, the gnu grep does not bother munmap()'ing the space so, in fact, the deadlock can occur between two unrelated files as well as with the same file. This is the more likely deadlock scenario. The solution is more difficult. We could hack an exception for PRIVATE mmap's... there really is no need for the vm_fault code to lock the vnode. Howver, other situations can occur where this hack would not work. This is 'kinda a known problem' in FreeBSD. We really need to find a solution to it. Other similar deadlocks can occur if you mmap() one file and read() or write() data from it to another file, and vise versa at the same time. Personally, I think the only real solution is to make vn_read() and vn_write() lock the uio space as well as the vnode being read or written. It would have to do it in the right order, and it would have to deal with the situation where the uio space covers multiple vnodes. Alternately, vnodes need to be redesigned without these fraggin all-encompassing locks for data R+W ops. -Matt (kgdb) back #0 mi_switch () at ../../kern/kern_synch.c:827 #1 0xf0151919 in tsleep (ident=0xf0a2e500, priority=0x8, wmesg=0xf0263a9c "inode", timo=0x0) at ../../kern/kern_synch.c:443 #2 0xf014b774 in acquire (lkp=0xf0a2e500, extflags=0x1000040, wanted=0x700) at ../../kern/kern_lock.c:145 #3 0xf014b835 in lockmgr (lkp=0xf0a2e500, flags=0x1030041, interlkp=0xf51719b0, p=0xf5151200) at ../../kern/kern_lock.c:209 #4 0xf0171df0 in vop_stdlock (ap=0xf5176b94) at ../../kern/vfs_default.c:210 #5 0xf0204b39 in ufs_vnoperate (ap=0xf5176b94) at ../../ufs/ufs/ufs_vnops.c:2309 #6 0xf017aba4 in vn_lock (vp=0xf5171940, flags=0x1030041, p=0xf5151200) at vnode_if.h:811 #7 0xf01747b0 in vget (vp=0xf5171940, flags=0x1020041, p=0xf5151200) at ../../kern/vfs_subr.c:1348 #8 0xf0212f1e in vnode_pager_lock (object=0xf02af2b4) at ../../vm/vnode_pager.c:960 #9 0xf0206a56 in vm_fault (map=0xf51497c0, vaddr=0x805d000, fault_type=0x3, fault_flags=0x8) at ../../vm/vm_fault.c:243 #10 0xf022aebe in trap_pfault (frame=0xf5176d14, usermode=0x0, eva=0x805d038) at ../../i386/i386/trap.c:816 #11 0xf022ab92 in trap (frame={tf_es = 0x10, tf_ds = 0x10, tf_edi = 0x805d000, tf_esi = 0xf223e000, tf_ebp = 0xf5176e0c, tf_isp = 0xf5176d3c, tf_ebx = 0x1060, tf_edx = 0x0, tf_ecx = 0x700, tf_eax = 0x0, tf_trapno = 0xc, tf_err = 0x3, tf_eip = 0xf0229ce4, tf_cs = 0x8, tf_eflags = 0x10287, tf_esp = 0xffff1272, tf_ss = 0xffff0000}) at ../../i386/i386/trap.c:437 #12 0xf0229ce4 in fastmove_loop () #13 0xf0229b2b in i586_copyout () #14 0xf01fd707 in ffs_read (ap=0xf5176ef0) at ../../ufs/ufs/ufs_readwrite.c:289 #15 0xf017a689 in vn_read (fp=0xf09dda80, uio=0xf5176f38, cred=0xf09ef480) at vnode_if.h:303 #16 0xf015a757 in read (p=0xf5151200, uap=0xf5176f94) at ../../kern/sys_generic.c:121 #17 0xf022b4a0 in syscall (frame={tf_es = 0x2f, tf_ds = 0x2f, tf_edi = 0x0, tf_esi = 0x8000, tf_ebp = 0xefbf85c8, tf_isp = 0xf5176fe4, tf_ebx = 0xffffffff, tf_edx = 0x8059000, tf_ecx = 0xa0000, tf_eax = 0x3, tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0x280b303c, tf_cs = 0x1f, tf_eflags = 0x206, tf_esp = 0xefbf85a0, tf_ss = 0x2f}) at ../../i386/i386/trap.c:1100 #18 0xf0220dcc in Xint0x80_syscall () #19 0x804dc46 in ?? () #20 0x804e85c in ?? () #21 0x8048f7d in ?? () (kgdb) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 19:25:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 3058614C4A for ; Thu, 4 Mar 1999 19:25:34 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40405>; Fri, 5 Mar 1999 14:13:37 +1100 Date: Fri, 5 Mar 1999 14:25:08 +1100 From: Peter Jeremy Subject: Re: Simple DOS against 3.x locks box solid To: dillon@apollo.backplane.com Cc: current@FreeBSD.ORG Message-Id: <99Mar5.141337est.40405@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > The problem is a deadlock caused by the fgrep. The fgrep is mmap()ing > the file, but then it does some really weird crap when dealing with > larger files. ... > The solution is more difficult. We could hack an exception for PRIVATE > mmap's... there really is no need for the vm_fault code to lock the vnode. > Howver, other situations can occur where this hack would not work. Another interim solution would be to `fix' GNU grep so it doesn't attempt to read() into mmap()'d space. (Having not looked at the code, I don't know how difficult this would be). As for the general problem, is it sensible to allow a read-only file to be mmap'd R/W (with or without MAP_PRIVATE) and then written into? It would be fairly easy to make mmap() return EACCES if the fd was not open for writing (or map the memory R/O and SEGV on a write). I would personally prefer to see a process die with an mmap failure (or SIGSEGV), rather than cause a deadlock - ie even if we do want/ need to support R/W mmap() on R/O files [and I can see some possible use for this], it would be worthwhile restricting mmap() in the short-term - and removing the restriction once the underlying problem is solved. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 19:45: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D111C15074 for ; Thu, 4 Mar 1999 19:44:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA37181; Thu, 4 Mar 1999 19:43:40 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Mar 1999 19:43:40 -0800 (PST) From: Matthew Dillon Message-Id: <199903050343.TAA37181@apollo.backplane.com> To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: Simple DOS against 3.x locks box solid References: <99Mar5.141337est.40405@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Another interim solution would be to `fix' GNU grep so it doesn't :attempt to read() into mmap()'d space. (Having not looked at the :code, I don't know how difficult this would be). : :As for the general problem, is it sensible to allow a read-only file to :be mmap'd R/W (with or without MAP_PRIVATE) and then written into? It :would be fairly easy to make mmap() return EACCES if the fd was not :open for writing (or map the memory R/O and SEGV on a write). : :I would personally prefer to see a process die with an mmap failure :(or SIGSEGV), rather than cause a deadlock - ie even if we do want/ :... We really need to fix the kernel, I think. This sort of deadlock situation has been a problem for too long and it is only going to get worse as more programs use mmap(). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 20:35:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id EA5CF14C28 for ; Thu, 4 Mar 1999 20:35:02 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id WAA02492 for ; Thu, 4 Mar 1999 22:34:44 -0600 (CST) Date: Thu, 4 Mar 1999 22:34:44 -0600 (CST) From: Steve Price To: current@freebsd.org Subject: Using Soren's new ATA driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What are the steps one needs to take in order to help test Soren's new ATA driver? I tweaked the MAKEDEV script to create /dev/ad0* and added the lines to my kernel config file as suggested in Soren's commit message. Both my HD and CD are found but when it goes to set the root device I get this: ... changing root device to ad0s1a ad0s2: cannot find label (no disk label) ad0s3: cannot find label (no disk label) ad0s4: cannot find label (no disk label) /: bad dir ino 2 at offset 0: mangled entry panic: ufs_dirbad: bad dir The obvious answer would be to edit the label for each of these slices to change the wd0* disk entries (which do exist) to say ad0* instead, but is that what I really need to do? Or did I miss a step? Sorry for being so dense, but this change should most definitely make it into src/UPDATING along with the list of required steps. I have to say though it was a glorious feeling to see the probe for my CD not take its usual 20+ seconds. :) Thanks, Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 22:24:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id 650C3150AE for ; Thu, 4 Mar 1999 22:24:29 -0800 (PST) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id BAA00398; Fri, 5 Mar 1999 01:49:44 -0500 (EST) (envelope-from dervish) Date: Fri, 5 Mar 1999 01:49:44 -0500 From: Natty Rebel To: Steve Price Cc: current@freebsd.org Subject: Re: Using Soren's new ATA driver Message-ID: <19990305014944.A358@ikhala.tcimet.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Steve Price on Thu, Mar 04, 1999 at 10:34:44PM -0600 X-Operating-System: FreeBSD 4.0-CURRENT i386 X-PGP-Fingerprint: 2C CE A5 D7 FA 4D D5 FD 9A CC 2B 23 04 46 48 F8 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Steve Price (sprice@hiwaay.net): > What are the steps one needs to take in order to help test > Soren's new ATA driver? I tweaked the MAKEDEV script to create > /dev/ad0* and added the lines to my kernel config file as > suggested in Soren's commit message. Both my HD and CD are > found but when it goes to set the root device I get this: > > ... > changing root device to ad0s1a > ad0s2: cannot find label (no disk label) > ad0s3: cannot find label (no disk label) > ad0s4: cannot find label (no disk label) > /: bad dir ino 2 at offset 0: mangled entry > panic: ufs_dirbad: bad dir > > The obvious answer would be to edit the label for each of > these slices to change the wd0* disk entries (which do exist) > to say ad0* instead, but is that what I really need to do? I don't think you need to do this just yet ... :) > Or did I miss a step? Back out your changes to MAKEDEV. The new driver understands the wd0* entries ... > > Sorry for being so dense, but this change should most > definitely make it into src/UPDATING along with the list of > required steps. > > I have to say though it was a glorious feeling to see the > probe for my CD not take its usual 20+ seconds. :) > > Thanks, Steve > > > #;^) -- natty rebel harder than the rest ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 22:41: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from mnw.eas.slu.edu (mnw.eas.slu.edu [165.134.8.248]) by hub.freebsd.org (Postfix) with ESMTP id 4C3851509D for ; Thu, 4 Mar 1999 22:40:57 -0800 (PST) (envelope-from ejh@mnw.eas.slu.edu) Received: (from ejh@localhost) by mnw.eas.slu.edu (8.8.8/8.8.8) id AAA18355; Fri, 5 Mar 1999 00:40:39 -0600 (CST) Date: Fri, 5 Mar 1999 00:40:39 -0600 (CST) From: Eric Haug Message-Id: <199903050640.AAA18355@mnw.eas.slu.edu> To: sprice@hiwaay.net Subject: Re: Using Soren's new ATA driver Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I am also seeing this same problem. With ATA_DEBUG and AD_DEBUG I see that blocks 127 and 2127 are read successfully and then the panic. eric haug Saint Louis Univ. > ad0s4: cannot find label (no disk label) > /: bad dir ino 2 at offset 0: mangled entry > panic: ufs_dirbad: bad dir > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 23: 8:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 8D7B2150F3 for ; Thu, 4 Mar 1999 23:06:50 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA38141; Thu, 4 Mar 1999 23:06:28 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Mar 1999 23:06:28 -0800 (PST) From: Matthew Dillon Message-Id: <199903050706.XAA38141@apollo.backplane.com> To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: Simple DOS against 3.x locks box solid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi Matt, : :You wrote: :> We really need to fix the kernel, I think. This sort of deadlock :> situation has been a problem for too long and it is only going to :> get worse as more programs use mmap(). : :I agree. Since you suggest that the kernel fix is going to be a :while, I was suggesting an interim fix which would make processes :die (unnecessarily) rather than deadlock the system. : :Peter I don't think killing processes is a good idea. I have an interim solution that will work for the situation that grep creates. The precise deadlock situation that grep creates is actually due to a pending exclusive lock blocking additional shared locks from occuring on a vnode that is already shared-locked. Grep does a combination mmap()/read(). The deadlock was occuring due to an open() waiting to get an exclusive lock and preventing a vm_fault() within a read() from being able to obtain a second shared lock reference. vm_fault() always obtain shared locks. read() syscalls obtain shared locks. write() syscalls obtain exclusiuve locks. open() syscalls obtain exclusive locks. There are still deadlock situations possible, especially in combinations that use write(), but this tentitive patch should get many of the more common deadlocks. *** THIS IS EXPERIMENTAL *** *** DO NOT APPLY UNLESS YOU HAVE THIS EXPLICIT PROBLEM UNDER NORMAL OPERATING CONDITIONS *** -Matt Matthew Dillon Add to sys/proc.h: #define P_DEADLKTREAT 0x800000 /* lock aquisition - deadlock treatment */ Then patch: Index: kern/kern_lock.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_lock.c,v retrieving revision 1.23 diff -u -r1.23 kern_lock.c --- kern_lock.c 1999/01/20 14:49:11 1.23 +++ kern_lock.c 1999/03/05 03:39:51 @@ -205,9 +205,30 @@ switch (flags & LK_TYPE_MASK) { case LK_SHARED: + /* + * If we are not the exclusive lock holder, we have to block + * while there is an exclusive lock holder or while an + * exclusive lock request or upgrade request is in progress. + * + * However, if P_DEADLKTREAT is set, we override exclusive + * lock requests or upgrade requests ( but not the exclusive + * lock itself ). + */ if (lkp->lk_lockholder != pid) { - error = acquire(lkp, extflags, - LK_HAVE_EXCL | LK_WANT_EXCL | LK_WANT_UPGRADE); + if (p->p_flag & P_DEADLKTREAT) { + error = acquire( + lkp, + extflags, + LK_HAVE_EXCL + ); + } else { + error = acquire( + lkp, + extflags, + LK_HAVE_EXCL | LK_WANT_EXCL | + LK_WANT_UPGRADE + ); + } if (error) break; sharelock(lkp, 1); Index: kern/kern_subr.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_subr.c,v retrieving revision 1.27 diff -u -r1.27 kern_subr.c --- kern_subr.c 1999/02/22 18:39:49 1.27 +++ kern_subr.c 1999/03/05 03:39:52 @@ -63,13 +63,19 @@ { register struct iovec *iov; u_int cnt; - int error; + int error = 0; + int save = 0; KASSERT(uio->uio_rw == UIO_READ || uio->uio_rw == UIO_WRITE, ("uiomove: mode")); KASSERT(uio->uio_segflg != UIO_USERSPACE || uio->uio_procp == curproc, ("uiomove proc")); + if (curproc) { + save = curproc->p_flag & P_DEADLKTREAT; + curproc->p_flag |= P_DEADLKTREAT; + } + while (n > 0 && uio->uio_resid) { iov = uio->uio_iov; cnt = iov->iov_len; @@ -92,7 +98,7 @@ else error = copyin(iov->iov_base, cp, cnt); if (error) - return (error); + break; break; case UIO_SYSSPACE: @@ -111,7 +117,9 @@ cp += cnt; n -= cnt; } - return (0); + if (curproc) + curproc->p_flag = (curproc->p_flag & ~P_DEADLKTREAT) | save; + return (error); } int To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 23:19:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 39EB615143 for ; Thu, 4 Mar 1999 23:19:51 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA91140; Fri, 5 Mar 1999 08:19:28 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903050719.IAA91140@freebsd.dk> Subject: Re: Using Soren's new ATA driver In-Reply-To: <199903050640.AAA18355@mnw.eas.slu.edu> from Eric Haug at "Mar 5, 1999 0:40:39 am" To: ejh@eas.slu.edu (Eric Haug) Date: Fri, 5 Mar 1999 08:19:28 +0100 (CET) Cc: sprice@hiwaay.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Eric Haug wrote: > Hi > I am also seeing this same problem. > With ATA_DEBUG and AD_DEBUG I see that blocks 127 and 2127 > are read successfully and then the panic. Sounds like either it dont get the geometry right, or it uses too many secs/int for the drive to handle. Anyhow there is a new version pending that might fix those.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 4 23:59:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 4F9751509A for ; Thu, 4 Mar 1999 23:59:04 -0800 (PST) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.2/8.8.8) with SMTP id PAA21042 for ; Fri, 5 Mar 1999 15:58:43 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id PAA02405; Fri, 5 Mar 1999 15:58:42 +0800 Message-Id: <199903050758.PAA02405@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Successfully cross-compiling Linux code! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 1999 15:58:42 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, after unpacking various RPMs from my RedHat 5.23 CD, making a number of hardlinks within the library directories under /compat/linux, I've finally got this going. Who do I contact to put together an official Linux development port that'll work? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 0:50:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (unknown [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id D5CCB14FD1 for ; Fri, 5 Mar 1999 00:50:41 -0800 (PST) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Fri, 5 Mar 1999 09:52:42 +0100 Message-ID: <97A8CA5BF490D211A94F0000F6C2E55D097553@s-lmh-wi-900.corpnet.at> From: Ladavac Marino To: 'Peter Jeremy' , dillon@apollo.backplane.com Cc: current@FreeBSD.ORG Subject: RE: Simple DOS against 3.x locks box solid Date: Fri, 5 Mar 1999 09:47:57 +0100 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Peter Jeremy [SMTP:peter.jeremy@auss2.alcatel.com.au] > Sent: Friday, March 05, 1999 4:25 AM > To: dillon@apollo.backplane.com > Cc: current@FreeBSD.ORG > Subject: Re: Simple DOS against 3.x locks box solid > > > As for the general problem, is it sensible to allow a read-only file > to > be mmap'd R/W (with or without MAP_PRIVATE) and then written into? It > would be fairly easy to make mmap() return EACCES if the fd was not > open for writing (or map the memory R/O and SEGV on a write). [ML] Can you say dlopen( "/usr/lib/libc.so")? I thought you could :) Disallow RW MAP_PRIVATE maps of RO files and shared libraries are history. /Marino > Peter > > > 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 Mar 5 1: 8:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (Postfix) with ESMTP id DA2AC150AE for ; Fri, 5 Mar 1999 01:08:09 -0800 (PST) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id EAA11876 for ; Fri, 5 Mar 1999 04:07:54 -0500 (EST) Date: Fri, 5 Mar 1999 04:07:54 -0500 (EST) From: To: current@freebsd.org Subject: Re: Simple DOS against 3.x locks box solid In-Reply-To: <19990304155401.A5710@holly.dyndns.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 Thu, 4 Mar 1999, Chris Costello wrote: > Add /etc/login.conf restrictions if you don't want your users > to do that. Speaking of which... I've always used login.conf to set limits for specific user classes... However, it seems like some login.conf options just don't work. Is there a place I can get detailed information on login.conf (other than the man page) telling what options are implemented, and which ones are not? -- Mike Hoskins Systems/Network Administrator SEI Data Network Services, Inc. http://www.seidata.com "In a world where an admin is rendered useless when the ball in his mouse has been taken out, its good to know that I know UNIX." -- toaster.sun4c.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 1:41:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from jfh00.fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by hub.freebsd.org (Postfix) with ESMTP id 644F81514A for ; Fri, 5 Mar 1999 01:41:06 -0800 (PST) (envelope-from jfh@jfh00.fernuni-hagen.de) Received: (from jfh@localhost) by jfh00.fernuni-hagen.de (8.9.2/8.9.2) id KAA00576; Fri, 5 Mar 1999 10:40:38 +0100 (CET) (envelope-from jfh) To: current@freebsd.org Subject: news from the ATAPI-ZIP frontier MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: Fritz Heinrichmeyer Date: 05 Mar 1999 10:40:38 +0100 Message-ID: <86d82omfzd.fsf@jfh00.fernuni-hagen.de> Lines: 43 User-Agent: Gnus/5.070079 (Pterodactyl Gnus v0.79) Emacs/20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried to use the ZIP-disk with the native file format: First i made everything clean "dd if=/dev/zero of=/dev/rwfd0 count=2" --> 2+0 records in 2+0 records out 1024 bytes transferred in 0.040078 secs (25550 bytes/sec) then i invoced "disklabel -rw wfd0 zip100" --> disklabel: ioctl DIOCWLABEL: Inappropriate ioctl for device then i created a fs with "newfs /dev/rwfd0c zip100" --> Warning: Block size and bytes per inode restrict cylinders per group to 5. /dev/rwfd0c: 196608 sectors in 48 cylinders of 1 tracks, 4096 sectors 96.0MB in 10 cyl groups (5 c/g, 10.00MB/g, 4640 i/g) super-block backups (for fsck -b #) at: 32, 20512, 40992, 61472, 81952, 102432, 122912, 143392, 163872, 184352, then i continued with mount /dev/wfd0c /mnt df -->/dev/wfd0c 92367 0 84978 0% /mnt when copying something to /mnt, i see with dmesg ata0: unwanted interrupt ata0: unwanted interrupt atapi_transfer: bad command phase --- Fritz -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG Elektronische Schaltungen, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://ES-i2.fernuni-hagen.de/~jfh PGP fingerprint (mail for key): 160BDF84 3F2F63C0 5CA20D31 3E42D116 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 1:47:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 6380E150E6 for ; Fri, 5 Mar 1999 01:47:29 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA91401 for current@freebsd.org; Fri, 5 Mar 1999 10:47:12 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903050947.KAA91401@freebsd.dk> Subject: UPDATE2: ATA/ATAPI driver new version available. To: current@freebsd.org Date: Fri, 5 Mar 1999 10:47:12 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Second update to the new ATA/ATAPI driver: Now all actual probing of both ATA & ATAPI devices are done after interrupts are enabled, this kills the last "unwanted interrupts" (and there is no ugly hacks like in the old driver to avoid them). Command interrupt devices are now supported, this applies mostly to older CDROM's and apparently also the ZIP. Fixed problems: Number of total sectors wrong on some older drives. Fixed by not using the LBA size unless we know its valid. There has also been more general code clenaups, some reorgs also. As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. But please tell me how it works for you! Enjoy! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 1:50:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7232015122 for ; Fri, 5 Mar 1999 01:50:01 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA91411; Fri, 5 Mar 1999 10:49:25 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903050949.KAA91411@freebsd.dk> Subject: Re: news from the ATAPI-ZIP frontier In-Reply-To: <86d82omfzd.fsf@jfh00.fernuni-hagen.de> from Fritz Heinrichmeyer at "Mar 5, 1999 10:40:38 am" To: fritz.heinrichmeyer@fernuni-hagen.de (Fritz Heinrichmeyer) Date: Fri, 5 Mar 1999 10:49:25 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Fritz Heinrichmeyer wrote: > > I tried to use the ZIP-disk with the native file format: > when copying something to /mnt, > i see with dmesg > > ata0: unwanted interrupt > ata0: unwanted interrupt > atapi_transfer: bad command phase I think this is fixed in the update I just committed. I still havn't got a writeable ZIP media, but it should arrive soon. Anybody knows how to disable the writeprotect on a ZIP disk WITHOUT having to install DOS/WIN ?? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 1:55: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from jfh00.fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by hub.freebsd.org (Postfix) with ESMTP id 0907C15102 for ; Fri, 5 Mar 1999 01:54:44 -0800 (PST) (envelope-from jfh@jfh00.fernuni-hagen.de) Received: (from jfh@localhost) by jfh00.fernuni-hagen.de (8.9.2/8.9.2) id KAA00271; Fri, 5 Mar 1999 10:54:20 +0100 (CET) (envelope-from jfh) To: current@freebsd.org Subject: PS: news from the ATAPI-ZIP frontier References: <86d82omfzd.fsf@jfh00.fernuni-hagen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: Fritz Heinrichmeyer Date: 05 Mar 1999 10:54:19 +0100 In-Reply-To: Fritz Heinrichmeyer's message of "05 Mar 1999 10:40:38 +0100" Message-ID: <86yalc8do4.fsf@jfh00.fernuni-hagen.de> Lines: 11 User-Agent: Gnus/5.070079 (Pterodactyl Gnus v0.79) Emacs/20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG PS: copying finished never and there was a complete freeze of the workstation, apart from the keyboard beep ... -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG Elektronische Schaltungen, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://ES-i2.fernuni-hagen.de/~jfh PGP fingerprint (mail for key): 160BDF84 3F2F63C0 5CA20D31 3E42D116 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 2:15:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 6BFB314DDC for ; Fri, 5 Mar 1999 02:15:10 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA11320; Fri, 5 Mar 1999 19:14:58 +0900 (JST) Message-ID: <36DFAE57.60DFD4D1@newsguy.com> Date: Fri, 05 Mar 1999 19:13:43 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Kelly Yancey , current@freebsd.org Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? References: <000001be6663$b897bca0$1468f0c6@tech.freedomnet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kelly Yancey wrote: > > have to support ATA devices too. He also suggested a more universal device > name like drv0, drv1, drv2, etc rather than deliniating between whether the > drive is ATA or SCSI...I also think that is a good idea as I don't see any > good reason an application should care whether the drive is ATA or SCSI, as > long as the functionality is provided does it matter how? The boot code might be distressed... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 2:39:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from gaia.euronet.nl (gaia.euronet.nl [194.134.0.10]) by hub.freebsd.org (Postfix) with ESMTP id 4B041150CD for ; Fri, 5 Mar 1999 02:39:44 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: from scones.sup.scc.nl (i307.ztm.euronet.nl [194.134.67.68]) by gaia.euronet.nl (8.8.8/8.8.8) with ESMTP id LAA17161 from for ; Fri, 5 Mar 1999 11:39:26 +0100 (MET) Received: (from daemon@localhost) by scones.sup.scc.nl (8.9.2/8.9.1) id LAA83052 for current@FreeBSD.ORG; Fri, 5 Mar 1999 11:14:12 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by scones.sup.scc.nl with netnews for current@FreeBSD.ORG (current@FreeBSD.ORG) To: current@FreeBSD.ORG Date: Fri, 05 Mar 1999 11:14:05 +0100 From: Marcel Moolenaar Message-ID: <36DFAE6D.DB516F06@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <199903050758.PAA02405@ariadne.tensor.pgs.com> Subject: Re: Successfully cross-compiling Linux code! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > Well, after unpacking various RPMs from my RedHat 5.23 CD, making a number of > hardlinks within the library directories under /compat/linux, I've finally got > this going. Who do I contact to put together an official Linux development > port that'll work? I've made 2 ports (linux-base and linux-devel) based on Red Hat packages, to be used as a substitute for the current ports (linux_lib and linux_devel). I've made them (and an updated port of RPM) available on http://www.wi.leidenuniv.nl/~mhmoolen/ until Mike (or anyone else for that matter) has the time to commit it. I think it's best to talk to me for now, so we can join the best of both. BTW: (cross-)compilation also works with my ports :-) marcel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 3: 5:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 703961518A for ; Fri, 5 Mar 1999 03:04:55 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id UAA18183; Fri, 5 Mar 1999 20:04:43 +0900 (JST) Message-ID: <36DFB9FD.7BD55170@newsguy.com> Date: Fri, 05 Mar 1999 20:03:25 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Peter Jeremy Cc: dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: Simple DOS against 3.x locks box solid References: <99Mar5.141337est.40405@border.alcanet.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: > > Another interim solution would be to `fix' GNU grep so it doesn't > attempt to read() into mmap()'d space. (Having not looked at the > code, I don't know how difficult this would be). Pretend the DoS attack does not exist? :-) I'd hate to make such a grave problem less of a nuisance, being so serious. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 3:13:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.nwnexus.com (smtp04.nwnexus.com [206.63.63.52]) by hub.freebsd.org (Postfix) with ESMTP id 1E20E151CB for ; Fri, 5 Mar 1999 03:13:00 -0800 (PST) (envelope-from wrsomsky@halcyon.com) Received: from gramarye (evt-lx100-ip9.nwnexus.net [204.57.235.9]) by smtp04.nwnexus.com (8.8.8/8.8.8) with ESMTP id DAA31152; Fri, 5 Mar 1999 03:12:42 -0800 (PST) Received: (from wrsomsky@localhost) by gramarye (8.9.2/8.8.8) id DAA44975; Fri, 5 Mar 1999 03:11:22 -0800 (PST) (envelope-from wrsomsky) Date: Fri, 5 Mar 1999 03:11:21 -0800 From: "William R. Somsky" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: Heads up! /etc/rc.conf.site is dead. Message-ID: <19990305031121.A91934@gramarye.halcyon.com> References: <24234.918598869@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <24234.918598869@zippy.cdrom.com>; from Jordan K. Hubbard on Tue, Feb 09, 1999 at 02:21:09PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 09, 1999 at 02:21:09PM -0800, Jordan K. Hubbard wrote: > Rather that listen to people wail over the next few months, it was > decided instead to go to a slight variation on the previous theme in > hopes that more people will be happy with the compromise. > > In essence, what used to be everything in /etc/rc.conf has moved to > /etc/defaults/rc.conf and this file takes care of including > (optionally) /etc/rc.conf and /etc/rc.conf.local. This means that you > can go back to editing /etc/rc.conf again and the expected things will > happen, though those interested in the full set of tunables will still > need to look at /etc/defaults/rc.conf (which, like all defaults to > eventually live in that directory, will be freely upgradable by the > system). > > Since that made rc.conf.site obsolete, it was taken out of the > configuration. Please move it to rc.conf on your system, should you > be one of those folks who installed from an earlier snapshot and are > now updating your /etc from -current or -stable sources (not likely to > be all that many people). This change will also be in 3.1. > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Any chance of something similar being done for make.conf? I've gotten in the habit of only adding stuff at the end, but it's still a pain copying file chunks back and forth. (Well, just "forth" I guess, no "back") ________________________________________________________________________ William R. Somsky wrsomsky@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 3:51: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailin.hkstar.com (cygnus.hkstar.com [202.82.3.13]) by hub.freebsd.org (Postfix) with ESMTP id A3B4C14CAA for ; Fri, 5 Mar 1999 03:50:59 -0800 (PST) (envelope-from c5666305@ursa.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by mailin.hkstar.com (8.8.8/8.8.5) with ESMTP id TAA05371 for ; Fri, 5 Mar 1999 19:50:41 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8+Sun/8.8.8) id TAA05052 for freebsd-current@freebsd.org; Fri, 5 Mar 1999 19:50:40 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199903051150.TAA05052@b1.hkstar.com> Subject: error when make kernel using egcs-1.1.2pre To: freebsd-current@freebsd.org Date: Fri, 5 Mar 1999 19:50:40 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] 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 had successfully made the world using egcs-1.1.2pre. However, i encountered an error when tring to make the kernel. The error is as followings. Anyone knows how to solve it. Thanks. Clarence ======= make depend error ======= cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h ../../i386/i386/genassym.c cc1: Invalid option `-fformat-extensions' *** Error code 1 Stop. ======= make depend error ======= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 3:55:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 6661915124 for ; Fri, 5 Mar 1999 03:55:15 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id MAA91725; Fri, 5 Mar 1999 12:54:49 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903051154.MAA91725@freebsd.dk> Subject: Re: error when make kernel using egcs-1.1.2pre In-Reply-To: <199903051150.TAA05052@b1.hkstar.com> from Chan Yiu Wah at "Mar 5, 1999 7:50:40 pm" To: c5666305@hkstar.com (Chan Yiu Wah) Date: Fri, 5 Mar 1999 12:54:49 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Chan Yiu Wah wrote: > Hi, > > I had successfully made the world using egcs-1.1.2pre. However, i encountered > an error when tring to make the kernel. The error is as followings. Anyone > knows how to solve it. Thanks. > > Clarence > > ======= make depend error ======= > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h ../../i386/i386/genassym.c > cc1: Invalid option `-fformat-extensions' That is a "bruceism" comment it out in the makefile... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 4:40:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 25B9F15118 for ; Fri, 5 Mar 1999 04:40:54 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id EAA66262; Fri, 5 Mar 1999 04:40:33 -0800 (PST) (envelope-from obrien) Date: Fri, 5 Mar 1999 04:40:33 -0800 From: "David O'Brien" To: Chan Yiu Wah Cc: freebsd-current@FreeBSD.ORG Subject: Re: error when make kernel using egcs-1.1.2pre Message-ID: <19990305044033.B66213@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199903051150.TAA05052@b1.hkstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199903051150.TAA05052@b1.hkstar.com>; from Chan Yiu Wah on Fri, Mar 05, 1999 at 07:50:40PM +0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ======= make depend error ======= > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h ../../i386/i386/genassym.c > cc1: Invalid option `-fformat-extensions' > *** Error code 1 If you are up to the task, you can download my bmake framework and modified EGCS sources that have this FreeBSD'ism. FTP the cvs repository from ftp.nuxi.com:/pub/FreeBSD/egcs. It is also available via CVSup. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 5:38:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from jfh00.fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by hub.freebsd.org (Postfix) with ESMTP id 6659915183; Fri, 5 Mar 1999 05:38:12 -0800 (PST) (envelope-from jfh@jfh00.fernuni-hagen.de) Received: (from jfh@localhost) by jfh00.fernuni-hagen.de (8.9.3/8.9.3) id OAA00522; Fri, 5 Mar 1999 14:37:55 +0100 (CET) (envelope-from jfh) To: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: ZIP Drive now working MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: Fritz Heinrichmeyer Date: 05 Mar 1999 14:37:54 +0100 In-Reply-To: ray opera's message of "Fri, 5 Mar 1999 04:07:09 -0800 (PST)" Message-ID: Lines: 14 User-Agent: Gnus/5.070079 (Pterodactyl Gnus v0.79) Emacs/20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now the zip drive works with the old drivers, it was the "vector wdintr" what i changed now. Nothing else controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr I followed a hint in http://www.dancris.com/~p/software/ide_zip.html Where is a place one can learn such secrets? -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG Elektronische Schaltungen, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://ES-i2.fernuni-hagen.de/~jfh PGP fingerprint (mail for key): 160BDF84 3F2F63C0 5CA20D31 3E42D116 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 7:26:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-27.ppp.wenet.net [206.15.85.27]) by hub.freebsd.org (Postfix) with ESMTP id 5B36B15118 for ; Fri, 5 Mar 1999 07:26:35 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id CAA14973; Fri, 5 Mar 1999 02:23:03 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Fri, 5 Mar 1999 02:23:03 -0800 (PST) From: Alex Zepeda To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= Cc: current Subject: Re: news from the ATAPI-ZIP frontier In-Reply-To: <199903050949.KAA91411@freebsd.dk> 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 Fri, 5 Mar 1999, Søren Schmidt wrote: > I think this is fixed in the update I just committed. I still havn't > got a writeable ZIP media, but it should arrive soon. > Anybody knows how to disable the writeprotect on a ZIP disk WITHOUT > having to install DOS/WIN ?? There's a Linux program to do this.. check freshmeat, I think it's called gtkzip (actually I've got a copy here). What it appears to do is send a SCSI command to the ZIP drive (Linux has a SCSI over ATAPI driver to handle such things as ATAPI ZIPs). If you're looking for writable media try some of the non-iomega disks (Verbatim has a two pack for $13/disk, dunno if they sell in Europe), or buy enough ZIP drives to become an Iomega preferred customer (I've seen 5 for 1 and 20 for the price of 5 dealies). From the README: Author: KaYue Mak E-mail: gtkzip@yahoo.com Homepage: http://home.netvigator.com/~sallymak/gtkzip - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 8:11:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id B373A151A3 for ; Fri, 5 Mar 1999 08:11:33 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id KAA24356; Fri, 5 Mar 1999 10:08:39 -0600 (CST) Date: Fri, 5 Mar 1999 10:08:39 -0600 (CST) From: Steve Price To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= Cc: current@FreeBSD.ORG Subject: Re: UPDATE2: ATA/ATAPI driver new version available. In-Reply-To: <199903050947.KAA91401@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 5 Mar 1999, S=F8ren Schmidt wrote: # Second update to the new ATA/ATAPI driver: #=20 # Now all actual probing of both ATA & ATAPI devices are done after # interrupts are enabled, this kills the last "unwanted interrupts" # (and there is no ugly hacks like in the old driver to avoid them). # Command interrupt devices are now supported, this applies mostly # to older CDROM's and apparently also the ZIP. #=20 # Fixed problems: #=20 # Number of total sectors wrong on some older drives. # =09Fixed by not using the LBA size unless we know its valid. #=20 # There has also been more general code clenaups, some reorgs also. #=20 # As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. #=20 # But please tell me how it works for you! This works a little better on my machine. It doesn't panic anymore more. It just hangs where it used to panic. Should I turn on the DEBUG output, hand scribe the output, and send it to you? Thanks, Steve # Enjoy! #=20 # -S=F8ren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 8:16: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt051nb9.san.rr.com (dt051nb9.san.rr.com [204.210.32.185]) by hub.freebsd.org (Postfix) with ESMTP id C9C87151C1 for ; Fri, 5 Mar 1999 08:15:45 -0800 (PST) (envelope-from Studded@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051nb9.san.rr.com (8.8.8/8.8.8) with ESMTP id IAA14163; Fri, 5 Mar 1999 08:15:20 -0800 (PST) (envelope-from Studded@gorean.org) Message-ID: <36E00318.12B57753@gorean.org> Date: Fri, 05 Mar 1999 08:15:20 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: mike@seidata.com Cc: current@FreeBSD.ORG Subject: Re: Simple DOS against 3.x locks box solid References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mike@seidata.com wrote: > > On Thu, 4 Mar 1999, Chris Costello wrote: > > > Add /etc/login.conf restrictions if you don't want your users > > to do that. > > Speaking of which... I've always used login.conf to set limits for > specific user classes... However, it seems like some login.conf > options just don't work. Is there a place I can get detailed > information on login.conf (other than the man page) telling what > options are implemented, and which ones are not? The source is your only guide unfortunately. Several people have promised to do a comprehensive list and update the man page, but no one has come through yet. If you do the research please share your results. :) Good luck, Doug -- *** Chief Operations Officer, DALnet IRC network *** Nominated for quote of the year is the statement made by Representative Dick Armey (Texas), who when asked if he were in the President's place, would he resign, responded: "If I were in the President's place I would not get a chance to resign. I would be lying in a pool of my own blood hearing Mrs. Armey standing over me saying, 'How do I reload this damn thing?'" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 8:20:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 87F3F15094 for ; Fri, 5 Mar 1999 08:20:53 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id KAA31001; Fri, 5 Mar 1999 10:18:53 -0600 (CST) Date: Fri, 5 Mar 1999 10:18:53 -0600 From: Dan Nelson To: Alex Zepeda Cc: =?unknown-8bit?Q?S=F8ren_Schmidt?= , current Subject: Re: news from the ATAPI-ZIP frontier Message-ID: <19990305101853.A30864@dan.emsphone.com> References: <199903050949.KAA91411@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.3i In-Reply-To: ; from "Alex Zepeda" on Fri Mar 5 02:23:03 GMT 1999 X-OS: FreeBSD 3.1-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Mar 05), Alex Zepeda said: > On Fri, 5 Mar 1999, Søren Schmidt wrote: > > > I think this is fixed in the update I just committed. I still > > havn't got a writeable ZIP media, but it should arrive soon. > > Anybody knows how to disable the writeprotect on a ZIP disk WITHOUT > > having to install DOS/WIN ?? > > There's a Linux program to do this.. check freshmeat, I think it's > called gtkzip (actually I've got a copy here). What it appears to do > is send a SCSI command to the ZIP drive (Linux has a SCSI over ATAPI > driver to handle such things as ATAPI ZIPs). That sounds suspiciously like an X app. I use "mzip", which is part of the mtools port. It lets you set/reset the password and software WP bits on a zip disk. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 9: 7:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.is.co.za (apollo.is.co.za [196.4.160.2]) by hub.freebsd.org (Postfix) with ESMTP id EB29C15200; Fri, 5 Mar 1999 09:07:03 -0800 (PST) (envelope-from geoff@hangdog.is.co.za) Received: from admin.is.co.za (admin.is.co.za [196.23.0.9]) by apollo.is.co.za (8.8.6/8.7.5/IShub#2) with ESMTP id TAA01050; Fri, 5 Mar 1999 19:06:44 +0200 (GMT) Received: from hangdog.is.co.za (hangdog.is.co.za [196.26.1.216]) by admin.is.co.za (8.8.6/8.7.3/ISsubsidiary#1) with ESMTP id TAA17730; Fri, 5 Mar 1999 19:06:43 +0200 (GMT) Received: (from geoff@localhost) by hangdog.is.co.za (8.9.2/8.9.2) id TAA00286; Fri, 5 Mar 1999 19:06:43 +0200 (SAST) (envelope-from geoff) From: Geoff Rehmet Message-Id: <199903051706.TAA00286@hangdog.is.co.za> Subject: ATA driver To: sos@freebsd.org Date: Fri, 5 Mar 1999 19:06:42 +0200 (SAST) Cc: current@freebsd.org Reply-To: "Geoff Rehmet" X-Mailer: ELM [version 2.4ME+ PL43 (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 There, I've just decided to keep my list of bonnie tests running. I haven't pulled the latest changes yet, as CVSUP is basically a day behind from cvsup.za.freebsd.org. Here is what I have so far: First committed version of ATA -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ATA 64 3237 69.0 2913 14.0 1409 9.4 2951 59.3 3043 11.6 55.9 2.4 WD 64 2556 54.5 2902 13.3 1457 9.7 1987 40.3 3082 13.2 59.1 2.0 ATA-noX 64 3340 69.7 2984 11.9 1400 8.6 3135 62.4 3182 9.4 135.3 4.4 ATA-noX1 128 3221 68.5 2860 13.4 1169 7.6 2961 58.4 3038 12.2 54.2 2.3 ATA-noX1 128 3169 68.2 2933 12.8 1222 7.8 2944 58.1 3081 12.1 57.8 2.4 ATA-noX1 128 3175 66.9 3017 14.3 1166 7.6 3105 61.2 3142 12.4 56.3 2.4 After CVSUPing changes from 4/3/99 (before UPDATE-2 heads up message) All tests : freshly booted, no X -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ATA2 128 3140 67.6 3023 12.0 1175 7.5 3057 58.8 3068 8.6 56.3 2.0 ATA2 128 3122 67.4 3008 11.9 1161 7.2 3121 62.6 3189 9.1 57.5 2.1 ATA2 128 3125 65.9 2981 11.8 1177 7.1 3064 60.2 3189 9.6 56.5 2.1 The only significant diference is on Sequential block inputs and random seeks where, notably the CU times have gone down. (I have taken no account of other changes in the kernel.) Geoff. -- Geoff Rehmet, The Internet Solution - Infrastructure tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: geoffr@is.co.za URL: http://www.is.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 9:12: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from vrfy.ehlo.com (HSE-TOR-ppp21551.sympatico.ca [209.226.66.109]) by hub.freebsd.org (Postfix) with ESMTP id 24AC115188 for ; Fri, 5 Mar 1999 09:11:52 -0800 (PST) (envelope-from james@ehlo.com) Received: from james by vrfy.ehlo.com with local (Exim 2.12 #3) id 10Iy6X-0006v4-00 for freebsd-current@freebsd.org; Fri, 5 Mar 1999 12:09:41 -0500 Date: Fri, 5 Mar 1999 12:09:40 -0500 From: James FitzGibbon To: freebsd-current@freebsd.org Subject: Suggested change to rc.network Message-ID: <19990305120940.A12421@ehlo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is already a precedent for allowing users to use drop-in replacements for certain network daemons by specifying the path to the daemon in rc.conf. Examples include the ${ntpdate_program} and ${xtnpd_program} variables that are used in /etc/rc.network. Wietse Venema has for some time had a replacement portmapper that uses libwrap to control access using hosts.allow. It doesn't protect the daemons, but it can help disguise what RPC services you are running. I'm suggesting to have rc.network use a ${portmap_program} variable, with a suitable default in /etc/defaults/rc.conf of "/usr/sbin/portmap". Any comments appreciated. -- j. James FitzGibbon james@ehlo.com EHLO Solutions Voice/Fax (416)410-0100 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 9:26: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from ady.warpnet.ro (unknown [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id CAC40151C5 for ; Fri, 5 Mar 1999 09:24:51 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.8.8/8.8.8) with SMTP id TAA09795; Fri, 5 Mar 1999 19:24:55 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Fri, 5 Mar 1999 19:24:55 +0200 (EET) From: Adrian Penisoara To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: the current kernel 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 Tue, 2 Mar 1999, Kenneth Wayne Culver wrote: > with the latest kernel, I have had some problems: > > The first occured when I tried to use the arla AFS client. Everything > loads ok, but then after it is loaded, if I try to use it, the system > crashes. > > Second occured when I tried to start x11amp. The system crashed when I did > that. I have no idea what caused the crashes, but they don't happen with > my 3 day old kernel, and they happen with my 5 minute old kernel. Thanks X11amp always crushed my X server with the plain pcm sound driver; try it with OSS (http://www.se.opensound.com). > > > Kenneth Culver > > 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 Fri Mar 5 9:54: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (Postfix) with ESMTP id 1136815218 for ; Fri, 5 Mar 1999 09:53:18 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id LAA11140; Fri, 5 Mar 1999 11:52:51 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma011138; Fri, 5 Mar 99 11:52:27 -0600 Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (8.9.2/8.9.1) with ESMTP id LAA46377; Fri, 5 Mar 1999 11:52:23 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199903051752.LAA46377@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <19990305120940.A12421@ehlo.com> References: <19990305120940.A12421@ehlo.com> Subject: Re: Suggested change to rc.network Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: James FitzGibbon Cc: freebsd-current@FreeBSD.org Date: Fri, 05 Mar 1999 11:52:23 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sounds fair to me. send-pr a patch. Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org On 5 March 1999 at 12:09, James FitzGibbon wrote: > > There is already a precedent for allowing users to use drop-in replacements > for certain network daemons by specifying the path to the daemon in rc.conf. > Examples include the ${ntpdate_program} and ${xtnpd_program} variables that > are used in /etc/rc.network. > > Wietse Venema has for some time had a replacement portmapper that uses > libwrap to control access using hosts.allow. It doesn't protect the > daemons, but it can help disguise what RPC services you are running. > > I'm suggesting to have rc.network use a ${portmap_program} variable, with a > suitable default in /etc/defaults/rc.conf of "/usr/sbin/portmap". > > Any comments appreciated. > > -- > j. > > James FitzGibbon james@ehlo.co m > EHLO Solutions Voice/Fax (416)410-010 0 > > > 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 Mar 5 9:54:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id A387415164 for ; Fri, 5 Mar 1999 09:54:45 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id SAA10426; Fri, 5 Mar 1999 18:54:22 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id SAA37539; Fri, 5 Mar 1999 18:33:59 +0100 (CET) (envelope-from andreas) Date: Fri, 5 Mar 1999 18:33:59 +0100 From: Andreas Klemm To: "Jordan K. Hubbard" Cc: Chuck Robey , "David O'Brien" , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc Message-ID: <19990305183359.A37263@titan.klemm.gtn.com> References: <31170.920242197@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <31170.920242197@zippy.cdrom.com>; from Jordan K. Hubbard on Sun, Feb 28, 1999 at 02:49:57PM -0800 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.1-STABLE SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 28, 1999 at 02:49:57PM -0800, Jordan K. Hubbard wrote: > > Please keep in mind that if, in our haste, we import a compiler that > > puts instability into FreeBSD, then we've drunk poison. The feature > > A legit concern, but also realize that all of us are talking about > 4.0 here - the new compiler would be an issue we'd have up to a full > year on before the product it's in goes mainstream. If that's not enough > time to work out the compiler issues after switching, I can't imagine > when we WILL have a better time to try and do this then. Progress > entails some pain, and if we're unwilling to suffer any at all then > progress ceases entirely. Agreed. -- 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 Fri Mar 5 10: 1:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 98B3615267 for ; Fri, 5 Mar 1999 10:01:48 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.1/8.9.1) id NAA03386 for current@freebsd.org; Fri, 5 Mar 1999 13:01:30 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <199903051801.NAA03386@misha.cisco.com> Subject: rc.network To: current@freebsd.org Date: Fri, 5 Mar 1999 13:01:30 -0500 (EST) Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (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 How about the optional (ports) software just installs the rc.d/.sh and the user disables the corresponding things in /etc/rc.conf? I just installed xinetd and disabling inetd was rather painless... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 10:21:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 9BE871525B for ; Fri, 5 Mar 1999 10:21:29 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA49076; Fri, 5 Mar 1999 10:21:08 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Mar 1999 10:21:08 -0800 (PST) From: Matthew Dillon Message-Id: <199903051821.KAA49076@apollo.backplane.com> To: Andreas Klemm Cc: "Jordan K. Hubbard" , Chuck Robey , "David O'Brien" , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc References: <31170.920242197@zippy.cdrom.com> <19990305183359.A37263@titan.klemm.gtn.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Sun, Feb 28, 1999 at 02:49:57PM -0800, Jordan K. Hubbard wrote: :> > Please keep in mind that if, in our haste, we import a compiler that :> > puts instability into FreeBSD, then we've drunk poison. The feature :> :> A legit concern, but also realize that all of us are talking about :> 4.0 here - the new compiler would be an issue we'd have up to a full :> year on before the product it's in goes mainstream. If that's not enough :> time to work out the compiler issues after switching, I can't imagine :> when we WILL have a better time to try and do this then. Progress :> entails some pain, and if we're unwilling to suffer any at all then :> progress ceases entirely. : :Agreed. : :-- :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'' : I like idea of being able to choose between two different compilers on the fly -- as in with a kernel config option or a make.conf option. I don't think we can 'replace' gcc in 4.x. It will screw up too many people trying to track down bugs, including me. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 10:55:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id E193215217 for ; Fri, 5 Mar 1999 10:55:35 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id TAA12308; Fri, 5 Mar 1999 19:55:13 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id TAA39735; Fri, 5 Mar 1999 19:54:57 +0100 (CET) (envelope-from andreas) Date: Fri, 5 Mar 1999 19:54:57 +0100 From: Andreas Klemm To: Matthew Dillon Cc: Andreas Klemm , "Jordan K. Hubbard" , Chuck Robey , "David O'Brien" , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc Message-ID: <19990305195457.B39438@titan.klemm.gtn.com> References: <31170.920242197@zippy.cdrom.com> <19990305183359.A37263@titan.klemm.gtn.com> <199903051821.KAA49076@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199903051821.KAA49076@apollo.backplane.com>; from Matthew Dillon on Fri, Mar 05, 1999 at 10:21:08AM -0800 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.1-STABLE SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 05, 1999 at 10:21:08AM -0800, Matthew Dillon wrote: > I like idea of being able to choose between two different compilers > on the fly -- as in with a kernel config option or a make.conf option. > > I don't think we can 'replace' gcc in 4.x. It will screw up too many > people trying to track down bugs, including me. And what about including it as an alternative system compiler ? base: cc gcc g++ c++ egcs: ecc egcc eg++ ec++ Would that be possible ? Like awk and nawk in the past ?! ;-) That would bering an option to people, who want to have it in the base OS ... Andreas /// -- 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 Fri Mar 5 11:13:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 5C31815229 for ; Fri, 5 Mar 1999 11:13:54 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id UAA92478; Fri, 5 Mar 1999 20:13:27 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903051913.UAA92478@freebsd.dk> Subject: Re: UPDATE2: ATA/ATAPI driver new version available. In-Reply-To: from Steve Price at "Mar 5, 1999 10: 8:39 am" To: sprice@hiwaay.net (Steve Price) Date: Fri, 5 Mar 1999 20:13:27 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Steve Price wrote: >This works a little better on my machine. It doesn't panic >anymore more. It just hangs where it used to panic. Should >I turn on the DEBUG output, hand scribe the output, and send >it to you? That would be very helpfull yes... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 11:28:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 27492153EF for ; Fri, 5 Mar 1999 11:28:02 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA50965; Fri, 5 Mar 1999 11:27:41 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Mar 1999 11:27:41 -0800 (PST) From: Matthew Dillon Message-Id: <199903051927.LAA50965@apollo.backplane.com> To: Andreas Klemm Cc: "Jordan K. Hubbard" , Chuck Robey , "David O'Brien" , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc References: <31170.920242197@zippy.cdrom.com> <19990305183359.A37263@titan.klemm.gtn.com> <199903051821.KAA49076@apollo.backplane.com> <19990305195457.B39438@titan.klemm.gtn.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :On Fri, Mar 05, 1999 at 10:21:08AM -0800, Matthew Dillon wrote: :> I like idea of being able to choose between two different compilers :> on the fly -- as in with a kernel config option or a make.conf option. :> :> I don't think we can 'replace' gcc in 4.x. It will screw up too many :> people trying to track down bugs, including me. : :And what about including it as an alternative system compiler ? : :base: cc gcc g++ c++ :egcs: ecc egcc eg++ ec++ : :Would that be possible ? Like awk and nawk in the past ?! ;-) : :That would bering an option to people, who want to have it in :the base OS ... : : Andreas /// : :-- :Andreas Klemm http://www.FreeBSD.ORG/~andreas Well, of course... but that could be a port as easily as it could be put in the base system. In order for it to be useful, we'd have to be able to configure which compiler to use in a kernel config option or something like that. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 11:37:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from Vorlon.odc.net (Vorlon.odc.net [207.137.42.6]) by hub.freebsd.org (Postfix) with ESMTP id B3F5B15206 for ; Fri, 5 Mar 1999 11:37:18 -0800 (PST) (envelope-from nwestfal@odc.net) Received: from Millennium.home.lan (ts006d39.lap-ca.concentric.net [206.173.182.51]) by Vorlon.odc.net (8.8.7/8.8.7) with ESMTP id LAA11951 for ; Fri, 5 Mar 1999 11:36:59 -0800 Date: Fri, 5 Mar 1999 11:36:57 -0800 (PST) From: "Neal E. Westfall" X-Sender: nwestfal@Millennium.home.lan To: current@freebsd.org Subject: kernel hangs with latest ATAPI fixes 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 cvsup'ed about 3:00am PST Mar 5 and started a make buildworld before going to bed. When I got up, I did an installworld and recompiled the kernel, which now hangs right after detecting my ATAPI cdrom drive. Normally the next probe message is "Waiting for SCSI devices to settle" but now it hangs before displaying that message. (The cdrom is the only ATAPI device in the system) Hardware: Asus P6NP5 motherboard Generic ATAPI cdrom on primary master Tekram DC-390U2W SCSI controller (no U2W devices though) Seagate ST15150N on da0 (4 GB) Quantum FIREBALL_TM2110S on da1 (2 GB) On a successful boot with a kernel built the previous day, these things probe like this: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.1.0 ata-pci0: rev 0x00 on pci0.1.1 ata0 at 0x01f0 irq 14 on ata-pci0 de0: rev 0x22 int a irq 12 on pci0.10.0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:40:05:36:73:56 vga0: rev 0x5c int a irq 11 on pci0.12.0 ncr0: rev 0x01 int a irq 9 on pci0.13.0 . . . ata0: unwanted interrupt de0 XXX: driver didn't set ifq_maxlen acd0: < ICD-900AT/ A01> CDROM drive at ata0 as master acd0: drive speed 1367KB/sec, 120KB cache acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Waiting 15 seconds for SCSI devices to settle de0: enabling 100baseTX port changing root device to da0s1a da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 2014MB (4124736 512 byte sectors: 255H 63S/T 256C) da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) -- Neal Westfall mailto:nwestfal@odc.net http://www.odc.net/~nwestfal/ FreeBSD: The Power To Serve! http://www.freebsd.org/ $Id: dot.signature,v 1.2 1998/12/30 08:23:13 nwestfal Exp nwestfal $ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 11:52: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp4.erols.com (smtp4.erols.com [207.172.3.237]) by hub.freebsd.org (Postfix) with ESMTP id 8E5F015210 for ; Fri, 5 Mar 1999 11:52:01 -0800 (PST) (envelope-from shmit@natasya.mrf.va.noc.rcn.net) Received: from natasya.mrf.va.noc.rcn.net (natasya.mrf.va.noc.rcn.net [207.172.25.236]) by smtp4.erols.com (8.8.8/smtp-v1) with ESMTP id OAA10494; Fri, 5 Mar 1999 14:51:43 -0500 (EST) Received: (from shmit@localhost) by natasya.mrf.va.noc.rcn.net (8.9.2/8.9.1) id OAA01129; Fri, 5 Mar 1999 14:51:43 -0500 (EST) Message-ID: <19990305145143.D329@kublai.com> Date: Fri, 5 Mar 1999 14:51:43 -0500 From: Brian Cully To: Matthew Dillon , Andreas Klemm Cc: "Jordan K. Hubbard" , Chuck Robey , "David O'Brien" , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: gcc Reply-To: shmit@kublai.com References: <31170.920242197@zippy.cdrom.com> <19990305183359.A37263@titan.klemm.gtn.com> <199903051821.KAA49076@apollo.backplane.com> <19990305195457.B39438@titan.klemm.gtn.com> <199903051927.LAA50965@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903051927.LAA50965@apollo.backplane.com>; from Matthew Dillon on Fri, Mar 05, 1999 at 11:27:41AM -0800 X-Sender: If your mailer pays attention to this, it's broken. X-PGP-Info: finger shmit@kublai.com for my public key. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 05, 1999 at 11:27:41AM -0800, Matthew Dillon wrote: > :And what about including it as an alternative system compiler ? > : > :base: cc gcc g++ c++ > :egcs: ecc egcc eg++ ec++ > : > :Would that be possible ? Like awk and nawk in the past ?! ;-) > : > :That would bering an option to people, who want to have it in > :the base OS ... > > Well, of course... but that could be a port as easily as it could be > put in the base system. We could do what NetBSD did, which was have both and put an option in /etc/make.conf to the effect of USE_EGCS, which would default to off for now, and default to on when things shake out. Of course, NetBSD knew they were going to egcs, so it wasn't that big a deal for them. -- Brian Cully ``I'm not surprised,'' said I. ``You created God in your own image, and when you found out he was no good you abolished him. It's quite a common form of psychological suicide.'' -- Robertson Davies, Fifth Buisiness To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 11:53:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 192A315211 for ; Fri, 5 Mar 1999 11:53:32 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id UAA17770 for ; Fri, 5 Mar 1999 20:53:14 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id UAA08403 for ; Fri, 5 Mar 1999 20:53:06 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: NTP nanokernel support (experimental) From: Poul-Henning Kamp Date: Fri, 05 Mar 1999 20:53:06 +0100 Message-ID: <8401.920663586@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://www.freebsd.org/~phk/x.nanokernel.gz contains patches relative to -current to implement the new "nanokernel" PLL from Dave Mills. This only works with a ntpd v4, suggest 4.92c or better from: ftp://ftp.eecis.udel.edu/pub/ntp It does still not support the hardpps()/PPS_SYNC support, that will come later. Make sure to configure/make your ntpd-4 from scratch to gain advantage of the new resolution, simple recompilation may not be enough. (You also need to get timex.h from /sys/sys to /usr/include/sys. Make world recommended). You should now be truly limited to hardware performance (xtal tempco and interrupt jitter). Please send comments and observations, both positive AND negative. I am very interested in seing some peerstats files for refclocks running this code. Poul-Henning PS: See also http://www.freebsd.org/~phk/timechan.gif -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 12:22:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 1C1501524E for ; Fri, 5 Mar 1999 12:22:13 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id MAA09777; Fri, 5 Mar 1999 12:21:41 -0800 (PST) (envelope-from obrien) Date: Fri, 5 Mar 1999 12:21:41 -0800 From: "David O'Brien" To: Andreas Klemm Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: gcc Message-ID: <19990305122141.D9602@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <31170.920242197@zippy.cdrom.com> <19990305183359.A37263@titan.klemm.gtn.com> <199903051821.KAA49076@apollo.backplane.com> <19990305195457.B39438@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990305195457.B39438@titan.klemm.gtn.com>; from Andreas Klemm on Fri, Mar 05, 1999 at 07:54:57PM +0100 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And what about including it as an alternative system compiler ? > > base: cc gcc g++ c++ > egcs: ecc egcc eg++ ec++ People it is time to change. PEROID. You can make gcc 2.7.2.3 a port if you really need it. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 12:27:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 418D315229 for ; Fri, 5 Mar 1999 12:27:14 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id OAA10841; Fri, 5 Mar 1999 14:24:24 -0600 (CST) Date: Fri, 5 Mar 1999 14:24:23 -0600 (CST) From: Steve Price To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= Cc: current@FreeBSD.ORG Subject: Re: UPDATE2: ATA/ATAPI driver new version available. In-Reply-To: <199903051913.UAA92478@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 5 Mar 1999, S=F8ren Schmidt wrote: # It seems Steve Price wrote: #=20 # >This works a little better on my machine. It doesn't panic # >anymore more. It just hangs where it used to panic. Should # >I turn on the DEBUG output, hand scribe the output, and send # >it to you? #=20 # That would be very helpfull yes... Ok here goes. This is with ACD_DEBUG, AD_DEBUG, ATA_DEBUG, and ATAPI_DEBUG defined. Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 =09The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #84: Fri Mar 5 12:04:49 CST 1999 steve@zeus.hiwaay.net:/usr/src/sys/compile/zeus Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (300.00-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x652 Stepping=3D2 Features=3D0x183f9ff real memory =3D 134217728 (131072K bytes) avail memory =3D 127909888 (124912K bytes) Preloaded elf kernel "kernel" at 0xf029f000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 int a= irq 255 on pci0.4.0 chip3: rev 0x02 int b= irq 255 on pci0.4.1 chip4: rev 0x02 on pci0.7.0 ata-pci0: rev 0x01 on pci0.7.1 ata: type=3D7118086 class=3D01018001 cmd=3D02800005 ata0: iobase=3D0x01f0 altiobase=3D0x03f6 ata0: mask=3D03 status0=3D50 status1=3D00 ata0: mask=3D03 status0=3D50 status1=3D00 ata0: devices =3D 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=3D0x0170 altiobase=3D0x0376 ata1: mask=3D03 status0=3D50 status1=3D00 ata1: mask=3D03 status0=3D50 status1=3D00 ata1: devices =3D 0xc ata1 at 0x0170 irq 15 on ata-pci0 chip5: rev 0x02 on pci0.7.3 Probing for devices on PCI bus 1: vga0: rev 0xdc int a irq 11 on pci1.0= =2E0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=3D0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in ata-isa1: already registered as ata0 ata1 not found at 0x1f0 ata-isa2: already registered as ata1 ata2 not found at 0x170 ppc0 at 0x378 irq 7 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/7 bytes threshold ep0 not found at 0x300 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface PC-Card VLSI 82C146 (5 mem & 2 I/O windows) pcic: controller irq 3 Initializing PC-card drivers: ep ataintr: entered unit=3D0 ataintr: entered unit=3D0 ad0: ATA-3 disk at ata0 as master ad0: 7815MB (16007040 sectors), 15880 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/in, 0 depth queue ataintr: entered unit=3D1 atapi: queued MODE_SENSE cmd ata_start: entered atapi: trying to start MODE_SENSE cmd ataintr: entered unit=3D1 atapi_interrupt: enter atapi_interrupt: length=3D28 reason=3D0x0a ataintr: entered unit=3D1 atapi_interrupt: enter atapi_interrupt: length=3D28 reason=3D0x03 atapi_interrupt: error=3D0x00 ata_start: entered atapi: phew, got back from tsleep atapi: acd: mode sense 0-20-70-00-00-00-00-00-2a-18-1b-00-71-77-29-23-0d-c= 8-00-10-00-80-0d-c8-00-18-00-00 acd0: CDROM drive at ata1 as master acd0: drive speed 3445KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Card inserted, slot 0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 12:28:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A12EC15349 for ; Fri, 5 Mar 1999 12:28:27 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id MAA16306; Fri, 5 Mar 1999 12:28:08 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id MAA01964; Fri, 5 Mar 1999 12:28:08 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 5 Mar 1999 12:28:08 -0800 (PST) Message-Id: <199903052028.MAA01964@vashon.polstra.com> To: opsys@omaha.com Subject: Re: My current box is borked. In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , opsys wrote: > > I'm trying to build world but now to fix all this and I just get > this: > > cc -O -pipe -I/usr/src/usr.bin/make -I/usr/obj/usr/src/tmp/usr/include > -c /usr > /src/usr.bin/make/arch.c > arch.o: File truncateded > {standard input}: Assembler messages: > {standard input}:1280: FATAL: Can't write arch.o: File truncated > *** Error code 1 > > I get that same error on everything I try compiling. Run "df" and it will probably show you that one of your filesystems is full. Find out what's taking up all the space, and get rid of it. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 13:11:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 487531512B for ; Fri, 5 Mar 1999 13:11:20 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id QAA23789 for ; Fri, 5 Mar 1999 16:11:08 -0500 (EST) Date: Fri, 5 Mar 1999 16:11:07 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@freebsd.org Subject: fd broken/not my fault Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that actually, not through my own fault, the fd driver is broken. I noticed this weeks ago but thought it a fluke since I only had the problem on one computer. However, on the school FreeBSD box, I also notice the same problem! fd0: recal failed ST0 70 cyl 0 fd0: recal failed ST0 70 cyl 0 fd0: recal failed ST0 70 cyl 0 fd0: recal failed ST0 70 cyl 0 fd0c: hard error reading fsbn 16 of 16-31 (No status) fd0: recal failed ST0 70 cyl 0 fd0: recal failed ST0 70 cyl 0 fd0: recal failed ST0 70 cyl 0 fd0: recal failed ST0 70 cyl 0 fd0c: hard error reading fsbn 0 (No status) fd0: recal failed ST0 70 cyl 0 fd0: recal failed ST0 70 cyl 0 fd0: recal failed ST0 70 cyl 0 fd0: recal failed ST0 70 cyl 0 fd0c: hard error reading fsbn 1 (No status) Hope someone knows :( I'll check the recent updates to the driver and see if one of them is at fault. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 14:29:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (Postfix) with ESMTP id 2611A15276 for ; Fri, 5 Mar 1999 14:28:53 -0800 (PST) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id RAA19353; Fri, 5 Mar 1999 17:28:37 -0500 (EST) Date: Fri, 5 Mar 1999 17:28:37 -0500 (EST) From: To: Studded Cc: current@FreeBSD.ORG Subject: Re: Simple DOS against 3.x locks box solid In-Reply-To: <36E00318.12B57753@gorean.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, 5 Mar 1999, Studded wrote: > The source is your only guide unfortunately. Several people have > promised to do a comprehensive list and update the man page, but no one > has come through yet. If you do the research please share your results. Okay, now I know... knowing's half the battle, right? ;) I guess I'll be a good Unix Jedi and use the source... Thanks, and I'll be sure to share anything relevant. -- Mike Hoskins Systems/Network Administrator SEI Data Network Services, Inc. http://www.seidata.com "In a world where an admin is rendered useless when the ball in his mouse has been taken out, its good to know that I know UNIX." -- toaster.sun4c.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 14:58:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by hub.freebsd.org (Postfix) with ESMTP id 81DDF14E31 for ; Fri, 5 Mar 1999 14:58:33 -0800 (PST) (envelope-from ckempf@singularity.enigami.com) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.3/8.9.1) id RAA62221; Fri, 5 Mar 1999 17:58:16 -0500 (EST) To: freebsd-current@FreeBSD.ORG Cc: Subject: World seems a tad broken... Cc: From: Cory Kempf Date: 05 Mar 1999 17:58:15 -0500 In-Reply-To: Brian Feldman's message of "Fri, 5 Mar 1999 16:11:07 -0500 (EST)" Message-ID: <5fzp5rilx4.fsf@singularity.enigami.com> Lines: 20 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG # make -j11 buildworld [...] cc -O2 -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mno-486 -DDO_BAD144 -DBOOTWAIT=5000 -DTIMEOUT= -DBOOTSEG=0x1000 -DBOOTSTACK=0xFFF0 -I/usr/src/sys/i386/boot/cdboot/../biosboot -DCDBOOT -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -aout -nostdinc -I/usr/src/sys/i386/boot/cdboot/../../../../include -I/usr/src/sys/i386/boot/cdboot/../../.. -I/usr/obj/aout/usr/src/sys/i386/boot/cdboot -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/sys/i386/boot/cdboot/../biosboot/table.c In file included from /usr/src/sys/i386/boot/cdboot/../biosboot/boot.h:35, from /usr/src/sys/i386/boot/cdboot/../biosboot/table.c:53: /usr/src/sys/i386/boot/cdboot/../../../ufs/ufs/inode.h:69: parse error before `LIST_ENTRY' /usr/src/sys/i386/boot/cdboot/../../../ufs/ufs/inode.h:69: warning: no semicolon at end of struct or union /usr/src/sys/i386/boot/cdboot/../../../ufs/ufs/inode.h:100: parse error before `}' *** Error code 1 Stop. +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 Fri Mar 5 15:20:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles168.castles.com [208.214.165.168]) by hub.freebsd.org (Postfix) with ESMTP id 343D715328 for ; Fri, 5 Mar 1999 15:20:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA06961; Fri, 5 Mar 1999 15:14:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903052314.PAA06961@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans Cc: dcs@newsguy.com, current@FreeBSD.ORG, sheldonh@iafrica.com, sos@freebsd.dk Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-reply-to: Your message of "Wed, 03 Mar 1999 03:46:34 +1100." <199903021646.DAA26990@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 1999 15:14:15 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> >The only thing that bit me was that I used wd0 and wd2 with the older > >> >driver, whereas the newer driver automatically decided to use ad0 and > >> >ad1. This is "expected" behaviour, but it's something for other weenies > >> >to watch out for. :-) > >> > >> This breakage was announced :-). > > > >Besides, it is not even a breakage. It finally got _unbroken_. :-) > > It is breakage, and should be fixed. It's only just now been fixed. The convention on the i386 platform is to pack unit numbers; the 'wd' driver was our sole exception (the BIOS and the SCSI code both pack unit numbers). Since it's now consistent with everything else, it should stay as-is. Wiring ATAPI units down is of limited utility, but should probably be supported for people that like those silly removable drive sleds. -- \\ 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 Mar 5 16:26:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163]) by hub.freebsd.org (Postfix) with SMTP id 7968A1527C for ; Fri, 5 Mar 1999 16:26:51 -0800 (PST) (envelope-from tr49986@rcc.on.ca) Received: from a35 ([207.164.233.111]) by speed.rcc.on.ca (8.6.12/8.6.9) with SMTP id UAA13508 for ; Fri, 5 Mar 1999 20:40:59 -0500 Message-ID: <000201be6767$8400f420$2300000a@a35.my.intranet> From: "RT" To: Subject: NFS Troubles Continued... Date: Thu, 4 Mar 1999 07:39:43 -0500 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.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yesterday being daring I installed SoftUpdates. Works great locally, but now I find that my NFS problems occur more often. I've also removed the ne2000 cards from my system (as someone told me they may be causing network traffic problems). The 3coms remain in the server. On the client machine. I tried to compile a program (which consistently locks up in the configure program when locating the X headers). After this locked up, I then attempted to copy files from the same NFS mount to another place on that mount. Pid UserName Pri Nice Size Res State Time Wcpu cpu Command 1073 dark -2 0 844k 468k getblk 0:00 0.00% 0.00% imake 128 dark 2 0 208k 80k sbwait 0:00 0.00% 0.00% nfsiod 1097 dark -5 0 308k 136k nfsfsy 0:00 0.00% 0.00% cp Please note, I have 6 nfsiod sessions going (started with the appropriate flags). The others weren't doing anything interesting. The NFS mount is still readable, it is not writable. This occurrence did not make a .nfs###### file on server or client. If someone (appropriate) wants to test this out themselves, I can give root access on both the server and a client machine (via ssh shell). Problem occurred with 3.0-release, 3-stable, and 4-current (tested up to last weekends image). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 17: 1:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles168.castles.com [208.214.165.168]) by hub.freebsd.org (Postfix) with ESMTP id 8F50515269 for ; Fri, 5 Mar 1999 17:01:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA07519; Fri, 5 Mar 1999 16:51:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903060051.QAA07519@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: sobomax@altavista.net Cc: =?x-user-defined?Q?S=F8ren?= Schmidt , current@FreeBSD.ORG Subject: Re: CALL FOR TESTERS of new ATA/ATAPI driver.. In-reply-to: Your message of "Wed, 03 Mar 1999 16:16:49 +0200." <36DD4451.C74DCA90@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Fri, 05 Mar 1999 16:51:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is results of testing my machine (Toshiba Satellite Pro 445CDX > notebook). Shows not very huge improvement yet ;) The 1403 is a pretty slow drive, and the IDE interface in most of the = Satellites just plain sucks. > ad0: ATA-? disk at ata0 as master > ad0: 1376MB (2818368 sectors), 2796 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 0 depth queue I used to have one of these in another Satellite. I now have: wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S and its performance still sucks. At least its > 4x bigger. 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 Mar 5 17:10:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles168.castles.com [208.214.165.168]) by hub.freebsd.org (Postfix) with ESMTP id 26236152B0 for ; Fri, 5 Mar 1999 17:09:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA27943; Fri, 5 Mar 1999 17:04:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903060104.RAA27943@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: David Wolfskill Cc: freebsd-current@freebsd.org Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-reply-to: Your message of "Wed, 03 Mar 1999 10:26:57 PST." <199903031826.KAA98780@pau-amma.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 1999 17:04:21 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Date: Thu, 04 Mar 1999 02:53:09 +0900 > >From: "Daniel C. Sobral" > > >Irrespective of all the valid reasons to allow for wiring (but not > >mandate), static drive numbering is not BIOS compatible (thus, not > >DOS compatible). This violates POLA. > > I'm at least as much against POLA violations as anyone... but the real > POLA violation I see is the apparent dependence on the BIOS, since it is > "controlled" by a process external to the UNIX environment. > > "DOS compatability" is not one of my concerns; I have difficulty imagining > a universe in which it would become one. Indeed, if someone were to > claim "DOS compatibility" for something, I would have no way of knowing > what that was supposed to imply, since I'm nearly completely unfamiliar > with DOS. (The few times I've tried to use it, I would get different > results from the same actions on my part, so I gave up.) "DOS compatibility" is irrelevant. What is at issue here is _firmware_ compatability. -- \\ 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 Mar 5 17:13:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-32.ppp.wenet.net [206.15.85.32]) by hub.freebsd.org (Postfix) with ESMTP id 5BC6D152A7 for ; Fri, 5 Mar 1999 17:13:03 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id RAA17716; Fri, 5 Mar 1999 17:10:30 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Fri, 5 Mar 1999 17:10:30 -0800 (PST) From: Alex Zepeda To: Jeremy Lea Cc: Alexander Sanda , "David O'Brien" , current@FreeBSD.ORG Subject: Re: gcc In-Reply-To: <19990302171325.B303@shale.csir.co.za> 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, 2 Mar 1999, Jeremy Lea wrote: > Mozilla will only be ELF, since it is very likely that the minumum > compiler will be egcs. It will also need GTK+, not Motif. Eh no. Look at their web pages, they _recommend_ gcc 2.7.x, so it should still work just fine with a.out systems. > I'm surprised the old Netscape needed libg++... Netscape probably used the most prominent compiler available for FreeBSD/a.out, gcc 2.7.x. This meant using the old libstdc++ which probably depended on libg++. If you feel like hacking around with the Netscape binary, you could try a dummy libg++ to see if it really uses libg++ functions (which I doubt it is). Most likely it's just some stupid libstdc++ dependencies. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 17:14:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-32.ppp.wenet.net [206.15.85.32]) by hub.freebsd.org (Postfix) with ESMTP id 1E702152AD for ; Fri, 5 Mar 1999 17:14:20 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id RAA17727; Fri, 5 Mar 1999 17:12:29 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Fri, 5 Mar 1999 17:12:29 -0800 (PST) From: Alex Zepeda To: Dan Nelson Cc: =?unknown-8bit?Q?S=F8ren_Schmidt?= , current Subject: Re: news from the ATAPI-ZIP frontier In-Reply-To: <19990305101853.A30864@dan.emsphone.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 5 Mar 1999, Dan Nelson wrote: > That sounds suspiciously like an X app. I use "mzip", which is part > of the mtools port. It lets you set/reset the password and software WP > bits on a zip disk. It is an X app based on a cmdline app. But it also is a rather good source for ideas (SCSI over ATAPI!). - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 17:37:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 5BB7E152BB for ; Fri, 5 Mar 1999 17:36:46 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA01801; Fri, 5 Mar 1999 17:35:06 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdfq1792; Sat Mar 6 01:35:01 1999 Date: Fri, 5 Mar 1999 17:34:57 -0800 (PST) From: Julian Elischer To: RT Cc: current@FreeBSD.ORG Subject: Re: NFS Troubles Continued. In-Reply-To: <000201be6767$8400f420$2300000a@a35.my.intranet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is this on 4.x or 3.x? Matt Dillon has been working on softupdates/NFS interactions. if 4.x then he has changes that may help all this.. some will be back ported to 3.x when I get to it.. julian On Thu, 4 Mar 1999, RT wrote: > Yesterday being daring I installed SoftUpdates. Works great locally, but > now I find that my NFS problems occur more often. I've also removed the > ne2000 cards from my system (as someone told me they may be causing network > traffic problems). The 3coms remain in the server. > > On the client machine. I tried to compile a program (which consistently > locks up in the configure program when locating the X headers). After this > locked up, I then attempted to copy files from the same NFS mount to another > place on that mount. > > Pid UserName Pri Nice Size Res State Time Wcpu cpu > Command > 1073 dark -2 0 844k 468k getblk 0:00 0.00% 0.00% > imake > 128 dark 2 0 208k 80k sbwait 0:00 0.00% 0.00% > nfsiod > 1097 dark -5 0 308k 136k nfsfsy 0:00 0.00% 0.00% > cp > > Please note, I have 6 nfsiod sessions going (started with the appropriate > flags). The others weren't doing anything interesting. > > The NFS mount is still readable, it is not writable. This occurrence did > not make a .nfs###### file on server or client. If someone (appropriate) > wants to test this out themselves, I can give root access on both the server > and a client machine (via ssh shell). > > Problem occurred with 3.0-release, 3-stable, and 4-current (tested up to > last weekends image). > > > > > > 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 Mar 5 17:51:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.atl.bellsouth.net (mail1.atl.bellsouth.net [205.152.0.28]) by hub.freebsd.org (Postfix) with ESMTP id 750CB14D78 for ; Fri, 5 Mar 1999 17:51:05 -0800 (PST) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-72-159.atl.bellsouth.net [209.214.72.159]) by mail1.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id UAA17260; Fri, 5 Mar 1999 20:50:14 -0500 (EST) Received: from wghicks (localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id UAA12192; Fri, 5 Mar 1999 20:41:09 -0500 (EST) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199903060141.UAA12192@bellsouth.net> To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: Successfully cross-compiling Linux code! In-reply-to: Your message of "Fri, 05 Mar 1999 15:58:42 +0800." <199903050758.PAA02405@ariadne.tensor.pgs.com> Date: Fri, 05 Mar 1999 20:41:09 -0500 From: W Gerald Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Who do I contact to put together an official Linux development > port that'll work? Uh... man send-pr :-) Thanks! Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 18: 1:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 4A84D14C35; Fri, 5 Mar 1999 18:01:23 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA17166; Sat, 6 Mar 1999 12:31:05 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA09218; Sat, 6 Mar 1999 12:31:04 +1030 (CST) Message-ID: <19990306123104.J490@lemis.com> Date: Sat, 6 Mar 1999 12:31:04 +1030 From: Greg Lehey To: tim@scratch.demon.co.uk, FreeBSD Questions Subject: Re: vinum References: <199903022254.WAA98152@franklin.matlink> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903022254.WAA98152@franklin.matlink>; from tim@scratch.demon.co.uk on Tue, Mar 02, 1999 at 10:54:06PM +0000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [moved from -current to -questions] On Tuesday, 2 March 1999 at 22:54:06 +0000, tim@scratch.demon.co.uk wrote: > Help.. > ======= FreeBSD-CURRENT is designed for discussions about (wait for it) FreeBSD-CURRENT. It is not an appropriate forum for this question. You've already sent a (different) question on this subject to -questions. That's the correct place, so I'm sending it back there. > vinum - is this volume management such like vold in solaris ? I believe it has a similar function. There are other volds which apparently do different things. > am I correct in assuming that the initial boot device cannot be a part > of a vinum volume ? Currently. It's on the wish list, and will get done. > If this is the case then I would need my vinum information on the > initial disk, and can move information from one disk to another, create > a vinum disk and move the information back again ? I'm not quite sure what you mean here. In any case, it depends on your requirements. You can create a file system with just about everything from the root file system except the kernel, and mount that on a Vinum volume. That would be easier than what you propose, and since the kernel file isn't needed too much after booting, it would give you a pretty good resilience. > Is it advantageous to be running vinum ? There are advantages to running vinum, otherwise it wouldn't exist. Only you can determine whether it's right for you. > Is there any documentation other than the manpages on this, i.e > html. ? Take a look at http://www.lemis.com/vinum.html. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 18:34:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles171.castles.com [208.214.165.171]) by hub.freebsd.org (Postfix) with ESMTP id 04F0F15231 for ; Fri, 5 Mar 1999 18:34:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA64778; Fri, 5 Mar 1999 18:19:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903060219.SAA64778@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ville-Pertti Keinonen Cc: Sheldon Hearn , current@freebsd.org Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-reply-to: Your message of "04 Mar 1999 13:05:39 +0200." <86iuchms58.fsf@not.oeno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 1999 18:19:23 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's been like this with SCSI disks since day #1. I don't see it ever having been quite the disaster of epic proportions that you make it out to be. > When a boot fails with something like /dev/rwd2s1g: Device not configured, > how long will it take you to figure out that it was actually wd1 that > didn't probe and what is now visible as wd1 is what you used to know as > wd2? If the disks are identical, you have to look carefully at the boot > messages. If that isn't a POLA violation, what is? Talk about "bike shelter" material. -- \\ 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 Mar 5 18:43:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail0.atl.bellsouth.net (mail0.atl.bellsouth.net [205.152.0.27]) by hub.freebsd.org (Postfix) with ESMTP id 853FD1521A; Fri, 5 Mar 1999 18:43:49 -0800 (PST) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-72-159.atl.bellsouth.net [209.214.72.159]) by mail0.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id VAA16466; Fri, 5 Mar 1999 21:43:17 -0500 (EST) Received: from wghicks (localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id VAA12527; Fri, 5 Mar 1999 21:33:46 -0500 (EST) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199903060233.VAA12527@bellsouth.net> To: obrien@FreeBSD.ORG Cc: Andreas Klemm , Matthew Dillon , freebsd-current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: gcc In-reply-to: Your message of "Fri, 05 Mar 1999 12:21:41 PST." <19990305122141.D9602@relay.nuxi.com> Date: Fri, 05 Mar 1999 21:33:46 -0500 From: W Gerald Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > And what about including it as an alternative system compiler ? > > > > base: cc gcc g++ c++ > > egcs: ecc egcc eg++ ec++ > > > People it is time to change. PEROID. > You can make gcc 2.7.2.3 a port if you really need it. IMHO *everything* in contrib should have a backing "port" which is maintained in synch with the tree and also capable of overriding the corresponding "package" from /usr/src. I don't agree with David 100% about the timing or strategy but do respect the results of his effort and believe that the outcome will be good for FreeBSD. Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 19:57:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B321714EBE for ; Fri, 5 Mar 1999 19:57:09 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA05114; Fri, 5 Mar 1999 19:56:43 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Mar 1999 19:56:43 -0800 (PST) From: Matthew Dillon Message-Id: <199903060356.TAA05114@apollo.backplane.com> To: RT Cc: current@FreeBSD.ORG, Julian Elischer Subject: Re: NFS Troubles Continued. References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Is this on 4.x or 3.x? : :Matt Dillon has been working on softupdates/NFS interactions. :if 4.x then he has changes that may help all this.. :some will be back ported to 3.x when I get to it.. : :julian : :On Thu, 4 Mar 1999, RT wrote: : :> Yesterday being daring I installed SoftUpdates. Works great locally, but :> now I find that my NFS problems occur more often. I've also removed the :> ne2000 cards from my system (as someone told me they may be causing network :> traffic problems). The 3coms remain in the server. :> :... :> Pid UserName Pri Nice Size Res State Time Wcpu cpu :> Command :> 1073 dark -2 0 844k 468k getblk 0:00 0.00% 0.00% :> imake :> 128 dark 2 0 208k 80k sbwait 0:00 0.00% 0.00% :> nfsiod :> 1097 dark -5 0 308k 136k nfsfsy 0:00 0.00% 0.00% :> cp :> :> Please note, I have 6 nfsiod sessions going (started with the appropriate :> flags). The others weren't doing anything interesting. :> :> The NFS mount is still readable, it is not writable. This occurrence did :> not make a .nfs###### file on server or client. If someone (appropriate) :... This feels like something new but until the VFS/BIO/NFS patches are committed to -4.x it isn't possible to tell. It could be a lost buffer due to the nfs B_DONE bug. We know that there are almost certainly still problems with NFS related to sillyrename and/or if the server modifies files directly. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 5 23:16: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles171.castles.com [208.214.165.171]) by hub.freebsd.org (Postfix) with ESMTP id 2A96B14D34 for ; Fri, 5 Mar 1999 23:15:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA66909; Fri, 5 Mar 1999 23:10:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903060710.XAA66909@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" Cc: Kelly Yancey , current@freebsd.org Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-reply-to: Your message of "Fri, 05 Mar 1999 19:13:43 +0900." <36DFAE57.60DFD4D1@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 1999 23:10:17 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Kelly Yancey wrote: > > > > have to support ATA devices too. He also suggested a more universal device > > name like drv0, drv1, drv2, etc rather than deliniating between whether the > > drive is ATA or SCSI...I also think that is a good idea as I don't see any > > good reason an application should care whether the drive is ATA or SCSI, as > > long as the functionality is provided does it matter how? > > The boot code might be distressed... :-) Not as long as the ordering matched the BIOS ordering. The boot code would love it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 2:24:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id E1216151A2 for ; Sat, 6 Mar 1999 02:24:47 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id LAA08324; Sat, 6 Mar 1999 11:24:25 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id LAA68296; Sat, 6 Mar 1999 11:11:12 +0100 (CET) (envelope-from andreas) Date: Sat, 6 Mar 1999 11:11:12 +0100 From: Andreas Klemm To: "David O'Brien" Cc: Chan Yiu Wah , freebsd-current@FreeBSD.ORG Subject: Re: error when make kernel using egcs-1.1.2pre Message-ID: <19990306111112.A68250@titan.klemm.gtn.com> References: <199903051150.TAA05052@b1.hkstar.com> <19990305044033.B66213@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990305044033.B66213@relay.nuxi.com>; from David O'Brien on Fri, Mar 05, 1999 at 04:40:33AM -0800 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.1-STABLE SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 05, 1999 at 04:40:33AM -0800, David O'Brien wrote: > > ======= make depend error ======= > > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h ../../i386/i386/genassym.c > > cc1: Invalid option `-fformat-extensions' > > *** Error code 1 > > If you are up to the task, you can download my bmake framework and > modified EGCS sources that have this FreeBSD'ism. > > FTP the cvs repository from ftp.nuxi.com:/pub/FreeBSD/egcs. FTP Directory: ftp://ftp.nuxi.com/pub/FreeBSD/egcs/ Parent Directory .: Permission denied [As plain directory] -- 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 Sat Mar 6 5:14:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.a2000.nl (farida.a2000.nl [62.108.1.19]) by hub.freebsd.org (Postfix) with ESMTP id 2216D14F68 for ; Sat, 6 Mar 1999 05:14:25 -0800 (PST) (envelope-from alexlh@funk.org) Received: from node1484.a2000.nl ([62.108.20.132] helo=funk.org) by farida.a2000.nl with esmtp (Exim 2.02 #4) id 10JGu7-0007Ek-00 for freebsd-current@freebsd.org; Sat, 6 Mar 1999 14:14:07 +0100 Message-ID: <36E12A3A.294D4E2E@funk.org> Date: Sat, 06 Mar 1999 14:14:34 +0100 From: Alex Le Heux X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: netscape trouebles Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, For quite some time now Netscape 4.5 has been very unstable on my -current system. I've cvsup'ed and made world many times in the hope the problem would go away. Today I decided to ktrace it, and see where it would stop. Of course it now refuses to crash. Even on java stuff that would crash it _every_ time without the ktrace. Now I can start my netscape with "ktrace -f /dev/null netscape", and it'll probably be happy, although this is less than a satisfactory solution. I figure that the fact that it runs fine with the ktrace might mean something significant, although I wouldn't know what. So if anyone has an idea, I'd be delighted to hear about it. The system is a Celeron-366, not overclocked, running -current, XF3.3.3.1 and WindowMaker 0.51.0 and I have plenty of ram (160mb). Netscape is the only application giving me trouble. I've tried the FreeBSD version and the Linux version of Netscape, and they both behave the same. It appears that the Linux version is a bit less stable than the FreeBSD version. Am I the only one with this problem? Alex -- +--------------------------------+-------------------+ | SMTP: | E-Gold: 101979 | | ICBM: N52 22.647' E4 51.555' | PGP: 0x1d512a3f | +--------------------------------+-------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 6:44:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 0A65C15151 for ; Sat, 6 Mar 1999 06:44:10 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 6946 invoked by uid 1001); 6 Mar 1999 14:43:52 +0000 (GMT) To: alexlh@funk.org Cc: freebsd-current@freebsd.org Subject: Re: netscape trouebles From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 06 Mar 1999 14:14:34 +0100" References: <36E12A3A.294D4E2E@funk.org> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 06 Mar 1999 15:43:52 +0100 Message-ID: <6944.920731432@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For quite some time now Netscape 4.5 has been very unstable on my > -current system. I've cvsup'ed and made world many times in the hope the > problem would go away. > > Today I decided to ktrace it, and see where it would stop. > > Of course it now refuses to crash. Even on java stuff that would crash > it _every_ time without the ktrace. > > Now I can start my netscape with "ktrace -f /dev/null netscape", and > it'll probably be happy, although this is less than a satisfactory > solution. > > I figure that the fact that it runs fine with the ktrace might mean > something significant, although I wouldn't know what. So if anyone has > an idea, I'd be delighted to hear about it. I've had an unstable Netscape ever since upgrading to 3.x. There was quite a bit of discussion about this around a month ago, but no firm conclusion was reached. For me, it happens with MOZILLA_NO_ASYNC_DNS turned on (ie. no separate DNS lookup processes) *and* I access a site where the corresponding name servers take a long time to answer. I found some more discussion about Netscape hanging in a Linux related Web page, and the author has also produced a (Linux specific) patch. I include the README file below. Sorry, no URL, but it's real easy to find the package (search for Netscape-pipepatch) with ftpsearch. Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- The Netscape pipe overflow workaround ===================================== There is a known problem with most versions of Netscape currently in use, where the Netscape freezes when loading specific pages. The lockup is complete - there is no window refreshing and no reaction to the kill -TERM. The only way out is to kill the process with SIGKILL or from the window manager and to manually remove the lock file. The problem is timing-dependent - while most people seeing it can reproduce it using specific pages, these pages are different for different people. The cause of this problem is quite simple. On most (if not all Unixes) there is a limit on the pipe size and writing to a pipe will block, if the pipe is full. This limit is 4096 bytes on the Linux. The Netscape uses a pipe for some internal synchronisation and fails to take this into an account. When the pipe overflows, the Netscape locks up trying to write into the pipe and nobody reading it. The presented workaround is a side-effect of narrowing down this problem (the goal was to prove, if this is a kernel or application problem). It is NOT intended as a general solution to the problem (Netscape developers must fix it) and there is NO GUARANTEE that it doesn't break something else. However, the hack helped quite a lot of people and so I decided to publish it. The idea behind this hack is to insert a layer between Netscape and the libc, which catches the problematic pipe and fakes I/O operations that would otherwise cause the lock-up. Installation ============ First you must know what version of Netscape you are using - the keywords here are libc5 and glibc (aka libc6). This is not necessarily the library your distribution defaults to - it is perfectly possible to use libc5 Netscape on a glibc-based system. ldd $MOZILLA_HOME/netscape | grep libc.so will probably give an idea, but there can be broken installations of ldd giving questionable results (e.g. libc.so.5 => not found is a valid answer for a libc5 installation). Next edit the Makefile and check the LIBC and LIBDL variables. These should be OK for a glibc Netscape, you will need to change them for a libc5 one (the instructions for doing this is in the Makefile). Compile and install the hack (the default destination is /usr/local/lib): make make install Now the tricky part - you must set the LD_PRELOAD environment variable to point to your hack somewhere where only Netscape can see it. Generally you do this in some starting script for netscape. As the distributions vary here, you are basically on your own. The patch for Red Hat 5.2 is included (file starting.script.rh52.patch). End remarks =========== The workaround is (C) 1999 Stanislav Meduna. The use, modification and distribution is completely free. There is ABSOLUTELY NO WARRANTY and i will NOT support the workaround. There ARE known problems - it is not known, if they are caused by the hack or only exposed by using it - I will NOT try to fix them. Some of the discussion on this hack is included in the file Discussion. If you include the workaround in some distribution, I would like to hear about it. Stanislav Meduna stano@eunet.sk 30. 1. 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 7:43: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D1851150F4 for ; Sat, 6 Mar 1999 07:43:05 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id QAA96195; Sat, 6 Mar 1999 16:42:44 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903061542.QAA96195@freebsd.dk> Subject: Re: UPDATE2: ATA/ATAPI driver new version available. In-Reply-To: from Steve Price at "Mar 5, 1999 2:24:23 pm" To: sprice@hiwaay.net (Steve Price) Date: Sat, 6 Mar 1999 16:42:44 +0100 (CET) Cc: current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Steve Price wrote: [debug output omitted] I think I know what is failing now, I just have to find a fix for it.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 7:59:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id E9FAF14EE3 for ; Sat, 6 Mar 1999 07:59:21 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id KAA11728 for ; Sat, 6 Mar 1999 10:59:06 -0500 (EST) Date: Sat, 6 Mar 1999 10:59:06 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@freebsd.org Subject: callout changes nit 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 make a habit of checking out any interesting kernel changes in full, and one thing I found in the recent diff by Mr. Wollman for kern_timeout.c is: +void +callout_init(c) + struct callout *c; +{ + bzero(c, sizeof c); } That doesn't look correct, does it? Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 8: 8:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.kersur.net (mail.kersur.net [199.79.199.3]) by hub.freebsd.org (Postfix) with ESMTP id 3C1411520E for ; Sat, 6 Mar 1999 08:08:09 -0800 (PST) (envelope-from dswartz@druber.com) Received: from manticore (manticore.druber.com [207.180.95.108]) by mail.kersur.net (8.9.1/8.9.1) with SMTP id LAA18733; Sat, 6 Mar 1999 11:12:34 -0500 (EST) Message-Id: <3.0.5.32.19990306110744.00992550@mail.kersur.net> X-Sender: druber@mail.kersur.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sat, 06 Mar 1999 11:07:44 -0500 To: Brian Feldman From: Dan Swartzendruber Subject: Re: callout changes nit Cc: current@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:59 AM 3/6/99 -0500, Brian Feldman wrote: >I make a habit of checking out any interesting kernel changes in full, and one >thing I found in the recent diff by Mr. Wollman for kern_timeout.c is: > >+void >+callout_init(c) >+ struct callout *c; >+{ >+ bzero(c, sizeof c); > } > >That doesn't look correct, does it? Sure doesn't to me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 8:41:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 1281D15234 for ; Sat, 6 Mar 1999 08:41:18 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id IAA21472; Sat, 6 Mar 1999 08:41:01 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id IAA44512; Sat, 6 Mar 1999 08:41:00 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 6 Mar 1999 08:41:00 -0800 (PST) Message-Id: <199903061641.IAA44512@vashon.polstra.com> To: green@unixhelp.org Subject: Re: callout changes nit In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Brian Feldman wrote: > I make a habit of checking out any interesting kernel changes in full, and one > thing I found in the recent diff by Mr. Wollman for kern_timeout.c is: > > +void > +callout_init(c) > + struct callout *c; > +{ > + bzero(c, sizeof c); > } > > That doesn't look correct, does it? Agreed. I think it should be "sizeof *c". John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 8:51:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from send101.yahoomail.com (send101.yahoomail.com [205.180.60.87]) by hub.freebsd.org (Postfix) with SMTP id C028915151 for ; Sat, 6 Mar 1999 08:51:51 -0800 (PST) (envelope-from valsho@yahoo.com) Message-ID: <19990306165050.17003.rocketmail@send101.yahoomail.com> Received: from [147.226.106.179] by send101.yahoomail.com; Sat, 06 Mar 1999 08:50:50 PST Date: Sat, 6 Mar 1999 08:50:50 -0800 (PST) From: Valentin Shopov Subject: SNAP --> Current To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I installed 4.0-19990304-SNAP/src/sys and cvsup-ed to current . I found that the last changes of current are not included into snap/src/src (till 03/04/99). Is that o.k.? Val _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 9:35:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id B5A6B14F1F for ; Sat, 6 Mar 1999 09:35:42 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA15507; Sat, 6 Mar 1999 10:35:25 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA24426; Sat, 6 Mar 1999 10:35:14 -0700 Date: Sat, 6 Mar 1999 10:35:14 -0700 Message-Id: <199903061735.KAA24426@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Brian Feldman Cc: current@FreeBSD.ORG Subject: Re: callout changes nit In-Reply-To: References: X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I make a habit of checking out any interesting kernel changes in full, and one > thing I found in the recent diff by Mr. Wollman for kern_timeout.c is: > > +void > +callout_init(c) > + struct callout *c; > +{ > + bzero(c, sizeof c); > } > > That doesn't look correct, does it? Care to expand on why this looks wrong? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 9:36:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 71E601526A for ; Sat, 6 Mar 1999 09:36:50 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA15526; Sat, 6 Mar 1999 10:36:31 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA24445; Sat, 6 Mar 1999 10:36:21 -0700 Date: Sat, 6 Mar 1999 10:36:21 -0700 Message-Id: <199903061736.KAA24445@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: John Polstra Cc: green@unixhelp.org, current@FreeBSD.ORG Subject: Re: callout changes nit In-Reply-To: <199903061641.IAA44512@vashon.polstra.com> References: <199903061641.IAA44512@vashon.polstra.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I make a habit of checking out any interesting kernel changes in full, and one > > thing I found in the recent diff by Mr. Wollman for kern_timeout.c is: > > > > +void > > +callout_init(c) > > + struct callout *c; > > +{ > > + bzero(c, sizeof c); > > } > > > > That doesn't look correct, does it? > > Agreed. I think it should be "sizeof *c". Ahh, I see. I think it should say bzero(c, sizeof(struct callout)); To avoid the compiler using the size of the pointers et. al. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 10: 6:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 9C84015292; Sat, 6 Mar 1999 10:06:20 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id TAA02954; Sat, 6 Mar 1999 19:06:01 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 1B8D3883B; Sat, 6 Mar 1999 16:42:39 +0100 (CET) Date: Sat, 6 Mar 1999 16:42:38 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Cc: Poul-Henning Kamp Subject: Re: NTP nanokernel support (experimental) Message-ID: <19990306164238.A29897@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG, Poul-Henning Kamp References: <8401.920663586@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <8401.920663586@critter.freebsd.dk>; from Poul-Henning Kamp on Fri, Mar 05, 1999 at 08:53:06PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5120 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Poul-Henning Kamp: > Please send comments and observations, both positive AND negative. I can't get my DCF77 device to synchronize with both the kernel diff applied and 4.0.92c. With the older 4.0.90f I'm able to sync. remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) LOCAL(0) 10 - 24 64 377 0.000 0.000 0.000 *GENERIC(0) .DCFa. 0 - 20 64 357 0.000 10.664 0.617 ... remote refid st t when poll reach delay offset jitter ============================================================================== 127.127.1.0 127.127.1.0 10 - 57 64 377 0.000 0.000 0.000 *127.127.8.0 .DCFa. 0 - - 64 357 0.000 15.090 0.193 > I am very interested in seing some peerstats files for refclocks > running this code. 51243 56309.281 127.127.8.0 96f5 0.011960917 0.000000000 0.000000000 0.002261763 51243 56310.281 127.127.8.0 96f5 0.011612083 0.000000000 0.000000000 0.001471172 51243 56311.291 127.127.8.0 96f5 0.011183750 0.000000000 0.000000000 0.000786827 51243 56312.285 127.127.8.0 96f5 0.011175333 0.000000000 0.000000000 0.000718346 51243 56356.278 127.127.8.0 96f5 0.014832500 0.000000000 0.000000000 0.002910501 51243 56357.274 127.127.8.0 96f5 0.015144083 0.000000000 0.000000000 0.003002719 51243 56358.278 127.127.8.0 96f5 0.015144583 0.000000000 0.000000000 0.002788572 51243 56359.274 127.127.8.0 96f5 0.015447583 0.000000000 0.000000000 0.002825388 51243 56360.274 127.127.8.0 96f5 0.015403750 0.000000000 0.000000000 0.002513153 51243 56361.278 127.127.8.0 96f5 0.015087917 0.000000000 0.000000000 0.001963783 51243 56362.285 127.127.8.0 96f5 0.015087917 0.000000000 0.000000000 0.001396828 51243 56363.278 127.127.8.0 96f5 0.015090000 0.000000000 0.000000000 0.000193172 ... 51243 56494.272 127.127.8.0 96f5 0.014399417 0.000000000 0.000000000 0.000286762 51243 56495.277 127.127.8.0 96f5 0.014374750 0.000000000 0.000000000 0.000279898 51243 56496.277 127.127.8.0 96f5 0.014352500 0.000000000 0.000000000 0.000268971 51243 56497.269 127.127.8.0 96f5 0.014813083 0.000000000 0.000000000 0.000284027 51243 56497.652 127.127.8.0 96f5 0.014813083 0.000000000 0.000000000 0.000281249 -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 10:16:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 4441B14CEC for ; Sat, 6 Mar 1999 10:16:29 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id TAA26945; Sat, 6 Mar 1999 19:16:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id TAA14114; Sat, 6 Mar 1999 19:16:04 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Ollivier Robert Cc: current@FreeBSD.ORG Subject: Re: NTP nanokernel support (experimental) In-reply-to: Your message of "Sat, 06 Mar 1999 16:42:38 +0100." <19990306164238.A29897@keltia.freenix.fr> Date: Sat, 06 Mar 1999 19:16:04 +0100 Message-ID: <14112.920744164@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990306164238.A29897@keltia.freenix.fr>, Ollivier Robert writes: >According to Poul-Henning Kamp: >> Please send comments and observations, both positive AND negative. > >I can't get my DCF77 device to synchronize with both the kernel diff >applied and 4.0.92c. With the older 4.0.90f I'm able to sync. It looks synchronized to me, it just looks like it hasn't swung in yet ? I find it very sluggish in reacting too, but I'm not sure yet if it is a feature or a bug. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 10:16:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 498A115286 for ; Sat, 6 Mar 1999 10:16:47 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id NAA17855; Sat, 6 Mar 1999 13:16:25 -0500 (EST) Date: Sat, 6 Mar 1999 13:16:25 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Nate Williams Cc: John Polstra , current@FreeBSD.ORG Subject: Re: callout changes nit In-Reply-To: <199903061736.KAA24445@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 6 Mar 1999, Nate Williams wrote: > > > I make a habit of checking out any interesting kernel changes in full, and one > > > thing I found in the recent diff by Mr. Wollman for kern_timeout.c is: > > > > > > +void > > > +callout_init(c) > > > + struct callout *c; > > > +{ > > > + bzero(c, sizeof c); > > > } > > > > > > That doesn't look correct, does it? > > > > Agreed. I think it should be "sizeof *c". > > Ahh, I see. I think it should say > > bzero(c, sizeof(struct callout)); > > To avoid the compiler using the size of the pointers et. al. > I prefer to do this in my own code, usually. However, using *c doesn't "use the size of the pointer". > > Nate > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 10:35:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 81C8F1528D for ; Sat, 6 Mar 1999 10:35:28 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA15881; Sat, 6 Mar 1999 11:35:08 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA24560; Sat, 6 Mar 1999 11:34:57 -0700 Date: Sat, 6 Mar 1999 11:34:57 -0700 Message-Id: <199903061834.LAA24560@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Brian Feldman Cc: Nate Williams , John Polstra , current@FreeBSD.ORG Subject: Re: callout changes nit In-Reply-To: References: <199903061736.KAA24445@mt.sri.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > I make a habit of checking out any interesting kernel changes in full, and one > > > > thing I found in the recent diff by Mr. Wollman for kern_timeout.c is: > > > > > > > > +void > > > > +callout_init(c) > > > > + struct callout *c; > > > > +{ > > > > + bzero(c, sizeof c); > > > > } > > > > > > > > That doesn't look correct, does it? > > > > > > Agreed. I think it should be "sizeof *c". > > > > Ahh, I see. I think it should say > > > > bzero(c, sizeof(struct callout)); > > > > To avoid the compiler using the size of the pointers et. al. > > > > I prefer to do this in my own code, usually. However, using *c doesn't > "use the size of the pointer". Understood, but the point being that Garrett is an experienced programmer, and made this mistake. The latter version avoids any possibilities of said mistake. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 11: 0:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7C0E714CE5 for ; Sat, 6 Mar 1999 11:00:24 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA21989; Sat, 6 Mar 1999 11:00:06 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id LAA47116; Sat, 6 Mar 1999 11:00:06 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199903061736.KAA24445@mt.sri.com> Date: Sat, 06 Mar 1999 11:00:05 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Nate Williams Subject: Re: callout changes nit Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams wrote: >> > +void >> > +callout_init(c) >> > + struct callout *c; >> > +{ >> > + bzero(c, sizeof c); >> > } >> > >> > That doesn't look correct, does it? >> >> Agreed. I think it should be "sizeof *c". > > Ahh, I see. I think it should say > > bzero(c, sizeof(struct callout)); > > To avoid the compiler using the size of the pointers et. al. This is largely a matter of taste, so we don't need to agree on it. :-) But I do have a specific reason for preferring the "sizeof *c" form. Namely, it reduces redundancy. The advantage is best seen if you consider making a macro for clearing a structure. Here are two possibilities: #define CLEAR_STRUCT(ptr) bzero((ptr), sizeof *(ptr)) #define CLEAR_STRUCT(ptr, type) bzero((ptr), sizeof(type)) In this context, the 1-parameter form is indisputably less error-prone. Of course, the context of the original example was different. So I'm satisfied to say we are both "right". John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 11:18:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id BCC4814E75 for ; Sat, 6 Mar 1999 11:18:16 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id OAA20954; Sat, 6 Mar 1999 14:17:52 -0500 (EST) Date: Sat, 6 Mar 1999 14:17:52 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Nate Williams Cc: John Polstra , current@FreeBSD.ORG Subject: Re: callout changes nit In-Reply-To: <199903061834.LAA24560@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 6 Mar 1999, Nate Williams wrote: > > > > > I make a habit of checking out any interesting kernel changes in full, and one > > > > > thing I found in the recent diff by Mr. Wollman for kern_timeout.c is: > > > > > > > > > > +void > > > > > +callout_init(c) > > > > > + struct callout *c; > > > > > +{ > > > > > + bzero(c, sizeof c); > > > > > } > > > > > > > > > > That doesn't look correct, does it? > > > > > > > > Agreed. I think it should be "sizeof *c". > > > > > > Ahh, I see. I think it should say > > > > > > bzero(c, sizeof(struct callout)); > > > > > > To avoid the compiler using the size of the pointers et. al. > > > > > > > I prefer to do this in my own code, usually. However, using *c doesn't > > "use the size of the pointer". > > Understood, but the point being that Garrett is an experienced > programmer, and made this mistake. The latter version avoids any > possibilities of said mistake. > It's just as easy to make the mistake of typing sizeof(struct foo *); I think there should perhaps be a warning in gcc/egcs about this, like -Wpointer-sizeof that would warn if you try sizeof(c) where c is a pointer, but not sizeof(*c) or sizeof(void *). It would help find this kind of thing, but of course would only be enabled by user-choice, not by default. Maybe I should just write my own linter instead :) > > > Nate > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 12: 9:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from pinhead.parag.codegen.com (unknown [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id 8FB26152B5 for ; Sat, 6 Mar 1999 12:09:46 -0800 (PST) (envelope-from parag@cgt.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.8.8) with ESMTP id MAA59416 for ; Sat, 6 Mar 1999 12:09:29 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199903062009.MAA59416@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@freebsd.org Subject: Lots of warnings in 4.0-CURRENT kernel build 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, 06 Mar 1999 12:09:29 -0800 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just built a new 4.0-CURRENT kernel yesterday and noticed that there seem to be more warnings generated than used to be. I rebuilt it today with the latest sources as of 3am March 6, built a new kernel from scratch (after deleting the entire old build dir), removed the "cc" lines, and got this set of warnings that I've appended to the end of this note. (The kernel does link successfully, and at least last night's kernel is running fine, so this isn't a really critical problem.) I do understand that some of the code is still being worked on, but I thought files such as if_fxp.c and ncr.c are relatively stable now. I'm curious if most people are building kernels without the default warnings or are just ignoring them? I'd be happy to go over all the files and get everything to compile without warnings, but as others have already discovered, the warnings may be indicating real bugs that need fixing. Perhaps the owners could take a closer look? Maybe there should be a daily kernel warnings posting to the mailing list to prompt the owners to fix the code? :-) Or a daily send-pr containing the latest kernel warnings generated? :-) Or am I just pointing out what everyone but me already knows is being worked on? -- Parag Patel kern/init_sysent.c:23: warning: cast discards `volatile' from pointer target type kern/kern_sysctl.c: In function `sysctl_register_set': kern/kern_sysctl.c:127: warning: cast discards `const' from pointer target type kern/kern_sysctl.c: In function `sysctl_unregister_set': kern/kern_sysctl.c:135: warning: cast discards `const' from pointer target type kern/sys_generic.c: In function `write': kern/sys_generic.c:251: warning: assignment discards `const' from pointer target type pci/if_fxp.c: In function `fxp_init': pci/if_fxp.c:1294: warning: passing arg 2 of `bcopy' discards `volatile' from pointer target type pci/if_fxp.c:1351: warning: passing arg 2 of `bcopy' discards `volatile' from pointer target type pci/if_fxp.c: In function `fxp_mc_setup': pci/if_fxp.c:1867: warning: passing arg 2 of `bcopy' discards `volatile' from pointer target type pci/ncr.c: In function `ncr_log_hard_error': pci/ncr.c:5333: warning: cast discards `volatile' from pointer target type pci/ncr.c: In function `ncr_exception': pci/ncr.c:5470: warning: cast discards `volatile' from pointer target type pci/ncr.c: In function `ncr_int_ma': pci/ncr.c:5773: warning: cast discards `volatile' from pointer target type pci/ncr.c:5777: warning: cast discards `volatile' from pointer target type pci/ncr.c:5801: warning: cast discards `volatile' from pointer target type pci/ncr.c:5808: warning: cast discards `volatile' from pointer target type pci/ncr.c:5816: warning: cast discards `volatile' from pointer target type pci/ncr.c:5821: warning: cast discards `volatile' from pointer target type pci/ncr.c:5831: warning: cast discards `volatile' from pointer target type pci/ncr.c:5835: warning: cast discards `volatile' from pointer target type pci/ncr.c: In function `ncr_regtest': pci/ncr.c:6803: warning: cast discards `volatile' from pointer target type pci/ncr.c:6804: warning: cast discards `volatile' from pointer target type In file included from dev/kbd/atkbd.c:336: dev/kbd/kbdtables.h:1151: warning: missing braces around initializer for `key_map.key[0]' i386/isa/ipl_funcs.c: In function `setdelayed': i386/isa/ipl_funcs.c:136: warning: cast discards `volatile' from pointer target type i386/isa/joy.c: In function `joyread': i386/isa/joy.c:169: warning: suggest parentheses around comparison in operand of & i386/isa/sio.c: In function `comhardclose': i386/isa/sio.c:1338: warning: suggest parentheses around && within || i386/isa/sio.c: In function `comparam': i386/isa/sio.c:2000: warning: suggest parentheses around && within || i386/isa/snd/ad1848.c: In function `cs423x_attach': i386/isa/snd/ad1848.c:1587: warning: assignment from incompatible pointer type i386/isa/snd/ad1848.c: In function `opti931_attach': i386/isa/snd/ad1848.c:1690: warning: assignment from incompatible pointer type i386/isa/snd/ad1848.c: In function `opti925_attach': i386/isa/snd/ad1848.c:1755: warning: assignment from incompatible pointer type i386/isa/snd/ad1848.c: In function `guspnp_attach': i386/isa/snd/ad1848.c:1818: warning: assignment from incompatible pointer type i386/isa/snd/ad1848.c: In function `ad1816_intr': i386/isa/snd/ad1848.c:2039: warning: suggest parentheses around comparison in operand of & i386/isa/snd/sbcard.h:358: warning: `sb16_recmasks_L' defined but not used i386/isa/snd/sbcard.h:376: warning: `sb16_recmasks_R' defined but not used libkern/index.c: In function `index': libkern/index.c:48: warning: cast discards `const' from pointer target type libkern/rindex.c: In function `rindex': libkern/rindex.c:52: warning: cast discards `const' from pointer target type pci/es1370.c:150: warning: initialization from incompatible pointer type i386/isa/snd/ulaw.h:40: warning: `dsp_ulaw' defined but not used kern/kern_linker.c: In function `linker_file_sysinit': kern/kern_linker.c:114: warning: assignment discards `const' from pointer target type kern/kern_linker.c: In function `linker_preload': kern/kern_linker.c:971: warning: assignment discards `const' from pointer target type kern/vfs_aio.c: In function `aio_process': kern/vfs_aio.c:558: warning: cast discards `volatile' from pointer target type kern/vfs_aio.c: In function `aio_qphysio': kern/vfs_aio.c:1062: warning: cast discards `volatile' from pointer target type kern/vfs_aio.c: In function `aio_suspend': kern/vfs_aio.c:1499: warning: cast discards `const' from pointer target type kern/vfs_aio.c: In function `aio_read': kern/vfs_aio.c:1701: warning: cast discards `volatile' from pointer target type kern/vfs_aio.c: In function `aio_write': kern/vfs_aio.c:1763: warning: cast discards `volatile' from pointer target type kern/vfs_aio.c: In function `lio_listio': kern/vfs_aio.c:1861: warning: cast discards `const' from pointer target type kern/vfs_aio.c:1896: warning: cast discards `const' from pointer target type ufs/ffs/ffs_softdep.c: In function `deallocate_dependencies': ufs/ffs/ffs_softdep.c:1745: warning: suggest parentheses around assignment used as truth value ufs/ffs/ffs_softdep.c: In function `softdep_disk_write_complete': ufs/ffs/ffs_softdep.c:2957: warning: suggest parentheses around assignment used as truth value ufs/ffs/ffs_softdep.c:2962: warning: suggest parentheses around assignment used as truth value ufs/ffs/ffs_softdep.c:2968: warning: suggest parentheses around assignment used as truth value ufs/ffs/ffs_softdep.c: In function `softdep_sync_metadata': ufs/ffs/ffs_softdep.c:3727: warning: suggest parentheses around assignment used as truth value ufs/ffs/ffs_softdep.c:3846: warning: suggest parentheses around assignment used as truth value ufs/ffs/ffs_softdep.c: In function `flush_pagedep_deps': ufs/ffs/ffs_softdep.c:4154: warning: suggest parentheses around assignment used as truth value ./genassym >assym.s i386/isa/vga_isa.c: In function `comp_adpregs': i386/isa/vga_isa.c:886: warning: missing braces around initializer for `params[0]' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 12:25:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 83745152D0 for ; Sat, 6 Mar 1999 12:25:04 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id PAA24428 for ; Sat, 6 Mar 1999 15:24:49 -0500 (EST) Date: Sat, 6 Mar 1999 15:24:49 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: fd broken In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 5 Mar 1999, Brian Feldman wrote: > It seems that actually, not through my own fault, the fd driver is broken. I > noticed this weeks ago but thought it a fluke since I only had the problem on > one computer. However, on the school FreeBSD box, I also notice the same > problem! The point is that previously, it had stopped working on my home box. Now, it also doesn't work on a different box that had been 3.0 before, and had fd working great. I have not made any modifications to the fd driver. > > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0c: hard error reading fsbn 16 of 16-31 (No status) > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0c: hard error reading fsbn 0 (No status) > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0: recal failed ST0 70 cyl 0 > fd0c: hard error reading fsbn 1 (No status) > > Hope someone knows :( I'll check the recent updates to the driver and see if > one of them is at fault. None of them look like they could be at fault, at least easily. Can someone try using your floppy drive with the latest sources? It doesn't work in two 4.0 machines which have absolutely nothing in common except being 586en. > > Brian Feldman _ __ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 12:40:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa17-24.ix.netcom.com [207.93.156.24]) by hub.freebsd.org (Postfix) with ESMTP id 65DE3152BF for ; Sat, 6 Mar 1999 12:40:11 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id MAA05063; Sat, 6 Mar 1999 12:39:51 -0800 (PST) (envelope-from tomdean) Date: Sat, 6 Mar 1999 12:39:51 -0800 (PST) Message-Id: <199903062039.MAA05063@ix.netcom.com> From: Thomas Dean To: green@unixhelp.org Cc: current@FreeBSD.ORG In-reply-to: (message from Brian Feldman on Sat, 6 Mar 1999 15:24:49 -0500 (EST)) Subject: Re: fd broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the same problem on 4.0-current SMP of Mon Feb 15 03:34:29 PST 1999. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 12:48:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 5637B14C30 for ; Sat, 6 Mar 1999 12:48:13 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id VAA09361 for current@FreeBSD.ORG; Sat, 6 Mar 1999 21:47:54 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 99892883B; Sat, 6 Mar 1999 20:00:53 +0100 (CET) Date: Sat, 6 Mar 1999 20:00:53 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: NTP nanokernel support (experimental) Message-ID: <19990306200053.B30895@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <19990306164238.A29897@keltia.freenix.fr> <14112.920744164@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <14112.920744164@critter.freebsd.dk>; from Poul-Henning Kamp on Sat, Mar 06, 1999 at 07:16:04PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5120 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Poul-Henning Kamp: > It looks synchronized to me, it just looks like it hasn't swung in yet ? The two outputs I sent were with 4.0.90f. When I run 4.0.92c, ntpd is not able to get any accurate data from the device whereas 4.0.90f does. I get lots of these in /var/log/messages and it doesn't sync at all. -=-=- Mar 6 14:02:25 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 3 bits Mar 6 14:02:29 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 2 bits Mar 6 14:02:38 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 2 bits Mar 6 14:02:38 tara ntpd[7600]: PARSE receiver #0: FAILED TIMECODE: "-" (check receiver configuration / cableling) Mar 6 14:02:50 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 2 bits Mar 6 14:02:52 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 2 bits Mar 6 14:03:35 tara ntpd[7600]: PARSE receiver #0: no data from device within poll interval (check receiver / cableling) -=-=- Maybe it is a problem with 4.0.92c... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 12:56:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id A7036152BB for ; Sat, 6 Mar 1999 12:55:55 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id VAA28013; Sat, 6 Mar 1999 21:55:37 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id VAA14471; Sat, 6 Mar 1999 21:55:33 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Ollivier Robert Cc: current@FreeBSD.ORG Subject: Re: NTP nanokernel support (experimental) In-reply-to: Your message of "Sat, 06 Mar 1999 20:00:53 +0100." <19990306200053.B30895@keltia.freenix.fr> Date: Sat, 06 Mar 1999 21:55:32 +0100 Message-ID: <14469.920753732@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This looks like a reception problem. You must be pretty far out in the reception area of DCF77 (just like me), and will probably find that whenever a sunrise or sunset is in the area reception sux. Try to see if it does better in daylight... I don't know the state of the DCF77/parse stuff in v4 at all, I have not tried to use it, I'm relying on my GPS for now. Poul-Henning In message <19990306200053.B30895@keltia.freenix.fr>, Ollivier Robert writes: >According to Poul-Henning Kamp: >> It looks synchronized to me, it just looks like it hasn't swung in yet ? > >The two outputs I sent were with 4.0.90f. When I run 4.0.92c, ntpd is not >able to get any accurate data from the device whereas 4.0.90f does. > >I get lots of these in /var/log/messages and it doesn't sync at all. >-=-=- >Mar 6 14:02:25 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 3 bits >Mar 6 14:02:29 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 2 bits >Mar 6 14:02:38 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 2 bits >Mar 6 14:02:38 tara ntpd[7600]: PARSE receiver #0: FAILED TIMECODE: "-" (check receiver configuration / cableling) >Mar 6 14:02:50 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 2 bits >Mar 6 14:02:52 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 2 bits >Mar 6 14:03:35 tara ntpd[7600]: PARSE receiver #0: no data from device within poll interval (check receiver / cableling) >-=-=- > >Maybe it is a problem with 4.0.92c... >-- >Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr >FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 13:19:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from netlink1.nlcomm.com (netlink1.nlcomm.com [207.87.194.131]) by hub.freebsd.org (Postfix) with ESMTP id A0A5215000 for ; Sat, 6 Mar 1999 13:19:50 -0800 (PST) (envelope-from HellRaza@usa.net) Received: from orbit (modem17.nlcomm.com [207.87.194.151]) by netlink1.nlcomm.com (8.8.7/8.8.7) with SMTP id QAA24554 for ; Sat, 6 Mar 1999 16:19:31 -0500 Message-ID: <004501be6817$30758fe0$0300a8c0@orbit> From: "Nathan M Vargo" To: Subject: Date: Sat, 6 Mar 1999 16:20:40 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0040_01BE67ED.468B58C0" 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 This is a multi-part message in MIME format. ------=_NextPart_000_0040_01BE67ED.468B58C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable auth 99e0b1d8 unsubscribe freebsd-current HellRaza@usa.net ------=_NextPart_000_0040_01BE67ED.468B58C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
auth 99e0b1d8 unsubscribe freebsd-current HellRaza@usa.net
= ------=_NextPart_000_0040_01BE67ED.468B58C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 14:15:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id F1EE314CC9 for ; Sat, 6 Mar 1999 14:15:51 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id RAA13551; Sat, 6 Mar 1999 17:15:28 -0500 (EST) (envelope-from wollman) Date: Sat, 6 Mar 1999 17:15:28 -0500 (EST) From: Garrett Wollman Message-Id: <199903062215.RAA13551@khavrinen.lcs.mit.edu> To: Nate Williams Cc: Brian Feldman , John Polstra , current@FreeBSD.ORG Subject: Re: callout changes nit In-Reply-To: <199903061834.LAA24560@mt.sri.com> References: <199903061736.KAA24445@mt.sri.com> <199903061834.LAA24560@mt.sri.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Understood, but the point being that Garrett is an experienced > programmer, and made this mistake. The latter version avoids any > possibilities of said mistake. ...and instead opens up the possibility of the same bug if the type of the structure is ever changed. I will fix this (currently harmless) problem later today. -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 Sat Mar 6 15: 6:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179]) by hub.freebsd.org (Postfix) with ESMTP id 9EEAF15174 for ; Sat, 6 Mar 1999 15:06:10 -0800 (PST) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sat, 6 Mar 1999 18:01:01 -0500 (EST) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sat, 6 Mar 1999 15:01:00 -0800 (PST) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sat, 6 Mar 1999 18:00:59 -0500 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: Ollivier Robert , current@FreeBSD.ORG Subject: Re: NTP nanokernel support (experimental) In-Reply-To: Poul-Henning Kamp's (phk@critter.freebsd.dk) message dated Sat, 06 Mar 1999 21:55:32. <14469.920753732@critter.freebsd.dk> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Mar 1999 18:00:59 -0500 Message-ID: <19169.920761259@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just got a new set of PARSE patches from Frank Kardel, and I'm waiting for Dave Mills to give me the go-ahead to commit them. Dave is chasing some possible bugs and wanted a stable codebase for a while. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 18:39:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from pm06sm.pmm.cw.net (pm06sm.pmm.cw.net [208.159.98.155]) by hub.freebsd.org (Postfix) with ESMTP id 7366C14BFF for ; Sat, 6 Mar 1999 18:39:20 -0800 (PST) (envelope-from lopez@mv.mv.com) Received: from mv.mv.com (usr42-dialup28.mix2.Boston.cw.net [166.62.76.92]) by PM06SM.PMM.CW.NET (PMDF V5.2-29 #35324) with ESMTP id <0F8700KROE09O8@PM06SM.PMM.CW.NET> for current@FreeBSD.ORG; Sun, 7 Mar 1999 02:38:55 +0000 (GMT) Date: Sat, 06 Mar 1999 21:38:37 -0500 From: "Lawrence D. Lopez" Subject: Re: callout changes nit To: Brian Feldman Cc: current@FreeBSD.ORG Message-id: <36E1E6AD.807C5DC7@mv.mv.com> MIME-version: 1.0 X-Mailer: Mozilla 4.05 [en] (X11; U; Linux 2.0.30 i586) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ah, bzero(c, sizeof *c); I suppose. Brian Feldman wrote: > > I make a habit of checking out any interesting kernel changes in full, and one > thing I found in the recent diff by Mr. Wollman for kern_timeout.c is: > > +void > +callout_init(c) > + struct callout *c; > +{ > + bzero(c, sizeof c); > } > > That doesn't look correct, does it? > > Brian Feldman _ __ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > 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 Mar 6 18:55: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 2E0C31528F for ; Sat, 6 Mar 1999 18:55:03 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id SAA23360; Sat, 6 Mar 1999 18:54:44 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id SAA47884; Sat, 6 Mar 1999 18:54:43 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 6 Mar 1999 18:54:43 -0800 (PST) Message-Id: <199903070254.SAA47884@vashon.polstra.com> To: geoffr@is.co.za Subject: Re: ATA driver In-Reply-To: <199903051706.TAA00286@hangdog.is.co.za> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199903051706.TAA00286@hangdog.is.co.za>, Geoff Rehmet wrote: > > I've just decided to keep my list of bonnie tests running. I haven't > pulled the latest changes yet, as CVSUP is basically a day behind > from cvsup.za.freebsd.org. Are you sure? The CVSup server logs on freefall show that cvsup.za.freebsd.org has been updating itself reliably every hour. Or did you mean you're having trouble getting into it? If so, it might be worth trying cvsup2.za.freebsd.org instead. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 19: 8:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8D7F914C9B for ; Sat, 6 Mar 1999 19:08:22 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id TAA23400; Sat, 6 Mar 1999 19:08:04 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id TAA47913; Sat, 6 Mar 1999 19:08:03 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 6 Mar 1999 19:08:03 -0800 (PST) Message-Id: <199903070308.TAA47913@vashon.polstra.com> To: A.M.Zanker@open.ac.uk Subject: Re: Typo in new atapi-all.c In-Reply-To: <4.1.19990304100812.00cb03e0@aire.open.ac.uk> References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <4.1.19990304100812.00cb03e0@aire.open.ac.uk>, Mike Zanker wrote: > At 10:03 04/03/99 , Sheldon Hearn wrote: > > >I'm living in the past again. Fixed in rev1.225 of files.i386 . Update > >your src/sys/i386/conf, since LINT has been updated as well. > > Hmm, I just did but via cvsup.uk.freebsd.org. Maybe the fix hasn't > propagated to there yet. For small updates that you want immediately, CVSWeb is your friend: http://www.freebsd.org/cgi/cvsweb.cgi John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 22:37:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from ftp.dns.ne.jp (ftp.dns.ne.jp [210.155.3.5]) by hub.freebsd.org (Postfix) with ESMTP id 856B114C93; Sat, 6 Mar 1999 22:37:15 -0800 (PST) (envelope-from tanimura@sakuramail.com) Received: from silver.carrots (yksk3DS46.kng.mesh.ad.jp [210.147.34.92]) by ftp.dns.ne.jp (8.9.2/8.8.5) with ESMTP id PAA07822; Sun, 7 Mar 1999 15:36:45 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by silver.carrots (8.9.2+3.1W/3.7W) with ESMTP id PAA06791; Sun, 7 Mar 1999 15:36:52 +0900 (JST) To: bde@freebsd.org Cc: Seigo TANIMURA , freebsd-current@freebsd.org Subject: State "CPU255" in top(1) on an SMP box. From: Seigo TANIMURA X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990307153651W.tanimura@silver> Date: Sun, 07 Mar 1999 15:36:51 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 20 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I cvsuped, made and installed the world at 04:00 7th May 1999 (JST) on my SMP box to find that the STATE in top(1) displayed "CPU255" for some processes. I have only 2 CPUs... [/usr/src/usr.bin/top/machine.c:char *format_next_process(handle, get_userid)] if (smpmode && PP(pp, p_oncpu) == 0xff) ^^ this should be '!='. Seigo TANIMURA |M1, Nakagawa Lab, Dept of Electronics & CS =========================|Faculty of Engineering, Yokohama National Univ Powered by SIEMENS, |http://www.naklab.dnj.ynu.ac.jp/~tanimura/ FreeBSD 4.0-CURRENT |http://www.sakura.ne.jp/~tcarrot/ (7th Mar 1999) & muesli. |tanimura@naklab.dnj.ynu.ac.jp tcarrot@sakuramail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 6 22:57:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 62AC4152FC; Sat, 6 Mar 1999 22:57:42 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA26471; Sun, 7 Mar 1999 17:57:23 +1100 Date: Sun, 7 Mar 1999 17:57:23 +1100 From: Bruce Evans Message-Id: <199903070657.RAA26471@godzilla.zeta.org.au> To: bde@freebsd.org, tanimura@naklab.dnj.ynu.ac.jp Subject: Re: State "CPU255" in top(1) on an SMP box. Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >[/usr/src/usr.bin/top/machine.c:char *format_next_process(handle, get_userid)] > > if (smpmode && PP(pp, p_oncpu) == 0xff) > ^^ > this should be '!='. Oops. Thanks for the fix. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message